I got a MGCP gateway w/ SRST and a T1 PRI trunk for PSTN calls. When I lost the WAN, SRST worked but I faced 2 issues:
1. Active calls didn't survive, and
2. I couldn't make outbound calls
I think I have some workarounds for the 2nd issue. However, the 1st issue is what I really wanted to get to the bottom of it. I know if I lose all callmanagers, PRI will get backhauled to the SRST router, then D-channel gets reset and my call will be dropped. Is there a way to fix this problem? I want to keep MGCP if possible.
Re: Call preservation with MGCP fallback possible?
MGCP does not support call pres with ISDN PRI or
It will work for T1 CAS and POTS
H323 call pres is the way to go. I would recommend to all only use H323 or SIP trunking. You can control you call routing much cleaner. I know it is more configuration on the front end of deployment but so many applications coming out rely on you GW to be SIP or H323. Especially if you are planing contact center at any time in you solution.
You answered your own question in your post the D Channel drops. There is no way to get around that with out going to a diffrent protocol. even with MGCP fall back.
Why are you stuck on MGCP when we all know that protocol is going away. Sorry Cisco I know you do not agree with me but I saw the writing on the wall in The 2000 's when Megaco changed to MGCP and still had to many caveauts.
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...