Inbound Site-Code Dialing Example
To allegorize an entering armpit cipher dialing alarm flow, accede the cartography presented in
Figure 7-28 and its agnate agreement in Example 7-33.
IP WAN
PSTN
Phone1-1 10.10.0.1
2001
San Jose
Phone2-1
2001
Austin
R3
V V
Figure 7-28 Entering Site-Code Dialing Example Topology
Inbound Site-Code Dialing Agreement Example
Chapter 7: Configuring Advanced Punch Plans 417
R3(config)#voice translation-rule 2
R3(cfg-translation-rule)#rule 1 /^8022/ /2/
R3(cfg-translation-rule)#exit
R3(config)#voice translation-profile intersite-in
R3(cfg-translation-profile)#translate alleged 2
R3(cfg-translation-profile)#exit
R3(config)#dial-peer articulation 8010 voip
R3(config)#destination-pattern 8012...
R3(config)#session-target ipv4:10.10.0.1
R3(config)#translation-profile admission intersite-in
Figure 7-28 shows how the aforementioned VoIP punch aeon can be acclimated for both entering and outbound
calls. Because the aperture in San Jose is additionally configured to prefix the armpit cipher to
the calling cardinal for calls to Austin, the entering calling cardinal to Austin matches the
destination arrangement of the San Jose punch peers. The entering adaptation contour again strips
off the Austin 802 armpit cipher from the entering alleged number, and the alarm can be routed
to Phone2-1 in Austin.