Anatoli wrote: > Hi all, > > It looks like there is a bug in PJSIP, but I've submitted a bug in Asterisk > tracker as I'm not sure if it occurs only in connection with res_pjsip or as > stand-alone as well. > > Basically, when an endpoint registers via TCP, PJSIP processes everything as > corresponds: the communication is via TCP, REGISTER/ACK pass OK, the > endpoint can even establish calls. But, when another endpoint calls to the > first one, PJSIP tries to send INVITE message in a new TCP session > establishing it to the port already opened for the first session. This would > be OK for a UDP, but not for TCP. Please let me know if you observe the same > behavior without asterisk as well. I've responded on the issue but to keep everyone on this mailing list in the loop. PJSIP currently has an issue where if a transport selector is provided with a TCP factory it will not reuse any existing connections. The configuration used here caused that to happen, so there would indeed never be a reused connection. As well res_pjsip in Asterisk provides a rewrite_contact configuration option which will rewrite the contact to the source IP address and port. This works even for TCP. The existing TCP connection gets reused. Cheers, -- Joshua Colp Digium, Inc. | Senior Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - US Check us out at: www.digium.com & www.asterisk.org
