For those of you whom seem to have a grasp of Shorewall and IAX2 basics, but still having trouble, you may find this comforting.
Presently, I have two trixboxes that I use for business and personal use. There is one at my home in Columbus, GA, and one here at a military base in Iraq. The one at home, trixbox-1, hosts the trunk to my commercial (SIP) VoIP Provider, IPComms, and broadband internet. The box here, trixbox-3, connects to a satellite based ISP, and because they are the only ISP here and being contracted by AAFES, it's $50USD for 64kbps down, 32kbps up. It's pretty sad, I know.
Trixbox-1 has two NICs and does a number of things besides being a VoIP PBX; it does DHCP, Windows file sharing (SAMBA), etc, and is also my gateway using Shorewall. Trixbox-3 goes through another machine for it's internet connection that also uses Shorewall.
When first setting up the trunk, for a number of days, for the life of me I could not figure out why in the hell the two boxes would see each other according to the asterisk logs, but trixbox-3 would not register on trixbox-1. No matter what I did, nothing worked. Until, on accident, I did this... For one reason or another, IAX2 does not like traversing shorewall firewall after enabling it's down/ports blocked, whatever you want to call the state when the firewall is blocking ALL outgoing packets to the WAN/Internet.
What had I had to do was disable (routestop) shorewall, disconnect the ethernet cable from trixbox-3, enable the firewall to pass packets to the InterNet AND THEN plug the ethernet cable back into trixbox-3. Then, within 30 seconds or so, the damn thing worked.
That event was almost a year ago and to this day I still have to do that when fiddling with the firewall and have to disable it. I haven't the slightest clue why. I'm sure there is another fix such as going into the switch and shutting off the port, or purging the conntrack table on the firewall machine.
Later I'll post my configuration, but the one I used was posted by SkyKingOH.
Member Since:
2008-05-12