[OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Bogdan-Andrei Iancu]

Hi Nabeel,

Your OpenSIPS tries to connect via TCP to the destination and to avoid 
blocking it is doing it async:


Feb  1 19:22:13 server1 opensips: Feb  1 19:22:13 [20587] 
DBG:core:print_ip: tcpconn_new: new tcp connection to: 188.29.165.162
Feb  1 19:22:13 server1 opensips: Feb  1 19:22:13 [20587] 
DBG:core:tcpconn_new: on port 58985, proto 2
Feb  1 19:22:13 server1 opensips: Feb  1 19:22:13 [20587] 
DBG:core:proto_tcp_send: Successfully started async connection

After that, in 5 seconds, the final timer hits (as timeout for no 
reply), while the TCP connect still haven;t finished (so there is no 
actual packet sent out).

Regards,

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

On 01.02.2016 21:35, Nabeel wrote:
> Hi Bogdan,
>
> Below is the requested log for TCP call attempt.  User 1111 is trying 
> to call user 2222 via OpenSIPS server 162.248.6.120 :
>
> http://pastebin.com/UQ9mEemd
>
> On 1 February 2016 at 09:41, Bogdan-Andrei Iancu <bogdan at opensips.org 
> <mailto:bogdan at opensips.org>> wrote:
>
>     Hi,
>
>     I strongly suggest to look into the opensips logs and see what
>     opensips try to do with the call. Based on your saying (that you
>     see a timeout), I suspect your OpenSIPS tries to deliver the call
>     over TCP to a destination which does not listen on TCP.
>     If you do not know hoe to interpret the logs, run opensips in
>     debug=4 mode, upload the logs corresponding the INVITE execution
>     and provide the link.
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>     OpenSIPS Founder and Developer
>     http://www.opensips-solutions.com
>
>     On 31.01.2016 16:28, Nabeel wrote:
>>     Without using alias=domain.com <http://domain.com>, TCP still
>>     does not work.  My initial request for someone to test this using
>>     Linphone remains. Please test and let me know if you can call
>>     using TCP with OpenSIPS listening on an IP address.
>>
>>     On 31 January 2016 at 09:28, Nabeel <nabeelshikder at gmail.com
>>     <mailto:nabeelshikder at gmail.com>> wrote:
>>
>>         On further testing, using the IP address instead of the
>>         domain name in the URI setting of Linphone works with TCP, so
>>         I think this might be to do with SRV/NAPTR records associated
>>         with the domain.
>>
>>         On 31 January 2016 at 08:29, Nabeel <nabeelshikder at gmail.com
>>         <mailto:nabeelshikder at gmail.com>> wrote:
>>
>>             Hello,
>>
>>             There seems to be a problem with calls over TCP using
>>             Linphone, and since Linphone is a popular open source
>>             application, I would like someone to please verify this
>>             problem. Calls work fine with Linphone over UDP, but
>>             after registering with TCP using the same credentials,
>>             calls do not connect at all and lead to a request
>>             timeout.  A request timeout does not say much about the
>>             cause, but in this case I suspect there is something
>>             wrong with TCP on the server side. I would like someone
>>             to please install Linphone on your phone and connect to
>>             your OpenSIPS server using UDP and TCP. Please report
>>             here if the calls work over both transports.
>>
>>
>>
>>
>>
>>     _______________________________________________
>>     Users mailing list
>>     Users at lists.opensips.org <mailto: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/20160202/cfe5aa5c/attachment-0001.htm>