Author Topic: gsw_request_log  (Read 2589 times)

Offline bogdan

  • Jr. Member
  • **
  • Posts: 94
  • Karma: 0
gsw_request_log
« on: October 08, 2009, 04:08:51 PM »
Hello,

Can anyone explain how to create gsw_request_log and activate it? (on OCS7.1) I can't find description on this in the documentation and so I need to configure it by hand cause I don't have the wizard.
For this I think I need the fields and field datatypes, after configureing this in ConfManager I'll create the database table, but what keys showed I configure in the OCS component to activate it?

Regards

Offline bogdan

  • Jr. Member
  • **
  • Posts: 94
  • Karma: 0
Re: gsw_request_log
« Reply #1 on: October 09, 2009, 02:04:53 PM »
i did it :D

I looked in the dbserver logs asociated to my ocs and a saw the insert statement:
[quote]15:59:08.748 Dbg 10737 Forwarding request '94427' from 'App: 1732' to 'Oracle: 1732.1'
15:59:08.748 Dbg 10743 'Oracle: 1732.1' is spare
15:59:08.764 Dbg 10739 Oracle: id='1732.1' req='94427' SQL: insert into gsw_request_log (phone,request_type,switch_name,list_name,dn,agent_id,tenant_dbid,time_stamp,dnc_message) values ('#31#60XXXXXXXXX',9,'buc_pbx','Collection_list_manual','4285','7238',101,1255093148,'')
+0015  MSG_ERROR status='14' msg='ORA-00942: table or view does not exist[/quote]
=>
[quote]create table GSW_REQUEST_LOG (
      phone varchar2(64),
      request_type varchar2(100),
      switch_name  varchar2(100),
      list_name varchar2(100),
      dn        varchar2(10),
      agent_id  varchar(32),
      tenant_dbid  varchar2(32),
      time_stamp   number,
      dnc_message  varchar2(100)
)[/quote]

And now it works :D
But a new question comes now... In the the table I see records from all of the campaings, not only from the calling list that I set Log Table Access = GSW_REQUEST_LOG, why is that? how can I separate this calling_list from the others?

Regards



Offline bogdan

  • Jr. Member
  • **
  • Posts: 94
  • Karma: 0
Re: gsw_request_log
« Reply #2 on: October 09, 2009, 02:48:16 PM »
god damn it,
I think I didn't understood the concept behind gsw_request_log, I can't see in it the call made by CPD and there status...
I need a solution like log_call_stats that audits everything but not in a file, I want it in the DB...It seems Genesys doesn't offer this, so I'll just make a trigger on the calling_list table to insert in another table every change for field call_status, dial_time, attemt ...

Do I have another solution for this?

Regards

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
Re: gsw_request_log
« Reply #3 on: October 09, 2009, 10:19:36 PM »
I'm not sure from which release, maybe 7.5, but you need to check that, two more audit files were introduced, Record History Log and Extended Audit Trail. They both are plain text files, but especially the first should be very easy to import in a DB (maybe setting up a DTS or something?). It will also have fields like campaign and calling list id.

HIH

Fra