We are aiming to make backup/restore be able to do between version restores starting with FreePBX 15+. As the first step is making each and every FreePBX module be responsible for its own information versus how it’s done today. However, if you have something that is earlier, you can always use our home2.freepbx.org tool which is available right now.
To clarify one thing here. With Asterisk’s ARI and how it functions and is written this is possible, however you’d have to write an “SLA” ARI application (in whatever language you want) that could perform those actions.
To add to the chorus for multiple phones on a single extension, I often travel and would like to carry my extension with me, either a physical phone or soft phone on my pc. Now I create a separate extension, add to ring group, etc. This can be made to work but It would require less configuration overhead to be able to have a single extension. Not a critical for me but nice to have.
PJSIP allows you to do this. Or you can set a follow me on your primary extension.
Port FreePBX distro over to Debian or Ubuntu. I’m tired of the crappy and confusing networking stack in CentOS and its delayed hardware support. Not to mention FreePBX devs have complained about CentOS failing to provide an easy upgrade path recently from 6 to 7 (FreePBX 14 Release Candidate).
check out direct send for o365 email - it works today and requires no account - treat the pbx like it were an mfd
the main caveat with direct send is that it can only email to users in the o365 domain
backup to azure would be nice as well
im surprised no one has brought up management of UCP - no on struggles with sally left and susie now sits there ?
Last I knew, we were being discouraged from using PJSIP. Has that changed and when? Also routing calls and multiple devices are not quite the same from a callers point of view.
maybe an https redirect that can be enabled with an override from fwconsole just in case ?
uses can be pointed to an fqdn without worry of the protocol… anything that hits 80 is redirected to 443 and secure
nice - id like to see some duplicate features as well as templates … lets say a new CSR needs to be added and they may be a queue or ring group member with some other unique features - a CSR template to apply all the correct settings would be awesome
- 1 for TTS integration with something
wow - more than one awesome feature request… we are hiring you know ?
Where ever possible, it would be useful to have test options not unlike the feature in CID Superfecta. So as an example, Sys Admin/Email Settings could have a button to test. Also, call routing settings modules could allow entry of numbers and display the resulting number format and route, and so on.
Some community members not associated with Sangoma discourage use but Sangoma does not anymore.
Zulu 3 uses pjsip moving forward. That’s how committed we are to it.
2FA for admin access.
Speech recognition. Just tell asterisk who you want to call.
Poly Voice to Text message email integration.
Maybe Watson too. But I don’t like the way Watson types out a phone number. It spells it out. Not good for a cell phone redial.
Watson has meta options. I have played with a few of the api’s it is really cool stuff
This would be wild difficult to setup, but I would love to see a visual display of a dial plan.
–> Trunk In --> Call Flow (with audio bindings) --> Time Conditions --> IVR (with all breakouts) --> Ring Groups / Queues (with all failovers).
I keep a manual flow chart for each customer. Would love to see this as a dashboard module to see exactly how a call would flow. Visual debug tool.