Hi, I was of the view of section 16.7. If the context is not proxy, then it should follow the rule in section 8.2.6.2 which states, "The Via header field values in the response MUST equal the Via header field values in the request and MUST maintain the same ordering.". regards Ranga
Ranga <[EMAIL PROTECTED]> wrote:Hi, AFIK, UAS should calculate the response destination from the top via header and remove the same from the response. regards Rao [EMAIL PROTECTED] wrote: hi, RFC states following in section 8.2.6 "The Via header field values in the response MUST equal the Via header field values in the request and MUST maintain the same ordering." following is my view:- The UAS must not dilute any information carried in the request's VIA headers, in the response message. it may have added more information such as "recieved" parameter, but existing information from the request should remain as it is. not mentioning sent-by port 5060 in the response, still holds the via header same as the request message's via. But, I feel it is better practice to *not* do such changes and preserve the request's VIA parameters as they are. as of now I cant think of any implications of not keeping 5060 explicit in the response as it was in request. regards, Shetti "Kasam Patil" orks.com> To Sent by: sip-implementors- cc [EMAIL PROTECTED] ia.edu Subject [Sip-implementors] Via Header in Response 08/10/04 07:59 AM Hi, Is it a MUST to have the Via header in the response be exactly the same as in response ? For example, take a look at the PRACK and 200 OK exchange (seen below). Is the 200 OK response acceptable ? Thanks for your time, Kasam <==== INCOMING MSG (389 BYTES) ON UDP PORT 5060 FROM 10.77.28.68 21:21:49.93 PRACK sip:[EMAIL PROTECTED] SIP/2.0 Via: SIP/2.0/UDP 10.77.28.68:5060;branch=z9hG4bK1i5qd520ag5rq9gft1s0.1sr From: ;tag=SD28qa802-1_1146_f150_f136 To: ;tag=a4d18280921214932 Call-ID: SD28qa802-1f6c8351b311c990cf0181d53f039b57-v3000i1 CSeq: 2 PRACK RAck: 7654 1 INVITE Content-Length: 0 Max-Forwards: 69 =====> OUTGOING UDP MSG (300 BYTES) TO 10.77.28.68 : 5060 ON SIP_CALLP_SOCKET 226 21:21:49.93 SIP/2.0 200 OK Via:SIP/2.0/UDP 10.77.28.68;branch=z9hG4bK1i5qd520ag5rq9gft1s0.1sr To:;tag=a4d18280921214932 From:;tag=SD28qa802-1_1146_f150_f13 6 Call-ID:SD28qa802-1f6c8351b311c990cf0181d53f039b57-v3000i1 CSeq:2 PRACK l:0 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.732 / Virus Database: 486 - Release Date: 7/29/2004 _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors "DISCLAIMER: This message is proprietary to Hughes Software Systems Limited (HSS) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. HSS accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors --------------------------------- Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors --------------------------------- Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
