(Part 2 of 3) The complete step-by-step setup guide for deploying Microsoft Unified Communications products with Enterprise Voice in a lab environment using a single Windows Server 2008 Hyper-V computer and a single Internet IP address


 

Configuring OCS 2007 R2 Edge

Next we will install the OCS 2007 R2 Edge role, which provides connectivity to the internal OCS environment for remote clients.  For the purposes of this lab, we will deploy a single Edge server supporting all three roles – Access Edge, Web Conferencing Edge, and Audio/Video Edge.  While the typical configuration for Edge involves the use of at least two network cards with each connected to a different network, we will use two virtual NICs which are both connected to the same network, as shown below.

EdgeNetConfig

 

Step 1 – Connect to the Virtual Machine that will host the OCS 2007 R2 Edge role

To configure one of the virtual machines to host the OCS 2007 R2 Edge server role, we’ll need to connect to the Windows 2008 host computer and launch the Server Manager console.  Expand the Hyper-V role and verify that the virtual machine for Edge was created with the following specifications: 


Role OCS 2007 R2 Edge
Memory 1024MB
Network Two (2) Virtual NICs
Hard Disk 16GB Virtual Hard Disk
OS Version Windows Server 2003 SP2 (x64)
FQDN Edge-R2.contoso.com (not domain-joined)
IP Addresses 192.168.1.2 – 192.168.1.4 (External NIC)
192.168.1.5 (Internal NIC)

Although the DNS name of this server will be Edge-R2.contoso.com, it will not be joined to the Contoso.com domain.  To configure the server, double-click on the Edge virtual server within the Hyper-V section of the Server Manager console.

 

 Step 2 – Configure OCS 2007 R2 Edge Network Settings

Before installing the OCS 2007 R2 Edge binaries, we need to configure the network settings for the virtual machine.

A.  To configure OCS 2007 R2 Edge network settings

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Click Start, then click Run.  Type ncpl.cpl and press Enter to launch Network Connections.
  3. Rename each of the two available network connections, as follows:
    a.  Right click on the first interface, choose Rename, then change it to Hyper-V Internal (192.168.1.5).
    b.  Right click on the other interface, choose Rename, then change it to Hyper-V External (192.168.1.2 – 192.168.1.4).

    EdgeNetConfig2

  4. Right click on the Hyper-V External (192.168.1.2 – 192.168.1.4) network interface and select Properties.
  5. Highlight Internet Protocol (TCP/IP) and click on the Properties button.

    Edge6

  6. Under the General tab of TCP/IP Properties, configure the network adapter as follows:

    Choose Use the following IP address.

         IP Address:  192.168.1.2
         Subnet Mask:  255.255.255.0
         Default Gateway:  192.168.1.1  (our Linksys Router)

    Choose Use the following DNS servers.
     
         Primary DNS Server:  4.2.2.1  (Internet root server)
         Alternate DNS Server:  4.2.2.2 (Internet root server)

    Edge7

  7. While still within the TCP/IP properties of the Hyper-V External network adapter, click on the Advanced button.
  8. Under the IP Settings tab, click Add.  Enter the following two additional IP addresses:

    IP Address:  192.168.1.3
    Subnet Mask:  255.255.255.0

    IP Address:  192.168.1.4
    Subnet Mask:  255.255.255.0

  9. Next, click on the DNS tab within Advanced settings.  Under Append these DNS suffixes (in order), click Add and enter the domain contoso.com.  Then, under DNS suffix for this connection, enter contoso.com.  Finally, deselect the option to Register this connection’s addresses in DNS.

    ISA_Networking_2

  10. Click OK three times to complete the configuration of the Hyper-V External network adapter.
  11. Right click on the Hyper-V Internal (192.168.1.5) network interface and select Properties.
  12. Highlight Internet Protocol (TCP/IP) and click on the Properties button.
  13. Under the General tab of TCP/IP Properties, configure the network adapter as follows:

    Choose Use the following IP address.

         IP Address:  192.168.1.5 
         Subnet Mask:  255.255.255.0
         Default Gateway:  (empty)

    Choose Use the following DNS servers.
     
         Primary DNS Server:  (empty) 
         Alternate DNS Server:  (empty)

    Edge9

  14. While still within the TCP/IP properties of the Hyper-V Internal network adapter, click on the Advanced button.
  15. Click on the DNS tab within Advanced settings, and deselect the option to Register this connection’s addresses in DNS.
  16. Click OK three times to complete the configuration of the Hyper-V Internal network adapter.
  17. Close Network Connections.
  18. Click Start, then Run.  Type Notepad %windir%\system32\drivers\etc\hosts to open the hosts file for editing.
  19. After opening the hosts file in Notepad, add each of the following entries.  To minimize complexity, I use a single hosts file with identical entries on both my Edge server and my ISA server.

    192.168.1.5    edge-r2.contoso.com
    192.168.1.6    isa.contoso.com
    192.168.1.6    cwa.contoso.com
    192.168.1.6    as.cwa.contoso.com
    192.168.1.6    download.cwa.contoso.com
    192.168.1.6    mail.contoso.com
    192.168.1.6    autodiscover.contoso.com
    192.168.1.10   email.contoso.com
    192.168.1.11   ocs-r2.contoso.com
    192.168.1.12   cwa-r2.contoso.com
    192.168.1.13   mediation-r2.contoso.com

    hostsfile

  20. Save your changes by clicking File then Save.  If you find that you are unable to save your changes and receive an Access Denied error message, then you will need to launch Notepad as the local Administrator account, create the various entries, then save the file.
  21. After successfully configuring the network settings for the virtual machine, restart the Edge server.

 

Step 3 – Install OCS 2007 R2 Edge

After configuring the virtual machine, we are now ready to install the OCS Edge server binaries.

A.  To install OCS 2007 R2 Edge

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click SetupSE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. When prompted to install the Microsoft Visual C++ 2008 Redistributable, choose Yes to install it.
  5. When prompted to install Microsoft .NET Framework 3.5 SP1, choose Yes to install it.
  6. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  7. On the Deploy Other Server Roles page, click Deploy Edge Server.

    DeployEdge

  8. On the Deploy Edge Server page, at Step 1: Install Files for Edge Server, click Install.
  9. On the License Agreement page, click I accept the terms in the license agreement, and then click Next. If you do not accept the license terms, Setup cannot continue.
  10. On the Install location for Microsoft Office Communications Server 2007 R2, Edge Server page, in the Location box, type a path where Edge server should be installed, or accept the default location. Click Next.
  11. After the Edge server has been installed successfully, click Close to return to the Edge deployment wizard.

 

Step 4 – Activate OCS 2007 R2 Edge

Having successfully installed the Edge server binaries, we are now ready to activate the server.

A.  To activate OCS 2007 R2 Edge

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  5. On the Deploy Other Server Roles page, click Deploy Edge Server.
  6. On the Deploy Edge Server page, at Step 2: Activate Edge Server, click Run.

    Edge2

  7. On the Welcome page, click Next.
  8. On the Select domain service account page, select Create a New Account.  Enter the name RTCProxyService in the Account name box, then type the account password in the Password box.  Click Next.

    Edge3

  9. Review the information on the Ready to Activate Edge Server screen.  If all information is correct, click Next to activate the server.
  10. After the server has been successfully activated, click Finish on the Activation Complete page to close the Activation Wizard.

 

Step 5 – Configure OCS 2007 R2 Edge

Having successfully installed and activated the Edge server role, we are now ready to configure the server. 

A.  To configure OCS 2007 R2 Edge

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  5. On the Deploy Other Server Roles page, click Deploy Edge Server.
  6. On the Deploy Edge Server page, at Step 3: Configure Edge Server, click Run.

    EdgeConfig1

  7. On the Welcome page, click Next.
  8. On the Import Settings screen, click Next.
  9. On the Internal Interface configuration screen, select 192.168.1.5 (the IP address assigned to the Hyper-V Internal network interface) from the drop-down list and enter Edge-R2.contoso.com as the FQDN value.  Click Next.

    EdgeConfig2 

  10. On the External Interface configuration screen, configure each of the interfaces as follows, then click Next:

    Access Edge Server

    IP Address: 192.168.1.2
    FQDN: sip.contoso.com
    Federation Port: 5061
    Remote User Port: 5061

    Web Conferencing Edge Server

    IP Address: 192.168.1.3
    FQDN: sip.contoso.com
    Port (Other): 441

    A/V Edge Server

    IP Address: 192.168.1.4
    FQDN: sip.contoso.com
    Port (Other): 442

    EdgeConfig3

  11. On the Enable Edge Features screen, enable all of the following features:
    ü Allow remote user access to your network
    ü Allow anonymous users to join meetings
    ü Enable Federation
    ü Allow discovery of federation partners
    ü Federation with public IM providers
    ü MSN / AOL / Yahoo

    EdgeConfig4

  12. On the FQDN of Internal Next Hop Server screen, enter the FQDN of the OCS-R2 Front End server, OCS-R2.contoso.com.  Click Next.

     EdgeConfig5

  13. On the Authorized Internal SIP Domains screen, enter contoso.com.  Click Add, then click Next.

    EdgeConfig6

  14. On the Authorized Internal Servers screen, enter each of the following FQDN values.  Click Add, then click Next:

    Mediation-R2.contoso.com
    OCS-R2.contoso.com
    sip.contoso.com

    EdgeConfig7

  15. Review the information on the Configure Your Edge Server screen.  If all information is correct, click Next to configure the server.
  16. After the server has been successfully configured, click Finish to close the Configuration Wizard.

 

Step 6 – Copy UC Certificate and Internal CA Certificates to OCS 2007 R2 Edge server

Having successfully installed and activated the Edge server role, we are now ready to configure the server.  We’ll first need to copy our UC Certificate purchased from a publicly trusted Certification Authority and the certificate from our internal Certification Authority to the new OCS 2007 R2 Edge server.   

A.  To copy certificates to the OCS 2007 R2 Edge server

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Launch Windows Explorer, and navigate to the Certificates folder using the administrative share for the C:\ hard disk on the Exchange server (\\192.168.1.10\C$\Certificates).
  3. When prompted for authentication, enter the credentials of the built-in Domain Administrator account (Contoso\Administrator).
  4. Within the Certificates folder, select the file sip_contoso_com_exported.pfx and the file ContosoCA.cer.  After highlighting each file, choose Edit then Copy from the Windows Explorer menu bar at the top of the window, or simply press CTRL+C to copy the two certificates to the Windows clipboard.
  5. Again within Windows Explorer, navigate to the C:\ folder from the virtual hard disk on the OCS 2007 R2 Edge server.
  6. Choose Edit then Paste from the Windows Explorer menu bar at the top of the window, or simply press CTRL+V to paste the two certificates from the Windows clipboard into the root of drive C:\ on the Edge server.
  7. Verify that the two certificates were successfully copied to the OCS 2007 R2 Edge server, then close Windows Explorer.

 

Step 7 – Configure OCS 2007 R2 Edge Certificates

Having successfully installed and activated the Edge server role, we are now ready to configure the server. 

A.  To configure OCS 2007 R2 Edge Certificate (Private/Internal Interface)

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  5. On the Deploy Other Server Roles page, click Deploy Edge Server.
  6. On the Deploy Edge Server page, at Step 4: Configure Certificates for Edge Server, click Run.
    EdgeCert1 
  7. On the Welcome page, click Next.
     CreateEdgeCert1
  8. At the Available Certificate Tasks page, choose Create a New Certificate, then click Next.
     CreateEdgeCert2
  9. At the Select a Component page, choose Edge Server Private Interface, then click Next.
  10. At the Delayed or Immediate Request page, choose Send the request immediately to an online Certification Authority, then click Next.
    CreateEdgeCert3 
  11. At the Name and Security Settings page, enter a logical friendly name for the certificate (i.e. EdgeR2Internal), select a bit length of 1024, and select the Mark cert as exportable option.  Click Next.
    CreateEdgeCert4 
  12. At the Organization Information page, enter the name of your organization and organizational unit, then click Next.
    CreateEdgeCert5 
  13. At the Your Server’s Subject Name page, enter the FQDN of the Edge server (i.e. Edge-R2.contoso.com) as the Subject Name of the certificate, then click Next.  Do not add any Subject Alternative Name (SAN) values in your certificate request.
    CreateEdgeCert6 
  14. At the Geographical Information page, select your Country, select your State, and enter your City.  Click Next.
  15. At the Choose a Certification Authority page, select Specify the certificate authority that will be used to request this certificate.  Enter the name of your certificate authority (i.e. email.contoso.com\ContosoCA), click Next, then enter the credentials of the Domain Administrator account when prompted.
    CreateEdgeCert7 
  16. At the Request Summary page, verify that all information is correct, then click Next to submit the request.
  17. If the certificate request was successfully completed, you will be prompted to assign the certificate.  At the Assign Certificate Tasks page, choose Assign certificate immediately, then click Next twice.
  18. Upon successfully assigning the certificate, click Finish.

B.  To configure OCS 2007 R2 Edge Certificate (A/V Authentication Certificate)

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  5. On the Deploy Other Server Roles page, click Deploy Edge Server.
  6. On the Deploy Edge Server page, at Step 4: Configure Certificates for Edge Server, click Run Again.
    CreateEdgeCert9  
  7. On the Welcome page, click Next.
  8. At the Available Certificate Tasks page, choose Assign an existing certificate, then click Next.
    CreateEdgeCert10
  9. At the Available Certificates page, choose the EdgeR2Internal certificate that was created and assigned to the Edge Private Interface.  Click Next.
    CreateEdgeCert11
  10. At the Available Certificate Assignments page, choose the A/V Authentication Certificate option, then click Next twice.
    CreateEdgeCert12
  11. Upon successfully assigning the certificate, click Finish.

C.  To configure OCS 2007 R2 Edge Certificate (Access Edge/Web Conferencing Edge Public Interface)

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  5. On the Deploy Other Server Roles page, click Deploy Edge Server.
  6. On the Deploy Edge Server page, at Step 4: Configure Certificates for Edge Server, click Run Again.
  7. On the Welcome page, click Next.
  8. At the Available Certificate Tasks page, choose Import a certificate from a .pfx file, then click Next. 
    CreateEdgeCert13
  9. At the Import Certificate page, click Browse and navigate to C:\.  Select the file sip_contoso_com_exported.pfx, then click Open.  Verify that the option Mark cert as exportable is enabled, then click Next
    CreateEdgeCert14
  10. At the Import Certificate Password page, enter the Password for the certificate.  This will be the same password that was used to originally export the certificate from the certificate store on the Exchange server.  Click Next.
  11. At the Assign Certificate Task page, choose Assign certificate immediately, then click Next.
  12. At the Available Certificate Assignments page, select both the Access Edge Server Public Interface and the Web Conferencing Edge Server Public Interface, then choose Next twice.
     CreateEdgeCert16
  13. Upon successfully assigning the certificate, click Finish.

Having completed the certificate assignments for each of the network interfaces, you may find that you are unable to federate with other OCS environments or with PIC providers.   There are a number of known trust issues with certificates which may be a contributing factor to federation and/or PIC failures.  A few of the more common issues are listed below:

 

Step 8 – Start OCS 2007 R2 Edge Services

Having successfully installed, activated, and configured the Edge server role, we are now ready to start services. 

A.  To start OCS 2007 R2 Edge services

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  5. On the Deploy Other Server Roles page, click Deploy Edge Server.
  6. On the Deploy Edge Server page, at Step 5: Start Services, click Run.
    Edge11
  7. On the Welcome page, click Next.
  8. At the Start OCS 2007 R2 Services page listing all of the Edge services to be started, click Next.  
    Edge12 
  9. After services have been successfully started, click Finish.

 

Step 9 – Install OCS 2007 R2 Administration Console

The next step of the Edge server installation involves installing the OCS Administration Console.

A.  Install the administration console

  1. Log on to the OCS 2007 R2 Edge virtual machine as the built-in Administrator account (Edge-R2\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. At the main deployment page, select Administrative Tools from the menu on the right.
  5. On the License Agreement page, click I accept the terms in the license agreement and then click Next.
  6. When the installation finishes, close the OCS 2007 R2 Deployment Tools.
  7. Click Start, then Programs, then Administrative Tools.  There you will find the Office Communications Server 2007 R2 administration console as well as the Microsoft Office Communications Server 2007 R2, Communicator Web Access CWA management console.

 

Step 10 – Configure additional Edge settings to support External Connectivity

With the Edge server role successfully deployed, we need to configure additional settings to support external connectivity at both the Forest and Pool levels.  These settings will be configured using the OCS 2007 R2 Front End server.

A.  To configure Edge settings in Global Properties

  1. Log on to the OCS 2007 R2 Front End virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then Programs, then Administrative Tools, then choose Office Communications Server 2007 R2.
  3. Within the OCS 2007 management console, right click on the Forest – Contoso.com node, then select Properties, then choose Global Properties.
  4. Within Global Properties, click on the Edge Servers tab.

    a. Under Access Edge and Web Conferencing Edge Servers, click Add.
    b. Enter the FQDN of your Edge server, Edge-R2.contoso.com, then click OK.
    Edge_Global_Properties1

    c. Under A/V Edge Servers, click Add.
    d. Enter the FQDN of your Edge server, Edge-R2.contoso.com, and port 5062 (used for A/V Authentication).  Click OK.
    Edge_Global_Properties2
    e. Verify that your Edge Server tab settings are configured as follows:
    Edge_Global_Properties

  5. Again within Global Properties, click on the Federation tab.

    a. Select the option to Enable Federation and Public IM Connectivity.
    b. Enter the FQDN of your Edge server, Edge-R2.contoso.com.
    c. Enter port 5061, the port used for communications between the Edge and the OCS Front End servers.
    Edge_Global_Properties3

  6. Again within Global Properties, click on the Meetings tab.

    a. Under Anonymous Participants choose the option Allow users to invite anonymous participants
    b. Under Global Policy settings choose Default Policy.  Select Default Policy under Policy Definitions, then click Edit.
    Edge_Global_Properties4
    c. Configure the Default Policy settings as follows, then click OK:

    ü Enable Web Conferencing
    ü Use native format for PowerPoint files
    ü Enable program and desktop sharing
    ü Allow control of shared programs and desktop
    ü Allow presenter to record meetings
    ü Presenter can allow attendees to record meetings
    ü Enable IP Audio
    ü Enable IP Video
    ü Enable PSTN conference dial-in
    ü PSTN conference dial-in requires passcode

    Edge_Global_Properties5 

  7. Click OK twice to complete the configuration of Global Properties.

B.  To configure Edge settings in Pool Properties

  1. Log on to the OCS 2007 R2 Front End virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then Programs, then Administrative Tools, then choose Office Communications Server 2007 R2.
  3. Within the OCS 2007 management console, expand the Forest – Contoso.com node, then expand Standard Edition Servers. 
  4. Right click on the OCS-R2 pool object, expand Properties, then choose Pool Properties.
  5. Under the Media tab, configure the following settings:

    Encryption Level:  Require Encryption
    A/V Authentication Service:  Edge-R2.contoso.com:5062
    Media Port Range: 49152 to 65535

    Edge_Pool_Properties

  6. Click OK to complete the configuration of Pool settings.

 

Step 11 – Restart services on the OCS 2007 R2 Front End server

 

Our final step of configuring OCS 2007 R2 Edge services involves restarting the services on the OCS 2007 R2 Front End server. 

A.  To restart services on the Front End server

  1. Log on to the OCS 2007 R2 Front End virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then Programs, then Administrative Tools.  Click Office Communications Server 2007 R2 to launch the OCS 2007 R2 administration console.
  3. Within the administration console, expand the contoso.com Forest level entry, then expand Standard Edition Servers.
  4. Expand the OCS-R2 Pool object, then right click on the OCS-R2.contoso.com Front End server object.
  5. Expand Stop, then select Stop all started services.
  6. Monitor the status of the stopping of services displayed at the bottom left corner of the Administration Console window.
  7. When all services have stopped successfully, again, right click on the OCS-R2.contoso.com Front End server object.
  8. Expand Start, then select Start all stopped services.
  9. Again monitor the status of the startup of services of the Front End server.

 

This completes the configuration of the OCS 2007 R2 Edge role.

 

 

Configuring OCS 2007 R2 Mediation

Next we will install the OCS 2007 R2 Mediation role, which provides signaling and media translation between the VoIP infrastructure and a basic media gateway.  Although a typical deployment of the Mediation role involves using two network cards for enhanced security, we will use a single NIC configuration for the Mediation server in our lab. 

 

Step 1 – Connect to the Virtual Machine that will host the OCS 2007 R2 Mediation role

To configure one of the virtual machines to host the OCS 2007 R2 Mediation server role, we’ll need to connect to the Windows 2008 host computer and launch the Server Manager console.  Expand the Hyper-V role and verify that the virtual machine for Mediation was created with the following specifications: 


Role OCS 2007 R2 Mediation
Memory 512MB
Network One (1) Virtual NIC
Hard Disk 16GB Virtual Hard Disk
OS Version Windows Server 2003 SP2 (x64)
FQDN Mediation-R2.contoso.com (domain-joined)
IP Address 192.168.1.13

To configure the server, double-click on the Mediation virtual server within the Hyper-V section of the Server Manager console.

 

Step 2 – Configure OCS 2007 R2 Mediation Network Settings

Next, we need to configure the network settings for the Mediation virtual machine.  Again, we will be using a single NIC configuration in our lab.

A.  To configure OCS 2007 R2 Mediation network settings

  1. Log on to the OCS 2007 R2 Mediation Server virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then click Run.  Type ncpl.cpl and press Enter to launch Network Connections.  
  3. Right click on the Local Area Network network interface and select Properties.
  4. Highlight Internet Protocol (TCP/IP) and click on the Properties button.
  5. Under the General tab of TCP/IP Properties, configure the network adapter as follows:

    Choose Use the following IP address.

         IP Address:  192.168.1.13  
         Subnet Mask:  255.255.255.0
         Default Gateway:  192.168.1.1  (our Linksys Router)

    Choose Use the following DNS servers.
     
         Primary DNS Server:  192.168.1.10  (our internal DNS server)
         Alternate DNS Server:  None

    Med_Networking_1

  6. Click OK to commit your changes. 
  7. Close the Network Connections dialog box, and restart the Mediation virtual machine.

 

Step 3 – Install OCS 2007 R2 Mediation

After configuring the virtual machine, we are now ready to install the OCS Mediation server binaries.

A.  To install OCS 2007 R2 Mediation

  1. Log on to the OCS 2007 R2 Mediation virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click SetupSE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. When prompted to install the Microsoft Visual C++ 2008 Redistributable, choose Yes to install it.
  5. When prompted to install Microsoft .NET Framework 3.5 SP1, choose Yes to install it.
  6. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  7. On the Deploy Other Server Roles page, click Deploy Mediation Server.

    Mediation1

  8. On the Deploy Mediation Server page, at Step 1: Install Files for Mediation Server, click Install.
  9. On the License Agreement page, click I accept the terms in the license agreement, and then click Next. If you do not accept the license terms, Setup cannot continue.
  10. On the Install location for Microsoft Office Communications Server 2007 R2, Mediation Server page, in the Location box, type a path where Mediation server should be installed, or accept the default location. Click Next.
  11. After the Mediation server has been installed successfully, click Close to return to the Mediation deployment wizard.

 

Step 4 – Activate OCS 2007 R2 Mediation

Having successfully installed the Mediation server binaries, we are now ready to activate the server.

A.  To activate OCS 2007 R2 Mediation

  1. Log on to the OCS 2007 R2 Mediation virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  5. On the Deploy Other Server Roles page, click Deploy Mediation Server.
  6. On the Deploy Mediation Server page, at Step 2: Activate Mediation Server, click Run.
  7. On the Welcome page, click Next.
  8. On the Select domain service account page, select Use an existing account.  Enter the name RTCComponentService in the Account name box, then type the account password in the Password box.  This account is already a member of the RTCComponentUniversalServices group, which is required for the Mediation service to start.  Click Next.
  9. After the server has been activated, click Close on the Activation Complete page to close the Activation Wizard.

 

Step 5 – Install OCS 2007 R2 Administration Console

The next step of the installation of the Mediation server involves installing the OCS Administration Console.

A.  Install the administration console

  1. Log on to the OCS 2007 R2 Mediation virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. At the main deployment page, select Administrative Tools from the menu on the right.
  5. On the License Agreement page, click I accept the terms in the license agreement and then click Next.
  6. When the installation finishes, close the OCS 2007 R2 Deployment Tools.
  7. Click Start, then Programs, then Administrative Tools.  There you will find the Office Communications Server 2007 R2 administration console as well as the Microsoft Office Communications Server 2007 R2, Communicator Web Access CWA management console.

 

Step 6 – Configure OCS 2007 R2 Mediation

Having successfully installed and activated the Mediation server role, we are now ready to configure the server. 

A.  To configure OCS 2007 R2 Mediation

  1. Log on to the OCS 2007 R2 Mediation virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then Programs, then Administrative Tools, then choose Office Communications Server 2007 R2.
  3. Within the OCS 2007 management console, expand Forest – Contoso.com, then expand Mediation Servers.
  4. Open the Properties of your Mediation server, Mediation-R2.contoso.com.
  5. Under the General tab, enter the following information:

    Communications Server listening IP address:  192.168.1.13
    Gateway listening IP address:  192.168.1.13
    A/V Edge Server:  Edge-R2.contoso.com:5062
    Default Location Profile:  None

    Mediation2

  6. Under the Next Hop Connections tab, enter the following information:

    Office Communications Server Next Hop FQDN:  OCS-R2.contoso.com
    Port:  5061
    PSTN Gateway Next Hop IP Address:  192.168.1.14
    Port:  5060

    Mediation3

  7. When you have completed configuring options for both the General and Next Hop Connections tabs, click Apply and OK to commit your changes. 

Note:  Since we have not yet created a location profile, we are unable to select a location profile in the configuration of the Mediation server.  This will cause the following warning to appear.  Just click OK

Mediation5

Note:  You will also receive a warning to restart Mediation services.  You can safely ignore this warning.

Mediation6 


Step 7 – Request Certificate for OCS 2007 R2 Mediation

 

After configuring the Mediation server role, we will need to request a certificate from our Certificate Authority.

 

A.  To request a certificate for OCS 2007 R2 Mediation

  1. Log on to the OCS 2007 R2 Mediation virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Launch Windows Explorer, and navigate to the \Install\setup\amd64\ folder.
  3. Double-click DeploySE.exe, the setup program for the Standard Edition version of OCS 2007 R2. 
  4. On the Office Communications Server 2007 R2 Deployment Wizard page, click Deploy Other Server Roles.
  5. On the Deploy Other Server Roles page, click Deploy Mediation Server.
  6. On the Deploy Mediation Server page, at Step 4: Configure Certificate, click Run.
  7. At the Certificate Wizard splash screen, click Next.
  8. At the Available Certificate Tasks screen, choose Create a New Certificate, then click Next.

    MedCert2  

  9. At the Delayed or Immediate Request screen, choose the option Send the request immediately to an online certificate authority, then click Next. 

    MedCert3

  10. At the Name and Security Settings screen, enter the following information, then click Next:

    Name:  OCSR2MediationCert
    Bit Length:  1024
    Mark cert as exportable:  Enabled

    MedCert4

  11. At the Organization Information screen, enter contoso.com for both the Organization name and the Organizational Unit.  Click Next.
  12. At the Server’s Subject Name screen, enter Mediation-R2.contoso.com for the Subject Name value.  Do not enter any Subject Alternative Names for this certificate.  Click Next.

    MedCert6

  13. At the Geographical Information screen, enter your Country, State/Province, and City/Locality, then click Next.
  14. At the Choose a Certification Authority screen, select Email.contoso.com\ContosoCA from the drop-down list of Certificate Authorities, then click Next.

    ConfigFECert4  

  15. At the Request Summary screen, verify that all of the information was entered correctly, then click Next.
  16. Upon successfully submitting the certificate request, a new certificate should be issued by the Certificate Authority from your environment.  Choose the Assign option to assign the certificate immediately, then click Finish. 

    MedCert7

  17. You will be prompted to restart services, however you can ignore this warning. 

 

This completes the deployment of the OCS 2007 R2 Mediation Server role.  

 

 

Configuring Enterprise Voice

Next we will configure Enterprise Voice functionality for Office Communications Server.  There are several steps  that must be completed to configure Enterprise Voice, especially when Unified Messaging is involved.  As you will see, this is one of the more challenging tasks in deploying OCS 2007 R2.

 

Step 1 – Get the Phone Context value of the Unified Messaging Dial Plan

 

To successfully integrate OCS 2007 and Unified Messaging, the name of the Location Profile for your Enterprise Voice users must match the Phone Context value of your Unified Messaging Dial Plan.  To get this value, we will use the Exchange Management Shell on the Windows 2008 physical host computer.

A.  Get Phone Context value of UM Dial Plan

  1. Log on to the Windows 2008 physical computer as the built-in Domain Administrator account (Contoso\Administrator).
  2. Launch the Exchange Management Shell by clicking Start > Programs > Microsoft Exchange Server 2007 > Exchange Management Shell.
  3. Within the Exchange Management Shell, enter the following command to get details of all Exchange UM Dial Plans:

    get-UMDialPlan | fl name,uritype,voipsecurity,phonecontext,umservers

    [PS] C:\> get-umdialplan | fl name,uritype,voipsecurity,phonecontext,umservers

    Name : OCSDialPlan
    URIType : SipName
    VoIPSecurity : SIPSecured
    PhoneContext : OCSDialPlan.contoso.com
    UMServers : {EMAIL}

  4. Note that the PhoneContext value of the OCSDialPlan is ‘OCSDialPlan.contoso.com’. The name of the Location Profile you will create must match this value.

 

Step 2 – Install the OCS 2007 R2 Resource Kit Tools on the Mediation Server

 

To create and configure the OCS Location Profile, we will use Enterprise Voice Route Helper, which is installed with the OCS 2007 R2 Resource Kit tools.  We will need to install the resource kit tools on the Mediation server.

A.  To install the OCS 2007 R2 Resource Kit tools

  1. Log on to the OCS 2007 R2 Mediation virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Launch Internet Explorer, and navigate to http://www.microsoft.com/downloads/details.aspx?FamilyID=9e79a236-c0df-4a72-aba6-9a9602a93ed0&DisplayLang=en.
  3. Download and save the OCSResKit.msi installation file to disk.
  4. Double-click on the file OCSResKit.msi to launch the installation of the Resource Kit tools for Office Communications Server 2007 R2.
  5. At the installation splash screen, Click Next, then accept the License Agreement.
  6. When prompted for the installation path, just accept the default value and click Next.

     reskit

  7. When the installation of the OCS Resource Kit tools finishes, click Close.

 

Step 3 – Create a Location Profile using Enterprise Voice Route Helper

 

Next we will use the Enterprise Voice Route Helper tool to create a Location Profile for our Enterprise Voice enabled users.

A.  To create a Location Profile

  1. Log on to the OCS 2007 R2 Mediation virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Launch Enterprise Voice Route Helper by clicking Start > Programs > Microsoft Office Communications Server 2007 > Resource Kit > Enterprise Voice Route Helper.

    RH1

  3. From the Menu bar in Enterprise Voice Route Helper, click Insert > New Location Profile.

    RH2 

  4. Enter the name ‘OCSDialPlan.contoso.com’ for the name of the new Location Profile. This is the same value found in the PhoneContext field of the UM Dial Plan from Step 1. Click OK.

    RH3 

  5. Within the Location Profile Editor, enter Default Location Profile for the Description value of the location profile, then click Add to enter phone number Normalization Rules for the new Location Profile.

    RH4

  6. You will likely need to create several Normalization Rules both to correctly handle user dialing behavior within Office Communicator and to correctly format dial strings from telephone numbers stored in Active Directory and in Microsoft Outlook.  For the purposes of this lab, we will only create three very simple normalization rules:

    NormRule1

    Rule Name:  4 Digit Internal Dialing
    Internal Enterprise Extension:  Enabled
    Use Translation When Dialing from Device:  Enabled
    Starting Digits:  (empty)
    Length:  Exactly 4 Digits
    Number of Digits to Strip:  0
    Digits to Prepend:  +1980776
    Automatically Update Description:  Enabled

    Rule Name: 10 Digit Dialing
    Internal Enterprise Extension:  Disabled
    Use Translation When Dialing from Device:  Enabled
    Starting Digits:  (empty)
    Length:  Exactly 10 Digits
    Number of Digits to Strip:  0
    Digits to Prepend:  +1
    Automatically Update Description:  Enabled

    Rule Name:  11 Digit Dialing
    Internal Enterprise Extension:  Disabled
    Use Translation When Dialing from Device:  Enabled
    Starting Digits:  (empty)
    Length:  Exactly 11 Digits
    Number of Digits to Strip:  0
    Digits to Prepend:  +
    Automatically Update Description:  Enabled

  7. When all three normalization rules have been added, click Apply and then OK.
  8. Next, choose Edit > Edit Phone Usage from the Menu Bar.
  9. Save/Upload your work by clicking File > Upload Changes from the Menu Bar.
  10. After the changes have been uploaded successfully, click OK on the Change Report screen. 
  11. From the Phone Usage dialog box, click Add to add a new Route.
  12. From within the Route Picker dialog box, click New.
  13. With the Route Details box, configure the new route as follows:

        a. Enter PSTN Route as the Route Name value.
        b. Under the Target Phone Numbers\Prefixes tab, choose Match all numbers except as noted.
           RH6
        c. Under the Gateways tab, click Add then select Mediation-R2.contoso.com from the list of available gateways.
           RH7
       d. To complete the configuration of Route Details, click OK twice.

  14. Save/Upload your work by clicking File > Upload Changes from the Menu Bar. 

    RH8 

  15. After the changes have been uploaded successfully, click OK on the Change Report screen.
  16. Close the Enterprise Voice Route Helper application.  

 

Step 4 – Associate the OCS Environment with the Location Profile

 

After having created our new Location Profile, we now need to associate it to our OCS environment.

A.  To associate the Location Profile

  1. Log on to the OCS 2007 R2 Mediation virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then Programs, then Administrative Tools.  Click Office Communications Server 2007 R2 to launch the OCS 2007 R2 administration console.
  3. Within the administration console, expand the contoso.com Forest level entry, then expand Mediation Servers
  4. Right click on the Mediation-R2.contoso.com server object, then select Properties. 
  5. In the Default Location Profile drop down box, choose the newly created OCSDialPlan.contoso.com Location Profile.
    Mediation7
  6. Click OK to commit your changes

 

Step 5 – Start services on the OCS 2007 R2 Mediation server 

 

Now that we have configured Enterprise Voice, we need to restart services on the Mediation server.

A.  To start services on the Mediation server

  1. Log on to the OCS 2007 R2 Mediation virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then Programs, then Administrative Tools.  Click Office Communications Server 2007 R2 to launch the OCS 2007 R2 administration console.
  3. Within the administration console, expand the contoso.com Forest level entry, then expand Mediation Servers
  4. Right click on the Mediation-R2.contoso.com server object, then click Start.
  5. Monitor the status of the startup of services displayed at the bottom left corner of the Administration Console window.

 

Step 6 – Restart services on the OCS 2007 R2 Front End server

 

Our final step of configuring Enterprise Voice involves restarting the services on the OCS 2007 R2 Front End server.  This is done to ensure that our end users receive details regarding the default location profile and normalization rules though in-band provisioning during the client logon process.

A.  To restart services on the Front End server

  1. Log on to the OCS 2007 R2 Front End virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then Programs, then Administrative Tools.  Click Office Communications Server 2007 R2 to launch the OCS 2007 R2 administration console.
  3. Within the administration console, expand the contoso.com Forest level entry, then expand Standard Edition Servers.
  4. Expand the OCS-R2 Pool object, then right click on the OCS-R2.contoso.com Front End server object.
  5. Expand Stop, then select Stop all started services.
  6. Monitor the status of the stopping of services displayed at the bottom left corner of the Administration Console window.
  7. When all services have stopped successfully, again, right click on the OCS-R2.contoso.com Front End server object.
  8. Expand Start, then select Start all stopped services.
  9. Again monitor the status of the startup of services of the Front End server.

 

This completes the configuration of OCS 2007 R2 Enterprise Voice.

 

 

Configuring a VoIP Gateway or SIP Trunk

 

To provide external telephony connectivity for users in your lab, you will need to either purchase a VoIP gateway or a SIP trunk from a UCOIP certified provider. Currently, there are currently three vendors that offer VoIP gateways and four vendors that offer SIP trunks which have been certified for use with OCS 2007 R2. Given the enormity of scope with regards to configuring PSTN connectivity for Office Communications Server 2007 R2, this topic will not be covered in this documentation.

For more information, please check the Microsoft Unified Communications Open Interoperability Program website at http://technet.microsoft.com/en-us/office/ocs/bb735838.aspx#trunking.

While Dialogic, Quintum, and Audiocodes offer VoIP gateways for use with OCS 2007 R2, I purchased the Audiocodes MP-114 Media Gateway for my lab environment. In February 2009, I published a blog entry on Microsoft TechNet which provides configuration details for configuring PSTN connectivity for OCS environments using an Audiocodes MP-114 or MP-118 Media Gateway. If you have an Audiocodes media gateway, you may find this information useful if you plan to configure PSTN connectivity for your own lab.

Integrating AudioCodes MP-114/MP-118 Media Gateways with Microsoft Unified Communications Products

http://blogs.technet.com/daveh/archive/2009/02/01/integrating-audiocodes-mp-114-mp-118-media-gateways-with-microsoft-unified-communications-products.aspx

 

 

Configuring Users

Our next task will be to create and configure users for our lab environment.  Each user will be enabled for email, voice mail, and OCS with Enterprise Voice.  If you’re like me and find it difficult to come up with names for users in your lab, check out a random name generator like the one at http://www.behindthename.com/random

 

Step 1 – Create a Mailbox-Enabled User using Exchange Management Console (EMC)

Our first step will be to connect to our Exchange server (the Windows 2008 physical host computer) and create a mailbox-enabled user for our lab.  To do this, we will use the Exchange Management Console.

A.  To create a Mailbox-Enabled user account

  1. Log on to the Windows 2008 physical host computer (Exchange 2007 server) as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then All Programs, then Microsoft Exchange Server 2007, then choose Exchange Management Console.
  3. Within the Exchange Management Console, expand the Recipient Configuration object in the Navigation pane on the left, then select New Mailbox from the Action pane on the right. 
    CreateUser1
  4. Within the Introduction page, select the User Mailbox option, then click Next.
    CreateUser2
  5. At the User Type page, choose New User, then click Next. 
    CreateUser3
  6. At the User Information page, enter a First Name, Last Name, and Display Name value for your user account.  Additionally, configure a User Principal Name (user@domain.com), a pre-Windows 2000 Login Name (domain\user), and a Password value for your account.  Click Next. 
    CreateUser4
  7. At the Mailbox Settings page, enter a mailbox Alias for your user, then click Browse to select a Mailbox Database.  Choose the Mailbox Database from your Exchange 2007 server, then click OK.  Click Next. 
    CreateUser5
  8. At the Configuration Summary page, click New to create the mailbox-enabled user account. 
    CreateUser6
  9. Next, right click on the new user account and choose Properties from the context menu. 
    CreateUser7
  10. Within the Properties of the user account, click on the Address and Phone tab.
  11. Enter a Business phone number for the user account (i.e. 60001).  The number of digit in this extension should equal the number of digits specified in your Unified Messaging Dial Plan (i.e. 5 digits).  Click OK. 
    CreateUser8

 

Step 2 – Enable the user for Office Communications Server

Our next step will be to enable the user for Office Communications Server.  This will add the user to the OCS database and allow the user to connect to the OCS Front End server using Microsoft Office Communicator.   

A.  To enable a user for Office Communications Server

  1. Log on to the OCS 2007 R2 Front End virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, and then click Run. In the Open box, type dsa.msc, and then click OK.
  3. In the console pane of Active Directory Users and Computers, expand the Users container or other organization unit where your user accounts reside.
  4. Right-click the mailbox-enabled user that you create in Step 1 above (i.e., Spongebob Squarepants), and then click Enable users for Communications Server. 
    enableocs1
  5. On the Welcome to the Enable Office Communications Server Users Wizard page, click Next.
  6. On the Select Server or Pool page, select the Standard Edition server OCS-R2.contoso.com from the list, and then click Next. 
    enableocs2
  7. On the Specify Sign-in Name page, select Use user’s e-mail address to generate the SIP URI for the user account, then click Next. 
    enableocs3
  8. At the Ready to Enable Users page, click Next.
  9. Verify that the user was enabled successfully, and then click Finish. 
    enableocs4  

 

Step 3 – Configure OCS settings for enabled users

After enabling our account for Office Communications Server, our next step will be to configure the account for external connectivity and Enterprise Voice. 

A.  To configure a user for Office Communications Server

  1. Log on to the OCS 2007 R2 Front End virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, and then click Run. In the Open box, type dsa.msc, and then click OK.
  3. In the console pane of Active Directory Users and Computers, expand the Users container or other organization unit where your user accounts reside.
  4. Right-click on the user account that you created in Step 1 above, then select Configure Communications Server Users. 
    configureOCS1
  5. At the Welcome to the Configure Users Wizard splash screen, click Next.
  6. At the Configure User Settings page, Enable the Federation, Public IM Connectivity, Remote User Access, and Enhanced Presence options for all selected users. Click Next. 
     configureOCS1.5
  7. At the Configure User Settings anonymous meeting participation page, click Next. (This option will be grayed out)
  8. At the Configure User Settings meeting policy page, click Next. (This option will be grayed out.)
  9. At the Configure Enterprise Voice Settings page, enable the option for Change Enterprise Voice Settings and select the option for Enable Enterprise Voice. Click Next. 
     configureOCS2
  10. At the Configure Enterprise Voice Settings and Location Profile page, enable the option Change location profile for selected users, then choose the OCSDialPlan.contoso.com location profile from the list of available location profiles.  Click Next. 
    configureOCS3 
  11. At the Ready to Configure Users page, click Next.
  12. At the Configure Operation Status page, verify that your user was successfully configured for Office Communications Server.

 

Step 4 – Configure Enterprise Voice details for users

Our next step will be to configure the Line URI value for our user account.  This value allows us to define a E.164   telephone number for our user.

A.  To configure a Line URI value for a user

  1. Log on to the OCS 2007 R2 Front End virtual machine as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, and then click Run. In the Open box, type dsa.msc, and then click OK.
  3. In the console pane of Active Directory Users and Computers, expand the Users container or other organization unit where your user accounts reside.
  4. Right-click on the user account that you created in Step 1 above, then select Properties.
  5. Click on the Communications tab, and verify that the user is enabled for OCS. 
    LineURI1
  6. Under Telephony settings, click Configure.
  7. Under Telephony Options, verify that Enterprise Voice is enabled.  Enter the Line URI value tel:+19807760001 and select the OCSDialPlan.contoso.com Location Profile.  Click OK. 
     LineURI2
  8. Click OK to close user properties.

 

Step 5 – Enable the User for Unified Messaging using Exchange Management Console (EMC)

Our next step will be to enable the account for Unified Messaging.  This will allow unanswered or busy calls to this user to be diverted to voice mail.  Again, we will use the Exchange Management Console for this task.

A.  To enable the user account for Unified Messaging

  1. Log on to the Windows 2008 physical host computer (Exchange 2007 server) as the built-in Domain Administrator account (Contoso\Administrator).
  2. Click Start, then All Programs, then Microsoft Exchange Server 2007, then choose Exchange Management Console.
  3. Within the Exchange Management Console, expand the Recipient Configuration object in the Navigation pane on the left, highlight the mailbox in the Results pane in the center, then select Enable Unified Messaging from the Action pane on the right.
    EnableUM
  4. At the Introduction page, you will find options to configure the UM Mailbox Policy and UM PIN Settings.  To select a UM Mailbox Policy, click Browse and choose the OCSDialPlan Default Policy.  Click OK.  Then select the option Manually specify PIN, and to the right enter the desired PIN for this user.  Click Next. 
     EnableUM1
  5. At the Extension Configuration page, select the option Manually entered mailbox extension and enter the Business extension (i.e. 60001) from Step 1 above.  Again, the number of digits in the extension should match that of your UM Dial Plan.  Also select the option Manually entered SIP or E.164 address, and enter the email address of the user.  Click Next. 
    EnableUM2
  6. At the Configuration Summary page, click Enable to enable the account for Unified Messaging. 
    EnableUM3  

 

Step 6 – Generate Grammar Files for UM Dial Plan and Global Address List

After enabling our accounts for Unified Messaging, we need to be sure to include them in the grammar files used by Unified Messaging.  Although these files are created and/or updated by the server around 1:30am each day, the Directory Search feature of our Auto Attendant will not find our new UM enabled users until these files are generated.  

A.  To generate the grammar file for Unified Messaging

  1. Log on to the Windows 2008 physical host computer (Exchange 2007 server) as the built-in Domain Administrator account (Contoso\Administrator).
  2. From the Exchange server, open a command prompt.
  3. Create a new folder to hold the log files created by the galgrammargenerator utility using the following command: 

    md C:\temp 

    ggg_1

  4. Navigate to the folder where the galgrammargenerator utility resides by entering the following command:

    cd C:\Program Files\Microsoft\Exchange Server\Bin 

    ggg_2

  5. Next, run the following command to generate the grammar files for our Dial Plan:

    galgrammargenerator.exe –s {servername} –o c:\temp\DialPlan_GrammarGeneration.log 

    ggg_3

  6. Next, run the following command to generate the grammar files for our Global Address List:

    galgrammargenerator.exe -g -o c:\temp\GAL_GrammarGeneration.log 

    ggg_4

  7. Examine each of the log files in the C:\temp folder to verify that the UM Enabled user was included in the compiled grammar files. 

    ggg_5 

 

This completes the configuration of the user account for Exchange Server and Office Communications Server.


Comments (0)

Skip to main content