TMS phonebook failed in C-series endpoints after migration from appliance to VM

[Arbenjamin]

Dear all,

We have migrated the TMS 12.8  from the appliance to the TMS 13.0 on the VM platform. There is no TMSPE consideration, and mainly used for management and phonebook service.

After the migration is completed on the VM platform, we have found the C-series endpoint failed to receive phonebook from the TMS( while MXP 95 endpoints works fine with the TMS phonebook). 

In the C-series endpoint, we have double check the Configuration -> Phonebook Server 1 : URL. The link is converted from http://<TMS appliance address> /tms/public/external/phonebook/phonebookservice.asmx to  http://<VM TMS> /tms/public/external/phonebook/phonebookservice.asmx.

( Also, we have check the permission of both phonebook page, and there is no IIS problem).

In the MXP 95 endpoint, it can receive the phonebook from both VM TMS and TMS appliance.

Best Regards,

Ben

[Wayne DeNardi]

Have a look through the forums, there are a couple of similar issues about devices not accessing the phonebooks which include some fixes:

https://supportforums.cisco.com/discussion/12073851/check-if-tms-phonebook-reachable-codec

https://supportforums.cisco.com/discussion/12041581/c-series-endpoints-cant-receive-tms-phonebook#4124552

In general, it's that the C-series can't talk directly to the TMS server for some reason (web proxy, wan optimizer, incorrect IIS permissions, etc).

The curl command in some of those links will let you see what the codec is seeing when it tries the request.

There is also the possibility, if there is an IIS issue, that your MXPs are also not working, but are showing you a cached version of the phonebook - try updating the phonebook (ie, add a new entry) and see if it appears on the MXPs.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

[Arbenjamin]

Dear Wayne,

Thank for your kindly support. 

Actually, I am the owner of the second forum link. 

Here is some extra information,

TMS 12.8 appliance installed on Window Server 2003( Standard edition SP2)

Migrated TMS 13.2 VM installed on Window Server 2008 (Window Server 2008 R2 SP1)

Since the TMS configuration is same between TMS appliance and TMS VM, we guess the problem should be related to window server configuration.

Here is the putty log from the C-series endpoint with curl command.

From the Curl command to TMS VM(172.23.xxx.xxx), there is error message "You do not have permission to view this directory or page using the credentials that you supplied". 

So, we have disable "Anonymous Authentication", "basic Authentication" and " windows Authentication". However, still no luck.

Anyone knows configuration on the window server ?

Best Regards.

Ben

[Wayne DeNardi · Accepted solution]

Hi Ben,

As confirmed by the curl command - you don't have access to the web page as an anonymous user.  You'll need to correct your permissions.  One of the quickest ways to do this would be to try reinstalling TMS on to the server again - this should reconfigure the IIS settings required for TMS.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

[Arbenjamin]

Dear Wayne,

You are right, the problem is the access right of the anonymous user.

The problem is solved after the weekend, i guess the window server take time to reflect the changes.

Anyway, we are much appreciated on your afford.

Best Regards,

Ben

[Magnus Ohm]

Hi

"So, we have disable "Anonymous Authentication", "basic Authentication" and " windows Authentication". However, still no luck."

You need the anonymous authentication to be enabled, the others should be disabled on the "public" folder in the structure.

/Magnus

[Arbenjamin]

Dear Ohm,

Thank for your kindly support.

We still have a silly concern in terms of security, because everyone can access the phone book. 

Best Regards,

Ben 

[Wayne DeNardi]

It's just as easy for someone to be able to get the phonebook from one of your endpoints as it is from the TMS server, so I wouldn't be too concerned about TMS being a security problem.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.