root@raspberrypi:~ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:b6:1b:48 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.141/24 brd 192.168.1.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::45fb:bac0:178a:1c05/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:e3:4e:1d brd ff:ff:ff:ff:ff:ff
inet 172.20.20.20/24 brd 172.20.20.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::ba27:ebff:fee3:4e1d/64 scope link
valid_lft forever preferred_lft forever
WARNING: Always run Incredible PBX VM behind a secure hardware-based firewall.
root@raspberrypi:~ $ ip route
default via 172.20.20.1 dev wlan0
default via 192.168.1.1 dev eth0 metric 202
default via 172.20.20.1 dev wlan0 metric 303
172.20.20.0/24 dev wlan0 proto kernel scope link src 172.20.20.20 metric 303
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.141 metric 202
WARNING: Always run Incredible PBX VM behind a secure hardware-based firewall.
I had the same problem a few weeks back, had me scratching my head and chasing firewall rules... Just turn down the wlan0 interface with "ifconfig wlan0 down" to test it out and then everything should work fine - it did for me.
If that works change it from auto to manual in /etc/network/interfaces - assuming you don't need it.
root@pi3:~# ip route
default via 192.168.1.254 dev eth0 metric 202
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.64 metric 202
root@pi3:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.254 0.0.0.0 UG 202 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 202 0 0 eth0
I had the same problem a few weeks back, had me scratching my head and chasing firewall rules... Just turn down the wlan0 interface with "ifconfig wlan0 down" to test it out and then everything should work fine - it did for me.
If that works change it from auto to manual in /etc/network/interfaces - assuming you don't need it.
FWIW, you don't need a monitor at all if you know the secret handshake.
With a USB keyboard and network cable attached, boot the RasPi3. Wait one minute to be sure the boot has completed and there's a login prompt. Then type pi <ENTER>, wait 5 seconds, raspberry <enter>, wait 15 seconds, press <enter>, wait 30 seconds, press <enter> again, wait 15 seconds, press <tab>, press <enter>, wait 15 seconds, press <enter>, press <tab><tab><enter><enter>. Server will reboot and you can login from SSH as root:password within 30 seconds.
I have just installed the latest Incredible for Rasbian Jessie (15 Sept) and I have a question about disabling some components.
1. I would like to disable Chan-SCCP as I don't have any Cisco phones.
2. As I am outside the USA I would also like to disable GV OAUTH.
Can they be turned off in the Incredible GUI?
I managed to disable chan_sccp yesterday and while testing I found that the pbxstatus still showed the module as UP.Not in the GUI, but you can disable them in /etc/asterisk/modules.conf.
Link up your team and customers Phone System Live Chat Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.