Tuesday, October 9, 2012

VGW - MGCP the Easy Way

     Media Gateway Control Protocol (MGCP) is a is a plain-text (sent over UDP on port 2427) protocol used by call-control devices (like Communications Manager), known as media gateway controllers (MGCs) or call agents (CAs), to take control of a specific port on a gateway. Cisco Communications Manager knows and controls the state of each individual port on the gateway.

     If you want the fastest and automated way of configuration an MGCP gateway, you can utilize the "ccm-manager config server" CLI command. Having this automated MGCP configuration does not allow for partial/fractional T1 PRI's, but what you can do is enable the automation, modify the T1 manually, and disable the automation after all of the commands have been populated. Here's the steps in setting up an MGCP gateway:

  1. On the gateway, set the "ip domain name" and "hostname"(eg. BR1.company.com)
    1. This provides the full domain name which MGCP utilizes to register the gateway
  2. Configure the gateway on Cisco Communications Manager
    1.  CM Administration > Device > Gateway
    2. Add New
    3. Select specific Gateway Type (eg. Cisco 3945)
    4. Select MGCP as the protocol
    5. Set the full domain name of the router and CUCM Group
    6. Set the appropriate modules 
    7. Configure each of the endpoints/circuits
  3. From the Gateway's CLI configure MGCP
    1. mgcp bind control source-interface <voice interface or loopback>
    2. mgcp bind media source-interface <voice interface or loopback>
    3. ccm-manager config server <CUCM IP Address Primary> <CUCM IP Address Secondary>
    4. ccm-manager config
    5. ccm-manager mgcp

 MGCP Messages:
Command
Message Name
Sent By
Description
AUEP
AuditEndpoint
CallManager
Determines the status of a given endpoint.
AUCX
AuditConnection
CallManager
Retrieves all the parameters associated with a connection.
CRCX
CreateConnection
CallManager
Creates a connection between two endpoints.
DLCX
DeleteConnection
Both
From CallManager: Terminates a current connection.
From Gateway: Indicates that a connection can no longer be sustained.
MDCX
ModifyConnection
CallManager
Changes the parameters associated with an established connection.
RQNT
NotificationRequest
CallManager
Instructs the gateway to watch for special events such as hooks or DTMF tones. It is also used to instruct the gateway to provide a signal to the endpoint (for example, dial tone and busy tone).
NTFY
Notify
Gateway
Informs the Cisco CallManager when requested events occur.
RSIP
RestartInProgress
Gateway
Informs the Cisco CallManager that an endpoint or group of endpoints are taken out or placed back into service.









.

No comments:

Post a Comment