Hi,
If proxy A adds a record route and send it to proxy B then in case
if the proxy B wants to
send any request again to proxy A , it will use the ip,port and transport
information from its route set. If
proxy B doesn't support the transport that has mentioned in the route set
(the record route already updated by proxy A)
then it can't able to use the same. So inorder to avoid this conflict in
the transport protocol, RFC 3261 states that the
URI ( in record route ) SHOULD NOT contain the transport parameter unless
the proxy has
knowledge (such as in a private network) that the next downstream element
that will be in the path of subsequent requests supports that transport."
So if proxy A is quite sure about the transport supported in proxy B then
it can add transport in Record Route.
Regards,
S.Kingston Smiler.
"Atul kumar Jha" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/27/2006 01:27 PM
To
<[email protected]>
cc
Subject
[Sip-implementors] Query on the Record-Route in the Call
StatefulProxy/Transaction Stateful Proxy
Hi All,
When Proxy (CSP) record-routes and adds the IP Address and port in the
Record-Route, should it add the transport also in the Record route in
this case?
Here the Proxy decided to add the IP Address in stead of domain names.
If the transport parameter is not added, ACK request or any further
request will come on the IP Address and port as specified on the
Record-Route but not on the particular Transport( if Proxy does not
specify the transport in the Record-Route).The original INVITE is sent
on TCP/SCTP transport.
But as per RFC 3261, we should not add the transport in the
Record-Route. The section 16.6 point 4 Para 7 states:
"The URI SHOULD NOT contain the transport parameter unless the proxy has
knowledge
(such as in a private network) that the next downstream element
that will be in the path of subsequent requests supports that
transport."
So please suggest if I want to continue other requests on the same
transport as the Initial INVITE.
Regards,
Atul
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
*********************** FSS-Unclassified ***********************
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
