Telephone number normalization rules do not work as expected in Communicator 2005 (925052)



The information in this article applies to:

  • Microsoft Office Communicator 2005

SYMPTOMS

You type a telephone number in the Find box in Microsoft Office Communicator 2005. When you click Call, Communicator 2005 tries to call the telephone number without applying the Microsoft Office Live Communications Server 2005 address book normalization rules to that telephone number. For example, the telephone number +33(0) 169555412 does not have the E164 normalization rule applied to it. Therefore, the telephone number is not normalized to +330169555412.

CAUSE

This problem occurs if the normalization rules in the Company_Phone_Number_Normalization_Rules.txt file on the server that is running the Address Book Service are not in the Generic_Phone_Number_Normalization_Rules.txt file on the same server.

WORKAROUND

To work around this problem, follow these steps:
  1. On the server that is running the Address Book Service, click Start, click Run, type cmd, and then click OK.
  2. Type net stop abserver, and then press ENTER.
  3. Close the Command Prompt window.
  4. Open the Company_Phone_Number_Normalization_Rules.txt file in Notepad.
  5. Open the Generic_Phone_Number_Normalization_Rules.txt file in Notepad.
  6. In the Company_Phone_Number_Normalization_Rules.txt file, click Select All on the Edit menu, and then click Copy on the Edit menu.
  7. In the Generic_Phone_Number_Normalization_Rules.txt file, insert a blank line at the start of the file.
  8. Position the cursor on the blank line that you created in step 7, and then click Paste on the Edit menu.
  9. Save the Generic_Phone_Number_Normalization_Rules.txt file.
  10. Exit both instances of Notepad.
  11. Rename the Company_Phone_Number_Normalization_Rules.txt file to Company_Phone_Number_Normalization_Rules.OLD.
  12. Click Start, click Run, type cmd, and then click OK.
  13. Type net start abserver, and then press ENTER.
  14. Type abserver.exe -syncNow, and then press ENTER.
  15. Close the Command Prompt window.

STATUS

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

Modification Type:MajorLast Reviewed:10/3/2006
Keywords:kbServer kbService kbExpertiseInter kbtshoot kbprb KB925052 kbAudITPRO