Can anyone explain who data actually gets attached to the calls using an IVR behind the switch model?
AJ
Can anyone explain who data actually gets attached to the calls using an IVR behind the switch model?
AJ
Ani and DNIS as basic, then it depends on your swicth and IVR capabilities.
More specifically, what applications and process come into play when attaching/associating the call and data?
AJ
uh?
PBx receives the call and gets ANI and DNIS, then if using a CTI as Genesys it can attach more info (TServer) then your IVR can read and attach more data.
Hi,
The involved applications/processes are: IVR driver —> IVR TServer —> TServer
R.
Maybe the better question was how does TServer manage attached data, configure it: how can you create kvp, where could you capture the data for update.
AJ
If you’re referring to the call flow, you could attach it almost anywhere you like:
It really depends on what data you want to attach, and how you are going to use it once it is attached.
you can configure the attach data value-pairs using genesys CME.
after then, you can manage to parse and update the configured attach data fields within your appl. code
Ok,
I think you are asking how do you attach data using IVR and how is it passed on to Genesys T-Server! ;D
While many people will tell you a quick fix you can do using UUI_DATA, usually you need a connection from IVR to T-Server. This connection is offered by Genesys IVR Server, which provides an adapter to your IVR to use. Once you implement that adapter, from IVR GUI you can call on a new function, that will allow you to:
Genesys IVR server then passes that information to T-Server, and that attach data is then assigned to the call that your IVR is currently handling. After IVR sends the call to a VDN or an agent, connection id for that call is still the same, so attach data assigned to that connection ID is still inside T-Server, so it is passed along with the call to the next DN until you either delete it or the call is released.
Makes sense?
Vic