VoIPPress setup guide

What you need

WordPress

6.2 or newer

PHP

8.1 or newer

WooCommerce

7.0 or newer for customer and order matching (HPOS supported); the plugin also runs without WooCommerce

PBX

Asterisk, FreePBX or Issabel reachable over AMI (5038) or ARI (8088)

HTTPS

Recommended everywhere, required if the PBX notifies WordPress straight from the dialplan

Hosting

Shared hosting works with polling; real-time WebSocket push needs a VPS where a background process can run

Installation

1. 1. Install and activate the plugin

   Upload the plugin zip under Plugins → Add New → Upload, activate it, and enter your license key under VoIPPress → License. Activation lands you on the setup wizard.

2. 2. Connect your PBX

   In VoIPPress → Settings, choose your PBX type and fill in the AMI or ARI connection, then click Test connection. The wizard generates the exact configuration block to paste on the PBX side, including the permit line for your WordPress server's IP.

   [voippress]
   secret = YOUR_SECRET
   deny   = 0.0.0.0/0.0.0.0
   permit = YOUR_WORDPRESS_SERVER_IP/255.255.255.255
   read   = system,call,user,cdr
   write  = system,call,originate

3. 3. Let inbound calls reach WordPress

   Screen-pop needs the PBX to notify WordPress. Either run the bundled bridge agent on the PBX as a service (recommended — it keeps an AMI connection open and forwards events), or paste the generated dialplan snippet into your inbound context, which suits shared hosting.

   php voippress-bridge.php \
     --wp=https://your-site \
     --secret=INGEST_SECRET \
     --ami-user=voippress \
     --ami-secret=AMI_SECRET

4. 4. Add real-time push (optional)

   On a VPS you can run the WebSocket relay so screen-pops arrive instantly instead of on the polling interval. Put nginx in front for TLS and set the browser WebSocket URL in Settings.

5. 5. Give each agent their extension

   Every operator sets their SIP extension on their WordPress profile. That is what makes click-to-call ring the right device and attributes calls to the right person.

6. 6. Browser softphone (Pro)

   For calling from the browser, add WebRTC SIP accounts under VoIPPress → Softphone and assign them to operators — an operator can only register to accounts assigned to them. On Asterisk you need a wss transport, webrtc=yes on the endpoints and a TLS certificate on port 8089; the plugin includes a generator that writes that configuration for you.

Security notes

• Ingest requests are authenticated with an HMAC secret and rate limited.
• SIP credentials are encrypted at rest and never exposed to the browser.
• CSV exports neutralize spreadsheet formula injection.
• Charting assets are bundled with the plugin — no third-party CDN is contacted.
• GDPR export and erase are supported for stored call data.

If something does not work

Test connection fails

Check the firewall between WordPress and the PBX: AMI is 5038, ARI is 8088. The permit line in manager.conf must include your WordPress server's public IP.

No screen-pop on inbound calls

Confirm the bridge agent is running, or that the dialplan snippet is in the inbound context, and look for incoming rows in VoIPPress → Call history.

Calls stay stuck on ringing

The PBX is not sending CDR or hangup events. Make sure the AMI user has cdr read permission and the bridge agent is connected.

Most stores are live within an afternoon. Before buying you can also ask us for a walkthrough: the plugin includes a test-call simulator that shows the screen-pop without a PBX connected.