URS option on_route_error.. what it really does?

Option on_route_error defines what to do when an attempt to route a call resulted in an error, which is thrown by the Tserver to URS. If you are used to logs, you will find the EventError after RequestRouteCall.

Possible choices include:
default – Route the call to default destination
ignore – Ignore the error
delete – Delete the call from URS memory
reroute – Repeat the request
try_other – Find another target

Cheers!!
Gururaj S

How to handle Abandoned calls?

Is your customer worried about increasing number of abandoned calls? No worry.. :)
You can handle the abandoned calls very well in Genesys.
All you need to do is pay me some 100,000 £ (lol)..

To handle abandoned calls you have to first create a strategy that would have the business logic as required to handle abandoned calls. For example, to add the caller’s number to the callback list, or send a mail alert to the supervisor that your golden customer was left alone on the streets i.e., abandoned :). What next? Yes you have to execute this strategy in case of abandoned. For this use the function OnCallAbandoned[strategy name] , which sets the strategy to be executed if EventAbandoned is received..

Now you will be happy with appreciation mails from customer..lol..

Cheers!!
Gururaj S

Attaching Record information to OCS Record History logging

Record History logging provides you with additional reporting options for

calling lists. This logging process does not use database access to write logs;

instead it uses flat (text) files that the customer defines. You can turn enable this logging for selective calling lists.

How to configure Record history logging:

• In CME, select the calling list
• Go to Annex Tab and create section ‘default’, if not available already
• Create option ‘dial_log_destination’ with value as ‘Folder Path’ to store record history log files
• Create Option ‘dial_log_delimiter’ with value as ‘,’ to create comma separated delimiter between the fields

By default, it attaches the below mentioned mandatory fields

• record_id
• contact_info
• contact_info_type
• record_type
• record_status
• call_result
• attempt
• dial_sched_time
• call_time
• daily_from
• daiy_till
• tz_dbid
• agent_id
• chain_id
• chain_n

If you want to attach user-defined fields in the record history logging, please follow the steps below

• In CME, select the field .
• Go to Annex Tab and create section ‘default’, if not available already.
• Create Option ‘send_attribute’ with value as field name.

Record History log will then have the value with key as field name and value.. :-)

I am playing with Genesys 8.0 and planned to cover the details in the coming weeks.. keep watching this space..

Values of GSW_STAT_EVENT in log file

Last week, customer reported an issue 'Campaign Callback rescheduled call details are missing' in the canned reports. After few hours of log analysis, it seems to be a defect in Genesys Dialer (OCS) and raised SR with support team.

  I found this tabular list very useful while debugging reports for dialer solution and hope you will find it useful too

 CampaignActivated = 1,

CampaignDeactivated = 2,

DialingStarted = 3,

DialModeChanged = 4,

DialingStopped = 5,

WaitingAgentStart = 6,

WaitingAgentOver = 7,

WaitingPortsStart = 8,

WaitingPortsOver = 9,

WaitingRecordsStart = 10,

WaitingRecordsOver = 11,

SystemErrorStart = 12,

SystemErrorOver = 13,

CallCompleted = 14,

LeadProcessed = 15,

CallbackScheduled = 16,

CallbackCompleted = 17,

CallbackMissed = 18,

AgentError = 19,

RecordScheduled = 20,

Configuring SQL Server Express 2005 for Remote Access

If you are getting errors connecting to SQL Server Express 2005 via remote client software and don't have any problem connecting to it from the local machine, this post might be useful to you

If you are getting the error messages listed below, then we might have solution for you :-)

• sql server does not allow remote connections


• SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified


• An error has occured while establishing a connection to the server. When connecting to SQL Server 2005,this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.(provider:Named Pipes Provider,error:40-Could not open connection to SQL Server))


• Server does not exist or access denied

This issue occurs because SQL Server Express 2005 is not automatically configured for remote access and have to enabled  manually :-(

Follow the steps below to enable remote access in SQL Server Express 2005

1. Enable the TCP/IP protocol using the Surface Area Configuration Utility for remote connections


2. Enable the TCP/IP protocol in the SQL Server Configuration Utility


3. Make sure the SQL Server browser is started


4. Restart the system for changes to take effect

If you have any other suggestions, please let me know via comments and will update the post accordingly.

How do you configure ‘third party applications’ to be managed by Genesys?

You can monitor ‘third party applications’ like Tomcat in Genesys Management Framework. You need to configure new application object using ‘Third Party Application’ Template.

To start and stop using SCI, please configure start and stop command in Annex tab of the application object

To configure start command, Application –> Annex –> start_stop (section) –> start_command (option name)

To configure stop command, Application –> Annex –> start_stop (section) –> stop_command (option name)

I will be posting more tips & tricks in this site and if you would like to cover any particular topic, kindly let me know

How to avoid ‘Administrator’ access to supervisors?

In Genesys, if you are configuring non-agent, they are automatically added to the ‘Administrators’ access group. Many times, we have to configure Supervisors and would like to provide access to their agent group only. Prior to 7.6 version, it is achieved by creating new access group and removing the person from Administrators group.

From 7.6, you can disable the default access to the users. For every user, you need to manually assign him to the access group.

To disable the default access, create section ‘Security’ in Configuration Server ‘Options’ tab and configure the option to ‘no-default-access’ to ‘0’. Simple and found it useful to avoid any human errors