After each server has passed the Domain Name System (DNS)/Lightweight Directory Access Protocol (LDAP) traffic tests you can then set up the verification environment for testing client HTTP/HTTPS and server Session Initiation Protocol (SIP) traffic.

To prepare the verification environment

  1. Begin by setting up two client computers, Client A and Client B. In Active Directory, create two new users (User A and User B). Enable these users for Office Communications Server. Give the two users local Administrator rights on their respective computers.

  2. Log on to Client A as User A. Log on to Client B as User B.

  3. On each computer, click Start, click Runand then, in the Rundialog box, type perfmonand press ENTER.

  4. On the Communicator Web Access (2007 R2 release) server do one of the following:

    • If you are running Communicator Web Access on a Windows Server 2003 computer, in the Performance scope pane, select Performance Monitorand click Add. In the Add Countersdialog box, under Performance Object, click CWA - 03 - User session Service. In the list of counters, click CWA - 002 - Sessions, click Add, and then click Close. Click OK.

    • If you are running Communicator Web Access on a Windows Server 2008 computer, in the Performance scope pane, select System Monitorand click Add. In the Add Countersdialog box, under Performance Object, click CWA - 03 - User session Service. In the list of counters, click CWA - 002 - Sessions, click Add, and then click Close. Click OK.

  5. Open the Internet browser on Client A and Client B, and navigate to the Communicator Web Access URL.

  6. Verify that, from Client A, you can sign on to Communicator Web Access as User A. Verify that, on Client B, you can log on to Communicator Web Access as User B.

To verify client HTTP/HTTPS traffic and server SIP traffic

  1. Verify that the CWA – 002 Sessionsperformance counter for each server shows one connection each.

  2. Verify that User B (signed in to Client B), can search for User A and can add User A to his or her contact list.

  3. Verify that User A (signed in to Client A), can search for User B and can add User B to his or her contact list.

  4. Verify that the following functions work as expected:

    • Instant messaging

    • Presence change

    • Block and unblock of each contact from each client

    • Contact deletion on each client

  5. Verify that, when you unplug the network cable from the load balancer to one of the Communicator Web Access servers, the client connected to that server is signed out.

  6. On the client that was signed out in the previous step, sign on again to Communicator Web Access. Verify that the user can connect to the Communicator Web Access server that is still running.

  7. Verify that the CWA – 002 Sessionsperformance counter for the remaining server shows two connections.