PhoneNumberNormalizationRules missing

Wednesday, October 22, 2008 9:40 AM

0

Hi,

the HKEY_CURRENT_USER\Software\Microsoft\Communicator\PhoneNumberNormalizationRules registry
entry was missing on the client (OC2007) so:

I have a Company_Phone_Number_Normalization_Rules.txt in the OCS 2007 EE ABS share.

I used abserver -regenUR followed by abserver -syncNow on the OCS 2007 web
components server.

On the Windows client I stopped the communicator.exe process

I deleted %userprofile%\local settings\application data\Microsoft\Communicator\galcontacts.db file and then I started
OC 2007 again, a new galcontacts.db file was created on the client

BUT

the value PhoneNumberNormalizationRule is still missing!!

Any idea? How can I obtain the PhoneNumberNormalizationRules value uploaded in the client registry?

thanks

All Replies

Wednesday, October 22, 2008 11:29 AM

0

Normalization Rules have nothing to do with Addressbook Server functionality

Normalization Rules are downloaded automatically by the client at logon process but need to be configured on the OCS Environment

Open your OCS Management console and Right Click the Properties of your forest and select Voice Properties

Start Creating your location profiles and Normalization rules

Check the Voice Planning & Deployment guide

http://www.microsoft.com/downloads/details.aspx?FamilyId=24E72DAC-2B26-4F43-BBA2-60488F2ACA8D&displaylang=en
Wednesday, October 22, 2008 12:14 PM

0

Hi Deli, we have already configured the ocs environment and the main IM, conference, telephone and RCC services work fine, we have a problem with RNL (for some user it doesn't work ,even if the content of the addressbook is correct), studying this issue, we notice that the PhoneNumberNormalizationRules value in the registry key HKEY_CURRENT_USER\Software\Microsoft\Communicator doesn't exist.

Any idea is welcome

Thanks
Wednesday, October 22, 2008 12:48 PM

0

Are these users enabled for Enterprise Voice?

Compare them to the other users

Do you have the latest update for Communicator?

http://www.microsoft.com/downloads/details.aspx?FamilyID=1ad57f8f-78f7-45f6-a8c0-805936f46645&DisplayLang=en
Wednesday, October 22, 2008 1:15 PM

Moderator

1

Deli Pro-Exchange wrote:

Normalization Rules have nothing to do with Addressbook Server functionality

Actually that is incorrect; the contents of the 'Company_Phone_Number_Normalization_Rules.txt' file are loaded into the 'PhoneNumberNormalizationRules' registry setting (minus comments and test rules, followed by the built-in rules.) If this registry entry is blank then client-side normalization of Outlook contacts and numbers keyed-into the OC client will not function correctly. This is especially bad if using Remote Call Control as EV dialing rules are completed ignored in that scenario.

Take a look at these two blog entries for more information on the process, specifically the last portion of the first link:

http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=17

http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=26

Are you missing the entire registry value itself or just the string data? Did you manually delete it or did it just 'vanish'? The value should be created by default after client installation.

I've done some testing in the past and no amount of ABS re-syncing and client restarting would bring the value would seem to bring the string data back, regardless of whether the vlaue was completely missing the registry or just blank. A client reinstallation might do the trick but I'm going to keep digging into this as I'd like to identify the trigger

Wednesday, October 22, 2008 1:42 PM

Hi, thanks for your answer,

>Are these users enabled for Enterprise Voice?

>Compare them to the other users

Yes, all users are enable for enterprice voice

>Do you have the latest update for Communicator?

It's not the last version, but all users have the same version (both users that have the key value and the users that haven't it)

I think it's better I'll explain you the scenario:

we are integrating OCS and Italtel PBX.My scenario is this:

MOC(A)   <---> OCS <-> Cisco GW <-> Italtel <------> Telephone (B)
+08987066666                                                        717066351 (Private Number)

We created a new Location Profile for the Mediation server named 'dialstring' to resolve private numbers .
We have created a new normalization rule for address book:

(71\d*)
$;phone-context=DIALSTRING

If  receive an incoming call from B to A the call runs, but the RNL on MOC doesn't work. I see the toast with "717066351"
In the Address Book there is a OCS user with this number:
Mario Rossi (RCC)    OCS0001
          sip:Mario.Rossi@mycompany.it    tel:0003902555555
   +3902555555        tel:717066351;phone-context=DIALSTRING
   717066351           Mario.Rossi@mycompany.it

We have noticed that on the client A registry the PhoneNumberNormalizationRules entry doesn't exist, so maybe this problem is connected to the RNL issue.

Is there a way to force the download of the PhoneNumberNormalizationRules value?

Thanks

Wednesday, October 22, 2008 3:25 PM

Hi Jeff, I'll look your links ASAP, thank you very much.

I 'm missing the entire registry value not only the string data, I 'm not sure if it was deleted or not..

I'll let you know if your links help me

Bye

Wednesday, October 22, 2008 9:53 PM

Hey Jeff,

Does Microsoft have some documentation on this RCC feature/problem

I've try to find an explenation in the documentation but no luck (not in the OCS Voice guide anyway)

Proposed As Answer by kagen15 Thursday, October 01, 2009 10:24 PM

Thursday, October 15, 2009 2:34 PM

Apologies for resurrecting a year-old thread, but there was no answer here, and I'm having a very similar issue.

My PhoneNumberNormalizationRules registry entry is not updating when I update the Company_Phone_Number_Normalization_Rules.txt file. That is, once a user already has this registry entry, it no longer updates. New installs on new computers pull down the proper and current data.

In hopes of fixing this, I've uninstalled MOC, deleted the entire "Communicator" registry key and reinstalled. It replaced the key and some entries, but not PhoneNumberNormalizationRules. Has anyone found a way to force the sync of this?

Thursday, October 15, 2009 3:31 PM

Fixed!

Exiting MOC, deleting C:\Users Folder\AppData\Local\Microsoft\Communicator\EMAIL REMOVED and relaunching MOC repopulates the PhoneNumberNormalizationRules key!

Wednesday, October 28, 2009 11:55 PM

Would you mind to clarify the path and what exactly I should delete? I tried C:\Documents and Settings\%username%\Local Settings\Application Data\Microsoft\Communicator and then deleted the communicator directory. I then relaunched MOC and the registry value did not get updated. I also tried C:\Documents and Settings\%username&\Application Data\Microsoft\Communicator with the same result. These directories do get recreated once MOC is open but the registry for PhoneNumberNormalizationRules is not updated.

I am not using EV but RCC with OCS 2007 R2.

Thanks

Thursday, October 29, 2009 1:13 PM

I am also not using EV, but am using RCC with OCS 2007 (not R2). I am running Windows 7 - the directory structure of other OS's will be different.

I had to delete:

C:\Users\kcross.domain\AppData\Local\Microsoft\Communicator\sip_KCross@domain.com\

XP Users will probably have to delete c:\documents and settings\username\application data\local\microsoft\communicator\sip address.com\