cc/td/doc/product/access/sc/rel7/soln/voip13
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Configuring Media Gateways for the SS7 Interconnect for Voice Gateways Solution

Determining Software and Hardware Requirements

Installing Media Gateways

Installing the Cisco AS5300 Universal Access Server

Installing the Cisco AS5350 Universal Gateway

Installing the Cisco AS5400 Universal Gateway

Installing the Cisco AS5800 Universal Access Server

Installing the Cisco AS5850 Universal Gateway

Configuring Media Gateways

Setting the ISDN Switch Type

Configuring the Cisco AS5300 and Cisco AS5850 for B-Channel Negotiation

Configuring Redundant Link Manager

Completing VoIP Configuration

Configuring Number Translation

Configuring the Digit Strip

Configuring Dial Peer Call Legs Using Digit Translation Rules

Verifying the Configuration

Sample Output for the Cisco SS7 Interconnect for Voice Gateways Solution

Configuring Media Gateways for the SS7 Interconnect for Voice Gateways Solution

This chapter describes how to configure the access servers used by the Cisco SS7 Interconnect for Voice Gateways Solution. It includes the following sections:

• Determining Software and Hardware Requirements

• Installing Media Gateways

• Configuring Media Gateways

• Sample Output for the Cisco SS7 Interconnect for Voice Gateways Solution

Determining Software and Hardware Requirements

Software and hardware requirements vary depending on the version of the Cisco SS7 Interconnect for Voice Gateways Solution installed in your network. To view the latest requirements for your solution, see the following online documentation:

•Release Notes for Cisco SS7 Interconnect for Voice Gateways Release 1.3
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/soln/voip13/voip_rn.htm

Installing Media Gateways

This document assumes that all required hardware, voice feature cards, and network modules have been installed, and that each access server or router has been connected to a working IP network. If necessary, refer to the following sections:

• Installing the Cisco AS5300 Universal Access Server

• Installing the Cisco AS5350 Universal Gateway

• Installing the Cisco AS5400 Universal Gateway

• Installing the Cisco AS5800 Universal Access Server

• Installing the Cisco AS5850 Universal Gateway

Installing the Cisco AS5300 Universal Access Server

For instructions on installing a Cisco AS5300 and connecting it to a network, see the following documents:

•Cisco AS5300 Quick Start Guide (with Fast Step)

•Cisco AS5300 Chassis Installation Guide

•Cisco AS5300 Module Installation Guide

•Cisco AS5300 Software Configuration Guide

The entire documentation set for the Cisco AS5300 universal access server is available at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/index.htm

Installing the Cisco AS5350 Universal Gateway

For instructions on installing a Cisco AS5350 and connecting it to a network, see the following documents:

•Cisco AS5350 Universal Gateway Chassis Installation Guide

•Cisco AS5350 Universal Gateway Card Installation Guide

•Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide

The entire documentation set for the Cisco AS5350 universal gateway is available at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/index.htm

Installing the Cisco AS5400 Universal Gateway

For instructions on installing a Cisco AS5400 and connecting it to a network, see the following documents:

•Cisco AS5400 Universal Access Gateway Read Me First

•Cisco AS5400 Chassis Installation Guide

•Cisco AS5400 Universal Gateway Card Installation Guide

•Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide

The entire documentation set for the Cisco AS5400 universal gateway is available at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5400/index.htm

Installing the Cisco AS5800 Universal Access Server

For instructions on installing a Cisco AS5800 and connecting it to a network, see the following documents:

•Read Me First—Cisco AS5800 Universal Access Server

•Cisco AS5800 OAM&P Guide

•Cisco AS5800 Universal Access Server Hardware Installation Guide

•Cisco AS5800 Universal Access Server Dial Shelf Guide

The entire documentation set for the Cisco AS5800 universal access server is available at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/index.htm

Installing the Cisco AS5850 Universal Gateway

For instructions on installing a Cisco AS5850 and connecting it to a network, see the following documents:

•Cisco AS5850 Hardware Installation Guide

•Cisco AS5850 Universal Gateway Guide

•Cisco AS5850 Universal Gateway Commissioning Guidelines

•Cisco AS5850 Universal Gateway Operations, Administration, Maintenance, and Provisioning Guide

Note For detailed instructions on configuring your Cisco AS5850 to operate in handover-split mode, refer to RSC Handover Redundancy at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/handred.htm

The entire documentation set for the Cisco AS5850 universal gateway is available at the following location:

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5850/index.htm

Configuring Media Gateways

The process for configuring voice gateways includes the following major steps:

• Setting the ISDN Switch Type

• Configuring the Cisco AS5300 and Cisco AS5850 for B-Channel Negotiation

• Configuring Redundant Link Manager

• Completing VoIP Configuration

• Configuring Number Translation

• Configuring the Digit Strip

• Configuring Dial Peer Call Legs Using Digit Translation Rules

Setting the ISDN Switch Type

To communicate with the Cisco SC2200, you must set the appropriate ISDN switch type on the media gateway. To set the ISDN switch type, perform the following steps:

Step 1 Enter global configuration mode:

Router# configure terminal Router(config)#

Step 2 Set the ISDN switch type to primary-ni:

Router# isdn switch-type primary-ni

For more information about setting ISDN switch types, refer to National ISDN Switch Types for Basic Rate and Primary Rate Interfaces at the following location;
http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113t/113t_3/natisdn.htm

Configuring the Cisco AS5300 and Cisco AS5850 for B-Channel Negotiation

To improve call success rates, the Cisco AS5300 and Cisco AS5850 must be configured to negotiate ISDN B-channels with the Cisco Media Gateway Controller (MGC). This negotiation enables the MGC to setup the call on a different channel if the channel requested by the media gateway is unavailable.

To enable ISDN B-channel negotiation, perform the following steps:

Step 1 Enter global configuration mode:

Router# configure terminal Router(config)#

Step 2 To configure the appropriate interface, enter the following command:

Router(config)# interface {s0:23 | s0:15}

Note Use interface s0:23 in T1 networks; use interface s0:15 in E1 networks.

Step 3 Enter the commands to enable B-channel negotiation:

Router(config-if)# isdn negotiate-b Router(config-if)# isdn negotiate-bchan

Configuring Redundant Link Manager

Redundant Link Manager (RLM) provides virtual link management over multiple IP networks so that the Q.931 signaling protocol and other proprietary protocols can be transported on top of redundant links between the Cisco SC2200 and the media gateways. RLM opens, maintains, and closes multiple links, manages buffers of queued signaling messages, and monitors for both link failover and failover of the Cisco SC2200. Additionally, RLM allows these multiple, redundant paths to be treated as one path by upper layers.

Note Because the Cisco SC2200 can support only two RLM links to a NFAS group, you can assign only one interface to each route-switch-controller (RSC) card in a Cisco AS5850 operating in handover-split mode. This prevents link redundancy between the individual RSCs and the Cisco SC2200.

Q.921 is used to encapsulate the Q.931 messages, which guarantees the in-sequence transmission of Extended Q.931 messages and provides for retransmission when necessary. UDP provides for the connectionless transfer of signaling messages across the subnetworks (LAN or WAN) that connect the media gateways to the Cisco SC2200.

Because RLM handles all signaling between the Cisco SC2200 and the media gateway, D channels can be used to carry bearer traffic. This is accomplished through the use of Non-Facility Associated Signaling (NFAS). NFAS allows a single D channel to control multiple PRI interfaces. That single D channel is then mapped to the RLM group.

Figure 2-1 shows the mapping that occurs between a VoIP or POTS dial peer and the RLM group.

Figure 2-1 Call Flow from Dial Peer to RLM Group

Note This section includes basic instructions for configuring Redundant Link Manager in a Cisco SS7 Interconnect for Voice Gateways Solution. For detailed instructions on planning for RLM implementation, refer to the following online documentation:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rlm_123.
h tm

Note To configure RLM on a handover-split-mode Cisco AS5850, see the "Configuring RLM on a Handover-Split Mode Cisco AS5850" section.

Assigning RLM Groups

Step 1 Assign an RLM group and link weights. This determines where the RLM signaling comes from.

Caution rlm group 0 must match with the NFAS group (nfas_group) that is defined in the D-channel. The RLM port number is arbitrary and is determined by the customer. Refer to Chapter 5, "Provisioning SS7-Based POPs," in the Cisco Wholesale Voice Design and Implementation Guide, at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/soln/wv_rel1/wvpg/index.htm
rlm group 0 protocol rlm port 3002 <---arbitrary server columbia link address 10.40.0.10 source FastEthernet0/0 weight 2 link address 10.41.0.10 source FastEthernet0/1 weight 1 server fairfield link address 10.40.0.11 source FastEthernet0/0 weight 2 link address 10.41.0.11 source FastEthernet0/1 weight 1

Assigning Multiple RLM Groups

Voice gateways in this solution can support up to eight RLM groups per gateway. This capability enables you to spread trunks over multiple gateways. In order for the Cisco SC2200 to distinguish among the different RLM groups on each gateway, you must assign a unique UDP port number to each RLM group on a gateway.

Note Each controller supports 32 RLM connections — therefore, the Cisco SC2200 supports 256 total RLM connections.

Step 1 Configure the RLM groups as appropriate for your network.

interface Serial1/0/0:23 ip unnumbered Loopback0 dialer pool-member 1 isdn switch-type primary-ni isdn incoming-voice modem isdn calling-number 333444333 isdn rlm-group 1 no isdn send-status-enquiry isdn negotiate-bchan isdn bchan-number-order ascending

interface Serial1/0/3:23 ip unnumbered Loopback0 dialer pool-member 1 isdn switch-type primary-ni isdn incoming-voice modem isdn calling-number 333444333 isdn rlm-group 2 no isdn send-status-enquiry isdn negotiate-bchan isdn bchan-number-order ascending

Step 2 Assign link weights to the first RLM group.

rlm group 1 server fifi link address 10.4.8.10 source Loopback1 weight 90

Note The default UDP port for RLM groups is 3000. There is no need to change this for the first RLM group.

Step 3 Assign link weights and a unique UDP port to each remaining RLM group.

rlm group 2 protocol rlm port 3001 server fifi link address 10.4.8.10 source Loopback2 weight 90

Be sure to include the corresponding UDP ports when you configure RLM groups on the Cisco SC2200.

Configuring RLM on the Cisco AS5300, Cisco AS5350, Cisco AS5400, Cisco AS5800, and
Classic-Split Mode Cisco AS5850

To configure RLM on media gateways other than a Cisco AS5850 in handover-split mode, perform the following steps:

Step 1 To enter enable mode, enter the following commands:

Router> enable Password: password Router#

Step 2 To enter global configuration mode, enter the following command:

Router# configure terminal Router(config)#

Step 3 To specify the interface, enter the following command:

Router(config)# interface FastEthernet0

Step 4 To specify the RLM group that you want to configure, enter the following command:

Router(config-if)# rlm group 0 Router(config-rlm-group)#

Step 5 To specify the device name of the Cisco SC2200, enter the following command:

Router(config-rlm-group)# server mgc1

Step 6 To specify the link addresses and their weighting preferences, enter the following commands:

Router(config-rlm-group-sc)# link address 10.1.4.1 source FastEthernet0 weight1 Router(config-rlm-group-sc)# link address 10.1.4.2 source FastEthernet0 weight2

Note Links with higher weighting numbers are given higher priority to become active links. If all entries have the same weighting, all links will be treated equally.


Step 7 Repeat Step 5 and Step 6 for the second Cisco SC2200:

Router(config-rlm-group-sc)# server mgc2 Router(config-rlm-group-sc)# link address 10.1.5.1 source FastEthernet0 weight1 Router(config-rlm-group-sc)# link address 10.1.5.2 source FastEthernet0 weight2

Step 8 To enable EIGRP, enter the following command:

Router(config-rlm-group-sc)# router eigrp 100 Router(config-router)#

Step 9 Assign controller interfaces to nfas_group 0.

Router(config-controller)# pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 0 Router(config-controller)# pri-group timeslots 1-24 nfas_d none nfas_int 1 nfas_group 0 Router(config-controller)# pri-group timeslots 1-24 nfas_d none nfas_int 2 nfas_group 0 Router(config-controller)# pri-group timeslots 1-24 nfas_d none nfas_int 27 nfas_group 0

Note For detailed instructions on configuring NFAS groups, refer to the following online documentation:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios113ed/113t/113t_3/nfas.htm

Configuring RLM on a Handover-Split Mode Cisco AS5850

A Cisco AS5850 configured for handover-split mode provides greater redundancy and system availability by enabling each RSC to automatically take control of call processing if the other RSC fails. In normal operation, the RSC in slot 6 controls slots 0 through 5, and the RSC in slot 7 controls slots 8 through 13. When an RSC failure occurs in handover-split mode, the remaining RSC takes over control of all slots, cards, and call processing. The failed RSC will remain in a standby state until the active RSC is instructed to relinquish control of the slots usually controlled by the standby RSC.

Because of the different architecture used by the Cisco AS5850, RLM requires a different configuration to take advantage of handover-split mode. For each RSC, you must configure two RLM groups: an active RLM group to handle calls on the slots controlled by that RSC, and a standby RLM group to handle calls on the other slots if the other RSC fails. Table 2-1 shows the status of these four RLM groups during normal operation and when an RSC goes out of service.

Table 2-1 RLM Status Under Normal and Failure Conditions

Condition
RLM Group 0
RSC 0, Slot 0 to 5
RLM Group 1
RSC 0, Slot 8 to 13
RLM Group 2
RSC 1, Slot 8 to 13
RLM Group 3
RSC 1, Slot 0 to 5

Normal operation

Active

Standby

Active

Standby

RSC 0 fails

Standby

Standby

Active

Active

RSC 1 fails

Active

Active

Standby

Standby


Handover-Split Mode Limitations

Cisco AS5850s configured for handover-split mode operate under the following limitations:

•Each Cisco AS5850 can support 2 CT3 trunks. Cisco AS5850s configured for classic-split mode can support up to 4 CT3 trunks each.

•After an RSC fails, it takes up to 2 minutes for the active RSC to take over for the failed RSC. During this time, calls handled by the failed RSC are dropped, and new calls are not accepted. Calls handled by the active RSC are not affected by a switchover.

For detailed information on classic-split and handover-split modes, refer to the following online documentation:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122x/122xb/122xb_2/handred.htm

Configuring RLM Groups Associated with RSC 0

To configure RLM groups for RSC 0 on a handover-split mode Cisco AS5850, perform the following steps:

Step 1 Enter enable mode.

Router> enable Password: password Router#

Step 2 Enter global configuration mode.

Router# configure terminal Router(config)#

Step 3 Specify the interface to be used by RSC 0.

Router(config)# interface GigabitEthernet 6/0

Step 4 Specify the RLM group that you want to configure.

Router(config-if)# rlm group 0 Router(config-rlm-group)#

Step 5 Specify the device name, link addresses, and weighting preferences for both Cisco SC2200s.

Router(config-rlm-group)# server mgc1 Router(config-rlm-group-sc)# link address 10.1.4.1 source GigabitEthernet0 weight1 Router(config-rlm-group-sc)# server mgc2 Router(config-rlm-group-sc)# link address 10.1.5.1 source GigabitEthernet0 weight2

Note Links with higher weighting numbers are given higher priority to become active links. If all entries have the same weighting, all links will be treated equally.

Step 6 Repeat Step 4 and Step 5 for RLM group 1.

Step 7 Assign controller interfaces to nfas_group 0 and nfas_group 1. Controller interfaces assigned to slots 0 through 5 must be in one NFAS group. Controller interfaces assigned to slots 8 through 13 must be in the other NFAS group.

controller T1 2/0:1 framing esf pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 0 ! controller T1 2/0:2 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 1 nfas_group 0 ! controller T1 2/0:3 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 2 nfas_group 0 ! controller T1 2/0:28 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 27 nfas_group 0 ! controller T1 10/0:1 framing esf pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 1 ! controller T1 10/0:2 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 1 nfas_group 1 ! controller T1 10/0:3 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 2 nfas_group 1 ! controller T1 10/0:28 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 27 nfas_group 1

Step 8 Assign signaling interfaces to RLM groups 0 and 1.

interface Serial2/0:1:23 isdn switch-type primary-ni isdn incoming-voice modem isdn rlm-group 0

interface Serial10/0:1:23 isdn switch-type primary-ni isdn incoming-voice modem isdn rlm-group 1

Step 9 Assign UDP port 3002 to RLM group 1.

rlm group 1  protocol rlm 3002

Note RLM group 0 uses 3000 as the default UDP port.

Step 10 Shutdown RLM group 1, which is assigned to the cards controlled by the other RSC.

rlm group 1 shutdown protocol rlm port 3002 server mgc1 link address 10.1.4.1 source GigabitEthernet6/0 weight 1

server mgc2 link address 10.1.5.1 source GigabitEthernet6/0 weight 2

Configuring RLM Groups Associated with RSC 1

To configure RLM groups for RSC 1 on a handover-split mode Cisco AS5850, perform the following steps:

Step 1 Enter enable mode.

Router> enable Password: password Router#

Step 2 Enter global configuration mode.

Router# configure terminal Router(config)#

Step 3 Specify the interface to be used by RSC 1.

Router(config)# interface GigabitEthernet 7/0

Step 4 Specify the RLM group that you want to configure.

Router(config-if)# rlm group 2 Router(config-rlm-group)#

Step 5 Specify the device name, link addresses, and weighting preferences for both Cisco SC2200s.

Router(config-rlm-group)# server mgc1 Router(config-rlm-group-sc)# link address 10.1.4.1 source GigabitEthernet0 weight1 Router(config-rlm-group-sc)# server mgc2 Router(config-rlm-group-sc)# link address 10.1.5.1 source GigabitEthernet0 weight2

Step 6 Repeat Step 4 and Step 5 for RLM group 3.

Step 7 Assign controller interfaces to nfas_group 3 and nfas_group 2. Controller interfaces assigned to slots 0 through 5 must be in one NFAS group. Controller interfaces assigned to slots 8 through 13 must be in the other NFAS group.

controller T1 2/0:1 framing esf pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 3 ! controller T1 2/0:2 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 1 nfas_group 3 ! controller T1 2/0:3 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 2 nfas_group 3 ! controller T1 2/0:28 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 27 nfas_group 3 ! controller T1 10/0:1 framing esf pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 2 ! controller T1 10/0:2 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 1 nfas_group 2 ! controller T1 10/0:3 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 2 nfas_group 2 ! controller T1 10/0:28 framing esf pri-group timeslots 1-24 nfas_d none nfas_int 27 nfas_group 2

Step 8 Assign signaling interfaces to the RLM groups 3 and 2.

interface Serial2/0:1:23 isdn switch-type primary-ni isdn incoming-voice modem isdn rlm-group 3

interface Serial10/0:1:23 isdn switch-type primary-ni isdn incoming-voice modem isdn rlm-group 2

Step 9 Assign UDP port 3002 to RLM group 2.

rlm group 2  protocol rlm port 3002  no shutdown

Step 10 Assign UDP port 3000 and then shutdown RLM group 3.

rlm group 3  protocol rlm 3000  shutdown

Verifying RLM Configuration

To verify RLM configuration, perform the following steps:

Note The output included in the steps that follow is for reference purposes only. Your media gateways will produce different results as appropriate for your network and configuration.

Step 1 To verify the RLM configuration, enter the following command and specify the group number:

Router# show rlm group 0 status

RLM Group 0 Status User/Port: RLM_MGR/3000 ISDN3001 Link State: Up Last Link Status Reported: Up Next tx TID: 1 Last rx TID: 0 Server Link Group[mgc1]: link [10.1.1.1(Ethernet0), 10.1.4.1] = socket[active] link [10.1.1.2(FastEthernet0), 10.1.4.2] = socket[standby] Server Link Group[mgc2]: link [10.1.1.1(Ethernet0), 10.1.5.1] = socket[opening] link [10.1.1.2(FastEthernet0), 10.1.5.2] = socket[opening]

The link state must be up, and no errors should be reported.

Step 2 To view layer status information, enter the following command:

Router# show isdn status

Global ISDN Switchtype = primary-ni ISDN Serial1:23 interface dsl 0, interface ISDN Switchtype = primary-ni :Primary D channel of nfas group 0 Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 0 CCBs = 0 ISDN Serial2:23 interface dsl 1, interface ISDN Switchtype = primary-ni :Group member of nfas group 0 Layer 1 & 2 Status Not Applicable Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 1 CCBs = 0 Total Allocated ISDN CCBs = 0

For Serial 0:23 (the first half of the message):

•Layer 1 Status should be ACTIVE.

•Layer 2 Status should be MULTIPLE_FRAME_ESTABLISHED. (It might take several seconds for Layer 2 status to appear.)

•Layer 3 Status should be 0 Active Layer 3 Calls.

The second half of the message displays information for Serial 1:23.

Tip If the Layer 1 Status is Deactivated, it indicates a problem at the physical layer. Make sure that the cable connection is not loose or disconnected.

A Layer 2 error indicates that the Cisco MGW cannot communicate with the telco; there is a problem at the data link layer. There may be a problem with your telco, or the framing and line code types you entered may not match that of your telco.

Completing VoIP Configuration

This section lists the steps to configure the voice gateways in your solution to use Voice over IP (VoIP). Perform the following steps to complete this configuration:

Step 1 Establish a working IP network. For more information about configuring IP, refer to Cisco IOS IP and IP Routing Configuration Guide, Release 12.1 at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ip_c/index.htm

Step 2 Complete your company's dial plan and establish a working telephony network. For more information, see the appropriate documentation for your gateway:

•Voice over IP for the Cisco AS5300
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/voip5300/voip53_1.htm4934vcip.htm

•Cisco AS5350 and Cisco AS5400 Universal Gateway Software Configuration Guide
http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5350/53swcg/index.htm

Step 3 Integrate your dial plan and telephony network into your existing IP network topology. Merging your IP and telephony networks depends on your particular IP and telephony network topology. In general, Cisco suggests the following:

•Using canonical numbers wherever possible. (It is important to avoid situations where numbering systems are significantly different on different routers or access servers in your network.)

•Making routing and dialing transparent to the user—for example, avoid secondary dial tones from secondary switches, where possible.

•Contact your PBX vendor for instructions about how to reconfigure the appropriate PBX interfaces.

Step 4 Depending on the topology of your network or the resources used in your network, you might need to perform the following additional tasks:

•Distinguishing voice and modem calls on the media gateway

•Optimizing dial peer and network interface configurations

•Configuring IP precedence for dial peers

•Configuring RSVP for dial peers

•Configuring codec and VAD for dial peers

•Configuring Voice over IP for your H.323 clients

Note For further information about configuring dial peers, refer to Dial Peer Enhancements at the following location:.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121limit/121x/121xm/121xm_5/ftdpeer.htm

Cisco SS7 Interconnect for Voice Gateways Solution also offers VFC management features that enable you to easily upgrade and manage the system software stored in VFC Flash memory. Depending on your configuration, you might need to perform the following tasks to manage VCWare or DSPWare:

•Downloading VCWare

•Copying Flash files to the VFC

•Downloading VCWare to the VFC from the media gateway motherboard

•Downloading VCWare to the VFC from a TFTP server

•Unbundling VCWare

•Adding files to the default file list

•Adding codecs to the capability list

•Deleting files from VFC Flash memory

•Erasing the VFC Flash memory

Configuring Number Translation

Number translation is used in dial-peer configuration mode to match on a number type for a dial peer call leg.

To configure number translation using the numbering-type command in dial-peer configuration mode, enter the following commands in global configuration mode:

Command
Purpose
Example

dial-peer voice tag [voip | pots]

Enters the dial-peer configuration mode to configure a VoIP or POTs peer.

Media-Gateway (config) #
dial-peer voice 100 pots

numbering-type type of number

Specifies number type. Number types are:

•International

•Abbreviated

•National

•Network

•Reserved

•Subscriber

•Unknown

Media-Gateway (config-dial-peer) #
numbering-type international

Configuring the Digit Strip

When a called number is received and matched to a POTS dial peer, the matched digits are stripped and the remaining digits are forwarded to the voice interface. The Cisco SS7 Interconnect for Voice Gateways Solution implements a new command called the digit strip option to make this default behavior an option. The digit strip option is enabled by default.

To disable digit strip for a dial peer, enter the following commands in global configuration mode:

Command
Purpose
Example

dial-peer voice tag [pots]

Enters the dial-peer configuration mode to configure a POTs peer.

Note In this example, the dialed number is 525-1234 and the dial string matches dial-peer tag 100. The destination-pattern is 525..., strip match yields 1234, prefix 521 yields 521-1234.

Media-Gateway (config) #dial-peer voice 100 pots Media-Gateway (config-dial-peer)
#destination-pattern 525... Media-Gateway (config-dial-peer)
#direct-inward dial Media-Gateway (config-dial-peer)
#no digit strip Media-Gateway (config-dial-peer)
#port0:D

no digit strip

Disables digit strip.

 


Configuring Dial Peer Call Legs Using Digit Translation Rules

A dial peer defines the characteristics associated with a call leg. Dial peers are used to apply attributes to call legs and to identify call origin and destination. Attributes applied to a call leg include QoS, codec, VAD, and fax rate. A call leg is a discrete segment of a call connection that lies between two points in the connection. All of the call legs for a particular connection have the same connection ID.

There are two different kinds of dial peers:

•POTS—POTS dial peers describe the line characteristics usually associated with a traditional telephony network. POTS dial peers point to a particular voice port on a network device. On the media gateway, POTS dial peers point to a specific voice port on the media gateway through which voice traffic will travel to the rest of the voice network.

•VoIP—VoIP dial peers describe the line characteristics usually associated with a packet network connection (in the case of VoIP, this is an IP network). VoIP peers define the line characteristics between VoIP devices—the routers and access servers carrying voice traffic in this voice network.

A POTS dial peer points to a voice-port on the router, while the destination of a VoIP dial peer points to the destination IP address of the voice-router that terminates the call.

Complete the following procedures to configure call legs using the translation-rule command:

Tip You should configure your translation rules before you apply rules to your dial-peer call legs.

Step 1 To enter the translation-rule configuration mode and specify a rule, enter the following commands in global configuration mode:

Command
Purpose
Example

translation-rule translation-tag

Defines a translation-rule tag number and enter translation-rule configuration mode. All subsequent commands that you enter in this mode before you exit will apply to this translation-rule tag.

Media-Gateway (config) #translation-rule 5

rule precedence input-searched pattern substituted-pattern match-type substituted-type

Specifies translation rules. This command can be entered n times and is applied to translation-rule defined in Step 1.

Media-Gateway (config-translate) #rule 1 213% 510 national international


Note Applying translation rules to more than one dial -peer call leg in your end-to-end call is not recommended.

Step 2 To apply a rule to an inbound POTS call leg, enter the following commands in global configuration mode:

Command
Purpose
Example

voice-port port

Specifies the voice port.

Media-Gateway (config) #voice-port 0:1

translate [called | calling] translation-tag

Specifies the translation tag for inbound called or calling number.

Media-Gateway (config-voiceport) #translate called 5

Step 3 To apply a rule to an outbound VoIP call leg, enter the following commands in global configuration mode:

Command
Purpose
Example

dial-peer voice tag voip

Enters the dial-peer configuration mode to configure a VoIP peer.

Media-Gateway (config) #dial-peer voice 100 voip

session target {ipv4:destination-address | dns:host-name}

Specifies a destination IP address for this dial peer.

Media-Gateway (config-dial-peer)
#session target ipv4:10.1.2.2

translate-outgoing calling translation-tag

Translates outbound calling number.

Media-Gateway (config-voiceport)
#translate-outgoing calling 5

Step 4 To apply a rule to a VoIP call that originates from an H.323 node, enter the following global command:

Command
Purpose
Example

voip-incoming translation-rule called translation-tag

Specifies the translation tag for the VoIP inbound call leg.

Media-Gateway (config) #voip-incoming translation-rule called 5

Step 5 To apply a translation rule to an outbound POTs call leg, enter the following commands in global configuration mode:

Command
Purpose
Example

dial-peer voice tag pots

Enters the dial-peer configuration mode to configure a POTs dial peer.

Media-Gateway (config) #dial-peer voice 100 pots

port port

Specifies the voice port.

Media-Gateway (config-dial-peer) #port 0:1

translate-outgoing [called | calling] translation-tag

Specifies the translation tag for inbound called or calling number.

Media-Gateway (config-dial-peer) #translate-outgoing called 5

Sample Configuration and Output for Voice-over-IP

Following is a sample output from a Cisco AS5300 set up for bearer channels for VoIP:

Step 1 Enter your host name:

hostname XXXXXX ! no logging buffered no logging console aaa new-model

Step 2 Enter your password:

! username voice password username lab password ! ! resource-pool disable ! ! ! ip subnet-zero no ip domain-lookup ip host carteret 10.15.12.134 10.15.12.150 ip host YauPon 10.15.12.135 10.15.12.151 ! mgcp package-capability trunk-package mgcp default-package trunk-package

Step 3 Enter isdn switch-type primary-ni (This is the first command you will enter once the router is up and running.)

isdn voice-call-failure 0 cns event-service server mta receive maximum-recipients 0 ! dial-control-mib max-size 1200 !

Step 4 Enter controller T1 0: (This is the controller configuration command.)

framing esf linecode b8zs cablelength short 133 pri-group timeslots 1-24 !

Step 5 Enter controller T1 1:

framing esf linecode b8zs cablelength short 133 pri-group timeslots 1-24 !

Step 6 Enter controller T1 2:

framing esf clock source line secondary 1 linecode b8zs cablelength short 133

Step 7 Enter pri-group timeslots 1-24 nfas_d primary nfas_int 2 nfas_group 0:

This command links the PRI bearer channels on the media gateway to the RLM group for D-channel communication to the signaling controller over IP. The nfas_group number represents one or more PRIs that are controlled by the same D-channel. The int number should be configured to match the T-1 controller number.

Some tips to remember when configuring are as follows:

•Multiple T1/E1s can be part of the same nfas group.

•Multiple NFAS groups within the same RLM group on the media gateway are not supported at this time.

•The nfas_int number should be unique and defines the D-channel.

•All PRIs have to be part of the one RLM group.


Step 8 Enter controller T1 3:

framing esf clock source line primary linecode b8zs cablelength short 133

Step 9 Enter pri-group timeslots 1-24 nfas_d none nfas_int 3 nfas_group 0.

The voice ports will be automatically configured as shown below. The voice-port is created as a result of pri group nfas command. Voice ports 2:D and 3:D will be used in nfas-group 0.

! ! voice-port 0:D ! voice-port 1:D ! voice-port 2:D ! voice-port 3:D

The dial peers shown below are classic examples of Cisco H.323 provisioning to reach call destination.


Step 10 Enter dial-peer voice 471 pots:

destination-pattern 471....... direct-inward-dial port 2:D prefix 471 !

Step 11 Enter dial-peer voice 4514101 pots:

destination-pattern 4514101... direct-inward-dial port 0:D prefix 4514101 !

Step 12 Enter dial-peer voice 4514102 pots:

destination-pattern 4514102... direct-inward-dial port 1:D prefix 4514102 !

Step 13 Enter dial-peer voice 4101 pots:

destination-pattern 4101... direct-inward-dial port 0:D prefix 4101 !

Step 14 Enter dial-peer voice 4102 pots:

destination-pattern 4102... direct-inward-dial port 1:D prefix 4102 !

Step 15 Enter dial-peer voice 271 voip:

destination-pattern 271....... session target ipv4:172.18.193.110 tech-prefix 271# ! num-exp 451#.......... .......... num-exp 451#....... ....... num-exp 471#.......... .......... ! gateway !

Step 16 Enter interface Loopback0:

ip address 10.15.14.233 255.255.255.252 no ip directed-broadcast h323-gateway voip interface h323-gateway voip id z3-gk1 ipaddr 10.15.14.197 1719 h323-gateway voip h323-id z3-5300-1 h323-gateway voip tech-prefix 451# h323-gateway voip tech-prefix 471# !

Step 17 Enter interface Ethernet0:

ip address 10.15.12.2 255.255.255.240 no ip directed-broadcast !

Step 18 Enter interface Serial1:23.


Step 19 Enter isdn rlm-group 0.

This command is created as a result of the RLM global configuration command that resides at the bottom of the configuration.


Step 20 Enter rlm group 0.

This command allows the SC to communicate with the Cisco Media Gateway for call signaling and bearer channel control over UDP ports 3000 for Q.921 keepalives and 3001 for Q931 call setup.

server name x link address 10.15.12.134 source Ethernet0 weight 5 link address 10.15.12.150 source FastEthernet0 weight 2 server name y link address 10.15.12.135 source Ethernet0 weight 5 link address 10.15.12.151 source FastEthernet0 weight 2 radius-server host 10.15.12.6 auth-port 1645 acct-port 1646 radius-server key tvtest

Radius configuration is used for authentication and accounting records.

Step 21 Enter ntp server 10.10.10.25.

Network Time Protocol (NTP) is recommended to synchronize all the components of the solution to the same time reference. This can be achieved with the router or another NTP device such as the master source.

Verifying the Configuration

To verify the configuration perform the following steps:

Step 1 Enter sh isdn nfas gr 0.

ISDN NFAS GROUP 0 ENTRIES:

The primary D is Serial2:23. The NFAS member is Serial3:23.

The example shown above indicates the primary D-channel interface and its associated members in the group. There are two total NFAS members.There are 48 total available B channels.

The primary D-channel is DSL 2 in the IN SERVICE state.

There is currently no backup D-channel configured.

The current active layer 2 DSL is 2.


Step 2 Enter sh isdn stat to show the status:

ISDN Serial2:23 interface rlm-group = 0 dsl 2, interface ISDN Switchtype = primary-ni : Primary D channel of nfas group 0 Layer 1 Status: ACTIVE Layer 2 Status: TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED I_Queue_Len 0, UI_Queue_Len 0 Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 2 CCBs = 0 The Free Channel Mask: 0x80FFFFFF ISDN Serial3:23 interface dsl 3, interface ISDN Switchtype = primary-ni : Group member of nfas group 0 Layer 1 Status: ACTIVE Layer 2 Status: Not Applicable Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 3 CCBs = 0

Step 3 Enter sh rlm gro 0.

The presence of two signaling controllers shown below, indicates redundancy in the case of failover. This step is optional.

RLM Group 0 Status User/Port: RLM_MGR/3000 ISDN/3001 RLM Version : 2 Link State: Up Last Link Status Reported: Up Next tx TID: 1 Last rx TID: 0 Server Link Group[carteret]: Last Reported Priority: HIGH link [10.15.12.2(Ethernet0), 10.15.12.134] = socket[standby] link [10.15.12.34(FastEthernet0), 10.15.12.150] = socket[standby] Server Link Group[yaupon]: Last Reported Priority: HIGH link [10.15.12.2(Ethernet0), 10.15.12.135] = socket[active] link [10.15.12.34(FastEthernet0), 10.15.12.151] = socket[standby]

This is the interface that call signaling will traverse.

RLM Group 0 Timer Values open_wait = 3s force-down = 30s recovery = 12s switch-link = 5s minimum-up = 60s retransmit = 1s keepalive = 1s

RLM Group 0 Statistics Link_up: last time occurred at Nov 18 10:57:43.992, total transition=59 avg=06:36:36.298, max=2d22h, min=00:00:00.000, latest=00:00:04.844 Link_down: last time occurred at Nov 18 10:57:10.992, total transition=28 avg=00:56:54.621, max=1d00h, min=00:00:00.000, latest=00:00:33.000 Link_recovered: last time occurred at Nov 18 10:56:58.992, success=25(49%), failure=26 avg=0.038s, max=0.224s, min=0.000s, latest=0.000s Link_switched: last time occurred at Nov 11 12:25:52.324, success=6(100%), failure=0 avg=0.000s, max=0.000s, min=0.000s, latest=0.000s Server_changed: last time occurred at Nov 18 10:56:54.148 for totally 29 times Server Link Group[carteret]: Open the link [10.15.12.2(Ethernet0), 10.15.12.134]: last time occurred at Nov 18 10:57:40.992, success=33(6%), failure=509-0 avg=43.634s, max=177.004s, min=0.000s, latest=0.000s Echo over link [10.15.12.2(Ethernet0), 10.15.12.134]: last time occurred at Nov 18 11:12:40.979, success=1355251(97%), failure=33527-0 avg=0.000s, max=0.964s, min=0.000s, latest=0.000s Open the link [10.15.12.34(FastEthernet0), 10.15.12.150]: last time occurred at Nov 18 10:57:40.992, success=33(6%), failure=509-0 avg=43.549s, max=177.004s, min=0.000s, latest=0.000s Echo over link [10.15.12.34(FastEthernet0), 10.15.12.150]: last time occurred at Nov 18 11:12:40.979, success=1378593(97%), failure=32887-0 avg=0.000s, max=0.960s, min=0.000s, latest=0.000s Server Link Group[yaupon]: Open the link [10.15.12.2(Ethernet0), 10.15.12.135]: last time occurred at Nov 18 10:57:40.992, success=35(1%), failure=2247-0 avg=61.347s, max=177.000s, min=0.000s, latest=0.004s Echo over link [10.15.12.2(Ethernet0), 10.15.12.135]: last time occurred at Nov 18 11:12:41.983, success=998740(87%), failure=139142-0 avg=0.000s, max=2.688s, min=0.000s, latest=0.004s Open the link [10.15.12.34(FastEthernet0), 10.15.12.151]: last time occurred at Nov 18 10:57:40.992, success=35(1%), failure=2247-0 avg=61.270s, max=177.000s, min=0.000s, latest=0.032s Echo over link [10.15.12.34(FastEthernet0), 10.15.12.151]: last time occurred at Nov 18 11:12:42.019, success=1059514(88%), failure=138872-0 avg=0.000s, max=2.688s, min=0.000s, latest=0.016s

Sample Output for the Cisco SS7 Interconnect for Voice Gateways Solution

The following sections contain sample output for a voice gateway that has been configured for the Cisco SS7 Interconnect for Voice Gateways Solution.

! version 12.1 no service pad service timestamps debug datetime msec localtime service timestamps log uptime no service password-encryption service internal ! hostname ! no logging console enable password ! username all spe 1/0 2/9 firmware location system:/ucode/mica_port_firmware ! ! resource-pool disable ! ! ! ! modem recovery action none ip subnet-zero no ip domain-lookup ip host holden 10.15.0.1 ! isdn switch-type primary-ni mta receive maximum-recipients 0 ! ! controller E1 0 framing NO-CRC4 clock source line primary pri-group timeslots 1-31 nfas_d primary nfas_int 0 nfas_group 0 ! controller E1 1 framing NO-CRC4 pri-group timeslots 1-31 nfas_d none nfas_int 1 nfas_group 0 ! controller E1 2 shutdown framing NO-CRC4 clock source line secondary 1 pri-group timeslots 1-31 nfas_d none nfas_int 2 nfas_group 0 ! controller E1 3 shutdown framing NO-CRC4 pri-group timeslots 1-31 nfas_d none nfas_int 3 nfas_group 0 ! ! ! ! interface Ethernet0 ip address 209.165.200.224 255.255.255.224 no ip directed-broadcast no ip route-cache no ip mroute-cache ! interface Serial0:15 no ip address ip helper-address 209.165.200.224 no ip directed-broadcast no ip route-cache isdn switch-type primary-ni isdn incoming-voice modem isdn rlm-group 1 no fair-queue no cdp enable ! interface FastEthernet0 ip address 209.165.200.224 255.255.255.224 no ip directed-broadcast no ip route-cache no ip mroute-cache duplex full ! interface Group-Async1 description "Async Incoming Call" no ip address no ip directed-broadcast no ip route-cache no ip mroute-cache async dynamic address async mode interactive no snmp trap link-status no peer default ip address no fair-queue group-range 1 120 ! interface Dialer0 no ip address no ip directed-broadcast no cdp enable ! router rip redistribute connected network 10.0.0.0 ! no ip classless no ip http server ! logging 10.15.0.130 ! dialer dnis group dnis1 number 9157181 dialer-list 1 protocol ip permit dialer-list 1 protocol ipx permit snmp-server engineID local 00000009020000D00604FB36 snmp-server community public RO snmp-server community RW snmp-server trap-source FastEthernet0 snmp-server system-shutdown snmp-server enable traps snmp snmp-server enable traps isdn call-information snmp-server enable traps isdn layer2 snmp-server enable traps hsrp snmp-server enable traps config snmp-server enable traps entity snmp-server enable traps envmon snmp-server enable traps bgp snmp-server enable traps rsvp snmp-server enable traps frame-relay snmp-server enable traps rtr snmp-server enable traps syslog snmp-server enable traps dlsw snmp-server enable traps dial snmp-server enable traps dsp card-status snmp-server enable traps voice poor-qov snmp-server host 10.15.0.130 public ! rlm version 2 ! rlm group 1 server xxxx link hostname xxx source Ethernet0 weight 1 ! line con 0 exec-timeout 0 0 transport input none line 1 120 logging synchronous level 7 modem InOut transport preferred lat pad telnet rlogin udptn v120 transport input all transport output pad telnet rlogin udptn v120 line aux 0 line vty 0 4 exec-timeout 0 0 password login ! ntp clock-period 17179771 ntp update-calendar ntp server 10.15.0.1 source FastEthernet0 end

hometocprevnextglossaryfeedbacksearchhelp

Posted: Thu Oct 14 10:34:52 PDT 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.