Prerequisites for MGCP-Controlled Backhaul of BRI Signaling Cisco Unified CallManager
*Cisco Unified CallManager 4.1(1) or a later release
Cisco Voice Gateway
*20-MB flash memory
*64-MB DRAM
*One of the supported combinations of BRI voice interface card (VIC) and network module:
*VIC-2BRI-NT/TE or VIC-2BRI-S/T in NM-1V or NM-2V with Cisco IOS Release 12.3(11)T or a later release
*VIC2-2BRI-NT/TE in NM-HD-1V, NM-HD-2V, NM-HD-2VE, or NM-HDV2 with Cisco IOS Release 12.4(2)T or a later release
*EM-4BRI-NT/TE in EVM-HD-8FXS/DID with Cisco IOS Release 12.4(2)T or a later release
*MGCP enabled globally in a VoIP network
*MGCP control of dial peers and voice ports
*MGCP single-point configuration enabled
--------------------------------------------------------------------------------
Note For MGCP configuration instructions, see "Configuring MGCP Gateway Support for Cisco Unified CallManager" on page 23.
--------------------------------------------------------------------------------
Restrictions for MGCP-Controlled Backhaul of BRI Signaling
*BRI backhaul uses the enhanced interface numbering support available in Cisco IOS Release 12.3(11)T and later. Previous releases supported only the slot/subslot/port format with the subslot forced to 0 on the Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series. Cisco IOS Release 12.3(11)T and later releases support both the slot/port and slot/subslot/port interface numbering formats for BRI backhaul.
*Only the ETSI BRI Basic-NET3 switch type is supported.
*BRI calls are cleared during MGCP gateway fallback and rehome because ISDN BRI L2 must be reinitiated and brought up again by the new L3 task.
*Do not add the application mgcpapp command to voice dial peers that support BRI backhaul.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123cgcr/vvfax_c/callc_c/ccm_c/int_bri.htm#wp1057714
