Re: [Astlinux-users] Firewall/NAT Issue with SIP Devices behind the Astlinux Box

[James Babiak]

But that's the problem, I didn't. Not until you suggested it later on. While I originally had port 5060 configured in the plugin and being used on the ATA, when that didn't work I changed the port on the ATA to 5061 and later on 5090. Both times without modifying the voip-sip plug-in at all. And it continued to have an effect on the contents of my sip packets. But regardless of that problem, there is another one. The purpose, as far as I understand, of this plug-in is to assist in exactly what I was trying to accomplish. I should have able to use it in this scenario, since that's the purpose of the plug-in, correct? But not only did it not work, it actually broke things completely. And disabling it altogether was the only solution, proving that the plug-in itself is not only unnecessary, but counterproductive. So that's how I came to the conclusion that the voip-sip plug-in, or at the least Astlinux's implementation of it, is broken. 1) It listens and modifies the contents of sip packets outside of it's assigned port(s). 2) It changes IP addresses to seemingly random and invalid ones. -James Philip A. Prindeville wrote: If you had previously put 5090 into SIP_VOIP_PORTS then yes, that would have persisted across firewall restarts. Hence the need to reboot. On 01/25/2010 09:33 AM, James Babiak wrote: Hey Everyone, Ok, so I think I got everything working. It was the voip-sip plugin that was causing the problem. I had to disable it altogether and then reboot the astlinux box. Restarting only the firewall/iptables had no affect. It seems like the plugin is broken, because if enabled, it will apparently do some stateful packet inspection on all ports and modify the contents of any sip packets it sees, not just the packets destined for the ports defined in the plugin itself. And I guess restarting the firewall won't unload any plugins loaded at boot? In any case, once I disabled and rebooted, I was finally able to send a fax to the machine behind the ATA. Looking at a packet capture shows no evidence of modified sip messages. I'm at work so I haven't had a chance to test outbound faxes, but I'm hoping that will work as well... So even though I (hopefully) have it fixed, it's still very perplexing about why it was broken in the first place. First, why was the plugin going above and beyond the call of duty. Secondly, even if it was doing this on other ports, why would it set the RTP information to invalid IPs? Thanks again for the help Phillip and Lonnie! -James ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.