Configuring TEHO
You can complete the following tasks to configure TEHO:
Step 1. Define the VoIP outbound digit manipulation.
Step 2. Define the outbound VoIP dial peer.
Step 3. Define the outbound POTS dial peer.
To illustrate the configuration of TEHO, consider a scenario whose topology is presented
in Figure 7-29.
The design requirements for this scenario are as follows:
■ San Jose:
■ Local PSTN numbering range: 408XXXXXXX
■ Austin:
■ Local PSTN numbering range: 512XXXXXXX
All calls from Austin to the San Jose PSTN should be routed using the WAN link if possible.
If the WAN link fails, the PSTN link should be used.
To ensure that the correct ANI is presented for TEHO calls, a SJC-TEHO-OUT voice
translation profile should be configured and attached to both dial peers used for TEHO
to the San Jose site.
Figure 7-29 TEHO Configuration Scenario Topology
Step 1: Define VoIP Outbound Digit Manipulation for TEHO
Example 7-34 shows the configuration to define digit manipulation for TEHO on router
R3 in this scenario.
Example 7-34 Step 1—Defining VoIP Outbound Digit Manipulation for TEHO
418 Authorized Self-Study Guide Cisco Voice over IP (CVOICE)
IP WAN
192.168.1.1
PSTN
408 555-0100
R1
Phone1-1
2001
Phone1-2
2002
Phone2-1
2001
Phone2-2
2002
Austin
San Jose
R3
If the WAN fails, use
the Austin PSTN.
Use the WAN link
for calls to the
San Jose PSTN.
V
DID: 408555XXXX DID: 512555XXXX
R3(config)#voice translation-rule 10
R3(cfg-translation-rule)#rule 1 /^2/ /15125552/
R3(cfg-translation-rule)#exit
R3(config)#voice translation-profile SJC-TEHO-OUT
R3(cfg-translation- profile)#translate calling 10
Step 2: Define Outbound VoIP TEHO Dial Peer
To ensure that the correct ANI is presented for TEHO calls, an SJC-TEHO-OUT voice
translation profile is configured and attached to both VoIP dial peers used for TEHO to
the San Jose site.
Example 7-35 defines an outbound dial peer on router R3 that routes calls to San Jose.
Example 7-35 Step 2—Defining an Outbound VoIP TEHO Dial Peer
R3(config)#dial-peer voice 914081 voip
R3(config-dial-peer)#destination-pattern 91408.......
R3(config-dial-peer)#session-target ipv4:192.168.1.1
R3(config-dial-peer)#translation-profile outgoing SJC-TEHO-OUT
Step 3: Define Outbound POTS TEHO Dial Peer
To support pure PSTN fallback routing in case the WAN link fails, an additional dial peer
is configured. The destination-pattern 91408 and the prefix 1408 commands, as shown
in Example 7-36, strip off the national identifier and the San Jose area code.
Example 7-36 Step 3—Defining an Outbound POTS TEHO Dial Peer
Chapter 7: Configuring Advanced Dial Plans 419
R3(config)#dial-peer voice 914083 pots
R3(config-dial-peer)#destination-pattern 91408.......
R3(config-dial-peer)#prefix 1408
R3(config-dial-peer)#preference 1
R3(config-dial-peer)#port 0/0/0:23
Note The prefix command could also be replaced by the forward-digits command or a
voice translation profile.
Complete TEHO Configuration
As a reference, Example 7-37 provides the full TEHO configuration on router R3.
Example 7-37 TEHO Complete Configuration
R3#show running-config
... OUTPUT OMITTED ...
voice translation-rule 10
rule 1 /^2/ /13125552/
voice translation-profile SJC-TEHO-OUT
translate calling 10
dial-peer voice 914081 voip
destination-pattern 91408.......
session-target ipv4:192.168.1.1
translation-profile outgoing SJC-TEHO-OUT
dial-peer voice 914083 pots
destination-pattern 91408.......
prefix 1408
preference 1
port 0/0/0:23
... OUTPUT OMITTED ...