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
9 December 2009 at 14:03
obovsem said…
Make Cheap International Calls Using VOIP. Voip review - Choose The Best One For You. voip providers - Compare
4 January 2010 at 09:10
Kate Dunkin 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!
27 December 2012 at 21:04
Anonymous said…
i think you may have to add input and output from 10k to 20k ports.
27 June 2016 at 08:54
Post a Comment

Popular posts from this blog

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.
11 comments
Read more

WSUS Issues

Was configuring WSUS on a Server 2016 VM for a customer recently and found the performance to be very sluggish and most of the time the client PCs would time-out and throw an error message when trying to check for updates. After much digging on different forums I came across a fix that worked nicely: Open Internet Information Services (IIS) Manager and click on Application Pools Then Right-Click on your WsusPool instance and choose Advanced Settings Scroll down to Private Memory Limit (KB) and change it from the default of 1843200 to 0 which means unlimited. Then right-click and stop the WsusPool and then start it again. Hope this works for you.
Post a Comment
Read more

Unable to Extend Volume because the Windows Recovery Partition is in the way

I had to increase the space allocated to a customer's WSUS server VM that had run out of capacity and was keeling over. So I powered off the VM, added the extra capacity to the virtual hard disk, powered it back on, and went into Disk Management to extend the C: drive partition.  However, I discovered that because the Windows Recovery Partition was in between the C: partition and the new unallocated space (similar to the image below which I've copied from Woshub.com ), I was unable to do an "Extend Volume" job. The solution was to move the recovery partition.  This involves disabling it, deleting it, extending your partition as required, and then re-creating the recovery partition and enabling it. Here are the steps involved: Disable existing recovery partition: You will need to disable the existing Windows recovery partition. To do this, run this command from an admin command line/PowerShell:  reagentc /disable If you get the error message "REAGENTC.EXE: Operati...
Post a Comment
Read more