User`s guide

Introducing MultiVoice Gateway concepts
What is MultiVoice for the MAX?
MultiVoice Gateway for the MAX— User’s Guide Preliminary November 23, 1998 1-3
3 MultiVoice Gateway 1 forwards the phone number and PIN authentication to the
MultiVoice Access Manager.
4 The 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.
When Caller B answers the phone (goes off-hook), voice traffic is tunneled in IP packets, using
the IETF-standardized RTP protocol, between MultiVoice Gateway 1 and MultiVoice Gateway
2.
If the callers in Figure 1-2 used a traditional voice communications network, Caller A would
require a long-distance carrier’s services to reach Caller B. But, Caller A is in MultiVoice
Gateway 1’s coverage area, and can reach the Gateway with a local call. The IP-routed
network performs the same function as a long-distance carrier’s circuit-switched network.
Coverage Areas
Each MultiVoice Gateway services a coverage area, a group of telephone numbers that may
dial and receive calls through a particular MultiVoice Gateway. Coverage areas for each
MultiVoice Gateway are defined by assigning dial strings, such as country codes, area codes,
country code/area code combinations, area code/exchange combinations or complete
telephone numbers, and so forth, to a database on the Gatekeeper.
Individually, these phone numbers and dial strings represent individual inclusion areas.
Together, these inclusion areas represent the coverage area for a MultiVoice Gateway. For
example, an inclusion area may be specified by the partial telephone number '1732'. This
number is composed of a country code of '1' and area code of '732'. A MultiVoice Gateway
with this inclusion area would cover all telephone numbers within the 732 area code.
Multivoice network with a secondary Gatekeeper
Figure 1-3 shows an example of a MultiVoice network processing a call through a secondary
Gatekeeper. The secondary Gatekeeper configuration is designed to provide the MultiVoice
network with redundant call management capability.
Starting with TAOS Release 7.0.0, each MultiVoice Gateway may be configured to register
with a secondary Gatekeeper when it cannot register with the primary Gatekeeper. This
enables call processing to continue in the event that the primary Gatekeeper cannot be reached
by a MultiVoice Gateway.