inline
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?
Yes I understand the level of conformity. We are hoping to get an
agreement
with the UA developers to comply to this functionality and use it to
*really*
know that UA has rebooted. And yes, for our application we need to know if
a UA
has rebooted. Is there any other way defined in the standard which will
indicate this information explicitly?
2 possible clues:
Some UACs I have seen
1 - start with CSeq=1 after they have rebooted, and then increase from
there.
2 - send initial REGISTER without credentials, get challenged, and then
include the credentials in subsequent refreshes (sometimes being
re-challenged)
Both not 100% guaranteed or specified in any standard though. Of these two I
guess number (2) is more guaranteed than (1), but requires that you use
authentication (which you SHOULD anyway)
Jeroen
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
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
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
