messaging outcall notification problem 1

[telgeek1]

I upgraded a customer to a magix processor and merlin messagin. they are in key mode. i went into admin and gave each mailbox the ability to have outcalling notification. inside user mailbox ive got outcalling to a phone selected and have tried the # to dial with a 9, without a 9, with pauses etc.. ive made sure the voice mail ports are not restricted. ive even went into cntr programming and set auto line selection to start at the last line and work its way to first line for those ports. i leave a test message and can see the voicemail port access the line but then hangs up after just a sec and never dials.

theres two backplanes.
the first; the proccessor, 3-o16 mlx cards, 1-012 w/ ring gen and ttr, and the 6 port messaging.
the second; 3-800 loop start, and i added a 400 gs/ls/ttr for more touch tones.

not the way i would have configured it with the ext first and trunks last but inherited it this way.

ive tested the touch tones from an analog port on the 012 card with the 04,+2digits,+123456789*0# code and get a double tone confirmation. in my notes i have it should be a triple tone confirmation but its been a minute since i trouble shot this far into a legend.

What am I missing? appreciate any help. usually don't post unless i'm stumped... Thanks

 

[Telecomboy]

If you have auto line selected the lines for the voicemail ports, then you don't need the 9. If the port is being accessed and then hangs up, chances are there is still an issue with the dialing out. If you have auto line select picking a line a don't have a 9, that leaves restrictions. I know you say you unrestricted them, you should also check to make sure those extensions are not apart of a disallowed list.

 

[TouchToneTommy]

Did you try 9 - PAUSE (*) - and then the outside number?

Since it's not ARS, you must pause for dial tone to connect and be ready to accept your outcalling digits.

 

[telgeek1]

i am having laptop issues so was not able to connect with winspm and print ext info on voicemail ports. so maybe thats what i need to do to checkout dissallow lists. I am correct tommy that in key mode there is no ars table, so without auto line select the ports grab intercom voice and a 9 takes them to an assigned line programmed to appear on that extension. then obviously a pause or two. any other light bulbs pop up i'd appreciate it.

 

[telgeek1]

still don't understand why its disconnected after seizing a line. if it was restricted or apart of dissallow list wouldn't it have redirect tone for a minute?

 

[Telecomboy]

I have had Messaging systems that required up to 4 pauses before it would outcall properly. So, if you are dialing 9, try putting some extra pauses in there.

 

[telgeek1]

just an fyi for future. i finally fixed it by replacing the messaging module and licensing card. cost me about 750.00 on refurb market. then the old messaging had confused the processor some how because the processor was trying to talk to the new module the same as the old. had to default processor and program from scratch... needlees to say this is last magix upgrade ill probably quote. Cards are getting to expensive and Avaya seems to Have Office IP bugs worked out.
thanks for replies

 

[Telecomboy]

If it saw it as the old module, you could have done a board renumber through Winspm. The processor will then go and check the modules attached and "renumber" itself with any changes that have been made.

 

[Dexman]

Agreed with Telecomboy. When a module is replaced in a Legend or Magix carrier, it is good practice to execute a board renumber.

I "FEATURE 00

 

[merlinman]

If the problem was the Messaging, I doubt the Port card was a problem at all.

I would have started by doing an ERASE on the messaging, and then use the "Config Merlin Messaging" feature of the Magix System Programing (System) to program the Voice Mail.

It takes about 3 minutes and the results are always GREAT!

It uses EXTENSIONS LABELED WITH NAMES in the MAGIX, and creates mailboxes for them. It sets up coverage AND the calling group (7929).

http://home.comcast.net/~merlinman

-merlinmansblog.blogspot.com

 

[telgeek1]

it was taking the board renumbering but processor was acting like it still was trying to communicate unfinished business with either messaging module. constantly tying up last 2 vmail ports regardless which messaging module was in play. defaulting processor was only thing that cleared it. then utilizing new messaging module in first cabinet. it didnt like being in 2nd cabinet for some reason. I doubt if the licensing card was the issue but at that point i was tired of dicking with it. the problem with the auto config in this case is that config merlin messaging feature creates a mbox for every ext in the system. this paticular customer was down sizing staff but still maintaing the office space. so just a few mboxes, but utilizing the auto-attendant a lot. and still stay flexible for future. subletting etc.. just a weird conflict between the processor and the first messaging module. ended up biting me in the ass on time quoted.