Configuring the Access Gateway Module with Cisco CallManager

Before you configure IP telephony gateway mode, you need to add the Access Gateway module to Cisco CallManager as a new gateway. To add the Access Gateway module to Cisco CallManager, set Gateway Type to H.323 and Device Protocol to H.225 in the Cisco CallManager Administration application.

Figure 8-1 shows an example of the Add a New Gateway screen, with the Gateway Type and Device protocol entered in the drop-down list.

Figure 8-1: Adding Access Gateway Module to Cisco CallManager

Note You will not find the Access Gateway module listed in the drop-down box in Cisco CallManager 3.0.

Configuring the Access Gateway Module in Cisco CallManager

After selecting H.323 as the Gateway Type, you need to configure the Access Gateway module with the Gateway Configuration screen.

Figure 8-2 shows an example of the Gateway Configuration screen.

Figure 8-2: Configuring Access Gateway Module in Cisco CallManager

Enter the IP address of the Access Gateway module, and then select the Device Pool and other information as you would for any other Cisco device.

Note To find the IP address for your Access Gateway module, use the show run command.

H.323 does not pass port information to Cisco CallManager. As a result, there is no port information displayed on the screen. Cisco CallManager needs to use Routing Patterns to direct calls to the proper gateway.

Configuring Route Patterns in Cisco CallManager

Figure 8-3 shows an example of the Route Pattern Configuration screen.

Figure 8-3: Configuring Route Patterns in Cisco CallManager

The Routing Pattern tells Cisco CallManager how to handle incoming calls and to which devices to forward outgoing calls. After you configure Cisco CallManager, the functionality is the same for the Access Gateway module as for other gateway types.

Configuring an FXS Port in Cisco CallManager

Figure 8-3 shows an example of the Route Pattern Configuration screen for the FXS port.

Figure 8-4: Configuring Route Patterns in Cisco CallManager

This example shows an example configuration of the route patterns for an FXS port:

voice-class codec 1
	codec preference 1 g729r8
	codec preference 2 g711ulaw
	
dial-peer voice 100 pots
	destination-pattern +1.
	prefix 1
	port 1/0:23
dial-peer voice 101 pots
	destination-pattern 2010
	port 2/0
dial-peer voice 200 voip
	destination-pattern 2
	ip precedence 5
	voice-class codec 1
	session target dns:cm1.cisco.com

Fax-Relay is enabled by default. You need to set the fax-rate in the dial-peer statement:

chopin(config)# dial-peer voice 1200 voip
chopin(config-dial-peer)# fax-rate ?
12000    FAX   12000 bps
14400    FAX   14400 bps
2400     FAX   2400  bps
4800     FAX   4800  bps
7200     FAX   7200  bps
9600     FAX   9600  bps
disable  Disable Fax Relay
voice    Highest possible speed allowed by voice rate

Configuring Conferencing in Cisco CallManager

To configure conferencing services in Cisco CallManager, see the following sections:

Obtaining the Conference Bridge MAC Address

Before you can add conferencing to Cisco CallManager, you need to obtain the MAC adddress. To obtain the conference bridge MAC address, use the show voicecard conference command.

This example displays the results of the show voicecard conference command:

chopin# show voicecard conference
conferencing:            (mac address 00e0.b0ff.2e99)    Disabled
 
 
chopin(config)# voicecard sccp manager 172.20.58.168 port 2000
chopin(config)# voicecard sccp local g0/0
chopin(config)# voicecard conference ip-precedence 5

Configuring Conference Bridge in Cisco CallManager

To configure Conference Bridge in Cisco CallManager, enter the conference bridge MAC address in the device name field on the Conference Bridge Configuration screen.

Figure 8-5 shows an example of the Conference Bridge Configuration screen with the bridge MAC address entered in the device name field.

Figure 8-5: Configuring Conference Bridge

Configuring Meet Me Conferences in Cisco CallManager

To configure Meet Me Number conferences in Cisco CallManager, enter the Meet Me numbers and pattern in the appropriate fields of the Meet Me Number/Pattern Configuration screen.

Figure 8-6 shows an example of the Meet Me Number/Pattern Configuration screen.

Figure 8-6: Configuring Meet Me Number/Pattern Configuration.

Configuring Transcoding in Cisco CallManager

To configure transcoding services in Cisco CallManager, see the following sections:

Note Cisco CallManager uses Streaming Media Application (MTP). After you add Transcoder to Cisco CallManager, MTP is disabled and requests are forwarded to Transcoder.

Obtaining the Transcoder MAC Address

Before you can add the Transcoder to Cisco CallManager, you need to obtain the MAC adddress. To obtain the Transcoder MAC address, use the show voicecard transcode command.

This example displays the results of the show voicecard transcode command:

chopin# show voicecard transcode
transcoding:            (mac address 00e0.b0ff.2e99)    Disabled
 
 
chopin(config)# voicecard sccp manager 172.20.58.168 port 2000
chopin(config)# voicecard sccp local g0/0
chopin(config)# voicecard transcode ip-precedence 5

Configuring Transcoder in Cisco CallManager

To add the Transcoder to Cisco CallManager, enter the MAC address on the Configure Transcoder screen.

Figure 8-7 shows an example of the Configure Transcoder screen, with the MAC address entered in the appropriate field.

Figure 8-7: Adding Transcoder to Cisco CallManager

VoIP Configurations

This section describes VoIP gateway configurations with and without Cisco CallManager.

Configuring VoIP Without Cisco CallManager

Figure 8-8 shows an example of a VoIP configuration without Cisco CallManager.

Figure 8-8: VoIP Without Cisco CallManager

This example shows a configuration of Access Gateway #1 in Figure 8-8:

	destination-pattern 408.
	port 1/0:0
 
dial-peer voice 101 pots
	destination-pattern 4085551212
	port 2/0
 
dial-peer voice 200 voip
	destination-pattern 212.
	ip precedence 5
	codec g711ulaw
	session target ipv4:10.10.1.2
 
dial-peer voice 201 voip
	incoming called-number 408.
	codec g711ulaw

This example shows a configuration of Gateway #2 in Figure 8-8.

dial-peer voice 100 pots
	destination-pattern 213.
	port 1/0:23
 
dial-peer voice 101 pots
	destination-pattern 2125551212
	port 2/0
 
dial-peer voice 200 voip
	destination-pattern 408.
	ip precedence 5
	codec g711ulaw
	session target ipv4:10.10.1.1
 
dial-peer voice 201 voip
	incoming called-number 213.
	codec g711ulaw

Configuring VoIP with Single Cisco CallManager

Figure 8-9 shows an example of the VOIP configuration with a single Cisco CallManager.

Figure 8-9: Configuring VoIP With Cisco CallManager

This example shows a configuration of the Access Gateway module in VoIP mode with a single Cisco CallManager:

voice-class codec 1
	codec preference 1 g729r8
	codec preference 2 g711ulaw
	
dial-peer voice 100 pots
	destination-pattern +1.
	prefix 1
	port 1/0:23
dial-peer voice 101 pots
	destination-pattern 2010
	port 2/0
dial-peer voice 200 voip
	destination-pattern 2
	ip precedence 5
	voice-class codec 1
	session target dns:cm1.cisco.com

Cisco CallManager Configuration Errors

These are common Cisco CallManager configuration errors:

CM dial pattern and gateway dial-peer statements are not synchronized.
Codecs do not match.
Call setup is successful, but the user receives fast-busy when talk-path is established.

Table of Contents

Configuring the Access Gateway Module with Cisco CallManager