Configuring COR for SRST
The archetype illustrated in Figure 7-36 and Archetype 7-39 shows how to configure COR
for SRST.
Chapter 7: Configuring Advanced Punch Plans 433
V V
WAN
Extensions:
2000 - 2100
R1 R2 Unified
Communications
Manager
Figure 7-36 COR SRST Scenario Topology
Example 7-39 SRST COR Configuration
R1(config)#call-manager-fallback
R2(config-cm-fallback)#cor admission INTL 1 2000 – 2100
To configure COR for SRST, use the cor command in SRST agreement mode.
You can accept up to 20 corlists for anniversary admission and approachable call. A absence COR is
assigned to agenda numbers that do not bout any corlist numbers or cardinal ranges.
An assigned COR is invoked for the punch aeon and created for anniversary agenda number
automatically during Communications Manager fallback registration.
When allotment an admission or approachable corlist to SRST ephones, corlists can be
assigned to a specific agenda cardinal ambit (as the afterward syntax illustrates) or a
default corlist can be applied.
Router(config)#call-manager-fallback
Router(config-cm-fallback)#cor admission intl 1 2000 - 2100
The syntax of the cor command issued in call-manager-fallback agreement approach is
cor {incoming | outgoing} cor-list-name [cor-list-number starting-number -
ending-number | default]
The afterward is an account of the syntax:
■ incoming: corlist to be acclimated by admission punch peers.
■ outgoing: corlist to be acclimated by approachable punch peers.
■ cor-list-name: corlist name.
■ cor-list-number: corlist identifier. The best cardinal of corlists that can be created
is 20, absolute admission or approachable punch peers. The aboriginal six corlists are
applied to a ambit of agenda numbers. The agenda numbers that do not accept a
COR agreement are assigned to the absence corlist, provided a absence corlist has
been defined.
■ starting-number - ending-number: Agenda cardinal range, such as 2000–2025.
■ default: Instructs the router to use an absolute absence corlist.