Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Question for Matt H.

Status
Not open for further replies.

maripaq

Technical User
Jul 29, 2003
138
CA
I programmed up and ESDN 911 in LD24 and setup an OSN key on a set and it all work fine. I only have a question about DFCL (Default ESA calling number). What is this number used for exactly? Is this the number we want to appear at the PSAP?

Thanks Matt.

Maripaq
 
I found this information in the NTP

ESA Calling Terminal Identification

Once a CLID entry has been assigned to a station set or to a route, it is up to the system administrator to maintain the database so that the CLID entry remains valid.
If an undefined CLID entry is being referenced when the system is trying to compose the ESA calling number, then the ESA calling number is set to the Customer’s Default Calling Number (DFCL). The following error message is
provided as an indication:
ERR9009 cust# dn clid_ent#

After the ESA calling number has been composed for an ESA or tandem ESA call, the number of digits in the ESA calling number is validated by the system. If the ESA calling number is found to contain an unexpected number of digits, then the ESA calling number is set to the Customer’s Default
Calling Number (DFCL). The following error message is provided as an indication:
ERR9012 cust# clid_ent# calling#

Regards,

Javier
 
If I remember my NTP and class correctly, yes. (I played with it in my BARS/NARS class...). DFCL is used if you aren't using CLID, or if your CLID entry is invalid on that station, etc. It is also sent when CLID is not used and ANI is not used.

The NTP references several times that The DFCL is a number that is sent out if ANI is not used. and it also says that:

If an undefined CLID entry is being referenced when the system is trying to compose the ESA calling number, then the ESA calling number is set to the Customer’s Default Calling Number (DFCL). The following rror message is provided as an indication:

ERR9009 cust# dn clid_ent#

After the ESA calling number has been composed for an ESA or tandem ESA call, the number of digits in the ESA calling number is validated by the system. If the ESA calling number is found to contain an unexpected number of digits, then the ESA calling number is set to the Customer’s Default Calling Number (DFCL). The following error message is provided as an indication:

ERR9012 cust# clid_ent# calling#


It's a bit confusing, but I think it's just the last resort of the switch to send an identifying number to the PSAP. Not the clearest answer, but it helps I hope. If you're using ISDN trunks I would definitely go to the trouble to set up your ESA_XXXX entries on teh CLID tables, *if* you are going to be subscribing to E911 from your telco. If you aren't, then they will just send the main number and address of that trunk group anyway. -Matt

Matt H.
TMC - KCMO, USA
 
Looks like Javier beat me to the punch! :) (I had to look it up...) -Matt :):)

Matt H.
TMC - KCMO, USA
 
You guys always seem to have all the answers... Thanks a lot guys, it is much appreciated [thumbsup2]

Maripaq
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top