RyanDaviesNZ Tech Blog

It’s always nice when you can set up  new system and have to do as little as possible to get to your end goal. In the case of installing Hass.io (Managed Home Assistant) on Manjaro, this was incredibly easy.

Luckily, Hass.io only depends on a few packages being installed on the host, as everything Home Assistant runs in docker from there

These dependencies are:

Curl

Bash

Docker

jq

Avahi

dbus

Network Manager

SystemD

As long as you have the above dependencies installed and docker is running, Installing Hass.io is a breeze, You just run:

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s

and wait. Thats it!

Because installing dependencies manually is for amateurs, I have created an AUR package here.

This package should work on Manjaro and Arch based systems and you can install by using AUR tools such as yaourt or pacaur

After being a loyal CentOS follower for several years now, I made the decision to update my systems to a more lean and up to date distribution. Enter Arch Linux. I have been slowly migrating my systems across depending on the machine's function (And how critical it is to the operation of my network).

(V) = Virtual Machine (P) = Physical Machine Machines Migrated:

Netboot (V)- The system for holding all the PXE images and auto-provisioning new virtual or bare metal machines.

Q (V) - My Media management server, with Sickbeard, Couchpotato, Transmission, Headphones and SabNZBd

USS-Enterprise (P) - My Hypervisor. Which all Virtual Machines run on.

USS-Stargazer (P) - This is my laptop for everyday use

USS-Pegasus (P) - This is my gaming rig.

Machines left to migrate:

Core (V) - LDAP, Squid Cache and DHCP server

Data (V) - Web and Rails server

Fusion (V) - FreeSWITCH and FusionPBX (VoIP)

VCS (V) - Version Control (Git) server

Worf (V) - DNS and TheForeman (Management)

Yar (V) - MySQL Server

And the topic of todays entry. FusionPBX and FreeSWITCH on Arch, Replacing Fusion So I started off the install much like I would have if I had been installing on CentOS (See my previous guide) and was surprised to find it was relatively easy. FreeSWITCH is more up to date than the CentOS packages and runs just as well. I'll put up an Arch guide in the near future, for now here is a snapshot taken from FusionPBX on Arch:

Hi Brian,I do from time to time, You can usually find me as ProGEEK on Freenode

This is a basic guide to install FreeSWITCH and FusionPBX on CentOS 6.5

This guide assumes you are running the 64-bit version of CentOS and has been written for a fresh installation, adapt to your needs.

No configuration of FreeSWITCH is performed other than that is required for FusionPBX and FreeSWITCH to work together.

This guide installs FreeSWITCH and its dependencies, FusionPBX, NGINX, PHP-FPM and MySQL

FreeSWITCH and FusionPBX Guide

So, about a year ago I ditched Asterisk in favour of FreeSWITCH, set it up and never really did anything with it.

I put this down to the frontend I had on FreeSWITCH, I was using Bluebox, which was both confusing to use, and endless problems.

About a month ago I switched to FusionPBX, and I must say, SO much ease setting things up. I recently set up a Linksys SPA3000, which has an FXS port and an FXO port. I was keen to get a PSTN to VOIP gateway set up.

Following an asterisk tutorial for setting up the SPA3K, and adapting for FreeSWITCH, I was able to get this up and running in about 10 minutes and working well.

So recently I was plagued with a frustrating issue where the system clock of a virtual machine would only ever be correct after syncing with NTP, After a reboot the system would go back to being 12 hours behind, regardless of the UTC setting, Here is how I fixed it.

Note: All machines in this post are running CentOS 6.4

First step was to check UTC was actually set, which required UTC=true to be present in /etc/sysconfig/clock

Now, after much googling, the /etc/adjtime file can cause all sorts of havoc if incorrectly set up.

So we delete it and regenerate it.

rm -f /etc/adjtime ; hwclock --systohc --utc -D

What this command does is deletes the adjtime file, then sets the hardware clock to the system clock, adjusting for UTC, this hwclock command will also regenerate the adjtime file correctly.

After which we reboot, sync with NTP to make sure our time is spot on, and that's that!

x2x is a great program for users who have two computers and monitors, or a monitor and a laptop, and want to share mouse and keyboard between the two monitors. You have to be using X on both machines. In my case, I have Ubuntu Precise Pangolin (12.04 LTS) on both. To install X2X, on Workstation 1 do:

sudo apt-get install x2x

And on workstation 2 I do:

sudo apt-get install x2x openssh-server

Now, on workstation 1, just do the following in the command line.

ssh -XC user@workstation2  x2x -east -to :0

Make sure to replace "workstation2" with the name of your computer, or the IP. You can make a shortcut for this by adding that command to your shortcut.