mx controler 5.2.4.4. Auto attendant

[deanmulley]

Strange prob...!

I have a 40 user mx conroler with 5.2.4.4 software with an en beded auto attendant.
there are three options
1=sales that rings a key on some phones with multicall for 601
2=tech services rings as above multical 602
3=admin rings as above multicall 603
0=operator rings as above to muticall 0

aftre 15 sec the calls re route to first alternate and go to a mail box that is the same as the mutical key,all extentions have a key for message notification to the relevent mail box,when they hit said key it takes them straight to the mail box and they can pick up the messages.

the prob i have is this messages in the operator mail box 0 dont always light the notification key and if and when it does when the messages are read and removed the light dont always go out,also the message notification key doent take you to the mail box it goes to the start of the auto attendant,so you have to get messages by keying * mail box id/p/w....ext.
this set up works fine for all the other multicall nubers just not the operator mail box 0


any ideas......?

 

[MitelInMyBlood]

Do you have any digit conflicts with "0" ? Example, is zero a leading digit in your ARS table? Any extensions that begin with "0" ? Any feature-access codes with a leading zero? How about system speed call entries? Etc..

 

[deanmulley]

nope no conflicts that i can see

 

[MitelInMyBlood]

Try this; Program up a set and assign it in the VM hunt group. Make its COS exactly the same as one of your msg wtg ports. Now try to manually send (from the keypad) the VM Msg Wtg on/off commands to ext. 0. Example, our msg wtg FACs are *42 to enable and #42 to disable. So to test I would send *420 and #420.

If there are *NO* conflicts you should get confirmation tone back **immediately** upon sending the codes. If there is a digit conflict, confirmation tone will be delayed by the amount of time set in the interdigit timer for the COS.

Simpler yet, just dial '0' from any ext. If there are no digit 0 conflicts ext 0 should begin ringing immediately, within 1/2 second or less.

 

[TheMitelGuy]

why not just change 0 to ring to a multicall 604 or 600? I think the problem is the VM - which may not like the single digit extension (I could be wrong). I would change your dial 0 point to something more similar to that of your system dialing plan (i.e. 3 digit extensions). Try it and see what happens. You can always map 0 to 600 or 604.

 

[deanmulley]

Thanks for all your help guys....ive since spoke with mitel tech and although they didnt give me a straight answer as to why i cant ,they have said that i shouldnt use 0 (operator mail box) in this way,granted it doesnt work and i can set it up with a different directory number but what i was after was an answer to is there anything special with the 0 mail box to why it wont work in this way....