Table Of Contents
Single and High-Density Voice over IP Support for the Cisco AS5300/Voice Gateway
Frame Relay/HDLC/PPP Encapsulation and Backhaul of VoIP Traffic
Single Density Voice Support with DSPM-542
High-Density Voice Support with DSPM-549
Open Settlements Protocol For Packet Voice
Debit Card Billing/RADIUS/Vendor Specific Attribute Enhancements for Packet Telephony
Interactive TCL-based Voice Response
Restrictions for Backhaul/Encapsulation
Encryption Limitation on Open Settlements Protocol for Packet Voice
Cisco IOS Release and VCWare Compatibility
Identifying Voice Feature Cards
Replacing Firmware with VCWare in VCWare Mode
Replacing Firmware with VCWare in ROM Monitor Mode
Verifying VCWare or ROM Monitor Firmware Replacement
Configuring Voice Preference Groups
Configuration, Verification, and Troubleshooting Tips
Replacing ROM Monitor Firmware
Creating and Applying a Voice Preference List
Single and High-Density Voice over IP Support for the Cisco AS5300/Voice Gateway
Feature Overview
Cisco IOS Release 12.0(2)XH was the first (early deployment) release to support single and high-density VoIP support for the Cisco AS5300 (96/120 calls per system). Cisco IOS Release 12.0(4)XH1 (this release) adds support for the following features:
•
H.323 Version 2
•
•
•
•
•
•
•
For complete information about Cisco IOS Release 12.0 XH, see Release Notes for Cisco AS5300 Universal Access Server/Voice Gateway for Cisco IOS Release 12.0 XH/XH1.
New with VCWare
Cisco IOS 12.0(4)XH1 and VCWare Version 4.10 are the first releases that introduce feature parity (except for density) between the earlier generation AS53-6VOX (TI-C542-based) systems and the latest AS53-VOXD (TI-C549-based) high-density systems: There are now C542 and C549 versions of VCWare 4.10. For more information on Cisco IOS and VCWare releases, see "Cisco IOS Release and VCWare Compatibility."
Note
The following features are supported with VCWare Version 4.10:
•
•
•
•
Note
•
•
•
•
•
•
For more information about CODEC feature sets, see "New and Changed Information" in Release Notes for Cisco VCWare Version 4.10 for Cisco AS5300/Voice Gateway (78-6309-01).
Frame Relay/HDLC/PPP Encapsulation and Backhaul of VoIP Traffic
12.0(4)XH1 is the first Cisco AS5300/Voice Gateway IOS release that supports the use of serial ports or T1/E1 ports for Frame Relay/HDLC/PPP encapsulation and backhaul of VoIP traffic: All previous Cisco IOS releases limited the Cisco AS5300/Voice Gateway to passing calls between TDM (T1/E1) ports and Ethernet (10/100 Base T) ports and only supported the use of the earlier generation 4CT1/4CE1 feature cards. Encapsulating and backhauling VoIP traffic onto Frame Relay/HDLC/PPP links required a separate router on the same Ethernet network to encapsulate and pass VoIP traffic into a serial backhaul link (and vice versa).
Cisco IOS Release 12.0(4)XH1 supports the use of the Cisco AS5300 4CT1+ serial port and 4CE1+ serial port feature cards, previously only supported for AS5300 access server (modem/ISDN termination) applications.
Note
Furthermore, if you use AS5300/Voice Gateway ports for Frame Relay, HDLC, or PPP encapsulation, Cisco recommends that you only support voice traffic. IP Precedence and Weighted Fair Queueing mechanisms may not guarantee acceptable voice quality and low latency in mixed voice and data environments. For example, FRF.12 is not supported on the AS5300/Voice Gateway in this release.H.323 Version 2 Support
H.323 Version 2 Support upgrades Cisco IOS software to comply with the mandatory requirements in the Version 2 specification. This upgrade enhances the existing Voice Over IP GateWay, the Multimedia Conference Manager (GateKeeper and Proxy), and the dual tone multifrequency (DTMF) digital relay using H.245.
H.323 Version 2 defines a lightweight registration procedure that requires full registration for initial registration, but uses an abbreviated renewal procedure to update the gatekeeper and minimize overhead. Lightweight registration requires each endpoint to specify a TimeToLive (TTL) value in its Registration Request (RRQ) message.
The H.323 Version 2 gateway supports the registration of fully-qualified E.164 numbers with the gatekeeper for phones connected directly to the gateway. Tunneling through H.225 User-to-User Information Element (UUIE) facilitates transparent handling of supplementary services between two endpoints through a VoIP network. This eliminates the need to interpret various supplementary signaling messages in the VoIP gateways.
For more information, see "Gateway Support for Alternate Gatekeeper."
Single Density Voice Support with DSPM-542
This feature implements voice support on the Cisco AS5300 by using DSPM-542 digital signal processor (DSP) modules.
The benefits of voice features include support for:
•
•
•
•
•
This release supports a C542-based VCWare that provides CODEC and feature interoperability between the earlier generation, TI-C542-based AS5300/Voice Gateways, and the latest high-density versions. This release supports parallel C542-based VCWare/DSPWare and C549-based VCWare/DSPWare.
Note
High-Density Voice Support with DSPM-549
This release implements high-density voice support on the Cisco AS5300 by using DSPM-549 digital signal processor (DSP) modules. When equipped with Voice Feature Cards (VFCs) and voice-enabled Cisco IOS software, the AS5300/Voice Gateway supports carrier-class VoIP and FAX over IP services.
High-density voice support increases the voice capacity of a Cisco AS5300 up to 120 channels. This increase in voice support provides the voice density of up to four T1 lines (96 voice or FAX calls) or four E1 lines (120 voice or FAX calls).
A fully configured AS5300/Voice Gateway can support up to two high-density (48/60 channel) voice feature cards. Therefore, the system supports up to 96/120 simultaneous voice/fax calls (4T1/E1 density).
The benefits of high-density voice features include:
•
•
•
•
•
Open Settlements Protocol For Packet Voice
Internet voice telephony is often used for toll bypass by using an existing data network or the Internet instead of PSTN trunking. Calls of this nature require an originating and terminating gateway to be completed. When the originating and terminating voice gateways are owned by two different carriers, settlement between these carriers is required. The Open Settlements Protocol for Packet Voice project implements a standardized settlement protocol which can be implemented between different vendors gateways and voice settlement servers.
The Cisco gateway-based Open Settlements Protocol interacts between carriers to create a single authentication at initialization. The authentication is the basis for the establishment of a secure communication channel between the Settlement system and the infrastructure component.
Note
This channel then allows the following three types of transactions to be handled:
•
•
•
Note
For more information on the Open Settlement Protocol, see "Settlement for Packet Telephony on Cisco Access Platform."
Debit Card Billing/RADIUS/Vendor Specific Attribute Enhancements for Packet Telephony
The Debit Card feature offers service providers debit accounting for calling services. The Debit Card feature and RADIUS-specific enhancements also support Vendor Specific Attributes (VSA). The Debit Card for Packet Telephony on Cisco AS5300 works in tandem with the Cisco Interactive Voice Response (IVR) feature. The IVR voice scripts have been modified to use Tool Command Language (TCL) scripts.
The feature components consist of IVR functionality in Cisco IOS software that works in connection with an integrated third-party billing system. This includes the ability to maintain per-user credit balance information through a RADIUS interface to the Cisco IOS software. When these features are implemented, the billing system and IOS software functions enable a carrier to authorize voice calls and to debit individual user accounts in real time at the edges of a VoIP network without requiring external service nodes.
For more information on Debit Card Billing, see "Debit Card for Packet Telephony on Cisco Access Platforms."
Interactive TCL-based Voice Response
Cisco is building voice gateways to connect more traditional telephone networks to voice over IP (VoIP) networks. Customers who are installing VoIP networks often need a mechanism at the gateway to present a customized interface to the caller. The interactive voice response (IVR) feature was first made available to customers with Cisco IOS Release 11.(3)NA2 with the Service Provider VoIP feature set. IVR, with the addition of scripts using Tool Command Language (TCL), is being introduced with Cisco IOS Release 12.0(4)XH/XH1, which is compatible with TCLware 1.0.x.
Note
IVR consists of simple voice prompting and digit collection to gather caller information for authenticating the user and identifying the destination. IVR provides the ability to:
•
•
•
•
Note
For more information on TCL scripts, see "Debit Card for Packet Telephony on Cisco Access Platforms." For more information on IVR, see "Configuring Interactive Voice Response for Cisco Access Platforms."
H.323 Alternate Gatekeeper
This release adds support for the H.323 "alternate gatekeeper" field on the AS5300/Voice Gateway. This field was added to provide future support for specific third-party gatekeepers. Cisco gatekeepers do not support this field.
Benefits
The benefits of these high-density voice feature enhancements include:
•
•
•
•
•
Restrictions
The following general restrictions apply to this release:
•
•
•
Restrictions for Backhaul/Encapsulation
Encapsulating and backhauling VoIP traffic onto Frame Relay/HDLC/PPP links requires the use of dedicated routers (such as Cisco 3600, 7200, 7500) on the same Ethernet network to encapsulate and pass VoIP traffic into a serial backhaul link (and vice versa).
Voice quality is directly affected by latency, which affects the CPU load. The following section highlights some key requirements and limitations associated with use of native FR/HDLC/PPP encapsulation for voice applications by using the Cisco AS5300/Voice Gateway.
To maintain high performance—including low latency (less than 200 ms round trip delay)—high-call success rate (99% CSR), and optimal voice quality, Cisco supports the use of native FR/HDLC/PPP encapsulation with the following restrictions:
•
•
•
•
•
CautionDo not enable CRTP on the AS5300/Voice Gateway, except for a few very limited cases, specifically where less than 10 - 24 total calls will be processed. Offload Cisco routers (for example 7200/7500 series) dedicated for any CRTP requirements. CRTP is processed switched and creates a significant load on the main AS5300 CPU/router resource.
Even in the case of very low-expected call volumes, first test a simulation of the proposed network environment to validate achievable call success rate and low latency with CRTP enabled. If you need native CRTP, limit the call rate to 1 call every 2 seconds.
If you do use CRTP for more than 10 - 24 simultaneous calls, it will have a negative effect on the sustained call success rate, packet latency, and voice quality of the AS5300.
These caveats are provided for guidance, and there are a wide variety of other backhaul scenarios that can be supported by the AS5300/Voice Gateway, particularly for low-volume applications. When considering other configurations, consider that there are many other VoIP features, processes, and conditions that contribute to system load, including:
•
•
•
•
•
•
•
Encryption Limitation on Open Settlements Protocol for Packet Voice
Open Settlements Protocol for Packet Voice is offered only in crypto images; they are under export controls. All users must be entitled before they can receive 56 or 56i images. See "Related Documents" for information on applying for entitlement.
Once you are entitled, you can see crypto images in the upgrade planner and you do not have to entitle yourself again—unless you come from a different host. You do not have to entitle yourself for every release because entitlement is good for all releases.
Related Documents
For related information on this feature, see the following documents:
•
•
•
Supported Platform
Cisco AS5300
Supported MIBs and RFCs
MIBs
•
•
•
•
•
•
For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB website on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
None
Prerequisites
The following Cisco IOS Release images are required for 549 DSP modules:
•
•
Note
Before you can configure your Cisco AS5300 to use VoIP, you must first complete the tasks listed below.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Cisco IOS Release and VCWare Compatibility
The Cisco VCWare compatibility matrix contains information about Cisco IOS and VCWare compatibility for the Cisco AS5300/Voice Gateway.
Note
Table 1 Cisco IOS Release and VCWare Compatibility Matrix
Configuration Tasks
Perform the following tasks to configure high-density voice for the Cisco AS5300:
•
•
•
•
Identifying Voice Feature Cards
The following steps identify the voice cards in the system and determine whether the VFC is in VCWare mode or ROM monitor mode. The mode determines how you download software to the VFC. If VCWare is not loaded on the VFC, you can use the ROM monitor mode to download the VCWare. Otherwise, the VCWare mode is active.
1
Enter enable mode (also called Privileged EXEC mode).
Enter the password.
You have entered enable mode when the prompt changes to router#.
2
Determine the type of voice feature card (requires VCWare mode).
If this command returns c542 or does not work, go to Step 4.
3
Determine the complexity mode. The first line of the return (cor-vfc) identifies the card as being in high-complexity mode if the return is in the form: cor-vfc-hc-1.x.x.x.bin.
If the return is in the form: cor-vfc-mc-l.x.x.x.bin, the card is in medium complexity mode.
4
Determine the number of voice cards in the system, the slot number for each card, and the VFC mode (VCWare or ROM monitor) in which you are running.
The VFC mode is indicated as follows:
•
or
•
Note the location and the mode type for each voice card. You will need this information when you upgrade the VCWare.
Go to one of the following sections to continue the procedure to upgrade the VCWare:
•
or
•
Replacing Firmware with VCWare in VCWare Mode
Use these steps to download new voice software if your voice card is running in VCWare mode. When downloading from a diskette, first copy the software from the diskette to a TFTP server.
CautionErasing the VFC files can result in system outage or the corruption of your VFC board. Ensure that you have the correct software version on your TFTP server.
1
See the Caution that precedes this table.
Erase the contents of the VFC Flash memory in the selected voice card. You must erase the previous files to load a new image.
If this command fails, go to "Replacing Firmware with VCWare in ROM Monitor Mode."
2
(Optional) Verify that the VFC Flash memory is empty.
3
Source file name? /path/filenameDestination file name [filename]? filename! note, the destination filename is *IMPORTANT*Accessing file 'filename' onipaddress...Loading filename from ipaddress (via Ethernet0):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - size bytes]Use the first copy command with Cisco IOS Release Versions 12.0(2)XH, 12.0(4)XH, 12.0(4)XH1, and 12.0(5)T2. Use the second copy command (no colons) with Cisco IOS Release Version 11.3(2)NA or later releases.
Use TFTP to download the new VCWare to VFC Flash memory. In this example, slot 1 is the default.
Note: Begin the destination image name with "vcw-" (all lowercase). Do not use any other character in front of vcw-; therefore, do not include a directory path at the beginning of the image name. Make sure that you enter the name correctly. If one character or space is wrong, the file is not recognized and is not copied.
4
Verify that VCWare is in the VFC Flash memory by providing a list of files.
5
Reload the VFC code from Flash memory for the specified slot before you unbundle the new VFC image.
6
Unbundle the DSPWare from the VCWare and configure the default file and capability lists with default values. This rewrites the default-file and capabilities lists. (See Steps 8 and 9.)
Press y when the prompt appears.
7
Verify that the DSPWare is unbundled by providing a list of files.
8
Verify that the default file list is initialized by providing a list of files.
9
5300# show vfc slot_number cap-list
5300#
Verify that the capability list is populated by providing a list of files.
10
5300# reloadReboot the Cisco AS5300 so these changes take effect.
Replacing Firmware with VCWare in ROM Monitor Mode
Use these steps to download new voice software if your voice card is running in ROM monitor mode. When downloading from a diskette, first copy the software from the diskette to a TFTP server, then, follow these steps.
CautionErasing the VFC files can result in system outage or the corruption of your VFC board. Ensure that you have the correct software version on your TFTP server before continuing. For more information on software versions, see "Cisco IOS Release and VCWare Compatibility."
Verifying VCWare or ROM Monitor Firmware Replacement
To check that you have successfully downloaded the software:
Step 1
5300# show vfc 1 dirFiles in slot 1 VFC flash:File Name Size (Bytes)1 . vcw-vfc-mz.c549.3.0.bin 4661682 . btl-vfc-l.3.0.bin 41743 . btj-vfc-l.3.0.bin 38684 . jbc-vfc-l.3.0.bin 127565 . cor-vfc-hc-l.3.0.bin 477546 . bas-vfc-hc-l.3.0.bin 386347 . fax-vfc-hc-l.3.0.bin 807948 . cdc-g711-hc-l.3.0.bin 2189 . cdc-g726-hc-l.3.0.bin 21810. cdc-g729-hc-l.3.0.bin 3151611. cdc-g728-hc-l.3.0.bin 2433412. cdc-g723.1-hc-l.3.0.bin 47234Step 2
5300# show vfc 1 def (full word is default-file)Default File List for VFC in slot 1:1. btl-vfc-l.3.0.bin2. cor-vfc-hc-l.3.0.bin3. bas-vfc-hc-l.3.0.bin4. cdc-g729-hc-l.3.0.bin5. fax-vfc-hc-l.3.0.bin6. jbc-vfc-l.3.0.bin7. btj-vfc-1.3.0.bin5300# show vfc 1 cap-listCapability List for VFC in slot 1:1. cor-vfc-hc-l.3.0.bin2. bas-vfc-hc-l.3.0.bin3. fax-vfc-hc-l.3.0.bin4. cdc-g711-hc-1.3.0.bin5. cdc-g726-hc-1.3.0.bin6. cdc-g729-hc.1.3.0.bin7. cdc-g728-hc-1.3.0.bin8. cdc-g723.1-hc-1.3.0.bin5300#Configuring Voice Preference Groups
To create preferences lists that can be applied to any dial peer:
Step 1
Step 2
Configuration, Verification, and Troubleshooting Tips
If you have trouble downloading the voice card software in VCWare mode, see the following suggestions:
Step 1
5300# show vfc 1 boardVFC board state is UP, vfc status VCWARE running(0x4)VFC board in slot 1 with 24 dsps5300#Step 2
5300# show vfc 1 ver vcwVoice Feature Card in Slot 1:VCware Version : 3.0ROM Monitor Version : 1.2DSPware Version : 3.0Technology : C549Step 3
If the system crashes after the new VFC cards have been placed in the system, it could mean that one or both of the VFC cards are not seated properly. Pull each VFC card partially out of its slot and reseat it firmly.
If a download failure occurs in VCWare mode and the VFC falls back to ROM monitor mode, see "Replacing Firmware with VCWare in ROM Monitor Mode."
Make sure that you count the number of DSP modules on both VFC cards to determine the total number of voice resources. Cisco supports up to five DSP modules per VFC. Then, enter the show version command to confirm that the total number of functioning voice resources equal the number of voice resources installed.
Configuration Examples
This section provides the following configuration examples:
•
•
Replacing VCWare Firmware
See the following example to download new voice software for a voice card running in VCWare mode:
5300# erase vfc 2This will erase the contents of VFC Flash.Continue ?[y/n]:yesThis will take some time. Please, wait...vfc5300# show vfc 2 directory5300# copy tftp: vfc:Address or name of remote host []?223.255.212.244Source file name []? /path/vcw-vfc-mz.c549.3.0.binDestination file name []? vcw-vfc-mz.c549.3.0.binAccessing tftp://223.255.212.244/path/vcw-vfc-mz.c549.3.0.bin...Loading vcw-vfc-mz.c549.3.0.bin from 223.255.212.244(via Ethernet0):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 491256/982016 bytes]5300# show vfc 2 directory5300# clear vfc 25300# unbundle vfc 2Do you want to continue ? [y/n]: y5300# show vfc 2 directory5300# show vfc 2 default-file5300# show vfc 2 cap-list5300# reloadReplacing ROM Monitor Firmware
See the following example to download new voice software for a voice card running in ROM monitor mode:
5300# clear vfc 1 purgedebug vfc 1 startdebug vfc 1 cons flash eraseThis will erase the contents of VFC Flash.Continue ?[y/n]: yThis will take some time. Please, wait...vfc5300# copy tftp: vfc:Voice card slot number 1Address or name of remote host [UNKNOWN]? 223.255.212.244Source file name? /path/vcw-vfc-mz.c549.3.0.binDestination file name [vcw-vfc-mz.c549.3.0.bin]? vcw-vfc-mz.c549.3.0.bin! note, the destination filename is *IMPORTANT*Accessing file 'vcw-vfc-mz.c549.3.0.bin' on 223.255.212.244...Loading vcw-vfc-mz.c549.3.0.bin from 223.255.212.244 (via Ethernet0):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 291292/291328 bytes]5300# show vfc 1 technology5300# clear vfc 1Do you really want to reset this card ? [y/n] yPlease, wait...5300# unbundle vfc 1Do you want to continue ? [y/n]: y5300# show vfc 1 directory5300# show vfc 1 default-file5300# show vfc 1 cap-list5300# reloadCreating and Applying a Voice Preference List
See the following example to create preference list 99 which can be applied to any dial peer:
5300(#conf tEnter configuration commands, one per line. End with CNTL/Z.5300(config)#voice class codec 995300(config-class)#codec preference 1 g711alaw5300(config-class)#codec preference 2 g711ulaw bytes 805300(config-class)#codec preference 3 g723ar535300(config-class)#codec preference 4 g723ar63 bytes 1445300(config-class)#codec preference 5 g723r535300(config-class)#codec preference 6 g723r63 bytes 1205300(config-class)#codec preference 7 g726r165300(config-class)#codec preference 8 g726r245300(config-class)#codec preference 9 g726r32 bytes 805300(config-class)#codec preference 10 g7285300(config-class)#codec preference 11 g729br85300(config-class)#codec preference 12 g729r8 bytes 505300(config-class)#end#5300(config)#See the following example to apply preference list 99 to dial-peer 1919:
5300(#conf tEnter configuration commands, one per line. End with CNTL/Z.5300(config)#voice class codec 995300(config-class)#codec preference 1 g711alaw5300(config-class)#codec preference 2 g711ulaw bytes 805300(config-class)#codec preference 3 g723ar535300(config-class)#codec preference 4 g723ar63 bytes 1445300(config-class)#codec preference 5 g723r535300(config-class)#codec preference 6 g723r63 bytes 1205300(config-class)#codec preference 7 g726r165300(config-class)#codec preference 8 g726r245300(config-class)#codec preference 9 g726r32 bytes 805300(config-class)#codec preference 10 g7285300(config-class)#codec preference 11 g729br85300(config-class)#codec preference 12 g729r8 bytes 505300(config-class)#end#5300(config)##(config)#dial-peer voice 1919 voip(config-dial-peer)#voice-class codec 99(config-dial-peer)#endYou can verify this action by entering the show ru command:#show rudial-peer voice 1919 voipvoice-class codec 99!voice class codec 99codec preference 1 g711alawcodec preference 2 g711ulaw bytes 80codec preference 3 g723ar53codec preference 4 g723ar63 bytes 144codec preference 5 g723r53codec preference 6 g723r63 bytes 120codec preference 7 g726r16codec preference 8 g726r24codec preference 9 g726r32 bytes 80codec preference 10 g728codec preference 11 g729br8codec preference 12 g729r8 bytes 50Command Reference
This section documents the new calling-number command. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references and the online feature module: High-Density Voice over IP Support for the Cisco AS5300/Voice Gateway for Cisco IOS release 12.0(2)XH.
In Cisco IOS Release 12.0(1)T or later releases, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:
command | {begin | include | exclude} regular-expression
See the following example of the show atm vc command where you want the command output to begin with the first line where the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, see the Cisco IOS Release 12.0(1)T feature module CLI String Search.
calling-number
Enter the calling-number dial-peer configuration command to enable or disable automatic number identification (ANI) passing on outgoing calls for T1 CAS (channel associated signalling) configured interfaces. Enter the no form of this command to disable ANI configuration.
calling-number {range string1 string2} | {sequence string1 string2 string3 string 4 string 5} | {null}
no calling-number
Syntax Description
Defaults
none
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command is designed for plain old telephone service (POTS) dial peers only.
You can use up to two information digits to prepend to the ANI string.
Examples
See the following example to generate an ANI with the prefix 408555 and rotating through 1000 to 1005 for each call using this peer:
5300(config-dial-peer)# dial-peer voice 1 pots5300(config-dial-peer)# calling-number range 4085551000 4085551005See the following example to generate strings to be substituted for ANIs for the next five calls using this peer:
5300(config-dial-peer)# dial-peer voice 1 pots5300(config-dial-peer)# calling-number sequence 1111 1112 1113 1114 1115List of Terms and Acronyms
AAA—Authentication, Authorization, and Accounting.
ANI—Answer Number Identification (calling party number).
CLI—Command Line Interface, IOS user command, and configuration system.
CO—Central Office.
CRTP—Compressed Real Time Protocol.
D-channel—Signaling channel; pathway for out-of-band call control.
DMA—Direct Memory Access (used by VC to transfer data to the AS5300 motherboard).
DNIS—Dialed Number Identification Service.
DSP—Digital Signal Processor.
DTMF—Dual Tone Multifrequency.
E.164 Address—In this context, the telephone number.
EANA—Exchange Access North American.
FGD—Feature Group D. Identifies a standardized service available to carriers delivered on a channelized T1 line.
Gateway—H.323 VoIP gateway is the point where a circuit-switched call is encoded and encapsulated into IP packets.
GateKeeper—In the context of this feature module, H.323 VoIP gatekeeper refers to the Cisco IOS-based gatekeeper.
H.323 RAS—Registration, Admission, and Status. The RAS signaling function performs registration, admissions, bandwidth changes, status, and disengagement procedures between the VoIP Gateway and Gatekeeper.
Hairpin Re-routing—also known as Hairpinning. Rerouting a call back to the PSTN at the originating VoIP gateway-usually because a VoIP route is unavailable or the PSTN is judged to be the most cost-effective alternative.
HSRP—Hot Standby Routing Protocol. Previously existing protocol for failover to standby gatekeeper/router in a redundant router configuration.
ISAC —ISDN Subscriber Access Controller.
ISDN —Integrated Services Digital Network.
ITU —International Telecommunication Union (formerly CCITT).
IVR—Interactive Voice Response. The system plays a message to the calling party and can also collect information from the calling party.
LEC —Local Exchange Carrier.
On-net—In this context of this feature module, on-net calls are voice over IP calls on the IP Network.
Off-net—In this feature module, off-net calls are those that are circuit-switched calls, whether they are switched by the PSTN or a PBX.
PBX—Private Branch eXchange.
PRI —ISDN Primary Rate Interface.
PSTN —Public Switched Telephone Network.
Q.931—ITU-T recommendation for Digital Subscriber Signalling System No. 1 Network Layer.
RTP—Real Time Protocol.
SNMP—Simple Network Management Protocol.
TDM—Time Division Multiplexing.
VFC—Voice Feature Card.
VoIP—Voice over IP.
