Table Of Contents
Configuration Examples
Two Routers Using Frame Relay Fragmentation
Two Routers Using a VoFR PVC
Router Using a VoFR PVC to a Cisco MC3810
Cisco MC3810 Concentrators Using Different VoFR Configuration Methods
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 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
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
•Two Routers Using a VoFR PVC
•Router Using a VoFR PVC to a Cisco MC3810
•Cisco MC3810 Concentrators Using Different VoFR Configuration Methods
•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 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
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.
Two Routers Using Frame Relay Fragmentation
shows an example of Frame Relay fragmentation between two routers.
Figure 8 Two Routers Using Frame Relay Fragmentation
Router A (Cisco 3600)
|
Router B (Cisco 3600)
|
|
|
ip address xxx.xxx.xxx
255.255.255.0
|
ip address xxx.xxx.xxx
255.255.255.0
|
frame-relay traffic shaping
|
frame-relay traffic shaping
|
|
|
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
|
|
|
|
map-class frame-relay toto
|
map-class frame-relay toto
|
encapsulation frame-relay
|
encapsulation frame-relay
|
|
|
|
|
|
|
|
This configuration uses FRF.12 fragmentation.
Two Routers Using a VoFR PVC
shows an example of two routers with connections using a VoFR PVC.
Figure 9 Two Routers Using a VoFR PVC
Router A (Cisco 3600)
|
Router B (Cisco 3600)
|
|
|
frame-relay traffic shaping
|
frame-relay traffic shaping
|
|
|
|
frame-relay interface-dlci 100
|
|
|
frame-relay interface-dlci 100
|
|
|
|
|
|
map-class frame-relay toto
|
map-class frame-relay toto
|
frame-relay voice-bandwidth t
|
frame-relay voice-bandwidth t
|
|
|
|
|
|
|
|
|
This configuration uses FRF.11 Annex C fragmentation.
Router Using a VoFR PVC to a Cisco MC3810
shows an example of a Cisco 3600 series router with connections to a Cisco MC3810 using a VoFR PVC. In this example, the Voice over Frame Relay interface on the Cisco MC3810 is configured using the vofr cisco command.
Note When a Cisco MC3810 is on a VoFR network, the configuration for connections to and from the Cisco MC3810 is slightly different than for other routers that support VoFR.
Figure 10 Router Using a VoFR PVC to a Cisco MC3810
Router A (Cisco 3600)
|
Router B (Cisco MC3810)
|
|
|
ip address xxx.xxx.xxx
255.255.255.0
|
ip address xxx.xxx.xxx
255.255.255.0
|
frame-relay traffic shaping
|
frame-relay traffic shaping
|
|
|
|
frame-relay interface-dlci 100
|
|
|
frame-relay interface-dlci 100
|
|
|
|
|
|
map-class frame-relay toto
|
map-class frame-relay toto
|
frame-relay voice-bandwidth t
|
frame-relay voice-bandwidth t
|
|
|
|
|
|
|
|
|
This configuration uses FRF.11 Annex C fragmentation.
Cisco MC3810 Concentrators Using Different VoFR Configuration Methods
On the Cisco MC3810, there are two different configuration methods for configuring Voice over Frame Relay on an interface. You can either use the vofr cisco command or the frame-relay interface-dlci dlci voice-encap size command. The first configuration method uses the vofr cisco command, which automatically provides support for weighted fair queuing and matches the configuration method supported on the Cisco 2600 and Cisco 3600 series routers.
The second configuration method uses the frame-relay interface-dlci voice-encap command, which does not automatically provide support for any queuing mechanism. However, if you enter the no frag-pre-queuing command, you can then statically configure either weighted fair queuing, priority queuing, or custom queuing on the interface. This second configuration method can be used to configure VoFR connections to Cisco 2600 and Cisco 3600 series routers.
You must choose one configuration method, because these commands are mutually exclusive on an interface.
shows an example of a VoFR PVC between two Cisco MC3810 concentrators, with each concentrator using a different VoFR configuration method. In this example, the VoFR PVC on the first Cisco MC3810 is configured using the vofr cisco command, while on the second concentrator, the VoFR PVC is configured using the frame-relay interface-dlci voice-encap command.
Figure 11 VoFR PVC Between Two Cisco MC3810 Concentrators Using Different Configuration Methods
Router A (Cisco MC3810)
|
Router B (Cisco MC3810)
|
|
|
ip address xxx.xxx.xxx
255.255.255.0
|
ip address xxx.xxx.xxx
255.255.255.0
|
frame-relay traffic shaping
|
frame-relay traffic shaping
|
|
|
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
voice-encap 320
|
|
|
|
|
|
|
|
map-class frame-relay toto
|
map-class frame-relay toto
|
|
|
|
|
|
|
|
|
frame-relay voice-bandwidth t
|
|
This configuration uses FRF.11 Annex C fragmentation.
Cisco-Trunk (Private Line) Calls between Two Routers
shows an example of VoFR Cisco-trunk (private line) calls between two routers.
Figure 12 Permanent Switched Calls Between Two Routers
Router A (Cisco 3600)
|
Router B (Cisco MC3810)
|
|
|
ip address xxx.xxx.xxx
255.255.255.0
|
ip address xxx.xxx.xxx
255.255.255.0
|
encapsulation frame-relay
|
encapsulation frame-relay
|
frame-relay traffic shaping
|
frame-relay traffic shaping
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
|
|
|
|
|
|
|
map-class frame-relay voice
|
map-class frame-relay voice
|
|
|
|
|
frame-relay voice bandwidth v
|
frame-relay voice bandwidth v
|
|
|
|
|
|
|
|
|
|
connection trunk 6001 answer-mode
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
session protocol cisco-switched
|
session protocol cisco-switched
|
|
|
FRF.11 Trunk Calls between Two Routers
shows an example of FRF.11 trunk calls configured between two routers.
Figure 13 FRF.11 Trunk Calls between Two Routers
Router A (Cisco 3600)
|
Router B (Cisco MC3810)
|
|
|
ip address xxx.xxx.xxx
255.255.255.0
|
ip address xxx.xxx.xxx
255.255.255.0
|
encapsulation frame-relay
|
encapsulation frame-relay
|
frame-relay traffic shaping
|
frame-relay traffic shaping
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
|
|
|
|
|
|
|
map-class frame-relay voice
|
map-class frame-relay voice
|
|
|
|
|
|
|
frame-relay voice bandwidth v
|
frame-relay voice bandwidth v
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
session protocol frf11-trunk
|
session protocol frf11-trunk
|
|
|
|
|
|
|
|
|
Tandem Configuration with Three Routers for Switched Calls
shows an example of a tandem configuration with two Cisco 3600 routers as endpoints, and a third Cisco 3600 as a tandem node.
Figure 14 Tandem Configuration with Three Routers for Switched Calls
Router A (Cisco 3600) Endpoint
|
Router C (Cisco 3600) Tandem Node
|
Router B (Cisco 3600) Endpoint
|
|
|
|
encapsulation frame-relay
|
encapsulation frame-relay
|
encapsulation frame-relay
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
|
|
|
vofr data 4 call-control 5
|
vofr data 4 call-control 5
|
vofr data 4 call-control 5
|
|
|
|
|
map-class frame-relay voice
|
|
map-class frame-relay voice
|
|
encapsulation frame-relay
|
|
|
frame-relay traffic-shaping
|
|
|
frame-relay interface-dlci 200
|
|
frame-relay voice bandwidth c
|
|
frame-relay voice bandwidth c
|
|
|
|
|
|
|
|
|
map-class frame-relay voice
|
|
|
|
|
|
|
|
|
|
|
|
|
|
frame-relay voice bandwidth c
|
|
|
|
|
|
|
|
session target serial 0/0 100
|
|
session target serial 0/0 200
|
|
|
|
|
|
session target serial 0/0 100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
session target serial 0/1 200
|
|
Tandem Configuration with a Cisco MC3810 Tandem Node for Switched Calls
shows an example of a tandem configuration with a Cisco MC3810 acting as a tandem node.
Note When a Cisco MC3810 is on a VoFR network, the configuration for connections to and from the Cisco MC3810 is slightly different than for other routers that support VoFR. The vofr cisco command is required for those connections.
Figure 15 Tandem Configuration with a Cisco MC3810 Tandem Node for Switched Calls
Router A (Cisco 3600) Endpoint
|
Router C (Cisco MC3810) Tandem Node
|
Router B (Cisco 3600) Endpoint
|
|
|
|
encapsulation frame-relay
|
encapsulation frame-relay
|
encapsulation frame-relay
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
|
|
|
|
|
|
|
|
|
|
map-class frame-relay voice
|
|
map-class frame-relay voice
|
|
encapsulation frame-relay
|
|
|
frame-relay traffic-shaping
|
|
|
frame-relay interface-dlci 200
|
|
frame-relay voice bandwidth c
|
|
frame-relay voice bandwidth c
|
|
|
|
|
|
|
|
|
map-class frame-relay voice
|
|
|
|
|
|
|
|
|
|
|
|
|
|
frame-relay voice bandwidth c
|
|
|
|
|
|
|
|
session target serial 0/0 100
|
|
session target serial 0/0 200
|
|
|
|
|
|
session target serial 0/0 100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
session target serial 0/1 200
|
|
Tandem Configuration with a Cisco MC3810 Endpoint Node for Switched Calls
shows an example of a tandem configuration with a Cisco MC3810 acting as an endpoint node.
Note When a Cisco MC3810 is on a VoFR network, the configuration for connections to and from the Cisco MC3810 is slightly different than for other routers that support VoFR. The vofr cisco command is required.
Figure 16 Tandem Configuration with a Cisco MC3810 Endpoint Node
Router A (Cisco 2600) Endpoint
|
Router C (Cisco 3600) Tandem Node
|
Router B (Cisco MC3810) Endpoint
|
|
|
|
encapsulation frame-relay
|
encapsulation frame-relay
|
encapsulation frame-relay
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 200
|
|
|
|
vofr data 4 call-control 5
|
vofr data 4 call-control 5
|
|
|
|
|
|
map-class frame-relay voice
|
|
map-class frame-relay voice
|
|
encapsulation frame-relay
|
|
|
frame-relay traffic-shaping
|
|
|
frame-relay interface-dlci 200
|
|
frame-relay voice bandwidth c
|
|
frame-relay voice bandwidth c
|
|
|
|
|
|
|
|
|
map-class frame-relay voice
|
|
|
|
|
|
|
|
|
|
|
|
|
|
frame-relay voice bandwidth c
|
|
|
|
|
|
|
|
session target serial 0/0 100
|
|
session target serial 0 200
|
|
|
|
|
|
session target serial 0/0 100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
session target serial 0/1 200
|
|
Tandem Configuration with a Cisco MC3810 Endpoint Node for Cisco-Trunk (Private Line) Calls
shows an example of a tandem configuration with a Cisco MC3810 acting as an endpoint node for Cisco-trunk (private line) calls.
Note When a Cisco MC3810 is on a VoFR network, the configuration for connections to and from the Cisco MC3810 is slightly different than for other routers that support VoFR. The vofr cisco command is required for those connections.
Figure 17 Tandem Configuration with a Cisco MC3810 Endpoint Node for Permanent Switched Call
Router A (Cisco 2600) Endpoint
|
Router C (Cisco 3600) Tandem Node
|
Router B (Cisco MC3810) Endpoint
|
|
|
|
encapsulation frame-relay
|
encapsulation frame-relay
|
encapsulation frame-relay
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 200
|
|
|
|
vofr data 4 call-control 5
|
vofr data 4 call-control 5
|
|
|
|
|
|
map-class frame-relay voice
|
|
map-class frame-relay voice
|
|
encapsulation frame-relay
|
|
|
frame-relay traffic-shaping
|
|
|
frame-relay interface-dlci 200
|
|
frame-relay voice bandwidth c
|
|
frame-relay voice bandwidth c
|
|
|
|
|
|
|
|
|
map-class frame-relay voice
|
|
destination-pattern 1001A
|
|
destination-pattern 2001A
|
|
|
|
|
|
|
|
|
frame-relay voice bandwidth c
|
|
|
|
|
session target serial 0/0 100
|
|
session target serial 0 200
|
|
|
|
|
|
|
|
connection trunk 2001A
answer-mode
|
session target serial 0/0 100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
session target serial 0/1 200
|
|
Tandem Configuration with All Cisco MC3810 Concentrators for Switched Calls
shows an example of a tandem configuration with Cisco MC3810 concentrators as both endpoint and tandem nodes.
Note When a Cisco MC3810 is on a VoFR network, the configuration for connections to and from the Cisco MC3810 is slightly different than for other routers that support VoFR. Either the vofr cisco command, or the frame-relay interface-dlci voice-encap command, is required for these connections on the Cisco MC3810.
Figure 18 Tandem Configuration with all Cisco MC3810 Concentrators
Router A (Cisco MC3810) Endpoint
|
Router C (Cisco MC3810) Tandem Node
|
Router B (Cisco MC3810) Endpoint
|
|
|
|
encapsulation frame-relay
|
encapsulation frame-relay
|
encapsulation frame-relay
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 200
|
|
|
|
|
|
|
|
|
|
|
map-class frame-relay voice
|
|
map-class frame-relay voice
|
|
encapsulation frame-relay
|
|
|
frame-relay traffic-shaping
|
|
frame-relay voice bandwidth c
|
frame-relay interface-dlci 200
|
frame-relay voice bandwidth c
|
|
|
|
|
|
|
|
|
|
|
|
|
map-class frame-relay voice
|
|
|
|
|
|
|
|
|
|
|
|
|
frame-relay voice bandwidth c
|
|
|
|
|
session target serial 0 100
|
|
session target serial 0 200
|
|
|
|
|
|
|
|
|
|
session target serial 0 100
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
session target serial 1 200
|
|
Cisco Trunk Call with Hunt Groups
shows an example of a Cisco trunk (private line) call with hunt groups configured. 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, the call setup is attempted through that dial peer. If the call setup fails, the master can continue attempting call setups 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.
Note When a Cisco MC3810 is on a VoFR network, the configuration for connections to and from the Cisco MC3810 is slightly different than for other routers that support VoFR. Either the vofr cisco command, or the frame-relay interface-dlci voice-encap command, is required for these connections on the Cisco MC3810.
Figure 19 Cisco Trunk (Private Line) Call with Hunt Groups
Router A (Cisco MC3810)
|
Router B (Cisco MC3810)
|
|
|
encapsulation frame-relay
|
encapsulation frame-relay
|
frame-relay traffic-shaping
|
frame-relay traffic-shaping
|
frame-relay interface-dlci 100
|
frame-relay interface-dlci 100
|
|
|
|
|
|
|
|
|
|
|
