[OpenSIPS-Users] TCP connection closed after the call is established

[Bogdan-Andrei Iancu]

Hi Mickael,

No, you cannot force it - it is against the TCP philosophy :) .

Which entity closes the TCP conn - OpenSIPS or the SBC ?

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 06.05.2015 11:02, Mickael Marrache wrote:
>
> Forget the previous error, it is not related to the issue.
>
> The issue is that when OpenSIPS sends the BYE to the SBC, it opens a 
> new TCP connection to the SBC but uses a randomly chosen source port, 
> therefore we don't see the SIP traffic using ngrep since we are 
> filtering using port.
>
> Is there a way to force OpenSIPS to always use port 5060 as source 
> port when opening TCP connections?
>
> *From:*Mickael Marrache [mailto:mickaelmarrache at gmail.com]
> *Sent:* Wednesday, May 06, 2015 10:15 AM
> *To:* users at lists.opensips.org
> *Subject:* TCP connection closed after the call is established
>
> Hi,
>
> We systematically get the following error with a particular SBC when a 
> BYE is received:
>
> Apr 30 21:41:47 [11535]: ERROR:core:tcp_read: error reading: 
> Connection reset by peer
>
> Apr 30 21:41:47 [11535]: ERROR:core:tcp_read_req: failed to read
>
> The components present in the call flow are:
>
> UAC <-> SBC <-> OpenSIPS <-> UAS
>
> The call works fine until a BYE is sent by the UAS to OpenSIPS which 
> doesn't forward the BYE to the SBC. I know the TCP connection between 
> the SBC and OpenSIPS is closed after the call is established, and 
> before the BYE is received. However, I expect OpenSIPS to open a TCP 
> connection with the SBC so that the BYE can be forwarded.
>
> Any idea?
>
> Thanks,
>
> Mickael
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150507/b363fd40/attachment.htm>