2015-11-24 13:30 GMT+01:00 Gaurav Khare <gaurav.kh...@onmobile.com>: > I wanted to know if any unsupported parameter in SIP Header comes in INVITE > request which is not part of any SIP standard then while framing the response > is UAS obliged to include the same unsupported parameter in the header ? > > For ex see below INVITE receiving and 180 Ringing sent, observe the missing > "yop" parameter from Via and Record-Route header in SIP 180 Ringing message. > UAS SIP stack doesn't understand the "yop" parameter and hence discarded it. > Can someone point me to any RFC section which says clearly that whatever my > UAS stack is doing is correct or not.
In page 14 RFC 3261 states: This response contains the same To, From, Call-ID, CSeq and branch parameter in the Via as the INVITE, which allows Alice's softphone to correlate this response to the sent INVITE. This is: the Via in the response MUST have the same ;branch param, but it is not mandated to have other parameters present in the request's Via. -- Iñaki Baz Castillo <i...@aliax.net> _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
