Telium Support Group

To start, lets make sure nothing significant is missing/misconfigured. To diagnose:

1. Stop the SecAst service
2. Delete the SecAst event log (file)
3. Start SecAst from the command line with the -f parameter (foreground)
4. Post the screen output and log file (first 200 lines)
5. Post the output of “ldd secast” (from the /usr/local/secast directory)

100% CPU is very unusual for SecAst so I suspect something major is missing/misconfigured. If the above looks ok I suggest you post your secast config file (if you are concerned about posting email it to support@autocommander.aws2.ocg.ca)

Licensing is a three step process:

The first step is to request a license file after installation, which you can do by telnetting to the telephony server on port 3001 (for HAast/HAfs) or 3000 (for SecAst) and generate a license request file. For example:


telnet localhost 3001

HAAst telnet interface on ‘Ford Motor Company Lansing Call Center PBX’
HAAst>license request
To create a license request, enter the information specified below. To abort
the request enter a . as the answer to any question.
 
Enter the name of your organization as it will appear in your license?
organization>My Company
Enter a description for the local node (eg: pair 1 server B, or Texas,
or Rack 1 upper)?
description>Los Angeles Colocation
Virtual machine detected. Automatically selecting Commercial Unlimited
edition (Flex Edition not available in virtual machines).
What type of license activation would you like to use: USB dongle Cloud, or
Volume license server [U, C, V]? (Hardware Fingerprint option not available
in virtual machines. See http://autocommander.aws2.ocg.ca/activation for more information)
activation>u
The license request has been successfully completed and placed in file:
‘/usr/local/haast/haast.licenserequest’
Send this file to support@autocommander.aws2.ocg.ca to receive your license file
HAAst>


This will create a file called haast.licenserequest in your /usr/local/haast directory (or hafs.licenserequest, or secast.licenserequest in the associated directory).

Second, you need to send that file to support@autocommander.aws2.ocg.ca and we will reply with a license file (and optionally send you a USB dongle if you chose that activation type).

Third and final step is to copy the license file we send you to your telephony server. If you chose USB Dongle activation then there is one extra step: plug in the dongle and issue the “license usbdongle” command and send the code on screen to support@autocommander.aws2.ocg.ca We will reply shortly thereafter with the pairing code for the dongle.

When you are all done restart the HAast (or HAfs or SECast) service and you will see in the event log, or from the web GUI, or from the telnet interface, that the system is running as the commercial edition (whichever edition you purchased)

The error you are seeing in the Asterisk CLI is due to an app not properly handling concurrent use of the AstDB (SQLite 3 database). When synchronizing the AstDB HAAst will briefly lock the database (with a SQL lock), at which point apps should queue their commands until the lock is released.

Most properly designed apps respect concurrency by checking for the lock, then either blocking or retrying for a period of time, to acquire the lock. An overly simplistic application might not check for a lock, and simply report an error (“database is locked”) following an attempt to write. We have seen this error before with FreePBX and a couple of open source Asterisk add ons.

Although the proper solution involves asking the app developer to correct their code, we realize that some developers have no interest in doing so (or become hostile if you suggest anything is wrong with their code). So until the developer in question fixes their code, we do offer a workaround.

Create an Asterisk pre-start event handler (/usr/local/haast/events/asterisk.start.pre) in HAAst containing the following code:


#!/bin/bash
sqlite3 /var/lib/asterisk/astdb.sqlite3 “PRAGMA journal_mode=wal”;


This will enable the “WAL” feature of SQLite3 – which effectively prevents reader and writer processes from locking each other out of the database. You can also issue this command from any bash prompt and you should see the response “wal”. If you don’t see this respnose, repeat the command every 10 seconds until “wal” is returned. (The command can fail if the database is already locked).

You can download the products directly from our website (without the need for a key/link). The “Free” edition you can download directly actually turns into the “Commercial” edition once you add a license file.

You can request your license files at any time, after you have installed the product. Once the product is installed and running, you must telnet to the built-in telnet server and there you must enter the command “license request”.

Answer the questions presented on screen, and then send the resulting license request file to support@autocommander.aws2.ocg.ca (you will see more instructions on the telnet screen). In response you will get a license file (and optionally a USB dongle depending on the activation options you chose onscreen) from the Telium support team.

For more information on activation options see

Yes you can! Like your other syncjobs, setup a new syncjob which requires the remotestate be ‘asterisk running’, localstate as ‘asterisk stopped’. Then set the syncjob to sync a single file:

/tmp/secast.state

Your tertiary PBX will always pull the latest security data from the active PBX. And if the tertiary promotes, there is no risk overwriting the local security data because of the localstate requirement.

PBXSync is designed to handle a mix of internal and external hosts. When you setup your pbxsync.conf file, you will notice that the rsync and MySQL IP address entries allow for up to 3 IP addresses. These three addresses represent:

1. Public IP – this is the IP address that PBXSync will publish to other PBXSync hosts not on your local subnet.
2. Private IP – this is the IP address that PBXSync will publish to other PBXSync hosts on your local subnet.
3. Local IP – this is the IP address that PBXSync uses when connecting to itself.

So for the Public IP use the IP address of your firewall, and for your Private IP use the internal (non-routable) IP address of an internal host. The local IP should probably be set to ‘localhostipv4’. Also be sure to set the localsubnets setting to match your internal network(s).

Next, on your firewall setup porting mapping from the public IP address to the internal private IP addresses & port. After that the external host will be able to reach the internal host as well.

In some (particularly recent) Asterisk versions quotes are considered just another character in the value of a setting. So

Quote:
secret=ABC

and

Quote:
secret=”ABC”

are different. Please remove quotes the credential setting values in your Asterisk /etc/asterisk/manager.conf file and restart the HAAst services.