Internal Notes on AstLinux

Transcription

1 Internal Notes on AstLinux For AstLinux to be run on a x86 architecture from a compact flash card, download the i586 tar.gz image. Use a command similar to this to write the CF card: gunzip -c ~gcooper/desktop/astlinux i586.img.gz > /dev/sdb Boot AstLinux without the USB key disk and log in as 'root' with a password of 'astlinux'. Then insert the USB key disk that will contain your configuration and voic files. Run this command and follow the prompts to create/recreate the keydisk: genkd To change the root password, just enter: passwd For a full-function PBX, I think it is usually best to configure the PBX (AstLinux) as the gateway to the Internet for your LAN. By making the PBX your edge device, you will find it easier to connect to ITSPs and receive inbound SIP calls. Furthermore, you can take advantage to the traffic shaping included with AstLinux to prioritize voice traffic. This, of course, requires two ethernet interfaces. 1 / 5

2 Besides the various PCI network interface cards (NICs) supported automatically by AstLinux, I found that the easy-to-find Linksys USB200M USB 10/100 adapter seems to work easily. I have also heard the Netgear FA-120 USB adapter works well also and I think it uses the same driver. To use the USB200M USB network adapter as your external (Internet or WAN) interface, do this: Boot the AstLinux box and log in as root. Remount the root filesystem as read/write: mount -o rw,remount / Edit the /etc/rc.modules file with vi or nano and add 'asix' before the module (driver) used by your internal interface. Remount the filesystem read-only, insert the USB NIC and then reboot. mount -o ro,remount / reboot 2 / 5

3 You can change the order of your network interfaces (eth0, eth1) by changing the order of the modules in rc.modules, should you need to. After you reboot, you should see both the INTIF and EXTIF if you have enabled them both in /etc/rc.conf by uncommenting them. Polycom Phone Provisioning with AstLinux Polycom phones default to using FTP for provisioning. The default FTP username is 'PlcmSpIp' and the default password is the same 'PlcmSpIp' (case-sensitive in both). This is very easy to support with AstLinux. Just create a user 'PlcmSpIp' with the same 'PlcmSpIp' password: adduser PlcmSpIp Then place all of your Polycom provisioning files in /home/plcmspip: scp polycom_files.tar PlcmSpIp@ :~ At the AstLinux box or from an SSH console: cd /home/plcmspip tar -xvf polycom_files.tar chown PlcmSpIp.PlcmSpIp * Configuration Files 3 / 5

4 There are generally three main configuration files: - <macaddress>.cfg - per phone - determines other config files - phone<ext>.cfg - per phone configuration - sip.cfg - global configuration settings for all phones Then there are two main directory files: directory.xml - default directory loaded into phone if per-phone directory doesn't exist - intended as baseline directory with which new phones are loaded - filesystem format required to reload default directory - doesn't work well as company-wide directory - <macaddress>-directory.xml - per phone directory - if exists, supercedes default directory - can be edited on the phone itself - editing of directory depends on write capability of FTP/TFTP space Example <macaddress>-directory.xml for Polycom 301 The polycom 301 only has one button available to program so we use it to retrieve messages. Change the <ct> to contain your voic extension. 4 / 5

5 <?xml version="1.0" encoding="utf-8" standalone="yes"?> <!-- $Revision: 1.2 $ $Date: 2004/12/21 18:28:05 $ --> <directory> <item_list> <fn>vm</fn> <ct>7001</ct> <sd>1</sd> </item_list> </directory> Example <macaddress>-directory.xml for Polycom 501 The Polycom 501 has two buttons to program and it already has a Messages button, so we use the buttons for Park/Pickup. <?xml version="1.0" encoding="utf-8" standalone="yes"?> <!-- $Revision: 1.2 $ $Date: 2004/12/21 18:28:05 $ --> <directory> <item_list> <fn>park</fn> <ct>*98</ct> <sd>1</sd> <fn>pickup</fn> <ct>*99</ct> <sd>2</sd> </item_list> </directory> 5 / 5