Sdílet prostřednictvím

  • Článek

Enterprise Voice Deployment Process

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Topic Last Modified: 2015-03-09

The following tables describe the deployment steps for each Enterprise Voice implementation option.

Table 1. Enterprise Voice Deployment Process with PBX Coexistence

Deployment steps Permissions Documentation

1. Deploy Office Communications Server, including a Mediation Server that connects to the PBX.

  • Create Enterprise pool: RTCUniversalServerAdmins and Domain Admins or equivalent credentials.

  • Configure pool: RTCUniversalServerAdmins.

  • Add server to pool: RTCUniversalServerAdmins.

  • Configure certificate: RTCUniversalServerAdmins.

  • Configure Web Components Server certificate: Local Administrator credentials.

  • Validate server and pool functionality: RTCUniversalServerAdmins.

Deploying Office Communications Server 2007 R2 documentation

Step 5. Deploy a Mediation Server in Deploying Enterprise Voice in the Deployment documentation

2. Deploy Office Communicator 2007 and any other voice clients.

Administrator on the computer on which Office Communicator is being installed.

Deploying Communicator in the Client Planning and Deployment documentation

3. Enable users for IM and presence.

RTCUniversalUserAdmins group.

Create and Enable Users in Deploying Office Communications Server 2007 R2 Enterprise Edition or in the Deploying Office Communications Server 2007 R2 Standard Edition in the Deployment documentation

4. Configure Office Communications Server for Enterprise Voice.

RTCUniversalServerAdmins group.

Office Communications Server 2007 R2 Enterprise Voice Deployment Guide in the Deployment documentation

5. Configure PBX to fork calls to Office Communications Server.

RTCUniversalServerAdmins (to get information from AD DS to convert an extension into the correct telephone URI).

See your PBX manufacturer’s documentation.

6. Deploy media gateways (if required).

Media gateways are external systems with their own authentication and authorization schemes. If the media gateway requires creation of trusted service entries, you must be at least a member of the RTCUniversalServerAdmins group.

Step 5. Deploy a Mediation Server in the Deploying Enterprise Voice documentation

See your media gateway manufacturer’s documentation.

7. Deploy RCC gateway (if required).

RCC gateways are external systems with their own authentication and authorization schemes. You must be at least a member of the RTCUniversalServerAdmins group to create the required trusted service entries.

See your RCC gateway manufacturer’s documentation.

8. Enable users for Enterprise Voice and PBX integration.

RTCUniversalUserAdmins group.

Step 8. Enable Users for Enterprise Voice in the Deploying Enterprise Voice documentation

Step 9. Enable Users for PBX Integration (Optional) in the Deploying Enterprise Voice documentation

Table 2. Stand-Alone Enterprise Voice Deployment Process: Greenfield

Deployment steps Permissions Documentation

1. Deploy Office Communications Server.

  • Create Enterprise pool: RTCUniversalServerAdmins and Domain Admins or equivalent credentials.

  • Configure pool: RTCUniversalServerAdmins.

  • Add server to pool: RTCUniversalServerAdmins.

  • Configure certificate: RTCUniversalServerAdmins.

  • Configure Web Components Server certificate: Local Administrator credentials.

  • Validate server and pool functionality: RTCUniversalServerAdmins.

Deploying Office Communications Server 2007 R2 documentation

2. Deploy Office Communicator 2007 and any other voice clients.

Administrator on the computer on which Office Communicator is being installed.

Deploying Communicator in the Client Planning and Deployment documentation

3. Configure Office Communications Server for Enterprise Voice.

RTCUniversalUserAdmins group.

Office Communications Server 2007 R2 Enterprise Voice Deployment Guide in the Deployment documentation

4. Deploy Exchange Server 2007 Unified Messaging and configure to integrate with Office Communications Server.

  • For Office Communications Server: RTCUniversalServerAdmins group.

  • For Exchange Server: Exchange Organization Administrators permissions are sufficient when Office Communications Server and Exchange Server are running in the same forest.

    Note

    The user account used to configure Exchange Unified Messaging must have READ access to Office Communications Server pools in AD DS and READ/WRITE access on the Exchange configuration containers (First Organization\UM Dial Plan Container, UM IP Gateway Container, UM Auto Attendant Container, and so on).

Step 1. Configure Unified Messaging on Microsoft Exchange to Work with Office Communications Server in the Deploying Enterprise Voice documentation

5. Deploy media gateways.

Media gateways are external systems with their own authentication and authorization schemes. If the media gateway requires creation of trusted service entries, you must be at least a member of the RTCUniversalServerAdmins group.

Step 5. Deploy a Mediation Server in the Deploying Enterprise Voice documentation

See your media gateway manufacturer’s documentation.

6. Enable users for Enterprise Voice.

RTCUniversalUserAdmins group.

Step 8. Enable Users for Enterprise Voice in the Deploying Enterprise Voice documentation

Table 3. Stand-Alone Enterprise Voice Deployment Process: Departmental

Deployment steps Permissions Documentation

1. Deploy Office Communications Server.

  • Create Enterprise pool: RTCUniversalServerAdmins and Domain Admins or equivalent credentials.

  • Configure pool: RTCUniversalServerAdmins.

  • Add server to pool: RTCUniversalServerAdmins.

  • Configure certificate: RTCUniversalServerAdmins.

  • Configure Web Components Server certificate: Local Administrator credentials.

  • Validate server and pool functionality: RTCUniversalServerAdmins.

Deploying Office Communications Server 2007 R2 documentation

2. Deploy Office Communicator 2007 and any other voice clients.

Administrator on the computer on which Office Communicator is being installed.

Deploying Communicator in the Client Planning and Deployment documentation

3. Configure Office Communications Server for Enterprise Voice.

RTCUniversalUserAdmins group.

Office Communications Server 2007 R2 Enterprise Voice Deployment Guide in the Deployment documentation

4. Enable users for IM and presence.

RTCUniversalServerAdmins group.

Client Access

5. Deploy Exchange Server 2007 Unified Messaging and configure to integrate with Office Communications Server.

  • For Office Communications Server: RTCUniversalServerAdmins group.

  • For Exchange Server: Exchange Organization Administrators permissions are sufficient when Office Communications Server and Exchange Server are running in the same forest.

    Note

    The user account used to configure Exchange Unified Messaging must have READ access to Office Communications Server pools in AD DS and READ/WRITE access on the Exchange configuration containers (First Organization\UM Dial Plan Container, UM IP Gateway Container, UM Auto Attendant Container, and so on).

Step 1. Configure Unified Messaging on Microsoft Exchange to Work with Office Communications Server in the Deploying Enterprise Voice documentation

6. Deploy media gateways.

Media gateways are external systems with their own authentication and authorization schemes. If the media gateway requires creation of trusted service entries, you must be at least a member of the RTCUniversalServerAdmins group.

Step 5. Deploy a Mediation Server in the Deploying Enterprise Voice documentation

See your media gateway manufacturer’s documentation.

7. Enable one or more subsets of users for Enterprise Voice.

RTCUniversalUserAdmins group.

Step 8. Enable Users for Enterprise Voice in the Deploying Enterprise Voice documentation

8. Migrate users to Enterprise Voice in one or more phases.

RTCUniversalUserAdmins group.

Note

Membership in RTCUniversalServerAdmins may be required if the migration requires changing server configuration.

Migration from Office Communications Server 2007 and Migration from Live Communications Server 2005 in the Migration documentation

Table 4. Stand-Alone Enterprise Voice Deployment Process: PBX Integration to Stand-Alone Option

Deployment steps Permissions Documentation

1. Deploy media gateways.

Media gateways are external systems their own authentication and authorization schemes. If the media gateway requires creation of trusted service entries, you must be at least a member of the RTCUniversalServerAdmins group.

Step 5. Deploy a Mediation Server in Deploying Enterprise Voice in the Deployment documentation

See your media gateway manufacturer’s documentation.

2. Reassign DID numbers (if any) to media gateways.

PBX permissions.

See your media gateway manufacturer’s documentation.

3. Deploy and configure Exchange Unified Messaging. This can be done before, after, or concurrently with deployment of media gateways.

  • For Office Communications Server: RTCUniversalServerAdmins group.

  • For Exchange Server: Exchange Organization Administrators permissions are sufficient when Office Communications Server and Exchange Server are running in the same forest.

    Note

    The user account used to configure Exchange Unified Messaging must have READ access to Office Communications Server pools in AD DS and READ/WRITE access on the Exchange configuration containers (First Organization\UM Dial Plan Container, UM IP Gateway Container, UM Auto Attendant Container, and so on).

Step 1. Configure Unified Messaging on Microsoft Exchange to Work with Office Communications Server in the Deploying Enterprise Voice documentation

4. If necessary, rename location profiles to the FQDN of their corresponding Exchange Unified Messaging dial plans.

RTCUniversalServerAdmins group.

Location Profiles

5. Replace PBX desktop phones with Office Communicator and/or Communicator Phone Edition or other SIP clients.

None.

Telephony Devices

Note

The migration path in table 4 is used only if PBX integration is used as a stepping stone to a stand-alone Office Communications Server deployment.