Skip to main content

Connect not detecting Disconnect

Posted by NickJ on Mon, 06/05/2017

I've had a few instances reported where after a SIP -> SIP Call between users on Thirdlane via physical handsets, Connect still shows those people as on a call.

Screenshot shows call as having been up for 27 minutes,
https://i.imgur.com/EF9sxiU.png

In reality, call lasted 46 seconds and both calls followed the standard BYE -> OK procedure (meaning the call was terminated cleanly).

https://i.imgur.com/o9ahHH4.png

Is this a known bug? Is there anything we can do to prevent this from happening?