search

rlarranaga / bafprp

Automatically exported from code.google.com/p/bafprp
0 stars 0 forks source link

errored out when reading file from Nortel CS-1500 #37

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. bafprp -v c:\usagefiles\test.baf
2.
3.

What is the expected output? What do you see instead?
I was expecting it to parse the file.
I got the following:
C:\Users\remtpi.MG\Desktop>type record.log
--------------------------------------------------------------------------
Record 1: Unknown
--------------------------------------------------------------------------
Length of record: 11268, CRC32: 325883723
--------------------------------------------------------------------------
File: c:\usagefiles\test.baf
--------------------------------------------------------------------------
Position: 72557
--------------------------------------------------------------------------
Structure Code: structurecode: Unknown: 1 : 01C3
Call Type: calltype: 000
Sensor Type: sensortype: 6C1
Sensor Identification: sensorid: Previously-Output Record : C00002
Record Office Type: recordofficetype: 073
Record Office Identification: recordofficeid: Default : 00C003
Date: date: 2010-00-0A
Timing Indicator: timingindicator: Default : Default : Default : Default : Possi
ble Time Stamp Error (conversation connect)
Study Indicator: studyindicator: Default : Network Completion : Validation Test
: Unknown: C : Default : Unknown: 2 : More Than 7 Digits Seen
Called Party Answer Indicator: calledpartyanswerindicator: Called Party Answer D
etected
Service-Observed/Traffic-Sampled Indicator: servicetrafficind: Default
Operator Action: operatoraction: Operator Identified, Operator Dialed
Service Feature Code: servicefeaturecode: 4C0
Originating NPA: originatingnpa: 9C0
Originating Number: originatingnumber: 013-84C1
Overseas Indicator: overseasindicator: 12-digit International Number
Terminating NPA: terminatingnpa: 5C000
Terminating Number: terminatingnumber: 0C0-0000
Time: time: 0C:0C:0C
Elapsed Time: elapsedtime: 0:00:01.6

C:\Users\remtpi.MG\Desktop>

What version of the product are you using? On what operating system?
v1.3.1 on Windows 7 Ultimate

Please provide any additional information below.
My file was polled off a Nortel CS-1500 landline switch.

Original issue reported on code.google.com by robmason...@gmail.com on 17 Aug 2011 at 7:02

GoogleCodeExporter commented 8 years ago 
Hi, this looks like there is some extra header data in your baf file.  Are 
there any different options you can choose from when you pull the call data?  
Some people have reported that they need to choose 'lite', or 'streamlined' or 
some such when exporting.
Bafprp expects the file to be in perfect baf format with no headers or extra 
vendor data that is not in the file spec.  You may have to play around with 
your export settings.
If you look at your file under a hex viewer the first few bytes should be 
similar to

52 00 00 AA 00 1C 00

No exactly, but very similar, especially AA, that code marks the beginning of a 
record.

Original comment by charless...@gmail.com on 17 Aug 2011 at 7:39

GoogleCodeExporter commented 8 years ago 
I'm having the same issue with a CS2k and the first part looks like this:

____SNIP____
0028 0000 0024 0000 aa09 013c 092c 036c
____SNIP____

The Metaswitch record that is processed correctly looks like this:

____SNIP____
0024 0000 aa09 013c 092c 800c 0000 000c
____SNIP____

It's also worth noting that there seems to be a largish chunk (looks like 2008 
or 2024 bytes) of additional 0xAA "padding" in the top of the file after the 
first 40 bytes.

I'm still looking for an option in the CBM to eliminate this, but haven't found 
one yet.

Original comment by mpcat...@gmail.com on 8 Aug 2012 at 1:47

GoogleCodeExporter commented 8 years ago 
Thanks for the report.  I have been considering different options to make 
bafprp ignore erroneous header data.  
A simple seek from the start would be the easiest, but I am unsure if it would 
work for all files.
I will take a look, in the meantime let me know if you can find the option to 
trim this data.

Original comment by charless...@gmail.com on 8 Aug 2012 at 3:20

GoogleCodeExporter commented 8 years ago 
Will do, but based on what I've seen so far I'm not optimistic.

If you have a fix you want to me to test, I would be more than happy to do so.

Thanks for the quick response!

Original comment by mpcat...@gmail.com on 8 Aug 2012 at 4:16

GoogleCodeExporter commented 8 years ago 
Possibly fixed in commit r233

Original comment by charless...@gmail.com on 3 Jan 2013 at 5:47