Change Log
JEDWare Change Log Every JEDWare release is listed below with what changed. The same notes are shown in the app under What’s new in the
Installing JEDWare means installing one integration on your 3CX server and logging in to the JEDWare web app. The requirements are short: 3CX v20 Update 6 or later with a Pro or Enterprise license, on Debian 10 or later from the 3CX ISO or on a supported Windows Server, and a JEDWare license key. The integration reads call data from 3CX and sends it to the JEDWare cloud, which is where you log in.
The guides below cover the whole life cycle of the integration. Get started with JEDWare takes a new customer through the four steps: license key, integration on the server, the network rule and the first login. There are separate installation guides for Debian and Windows, a guide for updating when the app asks for a newer version, and an uninstall guide for Debian.
Operations questions have their own pages: how to restart the JEDWare service on Debian or Windows, what to check when the integration status shows No connection, and which IP addresses and ports JEDWare uses, so the firewall rule can be prepared before the installation. The Change log records what each release of the app and the integration changed.
Most support cases that start with “JEDWare is disconnected” end with a restart of the service or a missing network rule, so those two guides are the first place to look.
JEDWare Change Log Every JEDWare release is listed below with what changed. The same notes are shown in the app under What’s new in the
JEDWare adds reports, dashboards and live wallboards to your 3CX phone system. Getting it running takes four steps: a license key, the integration on your
The JEDWare integration is a small service that runs on your 3CX server and talks to the JEDWare cloud. Check the list below before you
The installation takes about five minutes. You need: Root access to the 3CX server, in a terminal or over SSH. Your JEDWare license key, found
The installation takes about two minutes. You need: An administrator login on the 3CX server. Your JEDWare license key, found on your user page at
A restart of the JEDWare integration fixes most connection problems: the status No connection, a lost connection after a 3CX update, or a wallboard that
Most of JEDWare lives in our cloud and is updated without you doing anything. The integration on your 3CX server only needs an update when
This removes the JEDWare service, its files and its Nginx configuration from the 3CX server. Your JEDWare account, license, users, wallboards and scheduled reports stay
Ports The JEDWare integration reuses the Nginx configuration of your 3CX server, so it uses the same HTTPS port as the 3CX web console: 443
JEDWare shows No connection when the cloud cannot reach the integration on your 3CX server. The usual causes: The 3CX server was updated or restarted