So far, this looks like it is going to be a decent little unit for what I want it to do.
Configuration through the web UI wasn’t a problem. I set up an account on the TG100 and configured my asterisk box to register to it. Once registered – both originating and terminating calls worked properly. I didn’t talk to myself long enough to judge call quality or to see if doing anything in the UI or on the device would load it up enough to impact call quality. Also did not try call waiting, multiple channels, or to see if any voicemail indications were passed through.
SMS didn’t work properly for me with the as-shipped firmware – they showed up in the UI looking corrupted. They have worked properly with the newest firmware (220.127.116.11 released 2014-05-15). It looks like you will either have to use the web interface, or code your own interface to the API to work with SMS messages. I did try sending an SMS while a voice conversation was active. It didn’t send the message until the voice call was over.
Having not used them very much, and it’s not likely the prepaid service I am using supports them anyhow – I didn’t try any MMS messages.
Their API for sending/receiving SMS messages uses the Asterisk Manager interface – with a couple tweaks to the manager permissions there is a lot of potential. With a root shell provided, those tweaks can probably be made.
Network services, OS
Plugged into my LAN switch. The default IP (192.168.5.150) and login/password (admin/password) are printed on the label. Instead of rejiggering my network, I just did:
ifconfig eth0:1 192.168.5.1
And for good measure:
nmap -sSV -p1-65535 192.168.5.150
Starting Nmap 5.00 ( http://nmap.org ) at 2014-05-31 21:14 MDT Interesting ports on 192.168.5.150: Not shown: 65532 closed ports PORT STATE SERVICE VERSION 80/tcp open http Boa HTTPd 0.94.14rc21 514/tcp open shell? 5038/tcp open asterisk Asterisk Call Manager 1.1
Connecting to the web interface, it gives a nice popup “Security Advice: Please change the password on the first login.” That’s good of them to do. Tried turning on SSH, it became unresponsive after saving the setting and telling it to apply the change (maybe it was still reeling from nmap). Power cycle – nothing. Hold down the reset button for a while – rebooted and back online.
Try it again – success!
ssh in, turns out this little guy is actually running asterisk 18.104.22.168! I might be able to replace my current asterisk server with this – except that I have some inkling to try out connecting asterisk to my mobile and there is no bluetooth transceiver and no USB port to plug one in.
root@TG100:/etc/asterisk# rasterisk -x "core show version" Setting max files open to 2048 Asterisk 22.214.171.124 built by root @ lzwyeastar on a i686 running Linux on 2014-02-20 07:46:16 UTCroot@TG100:/etc/asterisk# netstat -pnl Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:514 0.0.0.0:* LISTEN 1100/inetd tcp 0 0 0.0.0.0:5038 0.0.0.0:* LISTEN 1276/asterisk tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1271/boa tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 1100/inetd tcp 0 0 0.0.0.0:8022 0.0.0.0:* LISTEN 1100/inetd udp 0 0 192.168.5.150:123 0.0.0.0:* 1383/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 1383/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 1383/ntpd udp 0 0 0.0.0.0:5060 0.0.0.0:* 1276/asterisk udp 0 0 0.0.0.0:4569 0.0.0.0:* 1276/asterisk Active UNIX domain sockets (only servers) Proto RefCnt Flags Type State I-Node PID/Program name Path unix 2 [ ACC ] STREAM LISTENING 2178 1276/asterisk /var/run/asterisk/asterisk.ctl root@TG100:/persistent# uname -a Linux TG100 3.2.0 #129 Fri Oct 25 14:39:37 CST 2013 armv7l GNU/Linux
Got excited and took it apart
I like the nice heavy case. Not sure what to take away from the components – but here they are.
Cracked out the Kill-A-Watt meter. Plugged in, no SIM card, no ethernet – pulling 2W. With ethernet and GSM registered – 2.2-2.5W. The highest I’ve seen while running has been maybe 2.7W, it’s been up for a little while now – Kill-A-Watt shows 40 hours 15 minutes, 0.08 kWH which works out to roughly 2W average continuous draw.
Corrupted SMS and upgrading firmware
The account validation SMS message from speakout showed up looking corrupted. This unit came with firmware 126.96.36.199, and looking at the release notes for the newest firmware 188.8.131.52 shows a couple maybe relevant bug fixes:
3. Fixed the issue that SMS sent out would have messy codes at the end of the original message if the SMS has more than 70 characters, containing Chinese characters and numbers or Chinese characters and English characters. 5. Fixed the issue that the spam messages from China Mobile would be shown as gibberish on NeoGate TG "Inbox" page.
Upgrading the firmware went smoothly. I already had a TFTP server running (which primarily serves configuration to my Polycom IP550), so I used that option to upload the firmware.
Re-try the validation SMS: Success! No more corrupted messages.