Jump to content
Posted 02 September 2015 - 09:38 AM
Posted 03 September 2015 - 04:05 PM
Since upgrading from 3.0.006.046 to 3.1.001.028 last night, we have two new issues:
Posted 03 September 2015 - 04:07 PM
We are actively working on both issues right now. I apologize that these got by us. We'll have them cleared up as soon as possible.
Posted 03 September 2015 - 04:19 PM
Thanks to everyone for responding quickly to these issues.
Posted 03 September 2015 - 07:54 PM
Have a big roll out tomorrow morning and notice that 3.1 is available.
Any other issues being seen out in the wild?
Posted 08 September 2015 - 01:02 PM
The first issue I previously mentioned with the queue call answer button is causing some workflow issues for our call takers and I am hoping that it gets a fix very soon.
Also, the link from the BPS interface in Configuration -> Updates is broken (http://updates.cudasvc.com/cgi-bin/view_release_notes.cgi?type=bpsware&platform=2&version=3.1.001.028) = "Release Notes for Cudatel Phone System firmware (version 3.1.001.028) are not available at this time"
There is also an issue that many users are having with the new Communication Command Center losing connectivity. It seems the reference to the phone extension gets lost. Then changing queue status sometimes results in an error in the CCC window: "There was an internal error processing your request". I called in to open a ticket on this issue.
I have gotten reports this morning that when the call taker is ready to hang up on some extensions, the phone randomly freezes up and becomes completely unresponsive and requires a manual phone power cycle reboot. One user stated that it has happened three times on her phone this morning. I am collecting more information. It could be unrelated to the firmware change, but I haven't ruled it out yet.
Posted 08 September 2015 - 02:25 PM
I see the bug that Gary filed for that CCC issue. Is this something you are able to reproduce? We have not seen this in our lab so if your users are running into this we'd like to know the steps that cause it.
Posted 08 September 2015 - 02:48 PM
I'd really like to know the steps that cause it too! ;-) I haven't figured it out yet. I'm keeping my eyes opened, though. Hopefully, we'll catch on to a pattern soon.
Posted 08 September 2015 - 02:50 PM
Thanks for bringing it to our attention regardless. We'll be on the lookout for it.
Posted 10 September 2015 - 12:50 PM
So I was able to catch the "There was an internal error processing your request" issue in the CCC on one user's computer and checked the Chrome dev tools. It showed:
Hopefully this is enough information for you to be able to reproduce the issue. You will probably have to leave the CCC open for quite a while before seeing this behavior.