Yesterday I received another Intel DN2820FYKH NUC computer.
I had ordered another one with the intent of running a Mythtv Backend and Frontend using a Realtek USB tuner.
I’ve installed Mythbuntu and got everything working, however I really like using Debian itself, and will look at doing a more custom install with Debian. So the plan is work on a Debian 7.7.0 x64 install.
I’ve configured this new Intel NUC with the usual 8GB ram (max it can take) and Dual Band 802.11ac wireless (as it’s only a $24 upgrade to buy the card), and I had a spare 500GB laptop drive, which I installed too.
Will be sure to post more about my progress regarding the Debian installation and tweaking it all.
Thought I’d do a follow up post on our Intel NUC (Model: DN2820FYKH).
The little machine is running fine and has only had one software crash since we started to use it. It is turned on 24/7 and gets used everyday. At the moment it has an uptime of 44days or so.
Still very impressed by the machine in day to day use. It does exactly what we need it to do with minimal footprint on a desktop.
Would certainly buy one of them again. Really do want an i3 or i5 based model some day.
The talk of the past year in hardware has been the Intel NUC, and I’ve been wanting to get my hand on one for the last few months, since the Third Generation module was released.
In the end I decided to purchase an Intel Celeron based one (Model: DN2820FYKH) and to load it up to run Windows 8.1 Pro.
For more detailed information about the specification, hint up the link here.
The Celeron model has some notiable differences (lacking features) between the i3 and i5 based models.
- Only one memory socket (max 8GB ram) (vs i3/5 16GB max in 2 sockets).
- Ships with wireless (vs i3/5 not shipping with it).
- No MSATA support, as the socket for it don’t exist.
Despite this lack of feature between it’s more powerful siblings, I figured that Windows 8.1 Pro on a machine where you can install 8GB ram and a 2.5″ Laptop SSD drive would be adequate for the footprint.
Sure enough, it runs very well. Reasonable and capable little computer. I paired mine with a powered USB hub and a 19″ monitor I had spare.
As per my previous posts, I use MyNetFone as my SIP provider and I run a Raspberry Pi with RasPBX (which is FreePBX for the Raspberry Pi ready to install/tweak and configure).
Below is a quick run down on how you can configure your SIP Trunk for MyNetFone on this device, which is working for me currently.
Trunk Name: mynetfone
Outbound CallerID: [configure based on your 09nnnn number or your DID if you have one]
Trunk Name: mynetfone-sip-out
Peer Details: (as below)
Last week, on a Friday night of all things. Decided I would give RasPBX another go. After spending a bit of time on it had managed to configure my DID, my extension and setup inbound routes.
I configured enough to be able to leave it running until I can configure the other features I was using on my more manual setup. Which includes time based rules and IVR. Will get to those items in the next few days.
Will do another post shortly that shows how I got my SIP provider (MyNetFone) setup via the Trunks.
I’ve had my Raspberry Pi and Asterisk setup running now for nearly 2 months. It hasn’t failed me once in this time.
If you remember back I ended up installing Raspbian and configuring Asterisk manually from command line. This setup suits me, as I want to learn about how it all works, not learn how to use one of the dedicated images that has a fancy web GUI (and learn how to use that). I might end up changing to that type of setup eventually, however what i have now works with all the features I need.
Will be sure to post back as time progresses with this setup.
I’d really love to get my USB based tuner to work on my Raspberry Pi for use with TvHeadEnd. My tuner as seen via lsusb output is below..
Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Anyone had any luck getting this to work with TvHeadEnd? If so add something in the comments.
Following from my other post here, I’ve managed to finally secure a cable I needed to hook up my USB DVB-T tuner to an outside antenna. I’ve subsequently configured my Raspberry Pi as per the forum post here with the required software.
Basically I have enabled SDR (Software Defined Radio) and using it to decode paging messages on the paging network.
I setup the tuner on Windows at first and used SDR# to find the frequency range. A friend told me roughly where to look and what to listen out for. He said you’d hear bursts every so often. Sure enough I did. I found based on my location in South West Sydney that 148.630 was the band that enabled me to get what I needed.
If you get it working, you will see output like so from the command line below;
rtl_fm -f 148.630M -s 22050 | multimon-ng -t raw -a POCSAG512 -a POCSAG1200 -a POCSAG2400 -f alpha /dev/stdin
POCSAG1200-: Alpha: 1957499:XMPROD PET_SYD_WATER_2 Regular heartbeat 1 to VHA
It appears that the paging network is still very much used by many. From looking at what comes over it, you can see that the medical industry uses it, in addition to other corporations for notifications etc.
I should add I found the following page helpful too. Click here.
Have completed my Ubuntu 12.04.2 LTS install and configured lxc (Linux Containers). I am so far very impressed just how easy it was to get this working out of the box. I think the Ubuntu team who produce Ubuntu 12.04.2 LTS has to be given a big clap. Very fine job.
I’ve install some Debian squeeze lxc’s and Ubuntu ones. All seem to work great and I will post more details soon on what I have done and how it was performed, as it might help anyone thinking of doing the same.
I wanted to do this so I could run some other software on the containers and not clutter the host install. Although the host will see the processors for the container etc. But that’s fine and expected on how lxc works.
My aim was to install Mythtv as a master backend into a container and have it use my HDHomerun network based tuner. This has actually worked, and I am currently running it now, however I noticed during reboot/auto start of the container that the mythtv-backend wouldn’t start. Turns out the upstart configuration is not going to work on a linux container. Wiki page here is the link to the config that ships in Ubuntu 12.04.2, and below is my change I made so that I could get it to start automatically, it’s a hack and needs some further investigation, but I was in a rush to get it working in my environment.
root@delta:~# cd /etc/init
root@delta:/etc/init# cat mythtv-backend.conf | grep start
#start on (local-filesystems and net-device-up IFACE!=lo and started udev-finish)
start on net-device-up IFACE!=lo
As per above, I hash out the original start on line and create the amended one below it. This is perform in the file /etc/init/mythtv-backend.conf
Now it will start correctly in my container at boot.
I did my research and determined that if I wanted WiFi on my Raspberry Pi I should stick to a model that can also run in Access Point mode for hacking around with, and sure enough I settled on a Realtek RTL8188CUS chipset one.
If anyone is interested, I purchased mine from this ebay seller here. This is a direct link to the one I actually got, in fact I bought two since they were cheap and I do have two Raspberry Pi’s after all.
I am using the blog post here, to determine if I can get it to do something. So far so good, see the output below;
michaelf@tom ~ $ dmesg | grep rtl
[ 6.792640] usbcore: registered new interface driver rtl8192cu
michaelf@tom ~ $ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 005: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
I followed the post and sure enough it works. if you want your RPi to still use a static IP with the br0 interface you can use the sample one below.
iface lo inet loopback
iface br0 inet static
bridge_ports eth0 wlan0
iface eth0 inet manual
iface wlan0 inet manual
If you want to setup the WiFi adaptor in client mode, you can follow the information on this post here. Which I can confirm works, as I got it working with my adapter.
Purchased a humble Linksys/Cisco IP phone SPA922 and installed it earlier in the week. However wasn’t able to use it until the power brick I ordered arrived. It came later in the week.
Been a long time since I installed asterisk, but I have fond memories that it was very awesome once you got it working. I struggled a little, but somethings were easy and others not so. Thanks to a friend who helped I managed to configure everything I needed and even got it to talk to my provider MyNetFone which I purchased a DID from to use from Sydney 02 region.
After tinkering Friday evening I got the inbound working and outbound working. My next step was to get IVR working on the inbound calls. I got this done on Saturday morning and evening.
Very happy with the setup so far, have subsequently copied over my configuration and voice files onto a Raspberry Pi where I have setup raspbian and installed asterisk. I choose to run it like this as I found the pabx based distro with the nice web interface confusing. What I have got works, and works well so far more me. Will continue to work/tweak it.
So far so good and very impressed.
Purchased 2 new Model B Raspberry Pi’s. The model now that has 512Mb ram. Plan is to use one for some SDR stuff and the other looks like might end up being used for Asterisk, as I am getting a Linksys desktop VoIP phone configured with it. Looking to setup a DID with a provider and do some testing against it.
Purchased a single unit first and after testing for a week found the new models to be very good, so purchased a 2nd unit this week.
I purchased a Raspberry Pi – Model B – 512Mb version to have a tinker with. As I noticed this model came out at some point.
I previously had some 256mb models and they ran pretty well however had a few limitations with them which affected what I needed to use them for. It appears so far the newer 512Mb model hasn’t had those issues so far. The problem I had was during reboot from command line the unit would hang during post and/or hang randomly.
I am going to check out OpenELEC again and see how much it has improved, in addition I have ordered a DVB usb tuner  that is being used for SDR. As I want to run some of that off the Raspberry Pi (RPi) to see how well it performs. Will post more about this soon, once all my hardware arrives.
 – Element 14 – Raspberry Pi – Model B – 512Mb cased.
 – Ebay – RTL2832U & R820T DVB-T RTL-SDR+DAB+FM USB Digital TV Tuner Receiver.
It would appear that one of the two Ubiquiti NanoStation Loco M2’s that I purchased has suffered a fault.
I reset it to factory defaults and upon it restarting I noticed that I could only get a ping of about 4-5 packets every 60 or so seconds. It never stayed up long enough for me to get back onto the web interface to configure it again.
Attempted a recovery using tftp etc and got it to accept the firmware via tftp, at which point it reboots post the loading. Once again goes into the same condition. I’ve now submitted it for RMA and will set about sending it back.
Not really my luck with hardware sometimes.
Looks like the Open Media Vault appliance I had running via the HP N40L Microserver had some issues.
I left it overnight to copy 400+Gb of files and woke to find it had failed half way. Host was up, but networking wasn’t working quite so well. Rebooted and immediately saw the root file system failed to mount and caused the usual panic.
I suspect the USB key I had the OS installed on has corrupted. Which means my data should be okay, although hasn’t impressed me much.
Think I will go back to my Debian install and just do everything via it. So it’s not an appliance, but at least I know it will work day in and day out when ran from the hard drive.