Dial Peer Enhancements
Available Languages
Table Of Contents
Supported Standards, MIBs, and RFCs
Configuring the Destination Pattern Dial String Using New Regular Expression Symbols
Configuring Number-Type Matching
Configuring the Dial Peer to Strip Matched Digits (POTS Dial Peers only)
Configuring Digit Translation Rules for Dial Peer Call Legs
Monitoring and Maintaining Digit Manipulation and Translation
voip-incoming translation-rule
Dial Peer Enhancements
Feature History
12.1(1)T
This feature was introduced.
12.1(5)XM2
Support was added for the Cisco AS5350 and Cisco AS5400 universal gateways.
This feature module describes the Dial Peer Enhancements feature support.
This feature has been available in earlier releases on other platforms. For example, Cisco IOS Release 12.1(1)T introduced this feature for the Cisco AS5300 universal access server. Refer to the following table, "Support for Dial Peer Enhancements in Cisco IOS Releases", for more information on this feature for previous releases on other platforms.
This feature module includes information on the benefits of this feature, supported platforms, related documents, and more.
This document includes the following sections:
•
Supported Standards, MIBs, and RFCs
•
Feature Overview
The dial peer configuration enhancements described in this document were previously implemented in earlier releases for Voice over IP (VoIP) on several platforms, and also, for some platforms for Voice over Frame Relay (VoFR) and Voice over ATM (VoATM).
This document includes a description of the implementation of these enhancements for the already supported platforms, such as the Cisco 2600 series, Cisco 3600 series, and Cisco MC3810 series. For more information on the earlier implementation on other platforms, see the Cisco IOS Release 12.1(1)T online documentation Dial Peer Enhancements.
Table 1 lists the Cisco IOS release in which these dial-peer enhancements were first implemented for each voice technology on the currently supported hardware platforms..
The following are the new dial-peer enhancements supported in this release:
•
Beginning in this release, additional dial string symbols are supported that you use with the destination-pattern dial-peer configuration command to establish the digit pattern.
For configuration information and a list of the dial string symbols supported, see the "Configuring the Destination Pattern Dial String Using New Regular Expression Symbols" section.
•
To match on a number type for a dial peer call leg, the numbering-type command is used in dial-peer configuration mode. Number-type matching is supported on Plain Old Telephone Service (POTS), VoIP, VoFR, and VoATM dial peers.
For configuration procedures, see the "Configuring Number-Type Matching" section.
•
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. A new command called digit-strip makes this default behavior an option. The digit-strip option is supported on POTS dial peers only.
For configuration procedures, see the "Configuring the Dial Peer to Strip Matched Digits (POTS Dial Peers only)" section.
•
When configuring your dial peers, you are provided with an option called the translation rule. This rule applies a translation rule to a calling party number (Automatic Number Identification [ANI]) or a called party number (Dial Number Information Service [DNIS]) for both incoming and outgoing calls within Cisco H.323 voice-enabled gateways. Also, the rule allows translation of the type of number. Refer to the Q.931 ITU specification for details.
For configuration procedures, see the "Configuring Digit Translation Rules for Dial Peer Call Legs" section.
Benefits
Reduced Number of Dial Peers
Currently, dial-peer configuration needs multiple dial peers to support a dialing plan. The dial-peer enhancements reduce the amount of effort in producing dial peer entries, improves VoIP system performance significantly because of less dial peer search, and uses less memory.
Digit Manipulation
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. A new command, digit-strip, makes this default behavior an option. This means that you can easily get caller ID and restriction information, and that do not have to make long-distance calls between small, neighboring countries.
Restrictions
None.
Related Documents
•
•
Supported Platforms
•
•
•
•
•
•
Supported Standards, MIBs, and RFCs
Standards
No new or modified standards are supported by this feature.
MIBs
No new or modified MIBs are supported by this feature.
To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to the Cisco MIB web site on Cisco Connection Online (CCO) at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
No new or modified RFCs are supported by this feature.
Prerequisites
The Cisco AS5350 and Cisco AS5400 do not support the Mica Modem Card, Microcom Modem Card, or VoIP Feature Card. Voice and modem functions are provided by the Universal Port Dial Feature card running SPE firmware. See the Cisco AS5350 Universal Gateway Card Installation Guide and the Cisco AS5400 Universal Gateway Card Installation Guide for more information. All references to the Cisco AS5300 in this document apply to the Cisco AS5350 and Cisco AS5400 platforms with the following exceptions:
•
•
•
Other Prerequisites
Before you can configure your platform to configure the dial-peer enhancements, you must do the following:
•
•
Configuration Tasks
See the following sections for configuration tasks for the Dial Peer Enhancements feature. Each task in the list is identified as either optional or required.
To configure the different dial-peer enhancements, see the following sections:
•
•
•
•
Configuring the Destination Pattern Dial String Using New Regular Expression Symbols
In this release, new dial string symbols have been added that provide you with new options for manipulating your dial string. The following new dial string symbols have been added:
•
•
•
•
•
Table 2 lists the new and previously existing dial string symbols that are supported and how they are used.
Table 2 Symbols Used in Dial Peer and Regular Expression Comparison
Indicates that a previous digit/pattern occurred zero or multiple times; similar to a wild card "*" used in a regular expression rule.
Yes / Yes
Indicates a sequence of one or more matches of the pattern.
Yes / Yes1
Indicates a pattern followed by "?" matching zero or one time. Enter ctrl-v before entering ? from your keyboard.
Yes / Yes
Indicates a single character.
Yes / Yes
Indicates a range. A range is a sequence of characters enclosed in "[ ]" and only numeric characters "0" to "9" are allowed in the range; similar to a regular expression rule.
Yes / Yes
Indicates a pattern, and is the same as the regular expression rule.
Yes / Yes
Indicates a pattern matching the null string at the end of the input string.
Yes/No
Indicates a character followed by a single character matching the first character, or a single character with no other significance (matching that character)
Yes/No
Indicates a match to the beginning of the string.
Yes/No
1 The "+" symbol can be part of dialing numbers in some countries, where "+" is always a leading digit in the dialed number. However, this does not conflict with the regular expression rule; "+" in regular expressions will never be a leading symbol.
To configure the dial-peer destination pattern in conjunction with the dial string symbols now supported in this release, enter the following commands beginning in global configuration mode:
Step 1
Router(config)# dial-peer voice number
{pots | voip|vofr | voatm}Enters dial-peer configuration mode.
Step 2
Router(config-dial-peer)# destination-pattern [+]string[T]
Specifies the destination pattern. You can use the symbols listed in Table 2 as part of the string digit pattern.
For more information, see the "destination-pattern" section
Configuring Number-Type Matching
Number-type matching is used in dial-peer configuration mode to match on a number type for a dial peer call leg. To configure number-type matching using the numbering-type command in dial-peer configuration mode, enter the following commands beginning in global configuration mode:
Configuring the Dial Peer to Strip Matched Digits (POTS Dial Peers only)
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 digit-strip command makes this behavior an option.
Digit stripping is enabled by default. To disable digit strip for a POTS dial peer, enter the following commands beginning in global configuration mode:
Step 1
Router(config)# dial-peer voice number pots
Enters dial-peer configuration mode to configure a POTs peer.
Step 2
Router(config-dial-peer)# no digit-strip
Disables digit-strip.
To reenable digit strip for a POTS dial peer, enter the following commands beginning in global configuration mode:
Step 1
Router(config)# dial-peer voice number pots
Enters dial-peer configuration mode to configure a POTs peer.
Step 2
Router(config-dial-peer)# digit-strip
Enables digit-strip.
For more information about how the digit strip command, see the "digit-strip" section.
Configuring Digit Translation Rules for Dial Peer Call Legs
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.
A POTS dial peer points to a voice-port on the router, and the destination of a voice network 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:
Timesaver
To enter the translation-rule configuration mode and specify a rule, enter the following commands in global configuration mode:
Note
To create additional rules to apply to the translation-rule, repeat step 2.
To apply a rule to an inbound POTS call leg, enter the following commands beginning in global configuration mode:
To apply a rule to an outbound VoIP call leg, enter the following commands beginning in global configuration mode:
To apply a rule to a VoIP call that originates from an H.323 node, enter the following global configuration command:
Note
To apply a translation rule to an outbound POTS call leg, enter the following commands beginning in global configuration mode:
Verifying Digit Translation
To verify the digit translation, enter the test translation-rule global-configuration command.
Router# test translation-ruletranslation-rule 21Rule 1 527.% 1408527 subscriber internationalRule 2 7.% 1408527 abbreviated internationalRouter# test translation-rule 21 45678 abbreviatedRouter#*Jan 19 16:39:14.578:The replace number 45614085278Router#Monitoring and Maintaining Digit Manipulation and Translation
To monitor and maintain digit manipulation an translation rules, enter the following command in EXEC mode:
router# show translation-rule [name-tag]
Displays information about the rules that have been configured for a specific translation name.
Configuration Example
The following example includes a translation that uses the "%" symbol so that zero or matches of the preceding character/digit:
dial-peer voice 2 voipdestination-pattern 1..........translate-outgoing called-number 1session target rastranslation-rule 1rule 0 10.% 0rule 1 11.% 1rule 2 12.% 2rule 3 13.% 3rule 4 14.% 4rule 5 15.% 5rule 6 16.% 6rule 7 17.% 7rule 8 18.% 8rule 9 19.% 9Command Reference
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release12.1 command reference publications.
The following modified commands are described in this section:
•
•
destination-pattern
To specify either the prefix or the full E.164 telephone number (depending on your dial plan) to be used for a dial peer, use the destination-pattern command in dial-peer configuration mode. Use the no form of this command to disable the configured prefix or telephone number.
destination-pattern [+]string[T]
no destination-pattern [+]string[T]
Syntax Description
Defaults
Enabled with a null string.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Use the destination-pattern command to define the E.164 telephone number for a dial peer.
This pattern is used to match dialed digits to a dial peer. The dial peer is then used to complete the call. When a router receives voice data, it compares the called number (the full E.164 telephone number) in the packet header with the number configured as the destination pattern for the voice-telephony peer. The router then strips out the left-justified numbers corresponding to the destination pattern. If you have configured a prefix, the prefix is appended to the front of the remaining numbers, creating a dial string, which the router then dials. If all numbers in the destination pattern are stripped-out, the user receives a dial tone.
There are certain areas in the world (for example, in certain European Union countries) where valid telephone numbers can vary in length. Use the optional control character t to indicate that a particular destination-pattern value is a variable-length dial string. In this case, the system does not match the dialed numbers until the interdigit timeout value has expired.
Note
Examples
The following example configures the E.164 telephone number, 555-7922, for a dial peer:
Router(config)# dial-peer voice 10 potsRouter(config-dial-peer)# destination-pattern +5557922The following example configures a destination pattern in which the pattern "43" is repeated multiple times preceding the digits "555":
Router(config)# dial-peer voice 1 voipRouter(config-dial-peer)# destination-pattern 555(43)+The following example configures a destination pattern in which the preceding digit/pattern was repeated multiple times:
Router(config)# dial-peer voice 2 voipRouter(config-dial-peer)# destination-pattern 555%The following example configures a destination pattern in which the digit numbers range between 5553409 and 5559499:
Router(config)# dial-peer voice 3 vofrRouter(config-dial-peer)# destination-pattern 555[3-9]4[0=9]9The following example configures a destination pattern in which the digit numbers range between 5551439, 5553439, 5555439, 5557439, and 5559439:
Router(config)# dial-peer voice 4 voatmRouter(config-dial-peer)# destination-pattern 555[13579]439Related Commands
digit-strip
To enable digit stripping on a POTS dial-peer call leg, use the digit-strip dial-peer configuration mode command. To disable digit stripping on the dial-peer call leg, use the no form of this command.
digit-strip
no digit-strip
Syntax Description
There are no arguments or keywords for this command.
Defaults
Digit stripping is enabled.
Command Modes
Dial-peer configuration mode
Command History
Usage Guidelines
The digit-strip command is supported on POTS dial peers only.
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.
Table 3 lists a series of dial peers configured with a specific destination pattern, and shows the longest matched number after the digit is stripped based on the dial string 408 555-3048.
Table 3
Digit-Strip Example for Longest Matched Number
Table 4 lists a series of dial peers configured with a specific destination pattern, and shows the number after the digit strip based on the dial string 408 555-3048 and the different dial peer symbols applied.
Table 4
Digit Strip Example for Matching the Destination Pattern
Examples
The following example disables digit stripping on a POTS dial peer:
Router(config)# dial-peer voice 100 potsRouter(config-dial-peer)# no digit-stripRelated Commands
numbering-type
To match on a number type for a dial-peer call leg, use the numbering-type dial-peer configuration command. To remove the numbering type for a dial-peer call leg, use the no form of this command.
numbering-type {international | abbreviated | national | network | reserved | subscriber | unknown}
no numbering-type {international | abbreviated | national | network | reserved | subscriber | unknown}
Syntax Description
Command Modes
Dial-peer configuration mode
Command History
Usage Guidelines
The numbering-type command is supported for POTS, VoIP, VoFR, and VoATM dial peers. The number-type options are implemented as defined by the ITU Q.931 specification.
Examples
The following example shows how to configure a POTS dial peer for network usage:
Router(config)# dial-peer voice 100 potsRouter(config-dial-peer)# numbering-type networkThe following example shows how to configure a VoIP dial peer for subscriber usage:
Router(config)# dial-peer voice 200 voipRouter(config-dial-peer)# numbering-type subscriberRelated Commands
rule
To apply a translation rule to a calling party number or a called party number for both incoming and outgoing calls, use the rule translation-rule configuration command. To remove the translation rule, use the no form of this command.
rule name-tag input-matched-pattern substituted-pattern [match-type substituted-type]
no rule name-tag input-matched-pattern substituted-pattern [match-type substituted-type]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Translation-rule configuration
Command History
Usage Guidelines
When configuring your dial peers, you are provided with an option called the translation rule. This applies a translation rule to a calling party number (Automatic Number Identification [ANI]) or a called party number (Dial Number Information Service [DNIS]) for both incoming and outgoing calls within Cisco H.323 voice-enabled gateways. Also, the rule allows translation of the type of number.
Examples
The following example applies a translation-rule. If a called number starts with 5552205 or 52205, then the translation-rule 21 will use the rule command to forward the number to 14085552205 instead.
Router(config)# translation-rule 21Router(config-translate)# rule 1 555.% 1408555 subscriber internationalRouter(config-translate)# rule 2 7.% 1408555 abbreviated internationalIn the next example, if a called number is either 14085552205 or 014085552205, then after the execution of the translation-rule 345, the forwarding digits will be 52205. If the match-type is configured and the type is not "unknown," then the dial peer matching will be required to match input string numbering type.
Router(config)# translation-rule 345Router(config-translate)# rule 1 .%555.% 7 any abbreviatedRelated Commands
show translation-rule
To display the contents of the rules that have been configured for a specific translation name, use the show translation-rule EXEC command.
show translation-rule [name-tag]
Syntax Description
name-tag
(Optional) The tag number by which the rule set will be referenced. This is an arbitrarily chosen number. Range is 1 through 2147483647.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command gives detailed information about the configured rules under this rule name. If the name tag is not entered, a complete display of all the configured rules will be shown.
Examples
The following example shows output for the show translation-rule command:
Router# show translation-ruleTranslation rule address:0x61AB94F8Tag name:21Translation rule in_used 1**** Xrule rule table *******Rule :1in_used state:1Match pattern:555.%Sub pattern:1408555Match type:subscriberSub type:international**** Xrule rule table *******Rule :2in_used state:1Match pattern:8.%Sub pattern:1408555Match type:abbreviatedSub type:internationalTranslation rule address:0x61C2E6D4Tag name:345Translation rule in_used 1**** Xrule rule table *******Rule :1in_used state:1Match pattern:.%555.%Sub pattern:7Match type:ANYSub type:abbreviatedTable 5
show translation-rule Field Descriptions
Related Commands
test translation-rule
To test the execution of the translation rules on a specific name tag, use the test translation-rule global configuration command. To disable, use the no form of this command.
test translation-rule name-tag input-number [input-numbering-type]
no test translation-rule name-tag input-number [input-numbering-type
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Examples
The following shows output for the test translation-rule command:
Router# translation-rule 21Rule 1 555.% 1408555 subscriber internationalRule 2 8.% 1408555 abbreviated internationalRouter# test translation-rule 21 45678 abbreviatedRouter#*Jan 19 16:39:14.578:The replace number 45614085558Router#Related Commands
translate
To apply a translation rule to an inbound POTS call leg, use the translate voice-port configuration command. To remove the translation rule to an inbound POTS call leg, use the no form of this command.
translate {calling-number | called-number} name-tag
no translate {calling-number | called-number} name-tag
Syntax Description
Defaults
No default behavior or values.
Command Modes
Voice-port configuration.
Command History
Examples
The following example applies translation rule 21 to the POTS inbound calling party number:
Router(config)# translation-rule 21Router(config-translate)# rule 1 555.% 1408555 subscriber internationalRouter(config-translate)# rule 2 7.% 1408555 abbreviated internationalRouter(config)# voice-port 0:1Router(config-voice-port)# translate calling-number 21The following example applies translation rule 20 to the POTS inbound called party number:
Router(config)# translation-rule 20Router(config-translate)# rule 1 .%555.% 7 any abbreviatedRouter(config)# voice-port 0:1Router(config-voice-port)# translate called-number 20Related Commands
translate-outgoing
To apply a translation rule to an outbound POTS or VoIP call leg, use the translate-outgoing dial-peer configuration command. To remove the translation rule to an outbound POTS or VoIP call leg, use the no form of this command.
translate-outgoing {calling-number | called-number} name-tag
no translate-outgoing {calling-number | called-number} name-tag
Syntax Description
Defaults
No default behavior or values.
Command Modes
Dial-peer configuration.
Command History
Examples
The following example applies translation rule 21 to the VoIP outbound calling number:
Router(config)# translation-rule 21Router(config-translate)# rule 1 555.% 1408555 subscriber internationalRouter(config-translate)# rule 2 7.% 1408555 abbreviated internationalRouter(config)# dial-peer voice 100 voipRouter(config-dial-peer)# translate-outgoing calling-number 21The following example applies translation rule 20 to the VoIP called number:
Router(config)# translation-rule 20Router(config-translate)# rule 1 .%555.% 7 any abbreviatedRouter(config)# dial-peer voice 100 voipRouter(config-dial-peer)# translate-outgoing called-number 20Related Commands
translation-rule
To create a translation name and enter translation-rule configuration mode to apply rules to the translation name, use the translation-rule global configuration command. To remove the translation rule, use the no form of this command.
translation-rule name-tag
no translation-rule name-tag
Syntax Description
name-tag
The tag number by which the rule set will be referenced. This is an arbitrarily chosen number. Range is 1 through 2147483647.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies to all translation rules.
Examples
The following example creates translation-rule 21 and applies a rule to it.
Router(config)# translation-rule 21Router(config-translate)# rule 1 555.% 1408555 subscriber internationalRelated Commands
voip-incoming translation-rule
To set the incoming translation rule for calls that originate from H.323-compatible clients, use the voip-incoming translation-rule global configuration command. To disable the incoming translation rule, use the no form of this command.
voip-incoming translation-rule name-tag {calling-number | called-number}
no voip-incoming translation-rule name-tag {calling-number | called-number}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
With this command, all IP-based calls will be captured and handled, depending on either the calling or called number to the specified tag-name.
Examples
The following example identifies the rule set for calls that originate from H.323-compatible clients:
Router(config)# voip-incoming translation-rule 5 calledRelated Commands
Debug Command
This section provides information on new and modified debug commands.
All other debug commands used with Voice over Frame Relay are documented in the Cisco IOS Release 12.1 command references.
The following new and modified commands are described in this section:
debug translation
To debug number translation traces, use the debug translation privileged EXEC command. To disable the debug, use the no form of this command.
debug translation {detail | min}
no debug translation {detail | min}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
.
Examples
The following example provides a sample debug trace for the debug translation command based on a short configuration below:
Router(config)# dial-peer voice 666 potsRouter(config-dial-peer)# destination-pattern 4085551504Router(config-dial-peer)# translate-outgoing called-number 111 port 0:DRouter(config)# translation-rule 111Router(config-translation)# rule 1 789 111Router# debug translation detailCalled Number 4085551504*Jan 9 22:48:23.948: xrule_checking*Jan 9 22:48:23.948: xrule_checking peer_tag 666*Jan 9 22:48:23.948: xrule_checking tag 111, callparty 2*Jan 9 22:48:23.948: xrule_checking direction 2*Jan 9 22:48:23.948: dpMatchString, target_number 4085551504*Jan 9 22:48:23.948: dpMatchString match_tmp 555*Jan 9 22:48:23.948: xrule_checking in_range*Jan 9 22:48:23.948: replace_string*Jan 9 22:48:23.948: replace_string match 555, replace 111*Jan 9 22:48:23.948: replace_string match_tmp 555*Jan 9 22:48:23.948: replace_string direction 2, callparty 0*Jan 9 22:48:23.948: replace_string target*Jan 9 22:48:23.948: replace_string direction 2, callparty 2, target 4085551504*Jan 9 22:48:23.948: replace_string buffer 4085551504*Jan 9 22:48:23.948: xrule_checking index 1,xrule_number 4085551504*Jan 9 22:48:23.948: xrule_checking called Callparms Numpertype 0x0 match_type 0x0*Jan 9 22:48:23.948: xrule_checking Xrule index 1, Numpertype 0x9Related Commands
Glossary
AAA—Authentication, Authorization, and Accounting. AAA is a suite of network security services which provides the primary framework through which access control can be set up on your Cisco router or access server.
ANI—Automatic number identification.
ARQ—Admission request.
CAS—Channel associated signaling.
CCAPI—Call Control Application Programming Interface
CLI—Command Language Interpreter. The basic Cisco IOS configuration and management interface.
dial peer—An addressable call endpoint. In Voice over IP (VoIP), there are two types of dial peers: POTS and VoIP.
DNS—Domain name system used to address translation to convert H.323 IDs, URLs, or e-mail IDs to IP addresses. DNS is also used to assist in the location of remote gatekeepers and to reverse-map raw IP addresses to host names of administrative domains.
endpoint—An H.323 terminal or gateway. An endpoint can call and be called. It generates and/or terminates the information stream.
gatekeeper—A gatekeeper maintains a registry of devices in the multimedia network. The devices register with the gatekeeper at startup, and request admission to a call from the gatekeeper.
The gatekeeper is an H.323 entity on the LAN that provides address translation and controls access to the LAN for H.323 terminals and gateways. The gatekeeper may provide other services to the H.323 terminals and gateways, such as bandwidth management and locating gateways.
gateway—A gateway allows H.323 terminals to communicate with non-H.323 terminals by converting protocols. A gateway is the point at which a circuit-switched call is encoded and repackaged into IP packets.
A H.323 gateway is an endpoint on the LAN that provides real-time, two-way communications between H.323 terminals on the LAN and other ITU-T terminals in the WAN, or to another H.323 gateway.
H.323—An International Telecommunication Union (ITU-T) standard that describes packet-based video, audio, and data conferencing. H.323 is an umbrella standard that describes the architecture of the conferencing system, and refers to a set of other standards (H.245, H.225.0, and Q.931) to describe its actual protocol.
H.323 RAS—Registration, admission, and status. The RAS signaling function performs registration, admissions, bandwidth changes, status and disengage procedures between the VoIP gateway and the gatekeeper.
IVR—Integrated voice response. When someone dials in, it responds with a prompt to get a personal identification number (PIN), and so on.
multicast—A process of transmitting PDUs from one source to many destinations. The actual mechanism (that is, IP multicast, multi-unicast, and so forth) for this process might be different for LAN technologies.
multipoint-unicast—A process of transferring PDUs (Protocol Data Units) where an endpoint sends more than one copy of a media stream to different endpoints. This might be necessary in networks which do not support multicast.
node—An H.323 entity that uses RAS to communicate with the gatekeeper. For example, an endpoint such as a terminal, proxy, or gateway.
POTS—Plain old telephone service. Basic telephone service supplying standard single line telephones, telephone lines, and access to the PSTN.
PSTN—Public switched telephone network. PSTN refers to the local telephone company.
QoS—Quality of service, which refers to the measure of service quality provided to the user.
RAS—Registration, admission, and status protocol. This is the protocol that is used between endpoints and the gatekeeper to perform management functions.
TDM—Time-division multiplexing. Technique in which information from multiple channels can be allocated bandwidth on a single wire based on preassigned time slots. Bandwidth is allocated to each channel regardless of whether the station has data to transmit.
VoIP—Voice over IP. The ability to carry normal telephone-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.
VTSP—Voice telephony service provider.
zone—A collection of all terminals (tx), gateways (GW), and Multipoint Control Units (MCU) managed by a single gatekeeper (GK). A zone includes at least one terminal, and can include gateways or multipoint control units (MCUs). A zone has only one gatekeeper. A zone may be independent of LAN topology and can comprise multiple LAN segments which are connected using routes or other devices.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)