Attendant Console Forward incomming Calls

[dtisa]

Well, I have setup a Definity g3si which includes 30 users with Octel voice mail integration, everything looking good but the attendant features. When a call comes in, it is forward to the Attendant console. My issue is that the console cannot forward the call after rings 3 to go to voice mail, like a regular extension. Any suggestions?

 

[4merAvaya]

Use Nite Service. Add a nite service button to the console. On the Main Listed Number form define the night station. Add a coverage path for that station. When the attendant activates night service the incoming calls will go to that station and cover to voice mail.

Kevin

 

[Bobg1]

If you are refering to having the attd in the coverage path for a station, you can also give the attendant a regular extension number, then use that number in the coverage path, this way the coverage call gets regular station treatment and not hung in the attd que.

 

[avayaman]

What release is your Switch? If it is rls 8.5 + I can tell you how to do it using Attendant Vectoring. You can also do it by using ACD, but this usually brings up the problem of not being able to answer one attendant call, put it on hold & pick up another.

You can also accomplish it, depending on your configuration, by changing zero to a hunt group access code. You then redefine a 2 digit local somewhere (eg 20) as attd. You point your incoming trunks to zero and set up the hunt group (non vectoring, non acd) with a coverage path that has the first point of coverage as attd and the second point as the extension you want overflow calls to end up at. You leave the members of the hunt group as blank. This will gather up dial zero calls as well. In this scenario you may have to assign a hunt-ns key to the console on this group to handle the destination of dial zero after hours as they will not follow the night destination of the LDN form, because they have arrived at the console via coverage. It may also be desirable to eliminate system wide coverage tone in the system parameters coverage form. Incoming trunk calls will not hear cover tone, but dial zero's will. If you have Attendant Vectoring, its a lot easier. Paul Beddows
Avaya Implementation
Telus
Vancouver, Canada
E-mail via

http://www.vancouver.hm/email.html

 

[dtisa]

Thanks all for the help. I'm running R6 and I did setup the night-serv feature. Now the calls are comming from the co and on the CHANGE TRUNK # I have an extension 8500 for the console. On this scenario what is the best way to allow it to ring on the console 3 times and then go to voice mail?

Thanks again

 

[avayaman]

I don't think you can do it that way. A call to the console extension number will not forward or cover or follow the LDN night destination. Paul Beddows
Avaya Implementation
Telus
Vancouver, Canada
E-mail via

http://www.vancouver.hm/email.html

 

[avayaman]

Further to the message above, you might try establishing an X-port, create a coverage path with the "all Prompts" set to yes. First point attd, second point your voice mail hunt group. Establish a mailbox with the X port Id and put an aut-msg-wt key for it on the console. In the System Parameters coverage form you have to set "Local coverage subsequent redirection no answer" to the number of rings you want (System wide). I think this will probably work for incoming trunk calls, it won't for dial zero calls. You might have to put a "y" in the "no Answer" columns of the coverage path, despite having the all prompts set to yes, in order for the coverage on no answer at the second point to work. I can try it out in our lab for you if you don't want to try it on a working switch. Paul Beddows
Avaya Implementation
Telus
Vancouver, Canada
E-mail via

http://www.vancouver.hm/email.html

 

[Bobg1]

If the attd console has an ext number and you use that number in a coverage path rather than "attd" the call being covered will remain following the coverage path and not get caught in the attendant que.