Merlin Magix Button Programming 3

[IAmKarl]

Hoping someone here might be able to help me out.

A client of mine has a merlin magix that has been in place for probably 10 years using POTS lines operating in a key system mode.

They just changed phone companies and the new company wanted to deliver as a PRI, so they had their original company come back and do the programming work on it.

So, in the changeover they obviously had to switch to a hybrid mode, which is where the heart of this question lies.

How we wanted to deal with this is to have a ring group which started on our receptionists (1 main receptionist and 3 additional who ring at the same time as backup) then fell over to an additional 10 people or so.

After that, we wanted them to program a few global call parks on all the phones (a mixture of 4424LD+ on the primary call handlers, and 4424D+ on the rest) which would allow people to simply park a call and then others to pick them up out of park.

Thats where the issue is. The company doing the programing says that it isn't simple on the Magix. On the 4424LD+'s it is simple to park and unpark a call, but the 4424D+ can't do it simply for some reason? Apparently they need to hit three buttons (function, parkin, and a programmed button) to pickup a call, and it is flat out not possible for them to place a call in the global park.

Is this true?

Are we (or they) going about this wrong?

We are simply trying to make it easy for a large group of people to put calls on hold and pick them up from different extensions (they may not know which extension when they put it on park).

If anyone has any insight I would be very grateful.

Thanks,

Karl P

 

[IAmKarl]

Assuming that these limitations are real.... Would switching the brain out for an IPOffice 500v2 with digital station expanders on it allow them to do what they want?

Thanks,

Karl P

 

[CarGoSki]

It is true that Merlin can be tricky and it does have its limitations. I won't speak to the Merlin programming cause it is too early for me to think but if you have a IPO as you suggested then you could program the same park buttons on each phone.

In IPO you can create an arbitrary number for a park zone and assign it to a button. If two users have the park button with the same park number then they can use it to park and unpark the same call from those two phones.

For 4400 series phones you can read all about it here.

http://marketingtools.avaya.com/kno...s/dsuser/hold_park_transfer_parkingcalls_.htm

good luck

 

[merlinman]

First off, I WOULD NOT RECOMMEND wasting money to purchase a new system, IPO or whatever. They have everything they need to do the job, it just needs to be done correctly by someone who really knows what they are doing.

It sounds like they set the Main Console up as a QCC.

If that's the case, it was an extremely BAD IDEA.

The way I do this with a PRI, is to provide the operator (A DLC for sure) 5 or so SA Buttons and then have COVERAGE on the extensions you want to ring when that extension rings.

QCC and GROUP RING are both REALLY BAD IDEA's.

The QCC has no flexibility in usage or programming and is VERY DIFFICULT for someone to learn, especially coming from a "KEY" environment.

GROUP RING will pretty much NEVER go to coverage.

So, that's my story and I'm sticking to it......

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

-merlinmansblog.blogspot.com

 

[phonesaz]

I agree with the QCC comment. If the console is in QCC mode, I would change to DLC which gives you a lot more flexibility. I believe you can park easier with a DLC as well? It seems like a lot of $$ to go with IP Office just to fix park. Especially if people are used to doing things the 'Merlin Magix' way. I just migrated a large client from Magix to IP Office and they love the look and speakerphone quality of the phones, but really prefer operating the way the are used to on the Magix.

 

[IAmKarl]

Thanks for the info guys.

We have found someone in the area who has been on merlin's for 20 something years and apparently knows there stuff.

We are going to get them to work with us on it.

Thanks for the information,

Karl P

 

[CarGoSki]

Thanks for the star.