I'm not sure if this is relevant or if you are still looking for a solution to this, but I will go ahead an post as I recently had to resolve this issue for a client. This is working in UCCX release 10.6.
The answer is, "YES!" You can obtain Account Number info from the Import Contacts data. It is found on the Get Session Info step, under the Context tab, using the system variable "BAAccountNumber." You can also obtain "BACallResult" and "BACampaign" for the dialer result and associated outbound campaign application. In your script, just assign these to variable type: String.
I know this is an older thread but make sure you are aware of the following. My guess this is what will trip up most folks as it's not documented anywhere. Especially since UCCX allows you to use a dialing prefix, but that will cause the variables to come in as null as it modifies the session information. Your outbound call to the customer must not be modified in anyway (translation or digit strips).
UCCX: Outbound BA Call Variables Return 'null' If Gateway Dialpeers Append and Strip Digits CSCve40147 Description Symptom: 1. The UCCX script uses the Get Contact Info step to get the session ID of the call.
2. The UCCX script then uses the Get Contact Info step for that session to populate the outbound BA variable.
3. The BA variable names assigned are the proper case since case matters.
4. Even though the above steps are followed properly, the BA call variables are populating as 'null' in the script as seen from the Engine (MIVR) logs and/or the UCCX Script Editor debug mode.
Conditions: Once the gateway determines the call result of the call (after live voice or voicemail is detected, etc), UCCX writes the BA variables and the dialing contact to memory in the IVROutboundContactKey table. See the engine logs for example:
If the gateway dialpeer inbound from UCCX appends digits to the UCCX campaign's called number and then removes the digits on the outbound dialpeer to the UCCX CTI port, UCCX will not be able to return the BA call variables to the call since the number that is written in memory has appended digits, while the call presented to UCCX does not.
In the UCCX Engine log snip-it above, the digits 91 where appended to the dialed contact 8765309 to give 876530991. The 876530991 number is the number associated with the BA variables.
When the call comes back to a CTI route point after stripping the 91 digits, UCCX will use the original number 8765309 and will not be able to find that number in the IVROutboundContactKey table.
Workaround: Do not use gateway dialpeers to append and strip digits for UCCX outbound calls.
This is a documentation defect to add this information to the UCCX Administration guide.
Contact Center users dial out/call customers from their computers via a desktop based application like Cisco Finesse Agent / CAD (Cisco Agent Desktop) application or any other 3rd party application.As per organizational process the requirement is ...
i want share with you my setup, how i configure TMS 15.6.0 with SQL 2012:
-first of all this deployment design in LAB just for practice, my deployment contain SQL and TMS in same server if you need to install TMS in another server yo...