rlarranaga / bafprp

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

Differentiating between multiple modules 164? #40

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
We have some BAF records with multiple Module 164 entries.  They might look 
like this in our debug output:

|| Appended module 164
Module code : E.164 / X.121 number
Number identity : Originating CPN
Country code : E.164 number 1-digit country code : 0001
Significant digits in next field : 010
Number : 00000XXXXXXX013
|| Appended module 164
Module code : E.164 / X.121 number
Number identity : Original Called Number
Country code : E.164 number 1-digit country code : 0001
Significant digits in next field : 010
Number : 00000XXXXXXX378

The only difference would be the Number Identity.  How would you ask for the 
m164 fields separately on the command line?  I generally do something like this:

/bafprp -rcsv -lfile -efile -ptphonenumber:hyphens:false 
-prfilename:/tmp/bafprptmp.10019 -pefilename:bafprp.err -plfilename:bafprp.log 
-prfields:calltype,calledpartyanswerindicator,m103.sigdigs,m103.digits,m164.sigd
igs,m164.largedigits,date,time,elapsedtime,carrierconnectdate,carrierconnecttime
,carrierelapsedtime,originatingnpa,originatingnumber,terminatingnpa,terminatingn
umber,overseasindicator,m164.countrycode,m164.numberidentity,operatoraction,trun
kgroupnumber

It seems there would need to be multiple m164 fields(?)  Can this be done 
currently?

--TimH

Original issue reported on code.google.com by th...@bendtel.net on 26 Feb 2014 at 11:26

GoogleCodeExporter commented 8 years ago
Hi Tim -
Bafprp should suffix the field with a .1
If you current version does not try compiling from the trunk, but I am pretty 
sure the field you should add to your list is m164.largedigits.1

When using standard file output, the program will print the field name next to 
the field data to remove any kind of guesswork in this process.

Also fyi there are numerous csv improvements available on the trunk if you are 
not using the trunk currently.  Including loading the fieldlist from a file :)

Original comment by charless...@gmail.com on 26 Feb 2014 at 11:45

GoogleCodeExporter commented 8 years ago
Should .1 give me the second set of m164 or the first?  .1 is giving me data, 
but .2 is not.

Original comment by th...@bendtel.net on 27 Feb 2014 at 1:27

GoogleCodeExporter commented 8 years ago
m164.largedigits should be the first instance, m164.largedigits.1 should be the 
second.  
But double verify that for sure

Original comment by charless...@gmail.com on 27 Feb 2014 at 1:29

GoogleCodeExporter commented 8 years ago
On Thu, 27 Feb 2014 01:29:23 +0000

    Yes, that occurred to me shortly after I wrote that and it
appears to be the case.  Thanks!

--TimH

Original comment by th...@bendtel.net on 27 Feb 2014 at 11:43

GoogleCodeExporter commented 8 years ago
Great!

Original comment by charless...@gmail.com on 27 Feb 2014 at 11:54