CS1000 rls. 4.5 -- 911 issues

[oceanSD]

Working on Caller ID to 911 on a CS1000 on 4.5 software...

Issue 1: Customer has range of DID numbes on a PRI. Until ESA was set up correctly, CLID was the last number on the PRI and 911 was also able to see address as expected. Changed ESA to send a DID number that appeared on the calling phone as a test and they received the correct number, but no address. When ESA was changed to send the main number, 911 received no number/address, but a code (probably the code listed in the Nortel docs - she had an emergency call so I didn't get the details...). I thought it was strange that the two DID numbers were treated differently. Here's the ESA block:

CUST 0
ESDN 911
ESRT 0
DDGT 911
DFCL nnnnnnnnnn (main number)
OSDN

Issue 2: If the local PRI's are down, customer wants calls to route second to COT trunks and third to across SIP trunks to another PRI. First of all, I don't know of a way to STEP to a third route (will be great when they upgrade to 5.0 so we can just use an RLI!); and I know there's not anything we can do about the COT trunks CLID; however, does anyone know of workaround to caller ID issue if the call goes across the SIP trunks?

Thanks in advance!

 

[oceanSD]

still looking for assistance... thanks!

 

[curtismo]

When using a PRI you will need to properly set up your CLID table in LD 15.

First, figure out what CLID table you are using. Then go into LD 21 and print it out. Example for table entry 0 (default):

REQ: prt
TYPE: clid
CUST 0
SIZE 100
RNGE 0

ENTRY 0
HNTN NPA <- area code (NPA)
ESA_HLCL NXX <- number sent when ESA is used (911)
ESA_INHN NO <- insert the HNDN?
ESA_APDN YES <- append DN to ESA_HLCL sent to 911
HLCL NXX
DIDN YES
HLOC
LSC
CLASS_FMT DN

 

[oceanSD]

Thanks for the response -- Here's the CLID -

ENTRY 0
  HNTN NNN       <--------(NPA)
  ESA_HLCL NNNNNNNNNN <---(MAIN NUMBER)
  ESA_INHN NO
  ESA_APDN NO
  HLCL NN       <---------(FIRST 2 DIGITS OF NXX)
  DIDN YES      
  HLOC
  LSC
  CLASS_FMT DN

ENTRY 1
  HNTN nnn             <---(NPA)
  ESA_HLCL NNNNNNNNNN  <---(MAIN NUMBER)
  ESA_INHN NO
  ESA_APDN NO
  HLCL NNNNNN       <-------(NXX + MAIN NUMBER)
  DIDN NO
  HLOC
  LSC
  CLASS_FMT DN

 

[911guru]

Your CLID tables look OK. The problem is most likely on the PSAP side.

The PBX only transmits CLID, and nothing else to the PSAP. This number is then cross referenced to a ALI Database (normally hosted by the Telco). What ever number you send MUST have a corresponding entry in the Telco ANI database. The code that the PSAP got was most likely an ANI FAIL code telling them that there was no ALI information for the number that was received.

Use of the CLIVER command in LD 20, and captures of the DCH messaging will help troubleshoot this, but in the end, whatever you send must be provisioned with an ALI record on the PSAP side.

911Guru

http://pbx-e911.com

 

[acewarlock]

First of all, I don't know of a way to STEP to a third route (will be great when they upgrade to 5.0 so we can just use an RLI!);"

Why can't you use RLI now?




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[tnphoneman]

As far as your routing you can do this now. 5.0 has nothing to do with this routing of the call. That is all done in your RLI programming. Entr 0 etc.

 

[911guru]

4.50 and prior ESA programming uses only an ESRT Route. The only way you can use multiple routes is via the STEP command.

5.00 allows you to define and ESA_RLI instead of an ESRT for each ERL.

911Guru

http://pbx-e911.com

 

[tnphoneman]

Wrong process on my part but it can still be accomplished.
Thanks for the info and correction.

 

[oceanSD]

Thanks for all the feedback - it looks like we're sending out the correct CLID and that it's just not in their database. I'll post more when I have an update... thanks again!

 

[johnpoole]

did not read all the replies, but to step to more then a second rdb add a rlb with as many entries as you need.. each one can point to a unique route and have it's own dgt table... i've used that on base to insure er calls even if both pri routes are down and all the local cot's are busy.. the last choice being a single ground start trunk in a route. the only other access to that was is from the switchroom via acod..

if i have that many ckts down i may need to talk to the provider (in harsh tones)

john poole
bellsouth business
columbia,sc

 

[911guru]

Problem there is that in 4.50 you can only send ESA calls to a single Route. 5.00 added the flexibility to send to an ESA_RLI.

Yes I know you can send ANY number to an RLI, but when you turn on ESA, and it is configured correctly, the ROUTE is your only choice.

It was an old way of thinking when we used to send 911 out on the copper trunks. In today's world, that is probably the last thing you want to do since there is no CLID modification available on 1FBs.

911Guru

http://pbx-e911.com

 

[oceanSD]

So, it looks like the only way around it is to NOT use ESA, set up 911 and 11 as SPN's routed to an RLI that has the PRI, then Centrex, then SIP trunks in it (Centrex second because it will at least send an associated CLID and SIP will not, at least, not that I know of). Would this be correct?