I'm sure there are better ways, but we use dial-peer status as an indication of a problem with a SIP trunk, at the CUBE level. As long as you have specific IP addresses configured in them as the session target, and have your monitoring tools look for a change in the status from "Active" to "Busy-out." However, if you're going to use session server groups (multiple IP's referenced in single dial-peer), then this method will not work, as the CUBE does not provide the status of the dial-peer when not using specific IP's. You will of course need to have the SIP options Ping statement entered on your carrier facing dial-peers. Make sure your service provider supports SIP options ping. In some regions, some carriers do not. So far this method appears to be sufficient. We also monitor the physical interface of the switches and routers which terminate the circuits. But if you do not have that option, the dial-peer status method may work.
-J From: cisco-voip <cisco-voip-boun...@puck.nether.net> On Behalf Of Riley, Sean Sent: Monday, May 24, 2021 3:25 PM To: cisco-voip@puck.nether.net Subject: [External] [cisco-voip] CUBE Monitoring SIP Provider We are transitioning from traditional PSTN PRI's to SIP using CUBE. With the PRI's I could monitor the logs on the router for when the PRI went down, so it would trigger an alert to splunk which we could alert off of. I am having a hard time finding something similar in CUBE for when the SIP provider is down or not allowing calls to progress. Any guidance on what others are doing to monitor their SIP provider service via CUBE would be much appreciated. Thanks.
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
