OCS Configuration

The configuration steps required to set up the Presence Proxy for the Speech Auto Attendant (SAA) with OCS 2007 are as follows:

Note: The Speech Auto Attendant must be installed and configured to use Active Directory as the user data source before the Presence Proxy can be configured. (See step 7 below.)

1. Create the Active Directory/OCS accounts for the NP-UM Presence Proxy

2. Add all NP-UM Presence Proxy accounts to the Allow list of every SAA user

3. Add all NP-UM Presence Proxy accounts as a PromptedSubscriber for every SAA user in the OCS database

4. Trust the NP-UM Server in OCS 2007

5. Verify that the OCS service entry exists in the Corporate DNS server

6. Configure DNS on the NP-UM server so that it can find the OCS service SRV record

7. Install and configure SAA on the NP-UM server

8. Purchase the SAA Presence license for the NP-UM server

9. Verify the installation

1 - Create the Active Directory/OCS accounts for the NP-UM Presence Proxy

For every 145 Speech Auto Attendant users that have their presence state monitored, it is necessary to create one account for use by the Presence Proxy. For example, to monitor 2000 SAA users, you need to create 14 Presence Proxy user accounts in the OCS Server. For the maximum supported 5000 presence users, it is necessary to create 35 Presence Proxy user accounts in OCS.

Create the Active Directory user accounts using the following names and SIP URIs in the same domain as the other OCS users (in particular, the domain used by the SAA users in NP-UM):

To create a user in the "Active Directory Users and Computers" management console on the Domain Controller:

1. Expand the domain holding the OCS users.

2. Right-click on Users, and then select New->Users.

3. Enter 'Mitel' for the First name, 'Presence' for the Last name, and 'mitelpresence99' for the User logon name, where 99 is blank for the first user, ’2’ is entered for the second user, ’3’ is entered for the third user, and so on for the remaining users (see table above).

4. Click Next.

5. Enter a password. For increased security, make the password as long as possible (at least 7 characters) and use a mix of numbers and letters in upper and lowercase.

6. Select the Password never expires check box. Leave all other check boxes empty.

7. Click Next.

8. Review the values entered for accuracy, and then click Finish.

9. The ’mitelpresence’ user will appear in the list of users in the right pane. Add as many ’mitelpresence’ users as is necessary based on the number of SAA users to have presence.

Next, enable the mitelpresence users for OCS by doing the following for every ’mitelpresence’ user in the right pane:

1. Right-click on the ’mitelpresence’ user, and the select Properties.

2. In the Properties window, select the Communications tab.

3. Select the Enable user for Office Communications Server checkbox.

4. In the Sign in Name field, enter 'sip:mitelpresence99' and select @xyz.com from the drop-down list, where xyz.com is replaced with the proper domain and 99 is replaced with the number matching this mitelpresence user (refer to the table above).

5. Select the OCS server from the Server or pool list.

6. Click OK.

7. Repeat the steps above for all other ’mitelpresence’ users.

Notes:

• It will take several minutes for these Active Directory changes to propagate and come into effect.

• Scripting (e.g., VB Script) can be used to automate the creation of accounts.

2 - Add all NP-UM Presence Proxy accounts to the Allow list of every SAA user in OCS

To add the mitelpresence as "Allowed" to each SAA user in OCS 2007, it is necessary to use a script. The user interface for modifying a user's Allow list that existed in LCS 2005 has been removed from OCS 2007 for both the OCS 2007 server and the Office Communicator client.

Sample scripts are included in the Microsoft Office Communications Server 2007 Resource Kit Tools. The Resource Kits are free and available for download from the Microsoft website. The resource kit is installed on the OCS 2007 server, default location C:\Program Files\Microsoft Office Communications Server 2007\ResKit\WMI Samples. The sample script of interest is LCSAddACEs.wsf. Instructions for using the script can be found in the included document OCS_ResourceKitTools_ReadMe.doc in the ResKit directory.

If the Presence Proxy user is missing from a user's Allow list, attempts by the Presence Proxy to subscribe to that user's presence may fail. The SAA user will be prompted by Office Communicator to add the Presence Proxy to their buddy list. Unless the Presence Proxy is in the user’s allow list, it will not be able to receive the user's presence status. If the Presence Proxy is added to their allow list properly, there will be no popup for the user and the Presence Proxy will never appear in their Buddy list in Communicator.

3 - Add all NP-UM Presence Proxy accounts as a PromptedSubscriber for every SAA user in the OCS database

This step is required to prevent every SAA OCS user from seeing popup windows in Office Communicator 2007 notifying them that a mitelpresence user has added them as a contact. The only way to prevent the popups is to modify the OCS database directly. The OCS server does not need to be stopped while performing this modification.

Follow the steps below to modify the OCS database:

1. Log into the OCS Server using an account with Administrative privileges.

2. Create a file named PresProxySub.sql containing the following text:

USE [rtc]

GO

delete dbo.PromptedSubscriber

from dbo.PromptedSubscriber ps

inner join dbo.Resource r

on ps.SubscriberId = r.ResourceId

where r.UserAtHost like 'mitelpresence%'

GO

insert into dbo.PromptedSubscriber

select distinct c.PublisherId,

r.ResourceId,

'True',

1,

'True',

0,

NULL,

NULL

from dbo.Container c,dbo.Resource r

where r.UserAtHost Like 'mitelpresence%'

order by c.PublisherId, r.ResourceId

GO

3. Then run the following command at the command prompt (cmd.exe):

sqlcmd -S (local)\rtc -d rtc -E -i PresProxySub.sql

This command can be run more than once as it first cleans up the PresenceProxy-related records already in the database (it will not create duplicate records).

In fact, this command should be re-run each time new OCS users (who are also SAA users) are added to prevent those new users from seeing the client contact list notification popup window.

4 - Trust the NP-UM Server in OCS 2007

In the OCS Management Console, add the NP-UM server as an Authorized Host:

1. Right-click on the server under Standard Edition Servers.

2. Select Properties -> Front End Properties

3. Select the Host Authorization tab.

4. Click Add....

5. Enter the NP-UM server's IP address or FQDN (select the appropriate radio button)

6. Select the Treat as Authenticated check box.

7. Click OK.

8. Click the next OK button.

5 - Verify that the OCS service entry exists in the Corporate DNS server

Ensure that the corporate DNS server (it may be running on the Windows Domain Controller or other Windows server) has been configured following the recommendations in the OCS Deployment Guide. This means there must be an SRV record for '_sip._tcp.xyz.com' where 'xyz.com' is the domain that OCS is in.

One way to verify the setup is to view the corporate DNS configuration directly. Another way is by using the Microsoft Office Communicator client. If it works using 'Automatic configuration', then DNS is correctly set up, assuming that the DNS servicing the Communicator Client PC is the same DNS in effect for the NP-UM Server that the Presence Proxy is running on.

In a working Office Communicator application:

1. Select Actions->Options.

2. Select the Accounts tab.

3. Click the Advanced button beside the Sign-in name box.

If Automatic configuration is selected, then the Communicator client is using DNS to locate the OCS server in the same way that the NP-UM Presence Proxy does. This means that DNS is already configured for OCS.

If Manual configuration is selected, try changing it to Automatic configuration as described below:

1. Select Automatic configuration.

2. Click OK to save the change.

3. Click OK again to exit the Options window.

4. Log out of Office Communicator (select Connect->Sign Out), and then log in again.

5. Click Sign In.

6. If prompted, log in as the same user.

If the login succeeds, DNS is correctly set up.

6 - Configure DNS on the NP-UM server so that it can find the OCS service SRV record

Ensure that the NP-UM server has its DNS set up so that DNS queries are forwarded to the Windows DNS server, often on the Domain Controller.

Many working DNS configurations are possible. The requirement is that the Presence Proxy running on the NP-UM server is able to use DNS to resolve the '_sip._tcp.xyz.com' service name (where xyz.com is the domain that OCS is in).

To test this, from a command line on the NP-UM system, enter the following command and verify that it returns the information for the OCS server:

dig _sip._tcp.xyz.com SRV +short

where "xyz.com" is replaced with the domain of OCS. The result should look similar to this:

0 0 5060 mylcs.xyz.com

where mylcs.xyz.com is the hostname of the OCS server and 5060 is the port used to connect to OCS. If the result is nothing or a blank line, DNS is incorrectly configured, or DNS on the NP-UM server is not configured correctly to use the corporate DNS server(s).

7 - Install and configure SAA on the NP-UM server

See Speech Auto Attendant Installation and  Configuration for installation instructions.  The Speech Auto Attendant must be set up to use Active Directory as the user repository. See Define an Active Directory Data Source.

8 - Purchase the Presence license for the NP-UM server

The "NuPoint Messenger: Enable Presence (Speech AA)" license must be purchased. Once that license becomes effective for the NP-UM server, no further actions are required. The Presence Proxy is always running when NP-UM is running and it will detect that the license has been purchased and will automatically start up within a minute of enabling the license.

9 - Verify installation

To verify the installation, check that the Speech Auto Attendant can retrieve the presence state of a user. Call the SAA main number and speak the name of an SAA user who is also an OCS-enabled user. SAA should speak the current presence state of the user before forwarding the call. Change the presence state of the SAA user (e.g., from Online to Busy or Be Right Back) and make another call through SAA to that user. The presence state spoken by SAA should be the new state.