call accounting tickets over ethernet

Post Reply
endo

call accounting tickets over ethernet

Post by endo »

i made a program that collects the cdr tickets from an alcatel 4400 (oxe) pbx over tcp/ip.
i know the necessary protocol between the client and the pbx and the client works fine.
but the ticket format is very different than the v24 output. is there a way to change/modify the output format? or is there a documentation about it? as i know it should be same with extended format (according to user manuel), but its not.

current format looks like this:

Code: Select all

??????ED5.16137078                       820                           ALEX                test123                       1                                                   0120061020 16:02:19    0         0        61   45   13    12                00000000 0         0    000000000000000000000000000000000000000000000000000000000000000010000000000001000       104         0         0         01 0 0 06137078                           0         0020061020 16:01:18820                            9999 9999 9999    132767     0
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????ED5.12847670                       894                           Fax      F5                                       1                                                   0120061020 16:02:25    0         0        33   41   13    12                00000000 0         0    000000000000000000000000000000000000000000000000000000000000000010000000000001000       105         0         0         01 0 0 02847670                           0         0020061020 16:01:52894                            9999 9999 9999    132767     0
????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
Top
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3806
Joined: 23 Sep 2004 06:47

Post by vad »

Format real time over Ethernet and format in compressed text file for external accounting the same.
Chech if you have validated options Application/ accounting - file for external accounting=true.
Or check presens TAXA*.DAT files in /usr4/account (on PBX).
Retriev this files (f.e. one) by ftp. Rename in TAXA*.z, unzip in txt file (I use Winzip).
You will have txt file, the first line - fields description (name, pozition and soon).
You can see on PBX content of this file with "accview -tf" command.
And you can see with "accview -l" command correspondence between unzipped file and "accview -tf".
Top
endo

Post by endo »

thank you for the reply.
Application/ accounting - file for external accounting is TRUE.
i able to get cdr files from ftp, i can convert those files to txt files using accview.
but i need to get cdr tickets using tcp/ip connection.
let me explain more detailed;

i connect to the pbx from tcp port 2533, send some commands, then pbx starts sending cdr ticket to my client appilication over tcp connection. this works fine.

the problem is, pbx document says "ticket format will be same with the extended v24 output format"

if i get tickets using accview they look like (but i don't want use this feature):

Code: Select all

====[/DHS3dyn/account/TAXAQYQA.DAT : Ticket number 1/1/9]=======================
(00) TicketVersion = ED5.1              (01) CalledNumber = 02163475989
(02) ChargedNumber = 331                (03) ChargedUserName = SEMA       
(04) ChargedCostCenter = M.KARDI        (05) ChargedCompany = 
(06) ChargedPartyNode = 1               (07) Subaddress = 
(08) CallingNumber =                    ...

if i get the tickets from serial port (v24) they look like (i don't want this too.):

Code: Select all

|1260    |KESKINOGLU      |I-SIGOR   |0409161337|000:00:25|    70.00| S E    |0|
|        |4623266             |N|            |   0|000001|000001|   0|   76|B|A|
|1251    |BILGIYAR        |I-SIGOR   |0409161337|000:01:49|   140.00| S E    |0|
|6254    |SELDA           |FNSSGR    |0409161333|000:00:42|        0|        |0|
|6001    |03523361053         |N|            |   0|000001|000001|   1|    7|B|E|
|6204    |EMINE           |FNSSGR    |0409161333|000:00:49|        0|      X |0|
|        | Incoming Call      |N|            |   0|000001|000001|   2|   47|B|E|
and if i use tcp connection (which is i should use);

Code: Select all

ED5.13473964                       859                           ELIF               test123                       1                                                   0120061020 15:46:05    0         0         1   40   13    12                00000000 0         0    000000000000000000000000000000000000000000000000000000000000000010000000000001000        17         0         0         01 0 0 03473964                           0         0020061020 15:46:04859                            9999 9999 9999    132767     0

ED5.16010912                       860                           ARSUN               test123                       1                                                   0120061020 15:46:48    0         0        43   33   13    12                00000000 0         0    000000000000000000000000000000000000000000000000000000000000000010000000000001000        18         0         0         01 0 0 06010912                           0         0020061020 15:46:05860                            9999 9999 9999    132767     0

i found some documentation about serial port output (field explanations etc.), but i coudn't find any documentation about the ticket format if i use tcp/ip client, for example the trunk number, direction of call (incoming/outgoing) etc.
regards,

vad wrote:Format real time over Ethernet and format in compressed text file for external accounting the same.
Chech if you have validated options Application/ accounting - file for external accounting=true.
Or check presens TAXA*.DAT files in /usr4/account (on PBX).
Retriev this files (f.e. one) by ftp. Rename in TAXA*.z, unzip in txt file (I use Winzip).
You will have txt file, the first line - fields description (name, pozition and soon).
You can see on PBX content of this file with "accview -tf" command.
And you can see with "accview -l" command correspondence between unzipped file and "accview -tf".
Top
User avatar
ALCATELMEX
Member
Posts: 8
Joined: 26 Oct 2006 14:31
Location: MEXICO

Ticket On Ethernet

Post by ALCATELMEX »

They are different the positions when is by serial (v24) to that by ethernet, I have an information that would be able you to resolve the problem, but also I am new in this, and I do not know as would be able to attach files, if someone knows that he tell me please. ...

For the moment, sends your mail and I send him you... :wink:
Top
User avatar
cavagnaro
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 7014
Joined: 14 Sep 2005 19:45
Location: Brasil, Porto Alegre
Contact:
Contact cavagnaro

Post by cavagnaro »

Hey AlcatelMex

What you need to do is to upload the files to a web server and then make a link to it using the URL button.

Saludos
Ignorance is not the problem, the problem is the one who doesn't want to learn

OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
Top
User avatar
ALCATELMEX
Member
Posts: 8
Joined: 26 Oct 2006 14:31
Location: MEXICO

Post by ALCATELMEX »

Gracias Cavagnaro...

Annex the llink of the files that can serve you to understand and to interpret the positions of the ticket by ethernet. These positions you should interpret them in your program...

ftp://ftp.estratel.com.mx/pub/Ticket.pdf
ftp://ftp.estratel.com.mx/pub/Ticket.txt

"Save destiny as..."

Salu2...
Top
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3806
Joined: 23 Sep 2004 06:47

Post by vad »

Whith accview command you see tickets in human form. retriev *.DAT file with ftp, unzip. you will see first string - #TicketVersion,1,5,L,CalledNumber,6,35,L,ChargedNumber,36,65,L,ChargedUserName,66,85,L,ChargedCostCenter,86,95,L,ChargedCompany,96,111,L,ChargedPartyNode,112,116,L,Subaddress,117,136,L,CallingNumber,137,166,L,CallType,167,168,R,CostType,169,169,N,EndDateTime,170,186,N,ChargeUnits,187,191,R,CostInfo,192,201,R,Duration,202,211,R,TrunkIdentity,212,216,R,TrunkGroupIdentity,217,221,R,TrunkNode,222,226,R,PersonalOrBusiness,227,227,N,AccessCode,228,243,L,SpecificChargeInfo,244,250,N,BearerCapability,251,251,N,HighLevelComp,252,253,R,DataVolume,254,263,R,UserToUserVolume,264,268,R,ExternFacilities,269,308,N,InternFacilities,309,348,N,CallReference,349,358,R,SegmentsRate1,359,368,R,SegmentsRate2,369,378,R,SegmentsRate3,379,388,R,ComType,389,389,N,X25IncomingFlowRate,390,391,R,X25OutgoingFlowRate,392,393,R,Carrier,394,395,R,InitialDialledNumber,396,425,L,WaitingDuration,426,430,R,EffectiveCallDuration,431,440,R,RedirectedCallIndicator,441,441,R,StartDateTime,442,458,N,ActingExtensionNumber,459,488,L,CalledNumberNode,489,493,R,CallingNumberNode,494,498,R,InitialDialledNumberNode,499,503,R,ActingExtensionNumberNode,504,508,R,TransitTrunkGroupIdentity,509,513,R,NodeTimeOffset,514,519,R
You see - field name, pozision.
Top
endo

Post by endo »

i tried to unzip TAXA*.DAT files, winzip/winrar/7zip all says corrupted zip files. and even there is no zip header (PKZIP..) in the beginnings of the files, are you sure those files are zip archives?

i've uploaded an example TAX file to here. i can extract this file using accview but not with winzip.

thank you anyway, i guess this field order is same with the ethernet output. thx a lot.
vad wrote:Whith accview command you see tickets in human form. retriev *.DAT file with ftp, unzip. you will see first string - #TicketVersion,1,5,L,CalledNumber,6,35,L,ChargedNumber,36,65,L,ChargedUserName,66,85,L,ChargedCostCenter,86,95,L,ChargedCompany,96,111,L,ChargedPartyNode,112,116,L,Subaddress,117,136,L,CallingNumber,137,166,L,CallType,167,168,R,CostType,169,169,N,EndDateTime,170,186,N,ChargeUnits,187,191,R,CostInfo,192,201,R,Duration,202,211,R,TrunkIdentity,212,216,R,TrunkGroupIdentity,217,221,R,TrunkNode,222,226,R,PersonalOrBusiness,227,227,N,AccessCode,228,243,L,SpecificChargeInfo,244,250,N,BearerCapability,251,251,N,HighLevelComp,252,253,R,DataVolume,254,263,R,UserToUserVolume,264,268,R,ExternFacilities,269,308,N,InternFacilities,309,348,N,CallReference,349,358,R,SegmentsRate1,359,368,R,SegmentsRate2,369,378,R,SegmentsRate3,379,388,R,ComType,389,389,N,X25IncomingFlowRate,390,391,R,X25OutgoingFlowRate,392,393,R,Carrier,394,395,R,InitialDialledNumber,396,425,L,WaitingDuration,426,430,R,EffectiveCallDuration,431,440,R,RedirectedCallIndicator,441,441,R,StartDateTime,442,458,N,ActingExtensionNumber,459,488,L,CalledNumberNode,489,493,R,CallingNumberNode,494,498,R,InitialDialledNumberNode,499,503,R,ActingExtensionNumberNode,504,508,R,TransitTrunkGroupIdentity,509,513,R,NodeTimeOffset,514,519,R
You see - field name, pozision.
Last edited by endo on 27 Oct 2006 03:19, edited 1 time in total.
Top
endo

Post by endo »

great document, thanks a lot! this is exactly what i need.

if there is anyone interested with capturing the cdr tickets via ethernet from a 4400 pbx i can give some explanations about it.

thanks again.
ALCATELMEX wrote:Gracias Cavagnaro...

Annex the llink of the files that can serve you to understand and to interpret the positions of the ticket by ethernet. These positions you should interpret them in your program...

ftp://ftp.estratel.com.mx/pub/Ticket.pdf
ftp://ftp.estratel.com.mx/pub/Ticket.txt

"Save destiny as..."

Salu2...
Top
endo

Post by endo »

oops! well, ok i made it. with the 7zip utility and with extension .z instead of .zip i able to extract it.
thank you all,
regards.
endo wrote:i tried to unzip TAXA*.DAT files, winzip/winrar/7zip all says corrupted zip files. and even there is no zip header (PKZIP..) in the beginnings of the files, are you sure those files are zip archives?

i've uploaded an example TAX file to here. i can extract this file using accview but not with winzip.

thank you anyway, i guess this field order is same with the ethernet output. thx a lot.
vad wrote:Whith accview command you see tickets in human form. retriev *.DAT file with ftp, unzip. you will see first string - #TicketVersion,1,5,L,CalledNumber,6,35,L,ChargedNumber,36,65,L,ChargedUserName,66,85,L,ChargedCostCenter,86,95,L,ChargedCompany,96,111,L,ChargedPartyNode,112,116,L,Subaddress,117,136,L,CallingNumber,137,166,L,CallType,167,168,R,CostType,169,169,N,EndDateTime,170,186,N,ChargeUnits,187,191,R,CostInfo,192,201,R,Duration,202,211,R,TrunkIdentity,212,216,R,TrunkGroupIdentity,217,221,R,TrunkNode,222,226,R,PersonalOrBusiness,227,227,N,AccessCode,228,243,L,SpecificChargeInfo,244,250,N,BearerCapability,251,251,N,HighLevelComp,252,253,R,DataVolume,254,263,R,UserToUserVolume,264,268,R,ExternFacilities,269,308,N,InternFacilities,309,348,N,CallReference,349,358,R,SegmentsRate1,359,368,R,SegmentsRate2,369,378,R,SegmentsRate3,379,388,R,ComType,389,389,N,X25IncomingFlowRate,390,391,R,X25OutgoingFlowRate,392,393,R,Carrier,394,395,R,InitialDialledNumber,396,425,L,WaitingDuration,426,430,R,EffectiveCallDuration,431,440,R,RedirectedCallIndicator,441,441,R,StartDateTime,442,458,N,ActingExtensionNumber,459,488,L,CalledNumberNode,489,493,R,CallingNumberNode,494,498,R,InitialDialledNumberNode,499,503,R,ActingExtensionNumberNode,504,508,R,TransitTrunkGroupIdentity,509,513,R,NodeTimeOffset,514,519,R
You see - field name, pozision.
Top
Post Reply

Return to “Application”