I'm not sure if the call could stay active unless it is the call manager that fails. If you lost network connectivity or the T1 went down the call would fail. I know you need the following command for SRST to fallback to MGCP in an SRST situation:
ccm-manager fallback-mgcp That should be all you need to get the fallback to work. As far as debugs, I'm not exactly sure, but when you do "show ccm-manager" you can see the status of MGCP. With 2 Callmanager servers, it would go "down" on the first server and "registering" on the second one. Once it times out, there is a field (fallback something like that, going from memory so don't remember exactly) that should show enabled/on once it stops trying to register to a server. you can make sure fallback-mgcp is enabled while the MGCP gateway is up as well. show ccm-manager would say enable/off in this case Hope this helps. Adam Compton On Fri, Mar 25, 2011 at 7:30 PM, Justin Brady <[email protected]> wrote: > What configs are necessary to ensure call preservation when losing the > primary call processor using MGCP? Also, what debugs would I use to see > this activity happen on the router and what parts of the debug would be > useful for explaining it? > > > > Justin > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
