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

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS
Post a Comment
Read more

Logon Scripts in Group Policy not running

Problem  Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful.  Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...
Post a Comment
Read more