Table Of Contents
Versatile Interface Processor-Based Distributed FRF.11 and FRF.12 for Cisco IOS Release 12.1 T
Supported Standards, MIBs, and RFCs
Configuring Dial Peer Digit Manipulation
Disabling Dial Peer Hunting on a Specific Dial Peer
Configuring a Frame Relay Map Class to Support Voice over Frame Relay Fragmentation
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
Cisco-Trunk Call with Hunt Groups
Versatile Interface Processor-Based Distributed FRF.11 and FRF.12 for Cisco IOS Release 12.1 T
Feature Overview
The Voice Over Frame Relay (VoFR) capabilities that were introduced in Cisco IOS Release 11.3 were extended to Cisco 2600, 3600, and 7200 series routers in Cisco IOS Release 12.0(4)T. In Cisco IOS Release 12.1(2)T, the Voice Over Frame Relay Using FRF.11 and FRF.12 feature was updated to standardize the configuration procedures across all platforms. After Cisco IOS Release 12.1(2)T, configuration procedures for the Cisco 2600, 3600, and 7200 series routers and the Cisco MC3810 multiservice access concentrator were nearly identical.
Versatile Interface Processor-Based Distributed FRF.11 and FRF.12 (VIP-Based FRF.11 and FRF.12) is now available in Cisco IOS Release 12.1(5)T. VIP-Based FRF.11 and FRF.12 brings the functionality of the Voice over Frame Relay Using FRF.11 and FRF.12 feature to VIP-enabled Cisco 7500 series routers running Cisco IOS Release 12.1 T.
Because VIP-Based Distributed FRF.11 and FRF.12 was not available in Cisco IOS Release 12.1 T until Cisco IOS Release 12.1(5)T, the configuration procedures for enabling FRF.11 and FRF.12 on the other supported platforms are almost identical to the procedures for enabling VIP-Based FRF.11 and FRF.12 on VIP-enabled Cisco 7500 series routers.
The one major difference between the other platforms and the VIP-enabled Cisco 7500 series router is the difference in map class configuration. The map class configuration procedure for VIP-enabled Cisco 7500 series routers is detailed in the "Configuring a Frame Relay Map Class to Support Voice over Frame Relay Fragmentation" section of this document.
This document describes the configuration procedures for VIP-enabled Cisco 7500 series routers enabling the VIP-Based FRF.11 and FRF.12 feature.
Benefits
Introduces Voice over Frame Relay Using FRF.11 and FRF.12 for VIP-Enabled Cisco 7500
VIP-Based FRF.11 and FRF.12 brings the functionality of the Voice over Frame Relay Using FRF.11 and FRF.12 feature to VIP-enabled Cisco 7500 series routers running Cisco IOS Release 12.1 T.
Restrictions
The following restrictions and limitations apply to the VIP-Based FRF.11 and FRF.12 feature:
•
VIP-Based FRF.12 does not function properly with some of the older port adapters. The following list charts the port adapters that don't function properly with VIP-Based FRF.12 and also recommends updated versions of these port adapters that support VIP-Based FRF.12.
Table 1 Port Adapters that do not Support VIP-Based FRF.12
•
In order for VoFR on a VIP-enabled Cisco 7500 series router to interoperate with VoFR on a Cisco MC3810, the Cisco MC3810 must be running Cisco IOS Release 12.0(3)XG or Cisco IOS Release 12.0(4)T or later.
•
VIP-enabled Cisco 7500 series routers cannot terminate calls initiated by a Cisco MC3810 using VoFR implementations prior to Cisco IOS Release 12.0(3)XG or 12.0(4)T.
•
It is currently not possible to translate from the Voice Over IP (VoIP) transport protocol to other protocols such as VoFR. As a result, a call coming in on a VoIP connection is not (tandem) switched to a VoFR connection.
•
Hookflash for dial-tone recall from the router is not supported. However, the router can pass-through hookflash on FXO-FXS permanent connections and E&M-E&M connections using the connection trunk voice port configuration command.
•
For VIP-enabled Cisco 7500 series routers, distributed Cisco Express Forwarding (dCEF) must be enabled to run VIP-Based FRF.11 and FRF.12.
•
When using the shape command, the cir value needs to be a multiple of 8000. The bc/cir and be/cir must be multiples of 4 ms.
•
A VIP with 128 MB of memory can support up to 500 service policies. Cisco Systems cannot guarantee support for possible problems caused by VIPs using more than 500 service policies at one time.
•
Cisco MC3810 concentrators running Cisco IOS Releases before Release 12.0(3)XG or Release 12.0(4)T cannot tandem VoFR calls from non-Cisco MC3810 access concentrators, including VIP-enabled Cisco 7500 series routers.
•
Voice over ATM Switched Virtual Circuits (SVCs) are not supported in this release.
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.
For information about VIP-Based Distributed FRF.11 and FRF.12 in Cisco IOS Release 12.1(1)E, see the Versatile Interface Processor-Based Distributed FRF.11 and FRF.12 feature module that is located in the Cisco IOS Release 12.1(1)E new features documentation index.
For information about Voice over Frame Relay Using FRF.11 and FRF.12 for Cisco 2600, 3600, and 7200 series routers, as well as the Cisco MC3810 concentrator, see the Voice Over Frame Relay Using FRF.11 and FRF.12 feature module on the 12.0(4)T new features documentation index and the Voice Over Frame Relay Using FRF.11 and FRF.12 feature module on the 12.1(2)T new features documentation index. Both of these documents are available online on Cisco Connection Online (CCO).
For more information about voice technologies, refer to the Cisco IOS Multiservice Applications Configuration Guide, and the Cisco IOS Multiservice Command Reference, for
Cisco IOS Release 12.1.Supported Platforms
The VIP-Based FRF.11 and FRF.12 is only available for Cisco 7500 series routers with a Versatile Interface Processor (VIP).
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:
•
Complete your company's dial plan.
•
Establish a working Frame Relay network. For more information about configuring Frame Relay, refer to Cisco IOS Release 12.1 Wide-Area Networking Configuration Guide for Cisco IOS Release 12.1.
•
Establish a working telephony network based on your company's dial plan:
–
Integrate your dial plan and telephony network into your existing Frame Relay network topology. Make routing and dialing transparent to the user—for example, avoid secondary dial tones from secondary switches where possible.
–
Contact your PBX vendor for instructions about how to reconfigure the appropriate PBX interfaces.
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:
•
Configuring Dial Peer Digit Manipulation (Required)
•
Configuring Dial Peer Hunting (Required)
•
Disabling Dial Peer Hunting on a Specific Dial Peer
•
Configuring a Frame Relay Map Class to Support Voice over Frame Relay Fragmentation
•
Configuring Voice over Frame Relay Connections
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
To configure dial peer digit manipulation to forward digits, perform the following steps beginning in global configuration mode:
Command PurposeStep 1
Router(config)# dial-peer voice tag potsEnter 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
The no state is not the default state.
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 global 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 a Frame Relay Map Class to Support Voice over Frame Relay Fragmentation
To configure a map class to support FRF.11 on a VIP-enabled Cisco 7500 series router, use the following commands to configure a service policy and apply this service policy in map class configuration mode:
Configuring Voice over Frame Relay Connections
After you have configured the Frame Relay data-link connection identifier (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:
•
Configuring Switched Calls (User-Dialed or Auto-Ringdown)
•
Configuring Cisco-Trunk Permanent (Private Line) Calls
•
Configuring FRF.11 Trunk (Private Line) Calls
In addition, special consideration is required for configuring calls for tandem nodes. For more information, see the "Configuring Connections for Tandem Nodes" section.
Note
Use of Cisco-trunks for permanent calls (private line) is recommended over FRF.11-trunk calls unless FRF.11-compliant standards-based interworking is required with non-Cisco devices. The Cisco-trunk protocol is a superset of the FRF.11 protocol and contains Cisco proprietary extensions designed to support switched call routing and other advanced features.
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 1Table 2 lists the different connection types for VoFR connections supported on the VIP-enabled Cisco 7500 series routers, and the combinations of commands to enter for each call type.
Table 2 Supported Voice over Frame Relay Connection Types
Type of Call Frame Relay DLCI Interface Command to Enter Data Fragmentation Supported by VoFR Command Session Protocol Command to Enter in Dial Peer Mode Voice Port Connection Command to EnterSwitched call
(user-dialed or auto-ringdown) to other routers supporting VoFRvofr [data cid]
[call-control [cid]]1FRF.11 Annex C
session protocol cisco-switched2
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 cisco3
Cisco proprietary4
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]5
FRF.11 Annex C
session protocol frf11-trunk
connection trunk destination-string [answer mode]
1 The recommended use of this command is vofr data 4 call-control 5.
2 The session protocol cisco-switched option is the default setting. If you do not enter this command, the setting still applies.
3 This command consumes data CID 4 and call-control CID 5.
4 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 Release 12.0(4)T.
5 For FRF.11 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
•
Configuring Switched Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
Configuring Switched Calls to Other Voice over Frame Relay Routers
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
VIP-enabled Cisco 7500 series routers cannot terminate or initiate calls with a Cisco MC3810 running software releases before Cisco IOS Release 12.0(3)XG and Release 12.0(4)T.
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
•
Configuring Cisco-Trunk Permanent Calls
•
Configuring Cisco-Trunk Permanent Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T
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:
•
cas—Use the cas option to support North American channel-associated signalling (CAS)/robbed-bit signaling. This is the default signaling type.
•
cept—Use the cept option to provide a basic E1 ABCD protocol, primarily for CEPT Ear and Mouth (E&M) signaling. This option is primarily used for European voice networks. If this option is used with FXS or FXO voice ports, the signaling used is equivalent to Mercury Exchange Limited (MEL) CAS.
•
ext-signal—Use the ext-signal option in cases where some external signaling channel is being used (for example, common channel signaling), or where no signaling information is being sent at all over a permanent "dumb" voice pipe. Applications where no signaling is required include using a simple voice pipe to carry audio for a public address system.
•
transparent—Use the transparent option when the ABCD signaling bits are copied through from the T1/E1 interface "transparently" without modification or interpretation (also known as transparent FRF.11 signaling). This allows the router to handle or transport unknown signaling protocols.
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.
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 VIP-enabled Cisco 7500 series routers.
Note
If you are configuring Cisco-trunk permanent calls to Cisco MC3810 concentrators running Cisco IOS releases before 12.1(2)T, see the "Configuring Cisco-Trunk Permanent Calls to a Cisco MC3810 Running Cisco IOS Releases Before 12.1(2)T" section.
To configure Cisco-trunk permanent calls, use the following commands from interface configuration mode:
This configuration uses standard FRF.11 Annex C fragmentation.
Note
Every time you enter the connection trunk or no connection trunk command, you must toggle the voice port (by entering shutdown, then no shutdown) for the changes to take effect.
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
Every time you enter the connection trunk or no connection trunk command, you must toggle the voice port (by entering shutdown, then no shutdown) for the changes to take effect.
Configuring FRF.11 Trunk (Private Line) Calls
On a VIP-enabled Cisco 7500 series router, you can configure FRF.11 trunk calls to a second router.
You cannot configure FRF.11 trunk calls for tandem VoFR configurations.
Note
This configuration requires that you set the session protocol dial peer configuration command to frf11-trunk.
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
Every time you enter the connection trunk or no connection trunk command, you must toggle the voice port (by entering shutdown, then no shutdown) for the changes to take effect.
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 multi-hop network.
Tandeming is supported on all platforms that support Voice over Frame Relay Using FRF.11 and FRF.12, including VIP-enabled Cisco 7500 series routers.
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 3 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
Pick up the handset on a telephone connected to the configuration and verify that you can get a dial tone.
Step 2
Make a call from the local telephone to a configured dial peer and verify that the call attempt is successful.
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
Pick up the telephone and listen to hear the dial tone from the remote PBX.
Step 2
Dial digits so that the remote PBX routes the call.
You can check the validity of your dial peer and voice port configurations by performing the following tasks:
•
If you have relatively few dial peers configured, enter the show dial-peer voice command to verify that the data configured is correct.
•
To show the status of the voice ports, enter the show voice port command.
•
To show the call status for all voice ports, enter the show call active voice [brief] command.
You can check the validity of your VoFR configuration on the DLCI by performing the following task:
•
To show the VoFR configuration, enter the show frame-relay vofr [interface [dlci [cid]]] command.
Troubleshooting Tips
If you are having trouble connecting a call, you can try to resolve the problem by performing the following tasks:
•
If no FRF.11 calls are going through, make sure that the frame-relay voice bandwidth command is configured.
•
If you have Voice over Frame Relay configured on a PVC and are experiencing problems with data connectivity on that PVC, make sure that the frame-relay fragment command has been configured.
•
If you suspect that the problem is with the dial plan or the dial peers, use the show dial-plan number dial string command to display which dial peers are used when a specific number is called.
•
If you have problems connecting an FRF.11 trunk call, make sure that the session protocol dial peer command is set to frf11-trunk.
•
If you are configuring FRF.11 trunk calls, verify that the called-number vofr dial peer command is configured and that its number matches the destination pattern of the corresponding POTS dial peer.
•
Be sure that the voice port is set to no shutdown.
•
Be sure that the serial port or the T1/E1 controller is set to no shutdown.
•
Be sure to toggle the voice port (by first entering shutdown, then no shutdown) every time you enter the connection trunk or no connection trunk commands.
Configuration Examples
This section provides specific configuration examples for different VoFR connections and call type scenarios. This section includes the following examples:
•
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
•
Cisco-Trunk Call with Hunt Groups
Note
In the examples, some commands are shown with a lowercase letter in boldface. These letters indicate command settings that must match on the different routers. For example, the frame-relay cir s value indicates that the committed information rate "s" must match on the routers as shown.
The examples do not provide complete configurations, but show the required commands to configure Voice over Frame Relay.
For examples of Voice over Frame Relay connections for non-Cisco 7500 series routers, see the Voice Over Frame Relay Using FRF.11 and FRF.12 Configuration Updates document on CCO or the Documentation CD-ROM.
Two Routers Using Frame Relay Fragmentation
Figure 1 shows an example of Frame Relay fragmentation between a Cisco 3600 and a VIP-enabled Cisco 7500 series router. This configuration uses FRF.12 fragmentation.
Figure 1 Two Routers Using Frame Relay Fragmentation
This example assumes that a map class called frf12-class was previously configured.
For information on low latency queueing on the VIP, see the Distributed Low Latency Queueing feature module on CCO. For information on distributed traffic shaping, see the Distributed Traffic Shaping feature module on CCO.
Two Routers Using a VoFR PVC
This example shows an example of Frame Relay fragmentation between a Cisco 7500 series router with a VIP and a Cisco 3600 series router.
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 Release



