I have deleted all voice mailboxes in the voice mail, leaving the general mailboxes. I have added two new boxes and set everything to 3 digit max in the voice mail. I can not transfer direct to voicemail with feature 56 ?????It will not take the 3rd digit.
Are these phantom mailboxes? If so, have you created an adjunct for each on the system so the system will recognize them?
Are the other extensions on the system 2-digit or 3-digit? If they are 2-digit, do these new voicemails conflict with the current 2-digit extensions? x10 would conflict with x100 mailbox as the system would see 10 and start trying to connect.
No phantom mailboxes.There are only 5 phones (as a test) that I have set up. The system has no 2 digit numbers on it and is set for 3 digit. I just has me stumped.
I can dial this ext. I have set up a 5 phone test system. I can call into this system and transfer the caller to the phone x-104 it rings four times and then goes to the correct voicemail. This however is a school and the office wants to trans directly to voice mail so the class is not disturbed.
Since it is such a small system, I would set it back to factory default because there must be something out there causing the issue. Once you do that, under sys renumber, default numbering, make sure you choose "set up space" vs. 3-digit. Then go back and renumber the extensions from 7100 to 100, 7101 to 101, etc. It has to be some sort of conflict out there, but you could waste more time searching for it then just reprogramming it.
What Josh is trying to say is using Feat 56 with or without a button on a MLX-DP digital phone is failing.This is a replacement 007MLM for one that failed.
The existing system is and was 3 digits x100 >>
When F56 is entered the VM responds and says enter Ext #, and it accepts the input of 2 digits of a 3 digit extension, but turkey's on the 3rd digit 10(x)of an actual physical ext. Conversely, 2 digits appear to go nowhere!
The VM was not defaulted, so I was told, before installation, therefore I suspect something got corrupted, or something is hidden.
A transfer to ext. with subsequent cover to VM works correctly for all users. The issue is in the VM on the direct transfer sequence somewhere.
Actually, when F-56 or Direct to VM is pressed, it is the Legend that is responding. It accumulates the digits, then sends the call to the coverage group. If the extension is not in the voicemail coverage group, the Legend will give you wave-off tone. It won't know if the extension is or is not in the group until it gets the last digit (unless you dial something like 2XX when all the extensions in the group are 1XX).
Double check that the VM calling group is the receiver for the coverage group, and that the extensions are in the coverage group.
Tommy, if that were true then the transfer to ext. with coverage to vm would not work, and they do.
As I said earlier, the VM "only" was replaced due to failure, all the Legend programming was basically unchanged.
I work with Tech216, but I havn't had time to go look at this issue, this cropped up after we got everything else working, I already had to slap him up-side the head once this week.
This is a school, and messages are directly transferred to the teachers VM boxes for later recovery, rather than disrupting class with calls, except for an emergency.
Does it happen when transferring from the Auto Attendant?
Does it happen when the Operator (or another user) transfers a caller to an extension?
I can call into this system and transfer the caller to the phone x-104 it rings four times and then goes to the correct voicemail.
Is this a transfer from the Auto Attendant?
If the extension is not in the coverage group, the call will return to the transferring extension, which would be a voice mail port. The voice mail port will answer with the mailbox.
but turkey's on the 3rd digit 10(x)of an actual physical ext.
Remember the turkey tone comes from the Legend, not the voice mail!
Incoming POTS lines ring 771, console (x100) and 9040 Wireless (for Portability) w/delay cover (20 sec) to 770 as 771 AA1 which now works fine. (this is what I had to slap him for).[as Yoda says, Not listening, he was]
Josh calls main # from cell phone, answers @ console and transfers to Ext--rings x104 (or any exists ext. w/vm)4 times then covers to user MB- no problem. GMB 9991 for "0" option is OK too!
Again calls, answers @ console, does D-VM to x104 VMB, it fails, as stated above.
AA1 answers if the operator is away/tied-up/night. The only stated option> GMB, no transfer allowed.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.