Hi!

I've got all entries in LYNC contacts duplicated.

i.e. when I press Call button I can see

Work 1144

Mobile 4144

Work 1144

Mobile 4144

 

Any ideas how to fix it?

Verify that you do not have 2 entries in Outlook. 1 may be a contact you (or someone/something else created) another may be from the Address book service. If they have the same name, it may be showing both values.

• Proposed as answer by Tom ArbuthnotMVP Sunday, April 24, 2011 9:23 AM

Hello,

I'm getting the same problem for some of my users too. There are no duplicate entries in Outlook at all

 

Hi!

No it's not an Outlook.

By the way if I search not Lync enabled user it shows only one phone number

Regards, Alexey

Hi
Same issue for some of our users... not an Outlook or Lync cache issue.
I made some research with Snooper: only one AD entry is processed, but is duplicated on the Lync contact card.

could be same issue as here: http://social.technet.microsoft.com/Forums/en-US/ocsaddressbook/thread/a2189771-e5b1-4c50-acbd-2a84f78d5d52

• Proposed as answer by Laurent C. _ Saturday, October 01, 2011 4:36 PM
• Unproposed as answer by Laurent C. _ Saturday, October 01, 2011 4:36 PM

Dear
I think I have the solution.

Have a look on the Lync client options of users with duplicates entries... the phone tab

They should have obsolete Phone numbers set. Those numbers are shared with other users, and create duplicates entries...

• Proposed as answer by Laurent C. _ Saturday, October 01, 2011 4:44 PM
• Unproposed as answer by Laurent C. _ Monday, October 03, 2011 7:03 AM

Hi!

 

I think it's not my case.

As you can see I have all checkboxes disabled but I still have duplicate phone numbers for myself  in the address book.

 

Let me join this discussion with the same problem

Symptoms...

• User account in AD contain non normalized Work Number (like "12-1234")
• Company_Phone_Number_Normalization_Rules file was created to include that numbers in Lync contacts

(\d{3}\d+)
$1

 

I've seen this behavior in OCS based on the defined normalization rules.  Take a look at the GalContacts.db file on any Lync workstation and see if the duplicate entries for these users appear in the file itself.

Yes, I can see duplicate entries in my GalContacts.db

Ok, if you don't mind it may help to share your normalization rules and the strings you have populated in an example user account's various telephone attributes?  Also, have you messed with the absconfig Resource Kit tool to modify your address book configuration at all?

Microsoft support said me they know the case:

I did not test but they suggest to normalized those 4 digit number by adding a "+" in front of them (via a rule in the Company_Phone_Number_Normalization_Rules.txt)

... hope it helps

 

Here you go

We are using 4-digit internal phone numbers and 6xxxx numbers to call from Lync  to Cisco UCM phones and back

##
## Normalize phone number patterns from Active Directory into UCM Dial Plan
##
## [1-7]XXX   --> XXXX
(^([1-7]{1}[0-9]{3})$)
$1
## +XXXX   --> XXXX
^\+(\d{4})$
$1
## 6.xXXX   --> 6.xXXXX
(^([6]{1}[0-9]{4})$)
$1
## +7xxxxxxxxxx  --> 8XXXXXXXXXX
^\+7(\d{10})$
8$1
##
## XXX XXXXXXX   --> 8XXX XXXXXXX
(^([0-9]{10})$)
8$1
^\+(\d{11})$
810$1
##
^\+(\d{12})$
810$1
##
^\+(\d{13})$
810$1
##

 

Basically anytime you normalize numbers in OCS/Lync outside of RFC3966 format then strange issues (like this) will appear. This is a side-effect of not following best practices and always normalizing numbers into RFC3966 format within Lync.

What are they calls being routed to?  Ideally you should be properly normalizing these strings into RFC3966 (+E.164) and not using extension dialing.  If you have a media gateway that device should be configured to de-normalize the numbers into the format required by your PBX or whatever you are connected.

If you are using Direct SIP then Lync can be configured to translate the patterns during outbound calls AFTER the intial normalization has been completed: http://technet.microsoft.com/en-us/library/gg412803.aspx  This way you can de-normalize the string into the format that the target system expects to see them.

 

 

As we can read here, just adding + to internal extension not making em RFC3966, bacause they are not world-wide reachable.

The proper format is just like +74999269193;ext=9193

But it's reeeally pain to read!

Why just not using numbers in AD as they written, then normalize them by Interal Lync rules. This works perfectly when dialing manually from Lync client, but we get this double records when using normalization rules with .TXT...

Adding a 'plus' to the line does not just 'fix the issue' but does tell Lync that the string is 'global' and it will attempt no normalization on inbound routing.  Basically if Lync sees a plus then it assumes it's normalized properly and sends the call as-is.  When a plus is used in non RFC3966 formats I've seen that double-entry issue.

Again, all numbers should be normalized into +E.164 format, and then de-normalize them to something else on the way out of Lync if needed. Pseudo normalizing strings within Lync to something like +7777 is just a recipe for problems, or quirky issues this the one here.

 

Hallo 

You can try this solutions:

1. Normalization

In normalisation File on Lync Share try to add plus sign example:

^(\d*)$

+$1

2. Similar SIP's

If you have communicator before lync or same sip with another domain, look at SIP's folder: AppData\Local\Microsoft\Communicator, close communicator and delete all folders starting ""sip_" on clients which phones is dublicate,  in my case it is the solution.

3. Lync Options

In Lync Client on users who contacts duplicate uncheck "include in my contacts card options" in -> Options -> Phones

4. Update on lync server

Update-CsUserDatabase -force

Update-CsAddressBook –force

5. Run Lync and wait for update

6. you can experiment with ABS Configuration Tool

7. if you keep numbers in AD try add + before it

 

 

 

• Edited by DimiKo Wednesday, January 04, 2012 7:39 AM

I know this is an old post but I'm seeing the same in our new Lync implementation..   some users, not all, have duplicate numbers listed in their Call pull down.   The odd thing is the 1st number shows 712-292-8928 and the 2nd shows +7122928928.   If I open up galcontacts in a text editor, that user actually has two numbers and it looks like  tel:+17122928928 and 712-292-8928

What would be causing this?

• Edited by Esteban Almeida Wednesday, June 27, 2012 5:58 PM mistype

 Set-CsClientPolicy -AddressBookAvailability WebSearchOnly

can help you fix issue!

Set-CsClientPolicy -AddressBookAvailability WebSearchOnly

can help you to fix!

Hi,

Any update on this issue, we are suffering the same. If we use normalization rules, we see work and mobile pone twice.

Thanks,

Aitor

I know this is an old post but I'm seeing the same in our new Lync implementation..   some users, not all, have duplicate numbers listed in their Call pull down.   The odd thing is the 1st number shows 712-292-8928 and the 2nd shows +7122928928.   If I open up galcontacts in a text editor, that user actually has two numbers and it looks like  tel:+17122928928 and 712-292-8928

What would be causing this?

Hi,

What did you do to resolve this issue? I am facing exact same issue.