Definity Console calls waiting issue

[rerictruax]

I have a Definity 9.5 with a 302c console. I am routing calls to the console via two different hunt groups that are for the two different companies.I set up a cover path with settings that has the console first then VM. The problem I am having is that when the operator is on a call the next call does not ring her next button i.e.. b, c, d it flashes tha call waiting light for to get off the button that she is on. How can I change it to go to the next available button. Thanks

http://www.rettelecom.com

One Geek Changing the World
One solution at a time

 

[orypecos]

I have never seen a attendant console set up to work that way, so I don't think it is possible. Going to the next appearance is a feature of regular non console phones.

 

[rjblanch]

You are stuck, we have the same scenerio for our office. Basically the hunt groups can only go to 1 line apperance and as such, that is button "a". The other calls will never go to the "b", "c" etc buttons.

The only calls that will go to these line apperances is internal calls.

We did try it a number of ways, but unfortuantely there is no way really around it....Unless you really want to program something where you have an "is agent available?" step in a vector to route to attendant and then check the secondary skill to ensure that the calls there havent been waiting longer. (See why we have left it alone!!!!)

 

[phonesrus]

If you wish to have the calls que up to the console, create a new "listed directory number" for each of the companies and put those numbers as the first point under the coverage path, put the voice mail as the second point if you have an auto-attd to answer.This will create an issue for night destination, since without tenant permissions you cannot create different night destinations for more than one company, unless you have no night destination defined. But you could create an additional auto-attd to allow a selection.
Regarding the console, only one call can be processed at a time. You can answer calls ringing to the console and place them on hold on successive loop buttons "b-c-d etc." and then go back and process them in the order received, but they will not drop to loop buttons they will only continue to que and ring.The console is a unique entity in an Avaya switch, it acts differently and can do things no other phone can perform.
Sounds like you need to go to support.avaya.com and download the Attd user guides for your switch release.