Office Communicator 2007 R2 audio becomes choppy during attendant console calls or Public Switched Telephone Network calls


Virtual Agent: "Want help? I can help you fix this issue."

Symptoms


You are running Microsoft Office Communicator 2007 R2 on Windows Vista. You make attendant console calls or you make Public Switched Telephone Network (PSTN) calls. You perform an operation that adds to the load of the CPU. For example, you open a new application. In this situation, you find that the audio from Office Communicator 2007 R2 becomes choppy.

Cause


This problem occurs because the threads that handle audio for Attendant Console are not prioritized correctly. This lets other resources to be prioritized ahead of these threads. This behavior cause delayed audio processing. The load that is added on the CPU triggers the audio to become choppy.

Resolution


To fix this problem, apply the following update:
980936 Description of the cumulative update package for Office Communicators Server 2007 R2 Attendant: April 2010

Workaround



To work around this issue, use one of the following methods:

Method 1


Prevent Office Communicator 2007 R2 from automatically starting when Windows Vista starts. Then, manually start Office Communicator 2007 R2, 60 seconds after Windows Vista starts.

Method 2


Let Office Communicator 2007 R2 automatically start when Windows Vista starts, and then re-start Office Communicator 2007 R2 60 seconds later.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

Method 3


Configure the Delay_Sec registry valuein the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Advanced\DelayedApps.
To do this, follow these steps:
  1. Click Start , and then click
    Run .
  2. In the Open box, type
    regedit , and then press ENTER.
  3. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\Advanced\DelayedApps
  4. Right-click Delay_Sec , and then click Modify .
  5. In the Value data box, type
    0 , and then click OK .
Note The default value in the Value data box is 60.


Note To complete the update to the
Delay_Sec registry value, log on to the computer as the local administrator. Then, change the ownership of the DelayedApps registry subkey to the local administrator account. Before you apply the changes on the
Owner tab of the Advance Security Settings for DelayedApps dialog box, make sure that the Replace owner on subcontainers and objects check box is selected.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.