Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Thread Tools Search this Thread Display Modes
Old 11-14-2013, 11:23 AM
kenkumpula kenkumpula is offline
Aspiring Member
Join Date: Feb 2012
Posts: 2
kenkumpula has 10 reputation points
Default Ghost Calls

For the purposes of this documentation I have defined a “ghost call” as a call that was delivered to an agent logged into Avaya OneX (VCC Desktop), CTI information appears for the call, and where the agent was not hearing any audio from the caller.

Based upon comments left by callers where they indicated they dialed one of our toll free numbers, took a prompt, said “yes” to the survey, never spoke to an agent, and were delivered to the survey.

1.Validated that all of the Avaya PBX (ACM-5.2.1) vectors had the appropriate first 2 steps in call flow (i.e. wait 0 seconds hearing music, wait 2 seconds hearing ringback) – required for SIP.
2.Verified via testing that the “allow VDN override” field did not impact this issue.
3.We have validated numerous calls via ICM query that the calls were in fact delivered to the agent in question; and that the ACD talk time is typically less than 10-15 seconds.
4.This is also confirmed by the documentation in the UES Survey portal that actually tags the agent with the call where caller left message saying they never spoke to an agent.

It should be noted that although the “incoming” toll free number call is SIP, when the call is routed to West gateway for them to take call control, it is then TDM and remains TDM. Our infrastructure no longer does quality monitoring (Qfiniti) on TDM trunks.
5.MST trace has been activated on numerous occasions, and we have been able to duplicate a “no audio/ghost call” and provide the pertinent information to AVAYA; but per AVAYA it always looks like a good call.
6.We have also made test calls ourselves using hammer; 1 out of 62 calls resulted in a “no audio/ghost call”;– no significant results.
7.We have engaged our survey (3rd party) vendor and provided them with our ICM query data requesting feedback on certain criteria (i.e. data center (Omaha vs. Denver); RTN/APN, IVR port number, did they see (DTMF) #9 (where caller was trying to route to survey themselves) along with some of their call recordings. Results from the survey vendor did not provide any significant information.
8.Placed test calls (in production environment) and requested that agent transfer our call using the “91” method (which is NOT the approved method of transfer); call was successful (two-way audio) to agent #2.
9.As we have both in-office agents and work-at home (some who use IP Softphone; others may still be using Work At Home Kits) it does not appear to be isolated to any one particular configuration.

I am hoping there is someone else out there who has been done this road.
Reply With Quote
Old 03-26-2014, 09:08 AM
vpatel1 vpatel1 is offline
Aspiring Member
Join Date: Mar 2014
Posts: 1
vpatel1 has 10 reputation points
Default ghost call dead air

Hi kenkumpula,

I was just wondering if you ever found a solution to this. We're going through the same issue with no leads in sight after months of troubleshooting.

Any help will be appreciated.
Reply With Quote
Old 03-26-2014, 02:50 PM
ebyh ebyh is offline
Hot Shot
Join Date: Dec 2012
Posts: 12
ebyh has 13 reputation pointsebyh has 13 reputation points
Default ghost call dead air

Ah, this reminds me of a similar REALLY frustrating problem I experienced years ago. For weeks we were tearing our hair out. Check your VDN programming. Any chance you have an extension populating the Return Destination field?

I had mistaken that field for RONA which is something different entirely.

The Return Destination kicks in if the agent disconnects *before* the caller does. If your Return Destination is set to route a call back to the agent queue, your system will keep it alive for a while as an active call, continuously cycling through the contact center even though by now the original party has disconnected! It was the worst.

If your agents are transferring callers to a survey, but hang up before the transfer is fully completed, maybe this could be the issue?

It's a long shot, but maybe.
Fortunately if this happens to be the problem, it's an easy fix.
Reply With Quote
Old 03-11-2015, 10:21 AM
carterbury carterbury is offline
Aspiring Member
Join Date: Mar 2015
Posts: 1
carterbury has 10 reputation points

Did anyone ever figure out this issue? I have the same problem in my environment. We also use the return destination to go to a survey. Our call recordings reflect these ghost/dead air calls. Our csr's are either heard repeating their greeting or there is absolutely nothing but a few clicks.
Reply With Quote
Old 03-11-2015, 10:49 AM
ebyh ebyh is offline
Hot Shot
Join Date: Dec 2012
Posts: 12
ebyh has 13 reputation pointsebyh has 13 reputation points

Unfortunately I think this is one of the risks of using the Return feature. If the caller hangs up but your server doesn't complete the disconnect, your agents will hear dead air.

You might consider adding a step... Return to a VDN tied to a vector which then collects digits after an announcement. Callers could be encouraged to opt-in to the survey by pressing 1 (or whatever). Then only route those calls to the agent queue. No response or any other digits could instead play a "thank you for calling xyz company; goodbye" and then disconnect.

I hope maybe this helps. Best wishes!
Reply With Quote
Old 08-05-2019, 09:41 AM
kumpuk kumpuk is offline
Aspiring Member
Join Date: Jun 2018
Posts: 2
kumpuk has 10 reputation points

It is 2019---- and these things still happen. I have moved to a new company, still using Avaya ACM, and still end up with Ghost calls. I would blame myself, but the issue was here before I arrived (phew). Calls come in, the agent "sees" the call for a split second and the call heads off to survey. This occurs randomly and seems to have no pattern on VDN/Vector or trunk group.
Reply With Quote
Old 08-05-2019, 01:57 PM
hurdk hurdk is offline
Join Date: Oct 2015
Posts: 67
hurdk has 11 reputation points

I am curious to know if you validated voip resources. Are you processing the calls thru a cabinet/media gateway? have you verified the correct ip-codec, etc? I get that the calls is getting to a TDM endpoint but are you verifying the ip portion is correct up to handoff to the TDM?
Reply With Quote

ghost call dead air

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 08:02 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.