Skip to main content

v2.1.1

· 2 min read

View this release on GitHub

What's new​

Automatic Inbound Number Selection​

FS PBX 2.1.1 improves inbound routing when different trunk providers send the called number in different SIP headers.

Highlights

  • Automatically use the Request-URI number when it matches a configured inbound phone number.
  • Fall back to the To-header number when the Request-URI does not match a configured number.
  • Support both single and multiple dialplan modes while respecting enabled accounts, routes, and server assignments.
  • Replace the manual Destination setting with automatic selection for newly generated phone-number routes.

Once a matching number is selected, routing stays with that number. Internal transfers continue using their called destination.

More Reliable Application Updates​

Application updates now handle optional integrations and background services more gracefully.

Highlights

  • Restart only the requested Supervisor processes that are currently running.
  • Preserve stopped services, including stopped members of a process group.
  • Continue the update with a warning if a background service cannot be restarted.
  • Allow updates from older versions to continue when the optional Ringotel DND repair encounters an account or API failure.

Improvements and fixes​

  • Fixed removal of stale Yealink RPS server assignments when the server has already been deleted from Yealink's cloud.
  • Improved inbound-route cache invalidation so adding, changing, or removing a phone number refreshes previously cached destination matches and misses.
  • Fixed database-connection cleanup when inbound dialplan XML is served from cache.