02-06-2012 02:05 AM - edited 03-17-2019 10:47 PM
Hello, I have an issue with sending the phone book to the endpoints, we have a C20 included in one of the phone book directories we created and whenver we include it to the Phone Boo, in the Set on Sytem part, the C20 still doesn't show any contacts in its phone book, I've tried enforcing the settings from Administrative Tools > Configuration > Network Settings > TMS Services, but still doesn't show the phone book... How could know what's actually going on when trying to enforce the phone book or setting in on the system ?
Kind regards.
Solved! Go to Solution.
02-06-2012 08:35 AM
Hi Mario
When endpoints look up phonebooks, it's a live lookup so there is a few steps you can do to verify that the phonebook setup is working as it should.
First of all the phonebook address configured on the endpoint. From the same network location the endpoint is located try to access the phonebook link from a regular browser. If you see the "Phonebook Service" you know that TMS is open for queries.
If you do not see the phonebook service you need to find out if this is isolated to that particular endpoint. If this is happening to all the endpoints, it's likely the Public folder in the IIS server does not have Anonymous access enabled with a valid user / domain user. Group policies can disable the standard service accounts so check this.
TMS also has a different feature where it filters out the phonebook entires. It basically checks if the endpoint that is looking up in the phonebook is routable. If not the entry does not show up. If you want it to show up regardless you can change the setting under general settings "Route phonebook entries" to "No" and see if this resolves your issue.
So if the phonebook address is correct and the IIS is not blocking the request and the endpoint is not filtered then check if the unit actually have a contact method. Endpoints without and address will not show up in the phonebook.
A last resort would be to do a wireshark capture while looking up the phonebook and raise a tac case for analysis.
Magnus Ohm
02-06-2012 08:35 AM
Hi Mario
When endpoints look up phonebooks, it's a live lookup so there is a few steps you can do to verify that the phonebook setup is working as it should.
First of all the phonebook address configured on the endpoint. From the same network location the endpoint is located try to access the phonebook link from a regular browser. If you see the "Phonebook Service" you know that TMS is open for queries.
If you do not see the phonebook service you need to find out if this is isolated to that particular endpoint. If this is happening to all the endpoints, it's likely the Public folder in the IIS server does not have Anonymous access enabled with a valid user / domain user. Group policies can disable the standard service accounts so check this.
TMS also has a different feature where it filters out the phonebook entires. It basically checks if the endpoint that is looking up in the phonebook is routable. If not the entry does not show up. If you want it to show up regardless you can change the setting under general settings "Route phonebook entries" to "No" and see if this resolves your issue.
So if the phonebook address is correct and the IIS is not blocking the request and the endpoint is not filtered then check if the unit actually have a contact method. Endpoints without and address will not show up in the phonebook.
A last resort would be to do a wireshark capture while looking up the phonebook and raise a tac case for analysis.
Magnus Ohm
02-07-2012 02:38 AM
Hello Magnus, thanks for the response, the IIS anonymous access setup change fixed the issue, thanks a lot.
Kind regards.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide