User`s guide

Configuring MultiVoice
Using authentication
MultiVoice Gateway for the MAX— User’s Guide Preliminary November 23, 1998 6-21
When you require ANI authentication
If you configure ANI authentication, the MultiVoice Gateway processes calls as follows:
1 The caller dials the local MultiVoice Gateway.
2 The local MultiVoice Gateway presents a dial tone to the caller.
3 The caller enters the destination phone number, followed by the pound sign (#).
Note: The caller may experience up to 10 seconds of silence after dialing during ANI
processing.
4 The local MultiVoice Gateway collects the ANI for the calling phone number.
5 The MultiVoice Gateway initiates a session with the Gatekeeper running MultiVoice
Access Manager and passes the ANI and destination phone number to it.
6 MultiVoice Access Manager compares the ANI to the User Alias information in the user
database.
If the ANI does not match a User Alias, MultiVoice Access Manager disconnects the
caller.
7 If the ANI matches a User Alias, MultiVoice Access Manager selects the IP address of the
destination MultiVoice Gateway, on the basis of configured coverage areas, and sends it to
the local MultiVoice Gateway.
If MVAM finds no MultiVoice Gateway with a coverage area that supports the called
number, the local MultiVoice Gateway disconnects the call.
8 The local MultiVoice Gateway initiates a session with the destination MultiVoice
Gateway.
9 The destination MultiVoice Gateway initiates a session with the MVAM to determine if it
approved the call. The MultiVoice Access Manager acknowledges the call request from
the distant Gateway.
If the MVAM rejects the call request, the destination MultiVoice Gateway disconnects the
call.
10 The destination MultiVoice Gateway dials the destination phone number to complete the
connection.
The MultiVoice Gateway collects the caller’s ANI and forwards it, in the Acknowledge
Request (ARQ) message, along with the destination phone number, to the MultiVoice Access
Manager. If the ANI matches the information in the user database, call setup continues.
Note: Since the MultiVoice Gateway collects both ANI and DNIS as a single operation,
callers may experience a delay of up to 10 seconds for processing before hearing a dial tone,
fast-busy, or other call progress tones.
For information on configuring ANI collection see “Collecting DNIS and ANI” on page 5-4
!
Caution: ANI authentication does not work across WANs or behind PBXs that do not
support delivery of DNIS/ANI.