CDR Capture via tcp/ip on Windows host the CaNiBuS way! 1

[FortKnox]

OK guys, I think you all gonna like this one.

First of all, thanks to Kerchak thread690-684030 for inspiring this idea.

I found an application called ByteWedge Pro from Fogsoft.

Its a tcp/ip client and/or server and it will listen and capture your CDR info, error check it, parse it, and spit it out to anything you want it to!

There is a trial version on the Fogsoft website.

The HOW-TO:

STEP 1
CHANGE NODE-NAMES IP
TCPCAS 192.168.0.50 (ip of your Windows box)

STEP 2
CHANGE IP-SERVICES
CDR1 C-LAN TCPCAS 50000

STEP 3
CHANGE SYSTEM-PARAMETERS CDR
(page-1)
Primary Output Format: customized
Primary Output Endpoint: CDR1
(page-2)
1: date
2: space
3: time
4: space
5: sec-dur
6: space
7: clg-num/in-tac
8: space
9: in-trk-code
10: space
11: dialed-num
12: space
13: code-used
14: return
15: line-feed

STEP 4
Open ByteWedge Professional
File/New
Import Source - Import Data From TCP/IP
Export Method - Send Strings to Excel
Parser - leave alone (I havent messed with it yet)
Import Options - Mode Server, TCP/Port 50000
Export Options - leave alone
Events - leave alone
Click DONE
Click START

It will open Excel and start populating the spreadsheet with data - might need to change the cell formats appropriately.

Enjoy!

 

[simreal]

Good info. I have used netcat before and had always looked for windows versions.

I haven't tried this yet but I will. Any word on the demo vs. full release of this software? Whats the difference?

 

[FortKnox]

The demo is the full version with a 15-day restriction.

 

[FortKnox]

I found Microsoft SQL Express which will install on Windows XP and best of all its free.

I got ByteWedge Pro pumping the call data into SQL Server like a champ.

The only issue I am having right now is when a call has a null incoming trunk code (because of inside to outside calls) ByteWedge isnt skipping to the next column - hopefully I'll get that little issue figured out.