PBX Data logger, problem with SQL database send

[Digitalfury]

I am getting an error on the SQL Database send for pbx logger. Working with Avaya IP Office.

Data have been processed with errors

The data is not being entered into the table.

[Arthur Grasin]

Is it possible the module is temporary disabled? In any other case, the program should display a bit more detailed error message.

[Digitalfury]

I have had a bit more luck with the ODBC export method. The only problem I am having now is that the call_duration field is throwing odd results. Due to the format.

It works when set up as a datetime2 field. But you obviously get an odd date in the duration field.

When it is set up as a Time field in both the bindings and the SQL database the logger throws a Datetime overflow error.

[Arthur Grasin]

Could you capture your data to a log file and attach it here? I'll verify our parser settings.

[Digitalfury]

Attached

[Arthur Grasin]

I've verified the parser and it doesn't append the date to the call_duration field. Due technical reasons, the program uses the "datetime" data type for the call duration field, but a date part is empty in this case.

[Digitalfury]

How should I rectify the problem? I have tried using the Time(7) field, but the parser throws a datetime overflow error when sending data to the SQL Server.

[Arthur Grasin]

You should use the "datetime" data type. Could you attach a screenshot with wrong data within your database?

[Digitalfury]

Attached, Surely it is possible to get duration as a time. obviously duration has no date value.

[Arthur Grasin]

I see that the the date part is empty (=0). Just change display mode for the call_duration column do hh:nn:ss.

[Digitalfury]

I have tried this. It only allows me to change the format. then I get the datetime overflow error on the pbx logger.

Any thoughts?

[Arthur Grasin]

You should change the display format in the client application that will retrieve data from the database.