Is the Call Data variable 'UUI'  in Call Studio ever populated? I have a customer in class who says they use this field a lot on their Avaya system, and they're starting to integrate with Cisco CVP, so he needs to pass this information into Studio.
Similarly he uses this data for screen pop - so is there a way to send UUI from a Studio app for a telephony transfer?
I looked in the CVP Self Service Bootstrap vxml doc for both stand alone and comprehensive environments, and I see ani and dnis being passed into the studio app, but I DON'T  see UUI. 
Thanks, Janine

Carrier has to enable UUI feature, you should emable debug ISDN q931 to verify the UUS info is reveived.
 
Syed Jafri
D+H

No, I never did get an answer. I wonder if you could assign UUI the way cisco assigns _ani and _dnis in ICM, so that it fills in the call data ani, dnis. You could try assigning _uui=<some data in ICM> -- perhaps that would end up copied into the UUI call data variable in vxml server. What are you passing UUI to or from? On 10/28/2011 4:12 PM, Cisco Developer Community Forums wrote: Michael Aossey has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Janine, Did you ever get your answer to this? I have been working with some UUI passing via custom elements but I have not seen a way to get the UUI start parameter to load directly. -- To respond to this post, please click the following link: <http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/4693624> or simply reply to this email. -- Janine Graves

As far as I'm aware the UUI parameter is just a redundant legacy item that unfortunately wasn't implemented. The TCL / VoiceXML bootstrap files would have to be modified to extract UUS from incoming GTD and pass it to the VoiceXML server via the URL params list. It's a bit inconvenient but the advantage of picking up UUI using a custom element is that you stay supported by not modifying any of the standard files.