|
|
This chapter describes how to configure the Cisco IOS on the Cisco AS5300 universal access server for the Cisco SS7 Interconnect for Voice Gateways Solution. The Cisco AS5300 acts as a network access server, or media gateway (MGW), in an environment where SS7 and Q.931/IP are used to signal the establishment of bearer channels on time-division multiplexing (TDM) trunks connected to the MGW.
This chapter includes the following sections:
 |
Note This model has two Ethernet ports and is suited to redundant Ethernet configurations. It also requires MICA modems if your network implements two-wire continuity checks for a dial-up gateway. |
The Cisco AS5300 supports the features shown in Table 6-1:
| Feature | Support for... |
|---|---|
Asynchronous and digital ISDN calling | Service and termination of (ISDN) calls per standalone Cisco AS5300 and one phone number. |
T1/E1 PRI lines | Supports two T1 or E1 PRI lines. Combines LAN, WAN, and asynchronous line support in a single package. |
Integrated modems | As many as 60 (with E1 configuration). |
Protocols and services | All protocols and services on the asynchronous ports. |
Telnet connections | Dialing out from the network. |
IBM tunneling and conversion | Data link switching (DLSw). |
Offers bandwidth management and optimization and security features including data compression, IPX/SPX spooling, and packet filters. | |
Multiprotocol security | Delivers multiprotocol security levels with authorization and accounting control. |
T1/E1 PRI lines | Terminates as many as eight E1 or T1 connections. |
Gateway routing | Provides gateway routing serial support. |
Voice feature cards (DSPs with continuity testing, Ethernet card management, and voice compression). |
Consult the following documentation for more details:
Before you begin the configuration, verify that you have the following Cisco AS5300 hardware:
Before you begin the configuration, confirm the version of software that is currently running.
Step 2 Type sh ver.
|
Note You must be in the enable mode and configuration mode in order to complete the configuration. |
|
Note In order to configure your media gateway, enter the following field/command: default ISDN switch type isdn switch-type primary-ni |
| Controller Format: T1| E1 0 | Type T1| E1 | Framing (SF|ESF) (crc4|no-crc4) | Linecode (B8ZS | AMI) (HDB3 | AMI) | Clocking (line | internal | loop timing) | Other | Description |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| pri-group timeslots (1-24 for T1 | 1-32 for E1) | pri-group nfas_d primary | none | pri-group nfas_int (Span-ID in signaling controller) | pri-group nfas_group |
|---|---|---|---|
| primary |
|
|
| none |
|
|
| none |
|
|
| none |
|
|
| Interface Name | Type | IP Address | Mask | Description |
|---|---|---|---|---|
FastEthernet0 | FE |
|
| Access to IP network, path to signaling controller for signaling, and so on. |
Ethernet0 | Ethernet |
|
| Access to IP network, path to signaling controller for signaling, and so on. |
Serial0:23 | serial | No IP address. | N/A | Pseudo ISDN D channel for configuration of signaling controller; created automatically with the pri-group command. |
Group-Async1 | async lines | IP unnumbered loopback0. | N/A | Cisco SS7 Interconnect for Access Servers Solution only—For async modem dial-in calls to be configured as a group; must be created manually. |
Dialer 1 | digital | IP unnumbered loopback0 | N/A | Cisco SS7 Interconnect for Access Servers Solution only—For digital dial-in calls to be configured as a group; created automatically by the dialer rotary-group 1 command in S0:23 interface configuration. |
| Interface Name | Description | ||
|---|---|---|---|
description pseudo D channel | In a signaling controller environment, this channel does not carry ISDN D channel signaling, but the configuration still requires a D channel definition so that it is linked to the Redundant Link Manager (RLM) and becomes a D channel over IP. | ||
no IP address | Configuration of the ISDN D Channel.
| ||
encapsulation ppp | Cisco SS7 Interconnect for Access Servers Solution only—Enables PPP encapsulation.
| ||
no logging event link-status | Disables logging of link state changes (default). | ||
dialer rotary-group 1 | Cisco SS7 Interconnect for Access Servers Solution only—Creates interface dialer1 for digital dial-in users in bearer channels of PRIs signaled by this D channel. | ||
isdn switch-type primary-ni | ISDN D channel signaling is type "ni", which is ISDN over IP from the signaling controller.
| ||
isdn incoming-voice modem | Bearer channels containing analog dial-in users are to be connected to modems (or VFC for VoIP) to establish PPP sessions. | ||
isdn rlm-group 0 | RLM group; indicates that ISDN D channel will be from the signaling controller to the IP address specified in the RLM group command below. | ||
no cdp enable | Disables Cisco Discovery Protocol on interface. |
| Interface Name | Description |
|---|---|
description digital group | Created automatically from dialer rotary-group 1 command in S0:23 interface configuration; for digital dial-in calls to be configured as a group. |
ip unnumbered loopback0 | These dial-in users will not be affected by the loss of an IP interface into the IP network. |
encapsulation ppp | Dial-in users are PPP. |
no logging event link-status | Disables logging of link state changes. |
peer default iP address pool default | IP addresses for analog dial-in users will be from the default IP address pool. |
ppp authentication chap | Enables Challenge Handshake Authentication Protocol (CHAP) authentication (optional). |
ppp multilink | Enables multilink PPP sessions to be established (optional). |
no cdp enable | Disables Cisco Discovery Protocol on this interface. |
| Parameter | Value | ||
|---|---|---|---|
IP subnet for first interface to signaling controller |
| ||
IP subnet for second (optional) interface to signaling controller |
| ||
IP subnet for interface to IP network (internet access router)
|
| ||
Pool of IP addresses for Group-Async1 and Dialer1 interfaces Configuration: ip local pool default <first_in_range> <last> |
| ||
Default route |
| ||
Do all IP addresses conform to class? If no, add statement: ip classless |
|
|
Note If you have questions or need assistance, see the CCO in the "Obtaining Technical Assistance" section. |
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:
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. |
For details, see the publication Redundant Link Manager Feature at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/rlm_123.htm
To configure the RLM on your Cisco AS5300, perform the following steps:
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 IP address of the first interface, enter the following commands:
Router(config)# interface ethernet0 Router(config-if)# ip address 10.1.1.1 255.255.255.255
Step 4 To specify the IP address of the second interface, enter the following commands:
Router(config-if)# interface ethernet0 Router(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 1 Router(config-rlm-group)#
|
Note The RLM group number must match the 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 7 and Step 8 for the second device:
Router(config-rlm-group-sc)# server r2-server Router(config-rlm-group-sc)# link address 10.1.5.1 source ethernet0 weight1 Router(config-rlm-group-sc)# link address 10.1.5.2 source ethernet0 weight2
Step 9 To configure the EIGRP, enter the following command:
Router(config-rlm-group-sc)# router eigrp 100 Router(config-router)#
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[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-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):
The second half of the message displays information for Serial 1:23.
 |
Tips 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. |
This completes the RLM configuration. If you have questions or need assistance, see the "Obtaining Technical Assistance" section.
Cisco RPMS provides the following:
Cisco RPMS offers three major functions:
To configure RPM on your Cisco Media Gateway, perform the following steps:
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 WORD Router(config) # range port s/s/p s/s/p Router(config) # range limit limit
|
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. |
|
Tips If you have an RPMS, you do not need to define VPDN groups/profiles, customer profiles, or DNIS groups on the Cisco AS5300—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:
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 WORD
Router(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 WORD
Router(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:
Step 6 To configure customer profiles, enter the following commands:
Router(config) # resource-pool profile customer WORD
Router(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:
Step 7 To configure VPDN profiles, enter the following commands:
Router(config) # resource-pool profile customer WORD
Router(config) # vpdn profile profile-name
Router(config) # resource-pool profile vpdn profile-name
Router(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-name
Router(config) # request dialin {l2f | l2tp} ip A.B.C.D {dnis dnis-group-name | domain Word}
Router(config) # multilink {link | bundle} number
Router(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. |
This completes the RPM configuration. For detailed configuration, troubleshooting, and command reference information, see the publication Resource Pool Management at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t5/
rpm1205t.htm
If you have questions or need assistance, see the "Obtaining Technical Assistance" section.
This section provides the following configuration examples:
resource-pool enable resource-pool call treatment resource busy resource-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 DEFAULT limit base-size 10 resource MICA-modems speech service silver dnis group default resource-pool profile discriminator deny_DNIS call-type digital dnis group bye-bye ! resource-pool profile service gold modem min-speed 33200 max-speed 56000 modulation v90 resource-pool profile service silver modem min-speed 19200 max-speed 33200 modulation v34 ! resource-pool aaa protocol local ! dialer dnis group ACME_dnis_numbers number 301001 dialer dnis group bye-bye number 301005
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 ACME limit base-size 30 limit overflow-size 10 resource isdn-ports speech dnis 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. |
The following command allows you to use VPDN by setting up a VPDN profile and a VPDN group:
resource-pool profile vpdn ACME_VPDN limit base-size 6 limit overflow-size 0 vpdn group outgoing-2 ! resource-pool profile customer ACME limit base-size 30 limit overflow-size 10 resource isdn-ports digital resource MICA-modems speech service gold dnis group ACME_dnis_numbers vpdn profile ACME_VPDN vpdn enable ! vpdn-group outgoing-2 request dialin 12f ip 172.16.1.9 dnis ACME_dnis_numbers local name HQ-NAS multilink bundle 1 multilink link 2 dnis ACME_dnis_numbers ! dialer dnis group ACME_dnis_numbers number 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. |
This section lists the steps you should follow to configure the Cisco MGW in your solution to use Voice over IP (VoIP).
Before you can configure your Cisco AS5300 to use VoIP, you must:
Step 2 Complete basic configuration for the Cisco AS5300. This includes, as a minimum, the following tasks:
|
Note For more information about any of these configuration tasks, see Cisco AS5300 Universal Access Server Software Configuration Guide at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/ 120t/120t3/voip5300/voip53_1.html |
Step 3 Install the voice feature card (VFC) into the appropriate slot of your Cisco AS5300.
Each VFC can hold up to ten digital signal processor modules (DSPMs) enabling processing for as many as 60 B channels per card. Each Cisco AS5300 supports two VFCs, for a total of 120 calls, that support four E-1 lines.
|
Note For more information about the physical characteristics of the VFCs or DSPMs, or about how to install them, see Cisco AS5300 Voice-over-IP Feature Card Installation and Configuration Guide at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/5300cfg/4934vcip.htm |
Step 4 Complete your company's dial plan.
Step 5 Establish a working telephony network based on your company's dial plan.
Step 6 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:
Step 7 Depending on the topology of your network or the resources used in your network, you might need to perform the following additional tasks:
Cisco SS7 Interconnect for Voice Gateways Solution for the Cisco AS5300 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:
|
Note The Cisco AS5300 VoIP tasks are described in detail in Voice over IP for the Cisco AS5300 located at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120t/120t3/voip5300/voip53_1.htm |
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) # |
numbering-type type of number | Specifies number type. Number types are:
| Media-Gateway (config-dial-peer) # |
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. |
Media-Gateway (config) #dial-peer voice 100 pots Media-Gateway (config-dial-peer) | ||
no digit strip | Disables digit strip. |
|
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:
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:
|
Tips You should configure your translation rules before you apply rules to your dial-peer call legs. |
| 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) |
translate-outgoing calling translation-tag | Translates outbound calling number. | Media-Gateway (config-voiceport) |
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 |
Following is a sample output from a Cisco AS5300 set up for bearer channels for VoIP:
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 Cisco AS5300 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. In this configuration, we configured the int number to match the T-1 controller number.
Some tips to remember when configuring are as follows:
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.
To verify the configuration perform the following steps:
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
! version 12.0 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
Posted: Fri Aug 25 14:26:23 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.