Archives

The HAAst log file or its parent directory has world write permissions, and newer versions of logrotate do not allow this to rotate. Manually running logrotate shows the results below:

$logrotate -d -v haast
reading config file haast
Handling 1 logs
rotating pattern: /var/log/haast after 1 days (7 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/haast
error: skipping “/var/log/haast” because parent directory has insecure permissions

The solution is to uncomment the line in the /etc/logrotate.d/haast file to allow rotating regardless of permission:

su root root

You are experiencing a network/routing issue somewhere on your network. It could be an ARP table is corrupt somewhere, or a device is simply not routing packets out the interface it should. This type of problem is common with multihoming (this is not a HAAst issue, it’s a network issue).

A complete solution is beyond the scope of this document. In fact, understanding and diagnosing ARP cache and routing problems is complex – don’t expect a simple answer. If you want to ensure that your Asterisk server is sending packets out the right interface on a multihomed system, you can set an iproute policy as follows:

1. edit the /etc/iproute2/rt_tables file and add the following line:

200 haastrt

2. add the following two lines to your asterisk.start.pre file (assuming the device you are dynamically creating is called eth0.haast):

ip rule add dev eth0.haast table haastrt
ip route add default dev eth0.haast table haastrt

3. Reboot your system and retry the ping test mentioned above.

If the problem remains then the most likely cause if your router.

Although unusual, this suggests that your FreePBX AstDB is corrupt or incomplete, and FreePBX is missing database entries needed by the dialplan. This can occur if you have installed a buggy FreePBX update, or FreePBX has crashed, etc.

There are four possible ways to correct the Asterisk database.

1. Restore the node from a backup
2. Request that FreePBX regenerate the Asterisk database using this BASH command (after stopping Asterisk). Note that some versions of FreePBX don’t support this command:
   
   curl https://SERVER/freepbx/admin/config.php?type=setup&display=devices&action=resetall

3. Recreate the Asterisk DB manually.
   • Stop FreePBX
   • Delete the /var/lib/asterisk/astdb.sqlite3
   • Start FreePBX
   • Edit & Submit each user
   • Click apply
4. Stop FreePBX on both peers and copy the file /var/lib/asterisk/astdb.sqlite3 from the working peer to the malfunctioning peer. (Be sure Asterisk is stopped on both systems before trying this).

Once corrected, be sure to resolve the underlying FreePBX/configuration/etc issue. As well, ensure that you have set the Asterisk database to synchronize in HAAst’s configuration file.

Error code 5 reflects a non-descript exit condition and is harmless.

In versions of HAAst prior to 2017 a warning with exit code 2 (in the case of MySQL database/table synchronization) means that differences were found between the source and destination tables but they were successfully synchronized. Other exit codes in this context are 0 (success, no differences), 1 (error condition), and 3 (combination of 1 and 2)

In version of HAAst from Jan 2017 onwards exit code 0 always means success (even if differences were found and then synced successfully).

No action is required; this is a normal exit code and indicates synchronization is working. We have notified the author of the library we use in the hope of a more appropriate exit code.

There is a known bug (in Ubuntu/Debian) relating to constantly changing MAC addresses for bonded interfaces. Further information can be found here: http://blog.widodh.nl/2015/09/ubuntu-and-the-changing-mac-address-withbonding/ or found on the Ubuntu bug tracker as bug 1288196.

The solution is that you must adopt one of the workarounds identified in the above article to avoid problems with HAAst functionality. Telium’s recommendation is to fix the MAC address for the bonded interface as follows (as recommended in the article):

auto bond0
iface bond0 inet manual
hwaddress fe:80:12:04:6d:6f
bond-slaves none
bond-mode 4
bond-miimon 100
bond-updelay 5
bond-downdelay 5

and if your distro permits, re-use a MAC address for the bondX interface which matches one of the underlying physical MAC addresses.

To start with, you should be aware that there is only one Asterisk ‘distribution’ and it’s from Digium. it’s a telephony engine only (no GUI) – it’s powerful and many large enterprise users demand the level of control afforded by using this powerful engine directly (no GUI).

Next there are configuration generators, which add a nice GUI to Asterisk. (But Asterisk is still the telephony engine handling your PBX). These configuration generators hide a lot of complexity (and power) of Asterisk so they’re not right for everyone. There are undoubtedly lots of opinions on the best configuration generator but here’s my opinion:

• Issabel: The Issabel project arose from the ashes of the Elastix project. This is one of the few remaining fully open source PBX’s. As noted below with Elastix, much of the support community and forums are in Spanish (but there is a lot of English too), but the product is suitable for all languages. Issabel remains a popular PBX and is rapidly growing as FreePBX popularity wanes
• xCally Motion: A popular configuration generator in Europe and Africa, and growing in popularity in North America. xCally Motion is squarely targeted at small call centers. The user interface is slick and the range of features is impressive.
• VitalPBX: A PBX distribution that is closed source and is trying to build a following. Initial reports from this PBX are positive and we expect popularity to keep growing. The roots of this distro are Ombutel (which is also the basis for Xorcom). Despite the common ancestry with Xorcom, this distro has surpassed Xorcom and is on track to be a serious contender. A slick UI, good features, and a small but dedicated development team make this worthy of consideration.
• FreePBX: A popular open-source configuration generator in North America. FreePBX has a nice GUI and is a popular product. However, reports of frequent bugs which can disable features or crash the PBX cause some concern (don’t update if it’s working). Well suited to small office / home office installations. Beware: The Sangoma website constantly steers you to the “FreePBX Distro”, which is confusingly similar in name to “FreePBX”. See below.
• FreePBX Distro: Based on FreePBX (but this distro is heavily closed source), this distro comes on an easy to install CD. However, at every turn this product pushes you towards commercial add-ons, registration, activation, etc. As well, there are reports that updates cause your PBX to upload ALL of your configuration data (including employee names, email address, etc. defined in the voicemail config) to Sangoma. Stay CLEAR of this one.
• PBX In A Flash: This distribution is actually approximately 13 different distributions. The authors take other distributions and repackage them, often taking out commercial code to support a purely open source movement. The PIAF repackaging of FreePBX was one of the most popular distributions available (particularly since FreePBX is moving towards closed source and commercial). However, as FreePBX is closing its source code PIAF is trying to find a new position in the marketplace.
• Elastix: A popular configuration generator in Latin America. A mostly open source product with strong support for Spanish users (and English too). Although not as popular as some of the others, their open source commitment was building a dedicated following. Legal troubles have shut down the product, and as of 2017 they are offering a free edition of ‘3CX’ for windows as a replacement. (Most users are switching to a different configuration generator).
• Thirdlane: A small distribution whose claim to fame was multi-tenant PBX’s (as used by hosted PBX resellers). However, the advent of virtual machines (one tenant per VM), as well as other players offer multi tenant capabilities, has left this distribution as a niche player.
• WaZo: A small distribution that combines a wide variety of technologies that tries to create a telephony solution to every problem (router, gateway, SBC, UC, etc). However, weak documentation, and what appears to be a very long list of issues keeps this project best suited to hackers. Trying to be all things to all people prevents this distribution from doing one thing very well.
• Other: There are lots more distributions as well, so I’ll update this post over time.

 
So if I had to recommend one distribution for you to look at first, I would recommend Issabel v4. Second choice would be VitalPBX, and third choice would be FreePBX (open source, NOT distro).

There is oly one distro that I would suggest you stay clear of, so avoid “FreePBX Distro“. It comes as an easy-to-install CD/ISO, which suckers a lot of people in, but you are being led down a proprietary path and puts your private information at risk.