|
|
This chapter contains configuration examples using the Cisco IOS software command-line interface (CLI) and Cisco CallManager. It contains the following sections:
This section presents examples that illustrate how to configure LAN and WAN interfaces on analog station interface (ASI) and multiservice route processor (MRP) cards (see the "Configuring WAN Interfaces" section) and contains the following sections:
This section explains how to configure a Fast Ethernet port on an ASI or MRP card.
To configure a Fast Ethernet interface on an ASI or MRP card, use the configuration mode to enter IOS commands at the ASI or MRP command prompt (see the "Configuring Fast Ethernet Ports" section):
 |
Note Use ICSConfig to assign or modify the IP address of an ASI or MRP card, as necessary. Do not use the CLI. |
To configure the serial interfaces on your asynchronous/synchronous serial WIC (WIC-1T, WIC-2T, or WIC-2A/S), enter the following IOS commands at the ASI or MRP command prompt, in configuration mode (see the "Configuring WAN Interfaces" section):
| Command | Purpose | |
|---|---|---|
| Step 1 |
Enters enable mode. You have entered enable mode when the prompt changes to |
|
| Step 2 |
Enters global configuration mode. You have entered global configuration mode when the prompt changes to |
|
| Step 3 | Enables routing protocols as required for your global configuration. This example uses IP routing. |
|
| Step 4 |
Enters the interface configuration mode. You have entered interface configuration mode when the prompt changes to |
|
| Step 5 | (Optional) All serial ports are initially configured as synchronous. Enter this command if you want to configure the port as asynchronous. |
|
| Step 6 | (Optional) Assigns asynchronous parameters. Enter these parameters as needed for your configuration. |
|
| Step 7 | ||
| Step 8 | (Optional) Specifies the time that the interface waits in controlled carrier mode. See Table 6-10 for a list of half-duplex timer commands. |
|
| Step 9 | (Optional) To use a port in DCE1 mode, connect a DCE cable, and set the internal TXC2 speed in bits per second. See Table 6-11 through Table 6-13 for clock rate settings for your interface. (For ports used in DTE3 mode, the MRP automatically uses the external timing signal.) |
|
| Step 10 | (Optional) When a port is operating in DCE mode, by default the DCE sends SCT4 and SCR5 clock signals to the DTE, and the DTE returns an SCTE6 signal to the DCE. If the DTE does not return an SCTE signal, enter this command to configure the DCE port to use its own clock signal. |
|
| Step 11 | (Optional) Interfaces that are connected with long cables might experience high error rates when operating at higher transmission speeds, because the clock and data signals can shift out of phase. If a DCE port is reporting a high number of error packets, using this command to invert the clock can often correct the shift. |
|
| Step 12 | Exits to global configuration mode. Note Repeat Step 4 through Step 12 if your MRP has more that one serial interface that you need to configure. |
|
| Step 13 | ||
| Step 14 | Saves the configuration changes to the startup-config file so that they are not lost during resets, power cycles, or power outages. |
| 1DCE = data communications equipment. Modems (analog) and CSU/DSUs (digital) are the most common DCE types.
2TXC = transmit clock signal 3DTE = data terminal equipment. Computers and terminals are the most common DTE types. 4SCT = serial clock transmit 5SCR = serial clock receive 6SCTE = serial clock transmit external |
|
Note Use ICSConfig to assign or modify the IP address of an ASI or MRP card, as necessary. Do not use the CLI. |
To configure the interfaces on your Basic Rate Interface (BRI) WIC (WIC-1B-S/T or WIC-1B-U), enter the following IOS commands at the ASI or MRP command prompt, in configuration mode (see the "Configuring ISDN BRI WICs" section):
| Command | Purpose | |
|---|---|---|
| Step 1 |
Enters enable mode. You have entered enable mode when the prompt changes to |
|
| Step 2 |
Enters global configuration mode. You have entered global configuration mode when the prompt changes to |
|
| Step 3 | Specifies an ISDN switch type. See Table 6-14 for a list of ISDN switch types. Note Switch types that are configured in interface configuration mode override this setting for the configured interface. |
|
| Step 4 | Enables routing protocols as required for your global configuration. This example uses IP routing. |
|
| Step 5 |
Enters interface configuration mode. You have entered interface configuration mode when the prompt changes to |
|
| Step 6 | If you are configuring this interface for voice, enter the switch type instead of an IP address. |
|
| Step 7 | Exits to global configuration mode. Note Repeat Step 5 through Step 7 if your card has more than one BRI interface that you need to configure. |
|
| Step 8 | (Optional) By default, the card allocates 25 percent of dynamic RAM (DRAM) to shared memory (used for data transmitted or received by WICs). Enter this command if you wish to increase the amount of shared memory. This example increases shared memory from 25 percent to 40 percent. |
|
| Step 9 | ||
| Step 10 | Saves the configuration changes to the startup-config file so that they are not lost during resets, power cycles, or power outages. |
|
Note Use ICSConfig to assign or modify the IP address of an ASI or MRP card, as necessary. Do not use the CLI. |
The IOS software provides the following default configuration for CSU/DSU- and T1-specific parameters:
To configure a new T1 or fractional T1 interface or to change the configuration of an existing interface, enter the following IOS commands in configuration mode (see the "Configuring T1 and Fractional T1 WICs" section):
| 1SF = Super Frame
2AMI = alternate mark inversion |
To configure a new T1 or E1 VWIC interface or to change the configuration of an existing interface, enter the following IOS commands (see the "Configuring VWICs for Data-Only Transmission" section):
|
Note Use ICSConfig to assign or modify the IP address of an ASI or MRP card, as necessary. Do not use the CLI. |
This section guides you through a sample Media Gateway Control Protocol (MGCP) configuration. This section presents only the minimum commands required for building a working configuration for an MRP with two Foreign Exchange Office (FXO) ports and two Foreign Exchange Station (FXS) ports.
This section describes how to configure one FXO connection to the PSTN, as well as FXS connections to analog handsets and VoIP connectivity to Cisco 7960 IP Phones. After performing this sample configuration, you will be able to make calls to and from all the phones in this example, and you will be able to route calls over the PSTN from any phone in this example.
This section assumes that the reader is already familiar with the process of configuring Cisco IP Phones in CallManager. It also assumes that there is at least one IP Phone already active on the CallManager server.
|
Note Before performing this sample configuration, you need to have previously run the ICSConfig initial configuration program on the Cisco ICS 7750, you need to have configured IP routing on the MRP, and you need to have configured the voice ports on the MRP. |
This section addresses the following topics:
The following procedure shows the minimum commands necessary for configuring an MRP or ASI for MGCP in the sample configuration.
Step 2 Configure the IP address (or DNS name) for the CallManager server.
Step 3 Select the codec type and the DTMF relay function.
Step 4 To enable support for Cisco CallManager within MGCP, enter the following command:
Step 5 Bind the MGCP application to the voice ports.
|
Note Use the show voice port command to determine the type of ports the MRP has and in what order they are installed. |
Step 6 Make certain that the voice ports are enabled.
|
Note The shutdown and no shutdown commands affect both ports on a VIC. It is necessary to enter the command on only one of the ports. |
The MRP is now ready to communicate with the CallManager server. It will periodically send out messages to attempt to establish a connection. When the CallManager server configuration is complete, the connection should automatically establish itself. You should not have to make any further changes on the MRP.
 |
Caution All dial plan-related configuration elements are controlled by Cisco CallManager, and they should not be configured in the MGCP gateway for MGCP-managed endpoints (those with application mgcpapp command in their dial-peer statement). You should not configure any of the following functions: Under Dial Peers destination-pattern Under Voice Ports connection { plar | tie line | trunk } |
This section shows how to configure Cisco CallManager for the sample configuration described in the previous section. It includes the following sample procedures:
This example uses the Default Device Pool. In addition, all Locations are set to < None >, all Calling Search Spaces are set to < None >, and all Partitions are set to < None >. If your configuration uses non-default Device Pools, Locations, Calling Search Spaces, or Partitions you must understand the implications of these features before proceeding. For more information about Cisco CallManager, refer to the Cisco CallManager Administration Guide .
|
Note This section assumes that you already have IP Phones configured on your CallManager server. |
This sample procedure shows how to create an MRP-based MGCP gateway in Cisco CallManager.
Step 2 In the Location or Address field, enter the following URL, replacing <ipaddress> with the IP address of the SPE running Cisco CallManager:
You are prompted for a user ID and password.
Step 3 In the User Name field, enter the User ID of your Administrator account.
Step 4 In the Password field, enter your Administrator account password.
Step 5 Click OK.
The Cisco CallManager Administration page appears.
Step 6 From the menu bar at the top of the page, select Device > Gateway.
The Find and List Gateways page appears, as shown in Figure 7-1.
Step 7 Click Add a New Gateway.
The Add a New Gateway page appears, as shown in Figure 7-2.
Step 8 In the Gateway Type field, select Cisco ICS77XX-MRP2XX.
|
Note This example uses the gateway type Cisco ICS77XX-MRP2XX. The Cisco Integrated Communication System 7750 (Cisco ICS 7750) also supports gateway types Cisco ICS77XX-ASI160 and Cisco ICS77XX-ASI81, in case your configuration includes these ASI cards. |
Step 9 Click Next.
The MGCP Configuration page appears, as shown in Figure 7-3.
Step 10 In the MGCP Domain Name field, enter the actual host name you have assigned to the MRP—in this case, MRP_1.
Step 11 In the Description field, enter an optional description of this MGCP gateway.
Step 12 In the Cisco CallManager Group field, choose the Cisco CallManager group in which you want to create the MGCP gateway.
Step 13 In the Installed Voice Interface Cards fields, select the carrier modules installed in the MRP. VWIC-SLOT is the only option available for the MRP.
Step 14 Scroll down the page, and configure any other settings necessary to describe your configuration. In this example, the default settings were chosen.
|
Note For more information about the settings on this page, choose Help > For This Page from the main menu, or click the blue button labeled "i." |
This procedure continues the configuration example and shows how to configure the FXO ports. The FXO ports connect to the PSTN. In this procedure, the type of port is determined and the attendant Directory Number (DN) is assigned.
Identify the VIC modules installed in slot 0, positions 0 and 1. In this example, they are a VIC-2FXO module and a VIC-2FXS module, respectively.
Step 2 Click Update to activate the changes.
The FXO and FXS ports appear next to the VIC module fields, as shown in Figure 7-5. These ports are also referred to as endpoint identifiers.
Step 3 Click the FXO port labeled 0/0.
The Gateway Configuration appears.
Step 4 In the Port Type field, select the type of FXO port. In this example, Loop Start is selected.
|
Note If you are not certain which option to use, you can experiment, without causing the system any harm. If you are not able to make or receive calls over the FXO port after you complete the MRP and CallManager configuration tasks, you can create a new MGCP Member, using the Ground Start option. You must first delete the original port configuration (MGCP Member). This step is required because it is not possible to change the port type of an MGCP Member after it is created. |
The Gateway Configuration page shows all the configuration options for the type of FXO port selected. For this example, Figure 7-6 shows the FXO Loop Start options.
Step 5 Configure the parameters necessary for your FXO gateway. An asterisk after a field name indicates that you must enter information in the field.
In Figure 7-6, Default was chosen in the Device Pool field. For the Port Direction field, Bothways was selected, to indicate that calls can be both originated and received through this FXO gateway. In the Attendant DN field, 7010 was entered, to indicate that extension 7010 should initially receive all incoming calls. All other fields were left with their default options.
|
Note For more information about the settings on this page, choose Help > For This Page from the main menu, or click the blue button labeled "i." |
Step 6 Click Insert.
Step 7 Click Back to MGCP Configuration.
You are returned to the MGCP Configuration page.
|
Note If you have additional FXO ports to configure, you can configure them by repeating Step 3 through Step 7 for each port. In this sample configuration, the second FXO port is not configured. |
This procedure continues the procedure, "Configuring FXO Ports," and shows how to configure FXS ports. The FXS ports connect to the analog telephony devices, handsets in this example. In this procedure, the type of port is determined and the DN is assigned. At the end of this procedure, the MGCP gateway is reset to activate the changes.
The Gateway Configuration page appears, showing the FXS options, as shown in Figure 7-7.
Step 2 Configure the parameters necessary for your FXS gateway. An asterisk after a field name indicates that you must enter information in the field.
In the example above, Default was chosen in the Device Pool field. All other fields were left with their default options.
|
Note For more information about the settings on this page, choose Help > For This Page from the main menu. |
Step 3 Click Insert.
Next to the icon in the top left corner of the Gateway Configuration page are icons that indicate the various FXS ports on this module. Next to the port just configured, which is 1/0 in this example, a link to Add DN appears on the page. This option lets you add a directory number (extension) for the FXS port that you just configured.
Step 4 Click Add DN.
The Directory Number Configuration page appears, as shown in Figure 7-8.
Step 5 Configure the parameters necessary for your directory number. An asterisk after a field name indicates that you must enter information in the field.
In the example shown in Figure 7-8, the directory number 7100 was entered in the Directory Number field, to assign extension 7100 to the phone connected to this port. All other fields were left with their default options.
|
Note For more information about the settings on this page, choose Help > For This Page from the main menu. |
Step 6 Click Insert.
Step 7 A confirmation dialog box appears. Click OK.
Step 8 In the top left corner, click the icon for FXS port 1/1 to configure the second FXS port.
Step 9 Repeat Step 2 through Step 7 for the remaining FXS port. In this example, the directory number for FXS port 1/1 is 7101.
|
Note If you lose your place in the menu system, select Device > Gateway from the main CallManager menu at the top of the screen. Then select Find. All the configured gateways will be listed on the screen. |
You have now configured the two FXS ports for the analog handsets. Next you must reset the gateway to activate the changes.
Step 10 Click Back to MGCP Configuration.
Step 11 Click Reset Gateway.
The Reset Gateway dialog box appears, as shown in Figure 7-9.
Step 12 Click Restart.
Restarting the gateway applies all your configuration changes to the configured gateway.
When you finish configuring the MRP, it will send MGCP messages to the CallManager server to attempt to establish an MGCP relationship. If the configuration was successful, the CallManager server and the MRP should be ready to route local calls between any IP phones registered to the CallManager and the analog phones connected to the FXS ports that were configured in the previous procedure, "Configuring FXS Ports."
Step 2 You should also be able to dial any IP Phones that you already had configured from the analog phones that you configured. You should also be able to call the analog phones from the IP Phones. Try making calls to and from all the phones in your configuration.
If some of your phones cannot place or receive calls, look at the Partition, Calling Search Space (CSS), Device Pool, and Location configurations. You may have a configuration that does not allow all local phones to call each other. If this is the case, temporarily place one IP Phone and one analog phone (FXS port) in the same Partition, Device Pool, Location, and Calling Search Space; then try the test again. When you have completed this task successfully, proceed to the next sample procedure, "Configuring a Route Pattern."
This sample procedure configures a simple route pattern to enable the phones to make calls via the PSTN. The standard North American Numbering Plan (NANP) pattern of "9.@" will be used.
The Find and List Route Patterns page appears.
Step 2 Click Add a New Route Pattern.
Step 3 The Route Pattern Configuration page appears, as shown in Figure 7-10.
Step 4 In the Route Pattern field, enter 9.@ to indicate the standard route pattern for dial plans using the NANP. This route pattern is configured to provide dial tone (on by default).
|
Note The Route Pattern "9.!" is often used for installations outside the United States that cannot use the NANP. |
Step 5 In the Gateway Router List field, choose the FXO gateway you configured previously.
Step 6 In the Discard Digits field, choose PreDot to indicate that the route pattern should drop everything up to and including the "." in the route pattern.
|
Note This example leaves all other fields at their default values. For more information on these fields and on how you might configure them for your installation, choose Help > For This Page from the main menu. |
You should now be able to route calls over the PSTN from any phone on the system by dialing a 9 and the phone number after you hear the dial tone. Perform the following steps to test calling:
Step 2 Try making a call to the PSTN from an IP phone.
This section contains examples for H.323 call routing configuration and contains the following sections:
This section explains how to map destination telephone numbers with the voice ports on the MRP or ASI card.
To configure a plain old telephone service (POTS) dial peer to associate a physical voice port with a local telephone device, use these key commands to configure the port and destination-pattern (see the "Configuring Dial Plans" section):
To configure a VoIP dial peer to associates a telephone number with an IP address, use these key commands to configure the destination-pattern and session target (see the "Configuring Dial Plans" section):
To define how to expand an extension number into a particular destination pattern, use the following global configuration command (see the "Create a Number Expansion Table" section):
Use the show num-exp command to verify that you have mapped the telephone numbers correctly.
After you have configured dial peers and assigned destination patterns to them, use the show dialplan number command to see how a telephone number maps to a dial peer.
|
Note You must still configure each telephone number in full on a local dial peer so that the MRP can find the voice port to which the number belongs. |
This section contains the following subsections:
This section explains how to configure ports on FXS VICs that connect directly to a standard telephone, fax machine, or similar device.
To configure the MRP with the dial-peer information in Table 6-19, enter the following global configuration commands:
To configure a VoIP dial peer on the West MRP for every telephone on the East MRP, all associated with the same IP address, enter the following information on the West MRP. See Table 6-22.
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 | Specifies the destination telephone number to be associated with the POTS dial peer. |
|
| Step 3 |
If you configured POTS dial peers on your MRP by following these examples, you can place calls between telephones connected to the same MRP. You can also use the show dial-peer voice command to verify that the data you configured is correct.
|
Note If the voice port is off line, use the interface configuration no shutdown command to enable it. |
|
Note Although placing calls directly between ports on the same MRP helps to verify your configuration, it is not recommended for general telecommunications use. |
To configure number expansion, enter the following commands on the East MRP to create the dial-peer configuration given in Table 6-23:
If you configured VoIP dial peers on your MRP by following these examples, you can place calls from that MRP to telephones on the remote MRPs (using only the extension if you configured number expansion). If you have trouble placing calls, ping the remote MRP to make sure you have IP connectivity, or use the show dial-peer voice command to verify that the data you configured is correct.
|
Note See the "Configuring Quality of Service" section if you need to improve the quality of voice connections. |
This section explains how to configure ports on FXO VICs.
To configure 9 to reach an outside line (that is, the analog PSTN), as mentioned in the "FXO Gateway to PSTN" section, enter the following commands:
To enable East MRP users to make calls over the West MRP local PSTN, enter the following commands:
If you configured your FXO interface according to this example, you can place outgoing calls over the PSTN. If you have trouble placing calls, use the show voice port command to make sure that the VIC is installed correctly. Use the show dial-peer voice command to make sure that the data you configured is correct, and test the PSTN by connecting a handset directly to the PSTN outlet and placing a call.
|
Note See the "Configuring Quality of Service" section if you need to improve the quality of voice connections. |
This section explains how to configure ports on E&M VICs.
To configure a local dial peer as if all the West telephones (represented by a wildcard destination pattern) are connected directly to this port, as referenced in the "Configuring E&M Interfaces" section, enter the following commands:
To configure VoIP dial peers for outgoing calls and to associate destination phone numbers on the East MRP with that MRP IP address, as shown in Figure 6-12, enter the following commands:
Follow these steps to configure the E&M port on the West MRP, as shown in Figure 6-12:
| Command | Purpose | |
|---|---|---|
| Step 1 | ||
| Step 2 | ||
| Step 3 | Specifies the appropriate cabling scheme for this voice port. |
|
| Step 4 |
|
Note For these commands to take effect, you have to cycle the port by using the shutdown and no shutdown commands. |
|
Note Configure the PBX to pass all DTMF signals to the MRP. |
If you configured the E&M interfaces correctly, you can place calls from a telephone served by one PBX to a telephone served by the other PBX (using only the extension, if you configured number expansion). If you have trouble placing calls, ping the remote MRP to make sure that you have IP connectivity.
|
Note See the "Configuring Quality of Service" section if you need to improve the quality of voice connections. |
This section provides configuration instructions on the following topics:
To configure a POTS dial peer for DID, following these steps, beginning in global configuration mode (see Figure 6-9):
|
Note DID is configured for inbound POTS dial peers only. |
The steps in this section include commands for configuring an NT interface and a TE interface.
To configure an ISDN BRI interface, follow these steps, beginning in global configuration mode (see the "Configuring ISDN Voice Interfaces" section):
| Command | Purpose | |
|---|---|---|
| Step 1 | Specifies an ISDN switch type. See Table 6-14 for a list of ISDN switch types. Note The only switch type currently supported for an NT interface is basic-net3. |
|
| Step 2 |
Enters interface configuration mode for slot 0, port 0. You have entered interface configuration mode when the prompt changes to |
|
| Step 3 |
Specifies that there is no IP address for this interface. For information about IP addressing, refer to the |
|
| Step 4 | (Optional) Activates overlap signaling to send to the destination PBX. In this mode, the interface waits for possible additional call-control information. |
|
| Step 5 | ||
| Step 6 | ||
| Step 7 | Configures the Layer 1 port mode emulation and clock settings. |
|
| Step 8 | ||
| Step 9 | (Optional; TE only) Configures the priority of the network clock for this BRI voice port. If this port is configured as TE and you want it to be the first-priority BRI voice port for recovering the clock signal from the network NT device, enter high. If this BRI voice port is configured as TE and you want it to be a low-priority BRI voice port for recovering the clock signal from the network NT device, enter low. The default for the BRI VIC is high. Do not use this command if this port is configured as NT with the command isdn layer1-emulate network. |
|
| Step 10 | ||
| Step 11 | (Optional) Configures the voice port to include the "Sending Complete" information element in the outgoing call setup message. This command is used in some geographic locations, such as Hong Kong and Taiwan, where the "Sending Complete" information element is required in the outgoing call setup message. |
|
| Step 12 | (Optional) Configures a static ISDN Layer 2 terminal endpoint identifier (TEI). |
|
| Step 13 | (Optional) Configures the ISDN port to send SETUP messages on the static TEI. Note A static TEI must be configured in order for this command to be effective. |
|
| Step 14 | ||
| Step 15 | (Optional) Resets the specified interface. The interface needs to be reset if the static TEI number has been configured in Step 15. |
|
| Step 16 | ||
| Step 17 | Saves the configuration changes to the startup-config file so that they are not lost during resets, power cycles, or power outages. |
When you finish configuring one interface, you must repeat Step 1 through Step 17, for the other BRI VIC interface.
|
Note To complete voice configuration, you must set up your voice ports and dial peers. Refer to the "Configuring Voice Ports" chapter in the Cisco IOS Voice, Video, and Fax Configuration Guide. |
To configure basic ISDN PRI interface parameters, follow these steps, beginning in global configuration mode (see the "Configuring ISDN PRI Interfaces" section):
| Command | Purpose | |
|---|---|---|
| Step 1 | Specifies an ISDN switch type. See Table 6-14 for a list of ISDN switch types. Note The only switch types currently supported for an NT interface are basic-net3 and basic-qsig. |
|
| Step 2 | Specifies the T1/E1 interface to configure. This example configures a T1 interface in slot 1 and port 0. |
|
| Step 3 | MRP(config-controller)# framing {esf | sf | crc4 | no-crc4} [australia] |
|
| Step 4 | Specifies the line-encoding method to match that of your telephone company service provider. |
|
| Step 5 | Configures the ISDN PRI group. The range argument specifies a range of time slots that make up the PRI group. The range is from 1 to 24 (for T1) or from 1 to 31 (for E1). |
|
| Step 6 | Exits controller configuration mode and returns to global configuration mode. |
|
| Step 7 | MRP(config)# tdm clock T1 1/0 both import T1 1/1 {internal | line} |
Specifies which end of the circuit provides the clock to the time-division multiplexing (TDM) switch. If internal is selected, the onboard clock provides the clocking. If line is selected, the other end of the circuit (the PSTN) provides the clocking. Note When configuring the interface payload type for T1 PRI, as shown in the command example, you should use the keyword both (for both voice and data) to ensure that sufficient processing power is available to carry in-band signaling. |
| Step 8 | Enters interface configuration mode and specifies the first ISDN line. (The ISDN serial interface is the D channel.) This example configures a T1 interface in slot 1, port 0, and channel 0. |
|
| Step 9 | Enables incoming ISDN voice calls. The modem keyword specifies that incoming voice calls will be handled as modems. Note You must use the modem keyword to enable voice calls. The modem keyword represents bearer capabilities of speech. |
|
| Step 10 | Exits to global configuration mode. Repeat Step 4 through Step 10 if your MRP has more than one T1 interface that you need to configure. |
|
| Step 11 | ||
| Step 12 | Saves the configuration changes to the startup-config file so that they are not lost during resets, power cycles, or power outages. |
You can check the validity of your voice port configuration by performing the following tasks:
To configure a Frame Relay main interface and a subinterface so that voice and data traffic can be successfully transported, enter the following commands (see the "Configuring VoIP for Frame Relay" section):
In this configuration example, the main interface is configured as follows:
The subinterface is configured as follows:
This section explains how to configure quality of service (see the "Configuring Quality of Service" section).
To configure IP precedence on VoIP dial peers, enter the following commands (this example sets the IP precedence to 5):
To configure RSVP, you must first enable RSVP. To enable RSVP for IP on an interface, use the following interface configuration command (see the "Configuring RSVP for Voice" section):
The following example enables RSVP and sets the maximum bandwidth to 100 kbps and the maximum bandwidth per single request to 32 kbps (the example assumes that both VoIP dial peers are configured):
After enabling RSVP, you must also use the req-qos dial-peer configuration command to request an RSVP session on each VoIP dial peer. Otherwise, no bandwidth is reserved for voice traffic.
|
Note You can use the ip rtp reserve command instead of configuring RSVP. If you configure RSVP, this command is not required. |
To configure multilink Point-to-Point Protocol (PPP) and interleaving on a configured and operational interface or virtual interface template, follow these steps (see the "Configuring Multilink PPP with Interleaving" section):
The following example defines a virtual interface template that enables multilink PPP with interleaving and a maximum real-time traffic delay of 20 milliseconds and then applies that virtual template to the multilink PPP bundle:
You must enable compression on both ends of a serial connection. To enable RTP header compression, use the following interface configuration command (see the "Configuring RTP Header Compression" section:
If you include the passive keyword, the software compresses outgoing RTP packets only if incoming RTP packets on the same interface are compressed. If you use the command without the passive keyword, the software compresses all RTP traffic.
By default, the software supports a total of 16 RTP header compression connections on an interface. To specify a different number of RTP header compression connections, use the following interface configuration command:
|
Note When you enter the show running-config command, the format of the ip rtp header-compression command will change to ip rtp header-compression iphc-format. |
This section describes the timing scenarios that can occur when different combinations of WICs and VICs are used on the two slots of an MRP (see the "TDM Clocking Scenarios" section).
Each of the topologies described in Table 6-25 is illustrated in the examples that follow.
In this topology, shown in Figure 7-11, the digital T1 port 0/0 is the clock source for the connected device. The phase locked loop (PLL) chip generates the clock internally and drives the clocking on the T1 line.
The following configuration sets up this clocking method:
|
Note Generally, this method is useful only when connecting to a PBX, key system, or channel bank. A Cisco VoIP gateway rarely provides clocking to the central office (CO), because CO clocking provides a higher Stratum level. |
In this topology, shown in Figure 7-12, the digital T1 port 0/0 receives clocking from the connected device (CO). The clocking of the PLL chip is driven by the clock reference on the receive (Rx) side of the T1 connection.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-13, there are two reference clocks. Both T1 port 0/0 and T1 port 0/1 receive clocking from the CO.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-14, T1 port 0/0 receives clocking for the PLL chip from the CO and puts the T1 port 0/1 connected to the CO into looped-time mode. This is usually the best method because the CO provides an excellent clock source.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-15, the digital T1 port 0/0 receives clocking for the PLL chip from the CO and uses this clock as a reference to clock T1 port 0/1. If T1 port 0/0 fails, the PLL chip internally generates the clock reference to drive T1 port 0/1.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-16, an MRP generates the clock for the PLL chip and provides clocking to both T1 port 0/0, which is connected to a CO, and to T1 port 0/1, which is connected to a PBX.
The following configuration sets up this clocking method:
Each of the topologies described in Table 6-26 is illustrated in the examples that follow.
In this topology, shown in Figure 7-17, there are two reference clocks. Both T1 port 0/0 and T1 port 1/0 receive clocking from the CO.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-18, T1 port 0/0 receives clocking for the PLL chip from the CO and puts the T1 port 1/0, which is connected to the CO, into looped-time mode. This is usually the best method because the CO provides an excellent clock source.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-19, the digital T1 port 0/0 receives clocking for the PLL chip from the CO and uses this clock as a reference to clock T1 port 1/0. If T1 port 0/0 fails, the PLL chip internally generates the clock reference to drive T1 port 1/0.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-20, an MRP generates the clock for the PLL chip and provides clocking both to T1 port 0/0, which is connected to a CO, and to T1 port 1/0, which is connected to a PBX.
The following configuration sets up this clocking method:
Each of the topologies described in Table 6-27 is illustrated in the examples that follow.
In this topology, shown in Figure 7-21, there are two reference clocks. Both T1 port 0/0 and T1 port 0/1 receive clocking from the CO.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-22, T1 port 0/0 receives clocking for the PLL chip from the CO and puts the T1 port 0/1, which is connected to the CO, into looped-time mode. This is usually the best method because the CO provides an excellent clock source.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-23, the digital T1 port 0/0 receives clocking for the PLL chip from the CO and uses this clock as a reference to clock T1 port 0/1. If T1 port 0/0 fails, the PLL chip internally generates the clock reference to drive T1 port 0/1.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-24, an MRP generates the clock for the PLL chip and provides clocking both to T1 port 0/0, which is connected to a CO, and to T1 port 0/1, which is connected to a PBX.
The following configuration sets up this clocking method:
Each of the topologies listed in Table 6-28 shows the timing that can result when slot 0 is a T1 interface and slot 1 is a WIC interface.
In this topology, shown in Figure 7-25, there are two reference clocks. Both T1 port 0/0 and T1 port 0/1 receive clocking from the CO.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-26, T1 port 0/0 receives clocking for the PLL chip from the CO and puts the T1 port 0/1, which is connected to the CO, into looped-time mode. This is usually the best method because the CO provides an excellent clock source.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-27, the digital T1 port 0/0 receives clocking for the PLL chip from the CO and uses this clock as a reference to clock T1 port 0/1. If T1 port 0/0 fails, the PLL chip internally generates the clock reference to drive T1 port 0/1.
The following configuration sets up this clocking method:
In this topology, shown in Figure 7-28, an MRP generates the clocking for the PLL chip and provides clocking both to T1 port 0/0, which is connected to a CO, and to T1 port 0/1, which is connected to a PBX.
The following configuration sets up this clocking method:
To verify that the controller is up and running and that no alarms have been reported, enter the show controller t1 command and specify the port number.
After configuring the new interface, you can perform the following tests to verify that the new interface is operating correctly:
|
Note If an interface is down and you configured it as up, or if the displays indicate that the hardware is not functioning properly, make sure that the new interface is properly connected and configured. |
Posted: Sun Jan 19 13:31:40 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
