MI> "RFC 3261 states that "A UA SHOULD use the same Call-ID for all registrations during a single boot cycle." Note the level of conformity required - it's 'SHOULD' strength rathert than 'MUST' strength, so inferring that the UA has rebooted from a change in the Call-ID in REGISTER may be an error. If you *really* want to know when a UA has rebooted I guess you need to transport that information explicitly. Do you *really* want to know that?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 17 November 2005 14:34 To: Steve Langstaff; [email protected] Subject: Re: [Sip-implementors] Call-ID usage by UA within the same boot cycle, after ... In a message dated 11/17/2005 5:23:07 AM Eastern Standard Time, [EMAIL PROTECTED] writes: I don't think that you can make the assertion that "technically a UA is still within the same boot cycle even when the network connection is lost". I have come across network devices that reboot themselves if they lose network connection for a long period. In the particular case I'm thinking of the device would attempt to DHCP for it's network address etc, but would also run a master timer to reboot itself if it didn't obtain a lease within a certain time. Yes, I agree with you. Great point. Thanks ! Actually I want to use the change of Call-ID in REGISTER as a trigger to indicate that UA rebooted for one of the application we are designing. So wanted to ensure that it's safe to assume that Call-ID in REGISTER should be changed only after a reboot of the UA. And in case of network failure, if the UA hasn't rebooted, Call-ID should not be changed. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Thanks & Regards Monica Ingudam (Mail: [EMAIL PROTECTED]) Signal Engineer AOL Dulles _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
