Google Voice Setup on FreePBX and Asterisk Version 11

This past weekend I installed a fresh new FreePBX (FreePBX 2.11.0) distribution with Asterisk 11.3. The install of FreePBX and Asterisk is made simple and once installed you have a fully functioning PBX waiting for your phones and trunks to connect.

I don’t have a trunk provider at this time so I decided to use Google Voice as my solution. The process of setting this up via the FreePBX WebUI was simplified and simply works. Best of all you have this all configured and running in under 10 min’s (5 min’s if you have done this more than once).

Here are the steps I took to get this up and running.


  • Computer (I am using a VMware Virtual Machine, 1GB of RAM, 2 vCPU, 16GB HDD)
  • Latest FreePBX Distribution CD/ISO (ISO works best for me to mount in VMware ESX)
  • Google Voice Account
  • Hardware or Softphone (I have tested with XLite and CSipSimple for Android)

After you have installed FreePBX and are up and running you will need to enter the webUI (http:// pbx address). From here you do the following:

Under Connectivity

  • Select Google Voice (Motif)
  • Under Typical Settings Enter your 
  • Google Voice Username 
  • Google Voice Password
  • Google Voice Phone Number (10 digit number, no spaces or dashes)
  • Check the option to Add Trunk
  • Check the option to Add Outbound Routes
  • Check the option to Send Unanswered ‘calls’ to Google Voicemail (optional)
  • Under Advanced Setting > Google Voice Status Message (keep it short)
  • In the XMPP Priority – Leave this as it is. No need to change this
  • Click Submit, followed by applying the settings (you’ll notice it in red up at the top navigation area)

Under Applications

  • Select Extensions
  • Device: Generic SIP Device and Submit
  • Configure an extension id (example: 101)
  • Fill in the Display Name (example: jermsmit)
  • Find your way down to ‘device options’
  • In the ‘secret’ a default passphrase is give, replace this what a value of your choosing 
  • Scroll down to the bottom and Click Submit

Under Connectivity

  • Inbound Routes
  • Create a description (example: GV_GoogleVoiceNumber)
  • In DID place your 10 digit Google Voice Number
  • Scroll down to ‘Set Destination’
  • Change the value to Extension and choose the extension you created above
  • Click Submit

Lastly you want to edit your sip settings

Under Settings

  • Choose Asterisk SIP Settings
  • Change the value of NAT to ‘yes’
  • Change the IP Configuration to ‘Dynamic IP’ (in my case)
  • Under Dynamic Host, enter your hostname (keep default refresh rate)
  • Under Local Networks fill out the info pertaining to your network. You can also attempt to use the Auto Configure if so desired.
  • Under Codecs you can leave the defaults (I enabled all of them)
  • Scroll to the bottom and Click Submit Changes

At this point you should be all set to test with your SIP Client. Simple log in using the extension and secret (password). Once registered attempt to place a phone call. Open port 5060 on your firewall and you can use this to connect to your server remotely.

Did you like this post, please stop by my Facebook Page and give us a Like

How-To Add an Additional Mailbox in Outlook 2010

It’s shocking that I need to steps by step someone today on how to do this. That said I might as well share the info here. *oh and no screenshots*

Open Outlook 2010 and Click File, Info, Account Settings
Highlight the account and Click Change
Click More Settings
Click Advanced Tab then Click Add
Type in the name of additional / secondary mailbox and Click OK
Verify the new mailbox is listed. Click OK to save
Click Next
Click Finish
Click Close

PS3 YLOD Fix: How I did it

Hello PlayStation 3 Owner,

If you have run into this issue, I am aware of how frustrated you are. I’ve been there and just recently fixed mine and my brother’s PS3 (Fat Body). We both encountered this same issue.

Back-story on my issue: My PS3 ran into the Yellow Light of Death (YLOD) issue and after much troubleshooting; checking cables, powering down for days, trying again… I gave up and purchased a replacement rather than paying for a repair via Sony or some third party. My PS3 has been in a box for about 2 years or longer. Recently my brothers encountered this same issue and I quickly thought, perhaps I should experiment on my old system to see if I could fix it, and if I was successful, fix his also.

Now I have read that the PS3 YLOD is caused by either too much heat or extreme cold temperature causing the solder connections to get cracked. These conditions might also loosen the connections and now you have a PS3 with the YLOD issue. That said I attempted to preform the “blow dryer method”.

You will need the following YLOD Fix it Kit:

  • 1 small screw driver
  • 1 small flat head screw driver / or in my case finger nail
  • 1 blow dryer (borrow one from your mom, sister, girlfriend, or wife)
  • 1 towel or in my case a small blanket (such as the one my son uses for naps)

Now that you have your YLOD Fix it Kit follow these steps:

  1. Unplug your PS3 from the Power, Video (HDMI), USB attached devices
  2. On the left side of the PS3, you will find a little tab, lift it out to reveal the hard driver holder
  3. Unscrew the little blue screw in the center, then pull out the hard drive, depending on the model you may need to slid the hard drive hold to the side then pull it out. *note* place the hard drive, cover, and little blue screw someplace safe.
  4. Wrap the PS3 in a towel or blanket, cover the whole unit but expose the vents in the back. *note* turn the PS3 upside down during the process so that the bottom of the PS3 is facing up
  5. Using a blow driver on high heat, blow hot air into the back vents, go slowly side to side for approx. 15 minutes. 
  6. Remove the towel or blanket, you will notice that the bottom will be very hot. Allow the PS3 to remain upside down and cool for about 15, 20, 30 minuets. Don’t attempt to cool it faster by placing in the freezer, allow it to cool to room temp on its own. **note** there is a reason for this, and I’ll go into that later
  7. Once the cool down is complete, re-install your hard drive, screw and cover tab.
  8. Attach your Power, Video (HDMI),USB attached devices
  9. Turn your TV on and change to the proper input
  10. Finally we are at the moment of truth; power on your PS3. If all went well you will see the green light and the PS3 XMB will be disabled on your screen. You are now back in action.
***final note***
If this doesn’t work the first time around please attempt it again, in my case I only had to do this once for it to work, my brother did it two times and his is working once again.

Good Luck to you,
– Jermal

How to upgrade ESXi 5.0 to ESXi 5.1

For some of you that may not know ESXi 5.1 has been released. If you are like me running it for free at home or in the office, you may have asked yourself. How can I update my existing ESXi 5.0 installation without needing to use a CD / USB. Well my friends, it’s good you stopped by.

First thing you need to down and go on and log into your VMware account and download the ESXi 5.1 Offline Bundle (a file named While your are there you should download all other ESXi 5.1 related downloads; You’ll only need them later anyhow.

Next you need up upload the bundle to a data-store that your host has access to. This can be done via the vSphere Client or any other SCP client such as WinSCP or Filezilla FTP Client. Once uploaded to a data store you can can SSH into your host and run the following commands to update your system:

esxcli software profile install -d /vmfs/volumes/datastore1/ -p ESXi-5.1.0-799733-standard


esxcli software profile update -d /vmfs/volumes/datastore1/ -p ESXi-5.1.0-799733-standard

When done you will find yourself back at the command interface and all you need to do is type ‘reboot‘ and wait about 5 min’s for the system to go down.

Please note that you should have already powered down any and all virtual guest systems before updating to minimize on the time it takes to reboot

Additional Notes: (if you are just patching 5.0 for the use with Win8/Server12

Consider this guidance, which is based on testing Windows 8 / Windows Server 2012 up to build 8224:
  • Windows 8 Developer Preview / Windows Server 2012 Release Candidate does not boot on ESXi 5.0. To resolve this issue, you must install patch ESXi500-201112001 (Patch 02):
    1. Download and install ESXi500-201112001 (Patch 02). For more information, see VMware ESXi 5.0, Patch Release ESXi500-201112001 (2007680).
    2. Create a new virtual machine configured for either Windows 7 or Windows 2008 R2.
    3. Enable 3D graphics or do not install VMware’s WDDM video driver.
    4. Install Windows 8 / Windows Server 2012 from Media.
    5. Install VMware Tools.Note: VMware does not recommend installing VMware’s WDDM video driver. Use the default VESA driver.
  • If you experience a black screen after installing VMware’s WDDM video driver in a virtual machine with Windows 8 / Windows Server 2012, enable 3D graphics or reinstall the operating system and VMware Tools without VMware’s WDDM video driver.
  • VMware does not currently recommend using USB xHCI with Windows 8 / Windows Server 2012. To work around this issue, remove the USB xHCI controller or use the USB EHCI+UHCI controller.Note: Any changes to the virtual hardware must be preceded by a full shutdown on the command line (shutdown /s /t 0 /full). Otherwise, the Windows 8 / Windows Server 2012 hibernate-shutdown may not fully detect hardware changes and you may experience a blue diagnostic screen or triple fault at boot.
  • The vmxnet3 virtual NIC does not work in a Windows 8 / Windows Server 2012 virtual machine with ESXi 5.0. To work around this issue, use e1000e or e1000 NICs.

Show List Of Network Cards in Linux

Here is a question I got not so long ago.

Jermal, How do I go about finding the name and type of network card I have in my Linux installation?

First off, thanks for asking me. I know of a few ways and I’ll list them here. Short and simple. We have the the following commands: ip, ifconfig, lspci, dmidecode, lshw commands. Out of these I only use 3.

ifconfig and ip commands

root@websvr:~# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0c:29:f2:1f:55
 inet addr: Bcast: Mask:
 inet6 addr: fe80::20c:29ff:fef2:1f55/64 Scope:Link
 RX packets:1234097 errors:0 dropped:119 overruns:0 frame:0
 TX packets:847638 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:1000
 RX bytes:177921015 (177.9 MB) TX bytes:359121554 (359.1 MB)
 Interrupt:18 Base address:0x2024
root@websvr:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
 link/ether 00:0c:29:f2:1f:55 brd ff:ff:ff:ff:ff:ff
root@websvr:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
 inet scope host lo
 inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
 link/ether 00:0c:29:f2:1f:55 brd ff:ff:ff:ff:ff:ff
 inet brd scope global eth0
 inet6 fe80::20c:29ff:fef2:1f55/64 scope link
 valid_lft forever preferred_lft forever

lshw command is another nice one also

root@websvr:~# lshw -class network
 description: Ethernet interface
 product: 79c970 [PCnet32 LANCE]
 vendor: Hynix Semiconductor (Hyundai Electronics)
 physical id: 0
 bus info: pci@0000:02:00.0
 logical name: eth0
 version: 10
 serial: 00:0c:29:f2:1f:55
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 32 bits
 clock: 33MHz
 capabilities: bus_master rom ethernet physical logical tp 1000bt-fd
 configuration: autonegotiation=off broadcast=yes driver=vmxnet driverversion= duplex=full firmware=N/A ip= latency=64 link=yes maxlatency=255 mingnt=6 multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:18 ioport:2000(size=128) memory:dc400000-dc40ffff

And when feeling a bit fancy you could toss in the lspci command with egrep

root@websvr:~# lspci | egrep -i --color 'network|ethernet'
02:00.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)

And… that is about it. I hope this answers your question

– Jermal