" /> iCON reporting issues - Genesys CTI User Forum

Author Topic: iCON reporting issues  (Read 2674 times)

Offline krish_kk123

  • Newbie
  • *
  • Posts: 23
  • Karma: 0
iCON reporting issues
« on: July 24, 2013, 02:00:05 AM »
Advertisement
Hi Guys,

Can I please request help from the iCON experts in this forum ? I have been working on a reporting issue with iCON and following are the details....e


1. Tried implementing SIP server 8.1 on date sunday, but rolled it back to 7.6 as we faced some issues with transfer mode functionalities
2. Issues reported with iCON for monday, tuesday and wednesday. GDW scripts failed to extract any data from iCON DB as data was missing in one of the tables. Criteria for the script is to check for callid in g_call, g_virtual_queue and g_route_result.
3. Issue fixed, as iCOn was restarted due to a crash because of qualys scan run
4.When queried iCON db, i noted that data was present in g_call and g_route_result, but missing in g_virtual_queue. Checked logs from t-server and SIP server and confirmed that data was sent to iCON for those dates.

Can anyone you please tell me if this is a known issue ?

And is there a way to restore the data in g_virtual_queue ?

Any help on this is really appreciated and Thanks in Advance!


Cheers
Krish




Offline gustav

  • Newbie
  • *
  • Posts: 44
  • Karma: 0
Re: iCON reporting issues
« Reply #1 on: July 25, 2013, 08:48:16 PM »
If you have data missing in ICON, there is no way to recover that data (ie. through logs).  Do you have HA ICON applications?  If so you should have a redundant IDB that may have captured the call records.  Any event queued message that is propagated to ICON for a Virtual Queue should have a corresponding record written in the g_virtual_queue table.

After the restart is the g_virtual_queue table being written to?  Do you have an ICON connection to the switch which has the Virtual Queues configured?  Is the TServer for the switch where you have the virtual queues configured up and running?  Even though VQs are virtual, they do require the corresponding TServer to be running in order for the queue events to be communicated to ICON.

A bigger question is why are you trying to report out of ICON and not using the GIM ETL?

Offline krish_kk123

  • Newbie
  • *
  • Posts: 23
  • Karma: 0
Re: iCON reporting issues
« Reply #2 on: July 26, 2013, 01:20:29 AM »
Yes, connections are there, and I can see event queued and diverted sent to iCON. We dont have a HA and its a pretty old set up not designed to use GIM, so the prefer to run their GDW scripts and extract data from iCON DB.

The problem is :

Data which i see in g_virtual queue is not present in g_call
and data which i see in g_call is not present in g_virtual _queue