cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
398
Views
0
Helpful
2
Replies

Attendant Console Queue has an issue with Calls from particular gtw

jcornish
Level 4
Level 4

My customer is having an issue with calls coming into a particular branch and being delivered to an Attendant Console Queue.  Calls come into a Cisco  4321 voice gateway (Version 15.4(3)S7, RELEASE SOFTWARE (fc3)) via ISDN and delivered to CUCM (Version 11.5), which translates the called number to a UCCX (version: 11.6.2.10000-38 (ES08-13)) trigger.  Within the script, it provides an option to press "0" which sends the caller to Attendant Console (Version: 11.0.2.20-11)

Up until last Monday morning, everything worked fine.  In the afternoon it was noticed that calls into the QBY queue would hang.  None of the receptionists are able to pick up the calls. They double click on the call in the AC, and it just does nothing. The call never transfers to their phone, it just sits in the queue ringing at their computer.  On the caller side, Silence on their end, call took ~5 seconds to even start ringing at the AC, receptionist unable to pick up.

Rebooted the two AC servers and the QBY gateway...no joy.  Resynched all of the CTI ports...no joy

Redirecting calls coming into the QBY gateway to another queue duplicates the issue.  Calls from another gateway into the QBY AC queue - no issue.

No overt changes have been made to any components and I cannot explain why the solution has worked for years, then suddenly stopped working for only one queue.

Can someone assist and point me in the right direction?

2 Replies 2

Jonathan Schulenberg
Hall of Fame
Hall of Fame

Are the calls arriving as G.711? Is there an MTP or transcoder getting invoked?

If yes and no, respectively, it’s likely a CSS issue. CTI redirects - which both CCX and CUAC perform - can get tricky. Does every CSS involved in the call path including the gateway’s incoming CSS have access to the receptionist DN?

Yes, all calls are g.711 and no, MTP or transcoder are not involved.  Yes, every CSS in the call path has access to the receptionist DN.  It is weird because this was working for the longest time, then it stopped...Only the one branch out of 8, and they are all configured the same.

Strangely, the call does appear in the QBY queue, but the receptionist cannot pick up the call or move the call and the call continues to ring.