jack

I use the FLEN prompt/feature and have the numbers built as SPNs with a deny of 1 through 9.

This kills any call that has a digit entered after 911 or 9+911. User gets reorder.


Works like a chram!!!!

Jack

__________________
Dogs rollover Phones hunt

freddog

Jack- this is a valuable tip! I know this question has come several times before. It would probably be a good idea to copy your solution to the frequently asked questions section.

gwebster

..but if you are using the ESA package 329, doesn't the 911 (if programmed as the ESDN) get captured before any NARS/BARS handling and routed out to the PSA?

telecom116

From personal experience, gwebster is correct. We have PRIs to the LEC and we found that you can't hang up fast enough from inadventant 911 calls...the ESA software sees the 911 string and the call is immediately connected to the PSAP.

Within several months of our initial installation we changed ourr BARS access code to 8 and it dropped our inadvertant 911 calls to zero (from 1 to 4 per month). At $100 per false call we had to do something; our people were hanging up and not staying on the line with the PSAP. We have quite a few 500 sets off-site, and they probably accounted for 60-70 percent of the false calls, most of which I believe were missed digits. A neighboring NPA is 913 so I believe our callers were missing the second 9 for whatever reason.

Of course the ability to do this is dependent on your current number plan. One other idea would be a two-digit BARS code (ex: 99, 9, if possible.

jack

DOH!!!!!!!!!!!!!!!!!!!!!!!!!!! :casstet: :casstet: :casstet: :casstet:

I really need to start reading ALL of the question!!!!!!!!!!!!!!!!!

In a non ESA enviorn. the previous answer is great.

Let me play w/ it in an ESA situation to adopt the concept, sorry!!!!


Jack

__________________
Dogs rollover Phones hunt

jack

Ok,

I agree that the 911 programmed as your ESDN no way to deal with this as soon as system sees 911 call is gone.

But the AC1+911 should still work as described, since it still see the BARS progrramming before the DMI changes the dialed digits into the ESDN.

Still just theroy at this point, other thoughts on this?

Jack

__________________
Dogs rollover Phones hunt

jack

Although in the example GW used this also will not work :casstet: :casstet: :casstet: :casstet:

One other thought is changing your ESDN to 9911, can be up to 4 digits, and force the 911 dial string to be subject to BARS via SPN & DGI.

Still this is only theroy would need to be tried out before I could recommend, anybody want to test?

Changing your AC1 does seem to be only other answer.

Jack

__________________
Dogs rollover Phones hunt

Fletch

The ESDN is translated at the DN level. If you want to handle 9-911 calls the proper way to do this is to capture 9-911 in BARS as we always have done use LTERM to terminate it locally to 911. ESA then picks it up as an ESA call and sends it.

The proper programming for AC1-911 is as follows:

AC1 SPN
911

RLI 911

ENT 0
LTERM = YES
DGT 911

DEL 1
INST x

Now when a user dials AC1+911 the call LTERMS to 911 at the DN level, ESA is captured and processed correctly.

This is important if you use the OSN feature of ESA. If you dont LTERM the AC1+911 calls, they are not recognized as ESA calls.

Setting 9911 as your ESDN is dangerous. Basically you are not capturing 911 as your ESA. Also on all PRI trunks, the ESDN is transmitted as the dialled number. Therefore 9911 is sent which may not be processed by the LEC correctly.

Just some thoughts, based on the discussion.

__________________
Fletch

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Don't forget to register for the FREE E911 Webinar on Oct. 30th!
http://thevoicereport.com/E911

jack

Fletch,

GREAT CATCH!!!!!!!!!!!!

Completly blew the part aabout the ESDN is also what is transmitted :casstet: :casstet: :casstet:

Thanks!!!!!!!!

Jack

__________________
Dogs rollover Phones hunt