Administrator's Guide

Features and technical reference
555-233-5061498 Issue 5 October 2002
Interactions
■ Attendant Console
If an attendant extends a call, the attendant’s COR is used to select ANI.
■ Authorization Codes
The authorization code COR is not used to select the ANI. The extension’s
ANI is used if an extension originates the call, and the ANI for the switch is
used if the originating endpoint is an incoming trunk.
■ Bridged Call Appearance
A call from a bridged call appearance uses the ANI of the primary
extension.
■ Call Vectoring
The ANI of the originating party is used, not the ANI of the call vector,
when a call vectoring route-to command routes a call over an outgoing
trunk.
■ Distributed Communications System (DCS)
In a DCS, the ANI sent to the CO is determined by the ANI for PBX on
PBX_B, but the category sent to the CO is determined by the Category for
MF ANI field on the Class of Restriction screen for the incoming DCS
trunk or by the type of call.
■ Expert Agent Selection (EAS)
The EAS agent’s login extension and COR is used to determine ANI.
■ Hunt Groups and Automatic Call Distribution (ACD) Splits
The phone’s extension and COR is used to determine ANI for a hunt group
or ACD split.
■ Multimedia Call Handling (MMCH)
For call origination, multimedia complexes use the COR assigned to their
phones.
■ Personal Station Access (PSA)
For ANI, the PSA extension and COR overrides the phone’s extension and
COR.
■ Remote Access
A remote access barrier code COR is not used for ANI. The extension’s
ANI is used if an extension originates the call, and the ANI for the switch is
used if the originating endpoint is an incoming trunk.