Not sure what the RFC's take is on this. May be experts on this forum could comment. Clearly its an ambigous message. But still if you wanted to process it, check the CSeq method, whatever CSeq method is listed process the message as that method. for example if it says "CSeq: 123 UPDATE", process it as an UPDATE message. Santosh
--- On Fri, 6/7/13, Jagan Mohan <[email protected]> wrote: From: Jagan Mohan <[email protected]> Subject: [SIPForum-discussion] Processing a SIP message containing multiple Request-Lines To: "SIP Implementors" <[email protected]>, "[email protected]" <[email protected]> Date: Friday, June 7, 2013, 2:55 PM Hello, I'm having this scenario, where there are multiple Request-Lines in the received SIP message. INVITE sip:[email protected] SIP/2.0 UPDATE sip:[email protected] SIP/2.0 BYE sip:[email protected] 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 -----Inline Attachment Follows----- _______________________________________________ This is the SIP Forum discussion mailing list TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion Post to the list at [email protected] _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
