PRI Caller ID help - PBX Info :: Your Free PBX, PABX and Telephone Information Resource

11-29-2004, 01:19 PM

I have a customer who has purchased a Cisco switch for VOIP and we have networked them in via PRI. When they make a call within the network caller ID information shows up on the called set, but when they call outside the network the billing number shows up. I've checked everything I can think of, tried making some minor changes to a few things in the route and still just getting the billing information on caller ID outside the Net. If anybody has any suggestions of anything I might have over looked Id apreciate it. I can post printouts as well just let me know what you need.

Thanks

HCJes · 11-29-2004, 01:22 PM

Our Telco does not offer us the ability for caller ID over PRI, therefore my knowledge is very limited in this. Do you have the D-CH setup. This is needed for Call ID info.

11-29-2004, 01:26 PM

Yes DCH is present

jack · 11-29-2004, 01:28 PM

If a Nortel phone calls off net is proper CLID sent?

11-29-2004, 01:33 PM

Yes the phones on the opt81 are sending out proper caller ID info.

jack · 11-29-2004, 01:36 PM

Can you post a level 0 & Level 2 D-channel msg. trap from both a Nortel & Cisco phone calling off net?

How are the trunks between the Cisco & *1 setup, i.e, ties?

11-29-2004, 01:40 PM

Yes there set up as Tie trunks, and give me a few minutes and I'll post some DCH info

slagburn · 11-29-2004, 02:17 PM

Quick thread high-jack to post an observation I made of level 2 DCH monitoring, without having the right tools or charts I really can't tell what each of the fields do so it's just a guess.

Here is a setup message on an NI-2 PRI from a digital station with CLS CLBA... I observed this same call at the Monitor 0 level and confirmed that CLID was sent however no CLID appeared on the phone I was calling.

DCH 12 UIPE_OMSG CC_SETUP_REQ REF 00000021 CH 3 23 TOD 11:46:00 CK 014ABCB0
PRIM HDR: 01 00 01 00 55 00
MSG HDR: 08 02 21 00 0E 00
BCAP: 01 0D 13 00 01 10 00 00 22 00 00 00 00 00 00
CHID: 09 09 0F 00 69 01 03 00 01 00 17
PROGI: 1E 04 03 00 01 83
CLG#: 05 0D 07 00 41 20 07 00 04 03 03 06 0A 0A 0A
CAD#: 03 0D 03 00 41 00 07 00 09 02 0A 04 08 03 07
SNCMP: 23 00
SRVIN: 24 04 03 00 01 01
PCATG: 1D 03 01 00 01

This is the same call from the same phone to the same phone across the same PRI but with CLS CLBD which is the default, in this senario the CLID was presented to the phone that I called.

DCH 12 UIPE_OMSG CC_SETUP_REQ REF 00000020 CH 3 23 TOD 11:45:26 CK 0149B36F
PRIM HDR: 01 00 01 00 55 00
MSG HDR: 08 02 20 00 0E 00
BCAP: 01 0D 13 00 01 10 00 00 22 00 00 00 00 00 00
CHID: 09 09 0F 00 69 01 03 00 01 00 17
PROGI: 1E 04 03 00 01 83
CLG#: 05 0D 07 00 41 00 07 00 04 03 03 06 0A 0A 0A
CAD#: 03 0D 03 00 41 00 07 00 09 02 0A 04 08 03 07
SNCMP: 23 00
SRVIN: 24 04 03 00 01 01
PCATG: 1D 03 01 00 01

The only difference I can find between the two is the bold portion of the CLG# field leading me to believe this must be some sort of call party privacy flag as I saw CLID go to the CO on both calls however only saw it once at the far end.

Just something to think about and hopefully someone can confirm what I'm seeing or tell me to leave it to the experts.

11-29-2004, 03:01 PM

Dch 29 is for the PRI betwwen the Meridian and the Cisco(where we have the problem)

Dch 14 is a PRI to the local CO

MSGI/MSGO MON 1:
DCH 29 IMSG CALLPROC REF 0000000D TN 00001554 CH 0000000D CK 07E76A6B
DCH 29 I 07E76A6B
2F 03 00 09 08 01 8D 02 05 03 A9 83 0D

DCH 29 IMSG ALERT REF 0000000D TN 00001554 CH 0000000D CK 07E76AA3
DCH 29 I 07E76AA3
2F 03 00 04 08 01 8D 01
enl msgo 29
.
DCH 29 IMSG CONNECT REF 0000000D TN 00001554 CH 0000000D CK 07E7AD69
DCH 29 I 07E7AD69
2F 03 00 04 08 01 8D 05

DCH 29 OMSG CONN ACK REF 0000000D TN 00001554 CH 0000000D CK 07E7AD6A
DCH 29 O 07E7AD6A
01 03 00 04 08 01 0D 0F

DCH 29 IMSG DISC REF 000086C1 TN 00001558 CH 0000000E CK 07E7BBE4
DCH 29 I 07E7BBE4
2F 03 00 09 08 02 06 C1 07 02 02 80 90

DCH 29 OMSG RELEASE REF 000086C1 TN 00001558 CH 0000000E CK 07E7BBE5
DCH 29 O 07E7BBE5
01 03 00 05 08 02 86 C1 4D

DCH 29 IMSG REL COMP REF 000086C1 TN 00001558 CH 0000000E CK 07E7BC4B
DCH 29 I 07E7BC4B
2F 03 00 05 08 02 06 C1 0B

DCH 29 IMSG DISC REF 00000014 TN 00001590 CH 00000014 CK 07E7BD46
DCH 29 I 07E7BD46
2F 03 00 08 08 01 94 07 02 02 80 90

DCH 29 OMSG RELEASE REF 00000014 TN 00001590 CH 00000014 CK 07E7BD48
DCH 29 O 07E7BD48
01 03 00 04 08 01 14 4D

DCH 29 IMSG REL COMP REF 00000014 TN 00001590 CH 00000014 CK 07E7BDAE
DCH 29 I 07E7BDAE
2F 03 00 04 08 01 94 0B

MSGI/MSGO MON 2:
DCH 29 IMSG DISC REF 000086C2 CH 21 20 TOD 13:36:04 CK 07EA3BE3
HEADER:2F 03 00 09 08 02 06 C2 45
CSE :08 02 80 90

DCH 29 OMSG RELEASE REF 000086C2 CH 21 20 TOD 13:36:04 CK 07EA3BE4
HEADER:01 03 00 05 08 02 86 C2 4D

DCH 29 IMSG REL COMP REF 000086C2 CH 21 20 TOD 13:36:04 CK 07EA3C42
HEADER:2F 03 00 05 08 02 06 C2 5A

MSGI/MSGO MON 1:
DCH 14 UIPE_IMSG CC_SETUP_IND REF 00004602 TN 00003B14 CH 00000005 TOD 13:38:0
4
2F 00 01 00 5C 00 08 02 02 8C 2E 00 01 07 13 00
81 90 00 00 A2 00 09 09 0D 00 A9 00 83 00 01 00
05 00 03 0A 03 00 80 00 04 00 07 04 0A 01 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 08 01 07 07 09 08 03 08
04 04

DCH 14 UIPE_IMSG CC_FAC_IND REF 00004602 TN 00003B14 CH 00000005 TOD 13:38:04
2F 00 01 00 2A 00 08 02 02 8C 23 00 37 22 19 00
9F 00 8B 01 00 01 00 A1 17 02 01 01 02 01 00 80
0F 55 4C 4D 45 52 20 4D 49 43 48 45 4C 4C 45 20

DCH 14 UIPE_IMSG CC_SETUP_IND REF 00004682 TN 00003B1C CH 00000007 TOD 13:38:1
0
2F 00 01 00 5C 00 08 02 02 8D 2E 00 01 07 13 00
81 90 00 00 A2 00 09 09 0D 00 A9 00 83 00 01 00
07 00 03 0A 03 00 80 00 04 00 03 08 02 07 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 04 0A 02 03 09 01 07 07
06 02

DCH 14 UIPE_OMSG CC_PROCEED_REQ REF 0000C682 TN 00003B1C CH 00000007 TOD 13:38
:10

DCH 14 UIPE_OMSG CC_ALERT_REQ REF 0000C682 TN 00003B1C CH 00000007 TOD 13:38:1
0
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 14 UIPE_IMSG CC_FAC_IND REF 00004682 TN 00003B1C CH 00000007 TOD 13:38:10
2F 00 01 00 2A 00 08 02 02 8D 23 00 37 22 19 00
9F 00 8B 01 00 01 00 A1 17 02 01 01 02 01 00 80
0F 42 54 4E 52 48 20 38 38 54 48 20 53 54 20 50

DCH 14 UIPE_IMSG CC_DISC_IND REF 00004482 TN 00003B94 CH 00000015 TOD 13:38:1
2
2F 00 01 00 0E 00 08 02 02 89 22 00 07 05 05 00
83 00 90 00

DCH 14 UIPE_OMSG CC_RELEASE_REQ REF 0000C482 TN 00003B94 CH 00000015 TOD 13:38
:12

DCH 14 UIPE_IMSG CC_RELEASE_CONF REF 00004482 TN 00003B94 CH 00000015 TOD 13:
38:12
2F 00 01 00 06 00 08 02 02 89 2B 00

DCH 14 UIPE_OMSG CC_SETUP_RESP REF 0000C602 TN 00003B14 CH 00000005 TOD 13:38
:12
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 14 UIPE_IMSG CC_SETUPCOMP_IND REF 00004602 TN 00003B14 CH 00000005 TOD 13:
38:12
2F 00 01 00 06 00 08 02 02 8C 38 00

MSGI/MSGO MON 2:
DCH 14 UIPE_IMSG CC_SETUP_IND REF 00004802 CH 59 9 TOD 13:39:00
PRIM HDR: 2F 00 01 00 44 00
MSG HDR: 08 02 02 90 2E 00
BCAP: 01 07 13 00 81 90 00 00 A2
CHID: 09 09 0D 00 A9 00 83 00 01 00 09
CAD#: 03 0A 03 00 80 00 04 00 04 08 02 04
GFFAC: 37 13 19 00 9F 00 8B 01 00 01 00 A1 08 02 01 01
02 01 00 84 00
PROGI: 1E 04 03 00 82 81

PRI218 DCH: 29 DATA: 00000000

.
DCH 14 UIPE_OMSG CC_SETUP_RESP REF 0000C782 CH 59 6 TOD 13:39:02
PRIM HDR: 01 00 01 00 11 00
MSG HDR: 08 02 82 8F 0F 00
PROGI: 1E 04 03 00 21 94
PCATG: 1D 03 01 00 00

DCH 14 UIPE_IMSG CC_SETUPCOMP_IND REF 00004782 CH 59 6 TOD 13:39:02
PRIM HDR: 2F 00 01 00 06 00
MSG HDR: 08 02 02 8F 38 00

DCH 14 UIPE_IMSG CC_DISC_IND REF 00004502 CH 59 1 TOD 13:39:04
PRIM HDR: 2F 00 01 00 0E 00
MSG HDR: 08 02 02 8A 22 00
CAUSE: 07 05 05 00 80 00 90

DCH 14 UIPE_OMSG CC_RELEASE_REQ REF 0000C502 CH 59 1 TOD 13:39:04
PRIM HDR: 01 00 01 00 0C 00
MSG HDR: 08 02 82 8A 0C 00
UCAP: 2D 04 01 00 00 80

DCH 14 UIPE_IMSG CC_RELEASE_CONF REF 00004502 CH 59 1 TOD 13:39:04
PRIM HDR: 2F 00 01 00 06 00
MSG HDR: 08 02 02 8A 2B 00

If you need anything else let me know.

Thanks

slagburn · 11-29-2004, 03:24 PM

I think we need to see more setup messages, I only see incoming setup messages on DCH 14 (CO) which doesn't really help us with the CLID on the outgoing calls.

Try this...

Turn off everything you have now.

SET MSGO 14 MON 0
SET MSGI 29 MON 0

ENL MSGO 14 MSG STP <---- should show only outgoing setup messages to the public which should contain the CLID and any flags.

ENL MSGI 29 MSG STP <----- should show only incoming setup messages from the CISCO which should contain the CLID and any flags.

Make some calls from both the Meridian and CISCO to the public then do this...

SET MSGO 14 MON 2
SET MSGI 29 MON 2

And repeat.

Ya might wanna do the same thing with MON 1 as I think that's all the NT tool will work with.

Using the MSG xxx options allows you to look at just one type of message and not the entire flood of DCH yammering.
Initially that should be all that's needed to help.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Blocking caller ID from a Davox Dialer	mmtech	Meridian Systems	6	08-07-2003 12:44 PM
AUDIX could not capture the external caller ID	waynelin	Merlin	2	08-07-2003 01:45 AM
MICS Caller ID	switch	BCM and Norstar	1	08-05-2003 04:45 PM
Caller ID name on SBC PRIs	jheath	Meridian Systems	1	07-20-2003 10:59 PM
Block Caller ID?	Wildman	Meridian Systems	6	03-10-2003 04:26 PM

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)