How to Block ALL Outgoing Calls and FAXes?

[tundranugget]

SX2000 LW32

We are at a remote site. Management is implementing an Incident Management Protocol. They want the option of completely cutting off access to the outside world, except for the Incident Management Team's phones and faxes. This includes all other voice phones, faxes and modems. It also includes LAN, internet and satellite phone, but those are not my problem. I only need to deal with the phones.

My question is: What is the easiest way to "pull the plug?"

I may not be here when "disaster strikes", so I have to set up a procedure that is as simple as possible. I also have to document the procedure so that whoever is managing the crisis can easily and quickly block access to the outside world. It will not be feasible to personally teach everybody that might be "on the spot", since we have Weekend Managers rotating from a large pool of managers and superintendents. If something ever did happen, there is no guarantee that the one left holding the bag would have actually been trained. So, again, the procedure has to be simple.

Would this work?

1. Assign a unique Class of Restriction to the Crisis Room phones and FAXes.

2. When the sky falls, change all Class of Restriction groups to include all Classes of Restriction except for the COR in step 1.

Thanks.

 

[nytalkin]

Sounds kind of bizzare. I wouldn't touch this one with a fork.

NO GOOD DEED GOES UNPUNISHED!

 

[AH64Armament]

establish a class of Restriction - say 10. add all this new COR to all COR groups that are in use. Change all users Night 2 to COR 10, except the phones that require outside access.
Program feature access code for Dialed Night service - I use **5* for activation and ##5# for checking.
The usage from a phone is:
**5*0 = Day
**5*1 = Night1
**5*2 = Night2

Program the Class of Service for the crisis phones only to be allowed to change day/night service.

When time to go into lockdown, set the system into Night 2 service from a crisis phone.

All phones should be locked down.

9911 if set as an emergency route, will be allowed regardless of setting.

Also make sure that ALL System Speed Calls are not using the override toll control.

Good luck,
Mark

 

[tundranugget]

Thanks for your help

Nyatalkin: I agree with you. Any concerns of mine have fallen on deaf ears. What management wants....

Mark, I tried what you said. I inherited this system and COR 4 was already in all COR Groups and was also already assigned to the COR for Night2 on most extensions. I tested my phone using Night1 (it is identical to Day for our site). When I put the system into Night1, all attempts to dial off-site were denied.

BUT, I was able to dial out using an account code. I looked in the Independent Account Code Definition form and the Account Codes all have a COR of "2". All account codes are 6 digits. Hundreds of account codes have been issued.

I then created a COS (15) with Account Code Length = 2 and, on my phone, assigned this to the COS for Night1 (for testing). Any attempt I made to use an account code resulted in "Invalid Account" and all attempts to dial off-site were still denied.

If I leave all restricted extensions with COR for Night2 set to 4 and change their COS for Night2 to 15, then I should have a solution.

I had already programmed for Dialed Night Service and that works just fine. I removed Dialed Night Service from all COS except one.

Thanks again.

 

[MitelInMyBlood]

How do they prevent people from using their cellular phones?

 

[tundranugget]

Well, the site is a half-hour airplane ride from the nearest cell coverage. Satellite phones would circumvent, for sure. We have a record of all official satellite phones at site and they will be "seconded" for the duration.

 

[IrwinMFletcher]

Here's a thought. Buy a second controller and have the team as resilient sets. When the disaster strikes, unplug the main controller.