On Wed, 2009-10-07 at 12:27 -0400, Andy Spitzer wrote: > Woof! > > Is SIP (specifically our proxy) supposed to re-send data on a TCP/IP > connection? If it doesn't get any response via TCP, should it close the > TCP connection that failed and not use it again?
I don't believe that it should. > I'm seeing sipXproxy send the same PDU 3 times down the same TCP/IP > connection, with about 100, 200, and 400 mS between each attempt. Then it > fails over and sends via UDP. It doesn't close the TCP/IP connection and > re-open, even after the failure it leaves it open and keeps trying to use > it for further calls. Those look like Timer E retransmits, which shouldn't happen on TCP. I think the right behavior is that when Timer F expires (64*T1, in our case 6.4 seconds), the transaction should return an error that's treated as a 408 timeout response. That would trigger a retry on UDP if the message allows, but in any case I'd expect such an error to also cause the failed TCP connection to be closed (on the theory that whatever is on the other end has failed). Good exposition - file an issue against sipXtackLib _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
