Please contact support on this. The forums are mainly for FreePBX and this is a pretty big issue if your using our appliances with PBXact and a yum update has broken the box somot doesnt boot.
PBXact OS bug
Commercial Endpoint Manager - Latest Version is Old
OK, I’ve created a feature request and will see what happens.
https://issues.freepbx.org/browse/FREEPBX-17618
Thanks again!
Call Transfer Fraud
I think that even after removing the “T” the system is still at risk if follow-me is configured.
We have seen that the follow me functionality views the external caller as an internal caller for the follow me leg of the call. I think this means that if an internal extension is set to follow me to a mobile that the external caller can transfer out (*2 or ##) of the call to the mobile and then dial out appearing to be an internal caller (which is allowed via the “t” in the dial plan.
regards Jason
"No matching endpoint found" on some extensions, but not all
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
Freepbx on Raspberry Pi for 15 extensions and 5 SIP trunks
Rule of thumb? I would say should be good for a couple hundred extensions or more. and the cpu for plenty of trans-coding. Asterisk is remarkably low overhead, 1G of ram is more than enough, figure about 4 or 5 G for the ‘system’ you are left with the rest for recordings.
I have vultr instances of 1G 1CPU that handily do 100 extensions with heavy duty faxing no problem.
Call Transfer Fraud
You are absolutely correct here. In-call transfers are rarely needed, SIP phones/Asterisk can generally handle transfers without such exposure.
Blacklist not working for direct to extension DIDs
Did you miss
– Executing [6400@from-digital:1] NoOp(“DAHDI/i1/2813622398-6e2”, “Catch-All DID Match - Found 6400 - You probably want a DID for this.”) in new stack
Allowing anonymous will bypass the blacklist.
Blacklist not working for direct to extension DIDs
I don’t allow anonymous calls. I have a default inbound route configured which all non-defined inbound routes hit. Calls to that inbound route get blacklisted properly.
The 6464 extension, which has an inbound route for the DID defined, receives calls that are on the blacklist.
However maybe I have the inbound route misconfigured, or the DID is also configured on the extension and it is routing based on that and not the inbound route.
I’ll check on that in the morning.
PBXact OS bug
Tony - I submitted a bug report and Andrew Negey canceled it and told me to go to the forums. That is why I posted it here.
Blacklist not working for direct to extension DIDs
But apparently not 6400
PBXact OS bug
Where did I say to open a bug report. Andrew works on the Dev team and issues.freepbx.org is for FreePBX. I said to open a support ticket, as this is a support issue and/or hardware issue it would appear.
PBXact OS bug
Support ticket has been opened. Ticket #806235
Commercial Endpoint Manager - Latest Version is Old
Polycom is not a certified partner so things like this happen when we do not have items to do for Certified partner phones so you will rarely see Polycom updates of any kind from us as they are basically frozen in time unless a major bug gets introduced in EPM to keep from even doing basic provisioning. Outlined here https://wiki.freepbx.org/display/FPG/EPM-Supported+Devices
PBXact OS bug
Hi David,
I went and looked at the bug report and Andrew was pointing out that the issue seems like a support request. While I understand the confusion in the 3 areas users may be able to get support as listed in our standard response, anytime it’s PBXact or Commercial module related, opening a ticket at support.sangoma.com is the best route. This ensures that we can better assist you by having our support team take a look. Sorry for the confusion and we will work on better communication in the future.
PBXact OS bug
Thanks. It is confusing where to go sometimes. I will get the hang of it.
PBXact OS bug
David,
No worries, we are constantly listening to feedback to try to offer the best experience possible. One small example is based on yours and other community members feedback we have already made changes to our standard responses which I hope will make it easier to understand moving forward. Again my apologies about the confusion.
Restore from "Upload File" doesn't work for most files
I saved a backup on one FreePBX (14.0.3.6) and copy the backup file to a windows server.
On another identical FreeBPX I try to Restore the file using the Import tab: “Upload File” Browse. FreePBX says it uploads the file (percentage counts up to 100%) and then… nothing. It doesn’t give me an option to restore and there are no error messages in any log that I can find (asterisk or freepbx.)
This does work for a config only backup, but not for a full backup.
If I copy the full backup to the new machines backup directory, and then use the Browse tab under Restore, everything works fine.
I spent an hour or more on this. Hopefully others won’t waste their time like I did.
If Import doesn’t actually work, maybe it should be disabled or at least an error message warning that it only sometimes works. Also, some sort of error message when it fails would be helpful.
PBXact missing trunks in menu
Add in:
fwconsole ma install oembranding
And this will fix the broken interface.
Thanks Lorne!
Commercial Endpoint Manager - Latest Version is Old
I see, that’s understandable since testing each firmware update will take time and money. Guess I’ll have to tackle this by custom firmware upload then.
Thanks for all of the info!
Fail2ban maintain list of banned IP addresses after restart
I am trying to configure fail2ban to maintain its list of banned IP addresses after it has been restarted. I have tried this method, but its not working.
For some reason the “persistent.bans” file is not created, so the IPs are not banned again on restart. It’s like “iptables-multiport.conf” is ignored.
Has anyone been successful in configuring fail2ban to maintain its list of banned IP addresses after it has been restarted?