This section provides information about how the Automatic Number Identification (ANI) feature interacts with other features on the system. Use this information to ensure that you receive the maximum benefits of ANI in any feature configuration.
Attendant Console
If an attendant extends a call, the attendant’s Class of Restriction (COR) is used to select the ANI prefix.
Authorization Codes
The authorization code COR is used to select the ANI prefix. The extension’s ANI is used if an extension originates the call. The ANI for the server is used if the originating endpoint is an incoming MF or SIP 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 that is sent to the CO is determined by the ANI for PBX field, 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 the ANI prefix.
Hunt Groups and Automatic Call Distribution (ACD) Splits
The phone’s extension and the COR is used to determine the ANI prefix for a hunt group or ACD split.
Multimedia Call Handling (MMCH)
For call origination, multimedia complexes use the COR assigned to their phones.
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. The ANI for the server is used if the originating endpoint is an incoming trunk.
Separation of Bearer and Signaling
The Separation of Bearer and Signaling feature can provide ANI while the media stream is going over a type of trunk that cannot provide ANI.
