[Serdev] Concept for a SIP cluster implementation

[Greger V. Teigre]

>> I don't want to use SRV, not only because of the NAT problem but also
>> because most of the SRV implementations in UACs I've seen so far are 
>> broken, if implemented at all.
>>
>> So each edge proxy will be set up with a hot-standby proxy for IP 
>> failover, so there's no need for a failover mechanism in the UAC (to be 
>> as much independent from it as possible).
>>
>> If the first edge proxy pair (say sip1.my.domain) get's to a limit 
>> regarding ressources, you can add a second pair and propagate the new 
>> hostname (sip2.my.domain) to new customers.
>
> Thus, you solve the problem by provisioning. Btw: Openwengo (cross 
> plattform SIP phone) fetches all the SIP provisioning from the service 
> provider using https. Thus, it would be easy to change SIP configuration 
> and host certain accounts on certain SIP proxies. I like this.

Openwengo looks interesting, smart concept.  BTW, sipura and grandstream can 
also use http/https for SIP provisioning.  Hopefully more and more phones 
get T069 support too.  Anybody knows about a GPLed T069 management server?!
g-)