Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

 
 
Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
  #1  
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
 

Tags
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 09:05 AM.

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.