Our Provider for the SIP trunks want us to do the following:
If the CUBE that terminates the trunk from the provider can’t reach a CUCM anymore, it should answer to the option ping of the provider with a “503” or similar – so the provider can route to another CUBE before sending a INVITE Message…
I tried with the “voice-class sip options-keepalive” to “busy-out” the dial peer facing to the CUCM, but even if there is no valid dialpeer anymore, it still resonse to the ping...
I am not sure how will achieve that. CUBE is not designed to use options ping like that. If CUBE can't reach the cucm server, using options ping it takes down the dial peer to that cucm and sends the call to another cucm, if one is available. This is independent of what is happening between cube and itsp. If the link to the itsp is not down, cube won't send 503 to ITSP...that will be wrong...
Please rate all useful posts
"The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
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...