FreePBX | Register | Issues | Wiki | Portal | Support

RMS failed to catch trunk down situation

rms
Tags: #<Tag:0x00007f74a68bfc78>

#1

I remember seeing somewhere in the collateral that RMS would monitor SIP trunks.

We just had an outage where Asterisk was in a loop trying to register our Digium SIP trunk and did not get any notification of an issue until we restarted FreePBX and got the a warning that Asterisk was unavailable.

I went and checked the link for “RMS checks and metrics” (https://wiki.freepbx.org/display/SL/RMS+Checks+and+Metrics?src=contextnavpagetreemode) and no longer see trunks listed there.

Has this been dropped?

Here are the errors we saw in the /var/log/asterisk/full log:
[2017-06-28 13:03:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #2)
[2017-06-28 13:03:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #3)
[2017-06-28 13:03:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #4)
[2017-06-28 13:04:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #5)
[2017-06-28 13:04:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #6)
[2017-06-28 13:04:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #7)
[2017-06-28 13:05:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #8)
[2017-06-28 13:05:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #9)
[2017-06-28 13:05:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #10)
[2017-06-28 13:06:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #11)
[2017-06-28 13:06:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #12)
[2017-06-28 13:06:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #13)
[2017-06-28 13:07:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #14)
[2017-06-28 13:07:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #15)
[2017-06-28 13:07:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #16)
[2017-06-28 13:08:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #17)
[2017-06-28 13:08:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #18)
[2017-06-28 13:08:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #19)
[2017-06-28 13:09:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #20)
[2017-06-28 13:09:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #21)
[2017-06-28 13:09:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #22)
[2017-06-28 13:10:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #23)
[2017-06-28 13:10:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #24)
[2017-06-28 13:10:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #25)
[2017-06-28 13:11:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #26)
[2017-06-28 13:11:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #27)
[2017-06-28 13:11:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #28)
[2017-06-28 13:12:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #29)
[2017-06-28 13:12:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #30)
[2017-06-28 13:12:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #31)
[2017-06-28 13:13:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #32)
[2017-06-28 13:13:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #33)
[2017-06-28 13:13:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #34)
[2017-06-28 13:14:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #35)
[2017-06-28 13:14:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #36)
[2017-06-28 13:14:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #37)
[2017-06-28 13:15:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #38)
[2017-06-28 13:15:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #39)
[2017-06-28 13:15:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #40)
[2017-06-28 13:16:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #41)
[2017-06-28 13:16:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #42)
[2017-06-28 13:16:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #43)
[2017-06-28 13:17:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #44)
[2017-06-28 13:17:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #45)
[2017-06-28 13:17:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #46)
[2017-06-28 13:18:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #47)
[2017-06-28 13:18:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #48)
[2017-06-28 13:18:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #49)
[2017-06-28 13:19:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #50)
[2017-06-28 13:19:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #51)
[2017-06-28 13:19:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #52)
[2017-06-28 13:20:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #53)
[2017-06-28 13:20:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #54)
[2017-06-28 13:20:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #55)
[2017-06-28 13:21:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #56)
[2017-06-28 13:21:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #57)
[2017-06-28 13:21:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #58)
[2017-06-28 13:22:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #59)
[2017-06-28 13:22:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #60)
[2017-06-28 13:22:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #61)
[2017-06-28 13:23:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #62)
[2017-06-28 13:23:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #63)
[2017-06-28 13:23:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #64)
[2017-06-28 13:24:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #65)
[2017-06-28 13:24:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #66)
[2017-06-28 13:24:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #67)
[2017-06-28 13:25:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #68)
[2017-06-28 13:25:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #69)
[2017-06-28 13:25:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #70)
[2017-06-28 13:26:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #71)
[2017-06-28 13:26:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #72)
[2017-06-28 13:26:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #73)
[2017-06-28 13:27:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #74)
[2017-06-28 13:27:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #75)
[2017-06-28 13:27:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #76)
[2017-06-28 13:28:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #77)
[2017-06-28 13:28:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #78)
[2017-06-28 13:28:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #79)
[2017-06-28 13:29:11] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #80)
[2017-06-28 13:29:31] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #81)
[2017-06-28 13:29:51] NOTICE[4150] chan_sip.c: – Registration for ‘56f31a357f6440c68b5c6e1fd240893b@sip.digiumcloud.net’ timed out, trying again (Attempt #82)

Any ideas/response appreciated.

  • Richard

#2

Ugh! I’m not going to say that a lot of the alerts RMS issues are not important (connected users trending down/up, etc) but something like monitoring the registration status of a SIP trunk (or any other trunk) seems like it would be absolutely critical. With zero response after six days RMS is not sounding so good anymore. That’s a shame, there’s really a need for this type of product.

  • Richard

(Tony Lewis) #3

Richard

RMS was a product we created in our lab for our NOC team and decided to smim.it down to a product idea and see if it has legs. We are still deciding the future of RMS and what we will do with it as a product. No decision has been made yet as it sits in our Lab group for a little longer and see what the feedback and take up rate is for it as a free product.


#4

Tony,
Thank you for the response. The RMS site (https://wiki.freepbx.org/display/SL/RMS) indicates this is a beta product, with a one month free trial available. That seemed to be saying (maybe I read too much into this) that it would be production soon.

We use a normal IT remote monitoring system already - in our case the Solar Winds MSP RMS, but I think my comments would apply to similar RMS products. They do not do some of the unique monitoring that a phone system needs.

Posting to the forums and watching other posts, some of the requests for more flexibility to configure “what checks are performed” and “with what settings”, have been responded to with something like “this is supposed to be a turnkey product, no adjustments needed”. I don’t think that’s realistic - but understand the desire to keep things simple.

Thank you again - Richard