Caller Id Name & Number not Displaying - CS1000 7.6

[babytech2009]

All,


Hello, I have an issue that started occuring at exsisting site. The name and number are not displaying when calls come in.

It shows 8000-12 or 8000-1 for example.

The Carrier has not been changed and I went to the carrier they state it is something on our system that needs changed to display incoming caller name and number.It was working before and is currently for the past few weeks a new issue that it does not show on any phone incoming caller information.

Would anyone be able to assist on where to go to find the issue and how to change it?


I have checked RDR and Clid in LD 21

Print out of phone I changed from CNID to CNIA did not resolve issue.

DES
TN 000 0 07 10 VIRTUAL
TYPE 3904
CDEN 8D
CTYP XDLC
CUST 0
MRT
ERL 0
FDN 73699
TGAR 1
LDN NO
NCOS 3
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
SCPW
CLS UNR FBD WTA LPR MTD FNA HTA TDD HFA GRLD CRPD STSD
MWA LMPN RMMD AAD IMD XHD IRA NID OLA VCE DRG1
POD SLKD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNIA CDCA MSID DAPA BFED RCBD >>>>changed CNID to CNIA still did not display incoming caller number
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDA CFXA ARHD FITD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
DDGA NAMA
DRDD EXR0
USMD USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC MCBN
CDMR PRED RECD MCDD T87D SBMD
PKCH CROD ELCD VMSA
CPND_LANG ENG
RCO 0
BFTN 000 0 06 00
HUNT 73699
LHK 1
LPK 1
PLEV 02
PUID
UPWD
DANI NO
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 SCR 73642 0 MARP
CPND
NAME
XPLN 24
DISPLAY_FMT FIRST,LAST
01 SCR 23642 0 MARP
CPND
NAME
XPLN 24
DISPLAY_FMT FIRST,LAST
02 ADL 16
03 ADL 16
04 ADL 16 73624
05 ADL 16 919723426655
06 ADL 16
07 ADL 16
08 ADL 16
09 ADL 16
10 ADL 16
11 ADL 16
12
13
14
15
16 MWK 73699
17 TRN
18 AO6
19 CFW 16 912676321626
20 RGA
21 PRK
22 RNP
23 SCC 0024
24 PRS
25 CHG
26 CPN
27 CLT
28 RLT
29
30
31
DATE 23 FEB 2015


>ld 21


TYPE NET_DATA
CUST 00
OPT RTD
AC1 INTL NPA SPN NXX LOC
AC2
FNP YES
ISDN YES
VPNI 0
PNI 0
PINX_DN
MBG 0
BSGC 65535
PFX1
PFX2
HLOC
LSC
RCNT 5
PSTN NO
TNDM 15
PCMC 15
SATD 1
OCLI NO
MSCO_DP PRV
DITI NO
TRNX YES
EXTT YES
FTOP FRES
VNR NO
NIT 8
FOPT 6
CNTC
NATC
INTC
ELC NO

~~~~~~~
CLID


ENTRY 0
HNTN 443
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 75
DIDN YES
DIDN_LEN 0
HLOC
LSC
CLASS_FMT DN

 

[KCFLHRC]

8000 is your route ACOD

 

[babytech2009]

KCFLRC,

Does that need changed on the PBX system(my end) or by the carrier?

 

[KCFLHRC]

You don't need to change it. My guess is something has changed with the carrier. This is a PRI, right? With a D-channel?

 

[babytech2009]

That is correct its a PRI and D Channel.

I thought it would be the carrier side since I dont make changes to the system.

However when engaged the carrier they stated its something on the PBX. Which didnt make sense.

 

[babytech2009]

And here is the response I get.

Hi

The carrier did not make any changes. When incoming caller id is showing the trunk the call is coming in on, it's something to do with the programming in the equipment. The carrier does not have the capability to program incoming caller id to show what trunk the call is coming in on.

Something in the equipment must have reverted back.

Thank you,


UNBELIEVABLE!

 

[KCFLHRC]

This is typically what you will see on a non PRI circuit, Route and member #. Have you looked at the d-channel and make sure it is established? Maybe bounce the circuit an d-channel.

 

[babytech2009]

KCFLHRC,

I may have to schedule a bounce from the PBX. The site is 24/7 so I am sure it will have to be done after hours.

 

[KCFLHRC]

What happens when you turn on inbound d-channel monitoring? Do you see the call hit the circuit and does it have caller id information with it?

 

[babytech2009]

This is what I show when I have MSGI enabled.


>ld 96
DCH000
.enl ms
DCH017


.enl msgi
DCH000
.stat dch
DCH 020 : OPER EST ACTV AUTO DES : local
DCH 052 : OPER EST ACTV AUTO DES : Local2
.enl msgi 20
OUTPUT TARGETS: TTY
.enl msgi 52
OUTPUT TARGETS: TTY
.
DCH000
.
DCH 20 UIPE_IMSG CC_PROCEED_IND REF 00005210 CH 20 23 TOD 12:50:30 CK 12D8F8BC

DCH 20 UIPE_IMSG CC_RELEASE_IND REF 00005210 CH 20 23 TOD 12:50:32 CK 12D8FEE2

 

[KCFLHRC]

Something is goofy. I don't see any inbound caller information, name or number.

 

[KCFLHRC]

Actually I think the information is coming out on the monitor in HEX, does this number mean anything to you, 316209340

 

[babytech2009]

I also put on MSGO as well.

OUTPUT TARGETS: TTY
.
DCH 52 UIPE_IMSG CC_SETUP_IND REF 0000046B TOD 12:58:52 CK 12E847A9
CALLED #:3676 NUM PLAN: UNKNOWN TON: UNKNOWN

DCH 52 UIPE_OMSG CC_PROCEED_REQ REF 0000846B CH 52 1 TOD 12:58:52 CK 12E847AB

DCH 52 UIPE_OMSG CC_ALERT_REQ REF 0000846B CH 52 1 TOD 12:58:52 CK 12E847AB
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 52 UIPE_OMSG CC_SETUP_RESP REF 0000846B CH 52 1 TOD 12:58:56 CK 12E85E17
PROGRESS: TERMINATING END IS NOT ISDN

DCH 52 UIPE_IMSG CC_SETUPCOMP_IND REF 0000046B CH 52 1 TOD 12:58:56 CK 12E85E87

 

[babytech2009]

KCFLRC

I dont see any as well which is really odd.

The number 316209340 unless it is a phone number incoming from Kansas I wouldnt know.I assume Kansas as I looked it up online.
I remote to the sites so I do not get to interact with the field to speak to them directly.

It has been going on for about a month with no caller id name or number.

I havent made any major changes to the system unless moving, or assigning to the person.

Here is some more that just came through.

PROGRESS: TERMINATING END IS NOT ISDN

DCH 52 UIPE_IMSG CC_SETUPCOMP_IND REF 0000046B CH 52 1 TOD 12:58:56 CK 12E85E87

TIM000 13:00 23/2/2015 CPU 0

DCH 20 UIPE_OMSG CC_SETUP_REQ REF 00005211 CH 20 23 TOD 13:03:29 CK 12F0C47C
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:4437573643 NUM PLAN: E164 TON: NATL
CALLED #:18884133727 NUM PLAN: E164 TON: NATL

DCH 20 UIPE_IMSG CC_PROCEED_IND REF 00005211 CH 20 23 TOD 13:03:29 CK 12F0C749

DCH 20 UIPE_IMSG CC_PROGRESS_IND REF 00005211 CH 20 23 TOD 13:03:31 CK 12F0D32A
PROGRESS: CALL IS NOT END TO END ISDN

DCH 20 UIPE_IMSG CC_ALERT_IND REF 00005211 CH 20 23 TOD 13:03:33 CK 12F0D8A8
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 20 UIPE_IMSG CC_SETUP_CONF REF 00005211 CH 20 23 TOD 13:03:35 CK 12F0F174
PROGRESS: TERMINATING END IS NOT ISDN

 

[KCFLHRC]

It sure like's you are sending out CLID information but not receiving any.

 

[babytech2009]

KCFLRC

Yes then i just saw another one..

So you still think bouncing the circuits would help?

DCH 20 UIPE_OMSG CC_SETUP_REQ REF 00005212 CH 20 22 TOD 13:15:35 CK 1306E194
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:4437573754 NUM PLAN: E164 TON: NATL
CALLED #:4106893670 NUM PLAN: E164 TON: NATL

 

[KCFLHRC]

I would try bouncing them if truly nothing has changed. But I have my doubt's, I think the carrier changed something.

 

[babytech2009]

KCFLRC,

I will attempt a circuit bounce and let post on here if it worked or not.

I have assumed from the begining that this is all carrier related.



Thank you as always!

 

[cs1ktech]

I seem to remember having this issue in the past after an upgrade...was it a recently upgraded to 7.6?
Turns out there was a patch in my case....

 

[babytech2009]

KCFLRC and Cs1ktech,

It was an issue with the carrier, they turned off caller id and name display. I skipped using GSA since they are no help. I created a ticket directly with the carrier and had a technician check the PRI configuration.

THank you both for your assistance.

I figured it was the carrier since it worked the month prior then stopped. I try not to create more work by changing out any PBX programming.