@pbxgeek I also found the modules page blank on a new install.
It would appear that in resources/classes/modules.php, $this->dir is empty, populating it with '/usr/lib/freeswitch/mod' resolved the issue.
I don't know where it pulls that in from, hope that helps a bit.
OK, still a bit scabby but create a file: /etc/fail2ban/jail.d/ignoreip.conf
NOTE: you need each ip address after the first line indented with a space.
Inside it, this kind of thing:
[DEFAULT]
ignoreip = 127.0.0.1/8
215.155.52.118
179.22.139.77
182.63.140.77
182.63.142.77
183.63.141.77...
I know I'm on of the people who pushed for the reinstatement of the wiki at that time, I'm actually suprised that it is still up now. That was long before the documentation was as extensive as it now is. At the time, there was a lot of very relevant information though I wouldn't dream of using...
Awesome Adrian, its come a long way.
Just a quick question: is the rabbitmq a single point of failure? I remember this being an issue with kazoo back in the early days.
So create two routes for the same dialplan with different gateways.
Then for each of those routes, add a condition at the beginning that matches the extensions you want.
The first condition will be something along the lines of sip_from_user ^200$ || ^201$
Well, immediately I see some of the filters are not enabled:
[sip-auth-challenge]
enabled = false <--------------------------------
port = 5060:5091
protocol = all
filter = sip-auth-challenge
logpath = /var/log/freeswitch/freeswitch.log
#logpath = /usr/local/freeswitch/log/freeswitch.log...
Well to be blunt then what is ANI? Where is this set? According to the SIP specs, caller id is either set in in the FROM header or it is set in RPID, p-asserted-id etc. Some proveiders will use the from, some rpid, some pid (p-asserted-id)
I know of no field in SIP for ANI, please enlighten me.
Its basically just experience. If you read through it, what you can actually see is that it is going through the dialplan as defined in the dialplan manager.
No, your outbound routes are likely to break everything, you are saying send anything over three digits, that will likely include ring groups, extensions, etc,etc, etc, Create separate outbound routes to match your emergency numbers etc.
I believe you problem is here: bridge(sofia/gateway/5719458e-8222-4631-b62e-d7c64d5fef69/7000
Why is it trying to use a gateway to send that call? I would guess that you have an outbound route that is catching that.