MGCP Gateway:

============
MGCP allows CUCM to take control of the Gateway voice ports.
Dial-plan completely administered from the CUCM.
An endpoint can be either the source or the destination for a media stream
Endpoint names have two componentsa local identifier, and a gateway identifier.
The entire name consists of the local identifier, followed by the @ symbol, and
then the gateway identifier. For example:
local_identifier@gateway_identifier.domain_name
The gateway identifier is its configured hostname, such as "BoiseRTR01." If the
gateway is configured with a domain name, it is appended to the end of the hostn
ame, such as "BoiseRTR01.company.com."
The format of a local identifier varies depending on the type of interface. The
local identifier for analog ports uses the following syntax:
--------------------------------------------------------------------------------
-------------------------------------------------
Endpoint type/Slot #/Subunit #/Port #
For example, an endpoint name for an FXO port might look something like this:
AALN/S0/SU0/1@VoiceGW
where
AALN (Analog Access Line Endpoint) means that it is either an FXS or FXO interfa
ce.
S0 is the slot number that contains the voice module.
SU0 (for Subunit 0) is the slot within the network module that holds the voice i
nterface card (VIC) or voice/WAN interface card (VWIC).
1 is the number of the voice port on the VIC or VWIC.
VoiceGW is the hostname of the gateway.
MGCP Interaction with call manager:
-----------------------------------
MGCP uses nine types of messages between the gateway and CallManager to control
the endpoints and connections.
The receiver must acknowledge each message. Messages between the CallManager and
the gateway are sent by default to port 2427.
Configuration of MGCP Gateway:
-------------------------------
VoiceGW(config)#mgcp
VoiceGW(config)#mgcp call-agent [ip-address|hostname] [port] service-type mgcp [
version 0.1 | 1.0 | rfc3435-1.0] -->specifies the primary call manager ip addres
s
VoiceGW(config)#ccm-manager mgcp --->enables the mgcp to support call manager
To download much of its MGCP configuration from CallManager
------------------------------------------------------------
VoiceGW(config)#ccm-manager config server {ip-address of call manager | dns-name
}
VoiceGW(config)#ccm-manager config
Next, you need to bind MGCP to the voice ports. You do this by configuring a dia
l peer for each voice port and binding MGCP to it using the application MGCPAPP
command
Note: the directory number is not specified in the port since its configured in
call manager
VoiceGW(config)#dial-peer voice 100 pots
VoiceGW(config-dial-peer)#application MGCPAPP
VoiceGW(config-dial-peer)#port 1/0/0
Configuring MGCP Fallback:
---------------------------
VoiceGW(config)#application
VoiceGW(config-app)#global
VoiceGW(config-app-global)#service alternate Default
When using MGCP fallback, you must also configure at least one dial peer with a
destination pattern so that it can route outbound calls when CallManager is not
available
VoiceGW(config)#dial-peer voice 200 pots
VoiceGW(config-dial-peer)#destination-pattern 9T
VoiceGW(config-dial-peer)#incoming called-number .
Configuration of PRI Backhaul:
------------------------------
Q.921 is handled by the gateway and the Layer3 in isdn q.931 is sent to the call
manager.
The protocol q.931 is the signalling protocol and it contains the ANI, DNIS numb
ers.
The Q.931 messages are tunnelled to the Voice gateway using the port 2428.