Author Topic: Transfered Queue Calls  (Read 2959 times)

melliott

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
    • View Profile
    • Email
Transfered Queue Calls
« on: January 09, 2008, 18:47:29 »
Some of our queue calls are transferred back out to another agency. These calls remain active even once the transfer has taken place and the agent hangs up. This of course is affecting the agent/queue stats and SLA's. What can I look for in this situation to resolve?

Thanks!!

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Transfered Queue Calls
« Reply #1 on: January 10, 2008, 10:00:37 »
Very likely you are using attended transfers - unfortunately in Asterisk they do not work for ACD calls. This is  a major annoyance everybody hates....  ;D
Anyway, you should use unattended transfers ( the #) and they will track completion correctly.

See http://lists.digium.com/pipermail/asterisk-users/2006-March/145902.html

melliott

  • Newbie
  • *
  • Posts: 3
  • Karma: 0
    • View Profile
    • Email
Re: Transfered Queue Calls
« Reply #2 on: January 14, 2008, 17:39:28 »
We are required to do these attended xfers to announce the client to the 3rd party, is there anything else we can do?

QueueMetrics

  • Loway
  • Hero Member
  • *
  • Posts: 2999
  • Karma: 39
    • View Profile
    • QueueMetrics
Re: Transfered Queue Calls
« Reply #3 on: January 15, 2008, 15:35:47 »
As a real-life solution, I usually suggest my clients to first make a new call to announce the caller, then hang up and do the unattended transfer. Or do the unattended transfer to a parking space and then open up another call and connect the destination to the parking slot. ;D