All:
We recently ran into a UAC which registers many AORs
all using the same call-id and from tag (with incremented
CSEQ). Our initial belief that this was disallowed, but
a re-read of Section 10 seems to indicate that this is in
fact the prescribed behavior for an UAC since it makes
no mention of the number of AORs being registered...
Call-ID: All registrations from a UAC SHOULD use the same Call-ID
header field value for registrations sent to a particular
registrar.
If the same client were to use different Call-ID values, a
registrar could not detect whether a delayed REGISTER request
might have arrived out of order.
CSeq: The CSeq value guarantees proper ordering of REGISTER
requests. A UA MUST increment the CSeq value by one for each
REGISTER request with the same Call-ID.
Presumably, the only reason we have NOT seen other UACs doing
this is that it limits them to serially registering all the AORs...
UAs MUST NOT send a new registration (that is, containing new Contact
header field values, as opposed to a retransmission) until they have
received a final response from the registrar for the previous one or
the previous REGISTER request has timed out.
Can someone more familiar with this situation comment on whether
it is fact the expected behavior for such a UAC with many AORs?
Appreciate any info or links to prior email threads.
Thanks and cheers,
Shaun Bharrat
Sonus Networks
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
