Call Reporting Issue - Auto Attendant to Queue

%3CLINGO-SUB%20id%3D%22lingo-sub-65483%22%20slang%3D%22en-US%22%3ECall%20Reporting%20Issue%20-%20Auto%20Attendant%20to%20Queue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-65483%22%20slang%3D%22en-US%22%3E%3CP%3ENot%20sure%20if%20this%20has%20already%20come%20up%2C%20I%20have%20not%20seen%20this%20specific%20issue%20on%20the%20site%20myself.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20identified%20a%20slight%20issue%20with%20the%20PSTN%20report%20for%20the%20Cloud%20PBX%20solution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EThe%20scenario%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3ECall%20an%20auto%20attendant%20number%3C%2FP%3E%3CP%3Eselect%20an%20option%20which%20then%20goes%20to%20a%20queue%3C%2FP%3E%3CP%3EOne%20of%20the%20users%20on%20the%20queue%20answers%20the%20call%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERun%20the%20report%20some%20time%20later%20and%20it%20will%20show%20the%20inbound%20call%20details%2C%20however%20it%20does%20not%20report%20who%20answered%20the%20call%20and%20instead%20just%20reports%20%3CNO%20data%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2F%22%3E%3C%2FNO%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAttached%20is%20an%20example%20of%20this%20(phone%20numbers%20removed)%2C%20I%20assume%20this%20is%20an%20issue%20that%20could%20be%20resolved%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F13859iAD5FEFE80ECC45C3%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22call%20report.png%22%20title%3D%22call%20report.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-65483%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMonitoring%20%26amp%3B%20Reporting%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPSTN%20Calling%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215392%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Reporting%20Issue%20-%20Auto%20Attendant%20to%20Queue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215392%22%20slang%3D%22en-US%22%3E%3CP%3EI%20raised%20a%20support%20request.%20And%20they%20said%20that%20it's%20intentional.%20There%20are%20no%20development%20plans%20to%20correct%20the%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFuming%20is%20an%20understatement.%20How%20on%20earth%20are%20we%20meant%20to%20track%20calls%3F!%3F!%3F!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207880%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Reporting%20Issue%20-%20Auto%20Attendant%20to%20Queue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207880%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20experiencing%20it%20again%20now%20so%20have%20also%20raised%20a%20support%20ticket.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnly%20seems%20to%20be%20where%20we%20have%20calls%20coming%20into%20service%20numbers%20that%20then%20go%20to%20call%20queues%20it%20then%20shows%20no%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20really%20any%20help%20as%20we%20need%20to%20be%20able%20to%20report%20on%20the%20call%20queues%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206898%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Reporting%20Issue%20-%20Auto%20Attendant%20to%20Queue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206898%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20opened%20a%20support%20ticket%20about%20this.%20It's%20happening%20to%20us%20too.%20And%20we%20can't%20report%20on%20calls.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-153273%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Reporting%20Issue%20-%20Auto%20Attendant%20to%20Queue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-153273%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20was%20an%20issue%20with%20the%20service%2C%20they%20managed%20to%20resolve%20it%20after%20it%20was%20raised%20as%20a%20service%20health%20issue.%26nbsp%3B%20It%20did%20occur%20again%20recently%20again%20with%20a%20service%20health%20notification.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-150509%22%20slang%3D%22en-US%22%3ERe%3A%20Call%20Reporting%20Issue%20-%20Auto%20Attendant%20to%20Queue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-150509%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20ever%20find%20a%20resolution%20to%20this%20issue%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Frequent Contributor

Not sure if this has already come up, I have not seen this specific issue on the site myself.

 

I have identified a slight issue with the PSTN report for the Cloud PBX solution.

 

The scenario

Call an auto attendant number

select an option which then goes to a queue

One of the users on the queue answers the call

 

Run the report some time later and it will show the inbound call details, however it does not report who answered the call and instead just reports <No Data>

 

Attached is an example of this (phone numbers removed), I assume this is an issue that could be resolved?

 

call report.png

5 Replies

Did you ever find a resolution to this issue? 

It was an issue with the service, they managed to resolve it after it was raised as a service health issue.  It did occur again recently again with a service health notification.

I have opened a support ticket about this. It's happening to us too. And we can't report on calls.

We are experiencing it again now so have also raised a support ticket.

 

Only seems to be where we have calls coming into service numbers that then go to call queues it then shows no data.

 

Not really any help as we need to be able to report on the call queues 

I raised a support request. And they said that it's intentional. There are no development plans to correct the issue.

 

Fuming is an understatement. How on earth are we meant to track calls?!?!?!