MGCP Fallback to H323

Posted: June 18, 2006 by cciestudy in Cisco General

application
global
service alternate Default

ccm-manager fallback-mgcp

sh ccm-manager
MGCP Domain Name:
Priority Status Host
============================================================
Primary Down 10.101.21.250
First Backup Down 10.102.21.251
Second Backup None

Current active Call Manager: None
Backhaul/Redundant link port: 2428
Failover Interval: 30 seconds
Keepalive Interval: 15 seconds
Last keepalive sent: 19:46:24 UTC Mar 5 1993 (elapsed time: 00:43:26)
Last MGCP traffic time: 19:46:33 UTC Mar 5 1993 (elapsed time: 00:43:17)
Last failover time: 14:36:07 UTC Mar 5 1993 from (10.100.1.50)
Last switchback time: 14:36:13 UTC Mar 5 1993 from (10.100.1.51)
Switchback mode: Graceful
MGCP Fallback mode: Enabled/ON
Last MGCP Fallback start time: 19:46:52 UTC Mar 5 1993
Last MGCP Fallback end time: 19:45:24 UTC Mar 5 1993
MGCP Download Tones: Disabled

Backhaul/Redundant link is down
Configuration Error History:
FAX mode: cisco
To simulate MGCP fallback, do not disable MGCP using the no mgcp command. This will not kick in the H323 fallback mode. Either apply an access list or create a null route for Callmanager server.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s