CAUTION!! Avaya confirms bug in R2.1
CAUTION!! Avaya confirms bug in R2.1
(OP)
Hey all, just got word that Avaya has confirmed bugs with the huntgroup capabilities of the IPOffice in firmware 2.1.
I have a client that has 9 huntgroups on firmware 2.1 and I've had no end of problems with that site, I will be downgrading them to 2.0 this weekend.
Apparently there is a maintenance patch coming in a couple of weeks that will resolve this - in the meantime, DO NOT use R2.1 if your customer is going to be using huntgroups.
Peter
I have a client that has 9 huntgroups on firmware 2.1 and I've had no end of problems with that site, I will be downgrading them to 2.0 this weekend.
Apparently there is a maintenance patch coming in a couple of weeks that will resolve this - in the meantime, DO NOT use R2.1 if your customer is going to be using huntgroups.
Peter
RE: CAUTION!! Avaya confirms bug in R2.1
RE: CAUTION!! Avaya confirms bug in R2.1
I have seen a problem with overflow groups not ringing in the correct way (rotory group always starting at the 1st extn.), this was reported to Avaya BEFORE V2.1 went on GA
This problem was also present in 2.0 so I would recommend testing Before downgrading
RE: CAUTION!! Avaya confirms bug in R2.1
The short list that I can remember off the top of my head:
1 - Phantom calls in queue that won't go away unless you reboot the switch, are never delivered to agents
2 - Agents becoming available, calls in queue not being delivered to their phone - they must press q-status button (group button)
3 - Agent in queue A is on a call. Agent in queue B sees her q-status button flash, presses it to answer call, and steals the caller away from agent in queue A!
4 - Assisted transfer token within a queued or still queued callflow does not work correctly.
There are more, but I hope the above list is convincing enough to downgrade.
Point 4 is worth expanding on. Do y'all remember in another thread we were discussing a solution I had to get a busy agents phone to beep when a new call arrives in queue, that involved an assisted transfer token? Well, I downgraded my lab 403 (which is running my customers config) to a 2.0 and left my lab VMS (also running customers setup) at 2.1 and Voila! it works like a charm as expected. In other words the problem was with the buggy huntgroups in R2.1 firmware, 2.1 VMPro seems fine.
I'll let y'all know on monday, after I've downgrade this cust, if all problems are resolved as I expect.
Peter
RE: CAUTION!! Avaya confirms bug in R2.1
RE: CAUTION!! Avaya confirms bug in R2.1
Also: the proteus install tries to iinstall SMDR, this does not work with V2.1 & delta server needs to be installed instead, however is smdr is not removed it will fight with delatserver & prevent it from working
delete SMDR from the proteus directory & all will be fine
RE: CAUTION!! Avaya confirms bug in R2.1
http://support.ctidata.co.uk/Download.asp
I know they are on Office 5.0.00.01
If I'm looking at the wrong site, any help would be great.
Thanks.
RE: CAUTION!! Avaya confirms bug in R2.1
It is still necesary to delete SMDR from the proteus instalation & ensure that the SMDR output from Deltaserver is being writen to the correct location
RE: CAUTION!! Avaya confirms bug in R2.1
they have Proteus Office V5.0.00.01 - it doesn't seem from the Proteus updates site like they need any? All the updates are from 2003. Maybe Proteus Ofice works fine with 2.1+ without any updates!
We'll see soon!
Cheers.