typically I point folks at CUDLI:
http://www.ciscounitytools.com/Applications/CxN/CUDLI/CUDLI.html
It has a built in data dictionary for all tables (including UdirytDirDb) - you can look at the alternate contact number view there and select, for instance, the TransferType column and see that the enumeration for it is 1 for supervised and 0 for release transfers...
The XML for all the data dictionaries for all versions of Connection are installed with it so you can just fetch the XML directly if you prefer - it's in the DataDictionary folder under the install directory with sub folders for each major Connection release.
 

I didn't understand what you were looking for - sounds like you wanted to know what those columns in the database meant , this is what I took from "DB information".  Instead you're looking for how to get that information from REST, correct?  Not entirely sure what your application is going to look like (i.e. what the user enters and what you wish to provide them based on that entry) but you can fetch menu entry key mappings for call handlers/users and display them no problem - I have samples for how to do this reasonably easily - however you can't search the database via REST for all alternate contact numbers that match a pattern if that's what you're going for.
Perhaps a clearer statement of what exactly you wish to be finding and displaying would be helpful here.

To get menu entries for a user (their primary call handler) you’d issue a GET like this:

https://lindborgload10:8443/vmrest/handlers/callhandlers/9558f1d8-881c-4d5e-a163-554eee2c239e/menuentries

Which returns XML for all 12 keys (0 through 9 and * and #) – the action and destination etc… defined in there. Constructing human readable descriptions of each one is a tad tedious (i.e. an action of 2 is goto which is used to send the call anywhere like another call handler or the like).

There is no way to search for all one key actions across all users directly via REST (certainly can be done via ODBC of course) – you have to fetch the users/primary call handlers and iterate over them – REST API is an object based design, not designed for searching across sub collections in tables or the like.

-J



From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Friday, January 04, 2013 2:34 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Ryan Ash in Cisco Unity Connection(CUC) - CUPI Questions: RE: User Transfer Information

Ryan Ash has created a new message in the forum "CUPI Questions": -------------------------------------------------------------- Sure. Our CUC admins used CUDLI, or something to provide me the information in the original post. Their request is here :
It is common for us to get requests from support and provisioning teams wanting to know what end users are using for their caller input. The requests come in one of two formats; either a request for caller input key actions for a group of users or a request wanting to know who is using a specific number as a caller input target. These requests usually come about when end users move on or when changes are made to contact center scripts.
We have a large number of clusters and thus we typically crawl the restful api either ondemand for requests of this nature or crawl key information (like users, dtmfaccessid, objects, etc) to be stored offline. If I can find this information via the restful api I can create a solution to search it in a manner that fits their needs. However I cannot find this information. I can have seen vmrest/handlers/callhandlers/<object>/transferoptions but these always list the 3 global options and not what I am hoping for.
Thanks so much for your help.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cuc/forums/-/message_boards/view_message/9929815 or simply reply to this email.