Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Adrian Georgescu]

OpenSIPS does not need to interact in anyway with a TURN server. A TURN server 
is used by the SIP client that has built-in TURN functionality. While they may 
run side by side, the only interaction of a sip proxy and TURN server is 
sharing the same database with credentials in order to authenticate the 
end-users.

What MediaProxy does, it simulates a TURN server candidate by inserting it into 
an offer generated by a SIP client that has ICE support. But it is not real 
TURN in the sense that it does not implement the TURN protocol (which does a 
lot of other things, not just the relaying packets over UDP part), and the 
client is unaware of this TURN candidate insertion. Practically, MediaProxy 
only relays RTP packets over UDP and is fouling both end-points into believing 
that during the ICE negotiation there is a relay server that can be used when 
end-to-end RTP does not work. One cannot get RTP over TCP running with this 
hybrid model.

If you want TCP, you need a real TURN client with a real TURN server. 

Regards,
Adrian


> On 06 Feb 2016, at 01:07, Nabeel  wrote:
> 
> On 3 February 2016 at 23:42, sevpal > 
> wrote:
> 
> Opensips interacts with the TURN in server MediaProxy only.
> 
> 
> That's not completely true, because the TURN server works with OpenSIPS when 
> using UDP for calls. It just doesn't work - or only partially works - with 
> TCP/TLS.  I tested by changing configurations in the TURN server to use TCP 
> relays/listeners only, but it still only works with UDP. This leads me to 
> believe that it is a limitation in OpenSIPS that it only handles the TURN 
> server properly when calls are using UDP, not TCP/TLS.
> 
> Coturn is probably the most comprehensive TURN server available today. Is 
> there any chance that OpenSIPS will fully support this in the future?
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

Hi,

I understand that OpenSIPS supports Mediaproxy which only relays RTP
packets over UDP.  My concern now is that due to Mediaproxy only supporting
UDP, OpenSIPS might have this limitation built into it for all TURN
servers, including Coturn.

In Linphone settings, there is a 'Stun server' option, and although it does
not state 'TURN server' here, I found that in most clients which do support
a TURN server, they still tend to refer to this as a 'Stun server' in their
settings.
On 6 Feb 2016 8:56 am, "Adrian Georgescu"  wrote:

> OpenSIPS does not need to interact in anyway with a TURN server. A TURN
> server is used by the SIP client that has built-in TURN functionality.
> While they may run side by side, the only interaction of a sip proxy and
> TURN server is sharing the same database with credentials in order to
> authenticate the end-users.
>
> What MediaProxy does, it simulates a TURN server candidate by inserting it
> into an offer generated by a SIP client that has ICE support. But it is not
> real TURN in the sense that it does not implement the TURN protocol (which
> does a lot of other things, not just the relaying packets over UDP part),
> and the client is unaware of this TURN candidate insertion. Practically,
> MediaProxy only relays RTP packets over UDP and is fouling both end-points
> into believing that during the ICE negotiation there is a relay server that
> can be used when end-to-end RTP does not work. One cannot get RTP over TCP
> running with this hybrid model.
>
> If you want TCP, you need a real TURN client with a real TURN server.
>
> Regards,
> Adrian
>
>
> On 06 Feb 2016, at 01:07, Nabeel  wrote:
>
> On 3 February 2016 at 23:42, sevpal  wrote:
>
> Opensips interacts with the TURN in server MediaProxy only.
>>
>
>
> That's not completely true, because the TURN server works with OpenSIPS
> when using UDP for calls. It just doesn't work - or only partially works -
> with TCP/TLS.  I tested by changing configurations in the TURN server to
> use TCP relays/listeners only, but it still only works with UDP. This leads
> me to believe that it is a limitation in OpenSIPS that it only handles the
> TURN server properly when calls are using UDP, not TCP/TLS.
>
> Coturn is probably the most comprehensive TURN server available today. Is
> there any chance that OpenSIPS will fully support this in the future?
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

On 3 February 2016 at 23:42, sevpal  wrote:

Opensips interacts with the TURN in server MediaProxy only.
>


That's not completely true, because the TURN server works with OpenSIPS
when using UDP for calls. It just doesn't work - or only partially works -
with TCP/TLS.  I tested by changing configurations in the TURN server to
use TCP relays/listeners only, but it still only works with UDP. This leads
me to believe that it is a limitation in OpenSIPS that it only handles the
TURN server properly when calls are using UDP, not TCP/TLS.

Coturn is probably the most comprehensive TURN server available today. Is
there any chance that OpenSIPS will fully support this in the future?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

In the SDP of the call, I see UDP relays being used:

a=candidate:1 1 UDP 2130706431 10.180.107.181 7076 typ host a=candidate:1 2
UDP 2130706430 10.180.107.181 7077 typ host a=candidate:2 1 UDP 1694498815
92.40.248.63 51755 typ srflx raddr 10.180.107.181

For calls over TCP and TLS, should the relays be using TCP instead of UDP?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[sevpal]

Video and voice calls work fine with Linphone client over UDP, TCP, 3G/4G and 
wifi and when using a media proxy. Did not even try to install a TURN server to 
test your case, because Opensips does not have any modules to interact with a 
TURN server, you may be at a dead end with that. 

In the case of the SDP bodies being received by Opensips from the UA, these 
would need to be forwarded to the TURN server for modification and then 
returned to Opensips to be sent to the UA for the  media to be redirected.

Opensips interacts with the TURN in server MediaProxy only. 

From: Nabeel 
Sent: Tuesday, February 02, 2016 2:30 AM
To: OpenSIPS users mailling list ; hamid2kv...@hotmail.com 
Subject: Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

Hi Hamid, 

I am not using the location table, I am using memory only to store the 
contacts. 

If you use TCP within the same network, where a TURN server is not required 
(TURN server not set in Linphone settings), I found that the calls then work 
depending on what the network allows. Within the same Wi-Fi network, in my case 
audio calls work but not video calls. But using 3G/4G only, with or without a 
TURN server set in Linphone settings, calls do not work at all. This is why I 
think the behaviour of TURN server has something to do with this. To those 
people stating that TCP works with Linphone, please test over 3G/4G where a 
TURN server might be required. 



On 2 Feb 2016 7:07 am, "Hamid Hashmi" <hamid2kv...@hotmail.com> wrote:

  Nabeel I have been using Linphone 3.6.1 with opensips for a long time. And 
its working fine on both UDP and TCP. I have gone through your logs, there is 
log line DBG:tm:matching_3261: RFC3261 transaction matching failed  Please 
check contact of your "to number" in location table.   


  Hamid R. Hashmi 
  Software Engineer - VoIP
  Vopium A/S




--
  Date: Mon, 1 Feb 2016 19:35:53 +
  From: nabeelshik...@gmail.com
  To: bog...@opensips.org; users@lists.opensips.org
  Subject: Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP


  Hi Bogdan, 

  Below is the requested log for TCP call attempt.  User  is trying to call 
user  via OpenSIPS server 162.248.6.120 :

  http://pastebin.com/UQ9mEemd


  On 1 February 2016 at 09:41, Bogdan-Andrei Iancu <bog...@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.comOn 31.01.2016 16:28, Nabeel wrote:

  Without using alias=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 <nabeelshik...@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 <nabeelshik...@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@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




  ___ Users mailing list 
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

  ___
  Users mailing list
  Users@lists.opensips.org
  http://lists.opensips.org/cgi-bin/mailman/listinfo/users





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [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  is trying 
to call user  via OpenSIPS server 162.248.6.120 :


http://pastebin.com/UQ9mEemd

On 1 February 2016 at 09:41, Bogdan-Andrei Iancu > 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 , 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 > 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 > 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@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users





___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

Hi Bogdan,

Even if I remove the 5 second timeout by removing #modparam("tm",
"fr_inv_timeout", 30), the timeout occurs after about 20 seconds. What do
you suggest is the solution?
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 Developerhttp://www.opensips-solutions.com

On 01.02.2016 21:35, Nabeel wrote:

Hi Bogdan,

Below is the requested log for TCP call attempt.  User  is trying to
call user  via OpenSIPS server 162.248.6.120 :

http://pastebin.com/UQ9mEemd

On 1 February 2016 at 09:41, Bogdan-Andrei Iancu 
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 Developerhttp://www.opensips-solutions.com
>
> On 31.01.2016 16:28, Nabeel wrote:
>
> Without using alias=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  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  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 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Bogdan-Andrei Iancu]

The problem is not the 5 seconds timeout at sip level, is the fact that 
the end point you are trying to connect to via TCP does not accept the 
connection. You can check that via tcpdump.


Regards,

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

On 02.02.2016 11:17, Nabeel wrote:


Hi Bogdan,

Even if I remove the 5 second timeout by removing #modparam("tm", 
"fr_inv_timeout", 30), the timeout occurs after about 20 seconds. What 
do you suggest is the solution?


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  is trying 
to call user  via OpenSIPS server 162.248.6.120 :


http://pastebin.com/UQ9mEemd

On 1 February 2016 at 09:41, Bogdan-Andrei Iancu > 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 , 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 > 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 > 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@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users







___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

Hi,

Please see the tcpdump trace below.  Can this be caused by incorrect use of
the TURN server? I am convinced that the problem relates to use of the TURN
server, but not sure if the problem is caused by OpenSIPS or the TURN
server itself.

http://pastebin.com/HPZ7nRYS
The problem is not the 5 seconds timeout at sip level, is the fact that the
end point you are trying to connect to via TCP does not accept the
connection. You can check that via tcpdump.

Regards,

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

On 02.02.2016 11:17, Nabeel wrote:

Hi Bogdan,

Even if I remove the 5 second timeout by removing #modparam("tm",
"fr_inv_timeout", 30), the timeout occurs after about 20 seconds. What do
you suggest is the solution?
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 Developerhttp://www.opensips-solutions.com

On 01.02.2016 21:35, Nabeel wrote:

Hi Bogdan,

Below is the requested log for TCP call attempt.  User  is trying to
call user  via OpenSIPS server 162.248.6.120 :

http://pastebin.com/UQ9mEemd

On 1 February 2016 at 09:41, Bogdan-Andrei Iancu 
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 Developerhttp://www.opensips-solutions.com
>
> On 31.01.2016 16:28, Nabeel wrote:
>
> Without using alias=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  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  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 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

Hi Bogdan,

Below is the requested log for TCP call attempt.  User  is trying to
call user  via OpenSIPS server 162.248.6.120 :

http://pastebin.com/UQ9mEemd

On 1 February 2016 at 09:41, Bogdan-Andrei Iancu 
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 Developerhttp://www.opensips-solutions.com
>
> On 31.01.2016 16:28, Nabeel wrote:
>
> Without using alias=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  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 < 
>> nabeelshik...@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 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Bogdan-Andrei Iancu]

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 , 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 > 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 > 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@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

Hi Hamid,

I am not using the location table, I am using memory only to store the
contacts.

If you use TCP within the same network, where a TURN server is not required
(TURN server not set in Linphone settings), I found that the calls then
work depending on what the network allows. Within the same Wi-Fi network,
in my case audio calls work but not video calls. But using 3G/4G only, with
or without a TURN server set in Linphone settings, calls do not work at
all. This is why I think the behaviour of TURN server has something to do
with this. To those people stating that TCP works with Linphone, please
test over 3G/4G where a TURN server might be required.


On 2 Feb 2016 7:07 am, "Hamid Hashmi" <hamid2kv...@hotmail.com> wrote:

> Nabeel I have been using Linphone 3.6.1 with opensips for a long time. And
> its working fine on both UDP and TCP. I have gone through your logs, there
> is log line DBG:tm:matching_3261: RFC3261 transaction matching failed
> Please check contact of your "to number" in location table.
>
>
> *Hamid R. Hashmi*
> Software Engineer - VoIP
> Vopium A/S
>
>
> --
> Date: Mon, 1 Feb 2016 19:35:53 +
> From: nabeelshik...@gmail.com
> To: bog...@opensips.org; users@lists.opensips.org
> Subject: Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP
>
> Hi Bogdan,
>
> Below is the requested log for TCP call attempt.  User  is trying to
> call user  via OpenSIPS server 162.248.6.120 :
>
> http://pastebin.com/UQ9mEemd
>
> On 1 February 2016 at 09:41, Bogdan-Andrei Iancu <bog...@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 Developerhttp://www.opensips-solutions.com
>
> On 31.01.2016 16:28, Nabeel wrote:
>
> Without using alias=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 <nabeelshik...@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 < <nabeelshik...@gmail.com>
> nabeelshik...@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 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> ___ Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Hamid Hashmi]

Nabeel I have been using Linphone 3.6.1 with opensips for a long time. And its 
working fine on both UDP and TCP. I have gone through your logs, there is log 
line DBG:tm:matching_3261: RFC3261 transaction matching failed  Please check 
contact of your "to number" in location table.   

Hamid R. HashmiSoftware Engineer - VoIPVopium A/S

Date: Mon, 1 Feb 2016 19:35:53 +
From: nabeelshik...@gmail.com
To: bog...@opensips.org; users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

Hi Bogdan,
Below is the requested log for TCP call attempt.  User  is trying to call 
user  via OpenSIPS server 162.248.6.120 :
http://pastebin.com/UQ9mEemd

On 1 February 2016 at 09:41, Bogdan-Andrei Iancu <bog...@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, 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 <nabeelshik...@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 <nabeelshik...@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@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




  




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
  ___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

Hamid, to answer your question about contact, here are the contacts of
callee and caller from memory:


AOR:: 
> Contact:: 
> sip:@188.29.164.62:36612;app-id=622464153529;pn-type=google;pn-tok=APA91bF-OsPp0vEMG1m_RZLhIaLNY90KYav0So_8a8Lm0rm-fUecuikFF5Prmnb_m5t9E4Cfavzssp-jkrzw9Y-VZ1FjqUSVJaTUhnE5FtSiJhUqkpgSprE;transport=tcp
> Q=
> Expires:: 86392
> Callid:: k8R9KdUDVj
> Cseq:: 21
> User-agent:: LinphoneAndroid/2599 (belle-sip/1.4.2)
> Received:: sip:188.29.164.62:36612;transport=TCP
> State:: CS_NEW
> Flags:: 0
> Cflags:: NAT
> Socket:: tcp:162.248.6.120:5060
> Methods:: 4294967295
> SIP_instance::
> 



 AOR:: 
> Contact:: 
> sip:@92.40.248.63:58688;app-id=622464153529;pn-type=google;pn-tok=APA91bGt_p4GcPUNLZsI_4YyvV8DzDYisZfBr9tVu7WpbWI1KOJ3Y5EUa0S-h9Zp8uq76TL2zpLhm5ZOkoyJ3rUC63903lOq050xXRt4LMz-059gwfQWiNc;transport=tcp
> Q=
> Expires:: 86383
> Callid:: 1ts0tZS4vk
> Cseq:: 21
> User-agent:: LinphoneAndroid/2599 (belle-sip/1.4.2)
> Received:: sip:92.40.248.63:58688;transport=TCP
> State:: CS_NEW
> Flags:: 0
> Cflags:: NAT
> Socket:: tcp:162.248.6.120:5060
> Methods:: 4294967295
> SIP_instance::
> 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

sevpal,

Thanks for the suggestions. I didn't have the domain in the domain table of
the database. However, I have added this and the problem is not solved.
The calls otherwise work without it, so I'm not sure why the domain table
is necessary.

I'm still working on the theory that the TURN server behaves differently
with TCP, UDP and TLS.  It is very strange behaviour, but Linphone
definitely shows this discrepancy with TCP using the Coturn TURN server.

On 31 January 2016 at 17:11, sevpal <sev...@aol.com> wrote:

> It’s just a configuration issue you are having, start by:
>
> 1. In windows, do an “nslookup your.domain.net”
> if the returned IP’s are not what you expect, then correct this. You
> may also want to do a reverse lookup “nslookup xxx.xxx.xxx.xxx” to return
> its domain name.
>
> 2. Configure your Opensips to listen on these IP’s
>
> 3. Add “your.domain.net” in your domain table (these are the domains your
> sips is responsible for, IP’s can go in this table but not recommended if
> you are strictly using domain names in the clients for authentication)
>
> By the way, TCP works with Linphone very well.
>
>
> *From:* Nabeel <nabeelshik...@gmail.com>
> *Sent:* Sunday, January 31, 2016 9:28 AM
> *To:* OpenSIPS users mailling list <users@lists.opensips.org>
> *Subject:* Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP
>
> Without using alias=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 <nabeelshik...@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 <nabeelshik...@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@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

I now believe this may be a discrepancy in the way my TURN server (Coturn)
is used over different protocols, as follows:

Using UDP, all calls use Coturn correctly and can establish calls without
problems.

Using TLS, calls within 15 minutes of clients' registration use Coturn
correctly and the calls can connect, but after 15 minutes of registration,
Coturn cannot establish the calls.

Using TCP, Coturn cannot establish the calls at all.

Please let me know if these are known issues with OpenSIPS+TURN server, and
if anything can be done on the OpenSIPS side to fix this.  I have contacted
the Coturn forum regarding this.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[sevpal]

It’s just a configuration issue you are having, start by:

1. In windows, do an “nslookup your.domain.net”
if the returned IP’s are not what you expect, then correct this. You may 
also want to do a reverse lookup “nslookup xxx.xxx.xxx.xxx” to return its 
domain name.

2. Configure your Opensips to listen on these IP’s

3. Add “your.domain.net” in your domain table (these are the domains your sips 
is responsible for, IP’s can go in this table but not recommended if you are 
strictly using domain names in the clients for authentication)

By the way, TCP works with Linphone very well.


From: Nabeel 
Sent: Sunday, January 31, 2016 9:28 AM
To: OpenSIPS users mailling list 
Subject: Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

Without using alias=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 <nabeelshik...@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 <nabeelshik...@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@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

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@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP

[Nabeel]

Without using alias=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  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  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@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users