Avaya IP Office Data Parser

[AndrewParker]

I am currently trying to implement an SMDR logging solution, I have been evaluating your product, i have managed to configure it to import the SMDR data into a SQL DB in real time, which is exactly what we are looking for, however, the only fields imported were:

CALL_TIME, CALL_DURATION, CALL_DURATION_S, RING, CALLER_PHONE, CALL_TYPE, DIALLED_PHONE, ACC

The fields that are available in the SMDR on an Avaya IP office are:

Call_Start, Call_Duration, Ring_Duration, Caller_Direction, Dialled_number, Dialled_number, Account_Is_Internal, Call_ID_Continuation, Party1_Device, Party1_Name, Party2_Device, Party2_Name, Hold_Time, Park_Time, AuthValid, AuthCode, User_Charged, Call_Charge,
Currency, Amount_at_Last_User_Change, Call_Units, Units_at_Last_User_Change, Cost_per_Unit, MarkUp

Is there any plans to modify the Avaya IP Office Parser to cater for the other fields presented in the SMDR?

[Arthur Grasin]

Simply attach a file with your data example with description of columns within the file and we'll prepare the parser for you. Because your PBX is freely configurable, then attach fields configuration from your PBX too.

[AndrewParker]

Thanks for the reply, my data file is attached.

Here is the script i used to create the table:

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[PBXDATA]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[PBXDATA]
GO

CREATE TABLE [dbo].[PBXDATA] (
[ID] [decimal](10, 0) IDENTITY (1, 1) NOT NULL,
Call_Start [datetime] NULL ,
Call_Duration [datetime] NULL ,
Ring_Duration [nvarchar] (40) NULL ,
Caller_Direction [nvarchar] (40) NULL ,
Dialled_number [nvarchar] (40) NULL ,
Dialled_number1 [nvarchar] (40) NULL ,
Account_Is_Internal [nvarchar] (40) NULL ,
Call_ID_Continuation [nvarchar] (40) NULL ,
Party1_Device [nvarchar] (40) NULL ,
Party1_Name [nvarchar] (40) NULL ,
Party2_Device [nvarchar] (40) NULL ,
Party2_Name [nvarchar] (40) NULL ,
Hold_Time [nvarchar] (40) NULL ,
Park_Time [nvarchar] (40) NULL ,
AuthValid [nvarchar] (40) NULL ,
AuthCode [nvarchar] (40) NULL ,
User_Charged [nvarchar] (40) NULL ,
Call_Charge [nvarchar] (40) NULL ,
Currency [nvarchar] (40) NULL ,
Amount_at_Last_User_Change [nvarchar] (40) NULL ,
Call_Units [nvarchar] (40) NULL ,
Units_at_Last_User_Change [nvarchar] (40) NULL ,
Cost_per_Unit [nvarchar] (40) NULL ,
MarkUp [nvarchar] (40) NULL,
) ON [PRIMARY]
GO

Please let me know if you need any more information from me?

THANK YOU!

[AndrewParker]

Hi there,

When do you think you will be able to look into this parser issue for me?

thanks

Andrew

[AndrewParker]

If we can get this sorted i am 99% certain we will be buying your software, can you please give me some indication on this issue?

many thanks

Andrew

[Arthur Grasin]

Andrew, I'm sorry for my late reply. Please, use the settings from the attached image and capture the data to a binary log file. Did you create the previous file with help of our data export plug-in?

[AndrewParker]

That's the SMDR file that the phone switch creates.

I have the logs created already, i have attached one for you now.

[Arthur Grasin]

Please, unpack the attached file to Program folder\Plugins\pbxparser\Configs and replace the original file with new one. We've added parser items for all columns. You can bind it to your database table columns within the data export plug-in. Please, let me know about results.

[AndrewParker]

Arthur,

Thanks for this, i started to bind to the database, but it appears the Parser does not have all the fields.

I came across these three before i stopped looking at it:

Call_Start, Calller_Direction, Dialled_Number

Is the parser you complied incomplete as to the Fields i listed in my DB Table?

thank you for your help...

[Arthur Grasin]

These columns are mapped to standard columns of our software:

Call_Start to CALL_TIME
Calller_Direction to CALL_TYPE
Dialled_Number to DIALED_PHONE

[AndrewParker]

Arhtur, would you be soo kind as to show me the translations for all the elements in the Parser to the titles i have used in my DB similar to your last post, but to cover all items?

[AndrewParker]

Have some errors also:

30/04/09 12:16:09
30/04/09 12:16:09 Avaya IP Office Phone [CSV]. Item: CALL_UNITS. Error occurred while converting string value "" to "Integer" data type  ('' is not a valid integer value)
30/04/09 12:16:09 Avaya IP Office Phone [CSV]. Item: LAST_UNITS. Error occurred while converting string value "" to "Integer" data type  ('' is not a valid integer value)
30/04/09 12:16:09 pbxlogger. Unable to write to database [[Microsoft][ODBC SQL Server Driver]Invalid precision value]
30/04/09 12:16:09
30/04/09 12:16:10 pbxlogger. Unable to write to database [[Microsoft][ODBC SQL Server Driver]Invalid precision value]
30/04/09 12:16:10

[Arthur Grasin]

Most fields have same item name and description (item name is in uppercase), except

Call_Start - CALL_TIME
Ring duration - RING
Caller - CALLER_PHONE
Direction - CALL_TYPE
Called_number - CALLED_PHONE
Dialled_Number - DIALED_PHONE
Is_Internal - FLAG1
Call ID - CALL_ID
Continuation - FLAG2
AuthValid - FLAG3

P.S. The updated version is attached. The data type for CALL_UNITS, LAST_UNITS has been changed to "string".

[AndrewParker]

Thanks again.

Error i get now is:

30/04/09 12:47:47 pbxlogger. Unable to write to database [[Microsoft][ODBC SQL Server Driver]Invalid precision value]
30/04/09 12:47:47

[Arthur Grasin]

I'll try to create a table with your structure and test it with your data. Could you create a backup copy of your current configuration from the File menu and attach it?