Author Topic: Interconnect Restriction (Read 13333 times)

bobcheese · « **Reply #15 on:** February 16, 2010, 03:52:19 AM »

and this didnt work?

mattwilsonuk · « **Reply #16 on:** February 16, 2010, 04:13:42 AM »

no because

ext1000 (IC1) ext2000 (IC2)
PBX 1-----------------------------------PBX 2
(ic64) IPTrunk (ic64)

if i block ic1 from 64 it doesnt get past the ip trunk to pbx 2

is this what you mean?

bobcheese · « **Reply #17 on:** February 16, 2010, 06:54:48 AM »

yes, is that not what you are trying to achive. to stop the set accessing the rest of the cluster as well as internal numbers except a pre defined list?

mattwilsonuk · « **Reply #18 on:** February 16, 2010, 07:02:54 AM »

sorry no... the internal numbers are withi the cluster so need to traverse ip trunks. would be ok if all the numbers this public phone needs to contact were on the same pbx.

bobcheese · « **Reply #19 on:** February 16, 2010, 07:08:26 AM »

ah I see. I am sending you down the wrong route then. Max dialled digits will prob be the easiest route for you

mattwilsonuk · « **Reply #20 on:** February 16, 2010, 07:19:43 AM »

yes works very well, not sure how to get around disabling the operator, cross that bridge later ;-)
Thanks...!!

Mattmayn · « **Reply #21 on:** February 18, 2010, 03:35:39 PM »

That could be done using interconnect assignment fairly easily I would think. Unless it is on another controller like you described earlier.

Mitel Forums - The Unofficial Source

News:

Author Topic: Interconnect Restriction (Read 13333 times)

bobcheese

Re: Interconnect Restriction

mattwilsonuk

Re: Interconnect Restriction

bobcheese

Re: Interconnect Restriction

mattwilsonuk

Re: Interconnect Restriction

bobcheese

Re: Interconnect Restriction

mattwilsonuk

Re: Interconnect Restriction

Mattmayn

Re: Interconnect Restriction