colpritt

I'm not sure what changed as I'm pretty sure this used to work, but for some reason users cannot conference another internal extension. They can conference up to the limit of external numbers, but can't get an internal extension on the call. Any ideas? Definity Prologix V11. Thanks!

nexSIP

There is a system limit of like 6 users in per conference call. is that what your hitting?

__________________
http://www.nexsip.com
Communicate Openly and Freely

PBXtech.info

 

colpritt

Nope, it's not that. Even if the 2nd station is the 3rd party on the call, it won't work. Any ideas? Thanks!!

ahays

We just had this exact problem with a customer. It turned out to be an ISDN setting ... something like NI1 instead of NI2. My customer is on vacation right now, but I'll check with him and post again.

regs,

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

colpritt

Thanks Al! But, ISDN setting where, on a trunk? I don't know how that would affect conferencing the internal party, but I guess it's not surprising if something that seems unrelated would be causing it. At any rate, if you could let me know after your customer is back from vacation, that would be great. Thanks again!

early

What is the value of the "conference parties without public network trunks" in the system-paremeters? I'm looking at a release 7 G3si. Unless r11 is drastically different, your value should be 6. Let me know.

PBXtech.info

 

ahays

We made NO CHANGES in the S8300. The LEC changed the PRI from NI1 to NI2 (again, I'm quoting from memory which is a dangerous thing for an old fart like me). I will verify when my customer returns from vacation. Until I can verify the actual fix, give your service provider a call and find out what protocol they're using on the PRI.

regs,

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

colpritt

Thanks Al. I finally broke down and called Avaya. I spent 1/2 hour on the phone with a very nice woman who was as stumped as we have been... she put me on hold for a while..... here's what it was. In the COR, "Restriction Override" has to be set to "none". I don't completely understand it yet, I need to do more research, but that fixed it. The definition in the documentation for Restriction Override is

Restriction Override
Allows the specified users to bypass restriction on conference, transfer or call
forwarding operations.
Valid entries

attendant - A telephone with a COR that is inward restricted cannot receive public network, attendant-originated, or
attendant-extended calls. Enter attendant to give your
attendants the ability to override this restriction.

all - Enter all if you want all of the users with this COR to
override inward restrictions.

none - Enter none if you do not want any users of this COR to
bypass the restrictions.