[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" <hamid2kviii at 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 +0000
> From: nabeelshikder at gmail.com
> To: bogdan at opensips.org; users at lists.opensips.org
> Subject: Re: [OpenSIPS-Users] Linphone and OpenSIPS over TCP
>
> 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>
> 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 <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>
> 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 listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> _______________________________________________ Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> _______________________________________________
> 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/20160202/4e30080b/attachment.htm>