Best way to implement SIP Options Pings on a SIP Trunk
I wanted to see if anyone had suggestions on the best way to configure SIP Options Pings.
Typically I would configure them per dial-peer. However, I really want to do it per destination IP address. I do not want a SIP Options ping for every single dial-peer being sent out every X seconds.
In my case I have 4 SIP trunks in the same CUBE. Each pointing to a different destination IP. There are 6 dial-peers per SIP trunk. I really do not want 24 option pings going out every X seconds. I guess I've never actually did a debug to see how many pings are going out at a time but I am assuming it sends one for each dial-peer or does it?
If I am correct in my assumption, is there way to only send one ping per destination IP and if that single IP goes unresponsive then all 6 dial-peers go down?
Allow multiple sip-server entries under the sip-ua. Then allow the setting of the options ping per sip-server. Then if the option ping fails all dial-peers with that sip-server destination would then busy out.
Seems simple enough to me and makes it much more efficient.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...