The RFC4475 fails to indicate which Call-Id to place within the 400 response. :)
Some requests are too malformed to bother returning a 400 response. Some vendors feel that a duplicated or missing Call-ID falls into that category; other vendors will return a 400 (even if the 400 is also malformed). Concerning rfc4475, "This document is informational and is NOT NORMATIVE on any aspect of SIP." > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Pavesi, > Valdemar (NSN - US/Boca Raton) > Sent: Thursday, May 20, 2010 3:40 PM > To: ext Satyakumar; RAVI KUMAR; Iñaki Baz Castillo > Cc: [email protected] > Subject: Re: [Sip-implementors] Two different callID in same invite > message. > > > RFC4475 --> Session Initiation Protocol (SIP) Torture Test Messages > > > > > 3.3.8. Multiple Values in Single Value Required Fields > > The message contains a request with multiple Call-ID, To, From, Max- > Forwards, and CSeq values. An element receiving this request must > not break. > > An element receiving this request would respond with a 400 Bad > Request error. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
