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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

911 bad CLID-how did this happen? 1

Status
Not open for further replies.

MikeSayers

IS-IT--Management
Jul 23, 2015
10
US
Got an email from our telco saying they received a 911 call from our PRI that IDd as xxx-2999, which is not in our DID ranges. The call was made from the attendant console.

What happened, and how do I prevent it from happening again? Relevant(?) data below, let me know if you need anything else.

REQ: prt
TYPE: clid
CUST 0
SIZE 256
RNGE

INTL

ENTRY 0
HNTN
ESA_HLCL aaaxxx (same as bad ID above, good within DID ranges)
ESA_INHN NO
ESA_APDN YES
HLCL 919209
DIDN YES
DIDN_LEN 0
HLOC
LSC
CLASS_FMT DN

ENTRY 1
HNTN
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL aaayyy3051 (main number)
DIDN NO
DIDN_LEN 0
HLOC
LSC
CLASS_FMT DN

ENTRY 2
HNTN
ESA_HLCL aaazzz (2nd DID range)
ESA_INHN NO
ESA_APDN YES
HLCL 919464
DIDN YES
DIDN_LEN 0
HLOC
LSC
CLASS_FMT DN


REQ: prt
TYPE: dnb
CUST 0
DN 2999
DATE
PAGE
DES

DN 2999
TYPE LDN

REQ: prt
TYPE: ldn
TYPE LDN_DATA
CUST 0

TYPE LDN_DATA
CUST 00
OPT XLDN
DLDN NO
LDN0 2999
LDN1
LDN2
LDN3
LDN4
LDN5
ICI 00 CFB
ICI 01 CFN
ICI 02 DF0
ICI 03 DL0
ICI 04 INT
ICI 05 RLL
ICI 06
ICI 07
ICI 08
ICI 09

REQ: prt
TYPE: att
TYPE ATT_DATA
CUST 0

TYPE ATT_DATA
CUST 00
OPT AHD BIND BIXA BLA
DNX IC1 ITG IDP XLF XBL
MWUD LOD
REA SYA ATDA
ATDN 0
NCOS 7
CWUP YES
CWCL 0 0
CWTM 0 0
CWBZ YES YES
MATT NO
RTIM 30 30 30
ATIM 0
AQTT 30
AODN
SPVC 00
SBLF NO
RTSA RSAD
SACP NO
ABDN NO
IRFR NO
XRFR NO
IDBZ NO
PBUZ 02 10
ICI 00 CFB
ICI 01 CFN
ICI 02 DF0
ICI 03 DL0
ICI 04 INT
ICI 05 RLL
ICI 06
ICI 07
ICI 08
ICI 09
RICI
 
You mean the TN?
REQ: prt
TYPE: tnb
TN 0 1 9 0
DATE
PAGE
DES

TN 000 1 09 00 VIRTUAL
TYPE 2250
CDEN 8D
CTYP XDLC
CUST 0
ERL 0
SGRP 0
SETN 000 1 09 01
ANUM 01
IADN
SSU 0000
ICDR ICDD
ABAN ABDD
CPND CNDA
AADN
DNDI DNDA
DAPC DAPA
LANG 00
KEY 00 BVR
KEY 01 BIN
KEY 02 EES
KEY 03 MDT
KEY 04 MTM
KEY 05 SSC 0000
KEY 06 RTC
KEY 07 ADL 16
KEY 08 ADL 16
KEY 09 ADL 2026
KEY 10
KEY 11
KEY 12
KEY 13
KEY 14
KEY 15
KEY 16
KEY 17
KEY 18
KEY 19
DATE 20 NOV 2009

REQ: prt
TYPE: tnb
TN 0 1 9 1
DATE
PAGE
DES

TN 000 1 09 01 VIRTUAL
TYPE 2250
CDEN 8D
CTYP XDLC
CUST 0
PRTN 000 1 09 00
 
Seems to be outputting the LDN Data for some reason. There is no where to assign a CLID table to a console that I know of.
 
The call was made from the console, the console is 2999 - working as designed.

The console uses clid 0. Change CLID 0 DIDN to NO and set it to outpulse your main number and have everyone else use a different CLID entry with DIDN set to yes
 
Argh, there are about 150 phones around here using CLID 0; no way to make the console use # 1?
 
Sorry, 0 is the default clid table and it's used by the system, i.e. ACDN, console and a couple of others that I can't remember at the moment.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top