If you are using SER you have a few options... none of the are pretty. You can have ser replicate changes to the other proxy via SERs built-in SIP replication which has limitations.
You can try the new experimental usrloc-cl module to store everything in a DB then use database sync. If you don't want the users to register again you can use a hot-standby setup with linux HA, so you only present one IP address to the client, or possibly use DNS SRV. I am working through some of these issues right now as well so may not be 100% correct. - Daryl On 10/20/05, sandeep kamath <[EMAIL PROTECTED]> wrote: > Hi All, > > Another query. > > Lets say I have deployed a SIP proxy - "PROXY-A" to which a very large > number of users are registered. I need to bring down PROXY-A for maintenance > and replace it with PROXY-B but donot want the users to register again. Is > there some way by which PROXY-B can pull the info out of PROXY-A so that the > customers donot see this transition. > > Is it possible for a SIP Proxy to fwd all the learnt registration > information to a backend central registrar. If any call needs to be routed > (eg: an invite message being received) the proxy can lookup the central > registrar and route the call . I want to know if this is a valid config and > do any SIP proxies support this as of now. > > > thanks, > sandeep > > > > On 10/20/05, sandeep kamath <[EMAIL PROTECTED]> wrote: > > > > Hi Dale, > > Thanks for the info. So from what I understand a single registration is > > possible . Are you aware if SER supports it. Or for that matter do other > > commercial SIP registrars support this feature. > > > > thanks again, > > sandeep. > > > > On 10/19/05, Dale R. Worley <[EMAIL PROTECTED]> wrote: > > > > > > On Wed, 2005-10-19 at 22:09 +0530, sandeep kamath wrote: > > > > I wanted to know if SER has a mechanism where it can exchange the > > > > information wrt the client registerations with other participating SER > > > > proxies. I doubt if SIP has a mechanism to do so. I guess it should be > > > a > > > > protocol that the SER proxies may have. > > > > > > A SIP registrar can actively duplicate its information into another SIP > > > registrar by doing third-party REGISTERs to it. So at the level of a > > > single registration, SIP has a mechanism. The more complex matter is > > > the process that, when a new registration is received, propagates it to > > > the other registrars. There is no mechanism in SIP for this. (Although > > > it is not a protocol matter per se, so that is not surprising.) > > > > > > Dale > > > > > > > > > _______________________________________________ > > > Sip-implementors mailing list > > > [email protected] > > > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > > > > > > > _______________________________________________ > Sip-implementors mailing list > [email protected] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
