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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

Configuring Office Communicator Users for Enterprise Voice<br />

Each of the endpoints in the OCS environment must be set to use the voice route.<br />

The setting is done in the Office Communications Server management console for all<br />

required users (endpoints) simultaneously or in the Active Directory for each of the Users<br />

(endpoints).<br />

To Configure Office Communicator Users for Enterprise Voice in the Office<br />

Communications Server management console:<br />

1 Navigate to Start > All Programs > Administrative Tools > Office Communications<br />

Server 2007 R2 to open the Office Communications Server management console.<br />

2 Expand the Enterprise pool or Standard Edition server node where your users reside.<br />

3 Expand the pool or server where your users reside, and then click the Users node.<br />

4 In the right pane, right-click one or more users whom you want to configure, and then<br />

select Configure users.<br />

The Welcome to the Configure Users Wizard opens.<br />

5 On the Welcome to the Configure Users Wizard dialog box, click Next.<br />

6 On the Configure User Settings dialog box, click Next.<br />

7 On the Configure Meeting Settings dialog box, click Next.<br />

8 On the Configure User Settings specify meeting policy dialog box, click Next.<br />

9 On the Configure Enterprise Voice dialog box, select Change Enterprise Voice Settings<br />

for selected users, and then click Enable Enterprise Voice. Click Next.<br />

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

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

Saved successfully!

Ooh no, something went wrong!