[SR-Users] topos module - possible bug

Sergey Basov sergey.v.basov at gmail.com
Tue Apr 25 19:59:27 CEST 2017


Actualy latest fixes to 180/183/200,  ACK and memory leak was pushed to 5.0
and master branch.

So, please try with latest 5.0.1 nightly.

--
WBR
Sergey Basov

25 апр. 2017 г. 8:55 PM пользователь "Pete Kelly" <pkelly at gmail.com>
написал:

> Call is with sipp but first goes through another SBC to clean up the SIP
> (in case of problems with sipp via headers etc).
>
> The traces I've done are actually with 4.4.
>
> Will they be OK or would you prefer 5.0.1? The problem is exactly the same
> on both.
>
> On 25 April 2017 at 16:25, Sergey Basov <sergey.v.basov at gmail.com> wrote:
>
>> Hi.
>>
>> Can you send dump of the call with kamailio 5.0.1 nightly?
>>
>> And does you make call using sipp?
>>
>> --
>> WBR
>> Sergey Basov
>>
>> 25 апр. 2017 г. 5:57 PM пользователь "Pete Kelly" <pkelly at gmail.com>
>> написал:
>>
>>> Looks like from last night:
>>>
>>> 5.0.1+0~20170425013247.36+trusty
>>>
>>> On 25 April 2017 at 15:42, Daniel-Constantin Mierla <miconda at gmail.com>
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> to be sure, it is 5.0.1 build from last night or quite recent? There
>>>> were some fixes in the past days to topos module.
>>>>
>>>> Cheers,
>>>> Daniel
>>>>
>>>> On 25.04.17 15:59, Pete Kelly wrote:
>>>>
>>>> Hi Daniel
>>>>
>>>> Sorry for the delayed response to this, the ACK is for a 200OK yes and
>>>> the problem still persists in latest 4.4 and the 5.0.1 nightly build.
>>>>
>>>> I have all DB entries/kam logs/pcap files.
>>>>
>>>> If you check the attached pcap, 192.168.70.70 and 192.168.252.70 are
>>>> the same instance of Kamailio, it is being used to bridge the 2 networks.
>>>>
>>>> Frame 34 shows the 200OK with lots of Record-Route etc, and frame 35
>>>> shows topos in action.
>>>>
>>>> However the ACK that is relayed in Frame 38 seems to be missing all the
>>>> Route information that was supplied in the 200OK, this causes the ACK to be
>>>> relayed directly to the Contact, breaking the proxy chain.
>>>>
>>>> Pete
>>>>
>>>> On 22 February 2017 at 18:31, Daniel-Constantin Mierla <
>>>> miconda at gmail.com> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> is the ACK for 200ok? Or an ack for a negative response?
>>>>>
>>>>> Can you get a pcap for such situation with all messages related to the
>>>>> call?
>>>>>
>>>>> Cheers,
>>>>> Daniel
>>>>>
>>>>> On 22/02/2017 17:20, Pete Kelly wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> I am using the topos module when bridging 2 networks with Kamailio.
>>>>>
>>>>> The INVITE/200OK part of the transaction is working fine (i.e. the
>>>>> Contact on both sides matches correctly the corresponding network).
>>>>>
>>>>> However when the ACK is sent into Kamailio, instead of realising the
>>>>> next hop is myself and skipping it, Kamailio is sending the ACK directly to
>>>>> itself as a packet, causing the call setup to break.
>>>>>
>>>>> Does anyone have any advice for this situation?
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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 Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
>>>>> Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com
>>>>> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
>>>>>
>>>>> --
>>>> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
>>>>
>>>> Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com
>>>> Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.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/20170425/9e59ff44/attachment.html>


More information about the sr-users mailing list