[Spce-user] Call does not stop after hang-up

Andrew Pogrebennyk apogrebennyk at sipwise.com
Thu Dec 20 09:10:42 EST 2018

did I understand you correctly that is a separate Sipwise CE box? 
If the message if not forwarded to the other leg usually this means a problem with some Record-Route headers in 200 OK.. but in that case even an ACK would be dropped before. 
You should check both kamailio-lb.log and kamailio-proxy.log and try to figure out if the message is dropped because of an error or something else.. many possible options here, but for sure we'd need to have the trace to be able to help you. 

----- Original Message -----

From: "Marcos Pytel" <marcos.pytel at cotesma.com.ar> 
To: spce-user at lists.sipwise.com 
Sent: Thursday, December 20, 2018 12:50:35 PM 
Subject: [Spce-user] Call does not stop after hang-up 


I’m using mr6.5.1 

I have this schema: is the device--- SIPWISE port5060--- SIPWISE port5062 + SIPWISE---- GW VoIP 

Device send to SipWise 5060 port, then Sipwise will route to Sipwise 5062 port, which might for the purpose to route to Sipwise, then this message will be finally lead to GW VoIP. 

when the device try to hangup, it sends BYE to the sipwise , but somehow Sipwise port 5062 sends back a 100 trying(???) and also I didn’t see a BYE come out from (Tot he GW) . Maybe there might be something wrong when the BYE message transferring from Port 5062 to sipwise? 

Thank you! 


Spce-user mailing list 
Spce-user at lists.sipwise.com 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20181220/2a302723/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 56769 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20181220/2a302723/attachment-0001.jpg>

More information about the Spce-user mailing list