[SR-Users] SIP client - Linphone

Pavithra Mohanraja pavimohan3004 at gmail.com
Mon Oct 5 17:10:06 CEST 2020


Hi Aymeric,
Thanks for your reply. Yes, as you said I get the below warning when I
start Linphone. But the port is actually not used by any other application.
And one more thing is,  I see this error only in case of enabling TCP
transport and not in UDP. So does that mean, linphone works only with UDP
transport?
*Warning: Could not start tcp transport on port 4060, maybe this port is
already used.*

On Mon, Oct 5, 2020 at 8:08 PM Aymeric Moizard <amoizard at gmail.com> wrote:

> Hi,
>
> I'm answering as the author of libosip & libeXosip ;)
>
> Linphone, in your case is based on eXosip.
> Linphone removed eXosip2 years ago and thus, you use
> a very old linphone and very old eXosip2 version..
>
>
> Anyway, whatever versions of eXosip2, it needs to be used that way:
>
> ctx = eXosip_malloc
> <http://www.antisip.com/doc/exosip2/group__eXosip2__conf.html#ga8ebd76492c77690fee6f3781abcfd692>
> ();
> if (ctx==NULL)
> return -1;
> i=eXosip_init
> <http://www.antisip.com/doc/exosip2/group__eXosip2__conf.html#gaf0d9eb7def600c00166c06185b7f6fb3>
> (ctx);
> if (i!=0)
> return -1;
>
> i = eXosip_listen_addr
> <http://www.antisip.com/doc/exosip2/group__eXosip2__conf.html#ga07d7c2b336f7145fe55a8d481fccc44a>
> (ctx, IPPROTO_UDP, NULL, port, AF_INET, 0);
> if (i!=0)
> {
> eXosip_quit
> <http://www.antisip.com/doc/exosip2/group__eXosip2__conf.html#gacfd12dbf24afb5182dd9b7269ea41cb0>
> (ctx);
> fprintf (stderr, "could not initialize transport layer\n");
> return -1;
> }
>
> If eXosip_listen_addr
> <http://www.antisip.com/doc/exosip2/group__eXosip2__conf.html#ga07d7c2b336f7145fe55a8d481fccc44a> is
> failing nothing can be done with eXosip2, and " create transport layer
> first" logs
> will happen for some API which can't be used in that state.
>
> http://www.antisip.com/doc/exosip2/group__howto__initialize.html
>
> If the socket can't be created, the above API will fail. So a usual
> scenario is to have the port already used.
>
> A simple way is to choose another port when this is happening and I guess
> this old version of linphone wasn't
> doing that:
>
> i = eXosip_listen_addr
> <http://www.antisip.com/doc/exosip2/group__eXosip2__conf.html#ga07d7c2b336f7145fe55a8d481fccc44a>
> (ctx, IPPROTO_UDP, NULL, port, AF_INET, 0);
> if (i!=0)
> i = eXosip_listen_addr
> <http://www.antisip.com/doc/exosip2/group__eXosip2__conf.html#ga07d7c2b336f7145fe55a8d481fccc44a>
> (ctx, IPPROTO_UDP, NULL, 0, AF_INET, 0);
> if (i!=0)
> {
> eXosip_quit
> <http://www.antisip.com/doc/exosip2/group__eXosip2__conf.html#gacfd12dbf24afb5182dd9b7269ea41cb0>
> (ctx);
> fprintf (stderr, "could not initialize transport layer\n");
> return -1;
> }
>
> Regards
> Aymeric
>
>
> Le lun. 5 oct. 2020 à 12:28, David Villasmil <
> david.villasmil.work at gmail.com> a écrit :
>
>> Not an expert here. But many moons ago, I was playing with pjsip and got
>> the same. You must create the socket first, make sure the ip assigned is
>> correct.
>>
>> On Mon, 5 Oct 2020 at 06:47, Pavithra Mohanraja <pavimohan3004 at gmail.com>
>> wrote:
>>
>>> Hi Jan,
>>> Sorry for the delayed response. I guess the issue is because of UDP
>>> transport, which my kamailio is not accepting. Because  the same scenario
>>> is reproduced when I change my pjsip configurations to udp instead of tcp.
>>> But linphone gives me the following error if I tried to connect using tcp.
>>>
>>>
>>> *ortp-error-wrong state: create transport layer firstortp-error-wrong
>>> state: create transport layer firstortp-error-eXosip: missing via header*
>>> Am I missing something really important? Please let me know. Thanks in
>>> advance.
>>>
>>> On Wed, Sep 30, 2020 at 5:33 PM Jan Rozhon <jan.rozhon at gmail.com> wrote:
>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Hmm, nothing obviously wrong. Is there anything in Kamailio's
>>>>
>>>> logs? Are you sure REGISTER reaches kamailio? Can you run tcpdump
>>>>
>>>> or even better sngrep on kamailio server?
>>>>
>>>>
>>>> Regards, Jan
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 30. 09. 20 13:28, Pavithra Mohanraja
>>>>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Hi Jan,
>>>>
>>>>
>>>> I have also tried as u suggested with reg_proxy only with
>>>>
>>>> sip server name, could not obtain any positive changes. I have
>>>>
>>>> also attached the debug logs, please have a look and suggest
>>>>
>>>> for any changes. Thanks in advance.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Sep 30, 2020 at 4:42
>>>>
>>>> PM Jan Rozhon <jan.rozhon at gmail.com> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>
>>>>> Sorry, I am not that good in linphone configuration file
>>>>>
>>>>> so I may be wrong, but it seems to me that reg_proxy
>>>>>
>>>>> should only contain uri of the server, not the user part.
>>>>>
>>>>> Moreover, I have definitely more options there but not
>>>>>
>>>>> using it as an IMS.
>>>>>
>>>>>
>>>>> Mine is a bit more wordy:
>>>>>
>>>>>
>>>>> [proxy_3]
>>>>>
>>>>>
>>>>> reg_proxy=<sip:sip.server.here;transport=udp>
>>>>>
>>>>>
>>>>> reg_identity=sip:420123456789 at sip.server.here
>>>>>
>>>>>
>>>>> realm=sip.linphone.org
>>>>>
>>>>>
>>>>> contact_parameters=message-expires=604800
>>>>>
>>>>>
>>>>> quality_reporting_collector=
>>>>> sip:voip-metrics at sip.linphone.org;transport=tls
>>>>>
>>>>>
>>>>> quality_reporting_enabled=1
>>>>>
>>>>>
>>>>> quality_reporting_interval=180
>>>>>
>>>>>
>>>>> reg_expires=600
>>>>>
>>>>>
>>>>> reg_sendregister=1
>>>>>
>>>>>
>>>>> publish=1
>>>>>
>>>>>
>>>>> avpf=-1
>>>>>
>>>>>
>>>>> avpf_rr_interval=1
>>>>>
>>>>>
>>>>> dial_escape_plus=0
>>>>>
>>>>>
>>>>> privacy=32768
>>>>>
>>>>>
>>>>> push_notification_allowed=0
>>>>>
>>>>>
>>>>> idkey=proxy_config_voVF8eoXq46cJLs
>>>>>
>>>>>
>>>>> publish_expires=600
>>>>>
>>>>>
>>>>> nat_policy_ref=bUwFfNPHt40-miQ
>>>>>
>>>>>
>>>>> Could you send the REGISTER message not being accepted?
>>>>>
>>>>>
>>>>> Regards, Jan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 30. 09. 20 12:54, Pavithra Mohanraja wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Hi Jan,
>>>>>
>>>>>
>>>>> I'm trying to connect linphone to my kamailio ims.
>>>>>
>>>>> Only register request is sent from Linphone and no
>>>>>
>>>>> acknowledgement  is received. I'm attaching you my
>>>>>
>>>>> linphonerc file. Please advise if any correction is
>>>>>
>>>>> required in the configuration.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 30, 2020
>>>>>
>>>>> at 3:50 PM Jan Rozhon <jan.rozhon at gmail.com>
>>>>>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hey, I have no problems with linphone (desktop
>>>>>>
>>>>>> and mobile).
>>>>>>
>>>>>>
>>>>>> Could you be more specific on what you set up
>>>>>>
>>>>>> and/or what the communication looks like when
>>>>>>
>>>>>> using linphone?
>>>>>>
>>>>>>
>>>>>> Regards, Jan
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Dne 30.09.2020 v 11:55 Pavithra Mohanraja
>>>>>>
>>>>>> napsal(a):
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>>
>>>>>> I am a newbie to sipclient Linphone. I know
>>>>>>
>>>>>> this issue is not related with kamailio.Yet If
>>>>>>
>>>>>> anybody have tried it before , kindly provide
>>>>>>
>>>>>> me with some links or procedures to be
>>>>>>
>>>>>> followed for call registration and
>>>>>>
>>>>>> connectivity with kamailio since in my case,
>>>>>>
>>>>>> request is going but response is not coming
>>>>>>
>>>>>> back resulting in timeout issue.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> This happens only in linphone.If i do the
>>>>>>
>>>>>> samething in PJSIP/zoiper, call
>>>>>>
>>>>>> registration and call establishment happens
>>>>>>
>>>>>> perfectly fine.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Kindly help.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>>
>>>>>> Pavithra
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>>
>>>>>> Kamailio (SER) - Users Mailing List
>>>>>>
>>>>>> sr-users at lists.kamailio.org
>>>>>>
>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>>
>>>>>>
>>>>>> Kamailio (SER) - Users Mailing List
>>>>>>
>>>>>>
>>>>>> sr-users at lists.kamailio.org
>>>>>>
>>>>>>
>>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>>
>>>>> Kamailio (SER) - Users Mailing List
>>>>>
>>>>> sr-users at lists.kamailio.org
>>>>>
>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>>
>>>>>
>>>>> Kamailio (SER) - Users Mailing List
>>>>>
>>>>>
>>>>> sr-users at lists.kamailio.org
>>>>>
>>>>>
>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>>
>>>> Kamailio (SER) - Users Mailing List
>>>>
>>>> sr-users at lists.kamailio.org
>>>>
>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>>
>>>>
>>>> Kamailio (SER) - Users Mailing List
>>>>
>>>>
>>>> sr-users at lists.kamailio.org
>>>>
>>>>
>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>>
>>> Kamailio (SER) - Users Mailing List
>>>
>>> sr-users at lists.kamailio.org
>>>
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>> --
>> Regards,
>>
>> David Villasmil
>> email: david.villasmil.work at gmail.com
>> phone: +34669448337
>> _______________________________________________
>> Kamailio (SER) - Users Mailing List
>> sr-users at lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>
>
> --
> Antisip - http://www.antisip.com
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20201005/3d962a1b/attachment.htm>


More information about the sr-users mailing list