It’s not always 192 seconds nor is the threshold even the same for all the PBXs (some are 120 and some are 180 seconds). This happens occasionally where we get a bunch of these and then it stops on its own a while later. They come in pairs too as the keepalives are eventually received a second message is sent.
Is this a problem with RMS or is there something else going on? Also, where can I change the threshold?
i tried to submit a ticket but in order to do so i have to purchase more support credits. there must be a better way to alert the NOC or support to major events like this without purchasing support credits.
thanks for the update. me thinks that there is some work to be done on the rms code. we need some way to temporarily suspend rms when things like this happen.
As far as work in RMS that is why its a free product still. We are still working on our long term roadmap and plans for it so it remains free as we gather more feedback and input.
Bob - Sorry for the message floods. The NOC team is already working with development to identify the condition that causes the excess alerts and monitor for it. We are also going to look at alerting on the email queue so we can get in front of it faster.
We will also work with the RMS developers to get the root cause identified and resolved.
RMS uses the same credentials as you would use to login to portal.sangoma.com. If you don’t remember your credentials you should be able to click the forgot password on the portal to reset it.
@bksales and @adolfoc Yes we were aware of the issue. At this time everything should be back to normal, however, if that isn’t the case for your deployments, please open a support ticket at support.sangoma.com.