sundance-communications.com/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems SX-200 ICP Two 5540 IP Consoles when both are busy...

I have a property with two 5540 IP consoles. When none are busy and the main number of the hotel is called, they want both consoles to ring. I created a hunt group with access code 444 and added both extensions for the consoles to it. Now, when someone calls the main number, both consoles ring. The problem is that when both consoles are busy, and another call comes in, neither console is being alerted via audio or display. Suggestions?

Thanks

You need to program LDN numbers on the keys and point the calls to that number.
Same for Dial 0 calls. When you do that they automatically enter the queue and indicate on the display # of calls waiting.
I never direct any calls to the console extension number.

Got it Steve. In the hunt group option, I assigned the console extension to the overflow and changed the Queue Call timer to 0:05 seconds. That alleviated the problem. The call overflowed to the overflow extension. Not a fix, but a band-aid.

Steve, I'll look into setting up the LDN numbers on the keys.

Thanks

Follow Steve's advice. You should never point incoming trunk calls to a console's prime line. Program the keys on each console with extension numbers making them LDN keys (Keys normally found on a Superconsole 1000). By doing that both externally and internally, you can have as many incoming calls appearing at the consoles as you have LDN keys programmed.

Rcaman

So I arbitrarily create extensions in Desktop Device Assignments then assign them to LDN Keys on each console? Hmm, so then how would I point the main phone number on the T1 to point at those extensions? I could set up a hunt group for those extensions.

Sheesh! I'm 3300 certified but not yet on the 200. I gotta tell you that the documentation for this system as well as the 3300 seems to be vague on MOL. Because of the framework provided in training, I can apply reason and logic to solve problems on the 3300. The 200 is a different ball game. I've found the documentation explaining features and programming to be lacking. I've spent quite a bit of time searching for information on the web and MOL thinking I will find the holy grail but have come up with very little. Thanks for your help. I will continue researching the LDN keys

Steve,

I want to make sure that I'm clear on what you've stated.
Set up phantom extensions in the Desktop Device Assignments form
Program those phantom extensions to the consoles in ATTD LDN Assignments.
Point the main number, the only number, of the straight T1 to those phantom extensions.

Is this assessment accurate Steve?

I think I got it Steve. I have an Avaya background and am new to Mitel. In an Avaya system, you'd create a phantom extension by creating it and assigning an X to the port and type(if memory serves me). I assumed it was similar in a Mitel system. What they say about assumptions is true. Anyway, I was banging my head against the wall trying to figure out why the system wouldn't let me program a phantom extension, meaning an extension with no bay/slt/cct info or type. Finally, I just went to ATTD LDN Assignment and added an arbitrary extension. I then pointed the main number to that extension. I called the main number and it worked. Mind you this is in my lab. I just connected the second console and will continue testing.

Suggestions or advice? Any and all are WELCOME.

Thanks,
CR

Yes. you populate the LDN keys on the consoles with "phantom" numbers. That is what we both wrote. No need for hunt groups.

Rcaman

Once you give the LDN keys on the first console numbers you can use those same numbers for the LDN keys on your second console.

Thanks guys. I set up the LDN keys yesterday evening. I'm going to f/u with the property this morning to get feedback.