We had a WAN outage at one of our branches today, and SRST was not triggered. I don't see any obvious config issues and SRST has been successfully tested at this branch by physically disconnecting the same WAN link that dropped today. There is only 1 WAN link at this branch so there was zero connectivity to the off-site ccm's during the outage.
I'm at a bit of a loss trying to figure out why SRST failed to work today. Any ideas on what to check?
It's an h.323 gateway, so it doesn't register per se and no conf bridges/transcoders/mtp's configured on the gateway. Just a pretty standard gateway config.
There's a single wan link terminating to this ISR. When I was implementing SRST, I tested it by physically disconnecting the wan link (as both ccm nodes are offsite). SRST was triggered as expected.
So our carrier had an outage and the circuit was down hard for about 6 hours. None of the phones went into cm fallback mode though so no in/outbound calls for the duration of the outage. With the wan link down, I couldn't reach the ISR to troubleshoot (no modem or terminal server at that site) but I imagine that a reload would have corrected it and forced the srst fallback.
I'd like to determine why SRST wasn't triggered to avoid this happening again. Both ccm nodes were completely unreachable during the outage so I have no clue what would have prevented srst fallback.
Do you have the SRST reference configured for the gateway inside CCM or do you have it set to "Use Default Gateway"?
I was told it is best to have the router set as the reference. I ran into a similar problem with one of my sites. It worked during testing when I had the gear in my office but once it was onsite, the failover didn't work as expected. Once I set the SRST reference and booted the phones, they worked fine.
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...