Skip to content

v2.2.0

Choose a tag to compare

@github-actions github-actions released this 05 Nov 20:25

What's new

Inbound SMS and MMS Webhooks

Forward incoming messages from any configured messaging provider to another application, using a consistent Telnyx-style event format.

Highlights

  • Set an account-wide destination under Account Settings → Messaging.
  • Choose Members, Account webhook, or Custom webhook for individual numbers in Message Settings.
  • Forward SMS, MMS attachments, and supported group participants. Attachment download links remain valid for 24 hours.
  • Verify incoming events using the account's shared signing secret, available to authorized administrators through Show and Copy controls.
  • Automatically retry failed deliveries while keeping the same event ID for duplicate protection.
  • Keep messages in administrative logs with a separate webhook delivery status. Forwarded messages bypass user conversations, unread counts, Ringotel, and email.

Saving a Custom webhook removes the number's members and email assignment, including members' ability to send from that number. Account webhook retains those assignments and uses them again if the account webhook is removed. Delivery changes apply to new messages; a failed webhook delivery does not fall back to members.

Receivers verify the Signature header using HMAC-SHA256 and acknowledge with HTTP 2xx. This uses an FS PBX shared secret, not Telnyx's signature scheme. Apply the database migrations separately from app:update.

Message Settings API Updates

The v1 Message Settings API can now switch a number between local members and webhook delivery.

Highlights

  • Create and update settings with inbound_delivery set to inherit, members, or webhook.
  • Set a custom destination with inbound_webhook_url, which requires a public HTTPS address.
  • Retrieve the saved delivery mode and custom URL in list and individual responses.
  • Keep signing secrets out of API responses; authorized administrators retrieve the shared secret in the interface.
  • View and copy a number's Message Settings UUID from its edit form for use in API requests.

The API documentation includes the new fields, examples, and assignment behavior. These endpoints configure message delivery; they do not send SMS replies.

Postmark Webhook Authentication

Postmark callbacks now require authentication for both outgoing email status updates and incoming email-to-fax.

Highlights

  • Require matching HTTP Basic Auth credentials before accepting Postmark events.
  • Reject requests when credentials are missing, incorrect, or not configured in FS PBX.
  • Expand the setup guide with separate instructions for outgoing email events and incoming email-to-fax, plus troubleshooting for delivery status and authentication failures.

Existing Postmark users must set POSTMARK_WEBHOOK_USERNAME and POSTMARK_WEBHOOK_PASSWORD in FS PBX and configure matching credentials on every Postmark webhook pointing to FS PBX. Apply the configuration and restart background workers as described in the Postmark guide. Until both sides match, email status callbacks and incoming email-to-fax requests are rejected.

Polycom Provisioning Upload Security

FS PBX 2.2.0 disables the old unauthenticated Polycom upload paths while preserving uploads through native provisioning.

Highlights

  • Removes the old unauthenticated Polycom log upload endpoint.
  • Disables legacy uploads for phone logs, configuration files, contact directories, call history, and core files.
  • Preserves previously uploaded files and their existing read access on upgraded servers.
  • Keeps native /prov/ uploads and their existing provisioning authentication settings unchanged.

Phones still using the legacy upload URLs must switch to native provisioning to continue uploading files.

Thanks to @nik-kl for reporting the legacy Polycom upload and mobile caller-ID security issues.

Improvements and fixes

  • Fixed Play Greeting in Basic Dialer when a recording path contains spaces or special characters.
  • Made Business Hours holiday destinations consistent with Phone Numbers, including voicemail names and clear warnings for missing destinations. Holiday lookups remain limited to the current account.
  • Failed email sends now show Failed instead of remaining on Sending. Retried fax and application-credential notifications reuse their email log entries, and a successful retry updates the same entry to Sent.
  • Corrected account selection for fax notification emails, including email-to-fax preparation failures, so notifications use the fax's account settings and templates.
  • Added a Voxutel SMS/MMS setup guide covering credentials, webhook configuration, media storage, and troubleshooting, with clearer diagnostics for rejected Voxutel webhooks.
  • Caller-ID changes from Ringotel custom pages now require an active mobile user and are limited to that user's extension and enabled numbers in the same account. No additional portal login is required.
  • New installations no longer enable the legacy Polycom upload directories in Nginx.
  • Existing servers update only recognized legacy locations present in their Nginx configuration. Unrecognized custom locations produce a warning for manual review.
  • Nginx configuration is backed up and validated before reloading. Failed changes are rolled back where possible, with warnings and retry instructions if the update cannot finish.