Cisco Cisco IOS Software Release 12.2(2)XA
MGCP 1.0 Including NCS 1.0 and TGCP 1.0 Profiles
Configuration Tasks
13
Cisco IOS Release 12.2(2)XA
Configuring an MGCP Profile and Profile-Related MGCP Parameters
This optional task creates a named, user-defined MGCP profile that consists of a subset of all the MGCP
endpoints on this gateway. More than one MGCP profile can be configured on a gateway. Each MGCP
profile is associated with a call agent and one or more endpoints. When multiple MGCP profiles are
configured, endpoints on a single media gateway can be controlled by different call agents. When each
endpoint comes on line, an RSIP (RestartInProgress) message notifies the appropriate call agent of the
endpoint’s presence.
endpoints on this gateway. More than one MGCP profile can be configured on a gateway. Each MGCP
profile is associated with a call agent and one or more endpoints. When multiple MGCP profiles are
configured, endpoints on a single media gateway can be controlled by different call agents. When each
endpoint comes on line, an RSIP (RestartInProgress) message notifies the appropriate call agent of the
endpoint’s presence.
Note
When partitioning a gateway for multiple call-agent control, the call agents must be
coordinated so that there are no overlapping transaction identification numbers.
coordinated so that there are no overlapping transaction identification numbers.
In addition, this task allows you to configure profile-related MGCP parameters to conform to the
requirements of the call agent, trunks, or lines that are being used with the profile’s endpoints. These
parameters are called profile-related MGCP parameters because they are associated with a particular
MGCP profile, or subset of endpoints, and they are configured in MGCP profile configuration mode.
Other parameters are considered global MGCP parameters; when they are configured, they apply to all
the endpoints on a gateway. Table 2 on page 7 lists commands that configure global and profile-related
MGCP parameters. Global MGCP parameters are discussed in the “Configuring Global MGCP
Parameters” section on page 10.
requirements of the call agent, trunks, or lines that are being used with the profile’s endpoints. These
parameters are called profile-related MGCP parameters because they are associated with a particular
MGCP profile, or subset of endpoints, and they are configured in MGCP profile configuration mode.
Other parameters are considered global MGCP parameters; when they are configured, they apply to all
the endpoints on a gateway. Table 2 on page 7 lists commands that configure global and profile-related
MGCP parameters. Global MGCP parameters are discussed in the “Configuring Global MGCP
Parameters” section on page 10.
The parameters for an MGCP profile are configured in a special MGCP profile configuration mode that
you enter with the mgcp profile command. One or more endpoints are associated with the profile by
using the voice-port command in MGCP profile configuration mode.
you enter with the mgcp profile command. One or more endpoints are associated with the profile by
using the voice-port command in MGCP profile configuration mode.
Note
The only parameter that can be configured in both profile configuration mode and in global
configuration mode is call agent, which is configured with the call-agent command for
MGCP profiles, and with the mgcp call-agent command for global configurations. These
commands are mutually exclusive; if one of these commands is configured, you are
blocked from configuring the other. For example, if the MGCP profile call-agent
command is configured for an MGCP profile, then you are not allowed to configure the
global mgcp call-agent command. This applies the other way round as well.
configuration mode is call agent, which is configured with the call-agent command for
MGCP profiles, and with the mgcp call-agent command for global configurations. These
commands are mutually exclusive; if one of these commands is configured, you are
blocked from configuring the other. For example, if the MGCP profile call-agent
command is configured for an MGCP profile, then you are not allowed to configure the
global mgcp call-agent command. This applies the other way round as well.
You do not have to define MGCP profiles to configure profile-related parameters. For endpoints that are
not associated with a user-defined MGCP profile, the values for profile-related parameters are provided
by a default profile. The default profile is configured in the same way that a user-defined MGCP profile
is configured, except that the keyword default is used in place of a profile name in the mgcp profile
command. The default profile has no association with voice ports or a call agent (the call agent for these
endpoints is defined by the global mgcp call-agent command).
not associated with a user-defined MGCP profile, the values for profile-related parameters are provided
by a default profile. The default profile is configured in the same way that a user-defined MGCP profile
is configured, except that the keyword default is used in place of a profile name in the mgcp profile
command. The default profile has no association with voice ports or a call agent (the call agent for these
endpoints is defined by the global mgcp call-agent command).
In the example below, two MGCP profiles are defined: MAX1 and MAX2. Each profile is associated
with a different call agent and a different voice port. The MAX1 profile is configured with a value of 3
for the max1 retries parameter and 5 for max2 retries. The MAX2 profile uses the values in the default
profile for those parameters. In the MAX2 profile, the MT package is configured as a persistent
with a different call agent and a different voice port. The MAX1 profile is configured with a value of 3
for the max1 retries parameter and 5 for max2 retries. The MAX2 profile uses the values in the default
profile for those parameters. In the MAX2 profile, the MT package is configured as a persistent