Hey Richard, I am exploring all options which is why I asked the question. All cases point to this being a bug in the SBC. So I do appreciate your response and the info that you provided. We are working with the SBC vendor to hopefully get this corrected.
Thanks, Trey -----Original Message-----From: Richard Whitehouse (projectclearwater.org) <[email protected]> To: [email protected] <[email protected]>, "Ormsbee, Trey" <[email protected]> Subject: RE: [Project Clearwater] Issue with TCP connections being closed Date: Fri, 18 Nov 2016 14:09:39 -0500 Trey, By default, we’ll time out any outbound connection after 33 seconds, and any inbound connection after 300 seconds. These timers are configured as part of the PJSIP SIP stack, and are only modifiable by changing the code, rather than as a runtime configuration option. https://github.com/Metaswitch/pjsip-upstream/blob/8588ad804ddb759b1f8b5225121dd6b485336562/pjsip/include/pjsip/sip_config.h#L526-L552 However, this shouldn’t present a problem, as the SBC should recreate the TCP connection to the Clearwater Sprout nodes, using the top Route header, which should connect to Sprout’s port 5054. This is possible with the SBCs we’ve interop tested with. Is there some reason why this isn’t possible? Richard From: Clearwater [mailto:[email protected]] On Behalf Of Trey Ormsbee Sent: 15 November 2016 23:46 To: [email protected] Subject: Re: [Project Clearwater] Issue with TCP connections being closed I was able to get some logs and captures that I can share. In the attached capture, the issue I am seeing is at Frame 114/115. This is sprout closing its tcp connection to my sbc. Which appears to be disrupting my sbc's ability to continue the session. The question is why is sprout closing this connection? It happens roughly 33 seconds after the ACK so it appears there is some kind of timer, what is that timer and can it be adjusted? Thanks, Trey -----Original Message-----From: Trey Ormsbee <[email protected]> To: [email protected] Subject: Issue with TCP connections being closed Date: Mon, 14 Nov 2016 18:09:36 -0600 I have an environment where sprout is tearing down a tcp connection to an sbc. It is in one call scenario a call between two registered users, the called parties tcp socket to the sbc is closed with a fin,ack (from sprout) after about 30 or so seconds into the call, the call however stays up and going,. If the called party ends the call the sbc does not send a BYE because the connection was closed. The message in the log is just: 14-11-2016 23:30:43.897 UTC Debug connection_tracker.cpp:92: Connection 0x7f9c90152d68 has been destroyed. In that line of code it appears that PJSIP has closed the connection. Can anyone tell me what would cause sprout to close an active connection with a fin,ack? Note, I have tried with a year old version of clearwater, as well as the latest release and this oddity happens on both. Thanks, Trey
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
