Hello,
I have a relatively freshly built Incredible PBX 13-13 VM (it's maybe a couple months old) running CentOS 7. I migrated over from an older version of Incredible PBX that was based on Asterisk 11. There are roughly 600 SIP endpoints.
We have been running Incredible PBX 13-13 in the wild now for a little over a week. Last week things seemed to work swimmingly. However, starting yesterday, I have been encountering an issue where it will simply stop functioning. This happened twice yesterday (mid morning and mid afternoon), and once so far today (mid morning). Asterisk is still running, but calls do not flow. The only way I've been able to recover this (which is usually in a panic) has been by a reboot. I've been watching the log, and when this happens I see variations of the following (this is from the most recent occurrence):
**See the attached file as it's too long to post here.**
When I do a 'pjsip show channelstats' I get something like the following (again from the last event):
I've noticed a sprinkling of the stasis-core-control queue errors throughout my monitoring, so I modified /etc/asterisk/stasis.conf so that initially there are 4 threads with an idle timeout of 10 seconds and no maximum size. This seemed to clear up the sporadic stasis-core-control queue threshold alerts, but was obviously not the resolution to my problem.
I'm not sure what other information would be helpful, so please let me know what you need and I will provide it. I'm under a bit of pressure to get this fixed...we are even considering falling back to our old Incredible PBX instance...something I'd really hate to do.
Any help anyone can provide would be greatly appreciated!!
I have a relatively freshly built Incredible PBX 13-13 VM (it's maybe a couple months old) running CentOS 7. I migrated over from an older version of Incredible PBX that was based on Asterisk 11. There are roughly 600 SIP endpoints.
We have been running Incredible PBX 13-13 in the wild now for a little over a week. Last week things seemed to work swimmingly. However, starting yesterday, I have been encountering an issue where it will simply stop functioning. This happened twice yesterday (mid morning and mid afternoon), and once so far today (mid morning). Asterisk is still running, but calls do not flow. The only way I've been able to recover this (which is usually in a panic) has been by a reboot. I've been watching the log, and when this happens I see variations of the following (this is from the most recent occurrence):
**See the attached file as it's too long to post here.**
When I do a 'pjsip show channelstats' I get something like the following (again from the last event):
Code:
BridgeId ChannelId ........ UpTime.. Codec. Count Lost Pct Jitter Count Lost Pct Jitter RTT....
===========================================================================================================
Vodex-000019b9 00:27:00 ulaw 49602 1 0 0.000 49583 0 0 0.002 0.000
PJSIP/Vodex-00001a80 not valid
Objects found: 9I've noticed a sprinkling of the stasis-core-control queue errors throughout my monitoring, so I modified /etc/asterisk/stasis.conf so that initially there are 4 threads with an idle timeout of 10 seconds and no maximum size. This seemed to clear up the sporadic stasis-core-control queue threshold alerts, but was obviously not the resolution to my problem.
I'm not sure what other information would be helpful, so please let me know what you need and I will provide it. I'm under a bit of pressure to get this fixed...we are even considering falling back to our old Incredible PBX instance...something I'd really hate to do.
Any help anyone can provide would be greatly appreciated!!
Phone System 