" /> Identify party that hangs up - GAD 7.6 - Genesys CTI User Forum

Author Topic: Identify party that hangs up - GAD 7.6  (Read 3580 times)

Offline Adam_W

  • Full Member
  • ***
  • Posts: 171
  • Karma: 0
Identify party that hangs up - GAD 7.6
« on: February 28, 2011, 07:04:57 AM »
Advertisement
Hi all

I've been experimenting with ways of identifying whether an agent or caller hangs up at the end of a call and being able to report on this.  There doesn't seem to be any easy way.  From other posts here I see others have struggled with this too.

If the agent uses the GAD I see the RequestReleaseCall but obviously the challenge is how to report on it.  My first thought was to modify the jsp that holds the action for the "Disconnect" button to add some attached data when pressed, but would rather avoid this option as no doubt it is unsupported and/or illegal!

So instead I'm thinking about trying to add a custom listener and applying some attached data when the correct interaction event happens.  I've had some success with attaching data upon EventEstablished. i.e.:

------------------------
//Implement listener....

if (event.getEventReason() == InteractionEvent.EventReason.ESTABLISHED) {

//Apply attached data
------------------------

Hopefully I can do the same when the call is released.  Has anyone else had any experience doing anything like this before?

Which event should I be listening for?  I can try listening for InteractionEvent.EventReason.RELEASED but I'm concerned that it might happen regardless of which party disconnected.

I can try it for myself later of course but I'm hoping I can save myself some time in trial and error if anyone else already knows :)


Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: Identify party that hangs up - GAD 7.6
« Reply #1 on: February 28, 2011, 09:37:53 AM »
Hi Adam,

Monitoring of EventReleased won't help you as you will get it regardless who has released the call. The only option is modification of TReleaseCall request and adding some attached data to this request. Unfortunately, it is unsupported (and probably illegal) modification of GAD as you wrote.

Genesys has added possibility to detect releasing party in T-Server release 8.0 for some switches. I would recommend you checking release notes/documentation of you T-Server and upgrade in case it's supported.

R.