Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

CAUTION!! Avaya confirms bug in R2.1

CAUTION!! Avaya confirms bug in R2.1

CAUTION!! Avaya confirms bug in R2.1

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.


RE: CAUTION!! Avaya confirms bug in R2.1

use hunt groups in what sense? Or when you have more than 9 hunt groups?

RE: CAUTION!! Avaya confirms bug in R2.1

Exact details of the problems would be usefull so that we can work around them.

 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

Remember the site I mentioned that was FUBAR'd in another thread?  Well, this is the client, and 2.1 is the cause.

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.


RE: CAUTION!! Avaya confirms bug in R2.1

I remember people saying Proteus doesn't work with 2.1 - is that still the case or has a patch come out?

RE: CAUTION!! Avaya confirms bug in R2.1

Proteus Now works with V2.1 just make sure that the correct patches are downloaded from th proteus web site.

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

sorry for the silly question - but I have not used Proteus before. I have just gone to the website, but it doesn't seem as if these are the patches you talk about:-


I know they are on Office

If I'm looking at the wrong site, any help would be great.


RE: CAUTION!! Avaya confirms bug in R2.1

They are the correct downloads - at least as far as the V4 deltaserver goes I have not yet tried with V5

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

yeh that's no problem - they will be using Delta Server v4.0.29 and I'll make sure they use the correct output.

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!


Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close