I came here for the exact same reason. My v13 servers don’t allow this. My 2 v14 servers do. This is a problem. The admin login is open to the world. I used to have to whitelist IP’s to get the login screen and now any IP can see it.
↧
Firewall Not working?
↧
Freepbx in HyperV
Found this today - I will copy it here and also make a post - had some VM’s throwing TONS of these errors:
kernel: Clocksource tsc unstable (delta = 131717343 ns). Enable clocksource failover by adding clocksource_failover kernel parameter.
Come to find out it’s a bug (CentOS or Microsoft I don’t know…) that occurs when the VM is Live-Migrated - it actually hung a machine this morning which is why I found out about it - went and looked through all my running machines and it was occurring on 7 of them - the clock “De-Stabilizes” during the migration.
Simple solution - add this to /boot/grub/grub.conf and reboot when you can:
clocksource_failover=acpi_pm
Put it at the end of the kernel line as an option and then reboot.
Here is the original article:
↧
↧
FreePBX VM's running under Hyper-V - Setting Change you need to make
Had a machine stop processing calls this morning - here is what I found:
Had some VM’s throwing TONS of these errors:
kernel: Clocksource tsc unstable (delta = 131717343 ns). Enable clocksource failover by adding clocksource_failover kernel parameter.
Come to find out it’s a bug (CentOS or Microsoft I don’t know…) that occurs when the VM is Live-Migrated - it actually hung a machine this morning which is why I found out about it - went and looked through all my running machines and it was occurring on 7 of them - the clock “De-Stabilizes” during the migration.
Simple solution - add this to /boot/grub/grub.conf and reboot when you can:
clocksource_failover=acpi_pm
Put it at the end of the kernel line as an option and then reboot.
Here is the original article:
↧
AT&T/Cricket Blocking Traffic
Thank you all for the helpful suggestions. I will do some more investigation and report back. Our FreePBX server is remotely hosted; not on-site.
↧
No such context 'macro-outisbusy' for macro 'outisbusy'. Was called by 100@from-internal
DTMF[2463][C-0000000e]: channel.c:4030 __ast_read: DTMF begin ‘1’ received on SIP/2000-0000000c
[2018-04-04 12:39:21] DTMF[2463][C-0000000e]: channel.c:4034 __ast_read: DTMF begin ignored ‘1’ on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:3944 __ast_read: DTMF end ‘1’ received on SIP/2000-0000000c, duration 120 ms
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4014 __ast_read: DTMF end passthrough ‘1’ on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4030 __ast_read: DTMF begin ‘2’ received on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4034 __ast_read: DTMF begin ignored ‘2’ on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:3944 __ast_read: DTMF end ‘2’ received on SIP/2000-0000000c, duration 120 ms
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4014 __ast_read: DTMF end passthrough ‘2’ on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4030 __ast_read: DTMF begin ‘3’ received on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4034 __ast_read: DTMF begin ignored ‘3’ on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:3944 __ast_read: DTMF end ‘3’ received on SIP/2000-0000000c, duration 120 ms
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4014 __ast_read: DTMF end passthrough ‘3’ on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4030 __ast_read: DTMF begin ‘#’ received on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4034 __ast_read: DTMF begin ignored ‘#’ on SIP/2000-0000000c
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:3944 __ast_read: DTMF end ‘#’ received on SIP/2000-0000000c, duration 120 ms
[2018-04-04 12:39:22] DTMF[2463][C-0000000e]: channel.c:4014 __ast_read: DTMF end passthrough ‘#’ on SIP/2000-0000000c
[2018-04-04 12:39:23] WARNING[460]: func_cdr.c:377 cdr_write_callback: CDR requires a value (CDR(variable)=value)
)[2018-04-04 12:39:23] WARNING[460]: func_cdr.c:377 cdr_write_callback: CDR requires a value (CDR(variable)=value)
)[2018-04-04 12:39:24] NOTICE[488][C-0000000e]: chan_sip.c:23808 handle_response_invite: Failed to authenticate on INVITE to ‘sip:2000@172.16.16.114;tag=as21c38503’
[2018-04-04 12:39:24] NOTICE[488][C-0000000e]: chan_sip.c:23808 handle_response_invite: Failed to authenticate on INVITE to ‘sip:2000@172.16.16.114;tag=as21c38503’
[2018-04-04 12:39:24] WARNING[2463][C-0000000e]: app_macro.c:310 _macro_exec: No such context ‘macro-outisbusy’ for macro ‘outisbusy’. Was called by 7042566755@from-internal
[2018-04-04 12:39:24] WARNING[2463][C-0000000e]: app_macro.c:310 _macro_exec: No such context ‘macro-outisbusy’ for macro ‘outisbusy’. Was called by 7042566755@from-internal
↧
↧
Firewall Not working?
So your PBX server is basically directly connected to the internet as apposed to using a separate dedicated router/firewall between the server/network and the internet?
↧
After Yesterday's Module Updates, 4-2-18, Fail2ban Should Always be Running
Thanks Lorne for the one answer to do. That fixed it. I did find that one but did not use that answer because of the HA (High Availability) system mentioned.
Please forgive me for being a chicken sometimes when multiple answers to a problem might be provided.
I have asked this question before when things suddenly go awry and nary an answer but…
why did this happen?
John
↧
Firewall Not working?
You ever used cyberlynk? Freepbx officially supported hosted servers. No firewall or router between. Never had an issue until recently. Something changed and it is not good.
↧
No such context 'macro-outisbusy' for macro 'outisbusy'. Was called by 100@from-internal
That is not the complete log of the call, but anyway, this is probably why your call is failing:
↧
↧
FreePBX VM's running under Hyper-V - Setting Change you need to make
Also, if you update the kernel (yum) you need to re-apply this fix.
↧
No such context 'macro-outisbusy' for macro 'outisbusy'. Was called by 100@from-internal
what could be the reason ? username, secret is given correctly still it is saying ‘Failed to authenticate’
↧
No such context 'macro-outisbusy' for macro 'outisbusy'. Was called by 100@from-internal
Re-check the username and password. If you are using the default auto-generated password, it can sometimes be too large, set it to a shorter password.
↧
Portmapper servers
Received a strange e-mail from my cloud hosting provider (Vultr) today:
Dear Customer,
Recent network security audits have detected some issues on your instances. Please review the following reports and help us to ensure the security of our network:
== Portmapper servers ==
Portmapper is a service usually used with NFS. When this is not properly firewalled, it can be abused to conduct DDOS attacks. We recommend that all portmapper services be behind a firewall, and restricted to only IPs that need to contact them.
For Linux machines, please add firewall rules to block port 111 on both UDP and TCP:
iptables -I INPUT 1 -m tcp -p tcp --dport 111 -j DROP
iptables -I INPUT 1 -m udp -p udp --dport 111 -j DROP
Please see https://blog.cloudflare.com/reflections-on-reflections/ for more information on reflection attacks.
The following IPs have been detected running open portmapper servers:
XXXX - at 2018-04-03 10:23:03
Is this something used by FreePBX? What are your recommendations to correct the issue without breaking anything?
↧
↧
AT&T/Cricket Blocking Traffic
Very often using Zoipers iax2 connection will get through where your provider is blocking sip.
↧
AT&T/Cricket Blocking Traffic
Verizon ACTIVELY blocks SIP on both their wireless HotSpots and the phones using tethering - look deep enough into your agreement and you will find where they say they are entitled to block competing services.
VPN can sometimes get you around it - or like Dicko says - IAX2 is usually not recognized.
↧
Multiple outbound CID outbound routes
I vote for 1 seeing setting up the accounts would have to be done on all phones and setting up the outbound routes only once.
↧
VM Stuck - Updating all FreePBX modules. This can take 5-10 minutes
Is this a xen based VM? The latest kernels (cents and freepbx both) do not work with on a xwn vm in pvm mode. You can either run the vm as a phvm, a full hvm or try to find a working kernel (some information on centos bug reports can be found).
After running into this over 6 months ago and I’m currently waiting for the fixes to eventually make it to freepbx.
↧
↧
FreePBX VM's running under Hyper-V - Setting Change you need to make
Ok - Scratch-Load Sangoma-7 is using grub2 - /boot/grub2/grub.cfg
I assume the change goes here:
BEGIN /etc/grub.d/10_linux
menuentry ‘Sangoma Linux (3.10.0-693.21.1.el7.x86_64) 7 (Core)’ --class sangoma --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option ‘gnulinux-3.10.0-693.11.1.el7.x86_64-advanced-d8867ba0-06e8-4c0c-8e81-3a0b81d48bb0’ {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root=‘hd0,msdos1’
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint=‘hd0,msdos1’ e52e8132-3284-4c59-975f-4f4000bf4183
else
search --no-floppy --fs-uuid --set=root e52e8132-3284-4c59-975f-4f4000bf4183
fi
linux16 /vmlinuz-3.10.0-693.21.1.el7.x86_64 root=/dev/mapper/SangomaVG-root ro crashkernel=auto rd.lvm.lv=SangomaVG/root rd.lvm.lv=SangomaVG/swaplv1 biosdevname=0 net.ifnames=0 rhgb quiet LANG=en_US.UTF-8 clocksource_failover=acpi_pm
initrd16 /initramfs-3.10.0-693.21.1.el7.x86_64.img
}
↧
Portmapper servers
I put in the suggested iptables updates and had no issues.
↧
Porting 2.11 version 'Wake Up Calls" module to V14
Thank you. I thought it was was a FreePBX thing.
↧