|
Table Of Contents
Configuring T1 CAS for VoIP on Cisco Access Platforms
Channelized T1 Robbed Bit Features
Configuring Service Provider T1 CAS
Configuring T1 CAS for VoIP on Cisco Access Platforms
Feature Summary
This feature adds support for T1 Channel Associated Signaling (CAS) and limited support for E1 R2 signaling to the Cisco AS5300 universal access server with the Voice Feature Card (VFC).
CautionCisco IOS Release 11.3(6)NA2 requires VCWare version 2.4 code. Cisco IOS Release 11.3(7)NA requires VCWare version 2.5.
CAS is the transmission of signaling information within the voice channel. Various types of CAS signaling are available in the T1 world. The most common forms of CAS signaling are loop-start, ground-start, and E&M. The biggest disadvantage of CAS signaling is its use of user bandwidth to perform signaling functions. CAS signaling is often referred to as robbed-bit-signaling because user bandwidth is being "robbed" by the network for other purposes. In addition to receiving and placing calls, CAS signaling also processes the receipt of DNIS and ANI information, which is used to support authentication and other functions.
The service provider application for T1 CAS includes connectivity to the public network using T1 CAS from the Cisco AS5300 to the end office switch. In this configuration, the Cisco AS5300 captures the dialed-number or called-party number information and passes it along to the upper level applications for IVR script selection, modem pooling, and other applications. Service providers also require access to calling party number, ANI, for user identification, for billing account number, and in the future, more complicated call routing.
Service providers who implement VoIP include traditional voice carriers, new voice and data carriers, and existing Internet service providers. Some of these service providers might use subscriber side lines for their VoIP connectivity to the PSTN; others will use tandem-type service provider connections.
Benefits
The T1 CAS interface is used for both connection to private PBX's, and to the PSTN. This feature is required by both Enterprise customers and Service Providers in North America. For most enterprise customers, T1 CAS is the only kind of line they use from the PSTN, and for connecting to their PBX's, E&M may be the only option.
List of Terms
ANI—Automatic number identification (calling party number).
CAS—Channel associated signaling.
CO—Central office.
CSM—Call switching module.
CT1—Channelized T1.
DNIS—Dialed number identification service. Same as called party number.
DSP—Digital signal processor.
DTMF—Dual tone multi-frequency.
EAIN—Bellcore FGD Exchange Access International Signaling.
EANA—Bellcore FGD Exchange Access North American Signaling.
E&M—Ear and mouth. A signaling technique for two and four wire telephone and trunk interfaces.
FGD—Bellcore Feature Group D.
FXO—Foreign Exchange Office.
FXS—Foreign Exchange Subscriber (as in FXS-loop-start and FXS-ground-start). FXS loop and ground start protocols are a type of signaling used to indicate the beginning of a call. The FXS interface is used on the line-side access to CO (for example, communication between CO and key system).
MF—Multiple Frequency, an interoffice address signaling method in which 10 decimal digits and five auxiliary signals are each represented by a pair of the following frequencies: 700, 900, 1100, 1300, 1500 and 1700 Hz.
PSTN—Public Switched Telephone Network.
RGW—Residential gateway.
RLCF—Reverse loop current feed.
Session Application—Application in the VoIP system responsible for providing the telephony user interface.
SAS—Special Exchange Subscriber (as in SAS loop-start and ground-start). Identical to FXS loop and ground start in functionality, but use of the A and B bits are different. (SAS transmitted B Bits are complementary to FXS transmitted B bits. SAS received A bits are complementary to FXS received A bits).
SGCP—Simple gateway control protocol.
SGCP Application—The application in the VoIP via SGCP system responsible for SGCP call management.
SPI—Service provider interface.
TGW—Trunking gateway.
TP—Bellcore FGD Terminating Protocol.
FGD-OS—Bellcore FGD Operator Services Signaling.
VFC—Voice feature card. The voice processing card which resides in one of the slots in the Cisco AS5300 platform. Up to five DSP modules (DSPM) can be installed onto the VFC to perform voice processing for up to 30 B channels and potentially 60 B channels. The VFC is a multi-DSP coprocessing card and software package that adds VoIP capabilities to the Cisco AS5300.
VoIP—Voice over IP. The ability to carry normal telephony-style voice over an IP-based internet with POTS-like functionality, reliability, and voice quality. VoIP is a blanket term which generally refers to Cisco's standards-based (for example, H.323) approach to IP voice traffic.
Platforms
This feature is supported on the following platform:
•Cisco AS5300 universal access server
•Cisco AS5850 universal gateway
Determining Platform Support Through Cisco Feature Navigator
Cisco IOS software is packaged in feature sets that support specific platforms. To get updated information regarding platform support for this feature, access Cisco Feature Navigator. Cisco Feature Navigator dynamically updates the list of supported platforms as new platform support is added for the feature.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or release. Under the release section, you can compare releases side by side to display both the features unique to each software release and the features in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions at http://www.cisco.com/register.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
Availability of Cisco IOS Software Images
Platform support for particular Cisco IOS software releases is dependent on the availability of the software images for those platforms. Software images for some platforms may be deferred, delayed, or changed without prior notice. For updated information about platform support and availability of software images for each Cisco IOS software release, refer to the online release notes or, if supported, Cisco Feature Navigator.
Functional Description
The new functionality of T1 CAS for VoIP includes all the T1 CAS and E1/R2 signaling already supported for the Cisco AS5300 in data applications, with the addition of dialed-number and calling-party number capture whenever available.
The implementation of this feature supports the following T1 CAS signaling systems for VoIP applications:
•E&M—E&M signaling is typically used for trunks. It is normally the only way that a CO switch can provide two-way dialing with direct inward dialing. In all the E&M protocols, off-hook is indicated by A=B=1, and on-hook is indicated by A=B=0. If dial pulse dialing is used, the A and B bits are pulsed to indicate the addressing digits. The are several further important subclasses of E&M robbed-bit signaling:
•E&M Wink Start—Feature Group B
In the original Wink Start protocol, the terminating side responds to an off-hook from the originating side with a short wink (transition from on-hook to off-hook and back again). This wink tells the originating side that the terminating side is ready to receive addressing digits. After receiving addressing digits, the terminating side then goes off-hook for the duration of the call. The originating endpoint maintains off-hook for the duration of the call.
•E&M Wink Start—Feature Group D
In Feature Group D Wink Start with Wink Acknowledge protocol, the terminating side responds to an off-hook from the originating side with a short wink (transition from on-hook to off-hook and back again) just as in the original Wink Start. This wink tells the originating side that the terminating side is ready to receive addressing digits. After receiving addressing digits, the terminating side then provides another wink (called an Acknowledgment Wink) that tells the originating side that the terminating side has received the dialed digits. The terminating side then goes off-hook to indicate connection when the ultimate called endpoint has answered. The originating endpoint maintains off-hook for the duration of the call.
•E&M Immediate Start
In the Immediate Start protocol, the originating side does not wait for a wink before sending addressing information. After receiving addressing digits, the terminating side then goes off-hook for the duration of the call. The originating endpoint maintains off-hook for the duration of the call.
•Ground Start / FXS—Ground Start Signaling was developed to aid in resolving glare when two sides of the connection tried to go off-hook at the same time. This is a problem with loop start because the only way to indicate an incoming call from the network to the CPE using loop start was to ring the phone. The 6-second ring cycle left a lot of time for glare to occur. Ground Start Signaling eliminates this problem by providing an immediate seizure indication from the network to the CPE. This indication tells the CPE that a particular channel has an incoming call on it. Ground Start is different than E&M in that the A and B bits do not track each other (that is, A is not necessarily equal to B). When the CO delivers a call, it "seizes" a channel (goes off-hook) by setting the A bit to 0. The Central Office equipment also simulates ringing by toggling the B bit. The terminating equipment goes off-hook when it is ready to answer the call. Digits are usually not delivered for incoming calls.
Channelized T1 Robbed Bit Features
Internet service providers can provide switched 56-kbps access to their customers using the Cisco AS5300. The subset of T1 CAS (robbed bit) supported features are as follows:
Supervisory: Line Side
•fxs-loopstart
•fxs-groundstart
•sas-loopstart
•sas-groundstart
•Modified R1
Supervisory: Trunk Side
•e&m-fgb
•e&m-fgd
•e&m immediate start
Informational: Line Side
•DTMF
Informational: Trunk Side
•DTMF
•MF
Configuration Tasks
The sample configuration is only intended as an example of how to use the commands to configure T1 CAS. It is not an example of a complete configuration for setting up the entire signaling for a telco network.
To configure T1 CAS for use with VoIP, perform the following tasks:
•Configure Voice Port Parameters
•Configure Dial Peers
•Configure T1 CAS voice ports as cas-group for channelized T1 lines.
Note For additional software configuration examples using T1 signaling, see Configuring Channelized T1 or E1. To access the document on Cisco Connection Online (CCO), go the following URL: http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/5300/5300swbk/5300bas.htm#xtocid1968913
Configuring Service Provider T1 CAS
The following sample configuration is an example of how to configure the voice ports as a cas-group for the channelized T1 lines.
Verify
To verify your controller is up and running and no alarms have been reported:
•Enter the show controller t1 or show controller e1 command and specify the port number.
5300# sh cont t1 2
T1 2 is up.
No alarms detected.
Version info of slot 0: HW: 2, Firmware: 16, PLD Rev: 0
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x42,
Board Hardware Version 1.0, Item Number 73-2217-4,
Board Revision A0, Serial Number 06467665,
PLD/ISP Version 0.0, Manufacture Date 14-Nov-1997.
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
Data in current interval (269 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Note the following:
•The controller must report being up.
•No errors should be reported.
Tips
Make sure the show controller t1 output is not reporting alarms or violations.
Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 11.3 command references.
cas-group - (controller t1)
To configure a channel group using CAS signaling, the cas-group command is used to specify the channels/timeslots to be allocated for the CAS group and the CAS signaling type.
cas-group channel timeslots range type signal [[tone] [service]]
no cas-group channel timeslots range type signal [[tone] [service]Two new service type attributes have been added to the cas group command.
Use the no form of this command to disable channel associated signaling for one or more timeslots. The service type are:
•voice or data
For e&m-fgb and e&m fgd, there are also tone type:
•dtmf or mf
•dnis or ani-dnis
For these two CAS signaling types the tone type is always set to mf and dnis is always required. They can be used for both voice and data calls.
Syntax Description
Default
cas-group 0 timeslots 1-24 type e&m-fgb dtmf
Command Mode
Controller configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.2.
This command was implemented on the Cisco AS5850 platform in Cisco IOS Release 12.2(2)XB1.
Use this command to enable an integrated modem to receive and transmit incoming and outgoing call signaling (such as on-hook and off-hook) through each T1 controller.
•If you want to collect DNIS information on a T1 controller, you must manually configure it on the access server.
•DNIS collection is performed only for E&M-fgb, and E&M-fgd.
•To collect DTMF DNIS for E&M-fgb under a controller T1 configuration, issue the cas-group 0 timeslots 1-24 type e&m-fgb dtmf dnis command.
•To collect MF DNIS for E&M-fgb, issue the cas-group 0 timeslots 1-24 type e&m-fgb mf dnis command.
By configuring DNIS as part of the cas-group command, the system can collect DNIS digits for incoming calls which can be directed as VoIP calls, or alternately can be redirected to specific modem pools setup for different customers or uses. To support modems you must be running MICA modems in the system and have at least 10% of your total modems in the default modem pool.
The following example configures the required signaling to support modem pooling and the digital number identification service (DNIS) over channelized T1 lines on a Cisco AS5300.
Example Configuration
router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)# controller t1 0
router(config-controller)# cas-group 0 timeslots 1-24 type e&m-fgb dtmf dnis
router(config-controller)# exit
router(config)#
router(config)# modem-pool accounts1
router(config-modem-pool)# pool-range 30-50
router(config-modem-pool)# called-number 2000 max-conn 21
router(config-modem-pool)# exit
router(config)#
Note T1 CAS fgd is asymmetric. When calling the switch, we only generate DNIS. When receiving form the CO, we get both ANI and DNIS.
Posted: Tue Jun 5 22:55:12 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.