I think we cannot infer from rfc...just based on most of the implementations We check a received message based on the dialog-id and not the call-id. As in your case FTag changed it is not matching so it should be taken as new call.
But I did see a text in 3261: 8.1.1.4 All SIP UAs must have a means to guarantee that the Call-ID header fields they produce will not be inadvertently generated by any other UA . so from 3261..rejecting this call is also ok... ________________________________________ From: Arunachalam Venkatraman (arunvenk) [EMAIL PROTECTED] Sent: Wednesday, October 29, 2008 7:03 PM To: Kanumuri, Sreeram; Paul Kyzivat (pkyzivat) Cc: [email protected] Subject: RE: [Sip-implementors] Call-id Use ( Re-use/Misuse) RFC 3261 does say the call-id has to be spatially and temporally unique. How can we draw the inference from the RFC that a UA must accept a call-id, for a new INVITE from another UA, that could only be generated by it ? _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
