911/ESA question... Please help - PBX Info :: Your Free PBX, PABX and Telephone Information Resource

eldond · 05-19-2006, 07:38 AM

Hello all

Let me say right up front that I am a Newbie and have gained a tremendous amount of insight from this forum.

I work at a school district in south florida and have inherited an Option 11 that functions as a standalone switch for our Maintenance, Transportation, Procurement, and Food Services Departments. It has its own DIDs and also has a T-1 tie to the main District switch (option 61) for four digit dialing.

We have two main problems:

1) After installing our new call accounting software, we discovered that the 911 calls originating from the option 11 route to the tie trunk on the option 61 and to the PSAP from there. This is not good because the main number/address the PSAP gets is for the 61 vice the 11.

2) The PSAP reported seven 911 calls yesterday; our software tracked two calls (both of which were legitimate). Five calls were false calls (hangups), but I would think the CDR record would show them.

Any/all thoughts and help are greatly appreciated.

ISS:
VERSION 2121
RELEASE 3
ISSUE 00 +
IDLE_SET_DISPLAY NORTEL

CLID Info:
ENTRY 0
HNTN 239
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 3340211
DIDN NO
HLOC 334
LSC
CLASS_FMT DN

ENTRY 1
HNTN 239
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 4794200
DIDN NO
HLOC 479
LSC
CLASS_FMT DN

ENTRY 2
HNTN 239
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 3442531
DIDN NO
HLOC 344
LSC
CLASS_FMT DN

ENTRY 3
HNTN 239
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 479
DIDN YES
HLOC
LSC
CLASS_FMT DN

I have tried to print out the ESA information in LD 24 but have no success. Screen capture follows:

Ld 24 error:
>ld 24
ACC000
MEM AVAIL: (U/P): 728380 USED U P: 362673 88594 TOT: 1179647
DISK RECS AVAIL: 382
REQ prt
TYPE ESA
CUST 0
SCH0282
>err sch0282

SCH0282
I/O device cannot be an OSN user due to user conflict. Input is
rejected.
Action: "Remove all the conflicting users before configuring the I/O
device
as an OSN user."
Severity: Info

Buckshot · 05-19-2006, 10:14 AM

The accounting software should have nothing to do with your 911 database. Do you have 911 database software?

I see by your CLID table that you have no information in the ESA range:

CLID Info:
ENTRY 0
HNTN 239
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 3340211
DIDN NO
HLOC 334
LSC
CLASS_FMT DN

Also, I am wondering where you are getting the OSN error from. Post your ADAN from LD 17.. that might be where the conflict is coming from.

Do you have non-DID callers who might be making 911 calls too? I've only set up ESA info 1 time, and it seems to work ok, so I have some of my prints to reference for any questions.

telecom116 · 05-19-2006, 11:53 AM

Do you have any local trunking (ie, analog trunks) off of the 11C? Are your DIDs supplied through the 61?

I have a similar setup where I have two 11c units, one with the PRI/DID trunks to the CO, with ITG IP trunks between the two. The second 11c has one analog trunk for emergency use (if the IP net is down) that I point the 911 calls to. That way these calls have the local address of the site. The only other solution is to work with your local telco on a PS/ALI solution, where you actually upload to the telco database the location info on all of your DID numbers.

As to the error that you are getting in ESA sounds like you may have more than one ESA DN enabled.

frenche · 05-19-2006, 03:26 PM

I think you will find that there is a minimum connect time before a call is considered complete. If the call is not connected for the minimum time the CDR system does not consider the call completed. This is to account for calls to busy numbers or calls disconnected before answer. Since 911 calls are usually answered very quickly and the caller is likey hanging up as soon as they hear "911, What's your emergency" the calls my not be connected long enough to be counted as a call.

Frenche

**Fletch** · 05-20-2006, 12:07 AM

The tracking of E911/ESA calls via CDR is not recomended by Nortel. You should make sure that ESA is set up correctly, and that your ESA/E911 calls are being routed via a PRI so that the proper ESA CLID can be applied. If youare routing over copper trunks then ESA CLID never comes into play as you cannot send CLID over COT trunks. Also when setting up ESA make sure that your 911 SPN is terminated locally so that these calls are seen as ESA calls. If you don't terminate locally to the ESDN, then the call is never ecognized as an ESA call, and you wont get any OSN notification.

As for your error, make sure you have an OSN DN defined in LD 24 and that the phone with that DN has an OSN key defined.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Voice Mail Question	jawdoc	Partner / Partner II	6	10-16-2006 02:55 PM
TGAR/External Call Forward Question.	hached	Meridian Systems	23	04-27-2006 03:16 PM
NORSTAR Voice Mail Question (Errors after ext move)	hetnkik	BCM and Norstar	4	11-08-2005 09:26 AM
Right, ignore my last question, this is a proper question!	PaulEMiles	Meridian Systems	3	12-31-2003 05:01 AM
Option 81 Question	VancouverTech	Meridian Systems	1	06-03-2003 07:26 PM

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)