Search results

Possibly none.. Hard to tell. When a machine is fully firewalled fail2ban is useless... and monitoring it is useless. When fully firewalled the only thing you want to monitor... is iptables and the in memory ruleset... Why not start by posting your entire iptables file after you sanitize it to...

Actually that's not only an iptables manager it also advertise this: So this has full potential to mess with fail2ban because some functions will overlap. And csf is probably not fail2ban aware while managing iptables... And fail2ban and lfd could both be monitoring the same log files... And...

No.

Did you call Digium to request support?

That's not even spam, it's link building for SEO. It's for wholesalers with big minimums and it's an exchange, not a provider. I don't think wholesalers visit PIAF forums to research 2010 posts to shop for DID exchanges... Ward, you have a soft spot, that's for sure! ;)

To all the NSA lovers out there, they are certainly not doing that anymore or they wouldn't be in business still but I remember DO had an issue in the past were they decided that it was creating too much load on their system to scrub the block device in between customers... It was an additional...

Rückportierung

TRUNK: IAX2/voipms DISABLED - falling through to next trunk Means just that, this trunk has a check in the "Disable trunk" checkbox under the trunk settings page in FreePBX. Seeing that it works with SIP I will elaborate that your new SIP trunk doesn't have a checkmark in the "disable trunk"...

Mostly this: And below it for example and all..

That's not right, no mention of setting up: "Dial Patterns that will use this Route" Which is your problem right now, just like it was in the previous log dump. No outbound routes match the number your dialing so it can't be completed as dialed. Why? because you're configuring the outbound route...

What did I miss :) Can you explain why these instructions should still be followed if the official PIAF install package is now a script that is to be run on any existing CentOS install? I'm not sure when those special instructions would still be needed? But even Ward didn't point that out so...

Your latest log dump is the following: You have no outbound route catching outgoing call to: 204xxxxxxx 1204xxxxxxx It's not even trying a trunk because it's not catched by any outbound route and thus never bridged with a trunk. The system is literally saying "cannot-complete-as-dialed.ulaw"...

my thinking is you should keep trying to make it work standalone... moreso if your monitoring other servers. Doesn't make sense to host Zabbix on the PBX as anyway it will not be on the other servers... So you still have to make Zabbix work when it's not on the same server it's monitoring...

Based on what you said I cant help to figure out what was wrong when the server was on another machine. There is no reason for it not to work as this is not special the situation here... Zabbix is always used on another server usually. I though you could be running into this...

exactly which version of asterisk are you running?

Which version of asterisk are you running?

http://pbxinaflash.com/community/index.php?threads/missing-kennonsoft-menu-after-upgrade.14720/ http://pbxinaflash.com/community/index.php?threads/missing-kennonsoft-menu-after-upgrade.14720/#post-94574

The source port would not matter for iptables even if it was not NAT. iptables filter traffic based on destination port toward the server, not the source port where it's coming from phone. The OP provided no information to indicate his Asterisk is listening on another port beside 5060. And he...

You feel attacked for nothing, you should have started a thread that's all I'm saying. It belongs in a new thread specific to your specific question, that's all. You're generally discussing your specific issue, not generally discussing good routers for PIAF. Check the answers/questions you...

So, again, lost... :confused: