Recent content by nulabeacon

you should be able to set up and use a CWR button ( call waiting ringer ) toggling this should solve the problem.

It's not so much about the Definty as thgese phones will work on G, Si's Cs and Call Managers , it is however more about the version of software that the Avaya CM is running , these are by far legacy phones. You can run some phones in alias mode, but you would have to check if this is possible.

Have you checked the public or private uknown , these need to include the 6XXX numbers or range.It is likely to be either one of the these two , think I have seen this before.

Is the unanswered transfer timer shorter than the coverpath time on the hunt group to voicemail, this may account for it and why the internal call works.

I am not sure this would be possible as the call-appearance keys on a console are fixed and not programmable in the same way as standard phones. calls will always be presented on call-appearnce key A first if available.

How are they connected , if you mean 3 groups via an external pagin system , you can busy and release them via admin and status to see if they are avaible. A little more inforamtion plz

You could try changing 0 on the dialplan to a virtual extension and using a cover path to send it to the correct 302 console extension number as alternative, you would have to determine if 0 call prioritiztion is important though and what you want to happen if the console is not attended or in...

3 issues I can see here potentially. 1. If the extension has an auto-attendant voicemail, you should be able to decrease the amount of time the AA waits for digits to be pressed this is usually a few seconds default. 2.Is the extension that the press 1 digit is set for a real extension, if so...

There is both a day and night destination within the " change-Incoming trunk " fields. If you place a destination in here , the night service key will activate it.

forgot to mention , it possible to set how many calls are queueing before notification or prirority notification occurs .

The principle is the same , no matter what console you have. Even though there are multiple call appearance keys, the first answered call appears on call-appearance key A. The any further callsare queued to the console via the attd-queue call button and attd-queue timer button. The extra call...

How about just using the tac code to access the trunk . Or if you wish to check the ars , using the partiton route table via cor and chaing the cor on a local extension to you . I am sure that you must have ars setup already locally for them to dial using thier own trunks.

The attendant call-queue can be set on the CM to work/ring straight away , I think te default is 1 call , which would mean it doesn't sound out until there are 2 calls in the queue. Even though the CW-Ringer may not be visible on the console itself( as you can change the Button-name) it is...

If you have proved the integration works , by incoming calls reaching the voicemail and hearing the users greeting correclty and the issue is only when you are trying to access .If so you can program the voicemail access button to include just a # or indeed the #password# to drop the user...

If it comes up with the main system prompt and not the extension number/name or personal greeting then there is an integration issue. Usually ths is down to either public unknown or the private uknown tables not having the extensionleading digit and length inserted.