Adding Genesys Engage (Platform SDK) links
The Genesys Engage (Platform SDK) link is a Java-based connector that connects the Pega Platform server to a Genesys Engage server. This is an out-of-the-box integration that Pega Call provides for local Genesys Engage connections.
- In the navigation pane of App Studio, click .
- In the list of computer telephony integration (CTI) settings, click CTI link setup.
- On the CTI link setup page, click Add new link.
- Enter a name and description for the link.
- In the Link list, select Genesys Engage (Platform SDK).
- In the T-Server host name field, enter the host name or the IP address of the T-server.
- In the Port field, enter the port number to which Pega Call connects.
- In the Tenant ID field, enter the unique identifier for the tenant in a multi-tenant environment.
- In the Application Name field, enter the Pega Call application name as configured in the Genesys framework.
- In the Password field, enter the application password as configured in the Genesys framework.
- If you want Pega Call to attempt to connect to a secondary server if the connection to the primary server fails, select the Enable failover check box.
- If you have enabled failover, configure the failover settings:
- In the Secondary t-server host name field, enter the secondary T-server host name.
- In the Port field, enter the secondary T-server port number.
- In the Tenant ID field, enter the unique identifier for the tenant in a multi-tenant environment.
- In the Application Name field, enter the Pega Call application name as known in the Genesys framework.
- In the Password field, enter the application password as configured in the Genesys framework.
- In the Telephony switch field, select the telephony switch to which the T-Server connects.
- In the Reason Codes section, add one or more reason codes for an agent to indicate to the telephony switch why they are setting themselves as unavailable (not ready) for calls, or logging out of the CTI user interface.
- Confirm your updates by clicking Save.
Previous topic Adding AACC links Next topic Adding Cisco ICM/UCCE links