Which header are you concerned with? In the Via, it needs to be left as is because the entity that added it is listening on that transport. In the Record Route it should also be left as is, but a proxy can modify it in responses for a RR it added in a corresponding request.
For the IPSec tunnel, I suppose it would depend on if the SIP application was decrypting the tunnel, or if the tunnel was decrypted before the SIP app saw the message. In the latter case, the application is listening for the transport in the tunnel. Let the list know if you run into any problems with different transports, I haven't heard of many implementations using anything other than UDP. John Hearty Level3 -----Original Message----- From: Terry Pollen [mailto:[EMAIL PROTECTED]] Sent: Monday, October 08, 2001 7:40 AM To: [EMAIL PROTECTED] Subject: [Sip-implementors] Transport parameter Hi all, I have a couple of questions regarding the transport parameter. Firstly, should the transport parameter be set on a hop-by-hop basis or should it be left unchanged from that sent by the UA, draft bis-04 does not seem very clear on this. Also, where an IPSec tunnel is used, should the transport parameter be set to 'tls' or should it be set to indicate the transport being used in the tunnel e.g. udp, tcp. Many thanks Terry Pollen BTexact Technologies _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
