A common VoIP protocol being used is H323 which NetMeeting also uses. tcpdump ports 389,522,1503,1720,1731,8080,1469 to see if packets are going through any of these ports. If they are then there's a good chance it's H323 and you need the p-o-m patch for H323 to get it working through NAT.. -----Original Message----- From: Arnt Karlsen [mailto:arnt@xxxxxxx] Sent: Thursday, September 11, 2003 10:38 AM To: netfilter@xxxxxxxxxxxxxxxxxxx Subject: Re: iptables SNAT and sip "REGISTER" On Tue, 09 Sep 2003 08:21:06 +0900, Zen Kato <zenkato@xxxxxxxxxxxxxxxxxx> wrote in message <20030909082106I.zenkato@xxxxxxxxxxxxxxxxxx>: > Hi Arnt, > > Thank you for your comment. > I upgraded to RHL-7.3 linux-2.4.20-20.7 and iptables-1.2.8-8.72.3. ..excellent. > SIP UAs could send and receive "REGISTER", "INVITE", "200 OK", > "ACK" and udp media packets via .100.30. So, DNAT/SNAT of iptales- > 1.2.8 works fine, but both sip phones can not have "audio"?! > > Both sip phones worked fine when I tested using non-NAT with a local > sip proxy. I don't know why this case does not work. ..pass, I dunno much about VoIP. This works in your lan but not across your firewall? Does it conflict with nat? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case.
