cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1174
Views
0
Helpful
6
Replies

EX90 Endpoint Will Not Receive TMS Phonebooks

kep224
Level 1
Level 1

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

1 Accepted Solution

Accepted Solutions

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 is the IP address or hostname of your TMS server.

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.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

View solution in original post

6 Replies 6

Hi Kyle

Are you created a phonebook in TMS?

Are you assigned a phonebook to your EX90?

br Oleksandr

amehla
Cisco Employee
Cisco Employee

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

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 is the IP address or hostname of your TMS server.

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.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

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. 

Having the same issue.  I issued the command and got the following:

$ curl http://10.0.240.9/tms/public/external/phonebook/phonebookservice.asmx

   

   

    </p><p></p><p> PhoneBookService Web Service</p><p></p><p>

 

   

     

PhoneBookService


     

         

Get global phone books.

     

     

         

The following operations are supported.  For a formal definition, please review the Service Description.

             

                 

  •                 GetPhonebooks

                   

                     
    Get all phone books set on the given system

                   

                 

                 

                 

  •                 ResolveSystem

                   

                     
    Resolve the given number to a system name

                   

                 

                 

                 

  •                 Search

                   

                     
    Search the phone book(s) set on the given system

                   

                 

                 

                 

         

       

       

     

    However the EX90 just spins when you click directory...

    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...