Table Of Contents
Voice over Frame Relay Using FRF.11 and FRF.12 Configuration Updates
Supported Standards, MIBs, and RFCs
Configuring Dial Peer Digit Manipulation
Disabling Dial-Peer Hunting on a Specific Dial Peer
Configuring Voice over Frame Relay Connections
Overview of Voice over Frame Relay Connection Types
Configuring Switched Calls (User Dialed or Auto-Ringdown)
Configuring Switched Calls to Other Voice over Frame Relay Routers
Configuring Switched Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
Configuring Cisco-Trunk Permanent (Private Line) Calls
Configuring Voice over Frame Relay Dial Peers for Cisco-Trunk (Private Line) Calls
Configuring Cisco Trunk Permanent Calls
Configuring Cisco Trunk Permanent Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
Configuring FRF.11 Trunk (Private Line) Calls
Configuring Connections for Tandem Nodes
Verifying Your Voice Connections
Two Routers Using Frame Relay Fragmentation
Router Using a VoFR PVC to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
Cisco-Trunk (Private Line) Calls Between Two Routers
FRF.11 Trunk Calls Between Two Routers
Tandem Configuration with Three Routers for Switched Calls
Tandem Configuration with a Cisco MC3810 Tandem Node for Switched Calls
Tandem Configuration with a Cisco MC3810 Endpoint Node for Cisco-Trunk (Private Line) Calls
Tandem Configuration with All Cisco MC3810 Concentrators for Switched Calls
Cisco Trunk Call with Hunt Groups
Voice over Frame Relay Using FRF.11 and FRF.12 Configuration Updates
Feature Overview
Voice over Frame Relay functionality has been updated in this release, so that configuration on all supported platforms is nearly identical. In Cisco IOS Release 12.0(4)T, when support for Voice over Frame Relay Using FRF.11 and FRF.12 was introduced, configuration procedures were different depending on the router platform used.
Some commands introduced in earlier Cisco IOS releases have been removed or modified. This document describes the configuration procedures effective in this release.
In addition, this release provides support for digital voice calls for Voice over Frame Relay on the Cisco 2600 and 3600 series routers. In previous releases, the Cisco 2600 and 3600 series only supported analog voice calls for Voice over Frame Relay.
Benefits
Configuration Consistency Across All Voice over Frame Relay Routers
This feature provides consistency for configuration requirements across the hardware models that support Voice over Frame Relay: the Cisco 2600 and 3600 series routers, the Cisco 7200 series routers, and the Cisco MC3810 multiservice access concentrator. In previous releases, configuration procedures on the Cisco MC3810 were different from those on other routers.
Digital Voice Support on the Cisco 2600 and 3600 Series Routers
Beginning in this release, the Cisco 3600 series routers support digital voice calls for Voice over Frame Relay. This feature requires that a Digital T1 Packet Voice Trunk network module is installed on the router.
Restrictions
•
The Cisco 2600 series and 3600 series routers cannot terminate calls initiated by a Cisco MC3810 using VoFR implementations before Cisco IOS Release 12.0(3)XG or 12.0(4)T.
•
•
•
•
Caution
Cisco IOS Release 12.0(5)XK and 12.0(7)T. If upgrading a Cisco MC3810 from
Cisco IOS Release 12.0(5)XK or 12.0(7)T to this release to obtain Voice over Frame Relay improvements, you lose support for your Voice over ATM SVCs.
Related Documents
For complete information about Voice over Frame Relay configuration, see the Cisco IOS Multiservice Applications Configuration Guide, for Cisco IOS Release 12.1.
•
Cisco IOS 12.1(2)T online documents:–
–
–
•
•
Cisco IOS Release 12.1.Supported Platforms
•
•
•
•
•
Note
Supported Standards, MIBs, and RFCs
Standards
None
MIBs
None
For descriptions of supported MIBs and how to use MIBs, see the Cisco MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
None
Prerequisites
Before you can configure a Cisco router to use Voice over Frame Relay, you must do the following:
•
•
•
–
–
After you have analyzed your dial plan and decided how to integrate it into your existing Frame Relay network, you are ready to configure your network devices to support Voice over Frame Relay.
Configuration Tasks
This section describes the following new and modified configuration procedures for Voice over Frame Relay in this release:
•
•
•
For all remaining Voice over Frame Relay procedures, see the "Configuring Voice over Frame Relay" chapter in Cisco IOS Multiservice Applications Configuration Guide for Cisco IOS Release 12.1.
Configuring Dial Peer Digit Manipulation
In Cisco IOS Release 12.1(2)T, the forward-digits command used for POTS dial-peer digit manipulation has been changed. To configure dial-peer digit manipulation to forward digits, perform the following steps beginning in global configuration mode:
Step 1
Enter dial-peer configuration mode for a POTS dial peer.
Step 2
Router(config-dial-peer)# forward-digits {num-digit | all | extra}or
Router(config-dial-peer)# default forward-digitsor
Router(config-dial-peer)# no forward-digitsIf using the forward-digits feature, configure the digit-forwarding method. The range for the number of digits forwarded (num-digit) is 0 through 32.
See the "Command Reference" section for an explanation of the command options.
In the default condition, dialed digits not matching the destination pattern are forwarded.
Note
Configuring Dial Peer Hunting
After you have configured dial peers, you can configure how the router performs dial peer hunting functions. To configure the dial peer hunting behavior on the router, perform the following steps beginning in configuration mode:
Disabling Dial-Peer Hunting on a Specific Dial Peer
If using dial-peer hunting, there may be situations when you want to disable dial-peer hunting on a specific dial peer. To disable dial-peer hunting on a dial peer, use the following commands beginning in global configuration mode:
To reenable dial-peer hunting on a dial peer, enter the no huntstop command.
Configuring Voice over Frame Relay Connections
After you have configured the Frame Relay DLCI settings and you have configured your dial plan, you are ready to configure specific VoFR connections.
There are many different scenarios for VoFR connections. For information on the different connection types, see the next section, "Overview of Voice over Frame Relay Connection Types."
For procedures on how to configure the different connection types, see the following sections:
•
•
•
In addition, special consideration is required for configuring calls for tandem nodes. For more information, see the "Configuring Connections for Tandem Nodes" section.
Note
Overview of Voice over Frame Relay Connection Types
When you configure VoFR connections, you can use many different connection types depending on the hardware platform, whether the call is to be a regular switched (user dialed or auto-ringdown) call, or whether the call is a permanent call (Cisco-trunk or FRF.11-trunk). You configure these specific connection types by using combinations of several commands.
Table 1 lists the different connection types for VoFR connections supported on the Cisco 2600 and 3600 series routers, and the combinations of commands to enter for each call type.
Note
Table 1 Voice over Frame Relay Connection Types that are Supported
Switched call
(user dialed or auto-ringdown) to other routers supporting VoFRvofr [data cid]
[call-control [cid]]2FRF.11 Annex C
session protocol cisco-switched3
For user dialed calls: none
For auto-ringdown calls:
connection plar destination-stringSwitched call
(user dialed or auto-ringdown)
to a Cisco MC3810 running
Cisco IOS Releases before 12.1(2)Tvofr cisco4
Cisco proprietary5
session protocol cisco-switched
For user dialed calls: none
For auto-ringdown calls:
connection plar destination-stringCisco-trunk
permanent call (private-line) to other routers supporting VoFRvofr data cid
call-control cidFRF.11 Annex C
session protocol cisco-switched
connection trunk destination-string [answer mode]
Cisco-trunk
permanent call
(private-line)
to a Cisco MC3810 running
Cisco IOS Releases before 12.1(2)Tvofr cisco
Cisco proprietary
session protocol cisco-switched
connection trunk destination-string [answer mode]
FRF.11 trunk call (private-line) to other routers supporting VoFR
vofr [data cid] [call-control cid]6
FRF.11 Annex C
session protocol frf11-trunk
connection trunk destination-string [answer mode]
1 The voice-encap option of the frame-relay interface-dlci command on the Cisco MC3810 is no longer supported as of Cisco IOS Release 12.1(2)T.
2 The recommended use of this command is vofr data 4 call-control 5.
3 The session protocol cisco-switched option is the default setting. If you do not enter this command, the setting still applies.
4 This command consumes data CID 4 and call-control CID 5.
5 Cisco proprietary fragmentation is based on an early draft of FRF.12 and is compatible with Cisco MC3810 concentrators running software releases before Cisco IOS Release 12.0(3)XG or 12.0(4)T.
6 For FRF.111 trunk calls, the call-control option is not required. It is only required if you mix FRF.11 trunk calls with other types of voice calls on the same PVC.
Configuring Switched Calls (User Dialed or Auto-Ringdown)
This section describes how to configure switched calls (user dialed or auto-ringdown) on the different router platforms. This section is divided into the following procedures:
•
•
Configuring Switched Calls to Other Voice over Frame Relay Routers
You can configure switched calls on Cisco 2600, 3600, and 7200 series routers, and on Cisco MC3810 concentrators.
Note
To configure switched calls on routers that support VoFR, use the following commands from interface configuration mode:
This configuration uses standard FRF.11 Annex C fragmentation.
Configuring Switched Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
You can configure switched calls to Cisco MC3810 concentrators running Cisco IOS releases before 12.1(2)T. However, the configuration is different from standard switched calls because earlier Cisco MC3810 releases used the Cisco proprietary version of FRF.12.
Note
To configure switched calls to a Cisco MC3810 running Cisco IOS releases before 12.1(2)T, use the following commands beginning in interface configuration mode:
This configuration uses Cisco proprietary data fragmentation.
Configuring Cisco-Trunk Permanent (Private Line) Calls
This section describes how to configure Cisco-trunk permanent (private line) calls on the different router platforms. This section is divided into the following procedures:
•
•
•
Configuring Voice over Frame Relay Dial Peers for Cisco-Trunk (Private Line) Calls
If you are sending Cisco-trunk (private line) calls over the Frame Relay network, you must configure the Voice over Frame Relay dial peers to specifically support Cisco-trunk (private line) calls. Cisco-trunk (private line) calls are permanent calls.
One key task when you configure Cisco-trunk (private line) connections is to configure the signal type for the dial peer. The signal-type dial-peer command supports the following options:
•
•
•
•
Configure the signal type so that the signal type that is selected in the dial peers on the routers at both ends of the permanent voice call are the same. When you configure a permanent connection between a T1/E1 Cisco MC3810 and an analog voice port on a Cisco 2600 or Cisco 3600 series routers, set the signal type to cas, which is the default.
Cisco 2600 and Cisco 3600 analog voice ports do not support the cept or transparent signal types. The T1/E1 Cisco MC3810 can also be set to transparent, which simply passes the signaling through from the Cisco 2600 or Cisco 3600 series routers without interpretation. However, when transparent is used, the Cisco MC3810 makes no assumptions regarding the on-hook and off-hook state of the call. By default, when configured by using transparent, the Cisco MC3810 operates the voice path in the permanently open state, so that voice packets are sent (and network bandwidth consumed) regardless of the state of the call.
To configure a VoFR dial peer to support Cisco-trunk permanent (private line) calls, use the following commands beginning in global configuration mode:
Configuring Cisco Trunk Permanent Calls
You can configure Cisco trunk permanent calls on Cisco 2600, 3600, and 7200 series routers, and on Cisco MC3810 concentrators.
Note
To configure Cisco trunk permanent calls on these routers, use the following commands from interface configuration mode:
This configuration uses standard FRF.11 Annex C fragmentation.
Note
Configuring Cisco Trunk Permanent Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
To configure Cisco trunk permanent calls to a Cisco MC3810 running Cisco IOS releases before 12.1(2)T, use the following commands from interface configuration mode:
This configuration uses Cisco proprietary data fragmentation.
Note
Configuring FRF.11 Trunk (Private Line) Calls
On the Cisco MC3810 and on Cisco 2600 and 3600 series routers, you can configure FRF.11 trunk calls to a second router.
You cannot configure FRF.11 trunk calls for tandem VoFR configurations.
Note
To configure FRF.11 trunk (private line) calls, use the following commands from interface configuration mode:
This configuration uses FRF.11 Annex C data fragmentation.
Note
Configuring Connections for Tandem Nodes
Tandeming is switching incoming VoFR calls on a Frame Relay DLCI to an outgoing VoFR enabled DLCI. Tandeming works for switched calls and Cisco-trunk permanent calls only. You cannot tandem FRF.11 trunk calls over a multihop network.
Tandeming is supported on the Cisco MC3810 and on Cisco 2600, 3600, and 7200 series routers.
Note
Depending on which router is used as the end node and which router is used as the tandem node, you must use the correct Frame Relay PVC type when configuring your connections. Table 1 shows the different combinations of routers that can serve as end nodes and tandem nodes, and the Frame Relay PVC type required.
When you configure a tandem node, you must configure two VoFR dial peers, one for each tandem connection.
Verifying Your Voice Connections
Verify that the voice connection for switched calls is working by following these steps:
Step 1
Step 2
Verify that the voice connection for FXO-FXS trunk calls from a telephone to a remote PBX is working by doing the following:
Step 1
Step 2
You can check the validity of your dial-peer and voice-port configuration by performing the following tasks:
•
•
•
•
You can check the validity of your VoFR configuration on the DLCI by performing the following task:
•
•
Troubleshooting Tips
If you are having trouble connecting a call, you can try to resolve the problem by performing the following tasks:
•
•
•
•
•
•
•
•
•
Configuration Examples
This section provides specific configuration examples for different VoFR connections and call type scenarios. This section includes the following examples:
•
•
•
•
•
•
•
•
•
Note
The examples do not provide complete configurations, but show the required commands to configure Voice over Frame Relay.
Two Routers Using Frame Relay Fragmentation
Figure 1 shows an example of Frame Relay fragmentation between two routers.
Figure 1 Two Routers Using Frame Relay Fragmentation
This configuration uses FRF.12 fragmentation.
Two Routers Using a VoFR PVC
Figure 2 shows an example of two routers with connections using a VoFR PVC.
Figure 2 Two Routers Using a VoFR PVC
This configuration uses FRF.11 Annex C fragmentation.
Router Using a VoFR PVC to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
Figure 3 shows an example of a Cisco 3600 series router with connections to a Cisco MC3810 running a Cisco IOS Releases before12.1(2)T. In this example, the Voice over Frame Relay interface on both the Cisco 3600 and the Cisco MC3810 is configured by using the vofr cisco command.
Figure 3 Router Using a VoFR PVC to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
This configuration uses FRF.11 Annex C fragmentation.
Cisco-Trunk (Private Line) Calls Between Two Routers
Figure 4 shows an example of VoFR Cisco-trunk (private line) calls between two routers.
Figure 4 Cisco-Trunk (Private Line) Calls Between Two Routers
FRF.11 Trunk Calls Between Two Routers
Figure 5 shows an example of FRF.11 trunk calls configured between two routers.
Figure 5 FRF.11 Trunk Calls Between Two Routers
Tandem Configuration with Three Routers for Switched Calls
Figure 6 shows an example of a tandem configuration with two Cisco 3600 routers as endpoints and a third Cisco 3600 as a tandem node.
Figure 6 Tandem Configuration with Three Routers for Switched Calls
Tandem Configuration with a Cisco MC3810 Tandem Node for Switched Calls
Figure 7 shows an example of a tandem configuration with a Cisco MC3810 acting as a tandem node.
Figure 7 Tandem Configuration with a Cisco MC3810 Tandem Node for Switched Calls
Tandem Configuration with a Cisco MC3810 Endpoint Node for Cisco-Trunk (Private Line) Calls
Figure 8 shows an example of a tandem configuration with a Cisco MC3810 acting as an endpoint node for Cisco-trunk (private line) calls.
Figure 8 Tandem Configuration with a Cisco MC3810 Endpoint Node for Permanent Switched Calls
Tandem Configuration with All Cisco MC3810 Concentrators for Switched Calls
Figure 9 shows an example of a tandem configuration with Cisco MC3810 concentrators as both endpoint and tandem nodes.
Note
Figure 9 Configuration with All Cisco MC3810 Concentrators as Endpoint and Tandem Nodes
Cisco Trunk Call with Hunt Groups
Figure 10 shows an example of a Cisco trunk (private line) call that is configured with hunt groups. In this example, the two routers are in master-slave mode with a backup path. Router B is configured as a slave and Router A is configured as the master. The master makes periodic attempts to establish the trunk until the trunk is established. Two dial peers match the destination string configured in the voice port, but because one dial peer has a higher preference than the other dial peer, the call setup is attempted through that dial peer. If the call setup fails, the master can continue attempting call setups by using the next available dial peer. After all dial peers are exhausted, the master can continue following the list cyclically by starting again from the dial peer with the highest preference.
Figure 10 Cisco Trunk (Private Line) Call with Hunt Groups
Command Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.1 command reference publications.
See new and modified debug commands in the "Debug Commands" section.
The following new and modified commands are described in this section (modified commands are marked by an asterisk):
•
•
dial-peer hunt
To specify a hunt selection order for dial-peers, use the dial-peer hunt dial-peer configuration command. Use the no form of this command to restore the default selection order.
dial-peer hunt hunt-order-number
no dial-peer hunt
Syntax Description
Defaults
The default is the longest match in phone number, explicit preference, and random selection (hunt order number 0).
Command Modes
Global configuration
Command History
Usage Guidelines
Use the dial-peer hunt dial-peer configuration command if you have configured hunt groups. "Longest match in phone number" refers to the destination pattern that matches the greatest number of the dialed digits. "Explicit preference" refers to the preference setting in the dial-peer configuration. "Least recent use" refers to the destination pattern that has waited the longest since being selected. "Random selection" weighs all of the destination patterns equally in a random selection mode.
Examples
The following example configures the dial peers to hunt in the following order: (1) longest match in phone number, (2) explicit preference, (3) random selection.
Router# configure terminalRouter(config)# dial-peer hunt 0Related Commands
dial-peer terminator
To change the character used as a terminator for variable-length dialed numbers, use the dial-peer terminator global configuration command. Use the no form of this command to restore the default terminating character.
dial-peer terminator character
no dial-peer terminator
Syntax Description
character
Designates the terminating character for a variable-length dialed number. Valid numbers and characters are #, *, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, a, b, c, and d. The default is #.
Defaults
The default terminating character is #.
Command Modes
Global configuration
Command History
12.0
This command was introduced.
12.0(7)XK
Usage was restricted to variable-length dialed numbers.
12.1(2)T
This command was implemented in Cisco IOS Release 12.1(2)T.
Usage Guidelines
There are certain areas in the world, for example, in certain European countries, where telephone numbers can vary in length. When a dialed-number string is identified as a variable length dialed-number, the system does not place a call until the configured value for the timeouts interdigits command has expired, or until the caller dials the terminating character. Use the dial-peer terminator global configuration command to change the terminating character.
Examples
The following example specifies "9" as the terminating character for variable-length dialed numbers:
Router# configure terminalRouter(config)# dial-peer terminator 9#Related Commands
dial-peer voice
To enter dial-peer configuration mode and specify the method of voice encapsulation, use the dial-peer voice global configuration command.
For the Cisco 2600 series routers
dial-peer voice tag {pots | voip | vofr}
no dial-peer voice tag
For the Cisco 3600 series routers and the Cisco MC3810 concentrator
dial-peer voice tag {pots | voip | vofr | voatm}
no dial-peer voice tag
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Use the dial-peer voice global configuration command to switch to the dial-peer configuration mode from the global configuration mode. Use the exit command to exit the dial-peer configuration mode and return to the global configuration mode.
Examples
The following example accesses dial-peer configuration mode and configures a POTS peer identified as dial peer 10:
Router# configure terminalRouter(config)# dial-peer voice 10 potsRelated Commands
forward-digits
To specify which digits to forward for voice calls, use the forward-digits dial-peer configuration command. If the no form of this command is entered, any digits not matching the destination-pattern are not forwarded. Use the default form of this command to restore the default state.
forward-digits {num-digit | all | extra}
no forward-digits
default forward-digits
Syntax Description
Defaults
Dialed digits not matching the destination pattern are forwarded.
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command applies only to POTS dial peers.
Forwarded digits are always right-justified, so that extra leading digits are stripped.
The destination pattern includes both explicit digits and wildcards if present.
Use the default form of this command if a non-default digit-forwarding scheme was entered previously and you wish to restore the default.
For QSIG ISDN connections, entering forward-digits all implies that all the digits of the called party number are sent to the ISDN connection. When you enter forward-digits num-digit and enter a number from 1 to 32, the number of digits specified (right justified) of the called part number are sent to the ISDN connection.
Examples
The following example forwards all of the digits in the destination pattern of a POTS dial peer:
Router(config)# dial-peer voice 1 pots Router(config-dial-peer)# destination-pattern 8... Router(config-dial-peer)# forward-digits allThe following example forwards four of the digits in the destination pattern of a POTS dial peer:
Router(config)# dial-peer voice 1 pots Router(config-dial-peer)# destination-pattern 555.... Router(config-dial-peer)# forward-digits 4The following example forwards the extra right-justified digits that exceed the length of the destination pattern of a POTS dial peer:
Router(config)# dial-peer voice 1 pots Router(config-dial-peer)# destination-pattern 555.... Router(config-dial-peer)# forward-digits extraRelated Commands
destination-pattern
Defines the prefix or the full E.164 telephone number to be used for a dial peer.
show dial-peer voice
Displays configuration information for dial peers.
frag-pre-queuing
This command was added in Cisco IOS Release 12.0(2)T on the Cisco MC3810. Beginning with Cisco IOS Release 12.1(2)T, this command is no longer supported.
frame-relay interface-dlci
To assign a data link connection identifier (DLCI) to a specified Frame Relay subinterface on the router or access server, use the frame-relay interface-dlci interface configuration command. Use the no form of this command to remove this assignment.
frame-relay interface-dlci dlci [ietf | cisco] [voice-cir cir]
no frame-relay interface-dlci dlci [ietf | cisco] [voice-cir cir]
Syntax Description
Defaults
No DLCI is assigned.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to configure Frame Relay DLCI and enter DLCI configuration mode:
Router(config-if)# frame-relay interface-dlci dlcihuntstop
To disable all further dial-peer hunting if a call fails when using hunt groups, enter the huntstop dial-peer configuration command. To reenable dial-peer call hunting, enter the no form of this command.
huntstop
no huntstop
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
Once you enter this command, no further hunting is allowed if a call fails on the specified dial peer.
This command can be used with all types of dial peers.
Examples
The following example shows how to disable dial-peer hunting on a specific dial peer:
Router(config)# dial peer voice 100 vofrRouter(config-dial-peer)# huntstopThe following example shows how to reenable dial-peer hunting on a specific dial peer:
Router(config)# dial peer voice 100 vofrRouter(config-dial-peer)# no huntstopRelated Commands
dial-peer voice
Enters dial-peer configuration mode and specifies the method of voice-related encapsulation.
signal-type
To set the signaling type to be used when connecting to a dial peer, use the signal-type command from dial-peer configuration mode. To return to the default signal-type, use the no form of this command.
signal-type {cas | cept | ext-signal | transparent}
no signal-type
Syntax Description
Defaults
cas
Command Modes
Dial-peer configuration
Command History
Usage Guidelines
This command applies to VoFR and VoATM dial peers. It is used with permanent connections only (Cisco trunks and FRF.11 trunks), not with switched calls.
This command is used to inform the local telephony interface of the type of signaling it should expect to receive from the far-end dial peer. To turn signaling off at this dial peer, select the ext-signal option. If signaling is turned off and there are no external signaling channels, a "hot" line exists, enabling this dial peer to connect to anything at the far end.
When you connect an FXS to another FXS, or if you have anything other than an FXS/FXO or E&M/E&M pair, the appropriate signaling type on Cisco 2600 series and 3600 series routers is ext-signal (disabled).
If you have a digital E1 connection at the remote end that is running cept/MELCAS signaling and you then trunk that across to an analog port, you should make sure that you configure both ends for the cept signal-type.
If you have a T1 or E1 connection at both ends and the T1/E1 is running a signaling protocol that is neither EIA-464 or cept/MELCAS, you might want to configure the signal-type for the transparent option in order to pass through the signaling.
Examples
The following example shows how to disable signaling on a Cisco 2600 series or 3600 series router or on a Cisco MC3810 concentrator for VoFR dial peer 200, starting from global configuration mode:
Router(config)# dial-peer voice 200 vofrRouter(config-dial-peer)# signal-type ext-signalRouter(config-dial-peer)#Related Commands
vofr
To enable Voice over Frame Relay (VoFR) on a specific DLCI and to configure specific subchannels on that DLCI, use the vofr command from Frame Relay DLCI configuration mode. Use the no form of the command to disable VoFR on a specific DLCI.
For switched calls
vofr [data cid] [call-control [cid]]
no vofr [data cid] [call-control [cid]]
For switched calls to Cisco MC3810 concentrators running Cisco IOS releases before 12.0(7)XK and 12.1(2)T
vofr [cisco]
no vofr [cisco]
For Cisco-trunk permanent calls
vofr data cid call-control cid
no vofr data cid call-control cid
For Cisco-trunk permanent calls to Cisco MC3810 concentrators running Cisco IOS releases before 12.0(7)XK and 12.1(2)T
vofr cisco
no vofr cisco
For FRF-11 trunk calls
vofr [data cid] [call-control cid]
no vofr [data cid] [call-control cid]
Syntax Description
Defaults
Disabled
Command Modes
Frame Relay DLCI
Command History
Usage Guidelines
Table 3 lists the different options of the vofr command and which combination of options is used beginning in Cisco IOS Release 12.0(7)XK and 12.1(2)T.
Table 3 Combinations of the vofr Command
Switched call
(user dialed or auto-ringdown) to other routers supporting VoFRvofr [data cid]
[call-control [cid]]1Switched call
(user dialed or auto-ringdown)
to a Cisco MC3810 running Cisco IOS releases before 12.0(7)XK and 12.1(2)Tvofr cisco2
Cisco-trunk
permanent call (private-line) to other routers supporting VoFRvofr data cid
call-control cidCisco-trunk
permanent call
(private-line)
to a Cisco MC3810 running Cisco IOS releases before 12.0(7)XK and 12.1(2)Tvofr cisco
FRF.11 trunk call (private-line) to other routers supporting VoFR
vofr [data cid] [call-control cid]3
1 The recommended use of this command is vofr data 4 call-control 5.
2 This command consumes data CID 4 and call-control CID 5.
3 For FRF.111 trunk calls, the call-control option is not required. It is required only if you mix FRF.11 trunk calls with other types of voice calls on the same PVC.
Usage Restrictions for Cisco IOS Releases Prior to 12.0(7)XK and 12.1(2)T
This section describes restrictions for using the vofr command in releases prior to Cisco IOS Release 12.0(7)XK and 12.1(2)T. Beginning in Cisco IOS Release 12.0(7)XK and 12.1(2)T, these restrictions no longer apply.
When you use the vofr command without the cisco option, all subchannels on the DLCI are configured for FRF.11 encapsulation. If you enter the vofr command is entered without any keywords or arguments, the data subchannel is CID 4 and there is no call-control subchannel.
Table 4 describes special conditions and restrictions for the use of the vofr command on the Cisco MC3810 running releases prior to 12.0(7)XK and 12.1(2)T.
If you select the "data" option, enter a numeric value to complete the command. If you select the call-control option, you do not enter a numeric value if you wish to accept the default call-control subchannel. See the following examples for clarification.
When you use the vofr command on a Cisco MC3810 without the "cisco" option, switched calls are not permitted. You can only make permanent FRF.11-trunk calls.
Note
Examples
The following example shows how to enable VoFR on Serial 1/1, DLCI 100 on a Cisco 2600 series, 3600 series, or 7200 series router or on a Cisco MC3810 concentrator, starting from global configuration mode:
Router(config)# interface serial 1/1Router(config-if)# frame-relay interface-dlci 100Router(config-fr-dlci)# vofrRouter(config-fr-dlci)#The above example configures CID 4 for data; no call-control CID is defined.
To configure CID 4 for data and CID 5 for call-control (both defaults), enter the following command:
Router(config-fr-dlci)# vofr call-controlRouter(config-fr-dlci)#To configure CID10 for data and CID 15 for call-control, enter the following command:
Router(config-fr-dlci)# vofr data 10 call-control 15Router(config-fr-dlci)#To configure CID 4 for data and CID 15 for call-control, enter the following command:
Router(config-fr-dlci)# vofr call-control 15Router(config-fr-dlci)#To configure CID 10 for data and CID 5 for call-control, enter the following command:
Router(config-fr-dlci)# vofr data 10 call-controlRouter(config-fr-dlci)#To configure CID 10 for data with no call-control, enter the following command:
Router(config-fr-dlci)# vofr data 10Router(config-fr-dlci)#To configure a Cisco router or MC3810 for a VoFR application with an older release of the Cisco MC3810 (before Release 12.0(3)XG), enter the following command:
Router(config-fr-dlci)# vofr ciscoRouter(config-fr-dlci)#Related Commands
frame-relay interface-dlci
Assigns a data link connection identifier (DLCI) to a specified Frame Relay subinterface.
class
Assigns a VC class to a PVC.
voice hunt user-busy
To configure an originating or tandem router so it continues dial-peer hunting if it receives a user-busy disconnect code from a destination router, use the voice hunt user-busy command in global configuration mode. To configure the router so it stops dial-peer hunting if it receives a user-busy disconnect code (the default option), use the no form of this command.
voice hunt user-busy
no voice hunt user-busy
Syntax Description
This command has no arguments or keywords.
Defaults
The command is disabled, meaning that the router stops dial-peer hunting when it receives a user-busy disconnect code.
Command Modes
Global configuration
Command History
Usage Guidelines
This command applies to routers acting as originating or tandem nodes in a Voice over IP, Voice over Frame Relay, or Voice over ATM environment.
This command is used for a configuration in which an originating or tandem router is configured with multiple dial peer entries that route a call to the same destination number, but on different destination routers. In this configuration, after all routes to the first router entry in the dial-peer list are active, a new call will not "roll over" to the next router in the dial-peer list.
This failure to route to the second destination router happens when the bandwidth on the voice interface is greater than the maximum capacity of the first destination router. This condition allows the originating or tandem router to attempt to place a new call to the first destination router because it has indications from the first destination router that there is more capacity based on the bandwidth setting. When the first destination router receives the call, if all of the ports are in use, the destination router returns a "user-busy" disconnect reason code to the originating or tandem router. The originating or tandem router interprets the disconnect reason code as "unavailable destination" for the call and returns a busy tone to the initiating caller.
The originating or tandem router fails to try other routers in the dial-peer list after receiving a "user disconnect" reason code, and so it terminates the call attempt. By using this command, you can perform dial-peer hunting on multiple destination routers even if the originating or tandem router receives a "user-busy" disconnect reason code from one of the destination routers.
Examples
The following example displays configuring the originating or tandem router to continue dial-peer hunting if it receives a "user-busy" disconnect code from a destination router:
Router(config)# voice hunt user-busyRelated Commands
preference
Indicates the preferred order of a dial peer within a rotary hunt group.
Debug Commands
This section provides information on new and modified VoFR debug commands for the Cisco 2600 series, the Cisco 3600 series, and the Cisco MC3810 multiservice access concentrator.
All other debug commands used with Voice over Frame Relay are documented in the Cisco IOS Debug Command Reference for Cisco IOS Release 12.1.
The following new and modified commands are described in this section:
debug ccfrf11 session
To display the ccfrf11 function calls during call setup and teardown, use the debug ccfrf11 session command from privileged EXEC mode. Use the no form of this command to turn off the debug function.
debug ccfrf11 session
no debug ccfrf11 session
Syntax Description
This command has no keywords or arguments.
Command History
Usage Guidelines
Use this command to display debug information about the various FRF.11 VoFR service provider interface (SPI) functions. Note that this debug command does not display any information regarding the proprietary Cisco switched-VoFR SPI.
This debug is useful only when the session protocol is "frf11-trunk."
Examples
The following example shows sample output from the debug ccfr11 session command:
Router# debug ccfrf11 sessionINCOMING CALL SETUP (port setup for answer-mode):*Mar 6 18:04:07.693:ccfrf11_process_timers:scb (0x60EB6040) timer (0x60EB6098) expired*Mar 6 18:04:07.693:Setting accept_incoming to TRUE*Mar 6 18:04:11.213:ccfrf11_incoming_request:peer tag 800:callingNumber=+2602100,calledNumber=+3622110*Mar 6 18:04:11.213:ccfrf11_initialize_ccb:preffered_codec set(-1)(0)*Mar 6 18:04:11.213:ccfrf11_evhandle_incoming_call_setup_request:calling +2602100,called +3622110 Incoming Tag 800*Mar 6 18:04:11.217:ccfrf11_caps_ind:PeerTag = 800*Mar 6 18:04:11.217: codec(preferred) = 4, fax_rate = 2, vad = 2*Mar 6 18:04:11.217: cid = 30, config_bitmask = 0, codec_bytes = 20, signal_type=2*Mar 6 18:04:11.217: required_bandwidth 8192*Mar 6 18:04:11.217:ccfrf11_caps_ind:Bandwidth reservation of 8192 bytes succeeded.*Mar 6 18:04:11.221:ccfrf11_evhandle_call_connect:EnteredCALL SETUP (MASTER):5d22h:ccfrf11_call_setup_request:Entered5d22h:ccfrf11_evhandle_call_setup_request:Entered5d22h:ccfrf11_initialize_ccb:preffered_codec set(-1)(0)5d22h:ccfrf11_evhandle_call_setup_request:preffered_codec set(9)(24)5d22h:ccfrf11_call_setup_trunk:subchannel linking successful5d22h:ccfrf11_caps_ind:PeerTag = 8105d22h: codec(preferred) = 512, fax_rate = 2, vad = 25d22h: cid = 30, config_bitmask = 1, codec_bytes = 24, signal_type=25d22h: required_bandwidth 65005d22h:ccfrf11_caps_ind:Bandwidth reservation of 6500 bytes succeeded.CALL TEARDOWN:*Mar 6 18:09:14.805:ccfrf11_call_disconnect:peer tag 0*Mar 6 18:09:14.805:ccfrf11_evhandle_call_disconnect:Entered*Mar 6 18:09:14.805:ccfrf11_call_cleanup:freeccb 1, call_disconnected 1*Mar 6 18:09:14.805:ccfrf11_call_cleanup:Setting accept_incoming to FALSE and startingincoming timer*Mar 6 18:09:14.809:timer 2:(0x60EB6098)starts - delay (70000)*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Alive timer stopped*Mar 6 18:09:14.809:timer 1:(0x60F64104) stops*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Generating Call record*Mar 6 18:09:14.809:cause=10 tcause=10 cause_text="normal call clearing."*Mar 6 18:09:14.809:ccfrf11_call_cleanup:Releasing 8192 bytes of reserved bandwidth*Mar 6 18:09:14.809:ccfrf11_call_cleanup:ccb 0x60F6404C, vdbPtr 0x610DB7A4freeccb_flag=1, call_disconnected_flag=1Related Commands
debug ccswvoice vofr-debug
To display the ccswvoice function calls during call setup and teardown, use the debug ccswvoice vofr-debug command from privileged EXEC mode. Use the no form of this command to turn off the debug function.
debug ccswvoice vofr-debug
no debug ccswvoice vofr-debug
Syntax Description
This command has no arguments or keywords.
Command History
Usage Guidelines
Use this command when troubleshooting a VoFR call that uses the "cisco-switched" session protocol. This command provides the same information as the debug ccswvoice vofr-session command, but includes additional debugging information relating to the calls.
Examples
The following example shows sample output from the debug ccswvoice vofr-debug command:
Router# debug ccswvoice vofr-debugCALL TEARDOWN:3640_vofr(config-voiceport)#*Mar 1 03:02:08.719:ccswvofr_bridge_drop:dropping bridge calls src 17 dst 16 dlci 100cid 9 state ACTIVE*Mar 1 03:02:08.727:ccswvofr:callID 17 dlci 100 cid 9 state ACTIVE event O/G REL*Mar 1 03:02:08.735:ccswvofr:callID 17 dlci 100 cid 9 state RELEASE event I/C RELCOMP*Mar 1 03:02:08.735:ccswvofr_store_call_history_entry:cause=22 tcause=22cause_text=no circuit.3640_vofr(config-voiceport)#CALL SETUP (outgoing):*Mar 1 03:03:22.651:ccswvofr:callID 23 dlci -1 cid -1 state NULL event O/G SETUP*Mar 1 03:03:22.651:ccswvofr_out_callinit_setup:callID 23 using dlci 100 cid 10*Mar 1 03:03:22.659:ccswvofr:callID 23 dlci 100 cid 10 state O/G INIT event I/C PROC*Mar 1 03:03:22.667:ccswvofr:callID 23 dlci 100 cid 10 state O/G PROC event I/C CONNccfrf11_caps_ind:codec(preferred) = 0Related Commands
debug ccswvoice vofr-session
To display the ccswvoice function calls during call setup and teardown, use the debug ccswvoice vofr-session command from privileged EXEC mode. Use the no form of this command to turn off the debug function.
debug ccswvoice vofr-session
no debug ccswvoice vofr-session
Syntax Description
This command has no arguments or keywords.
Command History
Usage Guidelines
Use this command to show the state transitions of the cisco-switched-vofr state machine as a call is processed, and when attempting to troubleshoot a VoFR call that uses the "cisco-switched" session protocol.
Examples
The following example shows sample output from the debug ccswvoice vofr-session command:
Router# debug ccswvoice vofr-sessionCALL TEARDOWN:3640_vofr(config-voiceport)#*Mar 1 02:58:13.203:ccswvofr:callID 14 dlci 100 cid 8 state ACTIVE event O/G REL*Mar 1 02:58:13.215:ccswvofr:callID 14 dlci 100 cid 8 state RELEASE event I/C RELCOMP3640_vofr(config-voiceport)#CALL SETUP (outgoing):*Mar 1 02:59:46.551:ccswvofr:callID 17 dlci -1 cid -1 state NULL event O/G SETUP*Mar 1 02:59:46.559:ccswvofr:callID 17 dlci 100 cid 9 state O/G INIT event I/C PROC*Mar 1 02:59:46.567:ccswvofr:callID 17 dlci 100 cid 9 state O/G PROC event I/C CONN3640_vofr(config-voiceport)#Related Commands
debug vtsp vofr subframe
To display the first 10 bytes (including header) of selected VoFR subframes for the interface, use the debug vtsp vofr subframe command in privileged EXEC mode. Use the no form of this command to turn off the debug function.
debug vtsp vofr subframe payload [from-dsp] [to-dsp]
no debug vtsp vofr subframe
Syntax Description
Command History
Usage Guidelines
Each debug output displays the first 10 bytes of the FRF.11 subframe, including header bytes. Use the from-dsp and to-dsp options to limit the debugs to a single direction. If not specified, debugs are displayed for subframes when they are received from the DSP and before they are sent to the DSP.
Use extreme caution in selecting payload options 0 and 5. These options may cause network instability.
Examples
The following example shows sample output from the debug vtsp vofr subframe command:
Router# debug vtsp vofr subframe 2vtsp VoFR subframe debugging is enabled for payload 2 to and from DSP 3620_vofr#*Mar 6 18:21:17.413:VoFR frame received from Network (24 bytes):9E 02 19 AA AA AA AAAA AA AA*Mar 6 18:21:17.449:VoFR frame received from DSP (18 bytes):9E 02 19 AA AA AA AA AA AAAA*Mar 6 18:21:23.969:VoFR frame received from Network (24 bytes):9E 02 19 AA AA AA AAAA AA AA*Mar 6 18:21:24.005:VoFR frame received from DSP (18 bytes):9E 02 19 AA AA AA AA AA AAAARelated CommandsRelated Commands
Glossary
ABCD signaling—4-bit telephony line signaling coding in which each letter of "ABCD" represents one of the 4 bits. This is often associated with CAS or robbed-bit signaling on a T1 or E1 telephony trunk.
CID—Channel ID. Designates the Frame Relay subchannel ID for Voice over Frame Relay.
CIR—Committed information rate. The average rate of information transfer a subscriber (for example, a network administrator) has stipulated for a Frame Relay PVC.
Cisco-trunk (private line) call—A Cisco-trunk (private line) call is established by the forced connection of a dynamic switched call. A Cisco-trunk call is established during configuration of the trunk and stays up for the duration of the configuration. It optionally provides a pass-through connection path to pass signaling information between the two telephony interfaces at either end of the connection.
Codec—Coder-decoder. (i) 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. (ii) 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, codec type, and telephone number associated with the call endpoint. There are four kinds of dial peers: POTS, VoIP, VoFR, and VoATM.
DS0—A 64-kbps B channel on an E1 or T1 WAN interface.
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. The DSP generates Annex A frames instead of passing a DTMF tone through the network as a voice sample.
Dynamic 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 recEive and transMit (or Ear and Mouth). 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 is also available on E1 and T1 digital interfaces.
FIFO—First-in, first-out. In data communication, FIFO refers to a buffering scheme where the first byte of data entering the buffer is the first byte retrieved by the CPU. In telephony, FIFO refers to a queuing scheme where the first calls received are the first calls processed.
FRF—Frame Relay Forum. An association of corporate members consisting of vendors, carriers, users, and consultants committed to the implementation of Frame Relay in accordance with national and international standards. Go to 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. Go to http://www.frforum.com.
FRF.11 Annex C—See FRF.12.
FRF11-trunk—A point-to-point permanent voice connection (private line) conforming to the FRF.11 specification.
FRF.12—The FRF.12 Implementation Agreement (also known as FRF.11 Annex C) was developed to allow long data frames to be fragmented into smaller pieces and interleaved with real-time frames. In this way, real-time voice and non-real-time data frames can be carried together on lower-speed links without causing excessive delay to the real-time traffic. Go to http://www.frforum.com.
FXO—Foreign Exchange Office. An FXO interface connects to the Public Switched Telephone Network's (PSTN) central office and is the interface offered on a standard telephone. Cisco's FXO interface is an RJ-11 connector that allows an analog connection to be directed at the PSTN's central office or to a station interface on 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.
hookflash—A short on-hook period usually generated by a telephone-like device during a call to Mercury Exchange Limited (MEL) Channel Associated Signaling (CAS). A voice signaling protocol used primarily in the United Kingdom.
PBX—Private branch exchange. 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).
PLAR—Private line, automatic ringdown. A leased voice circuit that connects two single endpoints together. When either telephone handset is taken off-hook, the remote telephone automatically rings.
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 via a traditional telephony network. POTS peers point to a particular voice port on a voice network device.
PSTN—Public Switched Telephone Network. PSTN refers to the local telephone company.
PVC—Permanent virtual circuit.
SVC—Switched virtual circuit.
Switched calls—Switched calls are normal telephone calls in which a user picks up a telephone, hears dial tone, enters the destination telephone number to reach the other telephone. Switched calls can also be private line auto-ringdown (PLAR) calls, or tie-line calls for fixed E&M to E&M fixed point-to-point connections.
Tandem switching—The dynamic switching of voice calls between VoFR or VoATM PVCs and subchannels; also called tandeming. Tandem switching is often encountered in multi-hop VoFR call connection paths.
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 via 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.
Guest
