TMS not showing Service Preference from Telepresence Server (Using TPConductor)

Question

Hi everyone
Hope you can help me with an issue I'm having implementing a Telepresence solution using Cisco UCS.
We already configure the TMS, Telepresence Server and Telepresence Conductor (all of them on virtual machines using Cisco UCS) using this guide.
http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/tms/config_guide/Cisco-TelePresence-Conductor-with-Cisco-TMS-Deployment-Guide-XC3_0-TMS14_6.pdf
We are facing issues when creating a conference alias. We configure the Alias on the Telepresence Conductor (Cisco Support tell us that Telepresence Server using virtual machines are only manage by the conductor), also we create the Service Preference.
But when we create the alias on the TMS, the Service Preference that we create on the conductor are not shown. We don't know why, or what we need to do to achieve this.
Someone can help us with this? we reinstall all over again and same issue.
Best Regards
Alvaro Rugama

Answer 1

Because you referenced the TMS 14.6 and Conductor XC3.0 deployment guide, that you're also using TelePresence Server 4.1 and those are your software versions.
Can you provide a screenshot of what you're seeing, or not seeing to best understand the issue?
Have you configured Conductor and the TPS to work together, configuring everything on the Conductor per the appropriate configuration guides linked here for your type of environment (CUCM or VCS)?  Making sure you have configured the following:
Service Preference
Service Preference marked for scheduling
Conference Bridge Pool
Conference Template
Conference Alias
I believe the service preference doesn't appear in TMS until you add the alias, and the service preference the alias uses in Conductor is marked for scheduling, however I can't check this at the moment to verify.  Make sure the alias you're inserting into TMS is exactly the same on Conductor, as they have to match.