Blocking users from calling other users 1

[AvayaNACR]

I am working with a government contractor. They are somewhat used to CM/Definity/Aura features, but want an IP Office. They have three groups, A B and C.

They want the following groups to be able to talk
A can talk to B
A can talk to C
B CANNOT talk to C

I do know that IP Office does not support tenant partitioning but is there a way to keep phones from calling each other? I heard short codes will not work because the system looks for extensions before it looks for short codes.

 

[Bas1234]

Won't work with SC. Use DND and the whitelist. Click help on the DND tab of a user.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[intrigrant]

Using DND and whitelists makes you can't receive external calls unless you program cli with wildcards like 0N presuming all external calls CLI start with a 0, unknown num bers and witheld numbers cannot ring the phone, group calls, diverted calls etc will be denied also.
So in my opinion this is not a option.

 

[amriddle01]

I agree, don't shoehorn an IPO in where it doesn't fit, or they need to change their requirements. If they don't and you install an IP Office they will not be happy in the long run

 

[sbcsu]

The HiPath range of systems have ITR Groups (Internal Traffic Restriction) matrix ability.
Maybe your system does too?

 

[AACon]

I actually have a pretty engenious idea for this, but it would take a bit of work to make for a whole group of users.

Users in Group A have DND on.
User in Group A have a leave start point in their VM that goes to a module; call it whatever you'd like.
Generic start point copies $CLI to $CP0
Test Variable Checks to see if $CP0 is an extension/HG/Mailbox; if so, disconnect (you actually get a busy tone).
If No Match, go to an assisted transfer, that transfers to a shortcode. The transfer would consist of *66$TARGET, source $CLI, description, Priority Call (or whatever).
The No Answer/Busy would go to a leave mail action for $TARGET

The shortcode would consist of code: *66XXXX/Priority Call/N

As long as the user is on DND, it will always go to this module. Other users on the system CANNOT call them.
Callers using the DID of the user can get through.
Callers going into a menu with a DBN directory or direct extension dial would not know the difference, you would just to a transfer to *66$KEY or wherever.

It seems to work pretty well so far.

Granted, you would probably have to do a bit more work and see if the $CLI starts with say a 5, and is 4 digits long, so you know it's the 5xxx extensions and then those CAN get through, and 6XXX cannot, etc. Pretty easy stuff in VMPRO, actually.

Of course, this would increase the vmpro port usage by quite a bit, but hey, governments like to waste money!

-Austin
ACE: Implement IP Office

 

[tlpeter]

Austin, when you are testing anyway can you test if the new option incoming call bar is overruled with a priority call?
It blocks all calls but incoming calls is too much sometimes

BAZINGA!

I'm not insane, my mother had me tested!

 

[mforrence]

I have another method that will work fine.
Say that group A is ext 1100 series, group B is 1200 series and group C is 1300 series.
Put all of group B into a user right with a user right shortcode 13X to barred. The shortcode will match before the extension, preventing calling.

 

[amriddle01]

That will only work if you aren't using dial delay count, extensions match before shortcodes

 

[AACon]

Peter, it does not; at least not in my case. The incoming call bar works only with external calls, and as soon as the call hits my switch I get a 403 Forbidden (and Q850/21/CallRejected) and it drops the call. Guess it does it's job. Internally, of course, incoming call bar doesn't do squat.

-Austin
ACE: Implement IP Office

 

[tlpeter]

That is what I thought.
Took bad that there is still no option for that.

BAZINGA!

I'm not insane, my mother had me tested!

 

[tlpeter]

A 403 is strange. I think it should give a 486 busy.

BAZINGA!

I'm not insane, my mother had me tested!

 

[intrigrant]

If tenancy is a prerequisite then quote another brand or a CM, IP Office isn't build for that and it cannot be emulated without running into other issues were a lot of common features are blocked.
In the long term you loose your hair if you have any left from similar projects in the past....

 

[AACon]

Well a 486 would indicate a busy destination, where a 403 means "hell no", which is technically what the call baring does.

-Austin
ACE: Implement IP Office