Skip to main content

Using VoIP with SmoothWall

I’ve been playing with SmoothWall Express (Polar) recently and am generally pretty impressed.  However, my Linksys SPA921 IP Phone hadn’t been working.  I decided to turn my attention to it today.

The phone wouldn’t give a dial tone at all unless I used the “SIP Proxy” option in SmoothWall, however, that wouldn’t allow any outgoing calls.  I tried creating various exceptions in the firewall, even setting the phone to be an “always allowed machine”, all to no avail.

Then I hit on the solution… I had a BT ADSL router connecting to the internet performing NAT, the SmoothWall connected to this performing NAT, and the IP Phone connecting to the SmoothWall as shown in the diagram below:

image

SIP doesn’t appear to play nicely with this double-NAT arrangement.  So I changed the WAN configuration on my BT ADSL router to run in “Bridged” mode and then configured the “Red” (internet) interface on the SmoothWall to run in PPPoE mode.  This required configuring the BT broadband username and password settings in the “PPP” section of “Networking”, then navigating to “Home” and hitting “Connect”.  I couldn’t believe it, it actually worked!  To refine things I disconnected, went back into “PPP” and ticked the “Persistent connection” and “Connect on SmoothWall restart” tick boxes and then re-connected.  This diagram shows the new setup:

image

This didn’t even require any exceptions in the firewall configuration or the use of SIP proxy.

I hope this helps you.

UPDATE: I had to add an outgoing firewall rule to allow a port range from 10000 to 20000.  I had been able to call but hadn’t properly tested actual sound over the link.  So it appears that SIP was getting through but not RTP.  Getting full call functionality required opening the aforementioned port range.

Comments

H. Abrantes said…
icaro.aquino@hotmail.com
obovsem said…
Make Cheap International Calls Using VOIP. Voip review - Choose The Best One For You. voip providers - Compare
Anonymous said…
This was a great read! I was just talking with a coworker about voip providers, I'm going to have to show her this. Thank you for sharing this with us it was very interesting and informative!
Anonymous said…
i think you may have to add input and output from 10k to 20k ports.

Popular posts from this blog

Evolution MK-249C MIDI Keyboard Mac OS X Problem

Mac OS X generally seems capable of dealing with just about anything you can throw at it. However upon connecting my trusty Evolution MK-249C MIDI keyboard up to my 2nd generation MacBook it steadfastly refused to play ball. This keyboard has always been instantly recognised by Windows XP and so it was surprising to encounter this. The M-Audio website (M-Audio took over Evolution it appears) offered no real assistance. There was no driver available for Mac OS X 10.4.9 as the keyboard is supposed to be "Class Compliant" which apparently means it doesn't need one... strange. Eventually after consulting some forums I found the fix. The problem seems to be related to Mac OS on the Intel MacBooks. There is a patch on the M-Audio site but only for MacOS 10.1.5. This must be downloaded and installed. Here is the link: http://www.m-audio.com/index.php?do=support.drivers&f=596 Upon restarting the OS the keyboard was recognised by Mac OS and GarageBand had no trouble tal...

Copying NTFS Permissions with RichCopy

 Microsoft's RichCopy is a fantastic tool for copying/moving files.  It's multithreaded so moves things along quicker and has a nice log so you can see what's working and what's going wrong. It's kind of like a GUI on top of RoboCopy and you can get it here... However, I always forget that it doesn't copy file/folder NTFS permissions by default.  This is what you need to do if you want permissions to copy across to the destination: - Click the "View" menu and then click on "Advanced". - Then click the "Option" button on the right below the "Source" and "Destination" buttons. - Click on "File attributes, Error Handling" - Tick the relevant boxes under the "Security information" section. Hope this helps.

XP Startup Issues - The Recovery Console

The Windows Recovery Console is a fantastically useful tool if you find yourself with a PC that will not boot Windows. There are many useful Windows startup tools such as Last Known Good Configuration and the many different flavours of Safe Mode but all of these rely on a bootable Windows system. System Restore is completely useless in this scenario since it relies on one being in Windows to use it. The kinds of things that could couse an unbootable Windows system could be: Corrupted boot files - e.g. NTLDR, NTDETECT.COM Corrputed Windows system files - NTOSKRNL.EXE, HAL.DLL The Recovery Console allows you to boot into an environment "underneath" that of your Windows installation (by using the Windows CD or by choosing it at boot time if you pre-installed it) and so you can perform major low level repairs to your Windows installation. Follow the link below to find out how to use the Recovery Console: http://support.microsoft.com/kb/314058/