system toolbox » voip

Hardware
ADSP-BF537 600MHz CPU
64MB SDRAM
1 Ethernet port with high performance PHY
Quad BRI based on Cologne silicon
SD card interface with a dedicated bus
256MB flash for voicemail and prompts.
Optional, hardware based echo cancellation.
Astifn with Asterisk 1.4.x, mISDN

Features
Interfaces & protocols: IAX, SIP, ISDN-2, H323
Codecs: a-law, u-law, Speex, GSM.
Monitor active channels & calls
Voicemail, Voicemail to e-mail
IVR menu's
Conference bridges
Follow-me
Music on Hold
Timebased rules
Call parking and transfer
Backup options
Firmware update thru the webGUI

sve ovo Price: 395.00 EUR ??!

može se kupiti preko paypal-a

Description     Unit Price     Quantity     Amount     
BR4 - Appliance
    €395.00     1     €395.00     
    Item total:     €395.00     
Shipping and handling:     €78.42     
Total:     €473.42     EUR

BR4 - Appliance

Total with Shipping:€473.42EUR
Click to view purchase details

LEC-64-BR4

Hardware based Line Echo Canceller.
Fully compliant to ITU-T G.165, G.168 (2000) and (2002) specification.
Passed all AT&T voice quality tests for carrier grade echo canceller systems.
Sub 50ms initial convergence times under many typical network conditions
Fast reconvergence on echo path changes
8 channels @ 64ms

120 EUR

Description     Unit Price     Quantity     Amount     
BR4 - Appliance
    €395.00     1     €395.00     
LEC-64-BR4
    €120.00     1     €120.00     
    Item total:     €515.00     
Shipping and handling:     €56.91     
2 Items, Total:     €571.91     EUR

kod ovih je mani shipping ako je više robe

AstLinux - Introduction

AstLinux is a custom Linux distribution centered around Asterisk, the Open Source PBX. Although Asterisk remains the core focus, other VoIP applications such as OpenSIPS and FreeSWITCH are also available. AstLinux has many features that make it ideal for embedded and commercial Asterisk based solutions.

• Linux kernel 2.6
• dnsmasq
• watchdog (busybox)
• ssmtp
• cron (busybox)
• bash
• busybox (and everything with it...)
• TFTP server
• vsftpd server
• mini_httpd (with SSL)
• PHP in CGI mode (patched for above)
• OpenSSH
• OpenSSL
• NTP (ntpdate, ntpq, ntpd)
• syslog (busybox with remote log support)
• vi (from busybox)
• tc (kernel traffic shaping)
• iptables
• phpconfig-like Asterisk GUI
• Asterisk
• AstShape (QoS/traffic shaping script)
• rsync
• nfs-utils (kernel modules and userspace tools for NFS support)
• Sangoma WanPIPE (for use with A101 / 102 / 104 /S518)
• Zaptel
• working ztdummy (zaptel timing source without zaptel hardware)
• libpri
• Asterisk Manager Proxy
• exec.php from m0n0wall
• and many, many more (download to find out!)

The AstLinux Development Environment (ADE)¶

ADE is based off of the excellent builroot2 build system. It uses Kconfig to provide various preconfigured options to the user in an ncurses-based menu environment (provided by Kconfig). Next we will copy the default AstLinux config file and look for any new configure options. Whenever software packages are changed or added the default config needs to be updated. Sometimes the developers don't do that.

Copy the default config file:

cp astlinux.config .config

Check for new configure options:

make oldconfig

If you get "make: command not found" or a similar error you will need to install some development tools before you can continue. On Debian based systems this is quite easy. The "build-essential" package provides most of what you need. On RedHat based systems you can start by installing make with yum. The AstLinux Development Environment includes a script that will check for the various packages required for building. It will help you as it goes along.

If this is your first time compiling AstLinux I suggest that you don't make any changes to the default AstLinux configuration. This will make it easier to troubleshoot any problems you might have. Now it's time to run make:

make

The AstLinux Development Environment requires a lot of disk space, bandwidth and CPU time. If this is a shared user system I recommend that you run make with nice to prevent the ADE from dominating your system's processor:

nice -n21 make

The ADE can take a long time to compile. If you'd like to benchmark your system you can run it with time:

time make

or:

time nice -n21 make

The ADE can take anywhere from 10s of minutes to several hours (or even days) to compile, depending on the speed of your system and internet connection.

After building the complete system the first time, you can modify the package selections by issuing the following command prior to make.

make menuconfig

The default options will create an ISO image as well as the runnix image files. The ISO image will be called astlinux.iso. The runnix files will be placed in <astlinux-root>/astlinux-<version>-<svn#> where <version> is either trunk or 0.6 and <svn#> is the current SVN revision that you have checked out.

What is Runnix?¶

Runnix is a new boot loader system which will be used on Astlinux 0.5.0 and greater.

Runnix is a kexec/syslinux based loader for booting linux systems. It supports a wide range of unique features and can be easily customized and extended. Automatic updates (even over a network), image verification, and failover are all supported.

Runnix uses syslinux to load a basic linux environment which can do several things, but eventually loads the target operating system.

Why Runnix?

• Never have to remove the Compact Flash card to load new images, just add them to the 'os' directory.
• Very flexible design allows you to store multiple images in the 'os' directory, then specify which version to load using the 'ver' file.
• Ability to load new images under Windows since the os itself is stored on a FAT16 partition
• Makes it easier to keep the 'key disk' and unionfs partitions on the same device as the os without worrying about removing either when replacing the Astlinux version currently installed. (the old process involved writing out the image using 'dd' which did replace the partition image on the CF and would likely remove the key disk if it was stored on the same CF

Installing Astlinux with the Runnix boot loader

Astlinux 0.6.x and later include runnix in the img files. Download the appropriate file from the Source Forge page and follow the Astlinux install instructions.

Raw Install (not recommended)

If you wanted to experiment with the runnix configuration and get into the nitty gritty details

Download Runnix from http://sourceforge.net/projects/runnix/ . Extract the files into a temporary location on your development system's hard drive.

Create a fat 16 filesystem on the target device. Usually this will be a compact flash device, but this can also be a full blown hard drive.

fdisk -l /dev/yourdrive

verify that your filesystem Id is 6 and the System is FAT16 and that the first partition is bootable. You'll probably want to modify your drive to create two partitions on the same device (although it's still possible to use a separate device for your keydisk)

fdisk /dev/yourdrive

Delete any existing partitions

Create a new boot partitions which will contain the runnix bootloader and the Astlinux image(s). A typical size for this parition is 128MB which would be enough to hold multiple versions of Astlinux. As mentioned above this partition should be FAT16 (Filesystem type 6 in Linux fdisk) and must be bootable.

Next create a linux partition that uses the rest of the space on the drive. This will be your keydisk.

Save your changes in fdisk by using w to write the changes to disk.

Format your newly created partition.

mkdosfs -F 16 /dev/yourdrive1

Next install syslinux onto it

cd runnix-<version>

./syslinux /dev/yourdrive1

cat mbr.bin > /dev/yourdrive

Finally copy the runnix files to your prepared drive

mount -t vfat /dev/yourdrive1 /some/mount/point

cp -R rootfs_vfat/* /some/mount/point

Now what? Let's take a look inside the runnix files.

cd /some/mount/point

ls -lah

-rwxr-xr-x 1 root root 38 Aug 15 07:18 boot.msg

-r-xr-xr-x 1 root root 9.8K Aug 15 07:14 ldlinux.sys

drwxr-xr-x 2 root root 4.0K Aug 15 07:18 os

-rwxr-xr-x 1 root root 1.7M Aug 15 07:18 runnix

-rwxr-xr-x 1 root root 1.6K Aug 15 07:18 runnix.conf.sample

-rwxr-xr-x 1 root root 897K Aug 15 07:18 runnix.img

-rwxr-xr-x 1 root root 197 Aug 15 07:18 syslinux.cfg

runnix.img is the initrd file

runnix is the kernel

syslinux.cfg defines how runnix starts.

os is the directory where your target operating system images go. At a minimum you'll need an <image>.run file and the associated <image>.run.sha1 file which will be used to validate the image and the initrd file.

astfin <> astlinux - astfin koristi blackfin CPU¶

uh ja sam skroz pomješao, ovaj uređaj ne koristi astlinux nego astfin

Astfin: Complete uClinux distribution for Blackfin CPU with integrated Asterisk and support for several open hardware line interface boards.

Updating astfin uImage

Please note that astfin2 trunk rev 1200+ supports uIMage update through the web based GUI. User will also have options to reset to factory default or to keep asterisk and network config files.

I will use br4-appliance as an example;

Checkout the applicable branch from Astfin’s svn

svn co https://astfin.svn.sourceforge.net/svnroot/astfin/software/astfin/trunk/ astfin

cd astfin

Select your hardware and related options
make menuconfig

Select BR4 as your target

make
make image

Copy your new uImage from your image_ folder to your tftp folder, usually tftpboot
cp image_br4 /tftpboot/uImage-br4

Now, boot your BR4 and hit any key during the countdown sequence to get to the uboot prompt BR4>

At this point, we will modify few values
setenv ipaddr 104.25.13.88
where 104.25.13.88 is an IP address which you wish to assign to this box

setenv gatewayip 104.25.13.1
where 104.25.13.1 is an IP address of a default gateway of your network

setenv serverip 104.25.13.5
where 104.25.13.5 is an IP address of your tftpserver

Now we need to download the image from the tftpserver
BR4> tftp 2000000 uImage-br4

You should see it being download, please record the image size (bold)
BR4>tftp 2000000 uImage-br4

id: 0x90000a46
MAC: 00:16:d3:2a:c5:b7
device TFTP from server 104.225.213.5;
our IP address is 104.225.213.84
Filename 'uImage-br4'. Load address: 0x2000000
Loading: #################################################################
...
################################################################# ################################################################# 
done Bytes transferred = 4576223 (45d3df hex)

BR4>

Now, we need to erase your NAND flash in preparation for a new image.
To do that we will execute the following commands from your u-boot prompt

BR4>nand erase clean
BR4x>nand erase

At this point we are ready to copy our image from memory location 0×2000000 into the beginning of your NAND.
BR4>nand write 0x2000000 0x0 0x460000

where 0×2000000 is the starting memory address where we saved our uImage 0×0 is the offset ( 0×0 means beginning of the flash) 0×460000 is the sizef of uImage.

In the next step, we need to modify the last portion of the u-boot environment and specify the size of the new image for “spiboot” variable
BR4>setenv spiboot 'nand read.jffs2 0x2000000 0x0 0x460000; run addnet; bootm 0x2000000'

So, basically we are saying: read from NAND (file system jffs2) at offset 0 (beginning) the first 0×460000 bytes and save it to memory address 0×2000000; then execute addnet micro then boot from the memory location 0×2000000 (so form where you just saved your kernel and file system image)

Now, very important, you need to save your environment.
BR4>save

Well, you are done, so reboot and watch it fly ;)

BR4>reset
Please note that you can also use our GUI to update firmware on your boxes.

Enjoy Mark

...

soekris embedded pc boards¶

astlinux se pominje u kombinaciji sa ovim soekris one-board kompjuterima

Soekris Engineering net5501

This compact, low-power, low-cost, advanced communication computer is based on an up to 500 Mhz 586 class processor. It has four 10/100 Mbit ethernet ports, up to 512 Mbyte DDR-SDRAM main memory and uses a CompactFlash module for program and data storage. It can be expanded using a MiniPCI type III board, a hard drive and one or two low-power standard PCI board.

It has been optimized for use as a Firewall, VPN Router, Internet Gateway and VoIP PBX, but has the flexibility to take on a whole range of different functions as a communication appliance. The board is designed for long life and low power.

It is available in any volume in the standard version, and as board only or with a small metal box and various power supplies. The board can be customized according to requirements when ordering higher volume.

With an HDD mounting kit you can install a 2.5" HDD on top of the board.

Click on the pictures at right for high resolution versions.

Standard stock configurations:

net5501-60: 433 Mhz CPU, 256 Mbyte DDR-SDRAM, 4 Ethernet, 2 Serial, USB connector, CF socket, 44 pins IDE connector, SATA connector, 1 Mini-PCI socket, 3.3V PCI connector.

net5501-70: 500 Mhz CPU, 512 Mbyte DDR-SDRAM, 4 Ethernet, 2 Serial, USB connector, CF socket, 44 pins IDE connector, SATA connector, 1 Mini-PCI socket, 3.3V PCI connector.

• 433 to 500 Mhz AMD Geode LX single chip processor with CS5536 companion chip
• 128-512 Mbyte DDR-SDRAM, soldered on board
• 4 Mbit BIOS/BOOT Flash
• CompactFLASH Type I/II socket.
• UltraDMA-100 interface with 44 pins connector for 2.5" Hard Drive
• Serial ATA 1.0 interface for Hard Drive, with +5V and +12V power header
• 1-4 VIA VT6105M 10/100 Mbit Auto MDIX Ethernet ports, RJ-45, protected to 700W/40A Surge
• 2 Serial ports, DB9 and 10 pins internal header
• USB 2.0 interface, one internal, one external port
• Power LED, Disk LED, Error LED, Network LED's
• Mini-PCI type III socket. (for t.ex. hardware encryption or wireless controller)
• PCI Slot, right angle 3.3V signaling only, dual PCI slot option
• 12 bit general purpose I/O, 20 pins header
• Temperature and voltage monitor
• Hardware watchdog
• Board size 6.3" x 6.5"
• Power using external power supply is 6-25V DC, max 20 Watt, protected with TVS
• Option for 5V supply using internal connector
• Operating temperature 0-60 °C

• Standard case with 1 PCI slot, 6.7" x 11.5" x 1.3".
• 1U 19" rackmount with with 2 PCI slots (available Q2 2009).

• comBIOS for full headless operation over serial port
• PXE boot rom for diskless booting
• Designed for FreeBSD, NetBSD, OpenBSD and Linux
• Runs most realtime operating systems

cijena na euro shop-u je 265 EUR, bez troškova transporta

pcengines embedded pc¶

pominje se podrška i ovim pločama pc engines

recimo jedna ploča je:

Part numbers     alix2d2 = 2 LAN / 2 miniPCI / LX800 / 256 MB / USB
Spec     
• CPU: 500 MHz AMD Geode LX800
• DRAM: 256 MB DDR DRAM
• Storage: CompactFlash socket, 44 pin IDE header
• Power: DC jack or passive POE, min. 7V to max. 20V
• Three front panel LEDs, pushbutton
• Expansion: 2 miniPCI slots, LPC bus
• Connectivity: 2 Ethernet channels (Via VT6105M 10/100)
• I/O: DB9 serial port, dual USB port
• Board size: 6 x 6" (152.4 x 152.4 mm) - same as WRAP.1E
• Firmware: tinyBIOS

i sve je to nekih < 90 EUR

pc engines cjenovnik

astlinux vs astfin2¶

astfin se se build-a na uClinux-u, dok astfin na "standardnom" linux-u, kako sam skontao. Astlinux je najviše orjentisan na x86 kompatibilne procesore( gornji primjei su AMD Geode procesori i VIA procesori, koji su, koliko znam x86 procesori). Astfin je opet isključivo embedded distribucija

tako recimo asteriks koji se koristi je uCasterisk - asterisk prilagođen za build na uClinux-u

http://svn.astfin.org/software/uCasterisk/trunk/README.txt

uCasterisk README
=================

Introduction
------------

uCasterisk (you-see-Asterisk) is a set of scripts, makefiles and
patches to build Asterisk for uClinux. The target is the Blackfin
BF533 STAMP board, although it should be portable to other uClinux
platforms.

uCasterisk in one part of a project to build a completely open
telephony platform. Both the hardware and the software are freely
available under the GPL.

For more information please see:

  http://www.rowetel.com/ucasterisk/ucasterisk.html

How to Build uCasterisk
-----------------------

1/ Configuration:

  http://www.rowetel.com/ucasterisk/ucasterisk.html#configuration

2/ Building:

  http://www.rowetel.com/ucasterisk/ucasterisk.html#building

sa git-svn pokupio repos-e

hernad@nmraka-5:~/devel/git$ git svn clone https://astfin.svn.sourceforge.net/svnroot/astfin/software/astfin/astfin2/trunk astfin2

Checked out HEAD:
  https://astfin.svn.sourceforge.net/svnroot/astfin/software/astfin/astfin2/trunk r1461

hernad@nmraka-5:~/devel/git$ git svn clone https://astlinux.svn.sourceforge.net/svnroot/astlinux/trunk astlinux

  https://astlinux.svn.sourceforge.net/svnroot/astlinux/trunk r2610

How To: Building an Embedded Asterisk PBX

Michael Graves
January 13, 2006

Introduction

Astlinux is a bundled distribution of the Asterisk open source iPBX private branch exchange (PBX) software and a Linux operating system. Originally developed by Mark Spencer at Digium, Asterisk is the leading open source software in the telephony/VoIP space. Asterisk excels at combining traditional TDM telephony capability - provided through hardware from Digium and others - with VOIP services. These include call routing, media gateway, media server and SIP signaling capabilities.

The Asterisk user community has been growing tremendously over the past two years, especially since the v1.0 release in the fall of 2004. With that growth has come the development of new distributions that bundle suites of software tools, to ease the setup and administration of a new Asterisk system. Asterisk@Home and Xorcom Rapid are both fine examples of this sort of activity.

Astlinux was developed by Kristian Kielhofner, and intended to go in a fundamentally different direction. Astlinux provides an Asterisk installation on a Linux distribution that has been built from scratch and optimized for small format hardware platforms - it takes what is essentially an embedded systems approach to Linux and Asterisk. In this article, I'll show you how to build an VoIP PBX using Astlinux and a Soekris Net4801 single board computer (SBC).

...