Hi, One way a Registrar can trigger registrations is by sending a message to a multicast addr, requesting the identified UAs are all the UAs to register, when needed. This can be triggered when the Registrar loses all the registration data or other scenarios.
This needs quite a bit of Support on the UA as well as the Registrar and quite a bit of issues around this. The UAs have to join/listen to the multicast session and the registrar has to multicast the registration triggering messages. Just a thought. Good material for a RFC ;). Kasturi -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dale R. Worley Sent: Tuesday, December 20, 2005 10:02 AM To: Sip-Implementors Subject: Re: [Sip-implementors] Stimulate a Re-Registration On Tue, 2005-12-20 at 10:50 -0500, Peter Musgrave wrote: > If I have a registrar which has been off the air for awhile (and some > registration intervals have expired) is there anything in SIP which allows > me to tell a UA that it should try and re-register now - or do I just have > to wait for its internal timer to decide to re-register? It depends on who "me" is -- The registrar can't tell the UA, because (by hypothesis) it has lost knowledge of the UA's existence. The user of the UA ought to be able to instruct the UA to attempt to register itself, but that is a matter of UA design, not the SIP protocol. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
