911 calls and CDR

[pruden]

Does anyone know if a CS1000 R5.5 can be set up to print a 911 CDR record to a seperate port / terminal? I don't want this terminal to get all the CDR records - just the 911 records. Or, is there another way that I can set up a device in our security office that will identify what telephone called 911? We want the 911 call to go to emergency services but we had a case where the caller hung up before they could identify themselves and when the emerg team showed up we did not know who called.

Any advice would be greatly appreciated.

 

[Reusser]

yes - just build a TTY with USER=OSN

Assuming you are using ESA programming (ld 24) for 911 calls

 

[pruden]

Thanks Reusser -

New to this location and ESA is not activated. I will start on that little project right away because this is exactly what we are looking to set up.

Many thanks.

 

[dj4020]

Reusser is correct and only if you are using ESa will you get the info of who dialed the 911 call, also you can set ip up to also include 9911 calls if you are using that as well. There is a patch for callers who misdial for example they dial 9 to get an outside line put in a 1 then enter anotehr 1 this normally is enough to send a call to 911 but the patch alowws I believe a 2 second delay to see if another digit is entered thus stopping the 911 call.

 

[GHTROUT]

I'd take a look at these:

http://www.youtube.com/view_play_list?p=3D7AC91BA6D7308E

[©] GHTROUT.com [⇔] Resources for Nortel Meridian/CS1000 System Administrators - You Can Hire Me Too

 

[cmoegie]

You do not need the patch in release 5.5 as misdial prevention is part of the ESA block in that release.
You get 9911 to be considered ESA call the RLI for the 911 has to have LTERM set to yes.

 

[Reusser]

Anyone have an Idea what path is refered to by above comments for misdial 911 calls?

I do not find anything in patch library. Maybe a PI patch?

 

[Reusser]

found it - it is listed under FAQs

 

[cmoegie]

Mis-dial prevention does not require require a patch in release 5.0 and above. Below is part of the documentation for 5.0 on ESA out of the What's New 5.0 NTP:

• Support for the use of Route List Indexes (RLIs) is introduced, whichallows ESA to identify alternate routing for emergency calls, in the event that the standard route is unavailable. This functionality helpsto ensure that an emergency call receives emergency handling byensuring delivery of the call to the appropriate emergency responder,including the ability to locally terminate an ESA call without required use
of loopback trunks.
• On-Site Notification (OSN) output and SNMP traps are enhanced to provide more detailed emergency call information.
• Virtual Office ESA calls can now route directly to the host Call Server for emergency call handling, rather than being redirected.
• Support is introduced for Multiple ESDN. Previously, it was only possibleto configure a single ESDN to be used in placing emergency calls. With CS 1000 Release 5.0 ESA, it is possible to configure up to 16 distinct ESDNs to better suit the needs of a multinational enterprise.
• Implementation of the Misdial Prevention functionality, which provides system administrators with the ability to prevent ESA calls from being made due to an accidentally misdialed ESDN. Cases outlining possible ESDN misdials can be configured for each ESDN entry in use in the enterprise (a notification is made for all calls blocked in this fashion,using the Misdial Prevention functionality).