Lync client and UC phones no longer searching by number....
-
Wednesday, February 29, 2012 5:24 PM
If you enter in the person's last four digits of their phone number, the clients will no longer find them. The dial-plan normalization rules and phone number normalization rules have not changed since deployment.
Any ideas?
- Moved by Noya LauModerator Monday, March 05, 2012 8:15 AM (From:Lync Clients and Devices)
All Replies
-
Wednesday, February 29, 2012 8:22 PM
is it happening on UC handsets or lync clients as well. Have you recently updated phones. Try to enable logging on phones and then see what is happening.
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync
-
Wednesday, February 29, 2012 8:28 PM
It is happening on both the handsets, and the lync client. I can turn on logging, however I have yet to find anyone, anywhere to tell me that the logging is worth anything. The CELogs they produce are useless.
Have not updated the phones since cu4, and everything was fine then. However we do have serval phones that will not update, as they report "Last Update Status: (0x5/404)".
-
Wednesday, February 29, 2012 8:36 PMare you seeing any error or warning on event viewer. I would suggest you to do lync logging which will give you more information related to this behaviour. you mean after updating cu4 this behaviour has started?
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync
-
Wednesday, February 29, 2012 8:47 PM
Let me clearify...
We have done no phone updates since updating to CU4, and before/after we had no issues searching by name or number on the UC phones or Lync Client. Now over the last serveral days the Lync clients and UC phones cannot search by number, but can search by name. We store our numbers in AD's work number field in the format xxx-xxx-xxxx. Here is the normalization we use in the Company_Phone_Number_Normalization_Rules.txt file:
\+?[\s()\-\./]*1?[\s()\-\./]*\(?\s*([2-9]\d\d)\s*\)?[\s()\-\./]*(\d\d\d)[\s()\-\./]*(\d\d\d\d)[\s]*
+1$1$2$3Again, this was put in place with RTM, and has never changed. Everything worked fine. In the past we would type in say 4567 (the last 4 digits of the phone number stored in AD) and it would produce the right person and their presence. Now all we get is the number normalized to +1 (xxx) xxx-xxxx and presence unknown.
Checked the Event log on all of the Lync FE's and no errors. Even deleted the AB files and ran update-csuserdatabase -v -force, then followed by update-csaddressbook -v -force 10 minutes later (just to make sure the first command finishes). Each do without any errors in the log. They both report sucess.
Power cycled the phones, and preformed the forced update procedure on the Lync clients, and still cannot search by number, but ok by name.
-
Wednesday, February 29, 2012 8:53 PM
Have you checked that address book is being downloaded on users computers. do the following
1. go to task bar press ctrl + right click on lync then click on configuration are you able to see any error
2. sign out user from lync
3. go to C:\Users\username\AppData\Local\Microsoft\Communicator\sip_username@company.com then delete GalContacts and GalContacts.db.idx and then sign the user again. wait for the ab to download
4. once downloaded then check again.
Also can you go lync share folders and check address book file that does it contain such info or not
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync
-
Wednesday, February 29, 2012 8:58 PM
I have already done that, actually have done it 3 times this week.
When I open the GalContacts.db file in notepad in contains the peoples numbers as +1xxxxxxxxxx and then xxx-xxx-xxxx.
Not sure how to check the share folders address book file, as it only contains the .lsabs and .dabs files. Opening them in notepad just shows garbage.
-
Wednesday, February 29, 2012 9:28 PMIt would be great if you could grab a logging tool messages
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync
-
Monday, March 05, 2012 9:00 AMModerator
Hi Dan,
Any update?
Please make sure the numbers are in E.164 format. Otherwise, Lync won't show them. And there is an article from Jeff for reference.
In addition, please also check this post. Hope helps.
Noya Lau
TechNet Community Support
- Edited by Noya LauModerator Monday, March 05, 2012 9:00 AM
-
Monday, March 05, 2012 4:30 PM
The update is that it still does not work.
As far as setting things in E.164 format, everything since RTM has not changed. The phone numbers have always been in xxx-xxx-xxxx format and have worked just fine. Now, just so we are clear that the E.164 format is not the issue, we also have all of the Exchange UM stuff in E.164 format and they cannot be search by their number either. Something else is the issue.
-
Thursday, April 19, 2012 3:39 PM
We have the same issue. What's funny is, I never realized it until today. Somebody sent an overhead page for me to call a certain number and didn't say who the number belonged to. So, I went to my Lync client because I know that it was an on-net DID, but got back what Dan is getting...the DID tagged with the location code we use to dial. We, too, are looking for suggestions to modify this so we CAN search by DID.The update is that it still does not work.
As far as setting things in E.164 format, everything since RTM has not changed. The phone numbers have always been in xxx-xxx-xxxx format and have worked just fine. Now, just so we are clear that the E.164 format is not the issue, we also have all of the Exchange UM stuff in E.164 format and they cannot be search by their number either. Something else is the issue.
.png)
