auto-answer and conference 2

[lmb2]

We have resilient 3300 LX controllers on version 7.1.3.4_2. Our conference room phones are 5220's with the 5310 conference unit with side control.

Is it possible without human intervention to have mulitple incoming calls automatically conferenced to an extension?

 

[kwbMitel]

Check out the FAQ page

How to make a non-busy extension become a key appearance

faq1329-5872


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelmatt]

Use Quick conference :)

 

[lmb2]

Thank you kwbMitel! Your instructions were VERY useful. Works like a charm! Now if I can figure out a way to beat that 8 call limitation without having to by an additional ASU or give up anymore of my analog trunks and still retain the automatic conferencing.

I know I can add more than 8 callers by manually adding calls from another line on the set but would like to do it automatically...without having buy the quick conference. Thanks anyway Mitelmatt, but these days you have to be able to do more with less.

 

[Mitelmatt]

Personaly, i think that with all the agrow you'll go through with that solution, Quick conference would work out cheaper and more functional. A great little app which is going to be advanced further.

You should at least investigate

 

[MitelInMyBlood]

The limitation with the Non-Busy Extension as a Key appearance as described in the FAQ is actually 7 calls (7 + you). However, if you had "participants" within the same facility you could do as the FAQ suggests and give them each a key appearance of the NBE (conceivably extending the total number of concurrent parties to 39) and they could join the conference simply by picking up the extension at their desk; and/or make the NBE the prime line as the FAQ also discusses and use your "control point" with a few lines of multicall along with the "add-held" function, allowing the conference moderator or control point to dial out and bridge addt'l parties.

The problem is that with each additional layer of complexity another shovelful of rock is thrown into the hole you've dug for yourself. Tread carefully with this "solution".

 

[kwbMitel]

If you require conferencing beyond 8 parties the Quick Conference Application would be your best bet.

Trying to defeat the limitations with most definitely be an unsatisfying experience

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[lmb2]

Mitelmatt, I did look into the quick conference and agree it is a sweet solution, but the powers that be are looking for a solution that doesn't require additional funding...at least at this point. However, I will be including the quick conference in next years capex requests.

MIMB, thank you for the clairification of the key appearances on other users desk extensions. (doh!)

 

[MitelInMyBlood]

I understand completely about "funding" - just be a little careful about pulling too many rabbits out of the hat to escape what needs to be done here to do it right. What we've given you with the FAQ should be looked upon as a temporary getaround for only a "control group" of informed users who understand it's a kludge with limitations and no guarantees and is most certainly not supported by anyone, least of all the manufacturer. Otherwise these bozos will beat you up when there are problems and have you milking that same goat until it dies.

By the way, it would probably be worthwhile to inform the users about the potential peril that can occur from dialing-into your homemade bridge from a cell phone. If they do, all bets are off and you may wind up with echo out the wazoo and about which you will be helpless.

We use this lash up as an "order wire" or whoop-n-holler circuit with a multiline set programmed to auto-answer for our own techs who themselves are telecom pros. Never in my wildest hallucinations would I ever put something like this in the CEO's office without the standard "you're on your own with this" disclaimer.