CTI Link Pro and DevLink 3: Varieties and Which to Use

Do I need a CTI Link Pro license and which variety of DevLink 3 should I use?

Monitor

In older versions of IP Office, Chronicall would need to connect to the UDP based Monitor feed in order to log call data. This method was imperfect as it depended on packets to deliver data which is unreliable. Xima worked with Avaya to establish a method to connect and gather data that was connection-based, with the fruit of this labor becoming DevLink 3.

DevLink 3 was introduced with IP Office R10 and Chronicall 3.8 with Monitor support for call data being discontinued at that point. Though Monitor may work on occasion, the correct method to connect Chronicall to the PBX is via DevLink 3.
This interface is included in the CTI Link Pro license with Avaya and is required on most installations.

With the introduction of IPO R11, we now have the option to connect to the PBX via the regular DevLink (port 50797) or a WebSocket, though most cases of IPO R11 will still use the standard DevLink3 to connect.
- The difference is seen when the IPO and Chronicall are housed in separate networks from one another.
- Hosted does not mean they will use the WebSocket as usually the PBX and Chronicall servers are both hosted on the same network and therefore can communicate internally.
The WebSocket needs to act differently as Chronicall will not be in the same network as the IPO and will need to communicate over the internet. Most companies will not be comfortable with opening their PBX ports to the world so we need a way to talk to it, thus the use of the WebSocket communications protocol.
- This will only work with R11 and will be the method companies will connect to our in-house Hosted Solution. Typically, the PBX will be either onsite or hosted itself, and Chronicall will be hosted in a completely different location/network.
WebSocket does still use Devlink 3 and will require CTI Link Pro licensing. This functionality was introduced in Chronicall 3.10.2c.

"Powered By Avaya" is an exception as it is hosted by Avaya and Chronicall is typically still local. "Powered By Avaya" is connected to the customer's network and everything acts like it is local so we will still use the standard DevLink 3 connection.
- Additionally, "Powered By Avaya" does not need a purchased CTI Link Pro license as it is built-in.