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

ESA ERL sending digits 9111

Status
Not open for further replies.

csomb42

Technical User
Apr 17, 2015
8
0
0
US
Gentlemen/Ladies,
I need some ESA/ERL educating. We recently converted from AT&T PRI's to Consolidated Communications/Surewest. After the conversion, 911 calls received an announcement from Consolidated stating the number was not recognized. D-Channel messages showed called # as 9111.

This is the first time I've worked with the CS1K Rls 7.5 and the ERL's so I could be missing something really simple.

I have ERL's 1 thru 8 built (not by me, but by the vendor that did the upgrade). If I print clidver it shows the called# as 9111 for all of the sets and ERL's. In order to get 911 working with my limited knowledge, I disabled all of the ERL's and let the 911 use the default ESA block. After disabling all of the ERL's the called# field shows 911 and the calls complete as they should. I would like to get everything working correctly again and that is where I need the help.

Where is the extra 1 coming from and how do I get rid of it in order to complete the call like I am with the default ESA block? All of the ERL's use a different RLI pointing to the same route and using the same DMI. The DMI deletes 3 and inserts 911.

Before disabling ERL's

TYPE: clidver

DN KEY TN ERL CTYP CLID ROUTE CALLED#
------- ------ ----------- ----- ------- ------------------ ----- ----------------
1000 01 SCR 016 1 08 02 1 911 C 1000 I 091 9111
1000 01 SCR 012 1 01 12 1 911 C 1000 I 091 9111
1000 01 SCR 012 0 10 08 1 911 C 1000 I 091 9111
1000 01 SCR 012 0 09 04 1 911 C 1000 I 091 9111

DCH 56 UIPE_OMSG CC_SETUP_REQ REF 000054EF CH 55 17 TOD 22:18:53 CK B7A07161
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:8650 NUM PLAN: E164 TON: LOCL
CALLED #:9111 NUM PLAN: E164 TON: LOCL

DCH 56 UIPE_IMSG CC_STATUS_IND REF 000054EF CH 55 17 TOD 22:18:53 CK B7A071FA
CAUSE: #100 - INVALID IE CONTENTS

STATE:CALL INIT

ESA009 CLID 8650

After disabling ERL's

REQ: prt
TYPE: clidver

DN KEY TN ERL CTYP CLID ROUTE CALLED#
------- ------ ----------- ----- ------- ------------------ ----- ----------------
1000 01 SCR 016 1 08 02 0 911 C 1000 R 020 911
1000 01 SCR 012 1 01 12 0 911 C 1000 R 020 911
1000 01 SCR 012 0 10 08 0 911 C 1000 R 020 911
1000 01 SCR 012 0 09 04 0 911 C 1000 R 020 911
1201 008 0 05 07 0 911 C 1201 R 020 911
1202 004 0 07 01 0 911 C 1202 R 020 911
1203 004 0 07 02 0 911 C 1203 R 020 911

I can provide additional print outs if anyone has a good idea where my issue is.

Thanks

Mark
 
Print the ERLs in LD 117 and see if they using an RLI.
If they are then you can print the RLI in LD 86.
Possibly something to do with the CTYP or DMI in the RLI.
 
pick a set to do the testing in LD 117 do a LOCRPT on that set and confirm the ERL its assigned. Then like Stanley says prt the ERL and take a look at the routing assigned. May be worth looking at ESA in 24 see what ESDN's are configured
 
ERL's 1 and 2 are the only ones using the new PRI's from CCI. I printed the following for everyone:

REQ prt
TYPE esa
CUST 0

CUST 0

ENTR 0 - Only one configured
ESDN 911
ESRT 20
DDGT 911
MISDIAL_PREVENTION NO
DFCL 9137914200
OSDN 4444
VOLO_COUNT 0

=> prt erl
_____________________________________________________________________________________________________________
| ERL |State| Site Name | Location Desc |RT#|RLI|AC |Prepend Digits | Static ELIN | OSDN |
|-----+-----+--------------------+--------------------+---+---+---+---------------+----------------+--------|
| 1| DIS |OMC_MAIN |MAIN HOSPITAL | | 91|AC1| | 9137914200| |
|-----+-----+--------------------+--------------------+---+---+---+---------------+----------------+--------|
| 2| DIS |DOCTOR_BLD_2 |DOCTOR_BLD_2 | | 92|AC1| | 9133248500| |
|-----+-----+--------------------+--------------------+---+---+---+---------------+----------------+--------|


RLI 91
ELC NO
ENTR 0
LTER NO
ROUT 20
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 0
DMI 3 -----> Both ERL 1 and 2 use the same trunks and same DMI
CTBL 0
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5

REQ prt
CUST 0
FEAT dgt
DMI 3

DMI 3
DEL 3
ISPN NO
INST 911
CTYP NCHG

My test set
=> locrpt dn 8650
____________________________________________________________________________________________________________________________
| | Prime | | | | | | | Location |MAN ND |
| TN | DN | Type |State| HWID | Signaling IP | ERL | ECL | Description |UPD UPD|
|-----------+-------+--------+-----+---------------------+------------------------+-----+-----+--------------------+---+---|
|240 0 4 30| 8650|1140 |REG |18f81547bc51576625 |10.240.162.75:5000 | 1| 0|MAIN HOSPITAL |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|
|240 0 5 30| 8650|2050PC |UNREG|1228b2bd1ec6836606 |10.100.253.64:5000 | 1| 0|MAIN HOSPITAL |YES|NO |
|--------------------------------------------------------------------------------------------------------------------------|

Is it possible that since this was working with AT&T that CCI has some sort of misdial prevention active and they are not processing the call as they say they should be with 911 and ignoring the 4th digit? Just a side thought

Thanks

Mark
 
I got nuthin'.
The only thing I thought was strange was the DEL 3 INST 911 (I just use RLI 0 for the ERL routes). But I tried the same configuration as yours and the CLIDVER still shows 911.
I don't see where the extra 1 is coming from.
 
Thanks StanleySteamer. I'm still looking and have requested that Surewest go over their config as well since AT&T has been processing the same call for the past 2 years.

Mark
 
Some providers will reject a call on a PRI if it isn't a valid number (i.e. an extra digit). To me there is a problem in the CS1000.
 
Like Stanley said why would you remove 3 digits to re-insert them I would alter the DMI to DEL 0 INST x . Is there any Numzone/ZFDP stuff configured in LD 117. Are users only dialing 911 or is 9911 also available?
 
bignose - I can't speak to why the previous person that was administering this PBX would use a DMI like that. I too thought it was strange. The ERL's are all disabled right now just I could get 911 operational using the default ESA block. There are no Numzones or ZFDP configured. Users can dial 911 or 9911. I changed the DMI to DEL 0/INST x. The call still does not complete, but now the DChannel messages and clidver print both show 9911 instead of 9111. So the DMI change did have an affect on it.

Mark
 
Just a guess... by using the same DMI that delete 3 and insert 3... if I dial 9111, it delete 3 which would be 911 and insert 3, which would created 9111
 
UPDATE - Resolved
yyrkrron, we are thinking along the same lines. Since changing the DMI to DEL 0 and INST nothing got me 9911 instead of 9111, I change the DMI again to DEL 4 and INST 911 and that resolved my issue. I'm still not sure where in the programming (ESA, ERL, etc.) it was picking up the extra digit, but changing the DMI corrected the issue.

Thanks everyone for your input.

Mark
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top