|
|
This chapter describes how to configure voice network modules with recEive and transMit (E&M), Foreign Exchange Office (FXO), and Foreign Exchange Station (FXS) interfaces for your Access Gateway module. Voice network modules convert telephone voice signals into a form that can be transmitted over an IP network.
This chapter contains these sections:
Voice over IP (VoIP) enables your Access Gateway module to carry live voice traffic (for example, telephone calls and faxes) over an IP network. VoIP offers the following benefits:
Before you can configure your Access Gateway module to use VoIP, you need to complete these tasks:
Before you configure an interface, have the following information available:
Obtain this information from your system administrator or network plan before you begin Access Gateway module configuration.
Whenever you install a new interface, or if you want to change the configuration of an existing interface, you must configure the interface. If you replace a module that was already configured, the Access Gateway module recognizes it and brings up the interface in the existing configuration.
 |
TimeSaver Before you begin, disconnect all WAN cables from the Access Gateway module to prevent it from trying to run the AutoInstall process. The Access Gateway module tries to run AutoInstall when you power it on if there is a WAN connection on both ends and the Access Gateway module does not have a valid configuration file stored in NVRAM (for instance, when you add a new interface). The Access Gateway module can take several minutes to determine that AutoInstall is not connected to a remote TCP/IP host. |
To configure a voice interface, use configuration mode (manual configuration). In this mode, you can enter Cisco IOS commands at the Access Gateway module prompt.
To enter configuration mode, follow this procedure:
Step 2 Power on the Access Gateway module by inserting it into a powered chassis or by powering on the chassis. If the current configuration is no longer valid, after about one minute you see the following prompt:
Would you like to enter the initial dialog? [yes/no]:
Enter No. You will enter the normal operating mode of the Access Gateway module. If the current configuration is valid, you enter the normal operating mode automatically.
Step 3 After a few seconds, you see the user EXEC prompt (gateway>). Enter enable and the password to enter enable mode:
gateway> enable Password: <password>
Configuration changes can be made only in enable mode. The prompt changes to the privileged EXEC (enable) prompt:
gateway#
Step 4 Enter the configure terminal command to enter configuration mode:
gateway# configure terminal gateway(config)#
The Access Gateway module enters global configuration mode, indicated by the gateway (config) # prompt.
Step 5 If you have not configured the Access Gateway module, or want to change the configuration, use Cisco IOS commands to configure global parameters, passwords, network management, and routing protocols. In this example, IP routing is enabled:
gateway(config)# ip routing
For complete information about global configuration commands, refer to the Cisco IOS Configuration Guides and Command References.
Step 6 If you have not already done so, configure the WIC that you plan to use for IP traffic. For instructions, see "Installing the Access Gateway module," or the configuration note for the WAN interface card.
Step 7 To configure another interface, enter the exit command to return to the gateway(config) # prompt.
Step 8 To configure the Access Gateway module for voice traffic, refer to the detailed instructions in the Voice over IP Configuration documention.
Step 9 When you finish configuring interfaces, exit configuration mode and return to the enable prompt by pressing Ctrl-z. To see the current operating configuration, including any changes you just made, enter the show running-config command:
gateway# show running-config
To see the configuration currently stored in NVRAM, enter the show startup-config command at the enable prompt:
gateway# show startup-config
Step 10 The results of the show running-config and show startup-config commands differ from each other if you have made changes to the configuration, but have not yet written them to NVRAM. To write your changes to NVRAM, and make them permanent, enter the copy running-config startup-config command at the enable prompt:
gateway# copy running-config startup-config Building configuration. . . [OK] gateway#
The Access Gateway module is now configured to boot in the new configuration.
Your actual configuration procedures depend upon the topology of your network. The following examples provide typical scenarios that you need to customize to reflect your network topology.
These scenarios are examples of VoIP configurations:
The following example shows how to configure VoIP for simple FXS-to-FXS connections.
In this example, a very small company that consists of two offices integrates VoIP into an existing IP network. One basic telephony device is connected to the Access Gateway module AGLB-1. The Access Gateway module AGLB-1 is configured for one POTS peer and one VoIP peer. Because one POTS telephony device is connected to Access Gateway module AGLB-2, it is also configured for one POTS peer and one VoIP peer. In this example, only the calling end (Access Gateway module AGLB-1) is requesting RSVP.
Figure 6-1 illustrates the topology of this FXS-to-FXS connection example.
hostname aglb-1 ! Create voip dial-peer 10 dial-peer voice 10 voip ! Define its associated telephone number and IP address destination-pattern +4155264002 sess-target ipv4:10.0.0.2 ! Request RSVP req-qos guaranteedDelay ! Create pots dial-peer 1 dial-peer voice 1 pots ! Define its associated telephone number and voice port destination-pattern +4085264001 port 1/0 ! Configure serial interface 2/0 interface Serial2/0 ip address 10.0.0.1 255.0.0.0 no ip mroute-cache ! Configure RTP header compression ip rtp header-compression ip rtp compression-connections 25 ! Enable RSVP on this interface ip rsvp bandwidth 96 96 fair-queue 64 256 36 clockrate 128000 gateway igrp 888 network 10.0.0.0 network 20.0.0.0 network 40.0.0.0
hostname ag1b-2 ! Create pots dial-peer 2 dial-peer voice 2 pots ! Define its associated telephone number and voice-port destination-pattern +4155264002 port 1/0 ! Create voip dial-peer 20 dial-peer voice 20 voip !Define its associated telephone number and IP address destination-pattern +4085264001 sess-target ipv4:10.0.0.1 ! Configure serial interface 2/0 interface Serial2/0 ip address 10.0.0.2 255.0.0.0 no ip mroute-cache ! Configure RTP header compression ip rtp header-compression ip rtp compression-connections 25 ! Enable RSVP on this interface ip rsvp bandwidth 96 96 fair-queue 64 256 3 clockrate 128000 ! Configure IGRP gateway igrp 888 network 10.0.0.0 network 20.0.0.0 network 40.0.0.0
The following example shows how to configure VoIP to link users with the PSTN gateway using an FXO connection.
In this example, users connected to the Access Gateway module in San Jose can reach PSTN users in Salt Lake City through Access Gateway module in Salt Lake City. The Access Gateway module in Salt Lake City is connected directly to the PSTN through an FXO interface.
Figure 6-2 illustrates the topology of this connection example.
 |
Note This example assumes that the company already has established a working IP connection between its two remote offices. |
! Configure pots dial-peer 1 dial-peer voice 1 pots destination-pattern +14085554000 port 1/0 ! Configure voip dial-peer 2 dial-peer voice 2 voip destination-pattern +9........... session target ipv4:172.16.65.182 ! Configure the serial interface interface serial 2/0 clock rate 2000000 ip address 172.16.1.123 no shutdown
! Configure pots dial-peer 1 dial-peer voice 1 pots destination-pattern +9........... port 1/0 ! Configure voip dial-peer 2 dial-peer voice 2 voip destination-pattern +14085554000 session target ipv4:172.16.1.123 ! Configure serial interface interface serial 2/0 ip address 172.16.65.182 no shutdown
The following example shows how to configure VoIP to link users with the PSTN gateway using an FXO connection in PLAR mode.
In this example, PSTN users in Salt Lake City can dial a local number and establish a private line connection in a remote location. As in the previous example, the Access Gateway module SLC in Salt Lake City is connected directly to the PSTN through an FXO interface.
Figure 6-3 illustrates the topology of this connection.
|
Note This example assumes that the company already has established a working IP connection between its two remote offices. |
! Configure pots dial-peer 1 dial-peer voice 1 pots destination-pattern +14085554000 port 1/0 ! Configure voip dial-peer 2 dial-peer voice 2 voip destination-pattern +9........... session target ipv4:172.16.65.182 ! Configure the serial interface interface serial 2/0 clock rate 2000000 ip address 172.16.1.123 no shutdown
! Configure pots dial-peer 1 dial-peer voice 1 pots destination-pattern +9........... port 1/0/0 ! Configure voip dial-peer 2 dial-peer voice 2 voip destination-pattern +14085554000 session target ipv4:172.16.1.123 ! Configure the voice port voice port 1/0 connection plar 14085554000 ! Configure the serial interface interface serial 2/0 ip address 172.16.65.182 no shutdown
Posted: Thu Sep 14 18:43:00 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.