Hi Wayne,Thanks for the reply

1/ Ive gone into TMS > Add Systems > From List > CUCM , as you've suggested and I currently do not see anything listed/found under System Name ( see screen shot )..

Does that mean that I need to set up an association in VCS first ?.. ( VCS > Configuration > Unified Comms ).. or do I need to set up a user group and roles in CUCM to talk to TMS as described in the discussion https://supportforums.cisco.com/discussion/11783026/adding-cucm-tms

2/ This kinda makes sense in that TMS should then push out the phonebook to a registered device.. From a CUCM registration perspective, how does the DX80 know to just use TMS as the source and not anything else provided from the CUCM cluster ?.

Thanks for the reply Wayne..I

Thanks for the reply Wayne..

I found the very same document the other day and had been using it for reference.. Unfortunately, DX80s dont fall under a TC based endpoints.. so it doesnt look like using TMS as a source for phonebook is possible ..

If you have managed it, please say !.

On a side note, whilst browsing through the Settings on the DX80 itself, I found a Cisco Directory Credentials option where it prompts me for my UDS details ( see attached screen shots )..

It does not seem to accept any of my account details to log in.. ( e.g CUCM admin, local user CUCM account or extension mobility account ).

Any idea what it does as I cannot find any details online for the setting..

Hi Jon,No, I haven't done it

Hi Jon,

No, I haven't done it myself - we don't have any DXs here (yet), but I would have thought it should have been possible similar to all the other endpoints - but I guess, as it's not running TC software, it's a different beast. I've just had a good read through the Admin Guide for the DX80 and it doesn't seem to mention you can do this at all, not is there any mention of TMS in the guide. So unless you can configure your CUCM to provide the DX80 a different phonebook to other devices, I can't see any easy/automatic way to give the unit a TMS phonebook.

Maybe you should log this as a Feature Request through your local Cisco Account Manager for consideration in a future software release.

Wayne

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

Alright guys I have a work

Alright guys I have a work around to this but its not pretty and frankly Cisco needs to solve this, how are they possibly thinking they can deploy a device like hte DX80 without tying it to the TMS phonebook. Thats a travesty and the fees to move your VC registered endpoints onto CUCM is prohibitive to say the least. That all said, Cisco get it together and solve this or the DX series will be dead to SO MANY people and companies.

Now with that all said, the work around:

The goal is to get all TMS endpoints into CUCM as a user so that they will show in the directory. Now you have two options. 1 if your MAIL ID is what you use for your URIs then all you need to do is import the CR users from AD (if CRs have AD accounts). You will then have a directory as long as all your URIS are right. Thats fine and relatively scale able. For those of us that do not have this done like this you will need to Export all of your video devices from TMS into an excel sheet. You will need to work the sheet a bit so that the columns can line up to DISPLAY NAME (name of endpoint) and MAIL ID (URI). You can import this into CUCM to create the CR users and they will then show in the directory. This is not long term scale-able and when you want to change a room you now have to edit a manual CUCM user. This will only work if you run 8.5 or higher.

Hi All,
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
view more

The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.
...
view more