From da48ade747abd72d2b1fb21ed9eeb7248e57af7b Mon Sep 17 00:00:00 2001 From: Ralf Becker Date: Wed, 26 Jan 2022 20:05:24 +0200 Subject: [PATCH] Updated CTI Computer Telephone Integration (markdown) --- CTI---Computer-Telephone-Integration.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/CTI---Computer-Telephone-Integration.md b/CTI---Computer-Telephone-Integration.md index a043c8d..915a3b3 100644 --- a/CTI---Computer-Telephone-Integration.md +++ b/CTI---Computer-Telephone-Integration.md @@ -32,7 +32,8 @@ To configure the integration you need the credentials of your Placetel (test-)ac Asterisk integration uses the ARI (Asterisk REST API) to talk to the Asterisk server and receive call events to show an automatic CRM view and record calls. Asterisk can not call a webhook for incoming and outgoing calls, but uses a websocket connection with ARI. Therefore you need to install an event forwarder to connect to ARI via a websocket and forwarding call events to EGroupware's webhook. The event-forwarder is available as container or NodeJS script which can run any server having access to the Asterisk and EGroupware server (including both of them): ``` -docker run -d -e EGW_WEBHOOK="http://cti:secret@172.17.0.1/egroupware/stylite/cti.php" -e ARI_URL="http://asterisk:secret@172.17.0.1:8088/ari" quay.io/egroupware/asterisk-events +docker run -d --restart=always -e EGW_WEBHOOK="http://cti:secret@172.17.0.1/egroupware/stylite/cti.php" + -e ARI_URL="http://asterisk:secret@172.17.0.1:8088/ari" quay.io/egroupware/asterisk-events ``` > Asterisk integration happens between EGroupware and Asterisk Server and does NOT need any configuration on the users workstation. ARI obviously need to be enabled and accessible on your Asterisk server.