Generalized Route Selection - Avaya Communication Manager Administrator's Manual

Feature Reference

Generalized route selection

Interactions
•
Call Detail Recording
If 15-digit CDR account codes are used, the FRL field in the CDR record is overwritten with the
account code.
Related topics
See Route Pattern on page 1125 to find more information on fields on the route pattern screen.
Generalized route selection
Generalized Route Selection (GRS) is built into AAR and ARS. Communication Manager uses GRS to
look at various route patterns and preferences and decide which preference is most appropriate at the
time. With GRS, voice and data calls can be sent along separate routes or be integrated on the same trunk
group. If the type of transmission is incompatible with the endpoint (for example, a digital data call is
sent to an analog phone), GRS provides a conversion resource such as a modem from a modem pool to
complete the call.
Detailed description
GRS recognizes one or more BCC for each trunk group preference in the route pattern. BCC defines the
type of information being sent as voice or data. Communication Manager checks the BCC for all trunk
groups to see if the route selected and type of call are compatible. The BCC is assigned to the route
preference on the Route Pattern screen.
GRS chooses a preference with BCC set to yes in this order: BCC 2, BCC 1, BCC 3, BCC 4.
When an exact match is not found in any route-pattern preference, calls with originating BCCs listed are
treated as follows:
•
BCC of 0 (such as voice or analog modem)
GRS routes a BCC 0-originated call with no match. This allows voice transfer to data when
making a data call.
Since BCC 0 (voice) has no Information Transfer Capability (ITC), Communication Manager
selects an ITC from the route pattern when a BCC 0 call is routed as a data call.
Determination of ITC codepoint,
Capability IE is determined.
1544
on page 1545 shows how the ITC codepoint in the Bearer
Administrator's Guide for Avaya Communication Manager
Table 58,
November 2003