Configuring Media Gateways for the SS7 Interconnect for Access Servers Solution

Table Of Contents

Configuring Media Gateways for the SS7 Interconnect for Access Servers 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

Configuring Media Gateways

Preparing the Media Gateway for Configuration

Setting the ISDN Switch Type

Configuring Redundant Link Manager

Configuring Resource Pool Manager (RPM)

Verifying the Configuration

Sample Output for the Cisco SS7 Interconnect for Access Servers Solution

Configuring Call Hairpinning on the Cisco AS5800

Call Switching Using Dial Peers

Using Class of Restrictions

Call Hairpinning Configuration Tasks

Complete Dial Plan Setup for Hairpinning

Configuring Media Gateways for the SS7 Interconnect for Access Servers Solution

This chapter describes how to configure the access servers used by the Cisco SS7 Interconnect for Access Servers 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 Access Servers Solution

• Configuring Call Hairpinning on the Cisco AS5800

Determining Software and Hardware Requirements

Software and hardware requirements vary depending on the version of the Cisco SS7 Interconnect for Access Servers 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 Access Servers Release 2.2(B)
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel7/soln/das22/das_rn.htm

Installing Media Gateways

This document assumes that all required hardware has been installed, and that each access server has been configured for channelized T1 or E1 signaling and 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 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

Configuring Media Gateways

The process for configuring access servers includes the following major steps:

• Preparing the Media Gateway for Configuration

• Setting the ISDN Switch Type

• Configuring Redundant Link Manager

• Configuring Resource Pool Manager (RPM)

Preparing the Media Gateway for Configuration

Complete basic configuration for the media gateway. This includes, as a minimum, the following tasks:

•Configuring a host name and password for the media gateway

•Configuring the Ethernet 10BASE-T/100BASE-T interface of your media gateway so that it can be recognized as a device on the Ethernet LAN

•Configuring the media gateway interfaces for ISDN PRI lines

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 terminalRouter(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 Redundant Link Manager

The Cisco Redundant Link Manager (RLM) provides link management over multiple IP networks so that your Cisco SS7 solution can tolerate failure of a signaling controller or one of its components. A feature enhancement to RLM for the Cisco SS7 Interconnect for Access Servers Solution is redundancy at the link and signaling controller level (Version 2 below). When each RLM group has multiple signaling controllers associated with a Cisco MGW, a signaling controller priority and link priority are examined by the RLM client (RLM software on the Cisco MGW) during failover, ensuring improved control handling.

The RLM client supports both versions of RLM functionality:

•Multiple redundant links between a single signaling controller and the MGWs (Version 1)

•Multiple redundant links between multiple signaling controllers and the MGWs (Version 2)

Upon installation, the RLM version defaults to the latest version (Version 2). To configure a different RLM version, use the following global configuration command:
MGW# rlm version version id #

Note The RLM feature is backward compatible on the signaling controller, but only one version of the RLM client can run on a given Cisco MGW. Cisco recommends using Version 2.

For more detailed information, refer to Redundant Link Manager at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rlm_123.htm

To configure the RLM on the media gateway, perform the following steps:

Step 1 To enter enable mode, enter the following commands:
Router> enablePassword: passwordRouter#

Step 2 To enter global configuration mode, enter the following command:
Router# configure terminalRouter(config)#

Step 3 To specify the IP address of the first interface, enter the following commands:
Router(config)# interface ethernet0Router(config-if)# ip address 10.1.1.1 255.255.255.255

Note The IP addresses used in this book are for illustrative purposes only. Be sure to use IP addresses appropriate for your network.

Step 4 To specify the IP address of the second interface, enter the following commands:
Router(config-if)# interface ethernet0Router(config-if)# ip address 10.1.1.2 255.255.255.255

Step 5 To specify the RLM group (MGW) that you want to configure, enter the following command:
Router(config-if)# rlm group 1Router(config-rlm-group)#

Note The RLM group number must match the non-facility associated signaling (NFAS) group number.

Step 6 To specify the device name, enter the following command:
Router(config-rlm-group)# server r1-server

Step 7 To specify the link addresses and their weighting preference, enter the following commands:
Router(config-rlm-group-sc)# link address 10.1.4.1 source ethernet0 weight1 Router(config-rlm-group-sc)# link address 10.1.4.2 source ethernet0 weight2

Step 8 Repeat Step 6 and Step 7 for the second device:
Router(config-rlm-group-sc)# server r2-serverRouter(config-rlm-group-sc)# link address 10.1.5.1 source ethernet0 weight1Router(config-rlm-group-sc)# link address 10.1.5.2 source ethernet0 weight2

Step 9 To configure the enhanced interior gateway routing protocol (EIGRP), enter the following command:
Router(config-rlm-group-sc)# router eigrp 100Router(config-router)#

Step 10 To configure NFAS and specify the channels to be controlled by the primary NFAS D channel, 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 NFAS 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.

For more detailed information about configuring NFAS, refer to NFAS with D Channel Back Up at the following location:

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

Verifying RLM 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 StatusUser/Port: RLM_MGR/3000 ISDN3001Link State: Up Last Link Status Reported: UpNext tx TID: 1 Last rx TID: 0Server Link Group[r1-server]: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[r2-server]: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-niISDN Serial1:23 interfacedsl 0, interface ISDN Switchtype = primary-ni :Primary D channel of nfas group 0Layer 1 Status:ACTIVELayer 2 Status:TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 0 CCBs = 0ISDN Serial2:23 interfacedsl 1, interface ISDN Switchtype = primary-ni :Group member of nfas group 0Layer 1 & 2 Status Not ApplicableLayer 3 Status:0 Active Layer 3 Call(s)Activated dsl 1 CCBs = 0Total 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.

Configuring Resource Pool Manager (RPM)

Resource pool management allows service providers to provide wholesale (VPDN) dial service to corporate customers and retail dial service to end users from a single Cisco MGW or across multiple Cisco MGW stacks using one or more external Cisco Resource Pool Manager Servers (RPMS).

Cisco RPMS provides the following:

•Customer shared resource management.

•Advanced VPDN services for enterprise accounts and ISPs.

•Efficient use of resources to offer different oversubscription ratios and dial service agreements.

•Combination of retail and wholesale services on the same Cisco MGW.

Cisco RPMS offers three major functions:

•Resource management uses the call type and dialed number information service (DNIS) number to accept or reject the call based on the customer profile session limits associated with the DNIS number. If the call is accepted, the call is assigned to a media gateway resource.

•Dial services determines how the call is handled after it is answered. The call can be authenticated locally or sent to a home gateway through a VPDN tunnel (using the DNIS number or a domain name).

•Call discrimination prevents unapproved call types from accessing Cisco MGW resources. When a call is placed, the Cisco MGW sends the call type and (DNIS) to the Cisco RPMS. The Cisco RPMS compares this combination to the call discrimination table. If the call type/DNIS number combination appears in the table, it is rejected.

For detailed configuration, troubleshooting, and command reference information, see Resource Pool Management at the following location:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/rpm1205t.htm

To configure RPM on your Cisco Media Gateway, perform the following steps:

Step 1 To enable RPM, enter the following commands in configuration mode:
Router(config) # resource-pool {enable | disable}Router(config) # resource-pool call treatment profile {busy | no-answer}Router(config) # resource-pool call treatment resource {busy | channel-not-available}Router(config) # resource-pool aaa protocol local

Note With RPM disabled, the resource groups still take effect (that is, modem pooling is still not possible). Also, local AAA is authorization and accounting for RPM.

Step 2 To configure resource groups, enter the following commands:
Router(config) # resource-pool group resource WORDRouter(config) # range port s/s/p s/s/pRouter(config) # range limit limit

Note the following rules:

•Resource groups can apply to multiple customer profiles.

•You can separate the physical resources into groups.

•Do not mix MICA and Microcom modems.

Note For external Cisco RPMS environments, configure resource groups on the Cisco MGW before defining them on external RPMS servers. For standalone environments, configure resource groups before using them in customer profiles.

Tip If you have an RPMS, you do not need to define VPDN groups/profiles, customer profiles, or DNIS groups on the media gateway—you need to define only resource groups. Configure the remaining items by using the RPMS system.

Step 3 To configure DNIS groups, enter the following commands:
Router(config) # dialer dnis group {dnis-group-name}Router(config) # call-type cas {digital | speech}Router(config) # number number

Note the following:

•For default DNIS service, DNIS group configuration is not required.

•Each DNIS group or call type combination applies to one customer profile.

•Default DNIS groups can be used four times, one for each call type.

•You must statically configure CAS call types.

•You can use x, X, or . as a wildcard within each number.

Step 4 To configure discriminator profiles, which enable you to process calls differently based on call type and DNIS combination, enter the following commands:
Router(config) # resource-pool profile discriminator WORDRouter(config) # call-type {all | digital | speech | v110 | v120}Router(config) # dnis group {dnis-group-name | default}

Note You must specify both profiles.

Step 5 To configure service profiles, enter the following commands:
Router(config) # resource-pool profile service WORDRouter(config) # modem {min-speed {speed | any}} {max-speed {speed | any}} [modulation (k56flex | v22bis | v32bis | v32terbo | v34 | v90 | any}] [error-correction {mnp4 | lapm | any | none}] [compression {mnp5 | v42bis | any | none}]

Note the following:

•Services apply only to MICA modems (speech or V.110).

•Error-correction and compression are hidden options.

Step 6 To configure customer profiles, enter the following commands:
Router(config) # resource-pool profile customer WORDRouter(config) # dnis group {dnis-group-name | default}Router(config) # limit base-size {number | all}Router(config) # limit overflow-size {number | all}Router(config) # resource WORD {digital | speech | v110 | v120} [service WORD]

Note the following:

•Multiple resources of the same call type are used sequentially.

•The limits imposed are per customer (DNIS)—not per resource.

•A digital resource with a call type of "speech" allows for Data over Speech Bearer Service (DOSBS).

Step 7 To configure VPDN profiles, enter the following commands:
Router(config) # resource-pool profile customer WORDRouter(config) # vpdn profile profile-nameRouter(config) # resource-pool profile vpdn profile-nameRouter(config) # limit base-size {number | all}Router(config) # limit overflow-size {number | all}Router(config) # vpdn group group-name

Note A VPDN profile is required only if you want to impose limits on the VPDN tunnel that are separate from customer limits.

Step 8 To configure VPDN groups, enter the following commands:
Router(config) # vpdn-group group-nameRouter(config) # request dialin {l2f | l2tp} ip A.B.C.D {dnis dnis-group-name | domain Word}Router(config) # multilink {link | bundle} numberRouter(config) # loadsharing ip A.B.C.D [limit number]Router(config) # backup ip A.B.C.D [limit number] [priority number]

Note The dnis-group-name is required to authorize the VPDN-group with the RPM. Also, this data is optional on the AAA server.

RPM Configuration Examples

This section provides the following configuration examples:

• Sample Configuration for Resource Pool Management

• Sample Customer Profile Configuration for Data-over-Voice Bearer Service

• Sample VPDN Configuration

Sample Configuration for Resource Pool Management
resource-pool enableresource-pool call treatment resource busyresource-pool call treatment profile no-answer!resource-pool group resource isdn-portsrange limit 46resource-pool group resource MICA-modemsrange port 1/0 2/23!resource-pool profile customer ACMElimit base-size 30limit overflow-size 10resource isdn-ports digitalresource MICA-modems speech service golddnis group ACME_dnis_numbers

Note Replace resource isdn-ports digital above with resource isdn-ports speech to set up DOVBS.

!resource-pool profile customer DEFAULTlimit base-size 10resource MICA-modems speech service silverdnis group defaultresource-pool profile discriminator deny_DNIScall-type digitaldnis group bye-bye!resource-pool profile service goldmodem min-speed 33200 max-speed 56000 modulation v90resource-pool profile service silvermodem min-speed 19200 max-speed 33200 modulation v34!resource-pool aaa protocol local!dialer dnis group ACME_dnis_numbersnumber 301001dialer dnis group bye-byenumber 301005

•Digital calls to 301001 are associated with the customer ACME by using the resource group isdn-ports.

•Speech calls to 301001 are associated with the customer ACME by using the resource group mica-modems and allow for V.90 connections (anything less than V.90 are also allowed).

•Digital calls to 301005 are denied.

•All other speech calls to any other DNIS number are associated with the customer profile DEFAULT. Using the resource group mica-modems allows for V.34 connections (anything more than V.34 is not allowed; anything less than V.34 is allowed).

•All other digital calls to any other DNIS number are not associated with a customer profile and are, therefore, not allowed.

•In this case, the customer profile named DEFAULT serves as the default customer profile for speech calls only. If the solution uses an external RPMS server, this same configuration can be used for backup resource pooling if communication is lost between the Cisco MGW and the RPMS.

Sample Customer Profile Configuration for Data-over-Voice Bearer Service

To allow ISDN calls with a speech bearer capability to be directed to digital resources, make only the following change (highlighted in bold) to the configuration shown in the "Sample Configuration for Resource Pool Management" section:
resource-pool profile customer ACMElimit base-size 30limit overflow-size 10resource isdn-ports speechdnis group ACME_dnis_numbers

Note This change causes ISDN speech calls (in addition to ISDN digital calls) to be directed to the resource isdn-ports, thus providing DOVBS.

Sample VPDN Configuration

The following command allows you to use VPDN by setting up a VPDN profile and a VPDN group:
resource-pool profile vpdn ACME_VPDNlimit base-size 6limit overflow-size 0vpdn group outgoing-2!resource-pool profile customer ACMElimit base-size 30limit overflow-size 10resource isdn-ports digitalresource MICA-modems speech service golddnis group ACME_dnis_numbersvpdn profile ACME_VPDNvpdn enable!vpdn-group outgoing-2request dialin 12f ip 172.16.1.9 dnis ACME_dnis_numberslocal name HQ-NASmultilink bundle 1multilink link 2dnis ACME_dnis_numbers!dialer dnis group ACME_dnis_numbersnumber 301001

Note If the limits imposed by the VPDN profile are not required, do not configure the VPDN profile. Replace the command vpdn profile ACME_VPDN under the customer profile ACME with the command vpdn group outgoing-2.

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 = 0dsl 2, interface ISDN Switchtype = primary-ni : Primary D channel of nfas group 0Layer 1 Status:ACTIVELayer 2 Status:TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHEDI_Queue_Len 0, UI_Queue_Len 0Layer 3 Status:0 Active Layer 3 Call(s)Activated dsl 2 CCBs = 0The Free Channel Mask: 0x80FFFFFFISDN Serial3:23 interfacedsl 3, interface ISDN Switchtype = primary-ni : Group member of nfas group 0Layer 1 Status:ACTIVELayer 2 Status: Not ApplicableLayer 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 StatusUser/Port: RLM_MGR/3000 ISDN/3001RLM Version : 2Link State: Up Last Link Status Reported: UpNext tx TID: 1 Last rx TID: 0Server Link Group[carteret]: Last Reported Priority: HIGHlink [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: HIGHlink [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 Valuesopen_wait = 3s force-down = 30srecovery = 12s switch-link = 5sminimum-up = 60s retransmit = 1skeepalive = 1s
RLM Group 0 StatisticsLink_up:last time occurred at Nov 18 10:57:43.992, total transition=59avg=06:36:36.298, max=2d22h, min=00:00:00.000, latest=00:00:04.844Link_down:last time occurred at Nov 18 10:57:10.992, total transition=28avg=00:56:54.621, max=1d00h, min=00:00:00.000, latest=00:00:33.000Link_recovered:last time occurred at Nov 18 10:56:58.992, success=25(49%), failure=26avg=0.038s, max=0.224s, min=0.000s, latest=0.000sLink_switched:last time occurred at Nov 11 12:25:52.324, success=6(100%), failure=0avg=0.000s, max=0.000s, min=0.000s, latest=0.000sServer_changed:last time occurred at Nov 18 10:56:54.148 for totally 29 timesServer 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-0avg=43.634s, max=177.004s, min=0.000s, latest=0.000sEcho 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-0avg=0.000s, max=0.964s, min=0.000s, latest=0.000sOpen 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-0avg=43.549s, max=177.004s, min=0.000s, latest=0.000sEcho 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-0avg=0.000s, max=0.960s, min=0.000s, latest=0.000sServer 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-0avg=61.347s, max=177.000s, min=0.000s, latest=0.004sEcho 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-0avg=0.000s, max=2.688s, min=0.000s, latest=0.004sOpen 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-0avg=61.270s, max=177.000s, min=0.000s, latest=0.032sEcho 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 Access Servers Solution

The following section contains sample output from an media gateway that has been configured for the Cisco SS7 Interconnect for Access Servers Solution
version 12.1service timestamps debug datetime msec localtime show-timezoneservice timestamps log datetime msec localtime show-timezoneservice password-encryption!hostname ppp1-1.os1!boot system flash c5300-js-mz.121-5.binboot system flash bootflash:logging console emergencies!username admin privilege 15 password 7 <---- Removed ---->username ppp1.os password 7 <---- Removed ---->spe 1/0 2/9firmware location flash:/mica-modem-pw.2.7.1.0.bin!!resource-pool disable!!!!!clock timezone MET 1clock summer-time MET-DST recurring last Sun Mar 2:00 last Sun Oct 3:00modem country mica norwayip subnet-zerono ip fingerip domain-list world-online.noip name-server 10.2.64.170ip name-server 10.2.64.171!ip cef!async-bootp nbns-server 0.0.0.0vty-asyncvty-async virtual-template 1isdn switch-type primary-niisdn voice-call-failure 0cns event-service servermta receive maximum-recipients 0!!controller E1 0framing NO-CRC4clock source line primarypri-group timeslots 1-31 nfas_d primary nfas_int 1 nfas_group 0!controller E1 1framing NO-CRC4clock source line secondary 1pri-group timeslots 1-31 nfas_d none nfas_int 2 nfas_group 0!controller E1 2framing NO-CRC4clock source line secondary 2pri-group timeslots 1-31 nfas_d none nfas_int 3 nfas_group 0!controller E1 3framing NO-CRC4clock source line secondary 3pri-group timeslots 1-31 nfas_d none nfas_int 4 nfas_group 0!!!!interface Ethernet0ip address 10.0.1.17 255.255.255.192no ip mroute-cacheno cdp enable!interface Virtual-Template1ip unnumbered FastEthernet0ip verify unicast reverse-pathno logging event link-statuspeer default ip address pool ippoolcompress stacppp authentication pap callin modemauthenppp accounting modemaccountppp multilink bapppp bap call acceptppp bap timeout pending 20!interface Serial0no ip addressno ip mroute-cacheno fair-queueclockrate 2015232no cdp enable!interface Serial1no ip addressno ip mroute-cacheno fair-queueclockrate 2015232no cdp enable!interface Serial2no ip addressno ip mroute-cacheno fair-queueclockrate 2015232no cdp enable!interface Serial3no ip addressno ip mroute-cacheno fair-queueclockrate 2015232no cdp enable!interface Serial0:15no ip addressencapsulation pppno ip route-cache cefdialer rotary-group 1autodetect encapsulation ppp v120isdn switch-type primary-niisdn incoming-voice modemisdn T203 10000isdn rlm-group 0no isdn send-status-enquirycompress stacno cdp enable!interface FastEthernet0ip address 10.2.67.17 255.255.255.192ip access-group snmp-filter inip access-group ppp-martians-out outip route-cache flowip summary-address eigrp 900 10.2.73.0 255.255.255.128 5no ip mroute-cacheduplex fullspeed autono cdp enableno mop enabled!interface Group-Async1ip unnumbered FastEthernet0ip verify unicast reverse-pathencapsulation pppno ip mroute-cacheno logging event link-statusdialer in-banddialer idle-timeout 7200dialer-group 1async mode dedicatedpeer default ip address pool ippoolcompress stacno cdp enableppp max-bad-auth 3ppp authentication pap callin modemauthenppp accounting modemaccountgroup-range 1 120!interface Dialer1ip unnumbered FastEthernet0ip verify unicast reverse-pathencapsulation pppno ip mroute-cacheno logging event link-statusno keepalivedialer in-banddialer idle-timeout 7200dialer-group 1peer default ip address pool ippoolcompress stacno cdp enableppp max-bad-auth 3ppp authentication pap callin modemauthenppp accounting modemaccountppp multilink bapppp timeout retry 1ppp timeout authentication 1ppp bap call acceptno ppp bap drop requestno ppp bap timeout pendingno ppp bap monitor load!!ip local pool ippool 10.2.73.1 10.2.73.127ip classlessip route 10.0.2.0 255.255.255.192 10.0.1.1ip route 10.2.66.10 255.255.255.254 10.2.67.1ip tacacs source-interface FastEthernet0no ip http server!!dialer-list 1 protocol ip permitno cdp run!tacacs-server host 10.2.64.147tacacs-server host 10.2.64.146tacacs-server key <---- Removed ---->snmp-server engineID local 000000090200003080BD3C8Csnmp-server community <---- Removed ----> ROsnmp-server community <---- Removed ----> RO!!rlm group 0server sc000link address 10.2.66.12 source FastEthernet0 weight 3link address 10.0.2.12 source Ethernet0 weight 4server sc010link address 10.2.66.13 source FastEthernet0 weight 1link address 10.0.2.13 source Ethernet0 weight 2alias exec u undeb all!line con 0exec-timeout 0 0login authentication xTYtransport input noneline 1 120no flush-at-activationmodem InOutmodem autoconfigure type micaautocommand ppptransport input alltransport output pad telnet rlogin udptn v120 lapb-taline aux 0password 7 <---- Removed ---->line vty 0 4access-class 1 inexec-timeout 0 0password 7 <---- Removed ---->transport input telnetescape-character 3line vty 5 124autocommand ppp negotransport input v120!ntp clock-period 17180014ntp update-calendarntp server 10.2.64.146end
Configuring Call Hairpinning on the Cisco AS5800

The hairpinning feature takes an incoming call and forwards the call out from the access server to another device, such as a voice switch or voice terminal. This is done without affecting the calling customer's experience. An incoming call is matched against configured dial peers, and based on the configured called number, the outgoing interface is selected.The call is sent out through a circuit-switched connection through the access server. No Cisco AS5800 modems or DSPs are involved, although a circuit is established through the access server.

Note Hairpinning is supported only on the Cisco AS5800.

Note Hairpinning requires the MICA plane.

Call Switching Using Dial Peers

Call switching using dial peers enables the Cisco AS5800 to switch both voice and data calls between different interfaces based on the dial peer matching. An incoming call is matched against configured dial peers, and based on the configured called number, the outgoing interface is selected. Any call that arrives from the PSTN is either terminated on the access server or switched back to the PSTN, depending on the configuration.

Note An incoming call will be hairpinned back to the PSTN only if it matches a dial peer.

A dial peer is an addressable call endpoint identified, for example, by a phone number or a port number. Dial peers are defined from the perspective of the access server and are used for both inbound and outbound call legs. An inbound call leg originates outside the access server. An outbound call leg originates from the access server.

For inbound call legs, a dial peer might be associated with the calling number or the port designation. Outbound call legs always have a dial peer associated with them. The destination pattern (a defined initial part of a phone number) is used to identify the outbound dial peer. The call is associated with the outbound dial peer at setup time.

POTS dial peers associate a telephone number with a particular voice port so that incoming calls for that telephone number can be received and outgoing calls can be placed.

Using Class of Restrictions

The Class of Restrictions (COR) functionality provides the ability to deny certain call attempts based on the incoming and outgoing class of restrictions provisioned on the dial peers. This functionality provides flexibility in network design, allows users to block calls (for example, to 900 numbers), and applies different restrictions to call attempts from different originators.

COR is used to specify which incoming dial peer can use which outgoing dial peer to make a call. Each dial peer can be provisioned with an incoming and an outgoing COR list. The incoming COR list indicates the capability of the dial peer to initiate certain classes of calls. The outgoing COR list indicates the capability required for an incoming dial peer to deliver a call via this outgoing dial peer. If the capabilities of the incoming dial peer are not the same or a superset of the capabilities required by the outgoing dial peer, the call cannot be completed using this outgoing dial peer.

Note The use of COR is not required for call hairpinning.

Call Hairpinning Configuration Tasks

To configure call hairpinning on the Cisco AS5800, refer to the following sections:

• Configuring Global or Interface Trunk Groups

• Configuring Dial Peer Classes of Restrictions

Configuring Global or Interface Trunk Groups

You can create trunk groups globally (using the one-command version of Step 1) or on each interface (using the two-command version of Step 1). To configure trunk groups, use the following commands beginning in global configuration mode:

Command

Purpose

Step 1

Router(config)# trunk group group-number

Defines the trunk group globally.

or

Router(config-if)# interface serial0/0/n
and

Specifies the PRI D-channel. For n, the D-channel number, use:

•0:23 on a T1 PRI

•0:15 on an E1 PRI

Router(config-if)# trunk-group group-number

Adds the interface to a trunk group. If the trunk group has not been defined globally, it will be created now.

Step 2

Router(config-if)# max-calls {voice | data | any}
number | [direction in | out]

Applies a maximum number of calls restriction to the trunk group.

This command can be repeated to apply a maximum number to different types of calls and, optionally, to specify whether the maximum applies to incoming or outgoing calls.

Note Repeat Step 1 and Step 2 to create additional trunk groups and specify their restrictions, as needed for your traffic.

Step 3

Router(config)# dial-peer voice tag pots

Enters dial-peer configuration mode and defines a remote dial peer.

Step 4

Router(config-dial-peer)# trunkgroup group-number

Specifies the trunk group to be used for outgoing calls to the destination phone number.

Configuring Dial Peer Classes of Restrictions

To configure classes of restrictions for dial peers, use the following commands beginning in global configuration mode:

Command

Purpose

Step 1

Router(config)# dial-peer cor custom

Specifies that named classes of restrictions apply to dial peers.

Step 2

Router(config-cor)# name class-name

Provides a name for a custom class of restrictions.

Note Repeat this step for additional class names, as needed. These class names are used in various combinations to define the lists in Step 3 and Step 4.

Step 3

Router(config)# dial-peer cor list list-name

Provides a name for a list of restrictions.

Step 4

Router(config-cor)# member class-name

Adds a COR class to this list of restrictions.

The member is a class named in Step 2.

Note Repeat Step 3 and Step 4 to define another list and its membership, as needed.

Step 5

Router(config)# dial-peer voice tag pots

Enters dial-peer configuration mode and defines a remote dial peer.

Step 6

Router(config-dial-peer)# corlist incoming cor-list-name

Specifies the COR list to be used when this is the incoming dial peer.

Step 7

Router(config-dial-peer)# corlist outgoing cor-list-name

Specifies the COR list to be used when this is the outgoing dial peer.

Note Repeat Step 5 through Step 7 for additional dial peers, as needed.

Complete Dial Plan Setup for Hairpinning

This example represents a complete dial-plan configuration for hairpinning on the Cisco AS5800:
!version 12.1no service single-slot-reload-enableservice timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname nas-pop1!boot bootldr slot0:c5800-p4-mz.0.3.0no logging bufferedno logging bufferedlogging rate-limit console 10 except errorsenable password letmein!username user_T password 0 ciscousername user_B password 0 ciscousername nas-pstn password 0 ciscousername callgen-term password 0 ciscousername nas-pop1 password 0 ciscoshelf-id 0 router-shelfshelf-id 1 dial-shelf!!resource-pool disable!modem-pool Defaultpool-range 1/2/0-1/2/143,1/3/0-1/3/143!clock timezone MST -7!!ip subnet-zerono ip fingerno ip domain-lookup!isdn switch-type primary-niisdn voice-call-failure 0call rsvp-sync!!controller E1 1/0/0pri-group timeslots 1-31 nfas_d primary nfas_int 0 nfas_group 1!controller E1 1/0/1pri-group timeslots 1-31 nfas_d none nfas_int 1 nfas_group 1!controller E1 1/0/2pri-group timeslots 1-31 nfas_d none nfas_int 2 nfas_group 1!controller E1 1/0/3pri-group timeslots 1-31 nfas_d none nfas_int 3 nfas_group 1!controller E1 1/0/4pri-group timeslots 1-31 nfas_d none nfas_int 4 nfas_group 1!controller E1 1/0/5pri-group timeslots 1-31 nfas_d none nfas_int 5 nfas_group 1!controller E1 1/0/6pri-group timeslots 1-31 nfas_d none nfas_int 6 nfas_group 1!controller E1 1/0/7pri-group timeslots 1-31 nfas_d none nfas_int 7 nfas_group 1!controller E1 1/0/8pri-group timeslots 1-31!controller E1 1/0/9pri-group timeslots 1-31!controller E1 1/0/10pri-group timeslots 1-31!controller E1 1/0/11pri-group timeslots 1-31!controller T1 1/1/0!controller T1 1/1/1!controller T1 1/1/2!controller T1 1/1/3!controller T1 1/1/4!controller T1 1/1/5!controller T1 1/1/6!controller T1 1/1/7!controller T1 1/1/8!controller T1 1/1/9!controller T1 1/1/10!controller T1 1/1/11!!interface Loopback0ip address 192.168.111.1 255.255.255.255ip broadcast-address 192.168.111.1no ip route-cacheno ip mroute-cache!interface Loopback1no ip address!interface FastEthernet0/0/0ip address 10.10.7.10 255.255.255.0ip broadcast-address 10.10.7.255no ip route-cacheno ip mroute-cachelogging event link-statusduplex full!interface FastEthernet0/1/0ip address 10.10.8.10 255.255.255.0ip broadcast-address 10.10.8.255no ip route-cacheno ip mroute-cacheduplex full!interface Serial1/0/0:15ip unnumbered Loopback0encapsulation pppip mroute-cacheno keepalivedialer hold-queue 1dialer-group 1isdn switch-type primary-niisdn incoming-voice modemisdn rlm-group 1no isdn send-status-enquiryisdn bchan-number-order ascendingppp authentication chap!interface Serial1/0/8:15no ip addressisdn switch-type primary-niisdn protocol-emulate networkisdn calling-number 5800-ch8no isdn T309-enableisdn bchan-number-order ascendingtrunk-group 101no cdp enable!interface Serial1/0/9:15no ip addressisdn switch-type primary-niisdn protocol-emulate networkisdn calling-number 5800-ch9no isdn T309-enableisdn bchan-number-order ascendingtrunk-group 101no cdp enable!interface Serial1/0/10:15no ip addressisdn switch-type primary-niisdn protocol-emulate networkisdn calling-number 5800-ch10no isdn T309-enableisdn bchan-number-order ascendingtrunk-group 101no cdp enable!interface Serial1/0/11:15no ip addressisdn switch-type primary-niisdn protocol-emulate networkisdn calling-number 5800-ch11no isdn T309-enableisdn bchan-number-order ascendingtrunk-group 101no cdp enable!interface Group-Async0ip unnumbered Loopback0no ip proxy-arpencapsulation pppip tcp header-compression passiveno ip mroute-cachelogging event link-statusdialer in-banddialer-group 1async default routingasync dynamic addressasync mode dedicatedno peer default ip addressppp authentication chapgroup-range 1/2/00 1/3/143!ip kerberos source-interface anyip classlessip route 0.0.0.0 0.0.0.0 10.10.8.1ip route 192.168.65.0 255.255.255.0 10.10.8.5ip route 192.168.100.0 255.255.255.0 10.10.8.5no ip http server!no logging traplogging facility local0logging 10.1.1.5snmp-server engineID local 000000090200000217C46400snmp-server community public ROsnmp-server community lab RWsnmp-server enable traps snmp authentication linkdown linkup coldstartsnmp-server enable traps calltrackersnmp-server enable traps isdn call-informationsnmp-server enable traps isdn layer2snmp-server enable traps hsrpsnmp-server enable traps configsnmp-server enable traps entitysnmp-server enable traps envmonsnmp-server enable traps aaa_serversnmp-server enable traps syslogsnmp-server enable traps ipmulticastsnmp-server enable traps rsvpsnmp-server enable traps frame-relaysnmp-server enable traps rtrsnmp-server enable traps dialsnmp-server enable traps dsp card-statussnmp-server enable traps ipdcsnmp-server enable traps bgpsnmp-server enable traps voice poor-qovsnmp-server host 10.10.8.100 public!!rlm group 1server sc2200blink address 10.10.7.20 source FastEthernet0/0/0 weight 100!!trunk group 101!voice-port 1/0/0:D!voice-port 1/0/8:D!voice-port 1/0/9:D!voice-port 1/0/10:D!voice-port 1/0/11:D!dial-peer cor customname 800_callname 900blockname 888_call!!dial-peer cor list list1member 800_call!dial-peer cor list list2member 888_call!!dial-peer voice 1 potscorlist incoming list1trunkgroup 101destination-pattern 1800......no digit-stripdirect-inward-dialprefix 1800!dial-peer voice 2 potscorlist incoming list2trunkgroup 101destination-pattern 1888......no digit-stripdirect-inward-dialprefix 1888!!line con 0session-timeout 5transport input noneline aux 0line vty 0 4exec-timeout 0 0password letmeinloginline vty 5 9password letmeinloginline 1/2/00 1/2/143activation-character 0disconnect-character 0modem InOutno modem log rs232escape-character soft 0escape-character 0autohanguphold-character 0line 1/3/00 1/3/143activation-character 0disconnect-character 0modem InOutno modem log rs232escape-character soft 0escape-character 0autohanguphold-character 0!ntp update-calendarntp peer 172.20.144.245

	Command	Purpose
Step 1	Router(config)# trunk group group-number	Defines the trunk group globally.
	or
	Router(config-if)# interface serial0/0/n and	Specifies the PRI D-channel. For n, the D-channel number, use: •0:23 on a T1 PRI •0:15 on an E1 PRI
	Router(config-if)# trunk-group group-number	Adds the interface to a trunk group. If the trunk group has not been defined globally, it will be created now.
Step 2	Router(config-if)# max-calls {voice \| data \| any} number \| [direction in \| out]	Applies a maximum number of calls restriction to the trunk group. This command can be repeated to apply a maximum number to different types of calls and, optionally, to specify whether the maximum applies to incoming or outgoing calls. Note Repeat Step 1 and Step 2 to create additional trunk groups and specify their restrictions, as needed for your traffic.
Step 3	Router(config)# dial-peer voice tag pots	Enters dial-peer configuration mode and defines a remote dial peer.
Step 4	Router(config-dial-peer)# trunkgroup group-number	Specifies the trunk group to be used for outgoing calls to the destination phone number.

	Command	Purpose
Step 1	Router(config)# dial-peer cor custom	Specifies that named classes of restrictions apply to dial peers.
Step 2	Router(config-cor)# name class-name	Provides a name for a custom class of restrictions. Note Repeat this step for additional class names, as needed. These class names are used in various combinations to define the lists in Step 3 and Step 4.
Step 3	Router(config)# dial-peer cor list list-name	Provides a name for a list of restrictions.
Step 4	Router(config-cor)# member class-name	Adds a COR class to this list of restrictions. The member is a class named in Step 2. Note Repeat Step 3 and Step 4 to define another list and its membership, as needed.
Step 5	Router(config)# dial-peer voice tag pots	Enters dial-peer configuration mode and defines a remote dial peer.
Step 6	Router(config-dial-peer)# corlist incoming cor-list-name	Specifies the COR list to be used when this is the incoming dial peer.
Step 7	Router(config-dial-peer)# corlist outgoing cor-list-name	Specifies the COR list to be used when this is the outgoing dial peer. Note Repeat Step 5 through Step 7 for additional dial peers, as needed.