LGGDK162 Plugin issue

[juan.mostert]

As per our discussion on 6/6/12 over the telephone please find attached the raw data entries for the month of June. Note that the dates are incorrect as the day is before the month instead of visa verse. Bellinda advised that it could be a plugin issue. Please advise.

[Belinda Frick]

I saw the hyper terminal screenshot from an earlier post you made, the date is also incorrect there:
Plugin for LG GDK162

The problem is that your date is mm/dd/yy in stead of dd/mm/yy. You will need to contact your PABX support to configure this correct or refer to forum post: Incorrect dates on LG GDK PABX

The rawdata you provided does load with the 'Plg100.dll' plugin, but it was not written for the LG GDK 162. I cannot confirm that it will translate all call actions correct and therefore cannot suggest it.

Please change the date on the PABX to be in the correct format and use the plugin 'plg162.dll'.

NOTE:

All rawdata logged until the change is made, so that the PABX outputs in the correct date format for the plugin, cannot be used to re-load call details. You can edit the rawdata files with a search and replace to 'swop' the 'mm' and 'dd' value.

For example: The date shows as '03/06/12' and is for 6 March 2012:

Code: Select all

9393  126  11  00:22 03/06/12 07:55  O0786766562         **

You need to search for '03/06/12' and replace with ''06/03/2012' to have the result:

Code: Select all

9393  126  11  00:22 06/03/12 07:55  O0786766562         **

This is manual process per rawdata file for each day. If you make a mistake where you add or remove characters, this will influence the call details shown in TNG.

[Belinda Frick]

To explain, we will assume the TNG was installed 9 March 2012.

Examples of what would happen if the 'day' and 'month' field is swopped:

• If todays date is 20120309 (9 March 2012), the calls will load for 20120903(3 September 2012).
  
  On the day of 20120309 it will look like TNG is not logging calls (if you look on the 'Call List' page), because they are being loaded for a future date. If you look at the record count on the Call List page, you will see that it increases.
  
  On the day of 20120903, if you go to the Call List page and check calls loaded at for example 10h00 in the morning there will already be calls for the entire working day. This is not calls that loaded today, but already loaded 20120309.
  
  Since the 'mm' and 'dd' field is swopped, on the day 20120903 it will load calls for 20120309. The record count will also increase, but the calls details displayed on your 'Call List' page will stay the same.
  
  This have call details for the future.
  
  
• If the PABX time was never corrected up to 20120903. Another scenario is for each month since 20120309 on the first of the month, the calls will load for January 2012.
  
  For example
  Actual Date Date calls loaded for:
  20120401 - 4 January 2012
  20120501 - 5 January 2012
  20120601 - 6 January 2012
  20120701 - 7 January 2012
  20120801 - 8 January 2012
  20120901 - 9 January 2012
  
  This means your TNG was installed 20120309, but it has call details for before the install date.
  
  Every month on the first of the month, the number of entries for January will also increase. The same counts for the other months. On the second of each month, calls will load for February. On the third of each month calls will load for March, etc.

Conclude:

Since the format of the date received from the PABX was incorrect and therefore it loaded into TNG on an incorrect date the call details cannot be used for TNG reporting.

You will need to first correct the PABX output. Please contact your PABX vendor/support to assist.

Thereafter blank the TNG database. All the calls loaded after the blank database was created will then be correct. To blank the TNG database see forum post - How do I blank the TNG call details?

You cannot re-import the raw data files as the date is incorrect and it will update to the incorrect day as explained in the post. Your reporting in TNG will thus be incorrect. If you whish to have the historic data then you need to 'fix' the rawdata and then import it. PLEASE NOTE this is a manually process and if you make any mistakes it will influence the accuracy of the TNG reporting.