19.08.2013 Views

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

RMX 2000 Administrator's Guide Version 7.6.1 - Polycom

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

8 Select the following parameters:<br />

Appendix H-Setting the <strong>RMX</strong> for Integration Into Microsoft Environment<br />

— In Assign users to a pool field, select the required pool.<br />

— In the Generate user SIP URI, define the SIP URI of the conferencing entity using one<br />

of the following methods:<br />

• Select the Specify a SIP URI option and enter the conferencing entity user<br />

portion of SIP URI defined in the active directory. This SIP URI must match the<br />

conferencing entity Routing Name configured in <strong>RMX</strong>. For example, for the<br />

meeting room account sip:vmr10@wave4.eng, use only the vmr10 portion of<br />

the address.<br />

or<br />

• Select the Use the user principal name (UPN) option.<br />

9 Click the Enable button.<br />

The selected user appears as enabled in the User Search pane.<br />

Defining the Microsoft SIP Server in the IP Network Service<br />

To enable the registration of the conferencing entities the SIP Server Type must be set to<br />

Microsoft and the Office Communication Server or Lync Server properties in the IP Network<br />

Service - SIP Servers dialog box.<br />

For more details, see "Configuring the <strong>RMX</strong> IP Network Service” on page H-36.<br />

Enabling Registration in the Conference Profile<br />

Registration of conferencing entities such as ongoing conferences, Meeting Rooms, Entry<br />

Queues, SIP Factories and Gateway Sessions with SIP servers is done per conferencing entity.<br />

This allows better control on the number of entities that register with each SIP server.<br />

<strong>Polycom</strong>, Inc. H-53

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!