Asterisk-Appliance Atcom IP04

[foschi]

Ich habe mir mal aus China von Atcom eine fertige Asterisk-Appliance IP04 gekauft, die David Rowe (Free Telephony Project) als OpenSource Hardware entwickelt hat und zusammen mit Atcom fertigt.

Die IP04 ist eine Appliance auf Basis eines BlackFin-DSPs mit uclinux und Asterisk 1.4 inkl. WebGUI, beinhaltet 4 analoge Ports (wahlweise FXS oder FXO, die hier beschriebene hat 3xFXS und 1xFXO), einen MMC-Card-Reader für die Speicherung von VoiceMail und IVR-Ansagen, einen LAN-Port und die Möglichkeit, eine serielle Konsole aufzusetzen.

Das Gerät kommt in einem nett kleinen Gehäuse inkl. europäischem Steckernetzteil und Anleitungs-CD, und sieht so aus:

Man entfernt die aufgeklebten Standfüsse und 6 Schrauben und kommt ans Innleben:

Huckepack-Module: rot=FXO, blau=FXS

Die analogen Schnittstellen sind über RJ12-Buchsen herausgeführt:

OK, das das Ding mit Linux und BlackFin arbeitet hat Atcom dann noch aufs PCB geätzt:

Geschlossen (Rückansicht, sorry wg. schlechtem Handycam-Bild) von der Rückseite sieht das Gerät dann so aus:

Die serielle Konsole ist aufsteckbar, und liegt als separates Platinchen mit in der Schachtel.

Zur Nutzung der seriellen Konsole muss man immer das Gehäuse öffnen; im aufgesteckten Zustand ist das Gehäuse nicht mehr verschliessbar.

 

[foschi]

Bootvorgang serielle Konsole

root:~> U-Boot 1.1.5 (May  5 2007 - 05:46:05)

CPU:   ADSP BF532 Rev.: 0.5
Board: IP04 IP-PBX
       http://www.rowetel.com/ucasterisk/ip04.html
Clock: VCO: 400 MHz, Core: 400 MHz, System: 133 MHz
SDRAM: 64 MB
In:    serial
Out:   serial
Err:   serial
256 MiB
DM9000#0
starting from spi flash
Hit any key to stop autoboot:  0 

Loading from device 0: NAND 256MiB 3,3V 8-bit (offset 0x0)
   Image Name:   uClinux Kernel and ext2
   Image Type:   Blackfin Linux Kernel Image (gzip compressed)
   Data Size:    4729008 Bytes =  4.5 MB
   Load Address: 00001000
   Entry Point:  00001000
Automatic boot of image at addr 0x02000000 ...
## Booting image at 02000000 ...
   Image Name:   uClinux Kernel and ext2
   Image Type:   Blackfin Linux Kernel Image (gzip compressed)
   Data Size:    4729008 Bytes =  4.5 MB
   Load Address: 00001000
   Entry Point:  00001000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
Starting Kernel at = 1000
Linux version 2.6.19.3-ADI-2007R1-bf1-svn (root@AlexHome) (gcc version 4.1.1 (ADI 07R1)) #1 Thu Sep 6 23:46:10 EDT 2007
Blackfin support (C) 2004-2006 Analog Devices, Inc.
Compiled for ADSP-BF532 Rev. 0.5
Blackfin uClinux support by http://blackfin.uclinux.org/
Processor Speed: 400 MHz core clock and 133 Mhz System Clock
Board Memory: 64MB
Kernel Managed Memory: 64MB
Memory map:
  text      = 0x00001000-0x0019205c
  init      = 0x00193000-0x001a54f4
  data      = 0x001a75b8-0x001ed4b0
  stack     = 0x001a8000-0x001aa000
  bss       = 0x001ed4b0-0x00220660
  available = 0x00220660-0x03200000
  rootfs    = 0x03200000-0x03f00000
  DMA Zone  = 0x03f00000-0x04000000
Instruction Cache Enabled
Data Cache Enabled (write-through)
Hardware Trace Enabled
Built 1 zonelists.  Total pages: 12700
Kernel command line: root=/dev/mtdblock2 rw ethaddr=00:09:45:54:20:ca ip=192.168.1.30:192.168.1.200:192.168.1.1:255.255.255.0:BF1:eth0:off
Configuring Blackfin Priority Driven Interrupts
PID hash table entries: 256 (order: 8, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Physical pages: 3200
Memory available: 48384k/63842k RAM, (73k init code, 1604k kernel code, 204k data, 1024k dma)
Blackfin Scratchpad data SRAM: 4 KB
Blackfin Instruction SRAM: 32 KB
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512
NET: Registered protocol family 16
Blackfin GPIO Controller
Blackfin DMA Controller
bf1_init(): chip_id=527A50CB,dspid=E5040005
bf1_init(): registering device resources
SCSI subsystem initialized
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
yaffs Sep  6 2007 23:42:25 Installing. 
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler cfq registered
Dynamic Power Management Controller Driver v0.1: major=10, minor = 254
Serial: Blackfin serial driver
bfin-uart.1: ttyBF0 at MMIO 0xffc00400 (irq = 21) is a BFIN-UART
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
dm9000 Ethernet Driver
eth0: dm9000 at 20100000,20100002 IRQ 48 MAC: 00:09:45:54:20:ca
BF5xx flash: probing 16-bit flash bus for cfi_probe
BF5xx flash: probing 16-bit flash bus for smt_flash
BF5xx flash: probing 16-bit flash bus for jedec_probe
uclinux[mtd]: RAM probe address=0x3200000 size=0xd00000
Creating 1 MTD partitions on "RAM":
0x00000000-0x00d00000 : "ROMfs"
uclinux[mtd]: set ROMfs:EXT2  to be root filesystem
Generic platform RAM MTD, (c) 2004 Simtec Electronics
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 649 at 0x05120000
Bad eraseblock 1189 at 0x094a0000
Creating 2 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x00000000-0x00800000 : "linux kernel"
0x00800000-0x10000000 : "file system"
mice: PS/2 mouse device common for all mice
cs_mask: 0x20, baud=0x0, flag=0x0, ctrl=0xff00, dir=0x4
Zapata Telephony Interface Registered on major 196
Zaptel Version: SVN-trunk-r1501 Echo Canceller: MG2
Code test: code function addr = 0x000f54c4
dma_alloc_init: dma_page @ 0x03009000 - 256 pages at 0x03f00000
port: 1 port_type: O
port: 2 port_type: S
port: 3 port_type: S
port: 4 port_type: S
port: 5 port_type: -
port: 6 port_type: -
port: 7 port_type: -
port: 8 port_type: -
Module 0: Installed -- AUTO FXO (FCC mode)
ProSLIC module is Si3215
reg 0: 0x3 
reg 14: 0x0 
reg 74: 0x32 
reg 80: 0x0 
reg 81: 0x0 
reg 92: 0xff 
reg 82: 0xc7 
reg 83: 0xc7 
reg 0: 0x3 
reg 14: 0x0 
reg 74: 0x32 
reg 80: 0x0 
reg 81: 0x0 
reg 92: 0xff 
reg 82: 0xc7 
reg 83: 0xc7 
Start automatic calibration
Module 1: Installed -- AUTO FXS
ProSLIC module is Si3215
reg 0: 0x3 
reg 14: 0x0 
reg 74: 0x32 
reg 80: 0x0 
reg 81: 0x0 
reg 92: 0xff 
reg 82: 0xc6 
reg 83: 0xc6 
reg 0: 0x3 
reg 14: 0x0 
reg 74: 0x32 
reg 80: 0x0 
reg 81: 0x0 
reg 92: 0xff 
reg 82: 0xc6 
reg 83: 0xc6 
Start automatic calibration
Module 2: Installed -- AUTO FXS
ProSLIC module is Si3215
reg 0: 0x3 
reg 14: 0x0 
reg 74: 0x32 
reg 80: 0x0 
reg 81: 0x0 
reg 92: 0xff 
reg 82: 0xc5 
reg 83: 0xc5 
reg 0: 0x3 
reg 14: 0x0 
reg 74: 0x32 
reg 80: 0x0 
reg 81: 0x0 
reg 92: 0xff 
reg 82: 0xc5 
reg 83: 0xc5 
Start automatic calibration
Module 3: Installed -- AUTO FXS
Found: Blackfin STAMP (8 modules)
wcfxs_init_ok = 1
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Blackfin dm9000 interrupt setup: DEMUX_GPIO irq 48
eth0: link down
IP-Config: Complete:
      device=eth0, addr=192.168.1.30, mask=255.255.255.0, gw=192.168.1.1,
     host=BF1, domain=, nis-domain=(none),
     bootserver=192.168.1.200, rootserver=192.168.1.200, rootpath=
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs: auto selecting yaffs2
block 586 is bad
block 1126 is bad
VFS: Mounted root (yaffs filesystem).
Freeing unused kernel memory: 72k freed (0x193000 - 0x1a4000)
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
devpts: called with bogus options
We already have unpacked Asterisk configuration...
rm: cannot remove '/defaults.tgz': No such file or directory
mv: cannot rename '/bin/gui_custommenus.conf': No such file or directory
Looking for host 192.43.244.18 and service ntp
host found : time.nist.gov
Registered tone zone 0 (United States / North America)
Starting Asterisk...

Welcome to:
       ____ _  _
      /  __| ||_|             _  _
 _   _| |  | | _ ____  _   _ \ \/ /
| | | | |  | || |  _ \| | | | \  /
| |_| | |__| || | | | | |_| | /  \
|  ___\____|_||_|_| |_|\____|/_/\_\
|_| IP04 Open Hardware IP-PBX

For further information see:
  http://www.rowetel.com/ucasterisk/ip04.html

Thanks to the Astfin, BlackfinOne, Asterisk and Blackfin communities.


BusyBox v1.4.1 (2007-09-06 23:55:25 EDT) Built-in shell (msh)
Enter 'help' for a list of built-in commands.

root:~>  1 Jan 00:00:13 ntpdate[51]: no server suitable for synchronization found
root:~>

 

[Thomas007]

Wie sieht es denn mit transcodieren aus?
ulaw/alaw gsm

 

[Numsi]

...sight, wenn erstmal die BRI fertig ist...

 

[foschi]

Ich denke dass es lange dauern wird bis Atcom BRI in die App einbaut, zumal das auch nicht notwendig ist (es gibt IP <-> ISDN-Gateways); ich würde die Box eh als reinen SIP-Server nutzen.

 

[netsecur]

I would like to inform you that the famous IP04 PBX developed by David Rowe and manufactured by Atcom Technologies is now finally ready for professional use.

We have dedicated almost six months to the development and testing of the IP04, and our improved firmware is now being factory installed by Atcom Technologies. As a result Voiptel has been appointed European Partner and main distributor of the IP04.

We are constantly working to improve the firmware as well as prepare new and value added applications for the IP04. Within the next two weeks we are planning to release an Operator Panel with a FREE 10 user license. This Operator Panel are currently in use by several norwegian city governments and is platform independent (runs on Windows, Mac, Unix, Linux ++). The free 10 user license will have no restrictions other than that the IP04 has to be registered with Voiptel.

For more information please visit us at www.voiptel.no

 

[mario2006]

Ich habe auch schon eine IP04 konfiguriert. Funktioniert tadellos!! Habe allerdings eine bestellt mit einem FXO Port. Habe ca. 10 Sip Clients dran. Läuft wartunfgsfrei. Kann ich empfehlen für kleinere Büros. Top!

Grüße
Mario

 

[netsecur]

...sight, wenn erstmal die BRI fertig ist...

I was talking to the guys at Atcom a few days ago, they told me they are working on the prototype now. So hopefully it is ready before summer. I will try to keep you informed...

Ich habe auch schon eine IP04 konfiguriert. Funktioniert tadellos!! Habe allerdings eine bestellt mit einem FXO Port. Habe ca. 10 Sip Clients dran. Läuft wartunfgsfrei. Kann ich empfehlen für kleinere Büros. Top!

Hi, if any of you like to try our updated GUI, send me a message through our website and I'll provide the link as well as instructions.

Edit Guard-X: Beiträge zusammengeführt!

 

[mario2006]

Hi netsecur,

what I need is, how to setup a VPN on uClinux. I read a lot of things in the forums and was not able to set it up.

Cheers
Mario

 

[netsecur]

Hi netsecur,

what I need is, how to setup a VPN on uClinux. I read a lot of things in the forums and was not able to set it up.

Cheers
Mario

Hi, Mario
we have always terminated the VPN tunnel on either the router or a VPN consentrator. One of the reasons for this is to avoid the extra burden on the CPU. We are planning to do some experiments with one of our IP08 units regarding it's potential as a gateway, and during these experiments we might take a closer look at the possibilities of using it as a VPN server at the same time monitoring the effect on the CPU. Will post the result on our site when the tests are concluded.

Best regards

Jan

 

[mario2006]

Hi Jan,

this would be fine.

Cheers
Mario

 

[netsecur]

Just wanted to share this with you and the others at the forum.

http://www.rowetel.com/ucasterisk/index.html#newnews

http://blackfin.uclinux.org/gf/proj...rum_action=ForumMessageBrowse&thread_id=27018

http://blog.astfin.org/

We have a demo unit online at the moment, just contact me if any of you would like to take a look.

 

[netsecur]

Progress on the BRI PBX!

...sight, wenn erstmal die BRI fertig ist...

Check out this post at http://blog.astfin.org/ . Mark has received the first prototype manufactured by Atcom, shouldn't take too long before it become available. We will do our best to have a version of the VoIPtel GUI waiting when they get ready to ship.

 

[foschi]

@netsecur: Thank you for your information regarding the IP04/08/BRI. Please do keep in mind that we are not particularly interested in any "business opportunities" companies offer - this is supposed to be a vendor neutral forum.

Any product details or technical information is always welcome.

 

[netsecur]

Ip04/08/bri

I appreciate the fact that this forum is not a place for marketing. It is true that we are Atcom's main distributor in Europe, but normally we only sell via our network of retailers. That's why I can assure you that my posts is for informational purpose only. Our VoIPtel GUI is open source and available to everybody regardless of where they have obtained their IP04/IP08. We are currently working directly with both David Rowe and Mark of astfin.org in order to integrate our GUI with both systems.

 

[mark_astfin_org]

@netsecur: Thank you for your information regarding the IP04/08/BRI. Please do keep in mind that we are not particularly interested in any "business opportunities" companies offer - this is supposed to be a vendor neutral forum.

Any product details or technical information is always welcome.

Well, I am sure that you would be interested in the fact that I already made a first call
Please look at this post to see details about the "bring-up" process
http://blog.astfin.org/?p=52
http://blog.astfin.org/?p=55
Any feedback/suggestions would be greatly appreciated.
Cheers,
Mark

 

[mark_astfin_org]

Finally, the product is ready for a prime time :dance:

We've experienced several delays due to case related issues (?) and such, nothing really related to electronics / software, so it took a little longer than we originally anticipated.
As usual, you will be able to find raw schematics on our forum and software is obviously 100% open.
For the management, we are using slightly modified version of Asterisk GUI ver 2.0, with fully working support for ISDN-2.

For more details please visit my blog.

Cheers,
Mark

 

[michaelxy]

Und kostet ?