Magix DID for VM?

[bostong3]

Let me start by saying, I'm a Definity/S8700 gal and know nothing about Merlin. I'm sure it's very easy once you get a hang of it, but to say I'm frustrated at the moment is an understatement!

We just acquired a company that has a Merlin Magix. I'm not sure of the version right now and the office is closed, so I don't have anyone there to transfer me in via WinSPM. All I know is that I pretty much hate this thing!

Anyways, the LEC has already forwarded their main # to our office and I've set up an AA here that will route back to their office until they move here. The problem is that the VM 770 is not a DID and I have no idea how to create one for this issue. I tried having someone forward a vacant station to 770, but they just get a wave off.

Any ideas!?!?! Right now I have a msg up telling people to call their own #s and *7 to get to access VM and that's not going to fly for very long!

 

[tdaugirdas]

The Magix is a fairly simple switch - compared to Definity - programming-wise. What is it you have to do? Do you need to send a specific DID to the autoattendant? Is the T1/PRI already programmed? Does the system have any analog (regular POTS) lines currently?

Tom Daugirdas,
President
STCG, Inc.
stcg.com

 

[bostong3]

I have an auto attendant (vector) on my Definity that I need to have a prompt route to the Merlin's VM. The Merlin is at a different site and it's VM extension 770 (is this default?) is not a DID. I have a range of DIDs, but just don't what I can do to set something up for VM remote access through the new AA.

 

[TouchToneTommy]

You could just renumber 770 to an unused DID, and when the call arrives it will be answered by the auto attendant.

Anyone with a button on their phone for "Get Messages" will be OK, the button will still get them in. Anyone who is used to dialing 770 to get messages will need to learn a new number.

Alternativly, you can renumber an adjunct extension to an unused DID, put it in the voice mail coverage group, and create a mailbox for it that points to the auto attendant, and you will have the same thing for answering, but 770 will not change.

And although I don't know Definity, I have watched over a lot of it's programming and think that the Legend/Magix is a lot more confusing until you stop asking "WHY" and focus on "HOW" - we had a Definity programmer sit in on Legend programming training, and she had to change a lot of thinking of how things happen in the Definity world to make them happen in the Legend world.

 

[phonesaz]

I agree w/ TouchTone Tommy. I call it illogical logic; you have to forget about normal linear thought processes and just go with the the way the Magix is. I think it has a lot to do w/ the evolution of the system over the years and people just adding new things to existing infrastructure (thus voice mail being handled as a calling group...) I tell every client of mine who works on Magix to download the feature reference manual to their desktop and use it frequently. The feature interactions are well-described, and the programming steps are detailed for both MLX 20 and WIN SPM. I find that after the first couple of issues, they are able to run on their own. If you don't have the reference manual yet, you can download it from avaya.com. Also this forum is excellent.

 

[bostong3]

Thanks! I think I did download the pdf, but just getting into the system remotely is a hassle (having to be forwarded to *10), so I've contacted the vendor that has been taking care of the system up until now. Hopefully it'll be gone in 3 months and everyone will be on my S8700. Now if I could just get rid of the Nortel Option61 in Cali!

Thanks again!