Use of "call fallback act" to control participating dialpeers
I have a VGW (CUBE) that uses SIP/H323 dial-peers for SIP PSTN calls to/from CallManager (H323). I also am using H323 dialpeers pointing towards backup POTS ports in case the SIP/MPLS connect goes down, and SRST kicks in.
So someone clued me into the "call fallback act" global command with the "monitor probe imcp-ping" dialpeer command. so with the dialpeer's probe responses are received, the dialpeer is active (SIP dialpeers use this and probe the carrier SIP switch). When I show dialpeer, it shows probe received and dialpeer active; however, calls are not processed. If I take the "call fallback active" command off, calls work via SIP dialpeers. One thing I noticed during a debug ccapi while fallback was active was intermittent messages indicating 100% loss (of probe):
Feb 24 02:53:06.581: //-1/B1E7F783A648/CCAPI/g113_calculate_impairment:
Re: Use of "call fallback act" to control participating dialpeer
I first tried to enter it under the dial-peer (that had the monitor probe configured) for when the WAN was up, and it did not appear as a command option. So I ended up putting it at the "global" setting. I did NOT try under voice service voip. Perhaps I'll try those two (again) tonight.
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...