Configuring an MGCP Trunk Gateway
Router(config)#ccm-manager mgcp
Router(config)#mgcp 4000
Router(config)#mgcp call-agent 209.165.202.129 4000
Router(config)#controller t1 1/0
Router(config-controller)#framing esf
Router(config-controller)#clock source internal
Router(config-controller)#ds0-group 1 timeslots 1-24 type none service mgcp
Router(config-controller)#exit
Router(config)#controller t1 1/1
Router(config-controller)#framing esf
Router(config-controller)#clock source internal
Router(config-controller)#ds0-group 1 timeslots 1-24 type none service mgcp
Router(config-controller)#exit
|
Configuring trunk gateways requires the address or the name of
the call agent, which is a requirement common to a residential gateway (RGW).
The trunk package is the default for a trunk gateway and does not need to be
configured. Again, other parameters are optional.
Example 6-13 illustrates
commands for configuring a trunk gateway. Instead of using the application mgcpapp command in a dial peer, a trunk
endpoint identifies its association with MGCP using the service mgcp parameter in the ds0-group controller subcommand. As always in MGCP,
the call agent maintains the relationship between the endpoint (in this case a
digital trunk) and its address.
Sections
Comments (0 posted)
Syndication
