Weird Caller ID

[MorpheusWin2K]

I'm posting this a 2nd time in hopes on getting or finding a fix. I'd really like to get the caller id working the way it used too, with name and number being displayed of the calling party.

We're running Succession 4.5 with MM12 on an Option 11C. We have 1 PRI which has our main number 201-555-xxxx, and just last week I added 2 other numbers that point to an analog DN for Faxes. The carrier is sending over 10 digits (these use to be our pot's lines). I created an IDC table in LD 49 pointing these numbers to the appropriate DN for faxing. I also had to point our main number to our ATDN, which is 7700. Everything works great, except now, whenever we get a call in, our phone displays show the name, along with our main number followed by the calling party number and it's very hard to pick out who is calling. What could have made this happen and what's the fix?

Thanx

 

[phonz1]

have you turned on the dchannel messaging for an inbound route yet? I went back and read your old post and I remember asking you that. Also, I told you that we don't have control over inbound numbers, that is controlled by the lec

 

[MorpheusWin2K]

I did do the enl msgi and saw the message before and after the IDC table was put in place and they both showed the same.

Also everything worked perfectly before I pointed our main number to the ATDN, which I needed to do in order to get it working again.

I'm stuck.

Thank You

 

[acewarlock]

I don't use IDC, I have the Telco Point the old numbers to our main number DID. I only have the telco send me the last 4 digits of the DID. Does the Telco send you more that 10 Digits for all your DID numbers or just the last 4?


You said your also pointing your main number to your ATDN, don't you have a Recpt?




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.

 

[pronei]

What level of msgo/msgi msging are you displaying?

0, 1 or 2?

Level 2 will show you EVERYTHING that comes across your DCH, use a HEX to ASCII conversion to see what is actually coming across your DCH.

To set different DCH monitoring modes:

LD 96
set x y mon z

x = msgi (inbound DCH) or msgo (outbound DCH)
y = dch you want to monitor
z = level 0,1,2)

Use Level 2 monitoring only during low call volume. It will put out a LOT of data.

 

[acewarlock]

Quote: Morpheuswin2k

I did do the enl msgi and saw the message before and after the IDC table was put in place and they both showed the same.

Also everything worked perfectly before I pointed our main number to the ATDN, which I needed to do in order to get it working again.

-----------------------------------------------------------
Don't tell us you did something, show us what was the DCH Monitoring output by Sacnning it and posting it here. Until you help us by posting the results of the DHC, where just guessing.




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.

 

[MorpheusWin2K]

Here is what the DCH channel looks like utilizing the msgi on all 3 levels:

Level 0

DCH 3 UIPE_IMSG CC_SETUP_IND REF 00001101 CH 1 1 TOD 8:20:38 CK CC7E2D70
CALLED #:2014897400 NUM PLAN: E164 TON: NATL
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:9734762412 NUM PLAN: E164 TON: NATL

DCH 3 UIPE_IMSG CC_FAC_IND REF 00001101 CH 1 1 TOD 8:20:38 CK CC7E304C

DCH 3 UIPE_IMSG CC_SETUPCOMP_IND REF 00001101 CH 1 1 TOD 8:20:40 CK CC7E35F2

DCH 3 UIPE_IMSG CC_RELEASE_IND REF 00001101 CH 1 1 TOD 8:20:56 CK CC7EB714

Level 1

DCH 3 UIPE_IMSG CC_SETUP_IND REF 00001081 TN 00001404 CH 00000001 TOD 8:18:54
CK CC7B0550
2F 00 01 00 62 00 08 02 01 21 2E 00 01 07 13 00
81 90 00 00 A2 00 09 09 0D 00 A9 00 83 00 01 00
01 00 03 10 03 00 A1 00 0A 00 02 0A 01 04 08 09
07 04 0A 0A 37 1A 19 00 9F 00 8B 01 00 01 00 A1
0F 02 01 01 06 07 2A 86 48 CE 15 00 04 0A 01 00
1E 04 03 00 82 83 05 10 07 00 21 83 0A 00 09 07
03 04 07 06 02 04 01 02

DCH 3 UIPE_IMSG CC_FAC_IND REF 00001081 TN 00001404 CH 00000001 TOD 8:18:56 C
K CC7B086A
2F 00 01 00 2A 00 08 02 01 21 23 00 37 22 19 00
9F 00 8B 01 00 01 00 A1 17 02 01 01 02 01 00 80
0F 4E 45 57 20 4A 45 52 53 45 59 20 20 20 20 20

DCH 3 UIPE_IMSG CC_SETUPCOMP_IND REF 00001081 TN 00001404 CH 00000001 TOD 8:1
8:56 CK CC7B098E
2F 00 01 00 06 00 08 02 01 21 38 00

DCH 3 UIPE_IMSG CC_DISC_IND REF 00001081 TN 00001404 CH 00000001 TOD 8:19:16
CK CC7BAAB7
2F 00 01 00 0E 00 08 02 01 21 22 00 07 05 05 00
84 00 90 00

DCH 3 UIPE_IMSG CC_RELEASE_CONF REF 00001081 TN 00001404 CH 00000001 TOD 8:1
9:16 CK CC7BAB66
2F 00 01 00 06 00 08 02 01 21 2B 00

Level 2

DCH 3 UIPE_IMSG CC_SETUP_IND REF 00000F01 CH 1 1 TOD 8:12:56 CK CC70098E
PRIM HDR: 2F 00 01 00 62 00
MSG HDR: 08 02 01 1E 2E 00
BCAP: 01 07 13 00 81 90 00 00 A2
CHID: 09 09 0D 00 A9 00 83 00 01 00 01
CAD#: 03 10 03 00 A1 00 0A 00 02 0A 01 04 08 09 07 04
0A 0A
GFFAC: 37 1A 19 00 9F 00 8B 01 00 01 00 A1 0F 02 01 01
06 07 2A 86 48 CE 15 00 04 0A 01 00
PROGI: 1E 04 03 00 82 83
CLG#: 05 10 07 00 21 83 0A 00 09 07 03 04 07 06 02 04
01 02

DCH 3 UIPE_IMSG CC_FAC_IND REF 00000F01 CH 1 1 TOD 8:12:56 CK CC700CFA
PRIM HDR: 2F 00 01 00 2A 00
MSG HDR: 08 02 01 1E 23 00
GFFAC: 37 22 19 00 9F 00 8B 01 00 01 00 A1 17 02 01 01
02 01 00 80 0F 4E 45 57 20 4A 45 52 53 45 59 20
20 20 20 20

DCH 3 UIPE_IMSG CC_SETUPCOMP_IND REF 00000F01 CH 1 1 TOD 8:12:58 CK CC701C9D
PRIM HDR: 2F 00 01 00 06 00
MSG HDR: 08 02 01 1E 38 00

DCH 3 UIPE_IMSG CC_RELEASE_IND REF 00000F01 CH 1 1 TOD 8:13:14 CK CC70A17E
PRIM HDR: 2F 00 01 00 06 00
MSG HDR: 08 02 01 1E 2C 00

I hope that this helps. Really would like to get this resolved. If I need to print anything else, just let me know.

Thank You

 

[phonz1]

I would say your next call would be to the Telco

 

[pronei]

These are common outputs for Level 2 DCH Messaging and according to your DCH, your not receiving any CLID from your PRI provider.

Level 2 output identifies the individual Information Elements (IE) in the messages and their hexadecimal values. The possible IEs are:

1 BCAP = bearer capability
2 CAST = call state
3 CHGA = charge advice
4 CHID = channel ID
5 CHST = change status
6 CLED = called number
7 CLES = called party subaddress
8 CLNG = calling number
9 CLNS = calling party subaddress
10 CNS5 = codeset 5 connected number subaddress
11 CON# = connect number
12 CON5 = codeset 5 connected number
13 CSE = cause

14 DES6 = codeset 6 Destination IE
15 DISP = display
16 FAC = facility IE for codeset 0
17 FAC6 = codeset 6 facility IE
18 FIND = feature Indication
19 HLYR = higher layer compatibility
20 INFO = information request
21 KYPD = keypad
22 LLYR = low layer compatibility
23 LS5 = locking Shift to codeset 5
24 LS6 = locking shift to codeset 6
25 LS7 = locking Shift to codeset 7

26 NLS5 = codeset 5 non-locking shift
27 NLS6 = codeset 6 non-locking shift
28 NLSO = non-locking shift to codeset 0
29 NOTI = notify indicator
30 NSF = network specific facility
31 ORG# = originating called number
32 ORG6 = codeset 6 Originating IE
33 PROG = progress indicator
34 RDG6 = codeset 6 redirecting number
35 REDG = redirecting number
36 REDN = redirection number

37 RETR = codeset 6 reason for return
38 RSTI = restart indicator
39 SHFT = shift
40 SIGN = signal
41 TACG = codeset 6 TTC advice charge
42 TNS = transit network selection
43 UNKN = unknown

44 UUI = user-user information

 

[pronei]

What kind of switch and which software release are we dealing with here?

 

[pronei]

Scratch that last message, I see 4.5 w/ MM12

Anyway, your still getting DCH msgs that I've never seen before. All the hex values listed translate to nothing legible. You need to call your Telco about this. Have them set a call trace and tell you exactly whats going through the DCH on their side.