News:

Welcome on our forum!

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Digitalfury

#1
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?
#2
Attached, Surely it is possible to get duration as a time. obviously duration has no date value.
#3
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.
#5
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.
#6
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.