Hi Dale, If you receive the message through UDP, you have to send it through UDP. Similarly it was TCP, you also have to send it through TCP. But Event though the original message was UDP, if the size is over MTU (normally less than 1500) it have to send through to TCP. If you don't do that, the UDP could be fragmented.
---------------------------------------------------------------------- Young-Joon Ryu (Alex) Team Manager IMS Platform Team Nable Communications, Inc. Tel : +82-2-3288-4334 (Ext:236) Mobile: +82-10-7701-8853 Fax: +82-2-558-8325 Email : [EMAIL PROTECTED] http://www.nablecomm.com ----------------------------------------------------------- -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, November 15, 2007 1:22 PM To: [email protected] Subject: Re: [Sip-implementors] How to determine transport to use from Route header Can anyone please tell me How to find out the transport protocol to send the request, when we have to use the Route header for determining next hop. Suppose we have a Route header with the value Route: <sip:10.58.2.21:5060;lr>, <sip:10.48.2.40:5061;lr> Now because the first route value contains the lr parameter so the IP and Port of the next hop will be 10.58.2.21 and 5060 respectively, But How to find out the transport to be used in this case. This problem is also seen when there is no Route header, and you have to use the request-URI to determine where to send the message. The rules are rather complicated -- RFC 3263 gives all the details. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
