Can you confirm whether your TMS is using proxy to access the endpoints? Also, can you confirm whether the application user configured in CUCM has the proper permission and it is associated to the endpoints? If all is correct, can you try to totally purge CallManager and its endpoints from TMS and add them again?
Regarding the top level domain configuration, this is required in order to have TMS scheduling endpoints registered to CUCM, because TMS will always append the top level domain to calls going through the Cisco Unified CM.
Please, take a look at this guide, page 46 and starting on page 72:
In addition, as you have a new TMS software version, I imagine that you are not using the old Cisco TMS appliance, so you probably have your TMS running under a standard Windows Server, and you probably have firewall, antivirus or any other security program running on that server.
Can you try to completly disable any local firewall and/or antivirus on the Windows where TMS is installed? If TMS begins to work as expected after turning off those security programs, I think you will have to add the TMS's executables as exception to the firewall/Antivirus softwares, so that they won't cause conflict with TMS's services.
In this folder you will find all the executables used by TMS's service:
C:\Program Files (x86)\TANDBERG\TMS\Services
For TMSPE, this is the path for the executable "C:\Program Files (x86)\TANDBERG\TMS\TMSProvisioningExtension\app\bin\wrapper-windows-x86-32.exe"
Try this and give us a feedback. =)
I hope this help.
Please rate useful replies and remember to mark any solved questions as "answered".
Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
We are also facing the same issue, we are using TMS 14.4.2 version and CUCM is running on 220.127.116.1100-2 version. All the above trouble shooting steps performed on TMS but still facing the same issue. We upgraded TMS in September - 2014, after upgrade we saw only one CTS device is showing the "Manager system not available" error.
Today we got errors for all the CTS devices which are registered to CUCM, but some of the devices like SX 10 are still active without any errors.
Worked with Cisco TAC on this issue, we found that there is a compatibility issue between TMS & CUCM. Cisco recommend to upgrade Call Manager to version 9.1.2, as it is more stable with TMS 14.4.
Do we really need to upgrade CUCM?? any other workaround for this issue.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...