PBX Data logger - date format

[HDGrimes]

I have installed the software and have it communicating with the PBX - I can now see data on the screen 
But when the data is parsed it is giving errors - our date is in dd/mm/yy format and the parsing seems to assume mm/dd/yy.
I am getting error:
25/08/09 17:03:42 Panasonic KX-TD1232. Item: CALL_TIME. Error occurred while converting date/time string value "25/08/09 05:02PM" with the template "mm"/"dd"/"yy hh:nnAM/PM" (Invalid argument to date encode)
I could not find anywhere to change this ?
It is also not writing to a database - but of course that may be because of these errors.
Any help appreciated
Hugo Grimes

[Arthur Grasin]

Could you change the format of date within your PBX to mm/dd/yy format (month is first)?

[HDGrimes]

Sorry, but I don't know how to change the format on the PBX - DD/MM/YY is the standard in the UK.  I am not an expert in modification to the PBX - and so am reluctant to make changes.  I would have thought it would be easier to change the parsing parameters - maybe that's because I understand that a bit better 

[Arthur Grasin]

OK. We'll update the parser module for your date format. I'll post it here shortly.

[ashok]

Athur - Even i am looking for date time format for Avaya Communication manager 3.x Below is the format

071809 1405 3501 157      9912850771          53529           42367 00229 1 9     
071809 1405 3701 059      9984431242          53751           53751 00015 2 9     

where in im not able to convert to date & time format as specified in the tutorial

Please suggest the way forward

[Arthur Grasin]

Please, unpack the attached file for Panasonic KX-TD1232 to program folder\plugins\pbxparser\configs (near other files with the xmlz extension). The format of date is adjusted for your format. Then, you need to select Panasonic KX-TD1232 [DD-MM-YY] in the parsers list.

[HDGrimes]

Excellent  thank you for your help.

Hugo Grimes

[tomvanzijl]

Hello Arthur,

I am testing your great software and I have installed the PBX Data Logger software, and also have it communicating with the PBX, a Panasonic KX-TD1232NL.
However, when the data is parsed it is giving errors, more or less the same as the topic starter. Obviously the dutch version of the TD1232 adds VM instead of AM in the string value and NM instead of PM in the date/time string.

I can not find any parameters in the Panasonic program to change the output format of the SMDR data.

The log file is attached. Would you be so kind to make a new parser config file for this?

Regards, Tom van Zijl

[Arthur Grasin]

Please, unpack the attached file to
program folder\plugins\pbxparser\configs

Then select the "Panasonic KX-T1232" parser from the parsers list.

[tomvanzijl]

Hello Arthur,

Thanks for your work! Unfortunately I get another error message:

23-04-10 10:11:28 Starting the program (loading program options)
23-04-10 10:11:32 Starting the program (searching plugins)
23-04-10 10:11:33 The data source COM1 has been successful opened
23-04-10 10:11:33 Starting the program (loading configs)
23-04-10 10:11:33 Starting the program (applying config)
23-04-10 10:11:33 Starting the program (changing state)
23-04-10 10:11:33 Starting the program
23-04-10 10:26:10 pbxdata. Unable to write to database [[Microsoft][ODBC SQL Server Driver][SQL Server]The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.]

Can you please advise me what to change in the XML file?
Maybe change dateformat='mm"/"dd"/"yy hh:nnAM/PM' locale="409" in dateformat='dd"/"mm"/"yy hh:nnAM/PM' locale="409" ?

Regards, Tom van Zijl

[Arthur Grasin]

Could you post a structure of your table?

[tomvanzijl]

Hi Arthur,

I have a attached a screen print of the structure. Hope this is sufficient.

Regards, Tom van Zijl

[Arthur Grasin]

We've tested the software with this structure. Is it possible you changed 'bind' settings and bind something else to CALL_TIME column?

Also, please, try to remove the "Panasonic KX-T1232.xmlz" file in the "Configs" folder.

[tomvanzijl]

Hello Arthur,

You are right. My 'bind' settings were changed. I reinstalled the program and now it works very well! Reinstalling was probably not necessary but I wanted to make a fresh new start.

Thanks for all your work and fast reply's. After I am ready with some tests I will almost certain continue to buy the program.

Regards, Tom van Zijl