http://doc.astlinux.org/ 2012-05-17T03:23:26-05:00 http://doc.astlinux.org/ http://doc.astlinux.org/lib/images/favicon.ico text/html 2010-02-24T14:38:42-05:00 http://doc.astlinux.org/userdoc:asterisk-config?rev=1267043922&do=diff Almost all configuration of Asterisk can, and should, be carried out via the Edit tab of the GUI. If you are familiar with traditional installations of Asterisk, do not edit the files in /etc/asterisk, the traditional location of Asterisk .conf files. If you want to edit the .conf files without using the GUI, the majority of them are located in /mnt/kd. text/html 2011-11-27T05:55:37-05:00 http://doc.astlinux.org/userdoc:berofix?rev=1322394937&do=diff The new bero*fix card from BeroNet is a kind of modular Media Gateway in form of a PCI/PCIe card or an external box, which talks to Asterisk via SIP . It will be detected by the the system as a standard network card . It's the successor to the BNxSO and BNxE1 ISDN cards. It has 2 module slots, which can be used for BRI and/or S2M connections (also mixed). FXS, FXO, 2BRI/2FXS and GSM modules are now supported too. The bero*fix card has its own webserver and is configured via a WebGUI. Further In… text/html 2012-05-12T07:43:32-05:00 http://doc.astlinux.org/userdoc:board_jetway_nf96fl-525?rev=1336826612&do=diff AstLinux Board Type: * “geni586” (VGA video console) * “geni586-serial” (19200 baud serial console) Complete System Recommended Options: * Daughterboard: 3x 10/100/1000 Intel LAN Module * Memory: 240-pin DDR2 667/800 DIMM 2GB (or 2x 1GB sticks) * Flash Drive: Emphase Industrial S1 SATA (or 44-pin IDE) Flash Module 2 GB * Case: * No PCI Expansion Card Support * M350 Universal Mini-ITX Case * AC Adapter (brick): AC Power Adapter 60W, 12V, 5A * Fan (optional)… text/html 2010-01-18T15:58:26-05:00 http://doc.astlinux.org/userdoc:changes-0.6?rev=1263851906&do=diff FIXME Only a draft version, must be enhanced. * Grub was replaced by the Runnix bootloader * Runnix allows easy upgrades (via WebGUI or CLI) * UnionFS usage * Asterisk 1.4.x versions * Asterisk-GUI * Newer Linux kernel (2.6.20.21 in 0.6.8 compared to 2.6.16.12 in 0.4.8) * curl, ethtool, nmap, sipp (not all packages are enabled by default) * New Web interface by Lonnie, see altweb-changelog.txt (0.6.x uses versions up to 1.4.07) * Arno's Iptables Firewall was added text/html 2010-01-18T16:01:47-05:00 http://doc.astlinux.org/userdoc:changes-0.7?rev=1263852107&do=diff FIXME Only a draft version, must be enhanced. * When you upgrade be sure to read the UPGRADE.txt in the SVN * If you are using mISDN with PCI cards please also read this. * There is also a ChangeLog.txt for the many changes in detail. * Changes to the Web interface by Lonnie, are found here altweb-changelog.txt (0.7.x uses version 1.6.xx) * Arno's firewall upgraded (requiring a manual process to complete when upgrading from 0.6) * Removed astfw -- all features were replaced with Ar… text/html 2012-04-09T07:40:48-05:00 http://doc.astlinux.org/userdoc:changes-1.0?rev=1333975248&do=diff AstLinux 1.0 is a major upgrade from the previous 0.7 series. Most notable is much newer: Linux Kernel, BusyBox and supporting packages. In addition the C Library is generated via eglibc, which is binary compatable with other glibc executables. Glibc compatibility adds support for binary addons, such as Digium's G.729 CODEC, among others. text/html 2010-10-27T08:34:56-05:00 http://doc.astlinux.org/userdoc:dahdi?rev=1288186496&do=diff DAHDI is the replacement for Zaptel made by Digium. More information about this change can be found here and here (Interview with Kevin P. Fleming, site is in German but interview is in English). Note: Because AstLinux is an embedded solution optimized for size, a full version of Perl is not included. This means that the DAHDI config tools (dahdi_cfg, dahdi_genconf, etc) will not work, and you must write your DAHDI config files manually, as detailed below. text/html 2012-04-25T18:40:27-05:00 http://doc.astlinux.org/userdoc:documentation?rev=1335397227&do=diff New Installation Upgrade from 0.7.x to 1.0.x Upgrade from 0.6.x Upgrade from 0.4.x Sounds Packages Network and System Configuration Asterisk Configuration Changes from 0.7.x to 1.0.x Changes from 0.6.x to 0.7.x Changes from 0.4.x to 0.6.x text/html 2010-04-06T10:25:06-05:00 http://doc.astlinux.org/userdoc:faq?rev=1270567506&do=diff Why did all my config changes disappear when I rebooted? Astlinux is designed to write to its storage as little as possible, in order to lengthen the lifespan of its hardware. When you first install Astlinux, the whole system is read-only. You need to configure persistent storage options. text/html 2010-01-14T07:35:01-05:00 http://doc.astlinux.org/userdoc:gui_errors?rev=1263476101&do=diff Backup failed If you see this message when you try to perform a backup from the “System Tab”, this might be because there is not enough room in /tmp for the archive. To solve this using the GUI, check the following option: “Prefs > System Tab Options > Backup temporary file uses /mnt/kd/ instead of /tmp/” text/html 2012-04-09T07:48:59-05:00 http://doc.astlinux.org/userdoc:misdn?rev=1333975739&do=diff Usage * The (unofficial) zaphfc DAHDI driver for single port HFC cards is now included in the AstLinux 1.0.0 release. * Since zaphfc doesn't work with DAHDI 2.5.x, you can build a custom version of AstLinux with DAHDI 2.6 and the zaphfc successor dahdi_hfcs at <http://build.astlinux.org> now. text/html 2012-01-27T17:42:34-05:00 http://doc.astlinux.org/userdoc:new-install?rev=1327707754&do=diff Simple Installation Method Starting with Astlinux 0.6.3 a new simple installation method is available that performs many steps from a web interface. * Download the appropriate astlinux-XXX.img.gz file from the AstLinux website. * On Linux or *BSD use dd to transfer the image to the CF card. (gunzip the image, then dd if=astlinux-XXX.img of=/dev/sdX where sdX is your compact flash card). On Windows boxes, you'll want to use physdiskwrite (0.5.1 or later). * Boot your system. * Conti… text/html 2011-07-01T14:57:33-05:00 http://doc.astlinux.org/userdoc:openvpn_access?rev=1309550253&do=diff Configuring client-specific rules and access policies Here is a good howto for this: <http://openvpn.net/index.php/open-source/documentation/howto.html#policy> Additionally in AstLinux the following must be done: * In the Firewall config “Allow OpenVPN Server tunnel to xx LAN Interface” must not be checked! * The iptables rules should be put into ”/mnt/kd/arno-iptables-firewall/custom-rules” file into the FORWARD_CHAIN. * Because the limited users have still access to the Astlinux s… text/html 2011-12-20T11:08:45-05:00 http://doc.astlinux.org/userdoc:runnix_astlinux_mismatch?rev=1324400925&do=diff * To fix mismatched RUNNIX/AstLinux you need either serial or video console access * serial access with a crossover cable, baudrate 19200 8N1 or 38400 for Alix 2 boards. * video console will probably have US keyboard layout * The other way is to get out the CF from the box, put it in CF card reader and make the changes on another computer as you would do with a flash drive. text/html 2010-03-24T12:38:17-05:00 http://doc.astlinux.org/userdoc:sounds-packages?rev=1269452297&do=diff Sounds Packages AstLinux 0.7.1 and later no longer includes sound files in the default image. This provides several benefits: * The download image has been reduced (~25% smaller) to approximately 30MB. * Users can choose to install more than just the core sounds, or non-english sounds. * For some users, better quality sound playback will be achieved. Additionally Asterisk 1.6.x users can use g722 sounds. text/html 2010-02-24T14:42:31-05:00 http://doc.astlinux.org/userdoc:system-config?rev=1267044151&do=diff General Information FIXME This page is under construction. UnionFS AstLinux uses a UnionFS overlay with a read-only 'firmware' and read-write partition. The following graphic shows a representation of this. The firmware resides in a VFAT partition along with the Runnix “bootloader”. Runnix is loaded by syslinux. After Runnix is active, it looks for the correct 'firmware' to use from the 'os' directory on the VFAT partition. It also mounts the unionfs writeable area if available. Multi… text/html 2010-01-05T10:29:38-05:00 http://doc.astlinux.org/userdoc:telephony_cards?rev=1262708978&do=diff DAHDI text/html 2012-05-09T16:36:31-05:00 http://doc.astlinux.org/userdoc:tt_ast_startup?rev=1336599391&do=diff Since Asterisk 1.6.0 there is a config file cli.conf, where you can add CLI commands, which will be executed, when Asterisk starts. With the originate command you can also trigger a “call” at startup. A call to a local dummy extension can trigger a context, where you can e.g. initialize custom lamp states (from a database) or something else. text/html 2012-04-09T17:43:43-05:00 http://doc.astlinux.org/userdoc:tt_asterisk-gui?rev=1334011423&do=diff The Asterisk GUI is not the same as the AstLinux Web Interface. The Asterisk GUI is an open source project created by Digium, allowing the Asterisk configuration to be created, edited and managed via a web browser. If you prefer to edit the Asterisk configuration via a text editor or via the Edit tab in the AstLinux Web Interface, do not use the Asterisk GUI without first understanding how the Asterisk GUI re-writes the configuration files. text/html 2012-02-10T10:28:47-05:00 http://doc.astlinux.org/userdoc:tt_asterisk_call_notify?rev=1328891327&do=diff At times it may be useful to display incoming calls on a computer desktop. One such method was developed by Sven Slezak <sunny at mezzo.net>. Several clients are available, and integration in the Asterisk dialplan is very simple. An example dialplan (extensions.conf) snippet: text/html 2012-04-24T15:54:44-05:00 http://doc.astlinux.org/userdoc:tt_cf_usb_combo_booting?rev=1335300884&do=diff A new feature implemented with runnix-0.3.3 and AstLinux 0.7.8 allows the AstLinux distribution to be placed on a USB flash drive and operate just as if it were on a CF card. If your AstLinux system box can boot directly to a USB drive, follow steps #2 and #3 below and install the USB flash drive as in #4. text/html 2010-01-24T13:26:46-05:00 http://doc.astlinux.org/userdoc:tt_change_net_hardware?rev=1264361206&do=diff Beginning with AstLinux 0.7, the network interface names (ex. eth0, eth1) are 'sticky' with respect the MAC address of the associated network interface. The system file that makes the associations is /etc/udev/rules.d/70-persistent-net.rules . If the file /etc/udev/rules.d/70-persistent-net.rules does not exist on first boot, it will be automatically generated, creating an association very similar to the way AstLinux 0.6 assigned network interfaces. text/html 2010-12-19T07:33:12-05:00 http://doc.astlinux.org/userdoc:tt_console-kmap?rev=1292765592&do=diff If the file 'os/console.kmap' exists on the vFAT boot partition and a non-serial console is used, both RUNNIX and AstLinux will use the 'console.kmap' keyboard map. More infos: * <http://dev.alpinelinux.org/bkeymaps/> * <http://www.mail-archive.com/busybox@busybox.net/msg12140.html> * or google ”busybox loadkmap de.map fr.map”. text/html 2010-01-06T13:10:54-05:00 http://doc.astlinux.org/userdoc:tt_editable_files?rev=1262805054&do=diff For the average user, there is a rule in AstLinux: /mnt/kd/. /etc/rc.modules and /etc/udev/rules.d/70-persistent-net.rules are two exceptions to the rule -- these two files may be directly edited. text/html 2012-03-02T06:09:09-05:00 http://doc.astlinux.org/userdoc:tt_ip_phone_provisioning?rev=1330690149&do=diff Most modern IP Phones allow automatic provisioning from a central location. Described here are AstLinux features and configuration tips to provision phones. Create the /mnt/kd/phoneprov/ directory. After a reboot, both HTTP and HTTPS will be served from that directory provided the URL directory path begins with /phoneprov/ . This directory is not effected by the root directory of the general HTTP/HTTPS server configuration, which is independent, though the listing and logging options also … text/html 2012-04-25T21:55:13-05:00 http://doc.astlinux.org/userdoc:tt_ipsec_vpn_apple_ios?rev=1335408913&do=diff The popular Apple iOS platform has limited VPN options, one of which is IPsec (Cisco) which uses IPsec + XAuth. IPsec + XAuth with certificates is supported in AstLinux 1.0.3 . Apple iOS 5.1 or later is recommended, iOS 4.2 has been shown to work with the settings described below, except NAT Traversal is not supported in iOS 4.2 . text/html 2011-03-11T10:49:10-05:00 http://doc.astlinux.org/userdoc:tt_ipv6_tunnel_config?rev=1299862150&do=diff Requirements: * AstLinux 0.7.4 or later * Static IPv4 public address * Hurricane Electric www.tunnelbroker.net account (free)* * Note that other IPv6 Tunnel Brokers exist, and possibly may better suit your location. This example will use tunnelbroker.net. text/html 2010-01-08T14:11:14-05:00 http://doc.astlinux.org/userdoc:tt_network_config?rev=1262981474&do=diff Giving '$INTIF' a gateway In some installations, AstLinux will not be your LAN's gateway, and AstLinux itself might have to use a gateway to reach a particular subnet (common in VPN situations). To configure this, edit /mnt/kd/rc.elocal (or create it, if not yet present, and make it executable), and add the following to it: text/html 2011-11-29T18:07:57-05:00 http://doc.astlinux.org/userdoc:tt_runnix?rev=1322611677&do=diff It is very important to understand that while AstLinux 0.7.x uses the runnix-0.3 (or runnix-0.2.1) bootloader, AstLinux 1.0.x requires the runnix-0.4 bootloader. This change is required since the Linux Kernel differences require different squashfs image formats. text/html 2012-01-27T11:07:42-05:00 http://doc.astlinux.org/userdoc:tt_virtualbox?rev=1327684062&do=diff You can convert an astlinux-XX.img file to a VirtualBox .vdi file and have a bootable system with a few simple steps. * Download an AstLinux 'geni586' .img.gz file * Decompress the image using gunzip, yielding a .img file * Use the VBoxManage utility to convert the image to a virtual disk text/html 2012-01-27T13:10:39-05:00 http://doc.astlinux.org/userdoc:tt_vmware?rev=1327691439&do=diff You can convert an astlinux-XX.img file to a VMware .vmdk file and have a bootable system with a few simple steps. * Download an AstLinux 'geni586' .img.gz file * Decompress the image using gunzip, yielding a .img file * Use the VBoxManage utility (VirtualBox) to convert the image to a virtual disk text/html 2011-01-05T15:37:03-05:00 http://doc.astlinux.org/userdoc:tt_web_interface_font?rev=1294263423&do=diff The Web interface uses a monospace font to display much of the information. The client web browser will automatically use an appropriate monospace font installed on the client computer. In particular, the Bitstream Vera Sans Mono monospace font is given priority if available. If the client computer does not contain the Bitstream Vera TrueType fonts, they may be optionally installed. Follow the normal steps for installing fonts on the client computer's operating system. text/html 2010-01-07T04:14:13-05:00 http://doc.astlinux.org/userdoc:upgrade-0.4?rev=1262859253&do=diff FIXME Only a draft version, must be enhanced, corrected. Please read UPGRADE.txt, changes-0.6 and changes-0.7 before you start. If you are using mISDN with PCI cards please also read this. Because there wasn't a WebGUI backup function in the 0.4.x releases, you could backup the content of your keydisk (/mnt/kd) over SSH: text/html 2011-11-26T17:37:00-05:00 http://doc.astlinux.org/userdoc:upgrade-0.6?rev=1322350620&do=diff Please read UPGRADE.txt and changes-0.7 before you start. If you are using mISDN with PCI cards please also read this. Automated Process (new after 0.6.2) Most normal users should use this process. You can upgrade now from the web interface OR from the CLI text/html 2011-12-20T10:48:07-05:00 http://doc.astlinux.org/userdoc:upgrade-0.7?rev=1324399687&do=diff Please read 1.0.x ChangeLog.txt before you start. It is very important to understand that while AstLinux 0.7.x uses the runnix-0.3 bootloader, AstLinux 1.0.x requires the runnix-0.4 bootloader. This change is required since the Linux Kernel differences require different squashfs image formats. text/html 2012-01-16T12:40:58-05:00 http://doc.astlinux.org/userdoc:wanpipe?rev=1326739258&do=diff Starting with AstLinux 0.7.6 the utilities wancfg and wancfg_dahdi which configures Sangoma telephony cards for DAHDI, are supported. These utilities define files in the /mnt/kd/wanpipe (aka /etc/wanpipe) directory. Previous to AstLinux 0.7.6 the utilities wancfg and wancfg_dahdi were not supported. The configuration files must therefore be created manually for older versions of AstLinux.