Hi,

I have enabled the web Search for one test user, and found the following problem:

When user type the phone number 0123456789, the Lync will normalise the number to "+358123456789" but no contacts can be found.

When user type the phone number +358123456789, the Lync founds the contact.

When using the GAL search, both formats find correct contact.

Is this something that Lync client send to the Web Search the number I have typed, and not the number which is normalized?

--

Did this issue happen with other normalization rules?

You should check the normalization rule you used for the test user is applied to the test user.

Not tried with other dial plans, but if I switch back to GAL search there are no problems. So if the problem is in the normalization rules, why it does not affect on the GAL search?

test the LYNC client on different computer or else

delete the sip profile folder on the client machine(c:\users\<user account>\appdata\local\microsoft\communicator\sip_user@domain.com)

Launch the lync client again.

Thanks Josh,

Do I understand right, if you are using Web Search only, you have no problems with it?

I'll test your advice, but I just wonder if I just change the client policy for user the behavior is different.

Ok I removed the whole user profile from the workstation -> No changes. So the problem must be with the Server search :-(

Refer the article

http://blog.schertz.name/2010/11/forcing-lync-address-book-web-query/

http://blogs.technet.com/b/nexthop/archive/2012/06/21/lyncmd-troubleshooting-the-lync-2010-address-book.aspx

http://blog.insidelync.com/2012/02/lync-address-book-client-synchronization-errors-and-common-problems/

http://waveformation.com/2011/02/11/restore-lync-abs-default-configuration/

The above article may helps

Thanks Josh about those links, but they were not so helpful. I actually tested this on my L2013 test environment and find out the same problem.

Anybody else seen this? Or is it so, that "WebSearchOnly" is not a common configuration for companies.

If you like to test this by yourself, I took the following steps:
1. User A and User B enabled for the Enterprise voice.
2. User B's lineuri is set to: "tel:+3589123456" also on telephone attribute in the AD object have "+3589123456".
3. User A have client policy which have "WebSearchOnly" for the "AddressBookAvailability" (set-csclientpolicy...)
4. User A have dial plan which pattern is "^0(9\d{2}\d+)$" and translate rule is "+358$1"
5. User A type the number "09123456" on the Lync client the number is normalized to "+3589123456", but User B is not found.
6. User A type the number "+3589123456" on the Lync and User B is found.
7. If you change the client policy so to "WebSearchAndFileDownload" or "FileDownloadOnly" both steps (5 and 6) can find user B.

Hi Petri,

Did you found a solution for your problem?

I have the same issue on my infrastructure.

Thank you for your reply or help.

Best regards

Nic