Cisco Cisco IOS Software Release 12.2(2)XA
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
Configuration Tasks
10
Cisco IOS Release 12.2(2)XA
Starting the MGCP Daemon
This task is required. To start the MGCP daemon, complete this step, beginning in global configuration
mode:
mode:
Configuring Global MGCP Parameters
This optional task configures global MGCP parameters on the gateway so that you can set these values
to conform to the requirements of the call agent, trunks, or lines that are being used with this gateway.
The global parameter values that you configure affect all the MGCP endpoints that you have identified
on this gateway.
to conform to the requirements of the call agent, trunks, or lines that are being used with this gateway.
The global parameter values that you configure affect all the MGCP endpoints that you have identified
on this gateway.
In addition to global MGCP parameters, there are also other MGCP parameters that apply to MGCP
profiles on the gateway. Table 2 on page 7 lists the different commands that configure global and
profile-related MGCP parameters. For configuration of profile-related parameters, see the “Configuring
an MGCP Profile and Profile-Related MGCP Parameters” section on page 13.
profiles on the gateway. Table 2 on page 7 lists the different commands that configure global and
profile-related MGCP parameters. For configuration of profile-related parameters, see the “Configuring
an MGCP Profile and Profile-Related MGCP Parameters” section on page 13.
Note
The only parameter that is common to both profile and global configurations is call agent,
which is configured with the call-agent command for MGCP profile configuration and
with the mgcp call-agent command for the global configuration. These commands are
mutually exclusive; if one of these commands is configured for an endpoint, you are
blocked from configuring the other. For example, if the MGCP profile call-agent
command is configured on an endpoint, then you will not be allowed to configure the
global mgcp call-agent command. This applies the other way round as well.
which is configured with the call-agent command for MGCP profile configuration and
with the mgcp call-agent command for the global configuration. These commands are
mutually exclusive; if one of these commands is configured for an endpoint, you are
blocked from configuring the other. For example, if the MGCP profile call-agent
command is configured on an endpoint, then you will not be allowed to configure the
global mgcp call-agent command. This applies the other way round as well.
Table 6
Identifying MGCP Endpoints for Analog CAS and POTS Lines
Command
Purpose
Step 1
Router(config)# dial-peer voice tag pots
Enters dial-peer configuration mode and specifies
the method of voice encapsulation.
the method of voice encapsulation.
Step 2
Router(config-dial-peer)# application mgcpapp
Enables the MGCP application on this dial peer.
Step 3
Router(config-dial-peer)# port number
Associates a dial peer with a specific voice port.
Step 4
Router(config-dial-peer)# exit
Exits dial-peer configuration mode.
Command
Purpose
Step 1
Router(config)# mgcp [port-number]
Initiates the MGCP daemon. The optional port
number argument allows you to specify the UDP
port over which the gateway receives messages
from the call agent (the gateway MGCP port
number).
number argument allows you to specify the UDP
port over which the gateway receives messages
from the call agent (the gateway MGCP port
number).
The default UDP port number for gateways is
2427.
2427.