01-08-2014 02:51 PM - edited 03-18-2019 02:24 AM
We have an EX90 that is provisioned via TMS. Systems messages can be sent and the EX90 can be configured via TMS. However, the EX90 will not display any phonebooks assigned to it in the Directory tab. When viewing the phonebook server config via the EX90s webui, all information appears to be correctly provisioned via TMS. Any help would be greatly appreciated.
Thanks,
Kyle
Solved! Go to Solution.
01-09-2014 03:37 PM
Is there perhaps a firewall between the endpoint and TMS that is stopping the endpoint requesting and receivng the phonebook from TMS? Or is it set to "https" when only "http" is available?
You can do a quick test of the connectivity by logging in to the endpont's CLI as "root" via telnet/ssh and requesting the phonebook:
curl http:///tms/public/external/phonebook/phonebookservice.asmx
where
You should receive some HTML back if you have access, or a timeout/couldn't connect error if you don't.
Wayne
--
Please remember to rate responses and to mark your quesion as answered if appropriate.
Please remember to mark helpful responses and to set your question as answered if appropriate.
01-08-2014 10:52 PM
Hi Kyle
Are you created a phonebook in TMS?
Are you assigned a phonebook to your EX90?
br Oleksandr
01-09-2014 03:34 AM
Hi Kyle,
i am assuming that you had configured the Phonebook server configuration correctly on EX90 unit.
In phonebook server URL, try to add the ip address of TMS instead of its hostname to check for any DNS issue.
eg. https://ipaddress/tms/public/external/phonebook/phonebookservice.asmx
01-09-2014 03:37 PM
Is there perhaps a firewall between the endpoint and TMS that is stopping the endpoint requesting and receivng the phonebook from TMS? Or is it set to "https" when only "http" is available?
You can do a quick test of the connectivity by logging in to the endpont's CLI as "root" via telnet/ssh and requesting the phonebook:
curl http:///tms/public/external/phonebook/phonebookservice.asmx
where
You should receive some HTML back if you have access, or a timeout/couldn't connect error if you don't.
Wayne
--
Please remember to rate responses and to mark your quesion as answered if appropriate.
Please remember to mark helpful responses and to set your question as answered if appropriate.
01-10-2014 06:40 AM
Thank you Wayne. Your answer helped solve the issue. When I issued the curl command I saw the html output of our captive portal; the codec had a http proxy in front of it as it was using an IP address from our guest pool.
02-26-2014 02:34 PM
Having the same issue. I issued the command and got the following:
$ curl http://10.0.240.9/tms/public/external/phonebook/phonebookservice.asmx
PhoneBookService
Get global phone books.
The following operations are supported. For a formal definition, please review the Service Description.
Get all phone books set on the given system
Resolve the given number to a system name
Search the phone book(s) set on the given system
However the EX90 just spins when you click directory...
02-26-2014 02:51 PM
Hey Guys,
Just and update. I change my phonebook to use the IP address of TMS instead of the hostname and it started working. The FQDN of TMS IS resolvable...
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