Repository navigation
v2.2.4
What's new
Guided Network Setup
FS PBX 2.2.4 adds Network Setup under Advanced → Variables to help configure the addresses used for SIP signaling and call audio.
Highlights
- Choose a direct public IP, a server behind NAT or a cloud public-IP mapping, or a private network/VPN layout.
- Select the local voice address from the server's active network interfaces.
- Configure public SIP and audio addresses, including a separate public address for audio when needed.
- Review existing values, replacements, and conflicting definitions before applying changes.
- Save settings for the current server while preserving definitions assigned to other servers.
- Keep saved settings if XML synchronization fails, with guidance to correct the problem and retry.
Saving synchronizes the current server's XML. Restart affected SIP profiles during a maintenance window, then test calls; saving does not restart profiles or configure operating-system networking, NAT, or firewall rules. On redundant installations, open each server directly and configure both nodes. The review identifies shared address rows that will become specific to one server or be disabled.
VTech NG-Series Hotel Phone Provisioning
Add native provisioning for supported VTech NG-Series SIP hotel phones through the vtech/NG-Series device template.
Highlights
- Configure one SIP account with primary and backup outbound proxies and UDP, TCP, or TLS transport.
- Download configuration over authenticated HTTPS using a common provisioning URL with the phone's MAC-address placeholder.
- Assign supported speed-dial buttons through Device Key Templates or individual Function Keys, including Service and Emergency buttons on supported cordless models.
- Clear old speed-dial assignments when keys are removed, left blank, or set to N/A.
- Configure voicemail notification, time synchronization, and optional VLAN, time-zone, and administrator-password settings.
- Refresh configuration at startup and when sending Sync from FS PBX.
Supported models are NG-S3111, NG-S3112, NG-S3211, NG-S3211W, NG-S3212, NG-S3311, NG-S3411, NG-S3411W, and NG-S3412. Function-key provisioning supports Speed Dial only; NG-S3111 handset speed dials use a separate configuration and are not changed by this template. Firmware updates remain separate from provisioning.
Sangoma EXP100 Expansion Keys
Configure EXP100 expansion modules on Sangoma S500 and S700 phones from the device's Expansion Keys or an assigned Device Key Template.
Highlights
- Map up to six expansion modules with 40 key positions per module.
- Configure Line, Speed Dial, BLF, and Park keys with their labels and assigned SIP accounts.
- Clear unused positions so removed assignments do not remain on the expansion module.
- Switch the phone's PC Ethernet port to expansion mode when usable expansion keys are configured, and restore normal PC bridging when all usable expansion keys are removed.
Expansion mode changes the role of the PC Ethernet port. Follow the EXP100 cabling and power requirements before applying the configuration. Existing custom provisioning templates need the corresponding changes added manually.
Shared Application Key During Standby Setup
Fresh high-availability standby setup now synchronizes the application encryption key so both servers can read the same saved credentials and integration settings after failover.
Highlights
- Check the application-key configuration on both servers before changing PostgreSQL configuration.
- Transfer the primary server's key to the standby over SSH as part of the confirmed standby setup.
- Back up the standby's environment file and preserve its other settings, including database passwords.
- Verify the shared key and restart the standby's configured Supervisor services before resetting its database or copying data.
- Stop setup with a clear error if key validation, synchronization, verification, or a service restart fails.
This applies to creating or replacing a standby with the replication setup script. That workflow replaces the standby database and restarts its configured services; use a new or disposable standby with no application traffic or running jobs. A normal application update does not change the keys on an existing pair.
Improvements and fixes
- Added Sync to the Devices page's Bulk Actions menu, using the existing paced synchronization process for selected registered devices.
- Fixed the API-token creation dialog retaining the previously generated token when reopened.
- Reorganized the getting-started guides and added First Login and Your First Account, covering administrator credentials, account creation, and regional preferences.
- Added Voicemail Basics with mailbox setup, greetings, message retrieval, email notifications, and troubleshooting; linked it from the extension and voicemail email guides.
- Expanded installation guidance for web URL and session settings, trusted HTTPS certificates, initial login, and scheduled-job owner selection on redundant servers.
- Added network setup guidance for NAT, multiple interfaces, server-specific addresses, startup readiness, and checking SIP profiles and real calls.
- Added a Voxutel trunk guide covering IP authentication, provider IPs, caller ID, routing, and call testing.
- Added a VTech provisioning guide, documented Sangoma EXP100 setup, and linked the phone provisioning video from the Devices and provisioning guides.
- Updated the high-availability guides to explain shared application keys and standby setup verification.