3300 - ADD HELD "Not Allowed" 1

[MitelInMyBlood]

What am I missing?
I've been doing CDE on the 2K product since "E-stream" and have been certified on the 3300 since rls 3.

Yesterday while on a 3-party conference call (conferenced together on my 5340IP) I tried to perform an "ADD HELD" operation and the screen message said NOT ALLOWED.

I've since checked extensively, there is no interconnect restriction prohibiting this and my station CLOS has Public-to-Public network connections allowed.

Here is the scenario:
The original 3-party conference consisted of myself + 2 others. The 2 other members at the time were one incoming call (the first party) and 1 outgoing call (the 2nd party). Both parties were external to the 3300, using IP trunks in the same trunk group. My onscreen display indicated I had a 3-party call at this point, all on a non-prime multicall key appearance of another set. So far so good.

At this point another external (IP) call rang in to me on another non-prime key appearance. This is where I ran into trouble.

I was able to answer the incoming call on the non-prime appearance and the 5340 gave me a screen prompt to "ADD HELD" which indeed I wanted to do. It next prompted me to press the key of the held line (also not my prime line) and then said "NOT ALLOWED".

About the only unusual thing about this is that all calls (as well as the existing 3-party conference) were on a non-prime multicall appearance of another set.

I've previously had as many as 7 parties conferenced together on my 5340 (1 incoming + 5 outgoing + myself) so what possible reason might there have been that prohibited me from adding the new incoming caller to my existing 3-party conference (aside from the fact that all were on a non-prime appearance)? I've been through the Interconnect tables and CLOS and don't see the reason.

Where else?

Thanks!!

 

[fissure]

Could it be any of these Class of service options:
Maximum CO Trunks In A Conference (which I think defaults to 1)
Maximum Parties in A Conference
Maximum Trunks in A Conference

You did say you'd been through CLOS so ignore this if you've checked them out

 

[MitelInMyBlood]

Been there already.
7
8
7
in that order.

 

[TheMitelGuy]

You cannot use Add Held to add a call to a conference that is on Hold.

 

[Henja]

Hi all,

Well this is a quirky on.... so what software level and type on 3300 are you running here??? The reason for asking is: The CX and CXi come with a dual DSP embedded on the Controller. The Base system will not support over 3x3 party conferences... this being 3 internal and 3 external!!!

Hope that helps
Jase.

 

[TheMitelGuy]

This is the trouble, it has nothing to do with hardware/software:

"The original 3-party conference consisted of myself + 2 others. The 2 other members at the time were one incoming call (the first party) and 1 outgoing call (the 2nd party). Both parties were external to the 3300, using IP trunks in the same trunk group. My onscreen display indicated I had a 3-party call at this point, all on a non-prime multicall key appearance of another set. So far so good.

At this point another external (IP) call rang in to me on another non-prime key appearance. This is where I ran into trouble."

I take it you had the conference call on hold at this point. You can not use Add-Held with a conference on hold. It has to do with the ownership of the call in the call control (i.e. you set does not/can not own a conference call).... now I'm starting to get to technical as I'm talking core software, but just trust me, you can't do what you did. It's even documented.

 

[MitelInMyBlood]

Thanks, that explains it. However, that means the prompt to "ADD HELD" technically should not have been presented. Am I correct in that?

The workaround then is to do the Non-Busy Ext as a key appearance trick, then CFA my prime DN to the NBE and let folks auto-join as needed.

 

[TheMitelGuy]

You are right and I would still DCR it.

Getting down to the code the conference is "owned" by the 3300 call control. If you had another call holding, that call would be "owned" by your set. Problem comes from the set does not see the conference call, because technically you have a call on hold, but it's owned by the Call Control. Hard to explain, but I would still open a DCR, I am siding with you!

 

[MitelInMyBlood]

DCR or DPAR?
Looks like a bug to me.

 

[TheMitelGuy]

You could go either way. You may get resistance on a DPAR, but give it a whorl.

 

[cmbf]

I have had this same problem, you need to go back to the prime key or original conference and add the call from there. I agree that it is mis leading and the option shoudl not be displayed if it is not allowed but this is how I get around it.