Case Study: Configuring an MGCP Gateway
Case Study Providing Enterprise VoIP Trunking to VoIP Service of the Service Provider
The New York office needs to connect a CallManager H.225 trunk to a SIP service provider. The CallManager is version 4.1.3. To provide security and protocol interworking, you plan to implement an IPIPGW to connect with the service provider, as shown in Figure 18-6.
Figure 18-6. New York IPIPGW Implementation
CallManager Configuration
Note the following points in CallManager trunk configuration:
- Configure the CallManager with an H.225 gatekeeper-controlled trunk
- Check Media Termination Point Required
- Uncheck Wait for Far End H.245 Terminal Capability Set
- Check Enable Inbound FastStart
- Gatekeeper Name should be IP Address Gatekeeper
- Gatekeeper Terminal Type should be Gateway
- Technology prefix should be 1#
Example 18-15 shows the configuration steps for implementing the IPIPGW. In this example, the Cisco IOS gatekeeper and the IPIPGW are running on the same router platform.
|
[View full width] ! ! Enabling IPIPGW functionality ! IPIPGateway#config t IPIPGateway(config)#voice service voip IPIPGateway(conf-voi-serv)#allow-connections h323 to sip IPIPGateway(conf-voi-serv)#allow-connections sip to h323 IPIPGateway(config-voi-serv)#exit ! ! Configuring the gatekeeper ! IPIPGateway(config)#gatekeeper IPIPGateway(config-gk)#zone local via_gk zone2 IPIPGateway(config-gk)#zone local CCM zone2 invia via_gk outvia via_gk IPIPGateway(config-gk)#zone prefix CCM 2125553... gw-priority 6 |
Figures 18-7, 18-8, and 18-9 illustrate the CallManager H.225 trunk configuration.
Figure 18-7. CallManager H.225 Trunk Configuration
Figure 18-8. CallManager H.225 Trunk Configuration (Continued)
Figure 18-9. CallManager H.225 Trunk Configuration (Continued)