Filter
Top Products
Appendix H-Setting the MCU for Integration Into Microsoft Environment
Polycom, Inc. H-57
Verifying the MCU Conferencing Entity Routing Name and Profile
MCU conferencing entity can be dialed directly from the buddy list of the Office
Communications client or the Lync client if its routing name matches the user name of Active
Directory account you created and Registration is enabled in the Conference Profile assigned
to it.
• To ensure that the MCU meeting room or conferencing entity is properly configured for
registration the following parameters must be defined:
— The user name on the conferencing entity in Active Directory account must be
identical to its Routing Name on the MCU.
For example, if the SIP URI in the Active Directory is
sip:vmr10@wave4.eng
, it must
be defined as
vmr10
in the Routing Name field of that MCU conferencing entity.
— In the Profile field, make sure that a conference Profile that has been enabled for SIP
registration is selected.
Monitoring the Registration Status of a Conferencing Entity in the RealPresence
Collaboration Server (RMX) Web Client or RMX Manager Application
The Status of the SIP registration can be viewed in the appropriate conferencing Entity list
or when displaying its properties.
Conferencing Entity List
The list of conferencing entity includes an additional column - SIP Registration, which
indicates the status of its registration with the SIP server. The following statuses are
displayed:
• Not configured - Registration with the SIP Server was not enabled in the Conference
Profile assigned to this conferencing Entity. In Multiple Networks configuration, If one
service is not configured while others are configured and registered, the status reflects
the registration with the configured Network Services. The registration status with each
SIP Server can be viewed in the Properties - Network Services dialog box of each
conferencing entity.
When SIP registration is not enabled in the conference profile, the MCU's registering to
SIP Servers will each register with an URL derived from its own signaling address. This
unique URL replaces the non-unique URL, dummy_tester, used in previous versions.
• Failed - Registration with the SIP Server failed.
This may be due to incorrect definition of the SIP server in the IP Network Service, or