Predictive outbound in Genesys(Avaya pbx)

Intended Audience: If you want to configure outbound in predictive mode in Genesys CTI and Avaya pbx.

Prerequisites: Genesys framework and Outbound solution (OCS and OCM)

Before beginning the work, ensure that your Avaya pbx has Call classifier card configured with enough number of call classifier ports.

Predictive dialing needs Vector Destination Numbers (VDNs) to be configured both in the switch and Genesys CME.

You can verify with Avaya personnel to create a VDN on the switch.Make a note of the VDN created. Now create and configure the same VDN on CME. VDN in CME is  a DN of type route point with switch-specific type as 2. Done ? now you can consider as half way through!

Make sure from the Avaya personnel that the VDN has Class of Restriction (COR) configured to allow outbound dialing. You can test the same by making a call from that VDN manually.

Now we will go to the routing part. In IRD, create a simple strategy to route the calls to an agent group. Load the strategy on to the VDN.

Now create a calling list with outbound numbers. Logon your agents. Start your OCM and run the campaign. In IRD's monitoring view of the strategy,[polldaddy poll=1061554] see if the calls are routed.

Can you see the call in agent desktop?. Cheers! :)

NO ? Post your error code in this blog and Lakshmi is there to help you :))

Network Logging in Genesys

How to configure network logging in Genesys ?

Network logging in Genesys is a multi-step process. First, the application sends the log record to Message Server. Message server sends record to update in DB.

1. Create Log Database 

2  Initialize the database using the scripts in Message Server installation folder

3. In Message Server, add connection to LogDAP

4. In Message Server, set property 'messages\db_storage' as "true"

5. From any application object (like T-Server), add connection to the Message Server

Please note that log level should be set to network for any centralized logging. 

It is simple, isn't it?

CTI link bouncing

Yes.. This could be a rare scenario as you think. But if you have used T-server with switch simulator,chances are more that you could have encountered this problem.

In this case, the T-server disconnects from the switch and status changes to "Service Unavailable".But after a while, the switch - Tserver connection is restored and the status becomes "started". Again, this doesn't last for much time. Just wait for some 45 seconds and the link goes down. And this game continues to give the same trouble.

Solution: In T-server, the option ts-tp-enabled should be set to false and this will fix the problem if you are as lucky as i am.. :)