alix

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 work

Tags: , , , , , , , , ,

Thursday, July 30th, 2009 AskoziaPBX 3 Comments

AskoziaPBX – 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:
03_BusinessHours_AddProviders

Set-up the new SIP Account with the right parameters:

04_BusinessHours_Operator_snapshot

Name:
(this is the name of sip account, for example voipstunt_account):
eutelia_sip
Dialing Pattern:
(this is the pattern for outbound call, no inbound; string | removes a prefix, string . match one or more characters;  “1|. matches 188888888 but only passes 88888888 to the provider”)
1|.
Username:
(this is the username of sip account):
02555555
Password:
(this is the password of sip account):
password
Host:
(this is the ip address or FQDN of SIP account proxy server):
Voip.eutelia.it
Incoming Extension:
(Here we need to associate the incoming extension with the custom BusinessHours Application):
02555555      ->        BusinessHours (custom application)
Click save
05_BusinessHours_Providers

Try to call SIP telephone number (i.e. 02555555)!

Tags: , , , , , , , , ,

Monday, July 6th, 2009 AskoziaPBX No Comments

AskoziaPBX – Business Hours (step1)

How to configure Askozia for Business Hours:
Prerequisites
The information in this document is based on these software and hardware versions:
·         AskoziaPBX v.1.03
·         Recordings packages 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
Setup a Custom Application with the following logic:
From AskoziaPBX GUI, Dialplan>Applications, create a new Custom Application as follow:

BusinessHours_Snapshot

Extension:
(this is the number for reach the application):
000BH01
Name:
(this is the name for application):
 
BusinessHours
Logic:
(this is the script for BusinessHours Application):
 
1,NoOp(Application start)
2,Set(DATAPATH=/storage/recordings.pkg/data/recordings)
3,GotoIfTime(09:00-13:00,mon-fri,*,*?8)
4,GotoIfTime(14:00-18:00,mon-fri,*,*?8)
5,Wait(2)
6,Playback(${DATAPATH}/it-business-hours)
7,Hangup()
8,Dial(Local/210@internal/n,,m)
9,Hangup();
Description of Logic Application:
 
1,NoOp (Application Start)
(do nothing, only a description for understand what application is doing)
2,Set(DATAPATH=/storage/recordings.pkg/data/recordings)
(datapath of custom play file)
3,GotoIfTime(09:00-13:00,mon-fri,*,*?8)
(Conditional Goto Based the AskoziaPBX appliance local time, if time is from 09:00 t0 13:00 from monday to friday, go to application number 8)
4,GotoIfTime(14:00-18:00,mon-fri,*,*?8)
(Conditional Goto Based the AskoziaPBX appliance local time, if time is from 14:00 t0 18:00 from monday to friday, go to application number 8)
5,Wait(2)
(Wait for some time… 2 seconds! so we are able to listen custom play file correctly).
6,Playback(${DATAPATH}/it-business-hours)
(Play it-business-hours.lsn file from DATAPATH variable, see application number 2). ATTENTION, no file extension required.
7,Hangup()
(Put down the call).
8,Dial(Local/210@internal/n,,m)
(Dial an extension, the “m” parameter is for music on hold; this could be a call group with 3 internal extension for example).
9,Hangup()
(Put down the call).
Click save

Application01_BusinessHours

In the next step, we will see how associate the BusinessHours Application with a External extension.

Tags: , , , , , , , , ,

Monday, June 29th, 2009 AskoziaPBX 1 Comment

AskoziaPBX – SoftPhone Video Tutorial

Setup SJPhone for Askozia PBXIP

Setup 3CXPhone for Askozia PBXIP

Tags: , , , , , , , , ,

Thursday, June 18th, 2009 AskoziaPBX 1 Comment
Next Entries »
 

Categories

AskoziaPBX

Create your full features PBX IP with voicemail and Automated Attendant with alix2d3 or alix2d2 system board.

You can find the PBX IP preconfigured image here:


And obtain all support information "how to" here: