Author Topic: Agent Client processing EventReleased on 1st Party Hangup  (Read 2516 times)

Offline Kevin S

  • Full Member
  • ***
  • Posts: 145
  • Karma: 4
Agent Client processing EventReleased on 1st Party Hangup
« on: June 09, 2010, 03:12:43 AM »
Hello all.

I have a question that hopefully someone can provide guidance on.

We have an Agent Client that was developed for us many moons ago (the vendor is now out of business) and we are trying to make a few corrections to the application.

One I have not been able to work through is the following:
1. Party A calls Agent B (Inbound call)
2. Agent B begins conference with Agent C
3. Party A hangs up while Agent B is still on Consult Leg with Agent C
4. Agent Client recognizes EventReleased from Party A and places application into ACW routine, then sets Agent B in a ready state (even though call between B and C is still active).

How can I check to see if the consult leg is still active, and bypass the ACW routine if the leg is still active?

We're using VB6.

Offline Fra

  • Hero Member
  • *****
  • Posts: 853
  • Karma: -4
Re: Agent Client processing EventReleased on 1st Party Hangup
« Reply #1 on: June 30, 2010, 05:23:29 PM »
From a Stat Server perspective, with an ongoing call on the agent's place, the status will not be Ready anyway.

Fra

Offline imaki

  • Jr. Member
  • **
  • Posts: 51
  • Karma: 0
Re: Agent Client processing EventReleased on 1st Party Hangup
« Reply #2 on: July 02, 2010, 04:04:07 PM »
Hello all.

I have a question that hopefully someone can provide guidance on.

We have an Agent Client that was developed for us many moons ago (the vendor is now out of business) and we are trying to make a few corrections to the application.

One I have not been able to work through is the following:
1. Party A calls Agent B (Inbound call)
2. Agent B begins conference with Agent C
3. Party A hangs up while Agent B is still on Consult Leg with Agent C
4. Agent Client recognizes EventReleased from Party A and places application into ACW routine, then sets Agent B in a ready state (even though call between B and C is still active).

How can I check to see if the consult leg is still active, and bypass the ACW routine if the leg is still active?

We're using VB6.

Best way is to make the client such as it does remember the calls it has ongoing. You can use the genesys eventmodels to create proper handling.
But there should be a command (you did not tell which sdk you use), to get addressinfo from tserver (TQueryAddress in tlib), within the corresponding event you can find info about the status and calls of the dn.