Freeing up Buttons on a 4424D/LD & ETR 4

[Dexman]

I'm developing a list of questions to ask in this forum as I fool around with my "woodshed" Merlin Magix. I'll spread them out as I don't want to become a forum hog.

Right now, with the Magix in Key Mode and an 800GS/LS-ID located in slot #2, desk sets reserve enough positions for all 8 possible telephone lines.

In situations where not all 8 telephone lines will be used, is there any way to free up buttons that are currently allocated for, say, lines 5->8 so they can be used for other purposes? I know that pooling the lines would accomplish that, but I don't see where you can break out individual lines within a pool as the Partner ACS can do.

I poured through the Feature Reference and System Manager Quick Reference, but came up empty.

Just for giggles, I tried busying out the lines as well as stopped pointing them towards 790, but those steps didn't work.

 

[kmefford]

If you aren't using the lines, just remove them from the extension. then the buttons can be whatever else.

 

[Dexman]

Hi kmefford!

Is this procedure the one I need? (I found this in the System Manager Quick Reference on pg 47/184.

Extensions->Lines/Trunks->(extension number)->Enter->Entry Mode->(line or trunk number)->Enter->Back->Back.

 

[TouchToneTommy]

Yes, except you will Delete them, instead of Entering them.

Instead of pressing Entry Mode, you can just click on each line to change its status from assigned to not assigned (and back).

Remember that the system assigns the lines in the order selected to the next available button. So if you want an unconvential layout, you need to add "phantom" lines as placeholders, add the line(s) that you want, then remove the placeholders. Then reprogram any buttons that were overwritten by the placeholders.

When you get to Hybrix/PBX mode, there is even more fun, as adding just ONE line of a pool will add ALL the lines in the pool (to an Operator position; it will make a single pool button on any other set). If you want a different config, you must remove the lines from the pool, add the lines to the Operator, then put them back in the pool. Not something that you want to do in the middle of a business day!

 

[Dexman]

Hi TTT!

I think a few of my brain cells just self-destructed after reading how line additions affect pools in hybrid mode. .

Key mode looks much safer to play with.

 

[kmefford]

If you only have a few lines and/or phones, key mode is generally easier to deal with.

 

[kmefford]

another fun thing to remember, if you are trying to delete a line from an extension then add a different one, things can get goofy.

You have to delete the line.... go back to "exit" the extension.... then add the new line. Otherwise, the new line will get assigned to the next available button and leave a blank button where the deleted line was.

Was that clear as mud?

 

[Dexman]

Actually that was pretty clear!

I tried out the sequence and it worked like a charm! Dropping unused lines really frees up feature buttons on the phones.

Up next, getting the designated loudspeaker page port to work properly and getting MOH to play for the <b>entire</b> duration of a call being transferred from the auto attendant to an extension.

Will generate posts for those issues a little later on.

 

[2BAvoice]

Even though the documents say you have an option for Music on transfer, you still hear ringing. Bell Labs told us "working as designed" we said the documents differ from this, they said "the documents are wrong" we said why in programming do you have the option, they said "shut up". Good luck. That was Legend R2, and I believe it is still the case through the last verion of Magix.

 

[Dexman]

Bell Lab's response to the how Music on Hold feature works on the Merlin Magix is quite interesting considering that it works perfectly fine with the Partner ACS.

2BA nailed the problem I'm seeing with the R4 Magix. When a call is being transferred from the auto attendant to an extension, I hear maybe 2 seconds worth of MOH and then ringing.

Other than that, MOH seems to work as it should.

I solved the paging mystery so I'll generate a new question for the final issue on my list.

 

[merlinman]

It works like this, when the phone being transferred to is AVAILABLE, it will ring.

IF the phone is in a QUEUE type situation, then you will get music on hold, until it is available.

The feedback is correct, I do not recall the documentation being wrong, but what ever.

IF you are REALLY GETTING TRANSFERRED, that is, when the call is REALLY RINGING on the phone you are transferring to, you get RINGING, 'cause it is ringing on the phone you are being transferred to.

If you are WAITING to be transferred, then you get music on hold.

IF you want to FORCE MUSIC on hold to your caller, (depending on your set up of course) you could set the receiving extension to have only one SA Button.

Also, you could "CAMP ON" the call, but that requires some funny stuff with voice mail coverage.

The system was designed with the idea that people who buy these systems really want to get their calls.

 

[Dexman]

Hey Merlinman!

I was hoping that, when it comes to MOH, the Magix would behave in a similar manner as the Partner ACS, where MOH completely replaces all ringing during call transfers, until someone picks up the call, the call answered by voicemail or if the call is sent to a covering extension.

It sounds as if MOH was not really meant to entirely replace ringing in the Merlin Magix.

Am I close?

 

[merlinman]

As I said, if the call is REALLY RINGING on an EXTENSION being transferred to, the caller will hear ringing.

If the call is REALLY ON HOLD (or in the process of being transferred, but not delivered) the caller will hear MOH.

That's kinda' the way the BIG SYSTEMS work.

Understand, the PARTNER was Designed AFTER THE LEGEND, by a COMPLETELY different set of Engineers. However, they had feedback from Tech Support Engineers who supported the LEGEND.

Things those guys didn't like or wanted, got changed to match their likes/dislikes/wants in the PARTNER, (KINDA').

Of course, all systems were the work of committees, and we know the result of such work. That is, a CAMEL is a HORSE made over by COMMITTEE!

 

[Dexman]

Ah, that would explain the difference between the Partner and the Magix/Legend.

I need to remember that analogy about the horse and camel!