The question was the response and the response is 400-bad request. Now , based on first or second callid . I think it works like VIA/ROUTE , normally the first VIA/RPUTE must be used. Then I think the first CALLID-ID will be enough JUST to TELL to the client
that there is a bad REQUEST and it will never break the SERVER. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext 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. Message Details : multi01 INVITE sip:[email protected] SIP/2.0 Contact: <sip:[email protected]> Via: SIP/2.0/UDP 192.0.2.25;branch=z9hG4bKkdjuw Max-Forwards: 70 CSeq: 5 INVITE Call-ID: [email protected] CSeq: 59 INVITE Call-ID: [email protected] From: sip:[email protected];tag=3413415 To: sip:[email protected] To: sip:[email protected] From: sip:[email protected];tag=2923420123 Content-Type: application/sdp l: 154 Contact: <sip:[email protected]> Max-Forwards: 5 v=0 o=mhandley 29739 7272939 IN IP4 192.0.2.25 s=- c=IN IP4 192.0.2.25 t=0 0 m=audio 49217 RTP/AVP 0 12 m=video 3227 RTP/AVP 31 a=rtpmap:31 LPC -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Satyakumar Sent: Thursday, May 20, 2010 1:09 PM To: RAVI KUMAR; Iñaki Baz Castillo Cc: [email protected] Subject: Re: [Sip-implementors] Two different callID in same invite message. Hi, There is nothing like two callids, It is a unique identifier for the call-leg/session. Hence it should match with the request callid. Regards, Satyakumar ----- Original Message ----- From: "RAVI KUMAR" <[email protected]> To: "Iñaki Baz Castillo" <[email protected]> Cc: <[email protected]> Sent: Thursday, May 20, 2010 12:08 AM Subject: Re: [Sip-implementors] Two different callID in same invite message. Thanks for your response! I understand call-Id should be unique for one call and 4xx should be proper response. Does any sip rfc mention what ideally we should do if we get two different call-id. rgds, Ravi On 5/19/10, Iñaki Baz Castillo <[email protected]> wrote: > > 2010/5/19 RAVI KUMAR <[email protected]>: > > > Now my question is what should be ideal behaviour in this case ? > > > > 1. we should not expect two different call-ID as a part of same invite > > message at the first point itself as callID is unique for the call? We > can > > say invite itself is not proper ? > > This is invalid. 400 should be a proper response. > > > > 2. we should process the invite message and check the integrity of > message ? > > since we have two different call - ID as a part of same invite > message ,we > > should send 4xx bad request. > > Yes, 400. No more. > > > > 3. Concatenating the call-ID is nowhere expected ? Anyother possible > > solution? > > It makes no sense at all. > > > -- > Iñaki Baz Castillo > <[email protected]> > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail immediately and permanently delete the message and any attachments. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
