Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring CTI link reconnect and failover

Updated on October 12, 2021

If a local Pega Call CTI link loses its connection to the CTI Server, it will attempt to reconnect. If you have a secondary Avaya AES Server, configure a connection to it as part of CTI Link configuration. Pega Call will attempt to connect to the secondary CTI server if it is unable to connect to the primary CTI server.

On successful connection to the primary or secondary CTI server, Pega Call will attempt to retrieve the state of the devices/telephones for agents who were logged into Pega Call. This includes retrieving the state of calls on the device. Call-attached data is not retrieved as part of this process.

On successful connection to the primary or secondary CCT server, Pega Call will attempt to retrieve the state of the devices/telephones for agents who were logged into Pega Call. This includes retrieving the state of calls on the device. Call-attached data is not retrieved as part of this process.

  1. In the header of Dev Studio, click ConfigureChannel ServicesPega CallAdministration & Configuration.
  2. Click ActionsEdit to open the CTI Link. The rule form for that CTI Link appears.
  3. Click the Failover tab.
  4. Select Enable Failover?.
  5. Enter the Host name or ip address of the secondary AES server that Pega Call connects to.
  6. Enter the port that Pega Call connects to on the secondary server.
  7. Configure the user ID, password, and TLINK information for the backup AES server.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us