[OpenSIPS-Users] OpenSIPS reopen TCP connectios and sends INVITE, but not BYE. How to change it?
razvan at opensips.org
Thu Oct 27 09:58:24 CEST 2016
Having OpenSIPS opening TCP connections towards client is a bit
dangerous, especially if the clients are behind NAT. That's because most
likely you will not be able to reach them, and opensips will get stuck
trying to connect (until it triggers a timeout). That's why the best way
to go is to try to keep the connection (ideally opened by the client at
REGISTER) as much as possible. This is usually done by pinging (as
discussed in a previous email). So my suggestion is to try to avoid
opening new TCP connections with clients, unless you really know they
will always be reachable.
The behavior you are describing (INVITE vs BYE handling), might be
related to the fact that you are setting the tcp_no_new_conn_bflag
flag for BYE messages, but not for INVITEs. Is this correct? If not, do
you see any errors in the script?
On 10/26/2016 10:59 PM, Rodrigo Pimenta Carvalho wrote:
> After some log debug I have observed the following behavior in the
> OpenSISP (2.2.1):
> When OpenSIPS has to send a SIP INVITE to a peer through a TCP
> connection that was closed before by some way, OpenSIPS open a new one
> and then sends the SIP message to the peer successfully.
> However, when OpenSIPS has to send a SIP BYE to a peer through a TCP
> connection that was closed before, OpenSIPS open a new one, but
> doesn't send the SIP BYE. In this case SIP BYE is discarded.
> How to change the behavior of OpenSIPS to make it to send the SIP BYE
> is such case?
> I'm looking for ways of fix or workaround of a TCP tear down
> connection that happens during dialogs.
> Any hint will be very helpful!
> RODRIGO PIMENTA CARVALHO
> Inatel Competence Center
> Ph: +55 35 3471 9200 RAMAL 979
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users