UUI / CTI / VDNs 1

[Zowwie438]

All,

-----------
ENV:
-----------
G3V11 w/ Avaya CTI Server (v1.3) to backend C TSAPI application.

-----------
Setup:
-----------
Vector 1234 adjunct routes a call to CTI after collecting phone number entry from customer and step sequences.

TSAPI application reads input data and routes call back to PBX so it may travel along it's normal route.

CTI App then monitors this call for events such as "answered" and then the rep picks up the phone we PUSH a customer data popup in their direction.

-----------
Don't want:
-----------
Currently with the above setup, the TSAPI app would have to READ the input numbers to see what voice prompt options the customer selected: 1 for customer service, 2 for live rep type thing.

based on 1 and 2 being passed... The TSAPI app would have to know what return vector to route to:
Example:
Vector 4433 routes calls to skill set 33.
If TSAPI app sees 1 and 2, then send back to Vector 4433.

-----------
Wants!
-----------
I wish to keep TSAPI app as abstract as possible. I would like for the originating Vector to TELL me where to send the call to for the next step.

If the switch admin programs their vector to adjunct route call to me with UUI of 4433, then I would know where to send the call to without having to keep any logic on my backend.

-----------
Summary
-----------
Any thoughts or work arounds?

Is there anyway to assign key/value pairs from inside a vector that can be read from a TSAPI app?

 

[Cti4all]

UUI is application set, not set in the PBX. You get collected digits in a different buffer.

CM 2.0 introduces 'Variables in Vectors' in which UUI can be used to define CM variable data in the 96 byte UUI buffer. Primarily this is intended to pass data from a routing app back to the vector. For instance, if 1 selected, and passed to the routing app as collected digits, the app defines that this needs to go to 'sales' and variable 'sales' is defined as 4433 in the CM.

I take it you don't want to be changing the routing application everytime you change vectoring.

I don't believe 1.3 requires any special features for this. UUI can use up to 96 bytes, and in CM you define the variable as being in specific bytes in the UUI. Then when you route response with UUI, you pass the route destination ('Sales') in the UUI along with any other UUI data. CM picks the bytes out that relate to the variable and pull the destination 4433 out of the CM global variable definition.

Now, you decide Sales calls will go to 4434, you simple change the global def of the 'sales' variable in CM and the route response 'sales' goes to 4434.