Configuring MultiVoice
Using authentication
MultiVoice Gateway for the MAX— User’s Guide
Preliminary November 23, 1998
6-19
Using authentication
When callers dial into the MultiVoice Gateway:
•
If PIN authentication is enabled, the Gateway presents the caller either with a dial tone or
with a prompt indicating that the MultiVoice Access Manager requires PIN authentication.
•
If ANI authentication is enabled, the Gateway collects the ANI information from the
caller’s telephone, passes it to MVAM for verification, then presents the caller either with
second dial tone, from the Gateway, or a fast-busy tone when it rejects a call.
When you do not require PIN authentication
When you do not configure PIN 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 (#).
4
The local MultiVoice Gateway initiates a session with the MultiVoice Access Manager,
passing the destination phone number to it.
5
The MultiVoice Access Manager sends the local MultiVoice Gateway the IP address of the
destination MultiVoice Gateway, selected on the basis of configured coverage areas.
If the MVAM finds no MultiVoice Gateway with a coverage area that supports the called
number, the local MultiVoice Gateway disconnects the call.
6
The local MultiVoice Gateway initiates a session with the destination MultiVoice
Gateway.
7
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.
8
The destination MultiVoice Gateway dials the destination phone number, and the
connection is complete.
If the caller does not press the pound sign after entering a string of digits, the MultiVoice
Gateway waits for a timer to expire, then sends the string to the MultiVoice Access Manager.
Initially set to 16 seconds, the timer starts running when the caller enters the first digit, but
restarts after each subsequent digit. However, each restart decrements the timer by one
seconds, up to a maximum of 14. If the caller enters 15 or more digits, the MultiVoice Gateway
waits two seconds before sending the string.
If the call is not established in several seconds, the local MultiVoice Gateway sends a tick-tock
sound to the caller which indicates that the call is still proceeding.
Note:
Unless your T1 or E1 line supports ISDN signaling, callers might not receive some call
information, such as busy signals.