1-4
Preliminary November 23, 1998
MultiVoice Gateway for the MAX— User’s Guide
Introducing MultiVoice Gateway concepts
What is MultiVoice for the MAX?
As illustrated in Figure 1-3, two MultiVoice Gateways connect Caller A to Caller B. Either of
the systems running the MultiVoice Access Manager can be the Gatekeeper.
Figure 1-3. Example of a MultiVoice network with a secondary Gatekeeper
When Caller A dials Caller B, the following events occur:
1
Caller A dials MultiVoice Gateway 1, and enters their PIN authentication (if required) and
Caller B’s phone number.
2
MultiVoice Gateway 1 attempts to register with it’s primary Gatekeeper.
If the registration fails, MultiVoice Gateway 1 attempts to register with its secondary
Gatekeeper.
3
When registration is established with the secondary Gatekeeper, MultiVoice Gateway 1
forwards the phone number and PIN authentication to the secondary Gatekeeper.
4
The secondary Gatekeeper authenticates Caller A and, if successful, forwards the IP
address of MultiVoice Gateway 2 to MultiVoice Gateway 1.
5
MultiVoice Gateway 1 establishes a session with MultiVoice Gateway 2.
6
MultiVoice Gateway 2 forwards the call request to Caller B.
The primary and secondary Gatekeepers are separate systems (Gatekeepers), each running its
own copy of the MVAM application, and are designed to function independent of the other.
Each Gatekeeper has unique gateway and user databases, and each maintains separate call and
activity logs. To ensure coverage, the two Gatekeepers must duplicate gateway and user
information. The secondary Gatekeeper does not report call activity to, nor share call records
with the primary Gatekeeper.
Gatekeeper registration policy and failure detection
Registration with the primary Gatekeeper fails when the MultiVoice Gateway cannot register
within five (5) registration attempts, at 5-seconds intervals, unless you change the defaults. If
registration fails, the MultiVoice Gateway does one of the following:
•
The MultiVoice Gateway attempts to register with the secondary Gatekeeper, if a valid IP
address (non-null) is configured for the
2nd
GK
IP
parameter. The same registration
policy applies (five registration attempts at five-second intervals) as with the primary
Gatekeeper.
PSTN
PSTN
IP network
MultiVoice
Gateway 1
MultiVoice
Gateway 2
Primary
Gatekeeper
Caller B
Caller A
Secondary
Gatekeeper
