News

MaxiPBX evolves continuously

Each version brings new features, improvements and fixes — deployed automatically across all instances, without service interruption. Expand a version to see its details.

PBX PlatformDesktop ApplicationMobile Application

v1.17.6 ARI access automatically enabled across the entire fleet 16 August 2026

Fixed ARI access automatically enabled across the entire fleet: ARI access (introduced in 1.17.5) was only truly exposed on freshly installed boxes — an updated box received the engine but not its activation (connection to local Asterisk and HTTPS exposure on port 443). This is now fixed: ARI access is automatically deployed on each box, including those already in service. It only remains to create an identifier and its authorized IP addresses (global ARI menu, or per tenant in client settings)

v1.17.5 PBX API: standard authentication & OpenAPI documentation 16 August 2026

Improved PBX API easier to integrate: it now accepts the standard authentication header «Authorization: Bearer <token>», in addition to the legacy header — without changing anything for existing integrations
Improved Clarified OpenAPI / Swagger documentation for integrators: authentication schemes are described on protected routes (user/admin token recommended for integrations, legacy header preserved for compatibility, dedicated API key for hospitality/PMS routes), public routes not being marked as authenticated. The access model is clarified — a tenant administrator remains limited to their own tenant, a general administrator manages all tenants — and API access documentation (URLs, headers, examples) is added
New Service codes (feature codes) customizable per client: in System › Extensions, «Features» tab, the code for each service can now be changed per tenant (for example *9 → *99), beyond simply enabling/disabling — each client adapts function codes to their habits. The entered code is validated (digits and symbols * # +) and any collision with another code is rejected and reported. Responsive interface
New Secured ARI (Asterisk REST Interface) access, global and per tenant: Asterisk's low-level API can now be opened to third-party integrations (CTI, custom call applications) via a MaxiPBX gateway. Dedicated credentials (login and encrypted password) managed at global level (entire box) or per tenant (each client manages theirs, isolated to their scope); IP address restriction mandatory (whitelist — access closed by default until an IP is authorized); exposed in HTTPS on port 443 (REST and event WebSocket) without opening an additional port; a tenant identifier only sees and controls calls from its own tenant (call initiation remains reserved for global level)
New Agent leaderboard in call center statistics: a «Top 10» ranking of best agents, with filter by queue (one, several or all queues) and ranking criterion of choice — answered calls, conversation time, answer rate, answer speed, or a combined score (volume + rate + conversation + speed) — calculated over the selected period. Podium 🥇🥈🥉 for the top 3, responsive table
Improved Enriched call trace panel: a summary of the call remains always visible (identifier, direction, status, duration, source, destination, start and end time)
Improved Clearer network captures: the «PCAP 2 min» button, which was misleading, is replaced by a configurable capture (2 min, 15 min, 1 h, 6 h or 24 h), explicitly presented as a capture «from now on» and not the reconstruction of a past call; recent captures display with their status, duration, size and a download link

v1.17.3 Audio diagnostics & call tracing 16 August 2026

New Collecting diagnostics from the application: the PBX receives audio diagnostic reports sent from the Web or Desktop softphone, enriches them with its own context and forwards them to ControlPlane for support
New Tracing a call from its log (CDR): from administration, a « Display trace » button opens a visual timeline of the call's journey — normalized log, telephony events, artifacts and correlation link to collected diagnostics
New Network captures (PCAP) on demand for diagnosis: a tenant administrator can start a short capture of telephony traffic (from 10 seconds to 5 minutes), stop it manually and download it (authenticated access). This is not a permanent recording — you start a short capture when reproducing the issue; the last available capture is linked to the call trace, with its size and download link (« Start PCAP », « Stop », « Download » buttons)
New Cross-functional logging of all modifications: automatic audit now records every operation of creation, modification, deletion, login and system or tenant action — including those that were not explicitly traced before. Each entry preserves the author, the tenant concerned, the IP address, the action type, the target, the result (succeeded or failed) and a summary, with automatic masking of sensitive data (passwords, secrets, tokens). The audit is « best-effort »: it never interrupts the action in progress, and large files/uploads are not retained (only metadata). The audit log also gains a filter by author and a filter to view system actions only

v1.17.0 External storage for call recordings (per tenant) 16 August 2026

New External storage for call recordings: Recordings can now be stored on an external server rather than on the box's disk. As with messaging (SMTP), configuration operates at two levels — a global system-level setting (default destination) and per-tenant override (each tenant can have its own destination). By default, storage remains local: nothing changes for existing installations
New Supported remote destinations: SFTP, FTP, SMB and S3-compatible object storage (AWS S3, Wasabi, Backblaze B2, MinIO, OVH, Scaleway, Google Cloud Storage…) via access presets. A «Test connection» button validates the configuration; secrets (passwords, access keys) are encrypted
New Move and retention mode: the recording is sent to remote storage then removed from the local disk (according to retention policy), and playback or download retrieves the file remotely on demand. Separate retention policy — local retention in days, remote retention in months — with automatic purge

v1.16.7 Setup wizard before login & installations in wizard mode on NAT box 16 August 2026

New Setup wizard before login: a box deployed in wizard mode (with no domain name defined at installation) now displays, before the login screen, a «Finalize your installation» page. Enter the final domain name, public IP address and private IP address (pre-filled) as well as the setup token, then click «Finalize»: the log scrolls in real time (HTTPS certificate issuance and network configuration), and at the end you are automatically redirected to the login page at the correct valid HTTPS address. Each step is visible in real time — no more wondering whether it's working
Fixed Installation in wizard mode on a box behind NAT made reliable end-to-end — this combination previously failed at several points: the hostname no longer takes the public IP address (a numeric hostname prevented an internal component from starting, causing the entire installation to fail), a temporary certificate is deployed during the wizard so HTTPS services start (the final certificate is issued at finalization), and the SIP telephony listening address is automatically corrected to the box's actual local interface. Result: a wizard mode installation behind NAT now succeeds on the first attempt, with valid HTTPS and functional telephony

v1.16.5 Improved interface deployment reliability 15 August 2026

Fixed Improved web configuration reload after an update: on certain boxes, an interface update could leave the web server without reloading its new configuration, making the interface temporarily inaccessible until manual intervention. The reload is now deferred to the very end of the update — once all components are in place and configuration is validated — systematically and without any manual manipulation

v1.16.3 15 August 2026

Fixed Page inaccessible (404 error) after upgrading to 1.16.2 on certain boxes: the new interface is now served at the site root, but an update could retain the old per-language web configuration that redirected elsewhere. The interface's web configuration is now bundled with the application and refreshed with each installation and update — no more residual 404 errors after a version upgrade

v1.16.2 Language overhaul, self-service network identity & deployment assistant 15 August 2026

New Instant language switching: clicking a language switches the ENTIRE interface immediately — Web softphone, PBX admin — without page reload or network delay. And no more brief display in the wrong language on startup: the application waits to have the correct language before displaying any text
New Language follows the account: chosen once, it automatically appears on the Web softphone, Desktop application and Mobile — it's a preference saved to the user, not a setting to reconfigure on each device
Improved Lighter application and faster updates: translations for 60 languages are now loaded on-demand instead of being duplicated for each language — the web interface is much lighter to install and update
New Two ways to deploy a PBX: either fully pre-filled as today (FQDN and IP addresses entered in ControlPlane — the installation handles everything, including SSL certificate), or via an assistant when you don't have the information beforehand: the box starts on its IP address, reachable immediately via HTTPS; the client opens the softphone, connects, and the deployment assistant pre-fills the detected internal IP and public IP, then asks for the FQDN — on validation, the certificate is issued and all network and telephony configuration is automatically applied
New «Network» page in self-service admin: change the FQDN, public IP or internal IP (NAT) on-the-fly, later, without reinstallation — the relevant network configuration is replayed in a targeted manner and the certificate is automatically re-issued. The same page serves as an assistant on first startup
New Auto-detection of public IP address: no need to find it yourself, it's detected and pre-filled automatically
New «Deployment to finalize» banner on admin pages while the box is in assistant mode: first access by IP leads directly to the assistant, impossible to overlook
New Fresh APT-native installations (optional): code is deployed by the package manager at installation — same robustness as APT updates — with clean fallback to the classical installation mechanism

v1.15.1 E-mail support & CRM integrations 15 August 2026

New E-mail support: a lightweight ticketing service integrated into omnichannel — each tenant manages multiple support mailboxes (IMAP retrieval, SMTP sending). Incoming e-mails become threaded tickets, grouped by conversation; you can reply to the customer or start a new e-mail directly from the application, with attachments on both incoming and outgoing messages (25 MB, executable file types rejected)
New Organized e-mail tickets: statuses (open, pending, resolved, closed), priorities (low → urgent), automatic reopening of a resolved ticket when the customer replies, and e-mail polling frequency configurable per mailbox. Configuration in the admin via the new “E-mail support” card in the Communication menu (with connection test); on the WebRTC/desktop softphone side, a new “Support” section; on mobile, a dedicated screen via Settings. Strict multi-tenancy, mailbox credentials encrypted at rest
New CRM integrations: MaxiPBX now connects to leading CRMs — HubSpot, Salesforce and Zoho (one-click OAuth connection), Odoo, ConnectWise, Vtiger and Jetpack CRM (API key). The engine is generic: other CRMs will be added on the same foundation. Strict multi-tenancy: each tenant connects its own CRM, with its credentials and tokens encrypted and isolated — nothing is shared between tenants
New Customer record on call: on an incoming call, the number is looked up in the tenant's CRM — name, company and record are displayed (enriched caller presentation), with an “Open in CRM” button on the WebRTC/desktop softphone and on the mobile call screen
New Call logging in the CRM: every call (incoming, outgoing, missed — depending on options) is logged as an activity on the correct contact, and a contact or lead can be created automatically when the number is unknown
New Click-to-call from the CRM: a MaxiPBX browser extension (Chrome, Edge, Firefox) lets you call in one click from the CRM page — select a number or phone link, and the agent's device rings and then dials. Secure connection to the PBX (with 2FA), the access token is never exposed to CRM pages; non-invasive detection, quick dialing in the extension window, and “Enable on this site” for a self-hosted CRM
New New “CRM Integrations” admin page in the Communication menu: add a CRM, one-click OAuth connection or API key entry, logging options, record URL template, “Test” button, enable/disable
Fixed A box could get stuck in an update loop, version frozen despite retries: on some older installations, the previous archive-based update mechanism could fail to deploy the new code. These boxes are automatically unblocked with the new mechanism
Improved Updates are now installed via the APT repository — atomic installation, more robust and significantly faster (a few minutes instead of a full redeployment replay). Existing boxes switch over automatically, with a safeguard: if the new mechanism is not available on a box, the previous one takes over — no box can be blocked by the switch

v1.15.0 Omni Hub (Telegram, SMS) & enhanced support 15 August 2026

New The conversation hub (formerly “Livechat”) becomes a true omnichannel center, renamed “Omni” everywhere — WebRTC softphone, desktop and mobile application — and its menu is moved right after “History”
New Telegram, new channel: receiving incoming messages (secure webhook), agent replies and media, directly in the Omni inbox. Self-service configuration from the admin: “Add Telegram” — the bot token is enough, the webhook registers automatically. Note: a Telegram bot cannot initiate a conversation (platform rule), the user must start the bot; receiving and replying then work normally
New SMS via Twilio, new two-way channel: receive and send SMS from the desktop and mobile applications. Incoming SMS are verified (signature) and deduplicated before arriving in the Omni inbox like any conversation; an agent can also start an SMS to any number — “New SMS” button with choice of sending number, recipient and text. Self-service configuration from the admin: “Add SMS” with credentials and Twilio number
Improved Every conversation clearly displays its origin: channel icon and label (Web / WhatsApp / Telegram / SMS), colored avatar badge, and channel filters in the inbox
Improved The support ticket creation window, previously tiny, becomes a proper enlarged dialog — both in the PBX admin and in the WebRTC softphone
New Rich text editor for tickets: bold, italic, underline, bullet and numbered lists, links — message formatting is preserved and sanitized on the ControlPlane side
New Attachments on tickets: add multiple files at creation and in replies, with authenticated display and download directly in the thread
Fixed No more “it's not responding”: all support errors (loading, creation, sending, uploading) are now clearly displayed, in all 60 languages
Improved Reliable ticket-to-PBX linking: the box now transmits its instance identifier when creating a ticket — no more silent failure on opening

v1.14.5 60 languages & time zones 15 August 2026

New The entire interface goes from 15 to 60 languages: the PBX admin, the WebRTC softphone, the mobile app, the Desktop app, the ControlPlane portal and the maxipbx.com website now speak the same list of 60 languages. 45 languages added — including Ukrainian, Russian, Arabic, Hebrew, Persian, Hindi and the major Indian languages, Simplified and Traditional Chinese, Japanese, Korean, Vietnamese, Thai, Indonesian, Malay, Swahili and other African languages, Danish, Swedish, Norwegian, Finnish, Estonian, Latvian, Lithuanian, Catalan, Filipino… Everyone can choose their language in their usual app or portal
New Each tenant now has a default time zone, chosen at creation and automatically pre-filled based on the country (e.g. Morocco → Africa/Casablanca, France → Europe/Paris, Switzerland → Europe/Zurich), which can then be changed from its record. This time zone serves as the default value for everything created within the tenant — users, time ranges, voicemails: no more need to set it extension by extension
New Each user can keep their own time zone, which takes priority over the tenant's — useful for teams spread across several countries. Existing tenants are preserved: their time zone is deduced from their country, nothing changes for them
Improved Call logs displayed at the right time: timestamps in Recents are shown in the user's time zone (their own time zone, otherwise the tenant's, otherwise the device's), rather than always the device's local time
New Time-difference note on international contacts: in the contact list (desktop, WebRTC and mobile), a badge indicates the time difference for a contact with an international number — e.g. from Switzerland, a +212 (Morocco) number shows «+1h», starting from a 1-hour difference. For countries with multiple time zones (USA, Russia, Canada…), the badge intentionally remains approximate («≈») rather than showing a falsely precise time; the calculation takes daylight saving/standard time into account

v1.14.3 SSH-free remote management & worldwide emergency numbers 14 August 2026

New Remote PBX management WITHOUT SSH (remote management module): some customers disable SSH access after deployment — from now on, the box itself pulls its actions from the ControlPlane at each heartbeat and executes them (it initiates all connections: nothing comes in via SSH). Controllable actions: service restarts (whitelist), machine reboot, and switching between beta ↔ stable channels on the fly with continuous reconciliation
New Inventory reported at each heartbeat and visible on the PBX record: component versions, OS and kernel version, disk and memory, channel, service status — plus a command history (sent → executed → result) per PBX
New Deployment key (fallback access) automatically deposited: the public deployment key is installed on the server at installation and reconciled at each update — if it has been removed, it is put back in place. A fallback access in addition to SSH-free remote management, overridable for a white-label deployment with its own ControlPlane
New Emergency numbers: WORLDWIDE coverage — 177 countries pre-configured from the official ITU reference (1160 entries), merged with previously validated lists so that no number is lost (e.g. Australia 000, Spain, Greece; Switzerland gains Rega 1414/1415 and child helpline numbers). Switzerland: 112, 117, 118, 143, 144, 145, 147; France: 15, 17, 18, 112, 114, 115, 119, 191, 196, 197, 116000, 116117; United States: 911, 511, 811. A country not covered by the reference (e.g. Mexico, Indonesia) remains empty, with a warning displayed until the customer completes it
Fixed Yealink T54W — BLF keys finally provisioned: programmable keys (BLF, shortcuts) were not displaying on these handsets even though they were correctly configured on the server side. The phone model was registered under a form («T54(W)») that was not recognized: the keys were being sent to a non-existent expansion module instead of the screen's native keys. The fix automatically normalizes the model and re-pushes the configuration to the affected phones upon deployment — no manual intervention required, and this applies to any model noted with a WiFi variant in parentheses

v1.14.2 Tenant country & emergency numbers 14 August 2026

New Tenant country: when creating a tenant, you now select its country (telecom), which determines the default outbound call routes (national / international) without altering the dialed number. Worldwide coverage: standard profile (national prefix 0, international 00) for the vast majority of countries, special profiles for Switzerland and France (10-digit national numbering) and North America (1 / 011), and support for numbers dialed directly in +E.164 format. Existing tenants remain unchanged
New Emergency numbers defined by the customer: no more default Swiss list imposed — each customer now enters their own emergency numbers in their tenant, both at creation and when editing. A clear warning « No emergency number has been configured » is displayed as long as the list is empty, both in the form AND as a badge in the tenant list
Fixed Call answering: when a call is already in progress and a new call rings, « Answer » (mobile / desktop / WebRTC) now picks up the call that is RINGING, not the already connected call. Outbound calls are never treated as « to be answered » anymore

v1.14.1 One-click admin access from the ControlPlane 14 August 2026

New From a PBX record in the ControlPlane, an “Open admin” button opens the administration interface for that PBX directly, already logged in — no need to retype the URL or password (new tab). Each user within their own scope: general administrator everywhere, wholesaler / sub-wholesaler / reseller only on their own PBXs
Improved One-click access security: the ControlPlane connects to the PBX on the server side (the secret is never exposed to the browser), the session token is passed in the URL fragment (never sent to a server nor included in the Referer) and is immediately removed from the URL upon arrival. If the PBX admin account has 2FA enabled, one-click access is cleanly denied (manual login required). Every access is logged on the ControlPlane side
Improved Auto-login is only active on a PBX once it has been updated to 1.14.1 — it is the PBX itself that hosts the auto-login page

v1.14.0 Responsive administration — mobile, tablet, desktop 14 August 2026

New Main menu finally accessible on mobile: below tablet size, the side menu simply disappeared, making navigation impossible. A « hamburger » button now opens a sliding menu, with a darkened background and closes when clicking outside the frame or when navigating
Improved Windows (modals): no more overly tall windows being cut off — content and buttons (Save…) now scroll correctly on small screens
Improved Layout: no more horizontal overflow — images and wide content now adapt, and tables scroll within their own frame. The administration interface now adapts to all screen sizes, from smartphone to large monitor

v1.13.9 13 August 2026

Improved BLF keys — full parity with a physical phone: the BLF menu in the applications (WebRTC / Desktop / Mobile) now displays ALL keys configured for the user, regardless of destination type. The filtering that hid non-“monitorable” keys has been removed: monitorable destinations (user, group, queue, conference, extension) keep their live status lamp, others are displayed as simple keys
Improved Licenses — detail in tenant settings: the dialog now displays, in read-only mode, the People (used / licensed) and Devices counters, along with the mode tag (NFR / Trial) where applicable — figures recalculated live from the partner console, whereas previously only “max X ext” was shown. Editing remains reserved to the console: this panel is informational only

v1.13.8 Maxi UC Softphone — visual refresh 13 August 2026

Improved Cosmetic overhaul of the Maxi UC softphone interface, faithful to the mockup: midnight blue palette, Inter font, revised proportions
Improved Dial pad, BLF key rail and queue dashboard reworked (layout and readability); navigation and side panel adjusted, labels completed in all 15 languages
Improved This version ONLY changes the softphone interface: no change to the telephony core or license management — the entire 1.13.7 foundation remains unchanged

v1.13.7 License management — complete overhaul 13 August 2026

New Licenses are now based solely on extensions, with TWO independent counters per customer: “People” (person-type users) and “Devices” (device-type users). No per-feature or per-simultaneous-call licensing; each counter is an explicit integer — 0 is a valid value (e.g. a 100% device-only customer)
New Managed from the partner console: each distributor manages licenses within their scope (general administrator, wholesaler, sub-wholesaler, reseller), with both counters editable from the PBX record. Three license modes: Paid, NFR (free) and Trial (free period with an end date) — NFR and Trial are reserved for the general administrator and the wholesaler, with a tag displayed on the customer
Improved On the PBX administration side, license editing has been removed: it is now handled exclusively via the partner console. The quota remains viewable in read-only mode, with a new “Refresh” button on the License card in system settings
New Signed lease and offline operation: the console issues a signed lease (counters + mode + 7-day validity) which the PBX caches — automatic refresh every 5 minutes, immediate push on every change, and manual refresh available. The PBX continues to operate even if the console is temporarily unreachable, within the lease's validity period
New Unified lifecycle and “emergency calls only” lockout: regardless of the cause (non-payment, expiration, prolonged loss of contact), a grace period is followed by lockout at D+10. A locked customer keeps its phones registered, but only EMERGENCY CALLS remain possible (numbers from the Emergency module + the 112/117/118/144/911 safety list). Lockout enforcement ships DISABLED by default: pre-production validation is required before any activation across the fleet — in the meantime, the mechanism runs in observation mode, with no impact on calls
Fixed Carrier trunks (Kissgroup / France model): more resilient registration in the event of a temporary blacklisting on the carrier side

v1.13.6 13 August 2026

Fixed Kissgroup carrier template (France): cleanup of pre-filled form values
Improved Improved reliability of the hot update of the variable IP address carrier table

v1.13.5 New « Maxi UC » softphone interface 13 August 2026

New Softphone: new « Maxi UC » visual identity — navy blue styling, redesigned Composer / Calls dock, and real-time dashboard

v1.13.4 13 August 2026

Improved The variable IP address carrier table now updates HOT, without restarting telephony

v1.13.3 13 August 2026

Fixed Additional safeguard against an empty carrier configuration during deployment

v1.13.2 13 August 2026

Fixed Fixed a telephony configuration error at installation, introduced in 1.13.1

v1.13.1 13 August 2026

Fixed Improved reliability of the deployment of support for variable IP address carriers (introduced in 1.13.0)

v1.13.0 Variable IP address carriers 13 August 2026

New Support for SIP carriers with variable IP addresses: incoming calls from a trunk whose carrier changes address (multi-server infrastructure, dynamic addresses) are now correctly recognized and attached to the right trunk — without having to manually maintain an address list
New New carrier template: Kissgroup (France) — the catalog of pre-configured carriers expands beyond Switzerland
Improved Trunk creation: country selection is now a worldwide list with built-in search

v1.12.3 Call recovery in applications 13 August 2026

New The PBX exposes the list of a user's ongoing calls: an application that has just started can thus detect a call that is ALREADY in progress (the app was closed and is reopened while it is ringing) and « recover » it — making it ring on the device that has just opened. This also applies to resuming a call answered on another extension

v1.12.2 BLF keys in the applications 13 August 2026

New The PBX now exposes, for each user, the BLF keys configured on their handset and the real-time status of monitored extensions (idle, ringing, on a call, on hold, away), read directly from the telephony system. The MaxiPBX applications (« BLF » menu/tab on Desktop/WebRTC and Mobile) rely on this service to reproduce the supervision keys of a desk phone, with one-click calling. Available for all accounts — including telephony users, not just administrators — with no additional configuration required

v1.12.1 E-mails via Microsoft 365 & Google Workspace 13 August 2026

New Sending e-mails via Microsoft 365 and Google Workspace: since Microsoft and Google no longer allow sending via classic SMTP (username + password), the e-mail configuration now supports their modern methods — both at platform level (system SMTP) and per client (a tenant's dedicated SMTP). New « Sending provider » choice: standard SMTP (unchanged), Microsoft 365 or Google Workspace
New Microsoft 365: sending via the Microsoft API (Graph) — requires entering the Azure tenant ID and sender address, with a Microsoft 365 administrator consent (same principle as for Teams). Google Workspace: sending via the Gmail API — requires a Google service account JSON key (domain-wide delegation) and sender address. Secrets are never displayed again (« already saved » indicator) and a test-send button is available for each method
Improved Administration interface adapted to all screen sizes, including laptops and small resolutions: large windows (user/extension record, queues, groups, devices, tenants…) no longer fill the entire screen or overflow it — width adjusted to the screen and automatic density on short or narrow screens, with scrollable content
Fixed User/extension record: the « Save » button now always remains visible at the bottom of the window, regardless of which tab is open (it could previously move out of frame on the longer tabs)

v1.11.9 Two-Factor Authentication (2FA) 12 August 2026

New Two-factor authentication (2FA) for PBX administration accounts: each administrator can strengthen their account with a one-time code (TOTP) in addition to their password. Self-service activation from Settings → “Two-Factor Authentication”: scan a QR code with an authenticator app (Google Authenticator, Aegis, FreeOTP…), confirm a code, and receive 10 recovery codes to keep safe
New At login, the administrator enters their code after their password; a recovery code can replace the app code if needed. 2FA is OPTIONAL and left to each individual's choice — never imposed, disableable at any time — and only applies to administration accounts: telephony user login is strictly unchanged
Improved Supervised recovery: if an administrator loses their phone and recovery codes, a system administrator can reset their 2FA from administrator management. On the security side: encrypted secret, hashed and single-use recovery codes, no bypass possible for an account with 2FA enabled

v1.11.8 PBX ↔ PBX Interconnection 12 August 2026

New New trunk type “PBX Interconnection”: connect this PBX to any other SIP PBX — another MaxiPBX or a third-party system (Asterisk, FreePBX…) — via a DYNAMIC registration-based trunk, with no fixed IP or VPN required. Ideal for linking two sites or two companies together
New Three topology options via the “Registration Direction” setting: this PBX registers to the other one; the other one registers here (dynamic remote address possible — incoming calls are recognized by authentication, not by IP); or both dynamic, designating as the fixed point the one with the most stable address
New Two-way routing: declare the DID and internal extension ranges of the remote PBX — dialing one of these numbers automatically routes out through the interconnection trunk
Improved Security: trunk disabled by default, strong password required, optional restriction to authorized IP addresses in addition to authentication. Fully configurable from the interface, with a connection guide for the other PBX (example provided for a third-party Asterisk)

v1.11.7 12 August 2026

Fixed Improved reliability of fleet updates — two failure cases at the very end of the process fixed, with the PBX never being taken down: on servers behind NAT, the update reconfigured the media flow with the public IP instead of the private IP (the NAT configuration is now stored on the machine and preserved across updates); and a web security header (HSTS) configuration file was missing from the update package. Servers with a direct public IP are not affected; these failures occurred after the service switchover — no box was ever taken out of service

v1.11.6 IPv6 dual-stack 12 August 2026

New IPv6 support (IPv4 + IPv6 dual-stack) on all installations: a PBX can operate in IPv4 only (as today) or in IPv4 + IPv6 simultaneously, across the entire chain — SIP signaling (IPv6 listening and advertising), RTP audio flows (address family chosen per call), softphone STUN/TURN relay, web interface/API/WebRTC, and firewall automatically covering IPv6 traffic. New optional “Public IPv6” and “Private IPv6 (NAT v6)” fields at deployment: left blank, nothing changes for the existing fleet. Declared IPv6 is retained during reconfigurations. Prerequisite: fixed public IPv6 (or delegated prefix) routed to the server, same ports as IPv4
New Enabling IPv6 on an ALREADY installed box: the IPv6 fields are also available in “Reconfigure” for an existing instance — reconfiguration regenerates telephony in dual-stack and restarts services. Safeguard: it stops cleanly, without disrupting anything, if IPv6 is not yet configured on the server's interface (it must be in place before reconfiguring)
New Trunks to IPv6-enabled carriers: the “SIP Server” field of a generic trunk accepts an IPv6 address — bare literal (2001:db8::1), bracketed, with port ([2001:db8::1]:5060) or as a URI. The PBX automatically brackets the address where required and switches registration and calls to the IPv6 socket when the carrier uses an IPv6 literal; a carrier using a dual-stack domain name remains routed over IPv4
Fixed Improved reliability of new installations on latest-generation servers: the web server configuration structure has evolved there, which caused certain installations to fail at the very end of deployment even though telephony was already in place. Three causes fixed — custom web domains placed in the correct configuration directory, TLS hardening without conflict with the default configuration (TLS 1.0/1.1 now genuinely rejected), and internal TLS verification without false failures. Existing installations are not affected; installation behind NAT on this type of server has been validated end to end
Improved IPv6 is delivered as enableable per installation, with production validation during a joint staging deployment. To be validated in a future step: automatic banning of IPv6 addresses (SIP anti-flood already covers IPv6) and direct phone provisioning over IPv6 — provisioning via the PBX domain name already works in dual-stack

v1.11.5 Security Hardening 12 August 2026

Improved Strengthened web encryption (hardening following a penetration test): the interface and API now only accept TLS 1.2 and 1.3 with modern algorithms (AES-GCM, ChaCha20) — legacy TLS 1.0/1.1 protocols and CBC algorithms (Lucky13 vulnerability) are no longer offered on the browser side. Older phones are not affected: their encryption (SIP-TLS and provisioning) goes through separate channels, kept compatible
Improved HSTS enabled: the browser is forced to remain on HTTPS, preventing downgrade attempts to an unencrypted connection
Improved Hardened SSH access: fewer authentication attempts allowed and reduced administration options. Two additional protections available per server: restricting SSH access to a list of administration IP addresses (the management server always remains authorized) and disabling password authentication in favor of keys only
Improved For reference: SIP anti-fraud and anti-attack protection (automatic blocking of addresses making repeated attempts, filtering of premium-rate destinations) was already in place and remains active

v1.11.4 Microsoft Teams, Expanded SSO & Installation Behind NAT 12 August 2026

New Installation on servers behind NAT (port forwarding) — full support: a PBX can now be deployed on a machine with a private IP behind a router/firewall, no longer only on a VPS with a public IP. New optional “Private IP (server behind NAT)” field at deployment; the entire telephony chain (SIP signaling, RTP audio flows, softphone STUN/TURN relay) listens on the private IP while advertising the site's public IP — registrations, calls and bidirectional audio as on a VPS. NAT configuration retained during reconfigurations. Prerequisite: fixed public IP and strict 1:1 port forwarding (SSH, web, SIP 5060/5061, STUN/TURN, provisioning, directory, RTP ranges), one PBX per public IP
New Microsoft Teams integration per tenant: Teams presence synchronization → extension (a user set to “Do Not Disturb” — and optionally “Busy” — in Teams automatically sets their extension to Do Not Disturb), configurable per customer in a new “Microsoft Teams” card (Azure tenant ID + Microsoft 365 admin consent)
New “MaxiPBX” Microsoft Teams app: the softphone (calls, contacts, call logs) directly in a Teams tab, with SSO SAML login — application package ready to publish in the Teams Admin Center. Prerequisite: WebRTC enabled on the extension and Azure AD application authorized by the customer
New SSO expanded to Microsoft Entra ID (Microsoft 365 / Azure AD) and Google Workspace: choice of identity provider in the SSO card (Okta, Microsoft Entra ID, Google Workspace or any generic SAML IdP), step-by-step configuration guide adapted to the provider, metadata accepted via URL (recommended for Entra ID, follows certificate renewal) or via XML file (Google Workspace). The non-operational OIDC configuration has been removed from the interface: SAML now covers all providers

v1.11.3 Okta / SAML SSO 12 August 2026

New SSO per tenant (SAML) — full integration natively built into the platform's authentication engine: each customer can enable single sign-on via their own identity provider (Okta, or any SAML IdP). New “SSO / Okta” card in the tenant's Security settings: method (Native / SAML), domain, IdP metadata and “force SSO for the entire tenant” option; the information to fill in on the Okta side (ACS URL, Entity ID, metadata URL) is displayed and copyable with one click
New “Sign in with SSO” button on the login page: the user enters their email and is redirected to their identity provider, then reconnected — with no impact on tenants that remain on classic login
New OpenID Connect SSO (Okta): per-tenant configuration (issuer, client ID/secret, scopes, displayed Redirect URI) and full identity verification (PKCE, JWKS signature check, iss/aud/exp/nonce). Final session token issuance is coming in a future version — SAML remains the recommended and fully operational path
Fixed User form: the window no longer closes when clicking outside it — no more loss of in-progress edits (closing via the cross icon or Escape)

v1.11.2 12 August 2026

Fixed Rooms “Emergencies” module now ACTIVE BY DEFAULT: actual execution of emergency scenarios is no longer locked by installation configuration — a simple update activates it across the entire fleet, with no re-provisioning or manual setting required. Remains disableable via an explicit system setting for establishments that wish to do so

v1.11.1 12 August 2026

Fixed Rooms — housekeeping service codes moved to a dedicated block (*571 cleaned, *572 to clean, *573 to inspect, *574 maintenance): codes *31/*32/*34 conflicted with existing PBX codes (agent login/logout, call listening). Code → status mapping remains configurable per establishment
Improved Trunk creation redesigned in two steps: choose the country (Switzerland listed first), then the carrier template in alphabetical order (MaxiConnect listed first for Switzerland, generic version at the end of the list) — two clear dropdown menus replacing the long grid of cards
Improved Rooms — “Room Groups” now has its own dedicated menu
Improved Rooms — express check-in: the room ↔ phone link is set up once and for all; when a guest arrives, only first name, last name, room and rights need to be entered (guest with separate first and last name)
Improved Rooms — consumption report locked at check-out and stay archive that is searchable and exportable, even months later
Improved Rooms — dedicated wallboard displayable on a TV: statuses and occupancy, flashing highlight (10 minutes minimum) of rooms that have called an emergency number, with detection of such calls from rooms, full-screen mode without side menu

v1.11.0 Rooms Module & Wallboards 11 August 2026

New New “Rooms” module (formerly “Hotel”), generic for hotels, hospitals, clinics, EMS, residences and care homes: room = permanent entity distinct from the occupant, multiple phones per room, arrival/departure (check-in / check-out), reset guaranteeing confidentiality between occupants, call profiles with real restrictions (emergencies never blocked), recurring wake-up calls that can also be triggered from the handset, room statuses + housekeeping via *31 to *34 codes, Do Not Disturb per room, room groups and inter-room calling policy, logged emergency calls, billing with rates, per-room event log, public REST API + webhooks + PMS connectors (OPERA / FIAS ready), phone monitoring with alerts, dashboard and dedicated reception interface with its own permissions
New Wallboard builder: multiple customized wallboards per tenant, choice of queues, configurable widgets (answered calls, missed calls, ongoing calls, average duration, wait time, agents online/busy/available/on break…), layout, theme and true TV full-screen mode
New Statistics menu transformed into a hub with 4 cards
New Direction filter in call logs and recordings (all / missed / incoming / outgoing)
New Reorganized user form: dedicated “Identifier” tab, “Recordings” section moved under “Advanced”
New Global country selector for GeoIP whitelists/blacklists in PBX security
New “Default Keys” menu moved under “Collaborators”
New Movable BLF separator to let keys overflow onto the expansion module (e.g. Mitel M685i)
New Customizable SMTP per tenant (falls back to the global system SMTP)
New Customizable email template for scheduled report delivery
New Interface available in 15 languages (translations completed)
Fixed Receptionist workspace: removed the wall of permission errors (dashboard hidden and redirect to the first authorized page)
Fixed Room call profiles that applied no real restrictions: restrictions are now effectively enforced on the telephony side
Fixed Rooms module activation that did not protect endpoints: effective access control now in place
Fixed Custom report fields (day, month, hour, metrics) now translated in all languages

v0.1.78 18 June 2026

New Administration rights centralized in General Settings: Tenant Admin system profile assignable per user and custom profiles managed in the same place

v0.1.77 18 June 2026

Improved Modals optimized for shorter screens: more compact display, better margins, and a narrower user form

v0.1.76 18 June 2026

Improved Unified schedule management: a single advanced interface, simply structured, without a simple / expert toggle

v0.1.75 31 May 2026

New Deployment pipeline validation release, with UI, orchestration and provisioning aligned
Fixed Recent fixes included for monitoring, phones and release workflows

v0.1.74 30 May 2026

New New dedicated tenant Notifications page for mobile / desktop push diagnostics
New Direct per-user actions: push test, token reset and diagnostic copy
New Tenant monitoring redirects push issues to this dedicated view
New Tenant audit added to navigation with quick filters, and in-call WebRTC quality diagnostic copy

v0.1.73 30 May 2026

New Tenant monitoring enhanced with a Mobile / Desktop Push tile and a resolvable incident center
New Recent push failures now surface in tenant alerts and incidents
Fixed Push incidents limited to the last 24 hours to avoid false red statuses

v0.1.72 30 May 2026

New Enhanced phone diagnostics (account language / timezone, admin-usable timeline)
New Hotel engine: wake-up calls and emergencies manageable from system settings
Fixed “Repair this phone” action: diagnostics, config regeneration and check-sync made more reliable
Fixed Mobile push registration: explicit tenant and reliable logging

v0.1.71 30 May 2026

New Release safeguard: the build verifies that UI, backend and release notes carry the same version number
New Direct access to System Settings pages blocked for tenant admins
New Enhanced tenant monitoring (trunk, user, phone, omnichannel and queue incidents)

v0.1.70 30 May 2026

Improved PBX monitoring cleaned up: tenant data (omnichannel, queues, users, phones) no longer appears there
Improved The system page now only displays services, PBX checks, system incidents, logs and release center

v0.1.67 30 May 2026

New Security separation of monitoring: tenant view cleaned up, PBX monitoring moved to System Settings
New System monitoring endpoints restricted to PBX administrators

v0.1.66 30 May 2026

New Operational incident center with tracked resolution
New Release Center in PBX Health: channel, policy and update status

v0.1.65 30 May 2026

New Phone action plan at the top of the Devices page, with per-device recommendations (repair, assign, reprovision)
Improved Simplified admin workflow to filter phones needing fixes, unassigned or detected

v0.1.64 30 May 2026

New Corrective actions in Monitoring: service restart, WebRTC tests, SMTP, push and phone web access
New Enhanced call center: answered calls, average SLA, longest wait and abandonment rate per queue

v0.1.63 29 May 2026

Fixed Refined TURN check (direct UDP port 3478 filtering): no more false negatives when many RTP streams are active

v0.1.62 29 May 2026

Fixed Fixed false positives in authentication and TURN monitoring (real API port verification, effective UDP listening detection)

v0.1.61 29 May 2026

New Call center monitoring: queues, waiting calls, abandonments and agents
Fixed Call services summary made tolerant of degraded responses

v0.1.60 29 May 2026

New Enhanced push monitoring with counters per channel and per source
New Push token resets logged to facilitate mobile / desktop diagnostics

v1.7.0 Diagnostic mode audio support & security hardening 16 August 2026

New Diagnostic mode (Tools menu › Diagnostic): if audio issues arise, start a collection, make your test calls, stop the collection, then send the report to support in one gesture
New Local collection of WebRTC audio metrics during the session (packet loss, jitter, latency, approximate MOS, codec, connection state, call events, audio devices, application version and platform) for precise diagnostics. Secrets and sensitive identifiers are excluded or masked before sending
Improved Application internal communication locked: sensitive actions (automatic login, notifications, window focus, closing, updates, remote control) now respond only to the main window and configured server — an unauthorized page or window can no longer trigger them. The local fallback screen (unreachable server) retains only reload and server change
Improved Account passwords better protected: a password is saved only if the operating system's secure vault is available; the old fallback storage (simply encoded, not encrypted) is removed — legacy passwords affected are removed during migration instead of being decrypted. Account management is restricted to its own « Accounts » window
Improved Secure remote control: each event (click, movement, scroll, key) is validated and bounded before execution, and invalid data is rejected. USB/HID device permissions are limited to already-supported telephone headset manufacturers (Jabra, Poly/Plantronics, EPOS, Yealink, Logitech)
Improved Diagnostic mode: clear status feedback in the application (collection start, stop and diagnostic send displayed) with any errors reported to the user

v1.6.2 Windows Signature 15 August 2026

Improved Windows: the application continues to be signed and recognized by Windows without security warnings — code signing migrates to a modern signing service, integrated into the build pipeline with automatic verification at each release. No visible changes to users; macOS signature and notarization remain unchanged

v1.5.7 Multi-server accounts & 60 languages 15 August 2026

New Account manager: via the new « File → Accounts » menu (also available in the tray), save multiple accounts — name, server URL, username, password — and log in with a single click, without re-entering your credentials. On launch, an account selector is displayed (it also serves as the initial setup); to switch servers, reopen « Accounts » and connect to another one: the application switches over and reconnects automatically. Accounts can be edited or deleted at any time
New Account passwords are encrypted via the operating system's keychain (macOS Keychain, Windows DPAPI, Linux libsecret). Seamless migration: the former single server automatically becomes the first account on first launch
Fixed Clicking the incoming call notification now brings the softphone to the foreground when it is running in the background — previously, the window would just flash in the taskbar without coming to the front (observed on Linux, same on Windows)
New « About » menu: a window displays the application name, version number and the currently connected server — accessible from the tray and from the « File » menu bar (along with Check for Updates, Switch Server, Quit)
Fixed Linux: the application previously displayed no menu bar (it only existed on macOS) — it is now built and visible on Linux, where the system tray is often absent. Windows keeps both the tray and the menu bar (press Alt to display it); macOS retains its system menu
New 60 languages: the Desktop application automatically follows the system language, among the 60 languages of the MaxiPBX ecosystem (with a distinction between Simplified and Traditional Chinese)

v1.5.2 Retrieve an ongoing call 13 August 2026

New Retrieve an ongoing call when opening the application: if the app was closed and a call comes in, opening it now shows you the ongoing call and lets you pick it up with a single gesture (“Retrieve call”) — the call then starts ringing in the application. This also applies to resuming, on the app, a call answered on another device

v1.5.1 13 August 2026

Fixed BLF keys: loading failed for user accounts (“action denied by remote service”). Fixed for all accounts, not just administrators (requires an up-to-date PBX)

v1.5.0 BLF Keys 12 August 2026

New New « BLF » menu: the line-supervision keys configured on your extension are now reflected in the application, just like on a desk phone. Each key displays the real-time status of the monitored extension (free, ringing, on call, on hold, away) and a click dials the extension directly. No need to reconfigure anything: the BLF keys already defined on your extension appear automatically. Requirement: up-to-date PBX

v1.0.2

New Stable download URL per brand (« -latest » alias)
New Clean recovery when the computer wakes from sleep
Improved Standardized Intel DMG naming to « -x64.dmg » (symmetry across macOS architectures)
Fixed Server input screen disabled in white-label mode
Fixed Fallback screen when the server is unreachable (end of the blank page issue)
Fixed Linux icons: fixed minimum required size and generic icon issue on GNOME

v0.1.3 20 May 2026

Improved Auto-update migrated to a more reliable distribution channel, with direct reading of version manifests

v0.1.2 20 May 2026

Fixed Auto-update now correctly detects new versions again

v0.1.1 20 May 2026

New Support for USB headsets (Jabra, EPOS, Yealink, Poly): answer/hang up from the headset
New « Change server » button directly from the login page

v0.1.0 First public release 20 May 2026

New First public desktop release: Windows, macOS Intel / Apple Silicon, Linux
New WebRTC softphone in a native window, with server selection on first launch (multi-reseller)
New Notification area icon with menu (change server, updates, quit)
New Automatic background updates
New Native microphone / camera / notification permissions handled
New macOS build signed with Developer ID and notarized by Apple

v1.6.1 Email support & CRM on mobile 15 August 2026

New “Email Support” screen (accessible via Settings): view tickets from your support mailboxes, reply to the customer, attach files, manage statuses and priorities — the same features as on desktop
New CRM on mobile: on incoming calls, the contact is resolved in the tenant's CRM (name and company displayed) and an “Open in CRM” button appears on the call screen

v1.6.0 Omni (Telegram / SMS) & more reliable support 15 August 2026

New Omni on mobile: the application receives and replies to Telegram and SMS conversations, clearly distinguishes the channel of each conversation (icon on the avatar), and allows starting an SMS from the mobile device. The « Livechat » menu is renamed « Omni » and moved after « History »
Fixed The Support screen no longer remains unresponsive when opening a ticket: the application automatically benefits from the fix delivered on the ControlPlane side — the ticket is now created in all cases. Attachments will arrive in an upcoming batch

v1.5.7 Time zone offset in the directory & 60 languages 15 August 2026

New “Time zone offset” indicator on international contacts in the directory: a badge signals the time difference for a contact with an international number — e.g. from Switzerland, a +212 (Morocco) number displays “+1h”, from a 1-hour difference onward. For countries with multiple time zones (USA, Russia, Canada…), the badge is intentionally approximate (“≈”); the calculation accounts for daylight saving/standard time, exactly as in the desktop application
New 60 languages: the mobile app now speaks all 60 languages of the MaxiPBX ecosystem (15 → 60), including Ukrainian, Russian, Arabic, Hebrew, Hindi, Chinese, Japanese, Korean, Vietnamese, Thai, Indonesian, Swahili and many others

v1.5.6 More reliable wake-up from background 14 August 2026

Fixed Fixed the “no server configured” message that could appear when reopening the app from the background, even though the server was correctly configured: under the load of waking up, the phone's secure keychain would intermittently return “empty” even though the value existed — the app wrongly believed it no longer had a server
Fixed This same read gap on wake-up could cause line registration and call setup to fail. With the app fully closed, reception already worked correctly — the issue was specific to returning from the background
Fixed Device account robustness: the device identifier could be mistakenly regenerated in this same scenario, which disconnected the mobile session — fixed
Improved The app now briefly retries reading its configuration, session, and identifier before concluding they are missing: a temporary keychain glitch no longer breaks anything

v1.5.5 iPhone Call Reliability 13 August 2026

Fixed iOS — fixed « silent » pickup / phantom call issue: the call screen could switch to « connected » (timer started) before the audio link was actually established — you would answer and the call would remain silent, or drop immediately. The application now waits until audio is actually active before validating the pickup; if the connection cannot be established, the call ends cleanly instead of leaving a frozen call card on screen
Fixed iOS — incoming call received with the app COMPLETELY CLOSED: the call notification could arrive before the app was ready to process it, and the call would not ring. Such calls are now stored and processed as soon as the app wakes up — ringing is guaranteed even after a full closure
Improved iOS — safeguard: if the pickup cannot succeed (call never received on the server side, network cut off, audio impossible), the call is cleanly terminated within 15 seconds instead of remaining displayed as « connected » indefinitely
Improved Android: no behavior change — call handling relies on the system's native telephony integration and is not affected; these improvements are specific to iOS

v1.5.2 Retrieve a call + improved call reception reliability 13 August 2026

New Retrieve an ongoing call when opening the app: if the app was closed and a call comes in, opening it shows the ongoing call so you can pick it up with a single gesture (“Retrieve call”). This also applies to resuming on mobile a call answered on another extension
Fixed iOS — call reception reliability further improved: after an extended sleep period, the app could believe it was still connected to the server even though its connection had actually been dropped; as a result, it would not re-register and the call would not go through (the screen showed “connected” but with no audio, while the caller kept hearing ringing). The app now checks the ACTUAL state of its connection and systematically re-registers on wake-up / on every incoming call

v1.5.1 13 August 2026

Fixed Fixed « no server configured »: in certain cases (right after a phone restart or during a slow launch), the app could display this message and fail to reach the server even though the configuration was properly saved. The server configuration and session token are now cached and made resilient — no more repeated vault reads on every request, and a temporarily failed read no longer causes the configuration to be lost
Fixed Incoming calls: if an answered call failed to connect (the call never reached the app — network issue, phone waking up), the call screen could remain « connected » with no audio while the caller heard ringing with no answer. The call is now properly ended instead of getting stuck
Fixed BLF keys: loading failed for user accounts (« action refused by remote service »). Fixed for all accounts (requires an up-to-date PBX)

v1.5.0 BLF Keys 12 August 2026

New New “BLF” tab: find your extension monitoring keys directly in the mobile app. Each key displays the real-time status of the monitored extension (free, ringing, on call, on hold, away) and a single tap calls the extension. BLF keys already configured on your handset appear automatically. Requirement: up-to-date PBX

v1.0.2 (build 52)

New Precise linking of incoming calls to their push notification (unique call identifier)
New Diagnostic log now viewable directly within the app
Fixed iOS: in-depth reliability improvements for call notifications (recurring VoIP push blocking issue resolved)
Fixed iOS: reserved execution time for answering calls in the background
Fixed Android: the “Answer” button in the notification now picks up correctly
Fixed iOS: callback from the phone's “Recents” log
Fixed Outgoing call: ringback tone and muted audio fixed on iOS
Fixed Call screens: fixed residual mappings and display priority