Search results

Probably not, if anything you will need to configure it manually.

fs_cli log should show you exactly what is going on.

that would be something along the lines of: systemctl stop event_guard systemctl disable event_guard I have to say though, I need to read the code more to see what it is doing but after doing a: systemctl restart event_guard The CPU usage dropped to almost nothing, IP tables is getting...

A simple restart of the service has brought it down to almost nothing. I still need to do some testing and fine out why there are no ip tables entries though.

Is anyone using FusionPBX 5 with this enabled? I am seeing it consume 100% CPU and it looks like it should be blocking in IP tables but IP tables is clean, the two chains it creates appear to have no entries blocking.

You should just need to put the effective_caller_id_number as 44123456789. the domain will be tagged on automatically. Who is the provider by the way?

Yes, 99.999% of time the hackers will send to xxx@ipaddress

The implication there from the chain is that the invite/reg is going to xxx@ipaddress. It should be xxx@domain.com

Also, unless things have changed that acl name should be domains that you are editing

@francois Could you perhaps detail this solution a little more, I'm sure many people would find this very useful.

Mark has now open sourced that app, take a look at: https://github.com/fusionpbx/fusionpbx-app-sip_trunks

Why can you not install the module?

did you flush cache and reload acl?

There was something years ago but I don't know how successful it was, search the forums.

None of those ACL settings should be there, they are all wrong, I assume you just guessed they should be there. Your carriers should be added to the domains ACL and all that you need to populate for each is the CIDR, nothing else.

Sorry, its completely custom for my needs and quite complex

I do not know if this was fixed in later versions of fusionpbx but, in the past, if you created a loop like this and there were no extensions registered this would cause the PBX to just crash as it would just go into an instant infinite loop.

Just for your info, my setup has nothing whatsoever to do with fusionpbx. Its just a lean, standalone freeswitch. I figured that way I can connect it to anything, its just a teams appliance,. Glad you are making progress by the way :)

I did a bit more digging yesterday. If I were you I would stick with the sipp for the options pings. What we found was that over time, using gateways, they all slowly died, this was due to freeswitch marking them bad after a number of failures. The sipp will NEVER mark them bad and just...

Oh, as you can also see, I was using a bogus SONUS USer-Agent, that was not necessary though