NEC Electra Elite IPK II System User Manual page 966

Document Revision 4C
ANI/DNIS Compatibility
The system is compatible with Telco T1 Automatic Number Identification (ANI) and Dialed Number
Information Service (DNIS) services. A compliment to Caller ID service, ANI/DNIS Compatibility
provides:
Receive Format

The Receive Format must be set as
as a Feature Group D format. (Example of ANI Information KP009727517645STKP7100ST.)
Flexible Routing

Based on the data received, the system can route the incoming ANI/DNIS call to:
An extension

An ACD or Voice Mail master extension number

A VRS and play a VRS message to the caller

A Department Group pilot number

A trunk Ring Group

Route According to DID Translation Table or Speed Dial Bins

Calls can be routed based on either the number of digits defined in Program 22-09-01 (digits 1~8)
or by digits entered in Speed Dial bins in Program 13-04-01.
ANI/DNIS Data Displayed as Caller ID Data
Data Error and Unanswered Call Handling

If a call can not be completed, send it to a predetermined Ring Group or play supervisory tones to
the caller.
Conditions
T1 Trunking requires a T1/PRI Interface ETU and a customer-provided CSU/DSU to

interface with the Telco. Consult your sales representative and the System Hardware
Manual for additional details.
ANI/DNIS Compatibility requires the use of system DTMF receivers. When all receivers are

busy, the incoming ANI/DNIS call waits for a receiver to become available.
The ANI/DNIS/Address data received from the Telco can have up to 10 digits.

An extension Class of Service (Program 20-09-02) determines whether ANI information is

displayed.
Refer to

tone.
The T1 Tie Line can be used for networking.

2 - 942

Dial Tone Detection on page 2-293
ANI DNIS in Program 34-09-01 option 4, which is treated
 
for the specifics on how the system detects dial
T1 Trunking (with ANI/DNIS Compatibility)
Electra Elite IPK II