Hi again, I just noticed that I missed this part when I skimmed through the FAQ. "Since PJSIP version 1.4, we have a feature to automatically switch transport to TCP when request size is larger than (default) 1300 bytes. See ticket #831<http://trac.pjsip.org/repos/ticket/831> for more info." I guess that means that the switching should work if done right. Best regards, Karl-Rikard ________________________________ Fr?n: pjsip-bounces at lists.pjsip.org [pjsip-bounces at lists.pjsip.org] f?r Karl-Rikard L?ndell [Karl-Rikard.Landell at cybercom.com] Skickat: den 13 oktober 2011 12:00 Till: pjsip at lists.pjsip.org ?mne: [pjsip] Problem with long SIP messages Hi everyone, I have problems with SIP messages that have become too large. When that happens, the server tries to set up a TCP connection instead, but the pjsua client doesn't ACK the TCP SYN. A TCP reset is sent instead. The server then tries to use fragmented UDP messages, but the client doesn't respond at all to those. I found this in the mailing list: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2009-January/006158.html "No we don't do automatic switching to TCP. Personally I feel that the RFC is a bit too naive in this regard, ignoring scenarios such as NAT where you can't just send response with TCP back to the client and expect it to just work. So my take on this is if you think message size is going to cause problem with UDP, then you should use TCP from the start." The mail is from January 2009. Is this still the case? I am using version 1.8.10, would upgrading to the latest greatest version to me any good, or is it still unsupported? About fragmented UDP messages, is that also unsupported? Best regards, Kalle _______________________________________________ Visit our blog: http://blog.pjsip.org<http://blog.pjsip.org/> pjsip mailing list pjsip at lists.pjsip.org http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
