Thirdlane.com logo

SIP peer list disappearing???

Posted by devand_cloud on Tue, 09/10/2013
Forums
Thirdlane platform General Questions

I manage a HPBX running ThirdLane PBX Manager 6.1.1.12 on Asterisk 1.8.20.1, and we have started to experience a strange issue.

Periodically, we will have our SIP peer list disappear. What I mean by that is that inside of the CLI, when you issue "sip show peers", it shows only the column headers; no peers. We also lose registration on all of our customers' handsets. Asterisk itself is not deadlocked when this happens, and any ongoing calls are not affected when the event is triggered. I am also still able to issue commands to asterisk (obviously, if i know the SIP peer list is empty, but thought worth mentioning). The only command that asterisk doesn't seem to want to respond to is "restart now". I have to execute "/etc/init.d/asterisk stop" from shell and run safe_asterisk to start it back up again.

I have been unsuccessful in finding anyone on any forums who have encountered this same issue. Hoping you guys might be able to shed some light on why this might be happening and how I could go about resolving it.

Thanks!

Submitted by devand_cloud on Thu, 09/12/2013 Permalink

How could I go about determining if / why this is happening (and resolve it)?

Submitted by eeman on Wed, 09/18/2013 Permalink

if you cant place or receive sip calls, even from static hosts defined by ip addresses (such as trunk providers) and typing core restart now does nothing, its because your tasks are hung, aka deadlock.

Submitted by devand_cloud on Tue, 09/24/2013 Permalink

Alright, so what would be the best way for us to go about determining why this is deadlocking?

I'm really grasping at straws here. I've tried going to the Digium IRC channel, but that hasn't been much help either to be honest.

Any assistance / insight you could provide would be very (very) much appreciated.

Thanks.

Submitted by thirdlane on Tue, 09/24/2013 Permalink

This looks like the problem with sip channel that was fixed in the later versions of 1.8

Updating is probably a good idea.

Submitted by devand_cloud on Tue, 09/24/2013 Permalink

We are running 1.8.20.1, just to confirm, was it fixed in a revision even more recent than that?

And if so, what revision would you suggest we update to?

Submitted by eeman on Wed, 09/25/2013 Permalink

deadlocks are prevalent in many many many versions of asterisk... I would start at around 1.8.16 and work your way upward slowly until the problem does not recur. Most likely the deadlock you are experiencing recently came about as the result of fixing some other bug report.