[SR-Users] missing BYE when 2 redundant kamailio servers share the same database

Vitaliy Aleksandrov vitalik.voip at gmail.com
Fri Mar 20 15:09:17 CET 2015



> We use TLS for SIP. The Wireshark pcap would be encrypted. I’ll try to 
> get a pcap anyway. Wonder if there is a way to dump pcap from inside 
> kamailio.
Wireshark can decrypt SIP signalling sent over TLS connections if you 
provide server's private key to it.

>
> All the requests within dialog are routed through 2 kamailio 
> instances. We want to make sure each phone only sends requests through 
> its registrar.
>
> I have included pjsua logs in subsequent emails in this thread. Those 
> logs have SIP messages, but only provide client perspective.
>
> Thanks for the help,
>
> Ding
>
>
>> On Mar 20, 2015, at 3:00 AM, Daniel-Constantin Mierla 
>> <miconda at gmail.com <mailto:miconda at gmail.com>> wrote:
>>
>> Hello,
>>
>> On 19/03/15 02:54, Ding Ma wrote:
>>> [...]
>>>
>>> My first question is why k1 loose_route sends the BYE to itself 
>>> instead of the client. Is this a bug?
>>>
>>
>> can you get the pcap of such call? We have to see the routing headers 
>> to say what is next hop address.
>>
>> Are all the requests within dialog routed via same instance of kamailio?
>>
>>> My next question is whether the above location routing for BYE from 
>>> peer kamailio a good/safe approach.
>>>
>>> The SIP traces will be sent later to avoid exceeding email size limit.
>>>
>> Cheers,
>> Daniel
>> -- 
>> Daniel-Constantin Mierla
>> http://twitter.com/#!/miconda  -http://www.linkedin.com/in/miconda
>> Kamailio World Conference, May 27-29, 2015
>> Berlin, Germany -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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20150320/7c3d0769/attachment.html>


More information about the sr-users mailing list