Unable to transfer to any extension with AA

[coladmin]

I am getting an "invalid entry" error from the auto attendant when I try to transfer to any extension. All extension are in group 30 and have been added to the config via the Merlin Messaging software. Any thoughts would be greatly appreciated

Magix Version 3.0
Messaging Version 3.0

 

[merlinman]

Digit Lenth ?

Email Me and we can discuss....

merlinman@comcast.net

 

[Stengrad]

Make sure you set all the VM ports (extensions) with rotary enabled. Also make sure there is a mailbox created ofr each of the extensions in question.

Field Technician
Virginia Integrated Communications

Http://www.vicom-corp.com

 

[coladmin]

I checked the port earlier and made sure that they are rotary enabled and the digit length is 4 digits. as soon as I press the first number
I get the invaild entry error

 

[t3chhelp]

selector code assignment on AA?

 

[jinxs]

Transfer restrictions on?

 

[coladmin]

the selector codes are at factory default 1-4 are direct extension transfer and 5-9 are unused. currently I have the transfer rectrictions on and it does not work I had turned them off and i still got the same error

 

[killbox]

1. All ext.'s are in group 30 and you've created Mailboxes for all of them?
2. Hunt type is linear and all VM port are in rotary enable?
3. Day and night, you're selector codes are set and your digit length is set. 4 digits if using for or 3 if using 3, etc.?
4. Did you configure the messaging or did you do the auto config merlin messaging??
Usually this happens if the ports aren't rotary enabled though.

KILLBOX

 

[coladmin]

1.all extensions are in group 30 and I have created a mailbox for them
2. the hunt type is linear and all vm ports are rotary enabled
3.I have not changed the slector codes at all and the system is set up for 4 digits
4. I used auto config and then renumbered the vm group to meet my dial plan

and other thougts. the strange thing is that I get the error as soon and I press and number in

 

[killbox]

What happens if you press *8 and then the ext. # at the auto attendant? If it let's you do it with *8, I'd default the VM and start again with the auto config.

KILLBOX

 

[coladmin]

killbox

if I *8 everyting works fine. I rebuilt the system last night and then I autoconfiged MM and I still got the same issue. I wonder if this is a bug in the 3.0 release?

 

[killbox]

Did you default the VM though???

Maybe try and take them out of rotary enable?? See what happens? Maybe the processor is doing something flakey? I haven't had this problem on 3.0 and I have a ton of them out there. Do you have another VM?? If you do, try and program it in house and then swap it out and see what happens. Then you can really narrow down it's not the VM.
Try and reprogram the selector codes again. Don't leave them default. Do them in the Day and Night and in the proper tenant obviously.

If all this doesn't work, I'd do a board renumber and then try. I've had a couple misc. problems on 3.0 and it fixed. go figure.

KILLBOX

 

[coladmin]

after taking the extensions out of rotary enable for the second time it worked

thanks!

 

[killbox]

No problem

KILLBOX