AskoziaPBX
AskoziaPBX – A new PBX IP now ready for all
We had published a new Askozia image by adding some base features that a pbx need to do:
The new PBX IP is now ready for company that need the following features:
- All base IP PBX features
- AA (one level automated attendant, also called IVR)
- BusinessHours Applications (automatic night&day applications and with code)
- AA with integrated BusinessHours Application (automatic night&day applications and with code)
Here the features added and the preconfigured snapshot.
In the next day we will publish the configuration guide for integrate Askozia with Cisco voice Gateway. So you can deploy a great solution at low cost with a Cisco1751-V router.
You can find the new image for alix.2X e3X preconfigured for ITALY and US (coming soon) users in the download category and all tech notes for how to in the support category.
Networksoul Team
AskoziaPBX – Preconfigured Image – Getting Started
Prerequisites The information in this document is based on these software and hardware versions: · Alix23x Embedded Appliance with preconfigured image installed · A PC with Ethernet connection Getting started After installed the preconfigured AskoziaPBX image on Compact flash (see Write Askozia image on CF), you are able to connect to the ALIX embedded appliance for verify configuration and tune it! The embedded Appliance start with 192.168.1.1 preconfigured LAN IP ADDRESS interface and with Username admin Password admin Attach an Ethernet cable from Ethernet interface of your PC and the LAN interface of the embedded device; put your PC ethernet interface in the same network address space of the embedded appliance for connect to it (for example 192.168.1.10 and netmask 255.255.255.0).
Try to reach the embedded device with an ICMP request from command line interface of your PC:
ping 192.168.1.1
you should receive an ICMP response; this indicate that you can connect via http and view/modify the configuration.
http://192.168.1.1
You will be asked to insert username and password for login!
AskoziaPBX – Write Askozia image on CF (LINUX)
How to create a Compact Flash from scratch (LINUX): Prerequisites The information in this document is based on these software and hardware versions: · Download the AskoziaPBX preconfigured image from here in /tmp directory · Compact Flash at least 128MB · Alix 2Dx Embedded Appliance · A PC with LINUX OS (UBUNTU in our case) Write preconfigured IMAGE to CF from scratch: 1. First of all, list all device partition table; please, don’t plugin the CF device networksoul@linux:/$ sudo fdisk –l [sudo] password for networksoul: <enter root password> Disk /dev/sda: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0×00072332 Device Boot Start End Blocks Id System /dev/sda1 * 1 993 7976241 83 Linux /dev/sda2 994 1044 409657+ 5 Extended /dev/sda5 994 1044 409626 82 Linux swap / Solaris networksoul@linux:/$ /dev/sda is the hard disk 2. Plug the CF into the reader, and list all partition table again networksoul@linux:/$ sudo fdisk -l Disk /dev/sda: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0×00072332 Device Boot Start End Blocks Id System /dev/sda1 * 1 993 7976241 83 Linux /dev/sda2 994 1044 409657+ 5 Extended /dev/sda5 994 1044 409626 82 Linux swap / Solaris Disk /dev/sdc: 2048 MB, 2048901120 bytes 64 heads, 62 sectors/track, 1008 cylinders Units = cylinders of 3968 * 512 = 2031616 bytes Disk identifier: 0×70707573 This doesn’t look like a partition table Probably you selected the wrong device. Device Boot Start End Blocks Id System /dev/sdc1 ? 428932 916907 968143376 d Unknown Partition 1 has different physical/logical beginnings (non-Linux?): phys=(255, 105, 46) logical=(428931, 3, 57) Partition 1 has different physical/logical endings: phys=(370, 10, 5) logical=(916906, 35, 24) Partition 1 does not end on cylinder boundary. /dev/sdc2 ? 428931 566055 272054928 a OS/2 Boot Manager Partition 2 has different physical/logical beginnings (non-Linux?): phys=(781, 111, 63) logical=(428930, 26, 34) Partition 2 has different physical/logical endings: phys=(357, 80, 50) logical=(566054, 55, 59) Partition 2 does not end on cylinder boundary. /dev/sdc3 ? 445839 891749 884685616+ 6f Unknown Partition 3 has different physical/logical beginnings (non-Linux?): phys=(372, 97, 51) logical=(445838, 30, 47) Partition 3 has different physical/logical endings: phys=(357, 32, 48) logical=(891748, 36, 27) Partition 3 does not end on cylinder boundary. /dev/sdc4 ? 727239 727252 26849 a OS/2 Boot Manager Partition 4 has different physical/logical beginnings (non-Linux?): phys=(269, 114, 37) logical=(727238, 12, 25) Partition 4 has different physical/logical endings: phys=(0, 0, 0) logical=(727251, 46, 30) Partition 4 does not end on cylinder boundary. Partition table entries are not in disk order networksoul@linux:/$ /dev/sda is the hard disk /dev/sdc is the CF; note that there are several non linux partitionbut this is not a problem! 3. List the image; we put it on /tmp directory networksoul@linux:/$ cd /tmp networksoul@linux:/tmp$dir askoziapbx-ITv10-alix23x-1.0.3.ZIP networksoul@linux:/tmp$ 4. Unzip the image networksoul@linux:/tmp$ networksoul@linux:/tmp$ unzip askoziapbx-ITv10-alix23x-1.0.3.ZIP Archive: askoziapbx-ITv10-alix23x-1.0.3.ZIP inflating: askoziapbx-ITv10-alix23x-1.0.3.img networksoul@linux:/tmp$ dir askoziapbx-ITv10-alix23x-1.0.3.img askoziapbx-ITv10-alix23x-1.0.3.ZIP networksoul@linux:/tmp$ 5. Umount the device networksoul@linux:/tmp$umount /dev/sdc 6. Copy the image on the CF and list the write partition networksoul@linux:/tmp$ sudo dd if=askoziapbx-ITv10-alix23x-1.0.3.img of=/dev/sdc 247968+0 records in 247968+0 records out 126959616 bytes (127 MB) copied, 150,03 s, 846 kB/s networksoul@linux:/tmp$ networksoul@linux:/tmp$ networksoul@linux:/tmp$ sudo fdisk -l Disk /dev/sda: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0×00072332 Device Boot Start End Blocks Id System /dev/sda1 * 1 993 7976241 83 Linux /dev/sda2 994 1044 409657+ 5 Extended /dev/sda5 994 1044 409626 82 Linux swap / Solaris This disk has both DOS and BSD magic. Give the ‘b’ command to go to BSD mode. Disk /dev/sdc: 2048 MB, 2048901120 bytes 255 heads, 63 sectors/track, 249 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0×90909090 Device Boot Start End Blocks Id System /dev/sdc4 * 1 4 25000 a5 FreeBSD Partition 4 has different physical/logical endings: phys=(1023, 254, 63) logical=(3, 28, 41) networksoul@linux:/tmp$ END JOB; now your IP PBX is ready to workAskoziaPBX – Business Hours (step2)
How to configure Askozia for BusinessHours (step2): Prerequisites The information in this document is based on these software and hardware versions: · http://www.networksoul.net/2009/06/askoziapbx-business-hours-step1/ · AskoziaPBX v.1.03 · Recordings pakages already installed http://www.zrnet.it (Roberto Zilli); · Recorded Message already registered in the path /storage/recordings.pkg/data/recordings (for example “it-Businness-hours.sln”); · Alix23x Embedded Appliance Providers Extension and BusinessHours application association: Now, we need to associate the custom BusinnessHours application with incoming provider extension; suppose we have a SIP provider account with the following credentials (all parameters are given by sip providers accounts): Username: 02555555 Password: password Sip server voip.eutelia.it: Sip extension: 02555555 From AskoziaPBX GUI, Accounts>Providers, add a new SIP Account as follow:
Set-up the new SIP Account with the right parameters:
Try to call SIP telephone number (i.e. 02555555)!
Categories
- AskoziaPBX (6)
- cisco (1)
- Debian Lenny (6)
- general (1)
- Home server (6)
- Linux (6)
- m0n0wall (1)
- switching (1)
- voice (1)
- Voyage Linux (6)
AskoziaPBX
You can find the PBX IP preconfigured image here:
And obtain all support information "how to" here:
