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 184.108.40.20600-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.
All Info from userid1run sql select * from enduser where userid='userid1'
userid selective info for multiple usersrun sql select eu.userid,eu.islocaluser,eu.status, eu.mailid, eu.directoryuri, dpc.name as ad_filter from enduser eu left join direct...
New update of Cisco Meeting Server book with Streamer and Scheduler components, the book will cover the following:certificates requirements, clustering, dial plan with call flow, WebRTC, WebBridge3, CallBridge, recorder, streamer, scheduler, NAT Traversal...
The Scheduler component was introduced as a beta feature in version 3.3. It was added as anew component that enabled Web app users to schedule meetings, modify the scheduledmeetings, and notify participants via email. From version 3.4, Scheduler is fully ...
A collection of the most important notes from different resources for Cisco CMS and vbrick integration. Live Streaming (Webcast) integration with VBrick DME allow users to watch any live streamed CMS conference anywhere inside the network from differ...