Polycom MGC-100 Getting Started Manual page 68

MGC-50/MGC-100 Getting Started Guide
3-38
Table 3-11: H.323 Dialog Box Parameters (Continued)
Field
Service Mode
(cont).
Prefix
Description
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.
Enter the same prefix that has been defined for the
Network Service in the gatekeeper. This number is
used as part of the dial-in string given to participants.
You can define several Network Services on the
MCU with each one of them containing one, several
or all IP cards.
Usually, one Network Service is defined for all IP
cards to let the system automatically manage the
resources allocated to conferences, as one prefix is
used for the Network Service. In this case, the
system finds the free cards from the pool of cards
registered with the IP Network Service.
When one Network Service is defined per card, the
MGC Manager operator must manage the
conferencing resources since there is no automatic
pooling.