Network Bulls
www.networkbulls.com
Best Institute for CCNA CCNP CCSP CCIP CCIE Training in India
M-44, Old Dlf, Sector-14 Gurgaon, Haryana, India
Call: +91-9654672192
The combination of voice translation-profiles and voice translation-rules creates a very
powerful tool for modifying numbers so that they match dial plan needs. Example 6-12
shows the configuration commands for voice translation profiles.
Example 6-12 Voice Translation-Profile Commands
RemoteSite#configure terminal
R e m o t e S i t e ( c o n f i g ) # v o i c e t r a n s l a t i o n - p r o f i l e name
R e m o t e S i t e ( c f g - t r a n s l a t i o n - p r o f i l e ) # t r a n s l a t e { c a l l e d I c a l l i n g I
r e d i r e c t - c a l l e d I r e d i r e c t - t a r g e t } translation-rule-number
You define a translation profile for voice calls using the voice translation-profile command
in global configuration mode. The name parameter of this command defines the name of
the translation profile. The maximum length of the voice translation-profile name is 31
alphanumeric characters.
You associate a translation rule with a voice translation profile using the translate command
in voice translation-profile configuration mode. The following list defines the
keywords and parameter for the translate command:
• called associates the translation rule with called numbers.
• calling associates the translation rule with calling numbers.
• redirect-called associates the translation rule with redirected called numbers.
• redirect-target associates the translation rule with transfer-to numbers and callforwarding
final destination numbers.
• translation-rule-number is the number of the translation rule to use for the call
translation. The valid range is from 1 to 2147483647. There is no default value.
NOTE The prior IOS digit manipulation tool translation rule has been replaced by
voice translation-rule. The commands are similar but are incompatible with each other.
SRST Dial Plan Voice Translation-Profile Commands for Digit Manipulation 143
SRST Dial Plan Voice Translation-Rule Commands for
Number Modification
Example 6-13 shows the configuration commands for voice translation-rules.
Example 6-13 Voice Translation-Rule Commands
RemoteSite#configure terminal I
RemoteSite(config)#voice translation-rule number
r o u t e r ( c f g - t r a n s l a t i o n - r u l e ) # r u l e precedence /match-pattern/
/replace-pattern/[type {match-type replace-type} [plan
{match-type replace-type}))
You define a translation rule for voice calls using the voice translation-rule command in
global configuration mode. The number parameter identifies the translation rule. The range
of the number is from 1 to 2147483647. The choice of the number does not affect usage
priority.
You define a translation rule using the rule command in voice translation-rule configuration
mode. The following list defines the keywords and parameters for the rule command, as
shown in Example 6-13:
• The parameter precedence defines the priority of the translation rule. The range is from
1 to 15.
• The parameter /match-pattern/ is a stream editor (SED) expression used to match
incoming call information. The slash (/) is a delimiter in the pattern.
• The parameter/replace-pattern/ is a SED expression used to replace the match pattern
in the call information. The slash is a delimiter in the pattern.
• The optional construct type match-type replace-type lets you modify the call's number
type. Valid values for the match-type argument are abbreviated, any, international,
national, network, reserved, subscriber, and unknown. Valid values for the replacetype
argument are abbreviated, international, national, network, reserved,
subscriber, and unknown.
• The optional construct plan match-type replace-type lets you modify the call's
numbering plan. Valid values for the match-type argument are any, data, ermes, isdn,
national, private, reserved, telex, and unknown. Valid values for the replace-type
argument are data, ermes, isdn, national, private, reserved, telex, and unknown.
144 Chapter 6: Implementing Cisco Unified SRST and MGCP Fallback
SRST Dial Plan Profile Activation Commands for Number Modification
Voice translation profiles can be bound to dial peers, source groups, trunk groups, voice
ports, and the voice service POTS.
Example 6-14 shows the configuration commands for voice translation profile activation.
Example 6-14 Voice Translation Rule Activation Commands
RemoteSite#configure terminal
RemoteSite(config)#voice-port 0/1/0:23
RemoteSite(config-voiceport) # t r a n s l a t i o n - p r o f i l e {incoming I outgoing} name
R e m o t e S i t e ( c o n f i g - v o i c e p o r t ) # e x i t
RemoteSite(config)#call-manager-fallback
r o u t e r ( c o n f i g - c m - f a l l b a c k ) # t r a n s l a t i o n - p r o f i l e {incoming I outgoing} name
In this example, the voice translationprofile is bound to a voice port. The voice
translationprofile can also be bound to all the dial peers, but the voice port needs to
be done only once.
You assign a translation profile to a voice port using the translation-profile command in
voice-port configuration mode. The following list defines the keywords and parameter for
the translation-profile command:
• The keyword incoming specifies that this translation profile handles incoming calls.
• The keyword outgoing specifies that this translation profile handles outgoing calls.
• The parameter name is the name of the translation profile.
In addition to the configuration shown in Example 6-14, the voice translation profiles can
be bound to the call-manager-fallback Cisco IOS service. The structure of the command
is identical.
NOTE The incoming direction of the voice translation-profile bound to the callmanager-
fallback Cisco IOS service handles the calls coming from IP Phones that are
registered with the router.
For more information about voice translation profiles, refer to the following documents at
Cisco.com, which you should be able to locate by searching by title:
• TechNotes Number Translation Using Voice Translation Profiles
• TechNotes Voice Translation Rules
SRST Dial Plan Class of Restriction Commands 145
SRST Dial Plan Class of Restriction Commands
Calling privileges can be assigned to IP Phones when they are in SRST mode using COR
commands. In the absence of COR in SRST dial peers, all phones can dial all numbers.
Example 6-15 shows the dial plan configuration commands for COR as they apply to SRST.
Example 6-15 Class of Restriction Commands
RemoteSite#configure terminal
RemoteSite(config)#call-manager-fallback
RemoteSite(config-cm-fallback)#cor {incoming I outgoing} cor-list-name
[cor-list-number starting-number - ending-number I default]
The command cor configures a COR on dial peers that are associated with directory
numbers. The following list defines the keywords and parameters for the cor command:
• The keyword incoming defines that a COR list is to be used by incoming dial peers.
• The keyword outgoing defines that a COR list is to be used by outgoing dial peers.
• The parameter cor-list-name is the COR list name.
• The parameter cor-list-number is a COR list identifier. The maximum number of COR
lists that can be created is 20, composed of incoming or outgoing dial peers. The first
six COR lists are applied to a range of directory numbers. The directory numbers that
do not have a COR configuration are assigned to the default COR list, as long as a
default COR list has been defined.
• The parameters starting-number - ending-number define the directory number range,
such as 2000 to 2025.
• The keyword default instructs the router to use an existing default COR list.
Table 6-2 summarizes the functions of COR dialed calls.
146 Chapter 6: Implementing Cisco Unified SRST and MGCP Fallback
Table 6-2 COR Dialing Possibilities
COR List on Incoming Dial
Peer
COR List on Outgoing Dial
Peer Result
No COR No COR The call succeeds.
No COR A COR list is applied for
outgoing calls.
The call succeeds. By default,
the incoming dial peer has the
highest COR priority when no
COR is applied. If you apply no
COR for an incoming call leg
to a dial peer, the dial peer can
make a call out of any other dial
peer, regardless of the COR
configuration on the outgoing
dial peer.
A COR list is applied for
incoming calls.
No COR The call succeeds. By default,
the outgoing dial peer has the
lowest priority. Because some
COR configurations exist for
incoming calls on the incoming
or originating dial peer, it is a
superset of the outgoing-call
COR configuration for the
outgoing or terminating dial
peer.
A COR list is applied for
incoming calls (a superset of
the COR list applied for outgoing
calls on the outgoing dial
peer).
A COR list is applied for
outgoing calls (subsets of the
COR list applied for incoming
calls on the incoming dial peer).
The call succeeds. The COR
list for incoming calls on the
incoming dial peer is a superset
of the COR list for outgoing
calls on the outgoing dial peer.
A COR list is applied for
incoming calls (a subset of the
COR list applied for outgoing
calls on the outgoing dial peer).
A COR list is applied for
outgoing calls (supersets of the
COR list applied for incoming
calls on the incoming dial peer).
The call does not succeed. The
COR list for incoming calls on
the incoming dial peer is not a
superset of the COR list for
outgoing calls on the outgoing
dial peer.
NOTE The complete configuration of COR is handled in the Cisco Voice over IP
course. Table 6-2 presents an overview only.
SRST Dial Plan Example
Figure 6-8 shows a multisite topology with a Cisco Unified SRST-enabled Cisco IOS router
in the remote site.
SRST Dial Plan Class of Restriction Commands 147
Figure 6-8 SRST Dial Plan Topology
Main Site
Cisco Unified
Communications
Manager
Phonel Phone2 Phone3
This figure shows a main site with a PSTN number of 51 l-555-2xxx and a remote site with
a PSTN number of 521-555-3xxx. Four digits are used for all internal calls, including calls
between the main site and remote site. The remote-site gateway has a single ISDN PRI
connection to the PSTN configured on port 0/1/0:23.
For the SRST remote-site configuration shown in Example 6-16, assume that the remote
site has only three phones, with one DN each. During SRST fallback, Phone 1 is configured
with directory number 3001 and has unlimited PSTN dialing access. Phone 2 is configured
with directory number 3002 and is not be allowed to place international calls. Phone 3 is
configured with directory number 3003 and is allowed to place only internal calls. Fourdigit
dialing to headquarters is configured, and calls should be sent to the main site over the
PSTN when in SRST mode.
The remote-site router also requires MGCP configurations, as discussed previously, but
they are not included in Example 6-16 for simplicity.
Example 6-16 Remote-Site SRST Dial Plan Configuration Example
a p p l i c a t i on
g l o b a l
s e r v i c e a l t e r n a t e d e f a u lt
i
•
c a l l - m a n a g e r - f a l l b a ck
ip source-address 10.1.250.101 port 2000
max-ephones 3
max-dn 3
cor incoming phonel 1 3001
cor incoming phone2 2 3002
continues
148 Chapter 6: Implementing Cisco Unified SRST and MGCP Fallback
Example 6-16 Remote-Site SRST Dial Plan Configuration Example (Continued)
cor incoming phone3 3 3003
d i a l p l a n - p a t t e r n 1 5215553...
e x t e n s i o n - l e n g t h 4
I
d i a l - p e e r cor custom
name i n t e r n al
name pstn
name p s t n - i n tl
I
d i a l - p e e r cor l i s t i n t e r n al
member i n t e r n al
!
d i a l - p e e r cor l i s t pstn
member pstn
I
d i a l - p e e r cor l i s t p s t n - i n tl
member p s t n - i n tl
I
d i a l - p e e r cor l i s t phonel
member i n t e r n al
member pstn
member p s t n - i n tl
I
d i a l - p e e r cor l i s t phone2
member i n t e r n al
member pstn
I
d i a l - p e e r cor l i s t phone3
member i n t e r n al
I
d i a l - p e e r voice 1 pots
d e s c r i p t i o n I n t e r n a l d i a l i n g from the PSTN
incoming called-number .
d i r e c t - i n w a r d - d i a l
p o r t 0/1/0:23
!
d i a l - p e e r voice 9 pots
d e s c r i p t i o n PSTN d i a l 9 f i r s t
c o r l i s t outgoing pstn
d e s t i n a t i o n - p a t t e r n 9T
port 0/1/0:23
!
d i a l - p e e r voice 9011 pots
d e s c r i p t i o n I n t e r n a t i o n a l d i a l 9 f i r s t
c o r l i s t outgoing p s t n - i n tl
SRST Dial Plan Class of Restriction Comman ds 149
Example 6-16 Remote-Site SRST Dial Plan Configuration Example (Continued)
d e s t i n a t i o n - p a t t e r n 9011T
p o r t 0/1/0:23
p r e f i x 011
I
•
d i a l - p e e r voice 2000 pots
d e s c r i p t i o n I n t e r n a l 4 d i g i t d i a l i n g to HQ
c o r l i s t outgoing i n t e r n al
t r a n s l a t i o n - p r o f i l e outgoing to-HQ
d e s t i n a t i o n - p a t t e r n 2 . ..
port 0/1/0:23
I
v o i c e t r a n s l a t i o n - r u l e 1
r u l e 1 r2l /15115552/
i
•
v o i c e t r a n s l a t i o n - p r o f i l e to-HQ
t r a n s l a t e c a l l e d 1
The first part of the SRST configuration includes the dialplan-pattern command
configured under call-manager-fallback configuration mode, which maps the internal
four-digit directory numbers to the E.164 PSTN number.
COR lists are configured for internal destinations called internal, for international PSTN
destinations named pstn-intl, and for all other PSTN destinations labeled pstn. These COR
lists are applied to dial peers as outgoing COR lists. Their function is equivalent to partitions
in CUCM.
Additional COR lists are configured, one per phone. These are applied as incoming COR
lists to phone directory numbers using the cor incoming command in call-managerfallback
configuration mode. The configuration shown in Example 6-16 applies the
incoming COR list phonel, which is equivalent to CSSs in CUCM, to phone 1, which
registers with the SRST gateway with a directory number of 3001, incoming COR list
phone2 to the phone with directory number 3002, and incoming COR list phone3 to the
phone with directory number 3003.
Outgoing COR lists are applied to the dial peers that are used as outgoing dial peers: dial
peer 9011 for international PSTN calls, dial peer 9 for PSTN calls, and dial peer 2000 for
calls to headquarters.
150 Chapter 6: Implementing Cisco Unified SRST and MGCP Fallback
NOTE For simplicity, Example 6-16 does not show all the outbound dial peers, as
shown previously in Example 6-9. Using the destination pattern 9T as shown in dial
peer 9 typically is avoided when possible for local or national calls to avoid the interdigit
timeout associated with the T wildcard.
Dial peer 1 is configured for inbound dialing from the PSTN with the incoming callednumber
command to identify all destination phone numbers. Direct inward dialing is enabled,
which turns off the second dial tone at ISDN port 0/1/0:23 for external calls dialing in.
The called E.164 numbers (521-555-3xxx) are mapped to four-digit extensions because of
the dialplan-pattern command that is configured in call-manager-fallback configuration
mode. As a result, incoming PSTN calls are sent to the four-digit extensions.
Outgoing calls to phones located at the main site at extensions 2xxx match a destination
pattern in dial peer 2000. Dial peer 2000 sends calls to port 0/1/0:23 after performing digit
manipulation using the to-HQ voice translation profile. This profile translates the four-digit
called number to an 11-digit E. 164 PSTN number. The result is that during SRST fallback,
users can still dial four-digit extensions to reach phones in headquarters.
