CUEAC-Unable to hear the continuous ring, it just rings once and stops.

[giftonabel]

I have configured the CUEAC server and below are the details of it:

CUEAC Administration Version: 3.1.1.133

CUEAC Console Version: 3.1.1.511

When we get a call on the console, it rings only once instead of continuously ringing, even if the call is on the queue and not answered.(The problem is Intermmitent, sometimes if we close and login again it rings continuously for the first time, then again the same problem continues)

Tried checking with other systems also, the problem remains the same.

I tried doing the Ring settings on the Console ->Preferences, but still no progress.

Pls. suggest if anything more needs to be done.

rgds,

Gifton

[marcusdewaal]

I have the same issue, did you find a solution?

Regards,

Marcus

[Rob Huffman · Accepted solution]

Hi Marcus,

It sounds like this bug

CSCtc84599 Bug Details	Bug #1 of 2 | < Previous            | Next >

Operator console rings only once for incoming calls

Symptom: Operator console rings only once for incoming calls Conditions: After upgrading to CUBAC 3.1.1.5, only the first call to the operator console will ring through the speakers until the operator picks up. All subsequent calls will ring through the speakers only once although the call still shows as being in queue. Call handling is still working, but when you have more agents the other agents may not realize that there is calls waiting in queue. Restarting the client console will allow the first call to work as above, but all subsequent calls will fail, so not really feasable as a workaround. Workaround: None Further Information The above issue is also seen in CUEAC 3.1.1.5.

Status Fixed              Severity         1 - catastrophic Last Modified In Last 3 Days         Product Cisco Unified Attendant Consoles          Technology 1st Found-In 3.1(1.5)                    Fixed-In Release-Pending

Hope this helps!

Rob

Please support CSC Helps Haiti

https://supportforums.cisco.com/docs/DOC-8895

https://supportforums.cisco.com/docs/DOC-8727

[jamgale]

This was indeed a bug, it has now been fixed.