[SR-Users] TCP connection select problem
张顺通
shuntongzhang at gmail.com
Mon Mar 21 11:34:41 CET 2016
Have provided Callid, thanks.
register callid
2bbadd72-d733-434e-bd06-45d9ddb5289b
a7fa5d8f-1e46-4605-9a6e-08751bc75fee
call
626fec11-684b-1234-d0b9-ecf4bbde9ef8
2016-03-21 16:45 GMT+08:00 Daniel-Constantin Mierla <miconda at gmail.com>:
> Quickly looked at the file and I see several calls there. All of them are
> exposing the issue? Or can you give the call-id of the call that didn't
> work fine? I don't want to lose time looking at all the calls, knowing one
> that is wrong is enough...
>
> Cheers,
> Daniel
>
>
> On 21/03/16 03:50, 张顺通 wrote:
>
> I Send you pcap Separatly.
>
> Sorry, can't send pcap to mail list.
>
> Thanks
>
> 2016-03-15 16:08 GMT+08:00 Daniel-Constantin Mierla < <miconda at gmail.com>
> miconda at gmail.com>:
>
>> Can you attach a pcap with such situation, which includes the REGISTER,
>> replies and the call showing the issue?
>>
>> Cheers,
>> Daniel
>>
>>
>> On 15/03/16 03:36, 张顺通 wrote:
>>
>> sorry，I have not expressed clearly.
>>
>> kamailio will recive two REGISTER at a time.In first 200 OK to REGISTER,
>> Server will tell Linphone the Linphone Nat Ip and Port.
>> like this:
>> Via:SIP/2.0/TCP 30.9.2.1:50691
>> ;received=42.1.7.1;alias;branch=z9hG4bK.kmhC2L9Rf;rport=33746
>> and Linphone will know it's outside nat Ip and port, Linphone while use
>> this Ip and Port in second REGISTER.
>> like this:
>> REGSITER
>> Contact:<sip: 42.1.7.1:33746;transport=tcp>
>>
>> So kamailio server know Linphone's nated ip and port and save in
>> DB(contact field).
>>
>>
>> my question is KA_EDGE receive sip from KA_REGISTER already have right
>> nat ip and port like
>> INVITE 123456 at 42.1.7.1:33746;transport=tcp SIP/2.0
>> but KA_EDGE do not send this sip msg to 42.1.7.1:33746, it send to
>> another nat ip and port(other Linphone's ip and port behind same NAT layer)
>>
>>
>> 2016-03-14 21:42 GMT+08:00 Daniel-Constantin Mierla <miconda at gmail.com>:
>>
>>> Indeed, the ports are different, that's why adding received is important
>>> in this situation.
>>>
>>> While local ip and local port are in most of the cases also unique for
>>> devices behind a nat router, it is not 100% true, because there can be many
>>> layers of NATs, which can result in seeing same local ip/port for devices.
>>>
>>> Cheers,
>>> Daniel
>>>
>>>
>>> On 14/03/16 13:06, 张顺通 wrote:
>>>
>>> source IP is same, But port is different。
>>> like INVITE sip:Linphone_nat_Ip:Linphone_nat_port;tcp;
>>>
>>>
>>> 2016-03-14 18:26 GMT+08:00 Daniel-Constantin Mierla <
>>> <miconda at gmail.com>miconda at gmail.com>:
>>>
>>>> Adding received information to Path helps to identify properly the
>>>> connection to be used. Because both devices are behind the same NAT,
>>>> practically they show the same source IP when they send traffic to server.
>>>>
>>>> Cheers,
>>>> Daniel
>>>>
>>>>
>>>> On 14/03/16 04:05, 张顺通 wrote:
>>>>
>>>> KA_EDGE have two IP，external public IP and internal IP.
>>>> I add modparam("path", "use_received", 1) and replace add_path()
>>>> to add_path_received() in edge server.
>>>> add modparam("registrar", "path_use_received", 1) in KA_REGISTER
>>>> server.
>>>>
>>>> DB path info <sip:aD15fXXXXXXXXXXXXeEpfqRY=@10.10.10.11;lr;ob>
>>>> --> <sip:10.10.10.11;lr;received=sip:42.129.1.1:43640%3Btransport%3Dtcp
>>>> >
>>>>
>>>> This kind of situation very little，It is not easy to reappear.
>>>> Can you tell me why this situation happen? and Why this change can
>>>> solve the problem?
>>>>
>>>> Thanks for Your Time.
>>>>
>>>>
>>>>
>>>> 2016-03-09 22:37 GMT+08:00 Daniel Tryba < <d.tryba at pocos.nl>
>>>> d.tryba at pocos.nl>:
>>>>
>>>>> On Wed, Mar 09, 2016 at 10:05:11PM +0800, 张顺通 wrote:
>>>>> > Yes，Use Path in DB. like <sip:XXxXXXXXXXXXX/ogxZg=@10.10.232.29
>>>>> ;lr;ob>
>>>>> > KA_REGISTER wile the path info in DB.
>>>>>
>>>>> Should not be a problem if you use the use_received options in
>>>>> <http://kamailio.org/docs/modules/stable/modules/path.html#idp135216>
>>>>> http://kamailio.org/docs/modules/stable/modules/path.html#idp135216
>>>>> and
>>>>>
>>>>> <http://kamailio.org/docs/modules/stable/modules/registrar.html#registrar.p.path_use_received>
>>>>> http://kamailio.org/docs/modules/stable/modules/registrar.html#registrar.p.path_use_received
>>>>>
>>>>> (and actually add the source as received on the kamailio edge server).
>>>>>
>>>>> _______________________________________________
>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>>>> <sr-users at lists.sip-router.org>sr-users at lists.sip-router.org
>>>>> <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
>>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users at lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>>
>>>> --
>>>> Daniel-Constantin Mierlahttp://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>>>> Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com
>>>>
>>>>
>>>> _______________________________________________
>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>>> sr-users at lists.sip-router.org
>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>>
>>>
>>> --
>>> Daniel-Constantin Mierlahttp://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>>> Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com
>>>
>>>
>>
>> --
>> Daniel-Constantin Mierlahttp://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>> Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com
>>
>>
>
> --
> Daniel-Constantin Mierlahttp://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
> Kamailio World Conference, Berlin, May 18-20, 2016 - http://www.kamailioworld.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20160321/29a4934a/attachment.html>
More information about the sr-users
mailing list