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!

Register Log in
  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How to arrange DCH's Traces ?

Status
Not open for further replies.
ROTA78

ROTA78

Technical User
Aug 18, 2007
62
CA
Hi All,
Thank you for you help,
I have DCH trace for five loops number of calls actually exceed 1000 call. I need to trace every call alone any one have any idea how to arrange them.
Thanks,
Rafat
 
Sort by date Sort by votes
Why DCH?

Why not use CDR?

If you have to arrange by DCH, write a script to import into access or excel and arrange by timestamp
 
Upvote 0 Downvote
What are you trying to do?




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.


 
Upvote 0 Downvote
I have a big file like these ::

DCH 102 UIPE_IMSG CC_SETUP_IND REF 00000985 CH 102 7 TOD 10:03:08 CK B075293A
CALLING #:0795542585 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN


DCH 102 UIPE_OMSG CC_PROCEED_REQ REF 00008985 CH 102 7 TOD 10:03:08 CK B075293D

DCH 102 UIPE_OMSG CC_ALERT_REQ REF 00008985 CH 102 7 TOD 10:03:08 CK B0752A95

DCH 102 UIPE_OMSG CC_SETUP_RESP REF 00008985 CH 102 7 TOD 10:03:12 CK B0754C1B
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 102 UIPE_IMSG CC_SETUPCOMP_IND REF 00000985 CH 102 7 TOD 10:03:14 CK B0754DED


DCH 102 UIPE_OMSG CC_DISC_REQ REF 00008985 CH 102 7 TOD 10:03:40 CK B0761999
CAUSE: #16 - NORMAL CALL CLEARING

DCH 102 UIPE_IMSG CC_RELEASE_IND REF 00000985 CH 102 7 TOD 10:03:40 CK B0761B3C

DCH 102 UIPE_OMSG CC_RELEASE_RESP REF 00008985 CH 102 7 TOD 10:03:40 CK B0761B3D




and I need to trace every call alone



are any software or tools exist to arrange them ??

Regards,,

Rafat Adly
 
Upvote 0 Downvote
I don't think there are any packaged DCH trace parsers. You will probably have to code your own.
 
Upvote 0 Downvote
You can use the REF ID in each one to consolidate the records.

Code: 
DCH 102 UIPE_IMSG CC_SETUP_IND [!]REF 00000985[/!] CH 102 7 TOD  10:03:08 CK B075293A 
CALLING #:0795542585 NUM PLAN: E164  TON: NATL 
CALLED  #:1343 NUM PLAN: E164  TON: UNKNOWN  


DCH 102 UIPE_OMSG CC_PROCEED_REQ REF [!]00008985[/!] CH 102 7 TOD  10:03:08 CK B075293D


You can see in the example above where the inbound REF (00000985) can be associated to the outbound REF of (00008985). Notice the '8' in the outbound side. That is added to the REF ID to keep the messages unique, but able to be associated to each other.

But to confirm what pronei said, I know of nothing that will do this for you other than an expensive Protocol Analyser software/hardware package.

What exactly are you trying to do? There may be an easier way to get the information ytou are looking for instead of trying to collect all of this DCH information.

911Guru
E911 FAQs are located at:
 
Upvote 0 Downvote
Dear all,
I have 70,000 lines of these traces customer want me to give hime a statistics on the number of successfull calls and actual call durration for every call and reason for disconnect ETC,,, any one can help meeeeee

I thought may be there are software to arrange that or any tools ?????
Thank you

DCH 104 UIPE_IMSG CC_SETUP_IND REF 0000479E CH 104 10 TOD 10:51:21 CK 91F03E45
CALLING #:791988673 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN

DCH 104 UIPE_OMSG CC_PROCEED_REQ REF 0000C79E CH 104 10 TOD 10:51:21 CK 91F03E49

DCH 104 UIPE_OMSG CC_ALERT_REQ REF 0000C79E CH 104 10 TOD 10:51:21 CK 91F03F69

DCH 107 UIPE_OMSG CC_SETUP_RESP REF 0000C49E CH 107 28 TOD 10:51:21 CK 91F04092
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 102 UIPE_IMSG CC_DISC_IND REF 0000326F CH 102 25 TOD 10:51:21 CK 91F0417B
CAUSE: #16 - NORMAL CALL CLEARING

DCH 102 UIPE_OMSG CC_RELEASE_REQ REF 0000B26F CH 102 25 TOD 10:51:21 CK 91F0417D

DCH 102 UIPE_IMSG CC_RELEASE_CONF REF 0000326F CH 102 25 TOD 10:51:21 CK 91F041CA

DCH 107 UIPE_IMSG CC_SETUPCOMP_IND REF 0000449E CH 107 28 TOD 10:51:21 CK 91F0427B

DCH 107 UIPE_IMSG CC_DISC_IND REF 00003E9E CH 107 27 TOD 10:51:21 CK 91F0434A
CAUSE: #16 - NORMAL CALL CLEARING

DCH 107 UIPE_OMSG CC_RELEASE_REQ REF 0000BE9E CH 107 27 TOD 10:51:21 CK 91F0434B

DCH 107 UIPE_IMSG CC_RELEASE_CONF REF 00003E9E CH 107 27 TOD 10:51:21 CK 91F043A2

DCH 102 UIPE_IMSG CC_SETUP_IND REF 0000346F CH 102 25 TOD 10:51:21 CK 91F04423
CALLING #:772159860 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN

DCH 102 UIPE_OMSG CC_PROCEED_REQ REF 0000B46F CH 102 25 TOD 10:51:21 CK 91F04427

DCH 107 UIPE_IMSG CC_SETUP_IND REF 0000489E CH 107 27 TOD 10:51:21 CK 91F04452
CALLING #:0774659909 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN

DCH 107 UIPE_OMSG CC_PROCEED_REQ REF 0000C89E CH 107 27 TOD 10:51:21 CK 91F04455

DCH 102 UIPE_OMSG CC_ALERT_REQ REF 0000B46F CH 102 25 TOD 10:51:21 CK 91F045F0

DCH 107 UIPE_OMSG CC_ALERT_REQ REF 0000C89E CH 107 27 TOD 10:51:21 CK 91F045F8

DCH 102 UIPE_IMSG CC_DISC_IND REF 0000756E CH 102 7 TOD 10:51:22 CK 91F04987
CAUSE: #16 - NORMAL CALL CLEARING
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 102 UIPE_OMSG CC_RELEASE_REQ REF 0000F56E CH 102 7 TOD 10:51:22 CK 91F04988

DCH 102 UIPE_IMSG CC_RELEASE_CONF REF 0000756E CH 102 7 TOD 10:51:22 CK 91F04ABF

DCH 102 UIPE_IMSG CC_SETUP_IND REF 0000356F CH 102 7 TOD 10:51:22 CK 91F04BF0
CALLING #:0774268234 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN

DCH 102 UIPE_OMSG CC_PROCEED_REQ REF 0000B56F CH 102 7 TOD 10:51:22 CK 91F04BF3

DCH 102 UIPE_IMSG CC_DISC_IND REF 00007F6E CH 102 13 TOD 10:51:22 CK 91F04C4C
CAUSE: #16 - NORMAL CALL CLEARING
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 102 UIPE_OMSG CC_RELEASE_REQ REF 0000FF6E CH 102 13 TOD 10:51:22 CK 91F04C4D

DCH 102 UIPE_OMSG CC_ALERT_REQ REF 0000B56F CH 102 7 TOD 10:51:22 CK 91F04C60

DCH 102 UIPE_IMSG CC_RELEASE_CONF REF 00007F6E CH 102 13 TOD 10:51:22 CK 91F04DAF

DCH 102 UIPE_IMSG CC_DISC_IND REF 00001A6F CH 102 27 TOD 10:51:22 CK 91F04E7D
CAUSE: #16 - NORMAL CALL CLEARING
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 102 UIPE_OMSG CC_RELEASE_REQ REF 00009A6F CH 102 27 TOD 10:51:22 CK 91F04E7F

DCH 102 UIPE_IMSG CC_RELEASE_CONF REF 00001A6F CH 102 27 TOD 10:51:22 CK 91F04FCA

DCH 102 UIPE_OMSG CC_SETUP_RESP REF 0000B1EF CH 102 3 TOD 10:51:22 CK 91F04FF7
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 107 UIPE_OMSG CC_SETUP_RESP REF 0000C61E CH 107 1 TOD 10:51:22 CK 91F05068
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 102 UIPE_OMSG CC_SETUP_RESP REF 0000B2EF CH 102 12 TOD 10:51:22 CK 91F0509E
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 102 UIPE_IMSG CC_SETUPCOMP_IND REF 000031EF CH 102 3 TOD 10:51:22 CK 91F051C1

DCH 107 UIPE_IMSG CC_SETUPCOMP_IND REF 0000461E CH 107 1 TOD 10:51:22 CK 91F05235

DCH 102 UIPE_IMSG CC_SETUP_IND REF 000035EF CH 102 13 TOD 10:51:22 CK 91F0528B
CALLING #:0773294089 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN

DCH 102 UIPE_OMSG CC_PROCEED_REQ REF 0000B5EF CH 102 13 TOD 10:51:22 CK 91F0528E

DCH 102 UIPE_IMSG CC_SETUPCOMP_IND REF 000032EF CH 102 12 TOD 10:51:22 CK 91F052BF

DCH 102 UIPE_IMSG CC_SETUP_IND REF 0000366F CH 102 27 TOD 10:51:22 CK 91F0532D
CALLING #:0772987816 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN

DCH 102 UIPE_OMSG CC_PROCEED_REQ REF 0000B66F CH 102 27 TOD 10:51:22 CK 91F05330

DCH 102 UIPE_OMSG CC_ALERT_REQ REF 0000B5EF CH 102 13 TOD 10:51:22 CK 91F05341

DCH 102 UIPE_OMSG CC_ALERT_REQ REF 0000B66F CH 102 27 TOD 10:51:22 CK 91F05345

DCH 107 UIPE_OMSG CC_DISC_REQ REF 0000979C CH 107 14 TOD 10:51:22 CK 91F05581
CAUSE: #16 - NORMAL CALL CLEARING

DCH 107 UIPE_IMSG CC_RELEASE_IND REF 0000179C CH 107 14 TOD 10:51:22 CK 91F0571F

DCH 107 UIPE_OMSG CC_RELEASE_RESP REF 0000979C CH 107 14 TOD 10:51:22 CK 91F05720

DCH 107 UIPE_IMSG CC_SETUP_IND REF 0000499E CH 107 14 TOD 10:51:22 CK 91F05882
CALLING #:794684763 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN

DCH 107 UIPE_OMSG CC_PROCEED_REQ REF 0000C99E CH 107 14 TOD 10:51:22 CK 91F05885

DCH 107 UIPE_OMSG CC_ALERT_REQ REF 0000C99E CH 107 14 TOD 10:51:22 CK 91F058B7

DCH 118 UIPE_IMSG CC_DISC_IND REF 000014EF CH 118 18 TOD 10:51:25 CK 91F05A6E
CAUSE: #19 - NO ANSWER FROM USER

DCH 118 UIPE_OMSG CC_RELEASE_REQ REF 000094EF CH 118 18 TOD 10:51:25 CK 91F05A6F

DCH 118 UIPE_IMSG CC_DISC_IND REF 0000146F CH 118 13 TOD 10:51:25 CK 91F05AC2
CAUSE: #19 - NO ANSWER FROM USER

DCH 118 UIPE_OMSG CC_RELEASE_REQ REF 0000946F CH 118 13 TOD 10:51:25 CK 91F05AC3

DCH 118 UIPE_IMSG CC_RELEASE_CONF REF 000014EF CH 118 18 TOD 10:51:25 CK 91F05AD4

DCH 118 UIPE_IMSG CC_RELEASE_CONF REF 0000146F CH 118 13 TOD 10:51:25 CK 91F05B24

DCH 118 UIPE_IMSG CC_SETUP_IND REF 000037EF CH 118 13 TOD 10:51:25 CK 91F05C6F
CALLING #:775072511 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN

DCH 118 UIPE_OMSG CC_PROCEED_REQ REF 0000B7EF CH 118 13 TOD 10:51:25 CK 91F05C72

DCH 118 UIPE_OMSG CC_ALERT_REQ REF 0000B7EF CH 118 13 TOD 10:51:25 CK 91F05D04

DCH 118 UIPE_IMSG CC_SETUP_IND REF 0000386F CH 118 18 TOD 10:51:25 CK 91F05D33
CALLING #:0778479946 NUM PLAN: E164 TON: NATL
CALLED #:1343 NUM PLAN: E164 TON: UNKNOWN

DCH 118 UIPE_OMSG CC_PROCEED_REQ REF 0000B86F CH 118 18 TOD 10:51:25 CK 91F05D36

DCH 118 UIPE_OMSG CC_ALERT_REQ REF 0000B86F CH 118 18 TOD 10:51:25 CK 91F05E9A

DCH 104 UIPE_OMSG CC_SETUP_RESP REF 0000C79E CH 104 10 TOD 10:51:25 CK 91F05F9D
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 107 UIPE_OMSG CC_SETUP_RESP REF 0000C71E CH 107 17 TOD 10:51:25 CK 91F05FCA
PROGRESS: INTERWORKING WITH PRIVATE WORK

DCH 104 UIPE_OMSG CC_SETUP_RESP REF 0000C69E CH 104 6 TOD 10:51:25 CK 91F06044
 
Upvote 0 Downvote
That's what CDR is for.




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.


 
Upvote 0 Downvote
Yes,
But CDR didnot give us the reason for disconnect, right ?

and also the side who send disconnect signal first..

Regards,
Rafat
 
Upvote 0 Downvote
Also any failed calls will not appear in the CDR,
CDR is only for successfull calls...
 
Upvote 0 Downvote
For the last time, there is NOTHING available!! You will have to code your own DCH parser, use Excel/VBS that would probably be the easiest combination to achieve what you want.

If you customer wants the information that bad, then I'm sure he'd be willing to pay a coder to accomplish this.

To code a simple vbs to import dch to excel shouldn't take an experienced coder for than 2 hours work tops.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

htroberts
  • Locked
  • Question
how to get into top compartment of 11c cabinet?
Replies
7
Views
501
htroberts
htroberts
JM2009
  • Locked
  • Question
CS1000 how to use telent to download the ip trunk error message??
Replies
3
Views
546
psychotech
psychotech
22NC
  • Locked
  • Question
Customer upgrading network switches. How to do a graceful switch
Replies
3
Views
386
Firebird Scrambler
Firebird Scrambler
umts
  • Locked
  • Question
How should I get started and what should I know? 2
Replies
9
Views
928
umts
umts
trmg
  • Locked
  • Question
DNs assigned to virtual set go to reorder 1
Replies
10
Views
644
trmg
trmg

Part and Inventory Search

Sponsor

Back
Top