|
|
This document describes the connection-monitoring and T1/E1 alarm-generation features introduced in Cisco IOS Release 12.1(3)T, which expand the local voice busyout and trunk conditioning features on the Cisco 2600 and 3600 series routers and Cisco MC3810 series concentrators.
This document includes the following sections:
The alarm conditioning feature provides status monitoring on T1/E1 PBX voice interfaces for permanent trunk connections created using the Cisco connection trunk command (private lines and tie-lines) and for switched calls. The feature supports operation with channel associated signaling (CAS) only; it does not support common channel signaling (CCS).
A T1/E1 alarm can be triggered by events detected through the monitoring of a specified set of voice ports within a T1/E1 trunk. To include a voice port in the monitored set, you must configure it to be monitored for one of the following connection states:
When all of the monitored voice ports on a T1/E1 trunk go out of service (PVCs are out of service and SVCs are busied out), a T1/E1 blue alarm (alarm indication signal, AIS) can be generated on the T1/E1 connected to the PBX or PSTN.
The set of monitored voice ports is defined by the DS0 group or groups you specify for triggering the T1/E1 alarm.
The alarm conditioning feature provides the following benefits:
Alarm conditioning is not supported on trunks using common channel signaling (CCS) protocols.
The alarm conditioning feature works together with the local voice busyout feature and the trunk conditioning feature, which are documented in the Cisco IOS Multiservice Applications Configuration Guide and the Cisco IOS Multiservice Applications Command Reference.
Cisco IOS Multiservice Applications Configuration Guide, Cisco IOS Release 12.1
Cisco IOS Multiservice Applications Command Reference, Cisco IOS Release 12.1
This feature is supported on the following Cisco platforms:
None
The following configuration tasks should be completed before configuring alarm conditioning:
The alarm conditioning feature described in this document require Cisco IOS Release 12.1(3)T or later.
Complete the following tasks to specify the DS0 group or groups to be monitored and to specify the triggered alarm type:
You can configure the system to monitor any combination of DS0 groups on a T1 or E1 trunk. An alarm is triggered only if all of the monitored DS0 groups on a T1 or E1 trunk go out of service. If one monitored DS0 group is in service, no alarm is triggered.
The DS0 groups can be either of the following types:
 |
Note A T1 or E1 trunk can carry a combination of permanent and switched connections. If one monitored DS0 group of either type is in service, no alarm is triggered. |
To specify the DS0 group or groups to be monitored, and the triggered alarm type for a T1 or E1 trunk, complete the following steps beginning in global configuration mode:
| Command | Purpose | |
|---|---|---|
Step 1 | router(config)# controller {t1 |
e1} {0 | 1}
| Enter controller configuration mode. |
Step 2 | router(config-controller)# mode cas | Configure the controller for CAS signaling. |
Step 3 | router(config-controller)# ds0-group | Configure DS0 groups on the controller. Repeat this step for each DS0 group to be configured. |
Step 4 | router(config-controller)# alarm-trigger blue | Enable alarm conditioning and configure the system to monitor one or more DS0 groups for the busied-out state. The keyword (required) blue specifies a blue (AIS) alarm. Values for ds0-group-list can be a single DS0 group number, a single range of numbers, or multiple ranges of numbers separated by commas. Allowable values are 0 to 23 for T1 and 0 to 30 for E1. |
Step 5 | router(config-controller)# exit | Exit from controller configuration mode. |
Use one or more of the following methods to verify that a T1/E1 controller is correctly configured for generating alarms:
Use the "show running-config" Command
Enter the show running-config command to review the alarm-generation parameters you have configured.
The following example shows part of the output from the show running-config command on a Cisco MC3810, with controller E1 0 configured so that a blue alarm is generated if DS0 groups 0, 1, and 2 (voice ports 0:0, 0:1, and 0:2) are all busied out:
router# show running-config Building configuration... . . . controller E1 0 mode cas ds0-group 0 timeslots 1-10 type e&m-immediate-start ds0-group 1 timeslots 11-15,17-20 type e&m-immediate-start ds0-group 2 timeslots 21-30 type e&m-immediate-start alarm-trigger blue 0-2 . . .
Create an Out-of-Service Condition (OOS or Busyout)
Create an out-of-service state on all of the voice ports on the controller; this should cause a blue alarm to be generated.
a. Shut down or disconnect any serial and Ethernet interfaces that are monitored for out-of-service busyout.
b. Activate any serial and Ethernet interfaces that are monitored for in-service busyout.
|
Note All of the voice ports configured for switched connections and monitored for alarm trigger must have the busyout monitor function enabled; otherwise, no alarm can be triggered. |
a. Shut down or disconnect the associated local serial interface.
b. Shut down the associated far-end T1/E1 controller.
Use the "show controller" Command
Enter the show controller command to display information about the alarm status of the T1 or E1 trunk.
router# show controller t1 0 T1 0 is up. Applique type is Channelized T1 Cablelength is long gain36 0db Yellow alarm detected. alarm-trigger is set to Blue Alarm is triggered Slot 3 CSU Serial #00000056 Model TEB HWVersion 3.70 RX level = 0DB Framing is ESF, Line Code is B8ZS, Clock Source is Line. Data in current interval (827 seconds elapsed): . . .
Alarm Trigger for Busyout of Voice Ports Due to Trunk Conditioning
This example creates three permanent trunks on controller T1 0 and configures T1 0 to send a blue (AIS) alarm if all three permanent trunks are out of service.
These steps create the voice ports and configure the alarm trigger:
router(config)# controller t1 0 router(config-controller)# mode cas router(config-controller)# ds0-group 0 timeslots 1-10 type fxs-ground-start router(config-controller)# ds0-group 1 timeslots 11 type fxs-ground-start router(config-controller)# ds0-group 2 timeslots 12-23 type fxs-ground-start router(config-controller)# alarm-trigger blue 0-2 router(config-controller)# exit router(config)#
These steps create a voice class to define the trunk conditioning parameters for permanent trunks (in which the default values are not used):
router(config)# voice class permanent 8
router(config-class)# signal keepalive 10
router(config-class)# signal timing oos timeout 60
router(config-class)# signal timing idle suppress-voice 5
router(config-class)# signal timing oos restart 120
router(config-class)# exit
router(config)#
These steps create a VoIP dial peer to define the network connectivity and trunk conditioning parameters for permanent trunks:
router(config)# dial-peer voice 100 voip router(config-dial-peer)# session target ipv4:172.20.10.10 router(config-dial-peer)# destination-pattern 10.. router(config-dial-peer)# voice-class permanent 8 router(config-dial-peer)# exit router(config)#
These steps assign each voice port to a permanent trunk and associate each trunk with a network dial peer:
router(config)# voice-port 0:0 router(config-voiceport)# connection trunk 1001 router(config-voiceport)# exit router(config)# voice-port 0:1 router(config-voiceport)# connection trunk 1002 router(config-voiceport)# exit router(config)# voice-port 0:2 router(config-voiceport)# connection trunk 1003 router(config-voiceport)# exit router(config)#
Alarm Trigger for Busyout of Voice Ports Due to Monitored Interface
This example creates three voice ports on controller T1 0 and configures T1 0 to send a blue (AIS) alarm if all three voice ports are busied out.
These steps create the voice ports and configure the alarm trigger:
router(config)# controller t1 0 router(config-controller)# mode cas router(config-controller)# ds0-group 0 timeslots 1-10 type fxs-ground-start router(config-controller)# ds0-group 1 timeslots 11 type fxs-ground-start router(config-controller)# ds0-group 2 timeslots 12-24 type fxs-ground-start router(config-controller)# alarm-trigger blue 0-2 router(config-controller)# exit router(config)#
These steps configure voice port 0:0 for busyout if serial port 0.1, 0.2, and Ethernet port 0 all go out of service, or serial port 1 comes into service:
router(config)# voice-port 0:0 router(config-voiceport)# busyout monitor serial 0.1 router(config-voiceport)# busyout monitor serial 0.2 router(config-voiceport)# busyout monitor ethernet 0 router(config-voiceport)# busyout monitor serial 1 in-service router(config-voiceport)# exit router(config)#
These steps configure voice port 0:1 for busyout if the connections to both of two remote IP addresses go out of service:
router(config)# voice-port 0:1 router(config-voiceport)# busyout monitor probe 209.165.202.128 codec g711a icpif 15 router(config-voiceport)# busyout monitor probe 209.165.202.129 codec g711a icpif 15 router(config-voiceport)# exit
These steps configure voice port 0:2 for busyout under any one of the following conditions:
router(config)# voice-port 0:2 router(config-voiceport)# busyout monitor serial 0.1 router(config-voiceport)# busyout monitor serial 0.2 router(config-voiceport)# busyout monitor serial 1 in-service router(config-voiceport)# busyout monitor probe 209.165.202.128 codec g711a icpif 15 router(config-voiceport)# busyout monitor probe 209.165.202.129 codec g711a icpif 15 router(config-voiceport)# exit router(config)# exit router#
The following new and modified commands are described in this section (modified commands are marked by an asterisk):
To configure a T1 or E1 to send an alarm to the PSTN or switch if specified T1 or E1 DS0 groups are out of service, use the alarm-trigger controller configuration command. To configure a T1 or E1 not to send an alarm, use the no form of this command.
alarm-trigger blue ds0-group-list
Syntax Description
blue Alarm type to be sent is "blue" (AIS). ds0-group-list The DS0 group or groups to be monitored for permanent trunk connection status or busyout status.
Defaults
No alarms are sent.
Command Modes
Controller configuration.
Command History
| Release | Modification |
|---|---|
12.1(3)T | This command was introduced on the Cisco 2600, 3600, and MC3810 series. |
Usage Guidelines
Any monitored time slot can be used for either permanent trunk connections or switched connections. PVCs and SVCs can be combined on a T1 or E1 and monitored for alarm conditioning.
An alarm is sent only if all of the time slots configured for alarm conditioning on a T1 or E1 are out of service. If one monitored time slot remains in service or returns to service, no alarm is sent.
Examples
The following example configures T1 0 to send a blue (AIS) alarm if DS0 groups 0 and 1 are out of service:
router(config)# controller t1 0 router(config-controller)# alarm-trigger blue 0,1 router(config-controller)# exit router(config)#
Related Commands Related Commands
| Command | Description |
busyout monitor | Configures a voice port to monitor an interface for events that would trigger a voice-port busyout. |
voice class permanent | Creates a voice class for a Cisco or FRF-11 permanent trunk. |
connection trunk | Creates a permanent trunk connection (private line or tie-line) between a voice port and a PBX. |
ABCD signaling—Four-bit telephony line signaling coding in which each letter of "ABCD" represents one of the four bits. This is often associated with CAS or Robbed-Bit signaling on a T1 or E1 telephony trunk.
AIS—Alarm Indication Signal.
AVBO—Advanced Voice Busyout.
Cisco-trunk (private line) call—A Cisco-trunk (private line) call is established by the forced connection of a switched call. A Cisco-trunk call is established during configuration of the trunk and stays up for the duration of the configuration. Optionally, it provides a pass-through connection path to pass signaling information between the two telephony interfaces at either end of the connection.
CLI—Command line interface.
codec—coder-decoder. An integrated circuit device that typically uses pulse code modulation to transform analog signals into a digital bit stream and digital signals back into analog signals. In Voice over IP, Voice over Frame Relay, and Voice over ATM, a DSP software algorithm used to compress/decompress speech or audio signals.
DLCI—Data-link connection identifier.
Dial peer—An addressable call endpoint that contains configuration information including voice protocol, a codec type, and a telephone number associated with the call endpoint. There are four kinds of dial peers: POTS, VoIP, VoFR, and VoATM.
DSP—Digital Signaling Processor.
DTMF—Dual tone multifrequency. Uses two simultaneous voice-band tones for dial such as touch tone.
DTMF relay—Enables the generation of FRF.11 Annex A frames for a VoFR dial peer.
Switched call—A telephone call dynamically established across a packet data network based on a dialed telephone number. In the case of VoFR, a Cisco proprietary session protocol similar to Q.931 is used to achieve call switching and negotiation between calling endpoints. The proprietary session protocol runs over FRF.11-compliant subchannels.
E&M—Stands for 2-wire or 4-wire interfaces with separate signaling paths (from "Ear and Mouth", also "recEive and transMit"). E&M is a trunking arrangement generally used for two-way switch-to-switch or switch-to-network connections. Cisco's analog E&M interface is an RJ-48 connector that allows connections to PBX trunk lines (tie lines). E&M connections are also available on E1 and T1 digital interfaces.
E1—European equivalent of T1. 32-64kbps channels include 1-channel for framing and 1-channel for signaling information. The clock rate is 2.048 Mhz.
FRF—Frame Relay Forum. An association of corporate members consisting of vendors, carriers, users, and consultants committed to implementing Frame Relay in accordance with national and international standards. See http://www.frforum.com.
FRF.11—Frame Relay Forum implementation agreement for Voice over Frame Relay (v1.0 May 1997). This specification defines multiplexed data, voice, fax, DTMF digit-relay, and CAS/Robbed-bit signaling frame formats, but does not include call setup, routing or administration facilities. See http://www.frforum.com.
FRF11-trunk—A point-to-point permanent voice connection (private line) conforming to the FRF.11 specification.
FXO—Foreign Exchange Office. An FXO interface connects to the Public Switched Telephone Network (PSTN) or to a station interface on a PBX. Cisco's FXO interface is an RJ-11 connector that allows an analog connection to the PSTN or to a PBX.
FXS—Foreign Exchange Station. An FXS interface connects directly to a standard telephone and supplies ring, voltage, and dial tone. Cisco's FXS interface is an RJ-11 connector that allows connections to basic telephone service equipment, keysets, and PBXs.
ICPIF—Calculated Planning Impairment Factor.
LVBO—Local Voice Busy Out.
MEL CAS—Mercury Exchange Limited (MEL) Channel Associated Signaling. A voice signaling protocol used primarily in the United Kingdom.
OOS—Out of Service state of the call or trunk.
PBX—Private Branch Exchange. A privately owned central switching office.
Permanent calls—Permanent calls are private line calls used for fixed point-to-point calls, connections between PBXs (E&M to E&M), or for remote telephone extensions (FXO to FXS).
POTS—Plain old telephone service. Basic telephone service supplying standard single line telephones, telephone lines, and access to the PSTN.
POTS dial peer—Dial peer connected by a traditional telephony network. POTS peers point to a particular voice port on a voice network device.
PSTN—Public Switched Telephone Network.
RTR—Response Time Reporter.
Switched calls—Switched calls are normal telephone calls when a user picks up a phone, hears a dial tone, and enters the destination phone number to reach the other phone.
T1—Digital carrier facility. T1 transmits DS-1-formatted data at 1.544 Mbps through the telephone-switching network by using AMI or B8ZS coding.
Trunk—Service that allows quasi-transparent connections between two PBXs, a PBX and a local extension, or some other combination of telephony interfaces with signaling passed transparently through the packet data network.
VoFR—Voice over Frame Relay.
VoFR dial peer—Dial peer connected by a Frame Relay network. VoFR peers point to specific VoFR devices.
Voice over Frame Relay—Voice over Frame Relay enables a router to carry voice traffic, for example, telephone calls and faxes, over a Frame Relay network. When sending voice traffic over Frame Relay, the voice traffic is segmented and encapsulated for transit across the Frame Relay network by using FRF.12 encapsulation.
Voice over IP—Voice over IP enables a router to carry voice traffic, for example, telephone calls and faxes, over an IP network. In Voice over IP, the DSP segments the voice signal into frames, which are then coupled in groups and stored in voice packets that are transported by IP.
VoIP—Voice over IP through Ethernet.
Posted: Wed Sep 27 12:49:03 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.