911 - Emergency Dialing

[bwtc]

I am reviewing our 911 procedures at our remote facaility, and was wondering if anyone has a possible solution to this issue:

The remote site utilizes 2 line pools. Pool A is for 2 copper lines, and Pool B is for 4 tie-lines.

Under normal scenarious, an outgoing call is routed through Pool B, and overflowed to Pool A.

There are a few phones that we want to restrict outgoing dialing.

The problem is that 911 will not work from these phone, either, because the 2 copper lines are assigned to pool A, which is restricted.

We really don't want to have to purchase a seperate copper line, just for 911 use. And, we would prefer not to dedicate one of these lines just for outgoing 911 use (both of these copper lines are in use for incoming calls).

Is there a way to "trick" the MICS (6.1 MR3) into assigning these 2 lines into more than 1 line pool, so I could give the phones that I don't want to use Pool A or Pool B, use Pool E (for example) if 911 is called?

Thanks

 

[bwtc]

I thought of a possible solution, but do not know if it'll function the way I'm hoping.

In our Trunk card, we are using 2 of the 4 available lines.

Can the lines be cross-punched, so Lines 001 & 003 are coming from the same source, and the same with 002 & 004 ? Lines 003 & 004 can then be assigned a different line pool.

My only concern with such an approach is if, say, line 002 is in use & someone dials 911. I don't think that the MICS would be "smart enough" to know that the line is currently in use, and would dial "911" in someone's ear.

Thanks

 

[gforce9]

Based on your description, I think a seperate set filter for those 'restricted' sets would be in order. You will have to deny 9*, but allow 911 in that set filter. Also, allow the access digit(s) for the main site. Give access to both line pools on those phones. The filter will restrict the use of those lines by the restricted sets, save for 911 calls. Do not 'cross punch' any lines....you will only expedite grey hair for yourself!

 

[bwtc]

gforce9,

Thanks for the advise. The next time I'm on-site, I'll build the filters & do the testing. I'd rather be there in case something goes wrong.

Will advise once I've tried.

 

[bwtc]

I tried this at corporate, but the restriction doesn't apply to the dest code. In other words, I can DENY 9*, Override 911.

But at our remote site, '9' first uses pool B (via E&M), and then uses pool A (local).

I want the restricted phones to be able to dial corporate (which is pool B). So, I do not want to deny access to pool B.

Since "9" as a restriction doesn't prevent the Dest code from being entered, it appears that the only way to get this to work properly will be to restrict *, and have overrides for 911 & the trailing numbers of the extension that aren't part of the dest code.

 

[hawks]

The restriction applies to the number after the Access or Desti code. So what you want to do is restrict 0,1,2,3..thru 9. Then allow the override of 911.

 

[bwtc]

hawks,

Understood. BUT... won't restricting the individual digits (0, 1, etc) not allow dialing of extensions at corporate offices, unless every extension is defined as a dest code (so the set restriction won't come into play?)

 

[hawks]

How do they dial across now 9 + ext?

 

[bwtc]

To call from facility-to-facility, they don't use 9 + ext. They use 4-digit direct-dialing (via Dest codes, which go over Pool B (E&M - lines 051-054)).

When they dial 9, it goes over Pool B by default, with an overflow to their local lines.

So, if they wanted to call ext 1835, they just dial 1835...

Unless I'm over-complicating things (which I've been known to do... ;-) ),

If I add each digit (0, 1... 9) & exempt 911, if someone dials "1835", it seems to me that the only way the above scenario would work is to setup 1835 (and all other extensions at corporate) as a dest code, to bypass the set restrictions.

BTW - I am not opposed to doing them, but am looking for a "cleaner" way...

 

[hawks]

Either that or you can over ride the extensions in the filter. So I take it you have a Desti Code of 1 or 18? If for calling to the outside world your desti code is 9 and Absorb Length 0 (remote side). Then you can do an override on your filter of 18* (any) and go into your Public dial plan and build a Prefix of 18 and make the DN length = 4.