Call correlator (bafview-bafprp) not display in bafprp

[GoogleCodeExporter]

I wanted to know if the "bafprp" project has same execution
mode similar to "bafview" project. When I run the bafprp which doesn't display 
in the "Call correlator" field.

For example 
The output records from bafview "-v" is :

-------------------------------------------
Toll call or simple billing
-------------------------------------------
Length of record 83
-------------------------------------------
Modules appended to this record
Structure type: 1
Call type: 6
Sensor : Type = 800
Sensor : ID = 000000 : Default
Recording Office : Type = 800
Recording Office : ID = 000000 : Default
Date: 29 August 2013
Timing indicator : Default : Default : Default
Study indicator : Default : Default
Called party off-hook : Called party off-hook not detected
Service observed / Traffic sampled : Default
Operator action : Automatically identified, customer dialed
Service feature code: Advanced Intelligent Network - Default
Calling number: 706-645-0067
Overseas indicator : NPA dialed by customer
Called number: 706-645-0067
Time: 13:20:09.6
Length of call: 0:00.0
|| Appended module 800
Module code : 800
Call correlator : 285043206835362
|| Appended module 801
Module code : 801
Trunk Group Number : Signaling type not specified : 0055
Cause : Failed route : Internal Q.850 cause : 063 : SIP code : 606
|| Appended module 0
Module code : Final module
End of record

The output records from bafprp is :

--------------------------------------------------------------------------
Record 1: Toll call or non-US
--------------------------------------------------------------------------
Length of record: 78, CRC32: 3806554662
--------------------------------------------------------------------------
File: BAF_2013-08-29_17h19_35_UTC.pri
--------------------------------------------------------------------------
Position: 36
--------------------------------------------------------------------------
Structure Code: structurecode: Modules Attached : 0001
Call Type: calltype: 006
Sensor Type: sensortype: 800
Sensor Identification: sensorid: Default : 000000
Record Office Type: recordofficetype: 800
Record Office Identification: recordofficeid: Default : 000000
Date: date: 2013-08-29
Timing Indicator: timingindicator: Default : Default : Default : Default : 
Default
Study Indicator: studyindicator: Default : Default : Default : Default : 
Default : Default : Default
Called Party Answer Indicator: calledpartyanswerindicator: Called Party Answer 
not Detected
Service-Observed/Traffic-Sampled Indicator: servicetrafficind: Default
Operator Action: operatoraction: Automatically Identified, Customer Dialed
Service Feature Code: servicefeaturecode: 027
Originating NPA: originatingnpa: 706
Originating Number: originatingnumber: 645-0067
Overseas Indicator: overseasindicator: NPA Dialed by Customer
Terminating NPA: terminatingnpa: 706
Terminating Number: terminatingnumber: 645-0067
Time: time: 13:20:09
Elapsed Time: elapsedtime: 0:00:00.0
Module Code: modulecode: 800
Module Code: modulecode: 285
Module Code: modulecode: 432
Module Code: modulecode: 683
Module Code: modulecode: 362
Module Code: modulecode: 801
Module Code: modulecode: 900
Module Code: modulecode: 5C2
Module Code: modulecode: 200
Module Code: modulecode: 636
Module Code: modulecode: 6C0
Module Code: modulecode: 0C0

I need to take the field Call correlator : 285043206835362 using bafprp, but in 
the bafprp output this field doesn't exists. With out this filed we can't 
correlate calls.

I am attaching both file, please check the attached file

Original issue reported on code.google.com by tittoseb...@gmail.com on 3 Sep 2013 at 1:55

Attachments:

• BAF_2013-08-29_17h19_35_UTC.pri.txt
• BAF_2013-08-29_17h19_35_UTC_bafprp.txt

[GoogleCodeExporter]

Thanks for the report -
It seems the module definition for code 800 is incorrect in some way, I'll take 
a look

Original comment by charless...@gmail.com on 5 Sep 2013 at 7:04

• Changed state: Accepted
• Added labels: OpSys-All, Usability

[GoogleCodeExporter]

Thank you very much for your reply.

I am not in expert in c++ and don't know to correct the issue.
Can I expect a fix soon?

I am in a critical  stage of my current project, which badly needs "Call 
correlator".

Thank you very much in advance.
Titto Sebastian

Original comment by tittoseb...@gmail.com on 10 Sep 2013 at 12:21

[GoogleCodeExporter]

I have this and one other issue to look into to - I'll try to take a look at 
the problem tonight.  :)

Original comment by charless...@gmail.com on 10 Sep 2013 at 3:57

[GoogleCodeExporter]

Thanks a lot

Original comment by tittoseb...@gmail.com on 10 Sep 2013 at 5:33

[GoogleCodeExporter]

Hello there - sorry for the delay.
I was just looking into the reference documents and bafview to find module 800 
and unfortunately I cannot find a definition in any of the documents I have.  
This usually means the module is vendor specific for whatever type of switch 
you are using.

I am guessing the bafview program you are using was given to you from the 
vendor?  Is it by chance open source?  If so could you upload it or send it to 
my email charlessolar@gmail.com

If you do not have the source, then the other option is to get the definition 
from the vendor.  If they object to adding their definitions into bafprp as 
open source please email me and we can come up with a solution.

As a last resort, if you are unable to contact the vendor, it is possible that 
I may be able to reverse the definition from the binary file if you can send it 
to me.

Original comment by charless...@gmail.com on 11 Sep 2013 at 12:25

[GoogleCodeExporter]

Hello, I was looking for something similar. The vendor definition we have is 
the call correlator is:

Module code identification: Table 88, Characters 4, Byte offset 0
Call correlator: Table 808, Characters 16, byte offset 2

Original comment by stephen....@gmail.com on 13 Dec 2013 at 12:26

[GoogleCodeExporter]

Hi Stephen - 
That is exactly what I need.  I can add this to bafprp in no time.

Original comment by charless...@gmail.com on 13 Dec 2013 at 3:53

[GoogleCodeExporter]

This issue was closed by revision r241.

Original comment by charless...@gmail.com on 13 Dec 2013 at 3:56

• Changed state: Fixed

[GoogleCodeExporter]

Please checkout the latest changes from the trunk and let me know if this 
addresses module 800 and the call correlator

Original comment by charless...@gmail.com on 13 Dec 2013 at 4:00