Configure Gatekeeper and SIP Server

For the best practice, Polycom recommends configuring gatekeeper and SIP server.

Procedure

  1. Connect to RealPresence Collaboration Server through RMX Web Client/RMX Manager application.
  2. Go to RMX Management > Rarely Used > IP Network Services.


  3. Double click the Default IP Service from the IP Network Services page.


  4. Go to Gatekeeper and complete the fields.
    Gatekeeper Field Description
    Gatekeeper

    Select Specify to enable configuration of the gatekeeper IP address.

    When Off is selected, all gatekeeper options are disabled.

    Primary Gatekeeper IP Address or Name Enter either the gatekeeper’s host name as registered in the DNS or IP address.
    Alternate Gatekeeper IP Address or Name

    Enter the DNS host name or IP address of the gatekeeper used as a fallback gatekeeper used when the primary gatekeeper is not functioning properly.

    Note: When in IPv4&IPv6 or in IPv6 mode, it is easier to use Names instead of IP Addresses.
    Alternate Gatekeeper IP Address or Name

    Enter the DNS host name or IP address of the gatekeeper used as a fallback gatekeeper used when the primary gatekeeper is not functioning properly.

    Note: When in IPv4&IPv6 or in IPv6 mode, it is easier to use Names instead of IP Addresses.
    MCU Prefix in Gatekeeper

    Enter the number with which this Network Service registers in the gatekeeper.

    This number is used by H.323 endpoints as the first part of their dial-in string when dialing the MCU.

    When another gatekeeper is used, this prefix must also be defined in the gatekeeper.

    Register as Gateway

    Select this check box if the RealPresence Collaboration Server is to be seen as a gateway, for example, when using a Cisco gatekeeper.

    Note: Do not select this check box when using Polycom ReadiManager or a Radvision gatekeeper.
    Refresh Registration every __ seconds

    The frequency with which the system informs the gatekeeper that it is active by re-sending the IP address and aliases of the IP cards to the gatekeeper. If the IP card does not register within the defined time interval, the gatekeeper will not refer calls to this IP card until it re-registers. If set to 0, re-registration is disabled.

    Note:
    • It is recommended to use default settings.
    • This is a re-registration and not a ‘keep alive’ operation – an alternate gatekeeper address may be returned.
    Aliases
    Alias

    The alias that identifies the Collaboration Server’s Signaling Host within the network. Up to five aliases can be defined for each Collaboration Server.

    Note:

    When a gatekeeper is specified, at least one alias must be entered in the table.

    Additional aliases or prefixes may also be entered.

    Type

    The type defines the format in which the card’s alias is sent to the gatekeeper. Each alias can be of a different type:

    • H.323 ID (alphanumeric ID)
    • E.164 (digits 0-9)
    • Email ID (email address format, e.g. abc@example.com)
    • Participant Number (digits 0-9, * and #)
    Note: Although all types are supported, the type of alias to be used depends on the gatekeeper’s capabilities.


  5. Click OK.