# LCS Configuration

The configuration steps required to set up the Presence Proxy for the Speech Auto Attendant (SAA) with LCS 2005 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 6 below.)

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

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

3. Trust the NP-UM Server in LCS 2005

4. Verify that the LCS service entry exists in the Corporate DNS server

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

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

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

8. Verify the installation

## 1 - Create the Active Directory/LCS 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 LCS Server. For the maximum supported 5000 presence users, it is necessary to create 35 Presence Proxy user accounts in LCS.

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

First Name | Last Name | Account | SIP URI
Mitel | Presence | mitelpresence@xyz.com | sip:mitelpresence@xyz.com
Mitel | Presence | mitelpresence2@xyz.com | sip:mitelpresence2@xyz.com
Mitel | Presence | mitelpresence3@xyz.com | sip:mitelpresence3@xyz.com
Mitel | Presence | mitelpresence4@xyz.com | sip:mitelpresence4@xyz.com
Mitel | Presence | mitelpresence5@xyz.com | sip:mitelpresence5@xyz.com
Mitel | Presence | mitelpresence6@xyz.com | sip:mitelpresence6@xyz.com
Mitel | Presence | mitelpresence7@xyz.com | sip:mitelpresence7@xyz.com
Mitel | Presence | mitelpresence8@xyz.com | sip:mitelpresence8@xyz.com
Mitel | Presence | mitelpresence9@xyz.com | sip:mitelpresence9@xyz.com
Mitel | Presence | mitelpresence10@xyz.com | sip:mitelpresence10@xyz.com
etc. | etc. | etc. | etc.

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

1. Expand the domain holding the LCS 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.

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 LCS by doing the following steps for every ’mitelpresence’ user in the right pane:

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

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

3. Select the Enable Live Communications for this user checkbox.

4. In the SIP URI box, enter 'sip:mitelpresence99@xyz.com' 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 LCS 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 LCS

To allow the Presence Proxy to monitor the presence state of SAA users without becoming a member of each user's Contact or Buddy list, it is necessary to add all Presence Proxy user accounts to the Allow list of every SAA user.

In the LCS management console:

1. Right-click on an SAA LCS user, and then select Properties.

2. In the Live Communications tab, click the View/Edit button beside the Allow and block list: label.

3. In the User Allow and Block List window, click Add.

4. In the Type list, select User.

5. In the Mask box, enter the SIP URI of a Presence Proxy's account—for example, 'sip:mitelpresence99@xyz.com' where 'xyz.com' is the LCS domain name and 99 is replaced with the number of the ’mitelpresence’ user.

6. Select Allow subscriptions and invitations.

7. Click OK for each window that appears to save the changes.

8. Repeat the steps above for every ’mitelpresence’ user account.

The Presence Proxy user accounts can also be added to the Allow list of every SAA user through Microsoft Office Communicator when logged in as an SAA user:

1. Select Actions > Options.

2. Select the Permissions tab.

3. Click New.

4. In the Type list, select User.

5. In the Account name box, enter the SIP URI of the Presence Proxy's account—for example, 'sip:mitelpresence99@xyz.com' where 'xyz.com' is the LCS domain name and 99 is replaced with the number of the ’mitelpresence’ user.

6. In the Permission list, select Allow.

7. Click OK.

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 buddy list, it will not be able to receive the user's presence status.

Note: The above procedure is practical for a small number of users. For larger numbers, scripting (for example, VB Script) can be used instead. The Microsoft LCS 2005 Resource Kit provides sample scripts that you can use as a starting point. To obtain the scripts, download the kit from the Microsoft website and install it on the LCS 2005 server.

## 3 - Trust the NP-UM Server in LCS 2005

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

1. Right-click the server under Live Communications servers and pools.

2. Select Properties.

3. Select the Host Authorization tab.

4. Click Add....

5. Enter the IP address of the NP-UM server.

6. Select the Treat as Authenticated check box.

7. Click OK.

## 4 - Verify that the LCS 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 LCS Deployment Guide. This means there must be an SRV record for '_sip._tcp.xyz.com' where 'xyz.com' is the domain that LCS 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.

## 5 - Configure DNS on the NP-UM server so that it can find the LCS 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 LCS 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 LCS server:

dig _sip._tcp.xyz.com SRV +short

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

0 0 5060 mylcs.xyz.com

where mylcs.xyz.com is the hostname of the LCS server and 5060 is the port used to connect to LCS. 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).

## 6 - 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.

## 7 - 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.

## 8 - 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 LCS-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.