
Feature Reference
Generalized route selection
Administrator’s Guide for Avaya Communication Manager
1545
November 2003
•
BCC 2
If there is no preference with BCC 2 yes, GRS chooses a preference with BCC 0 yes. If BCC 0
yes does not exist, the call is blocked.
•
BCC 1, 3, or 4
BCC 4 (DCP/DMI Mode 0), BCC 1 (Mode 1), and BCC 3 (Mode 3) calls requires an exact match
in order for the call to complete. ITCs must also match.
Example
Assume a route pattern is set up with BCC 0 and BCC 2 set to yes in preference 1, and BCC 1, BCC 3,
and BCC 4 set to yes in preference 2.
A voice or Mode 2 data call accessing this pattern uses preference 1. A Mode 1, Mode 3, or Mode 0 data
call uses preference 2, regardless of what trunks are available in the first preference.
Data modules and GRS
For all endpoints, Communication Manager automatically determines its current operating mode when a
data module begins operations. The default is Mode 2.
Because call origination from a data module determines the mode used on the call, you should press the
Originate/Disconnect button if you change data options. This way, the right mode is assigned to the next
call.
Table 59, BCC assignment,
on page 1546 lists the BCC for different types of information and endpoints.
Table 58: Determination of ITC codepoint
Originating
Endpoint’s
ITC
Routing Preference’s ITC
ITC
codepoint
in BC IE
restricted
un-
restricted
both
endpoint
both un-
restricted
voice
x
restricted
voice
x
unrestricted
voice
x
unrestricted
voice
x
unrestricted