Brett Tate <br...@broadsoft.com> writes: > In my opinion if the device doesn't want to support it, it can reject the > request (although there might be a better failure response). However, > there might be interoperability reasons to support it. > > In my opinion, you are experiencing a non-compliant reuse of Call-ID; > however some vendors have interpreted RFC 3261 differently. It has been > many years since I've seen the topic debated; thus I'm not sure if anyone > or sipcore is currently defending such Call-ID reuse as compliant.
I agree with this -- A device MUST NOT originate a call with a Call-ID that has ever been used before, therefore a UAS may reject an INVITE that attempts to create a dialog using a Call-ID that has been used for a previous dialog, as a reasonable way to cope with the error condition. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
