Why should a proxy worry with packet fragmentation issue? The IP stack would reassembled it. As far as SIPProxy, or UA it will get the complete reassembled packet.
By default UDP is supported by UA. So the Proxy can try first sending transport=udp, and if it fails, it can try using TCP. Maybe you can provide some use cases explaining your problem? Thanks, Neel -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tai-Hsing Yu Sent: Tuesday, February 22, 2005 8:59 PM To: [email protected] Subject: [Sip-implementors] RE: Questions of handling large request message Yes, I agree that the implementations MUST be able to handle messages up to 65K. But a situation is that if the client behinds NAT, the UDP packets larger than 1300 bytes might be fragmented and has the UDP fragmention issue. What should be proxy do under this situation, send the request packet using UDP or TCP when user registers to Proxy/Registrar with "transport=udp" or without "transport" parameter?? Thanks, fish You can still send REQUEST larger than 1300 bytes. If you read in the same section it says However, implementations MUST be able to handle messages up to the maximum datagram packet size. For UDP, this size is 65,535 bytes, including IP and UDP headers. Refer to Section 19.1.4. it says the two URIs are different. sip:[EMAIL PROTECTED] (can resolve to different transports) sip:[EMAIL PROTECTED];transport=udp Thanks, Neel _______________________________________________ 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
