Hi Jagan, Ideally all the SIP messages should contain one Request-Line. Here we see three Request-Lines, so it is a bad request and I feel it should be responded with 400 Bad Request. Some entity in the n/w might be manipulating the SIP message to contain multiple request lines. By the way what is the Method Name added in the C-Seq Header?
Regards Srinivas From: discussion-boun...@sipforum.org [mailto:discussion-boun...@sipforum.org] On Behalf Of Jagan Mohan Sent: Friday, June 07, 2013 2:55 PM To: SIP Implementors; discuss...@sipforum.org Subject: [SIPForum-discussion] Processing a SIP message containing multiple Request-Lines Hello, I'm having this scenario, where there are multiple Request-Lines in the received SIP message. INVITE sip:t...@server.com<mailto:sip%3at...@server.com> SIP/2.0 UPDATE sip:t...@server.com<mailto:sip%3at...@server.com> SIP/2.0 BYE sip:t...@server.com<mailto:sip%3at...@server.com> SIP/2.0 From: ... To: ... Call-ID: ... Via: ... < Message Body> Here, I see there are two possible solutions to handle this. 1) Just use the first request line and continue processing the SIP message as if it's an INVITE in this case. 2) Respond with a 400 Bad Request. Though my preference is to go with the first solution, I would like to know which solution should be preferred. I could not find any reference to this behavior, in any RFC. Is there any standard which talks about the same? Thanks, Jagan _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
