After the installation (or the start) of the live cd you have Debian Etch 4.0, Asterisk 1.4, MySQL and Apache ready to use. This documentation give you all the necessary informations to use asterLive™ and the already installed applications.
1. System settings
The system is configured with UTC time, you can change this with:
# tzconfig
from the command line (please do not forgett to restart asterisk and MySQL afterwards), you can change the keyboard layout with:
# loadkeys de
for german keyboard layout.
After an english installation, a Debian system is configured to use en_US.UTF-8 as the system locale, which can cause problems when connecting to it using an ssh client that is not capable of this character set. If you use F-Secure SSH client for example, you have to adjust the system locale to use en_US.ISO-8859-15. To change the system locale, call the following command from the command line:
# dpkg-reconfigure locales
When installing a system by using the included installer on asterLive™, all passwords (system root and MySQL root@localhost) are set to "changeme".
2. MySQL Database connections
the MySQL root password is: changeme and the password of the asterisk user on the asterisk database is: asterisk
There are 3 SIP Peers installed which are configured in the ast_sippeers table inside the asterisk database, the asterisk database hold also the queue, which will be used inside the dialplan (ast_queues) all tables that start with ast_ will be used for the Asterisk settings, you can handle easy the SIP Peers with phpmyadmin or if you use IVAN™, inside the IVAN™ GUI.
IVAN™ read the connection settings for the database from the file /etc/asterisk/res_mysql.conf if you want to use another database Server you only need to change this file and transfer the tables of the asterisk database.
asterBoard™ read the database connection from /etc/asterboard/webapi/config_zakotel.php and use the SIP Peers as Phones inside the application,
3. Apache Webserver
Inside the document root of the Apache webserver you have 3 importand folders: asterboard, ivan and phpmyadmin, all the folders are symbolic links that link to /usr/share
The directory asterisk will hold 2 files createhints.php for the configuration of the hints inside the Asterisk dialplan and mysql_conndata.php for the database settings which are used inside the asterisk dialplan. If you change the document root of your webserver you need to take care that this directory is accessible via http://localhost/asterisk (or you change the include settings inside /etc/asterisk/extensions.conf)
4. Asterisk Settings and Dialplan
Asterisk is installed with the addons and use the database for the configuration of SIP, IAX, QUEUES,...
lets take a look to the Dialplan /etc/asterisk/extensions.conf, there are some [globals] variables which are important:
; my Area (USE ONLY DIGITS, NO BLANKS, "+" OR OTHER CHARACTERS !!!)
INTL_PREFIX = 43
NATIONAL_PREFIX = 1
LOCAL_PREFIX = 222222
; Outbound trunks
; TRUNKx=,,,
TRUNK0=IAX2,iaxat,${GLOBAL(INTL_PREFIX)}${GLOBAL(NATIONAL_PREFIX)}${GLOBAL(LOCAL_PREFIX)},y
TRUNK1=Local,isdn-out,${GLOBAL(LOCAL_PREFIX)},y
EMERGENCY_TRUNK = Zap/1
EXTENSION_TIMEOUT = 15
DIAL_OPTIONS = rwW
DIALOUT_OPTIONS = rTW
DIALOUT_TIMEOUT = 60
QUEUE_OPTIONS = ntw
COMPANY_MAILBOX = 10
RECDIR = /var/www/recordings
SUPP_CID = prohib
#include "extensions.d/*.globals"
#include "include/macro-*.conf"
on the first 3 lines you can set your phone number for the outdial INTL_PREFIX, NATIONAL_PREFIX and
LOCAL_PREFIX the outbound trunks use a macro to dial out, you can change this easy to your needs by changing the first and second value of each line, if you want to add another trunk, you only need to insert another line and use TRUNK2= and go forward with TRUNK3= and so on... the TUNKS will be used inside the [outbound] context.
You can the EMERGENCY_TRUNK to make sure that emergency calls will be hadled correctly this setting will be used inside the [emergency] context.
The [inbound] context will be used for incomming calls, when a call reach this context, Asterisk will check on the Asterisk db if the DEVSTATES night is set to 2 if this is set the call will be forward to the COMPANY_MAILBOX (see the global settings of the company mailbox), if the DEVSTATE is not set, the calls to 10,11,12,... goe to the internal context and call the hints, all other calls will go to the board queue.
The [inbound] context can be used with 2 digits, if you want to use more or less you have to change the [inbound] and [internal] context.
Inside the [internal] context there is a include which generate the hints, please be sure that:
http://localhost/asterisk/createhints.php is accessable, the script createhints.php can only be used from 127.0.0.1
At the bottom of the dialplan there is another include which includes all *.conf files of the /etc/asterisk/extensions.d directory (also the dialplan for IVAN™).
There is one conference room configured which is inside the [internal] context it can be used on extension 7000
5. asterBoard™
you can access the asterBoard inside the document root of your webserver when you click on the asterboard directory, asterBoard comes with 3 configured phones (tel10, tel11, tel12) a conference room (extension 7000 inside the [internal] context and the board queue, the phones and the queue is configured inside the database (ast_sippeers for the phones, and ast_queues for the board queue), the phonebook.xml with the phones and queues will be automaticly generated when you open the asterBoard, the conference is hard coded inside
/var/www/asterboard/amfphp/services/asterboard/WebAPI_zakotel.php starting line #145 and will also be added to the phonebook.xml (the phonebook.xml will be generated on each start of the asterBoard, but it will not be stored on the file system, all changes you want to do needs do be done inside
/var/www/asterboard/amfphp/services/asterboard/WebAPI_zakotel.php).
Inside the ast_queues table there are 3 fields that are only used from asterBoard:
ab_name = the name of the queue which will be displayed inside the asterBoard
dp_extension = the extension where the queue is accessable inside the dialplan (/etc/asterisk/extensions.conf)
dp_context = the dialplan context where the queue is accessable, this is NOT the context field which will be used for queues to allow the caller to exit with a key for further action.
Please take a look to the already configured phones to see what fields are necessary (regexten must be set with the extension of the phone) and also do a look to the WebAPI_zakotel.php to get a better understanding how asterBoard work.
The License for your asterBoard must be set inside /etc/asterboard/config.xml
Licenses are being validated online once the application is started and several times during runtime of the application. So the computer that the software is running on needs permanent access to the internet, the host contacted is licensing.zakotel.com via the HTTP protocol. This
connection can be made either direct or by using a http proxy server.
With every license you purchase you can run exactly one computer with this license at a time. The online license verification process will recognize a second use and the application on the formerly started computer will terminate with an license violation.
For testing purposes, you can use the following demo license key inside the application config file config.xml:
...
<profile>
<displayname>Demo-Board</displayname>
<license>
<key>DEMO</key>
</license>
</profile>
...
This demo license will run for a certain time, normally one hour. A message in the status line will show you the remaining time the application will be usable.
6. IVAN™
you can start the setup of IVAN when you click on the ivan folder inside the document root, most of the configuration can be done inside the GUI, there is another configuration file /etc/ivan/ivan.localhost.conf where you can configure some special settings which are explained inside the file.
The License of IVAN must be insert into the file /etc/asterisk/at_license.d/ivan.conf, with the DEMO license you can run one connection if there come a second concurrent connection the call will not be answered, after the insert of the license you need to go to the Asterisk CLI:
# rasterisk
or, if you have access to the machine you can go to terminal 9 (ALT+F9) to access the Asterisk CLI
then restart the licensing module:
*CLI> asterTools licenses reload
you can see how many connection you can use:
*CLI> asterTools licenses show
will bring you the following output when you use the DEMO license:
asterTools(tm) licenses:
------------------------
Product Status in-use / max
ivan demo 0 / 1
please take a look to the Tutorials on this website for more informations about IVAN™
Submitted by Alfred on 26 August, 2008 - 11:53.
