Feature Request / Update : Call Notifications :
Notifications for everything. - Similar to the call recording above. Possibly a 2 tier option, or multiple recipients can be entered for Inbound, outbound and even on extensions.
Right now, (ver 17) There is a “Notifications” tab in OUTBOUND Routes (only) where you can get an email sent to someone to notify them a call was made. This is VERY Useful in 911 calls where you may want to send management or security, etc, a notification that 911 was called.
The problem, it seems this option is only available on outbound calls, and only if a pattern is matched or the call is successful.
I want to see these notifications on Inbound Routes and even per extension too. Apparently you can rig it with code to get it to do what you want, but that is a “tinkering” process. There is the voice mail notifications, but that only works if you have voice mail turned on. There are a number of reasons you would want notified if a call comes in and not need voice mail.
you are tracking a DiD for any activity.
Maybe you are considering dropping that DiD or tracking it for marketing purposes and want to see how many calls it gets, even hang ups. Several of our clients are consolidating more than a dozen external DiD numbers from their old pots phone systems down to only 2 or 3 DiD routes on the new system. They want to see if any of those old numbers are really being used and don’t ever otherwise need to have to log into the system to pull reports or research data.
As a failover alert option.
We have a system set up as a failover system. For all of our clients with their own onsite system, if for any reason their system is unreachable (power outage or internet out - happens a LOT here in Hawaii) All of their inbound calls are redirected to our failover system. Some we have extensions set up for their backup or emergency cell phones, some just want a message left in voice mail. In any instanace, if a call comes into our failover system, I want to get an email alerted to us and as well I want an alert sent to a staff person at the clients site to noitify them. Often it might be their first noitification that power or internet is out (tehy can get the email on their cell phones)
I can think of plenty of other uses for this as well.
Most call centres handle types of calls parts of which must never be recorded. You may need to educate your clients on this. The Payment Card Industry Data Security Standard,say that you must never record (or even make a not of on paper), the CVV security code on payment cards (e.g. credit and debit cards). It looks like the way some handle this is to transfer the call to a special extension, that is recorded, and is only used to capture card details, but that means at least one extension must never be recorded.
Maybe I should have chosen a better term than “Call Centers” But we do have clients that process a lot of inbound calls.
Yes, None of our clients are processing credit cards or payments of any type. We are working with non profits that are handling state and government contracts for things like prisoner re-entry, early release, court assigned living, etc. there is a mandate to record all calls for these particular clients here. This may not be the same for everyone everywhere, and I understand that. That is why I was also saying about having it be able to have exceptions to the “everything” rule too, in case they wnat to deal with things that are not recorded. The point of this thread is to make requests for version 18, yes ? That is what I am doing. Wanting to simplify things that otherwise seem to be some type of manual process.
Sorry, but that sounds rather dismissive. Like, we are just going to ignore the suggestion ?
The point of this thread is to make requests for version 18, yes ? That is what I am doing. Wanting to simplify things that otherwise seem to be some type of manual process.
Sorry, I was not aware there are separate community modules available that are not part of the standard FreePBX distributions or commercial modules to buy from Sangoma. I now see the “open source modules” category after I did a google search for it. I did not see it previously here in the forums menu. I will take a look there.
Sorry, I have never heard the term “Uptake” before.What does that mean in your context ?
No, you have misread my tone. I was suggesting that some of us would be happy to discuss what you’re trying to achieve further. You won’t achieve much of a conversation about it in this particular thread. It just wouldn’t happen; that’s not how the forum works.
The suggestion wasn’t ignored either. I gave you my opinion and also offered some advice.
By “uptake”, I mean people installing and using the module. Evidence of real-world use, along with feedback from those users, is what helps it to be considered by Sangoma for inclusion in 18.
All of these have federal and state requirements that must be met and a straight vanilla install of FreePBX isn’t going to cut it. You’re not asking for a feature to be added you’re asking for something to handle your legal compliance.
The biggest one here would be the re-entry programs. Those are highly regulated and since pretty much 95% of the re-entry programs involve substance abuse treatment any calls in regards to those things even making an appointment have to follow HIPPA requirements. Then of course you have the fact that some of this will touch CJIS (Criminal Justice Information System). Calls between the person and their PO or any supervised person needed to be handled differently.
Between the HIPPA and CJIS requirements you need to adjust these systems in a much more in depth ways. Both HIPPA and CJIS will require that the call recordings and any other data must be encrypted at REST and in TRANSIT the real kick here is that CJIS is more strict than HIPPA in some cases.
CJIS requires AES 256-bit encryption for all the data at rest and in transit. MFA for access. Background checks for those accessing the system, Audit Logs and Incident responses.
Yes it’s the same mandate basically anyone operating those type of services for the DOC. There are federal laws that all the states must follow and each state has their own laws on top of that. Again, you are asking for a feature that isn’t a feature but something that solves a compliance issue and even then, a blanket record everything wouldn’t meet your compliance requirement.
In this particular scenario there are way more things outside credit card numbers that can’t be recorded. You can’t record calls between “inmates” and their care providers, you can’t record certain calls between “inmates” and others who are serving in certain roles (POs, etc).
Basically a record all option will not solve what you need to solve.
Sometimes these threads get full of arguing about if a feature should or should not be included, and why someone is wrong for asking for a feature. It feels like it would be wise to have people with complex requests make a separate thread and link to it here, so that it doesn’t clog up this main thread. (Unfortunately there’s no tree system here so we can’t have nested replies.)
I see several complaints about AI written modules. I think the thing is, this allows rapid prototyping, and it’s very possible to have other AIs review the code. I’m doing AI written modules of my own, but I’m doing a lot of guiding, not just “whatever you think is best, Chat”. I think most of the good stuff we see is going to be from people who know what they want but need the assistance of AI to make it happen. If Linus thinks it’s a useful tool, then maybe it is. I’m working on things I wanted to see, and because of that I have a strong guidance on how to make it useful.
What would I like to see? Having to “pay” $0 every year to re-up the PBX MFA module is silly. If System Admin can be 25 years, so can PBX MFA.
Better integration with transactional mail services like Amazon SES, it was a huge hassle to get it working. Transactional mail services are the way to go for the PBX.
For additional models in Endpoint Manager, I would be happy to contribute working configs for phones I have set up in FreePBX. We mostly use Cisco (yes, I realize that lots of posters in the forums here would have comments about that, but I’d like to keep the thread from getting sidetracked) 3PCC phones, which we just lightly modified the Cisco SPA configs for and have to use one of the model entries for SPA for them.
At this point a roadmap would be great. What is being updated, added, removed, changes all that. We are supposed to get a beta in 4-6 weeks and we have no idea on what is actually being done. @penguinpbx you should work on this
There was that little hint about nftables previously in this topic and another one about IPv6 in another topic. Frogman also got a from YT a few posts back.
from YT a few posts back.
Cooling down non-v18 dev issue handling until BETA release