I purchased an IP04 from www.rowetel.com. Had it shipped priority and had it in just over a week all the way from Australia (”aaaaaaah, Crickey!”).
I was overly anxious so I busted open the box while sitting in my car at the post office. Ah, the smell of new electronics. The thing looks just like an 8 port switch you’d buy at your local electronics emporium, but it’s not
The case it comes in is not sealed shut. This is by design. David and the good people at Atcom figure you may want to begin hacking the device immedaitely via it’s serial adapter which unfortunately can only be accessed with the top off and the modular serial adapter plugged in. Strange configuration I must admit. To keep from damaging the board and/or serial pins I would have liked to have seen the device ship with a small ribbon cable you attach to the board’s headers and then to the external 9 pin serial adapter it ships with. Maybe I’ll shoot him my suggestion. We’ll see.
Not knowing it already came preloaded with Linux and Asterisk installed I began reading on how to get it installed. After I powered it on and saw data being dumped to my terminal program did I realize, “Hey this thing is ready to use”.
Excitement Turned To Sadness
Within a few hours my excitement about having a new toy turned to sadness as I began to experience what I call, “Typical Linux Bugs”. Hold on, I love Linux but any true user and developer on any Linux platform has to admit it has its moments where you’re rubbing your temples going, “Ah, this is why it’s free.”
After installing VoipTel’s Asterisk-GUI-1.2.6-1 I began to see things like my configuration disappearing. Not believing my eyes I would uninstall the packages and reinstall them only to have it occur again.
I posted my concern to the Blackfin Koop forums but didn’t get any nibbles. I’m sure they thought I was nuts since I just subscribed and was posting a problem. Not the case. I contacted David Rowe from whom I bought it and he was beginning to see that this does appear to be a problem based on my simple use of the GUI.
I also reported the issue to Voiptel.no in hopes they can track down the issue and fix the bug. Considering this is a brand new release of the GUI only weeks old my money is that they fixed one bug but introduced an even more deadly one.
In case anyone else is having this issue here is a summary of what I had configured, packages I had installed, etc:
Installed Packages:
asterisk-spandsp - 1.4.4-1 -
busybox - 1.10.1-1 -
dropbear - 0.51-1 -
libtiff - 3.8.2-1 -
login - 1.0-1 -
oslec - 1.0-1 -
spandsp - 0.0.4-1 -
voiptel-gui - 1.2.6-1 -
voiptel-ntp - 4.1.1-1 -
voiptel-sounds - 1.0-1 -
zaptel-sport - 1.4.3-1 -
I also had one customer SIP provider configured, 2 SIP users, one Calling and Incoming Call rule. The device also has 4 FXO ports. I added Port 3 as a Service Provider, clicked on ’save’, went to Calling Rules and it told me I had no rules defined. I went back to Service Providers and my primary SIP provider was gone and so was the FXO port I just added.
I had an SSH session open to the box with the Asterisk CLI open. I thought that maybe a reboot would solve it so I initiated that from the GUI and this appeared in the Asterisk CLI:
[Oct 23 20:07:53] NOTICE[377]: chan_local.c:566 local_alloc: No such extension/context executecommand@asterisk_guitools creating local channel
[Oct 23 20:07:53] NOTICE[377]: channel.c:2942 __ast_request_and_dial: Unable to request channel Local/executecommand@asterisk_guitools
[Oct 23 20:07:53] WARNING[377]: cdr.c:760 ast_cdr_init: CDR already initialized on ‘**Unknown**’
[Oct 23 20:07:53] NOTICE[377]: cdr.c:430 check_start: CDR on channel ‘**Unknown**’ already started
The box never rebooted either. I hit the button several times and it spit this same info out each time. I had to reboot it from the SSH session. When it came back up the GUI still didn’t show anything configured other than the phones.
I pulled up my SSH session and looked in the config files and saw everything in there. Asterisk even showed my phones and my SIP peers active. Dialing in or out is dead though.
Bizarre. If anyone has a solution post it. I’m dying to get this fixed so I can finish running this through its paces in hopes of finding a use for it with a couple of my clients (replacement for a Cisco Call Manager Express install that is out of support and maintenance).



