You're dealing with the signalisation, introducing a webapp driven
configuration can lead to some nice timeout/response time issues left to
investigate, or create an additional spof...

Regarding your example of offering a kamailio hosting service, or
dedicated proxies, I would do the absolute opposite, and deal with the
different configurations at the configuration management level ( very
easy to do with Ansible or Chef ) and some kind of orchestration/CD, but
that may be just me making sure that the proxies have a constant
response time, and that they do not add more than 5ms delay on heavy
loads...

I can only see this functionality being useful as a PoC or for extremely
small traffic, or for early beginners but they'll (eventually|probably)
do differently when they learn better Kamailio...

On top of that, with the embedded scripting engines, you can already
code something like that ( do a http request in lua, parse the result
and process or just run the code in result ). Doing that inside scripts
gives also more flexibility on the error handling side, allowing you
custom fallback back-ends, or very short timeout and default actions, ...

My 2 cents...

On 03/02/2016 11:38 AM, Tim Chubb wrote:
> Indeed I would have an almost immediate use for such a feature if it was 
> possible, same if you wanted to offer a kamailio hosting service or dedicated 
> proxies per carrier, reseller or customer.  It would also make the creation 
> of a kamailio config/dev webapp quite straight forward (install kam, point it 
> to webapp url, start, without having to run a webserver on the kamailio box 
> to write to local config files) which would help lower the bar of 
> understanding when it comes to people getting started with kamailio in much 
> the same way as you get CLI and ASDM when configuring a Cisco ASA... (Its 
> also something I would be able to contribute back to the community as whilst 
> my c skills are novice, I was a webdev for many years before I got into 
> devops)
>
> -----Original Message-----
> From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of 
> Alex Balashov
> Sent: 02 March 2016 19:23
> To: sr-users@lists.sip-router.org
> Subject: Re: [SR-Users] Kamailio 5.0 - HTTP loading of config files
>
> On 03/02/2016 02:20 PM, Tim Chubb wrote:
>
>> Another impetus for wanting to load config from HTTP is that you could 
>> serve dynamic config from a web app, i.e. customer specific configs 
>> for dedicated proxies
> Yeah, that's true. I could see that being useful for those exotic cases where 
> a large amount of Kamailio instances is fleet-managed.
>
> --
> Alex Balashov | Principal | Evariste Systems LLC
> 303 Perimeter Center North, Suite 300
> Atlanta, GA 30346
> United States
>
> Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list 
> sr-users@lists.sip-router.org 
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Reply via email to