[SIPForum-discussion] What is the use of record-route in 200 OK

[Stewart Bunce]

Record-Route headers are used to specify an ordered list of proxies which all subsequent requests in a dialogue must traverse. Your handling of the Record-Route headers will depend upon what kind of device you are in the SIP network (proxies treat them differently to a B2BUA for instance). Record-Route only really applies to the signalling messages so it shouldn't directly affect transmisson of the RTP packets, however it would affect the routing of the ACK message from A.
 
Could you provide a little more information on your network setup, and the nature of the device you are testing (i.e. is it a proxy, B2BUA, UA etc) as this will help determine if your use of the Record-Route headers is correct.
 
Stew

-----Original Message-----
From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org]On Behalf Of VG
Sent: 23 July 2008 15:21
To: discussion at sipforum.org
Subject: [SIPForum-discussion] What is the use of record-route in 200 OK


Hi All,

I like to know what is the use of record-route in 200Ok msg.
I got a invite from A with two record-route and i send with 2 record-route to B.

When I got 200ok from B then I get only one record route from my proxy,
Now I am sending this msg containg 1 record route to A.

But rtp doesn't travel in this case.
So I like to know whether record-route is the thing that is creating problem.

Regards,
Vikas




NOTICE & DISCLAIMER 
This email including attachments (this "Document") is confidential and may contain legally privileged information.  If you have received this Document in error please notify the sender immediately and delete this Document from your system without using, copying, disclosing or disseminating it or placing any reliance upon its contents.  We cannot accept liability for any breaches of confidence arising through use of this Document.

The information contained in this Document is provided solely for information purposes on an "as is" basis without warranty of any kind, either express or implied, including without limitation any implied warranty of satisfactory or merchantable quality, fitness for a particular purpose or freedom from error or infringement.  The user relies on the information contained herein, and its accuracy or otherwise, entirely at their own risk.

Any opinions expressed in this Document are those of the author and do not necessarily reflect the opinions of Telsis.  We will not accept responsibility for any commitments made by our employees outside the scope of our business.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20080724/0b70fbef/attachment-0002.html>