Release 1 Rollout (and abandoned calls)

After MI and softphone issues were resolved, this week we finally rolled out Release 1 of the solution for this client to the remaining Contact Centre sites. This means we are now live with approximately 2000 advisors handling 35K+ calls per day.

As usual the go-live was not quite as smooth as we would have liked. By Monday afternoon we were starting to get calls from Customers complaining that they had waited a long time in queue, hungup, called back and got answered immediately.

Realtime and historical statistics gave no indication of the problem. After a lot of digging by the team we identified that calls were getting stuck on external routing points (ERP) between the Genesys SIP side of the solution and the Avaya side of the solution.

The root cause of the problem was the Class of Restriction (COR) on the Avaya stations was not set correctly on a small number of stations. This resulted in the call setting stuck in the vector associated with the ERP (VDN). Unfortunately these advisors kept getting targeted again and again which meant that the total number of stuck calls was much higher than the number of incorrectly configured stations (for obvious reasons I won’t tell you how many calls were affected by this problem!).

As a secondary problem we found that there was no skill applied to the ERP VDNs. This caused the call to enter a “black hole” since as a backup even through the associated vector was set to target advisors there was no Avaya skill / split specified.

Further analysis showed that the maximum time to abandon was 99 minutes. We tracked this down to the “Vector Disconnect Timer” specified in the ACM system parameters:



SAP Gplus Load Balancer

A load balancing mechanism between SAP CRM and multiple Genesys SAP Gplus (ICI) adapter instances seems to be the source of much debate and frustration!

The standard response from SAP and Genesys seems to be to create multiple SAP roles / profiles and to tie these to individual Gplus instances via the SAP Communcation Profile.

However, in large deployments (2000+ users) such as at this client this does not really seem a feasible approach.

Further investigation into the Integrated Communication Interface (ICI) between SAP and the Gplus adapters seems to reveal the problem – traditional load balancing (without using SSL possibly) is not possible since there is no session information in the HTTP header:


Therefore, technically the only option is to implement “user affinity” based on the <user> element in the SOAP header:


So with this in mind I wrote a custom SAP Gplus Load Balancer Service which provides a load balancing mechanism using user affinity between SAP CRM and multiple Genesys SAP Gplus adapter instances.

The SAP Gplus Load Balancer is implemented as a Windows service which can be deployed on multiple physical servers and run in parallel to provide resilience and failover capabilities. SAP Gplus Load Balancer instances can be configured as application of type Third Party Server in Genesys CME allowing instances to be monitored and controlled using standard Genesys management framework components such as Solution Control Interface (SCI).

Here is an architecture diagram:


Let me know if you want more information!