Polycom MGC Administrator, Руководство администратора

Страница: 121 / 584

MGC Administrator’s Guide
3-71
Service Mode
(cont.) Note : In current Cisco implementations when
there is more than one IP card in use, the
gatekeeper selects one of the boards that are
registered with the dialed string. Thus the system
does not automatically forward the calls to an
available card. To overcome this problem,
combine
Register as a Gateway with Forwarding.
However, this method only works for defined dial-
in participants.
•
PseudoGatekeeper – Each IP card acts and is
defined as a gatekeeper allowing Board Hunting
to be performed. In PseudoGatekeeper mode, the
IP cards are manually registered with the
gatekeeper as neighboring gatekeepers. When
the gatekeeper receives an Admission Request
(ARQ) message from a participant looking for the
conference alias, the gatekeeper will forward the
request to all “neighboring gatekeepers” (IP
cards) simultaneously. The first card that has
enough resources to handle the call accepts the
request.
Note : Gatekeepers often send a multicast LRQ
message hoping that there is a gatekeeper that
can help with the translation. Multicast LRQ
messages are not handled by the MCU IP cards
within the Pseudo Gatekeeper mode.
•
PseudoGatekeeper-AVF – Applicable to the
Avaya environment only.
Prefix Enter a number to be used by H.323 participants to
dial to the MCU as part of the dial-in string. Usually,
one Network Service is defined for all IP cards to let
the system automatically manage the resources
allocated to conferences. When one Network Service
is defined per card, the MGC Manager operator must
manage the conferencing resources since there is no
automatic pooling.
Table 3-19: H.323 Dialog Box Parameters (Continued)
Field Description