I have my asterisk box on the public network. I have a winders box on the public network, running diax. I have a winders box, same setup, behind my Linux iptables firewall, on a private network. Both boxes cann register iax2 to asterisk, and dial, but as soon as asterisk tries to do the native bridge, the call fails. I've poked at this way too much today... what ports do I need to open for this to work? Tim -->>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< >> Tim Sailer >< Coastal Internet, Inc. << >> Network and Systems Operations >< PO Box 726 << >> http://www.buoy.com >< Moriches, NY 11955 << >> tps@buoy.com >< (631) 399-2910 (888) 924-3728 << >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
On Tue, 3 Feb 2004, Tim Sailer wrote:> I have my asterisk box on the public network. I have a winders box on the > public network, running diax. I have a winders box, same setup, behind > my Linux iptables firewall, on a private network. Both boxes cann register > iax2 to asterisk, and dial, but as soon as asterisk tries to do the native > bridge, the call fails. I've poked at this way too much today... what ports > do I need to open for this to work?"a private network" -- as in a NATed network? Maybe canreinvite=no or nat=yes will do the magic you need. Greg
Hi,> > I have 2 DIAX phones behind two different NAT firewalls and the * box onone> > of the phones network. > > It works for me. > > Cool. I am sure it has nothing to do with DIAX, but might be the > configuration on the * side. Using IAX(1) works fine, btw.This is very interesting. It seems they still are a lot of bugs to be solved in IAX2 ...:-(> > I have 4569 opened and forwarded/NATed to my *. I am on the same network > as the * server, a friend is remote. After about a minute you loose the > connection.This is another problem and it happens for me too (known bug, which seems to be related with the re-registration which occurs at 60s). BR, Dan
Dan wrote:>>>I have 2 DIAX phones behind two different NAT firewalls and the * box on>>Cool. I am sure it has nothing to do with DIAX, but might be the >>configuration on the * side. Using IAX(1) works fine, btw. > This is very interesting. It seems they still are a lot of bugs to be solved > in IAX2 ...:-(Unfortunately, so.>>I have 4569 opened and forwarded/NATed to my *. I am on the same network >>as the * server, a friend is remote. After about a minute you loose the >>connection.> This is another problem and it happens for me too (known bug, which seems to > be related with the re-registration which occurs at 60s).Maybe those two problems are related to each other, i.e. IAX2 tries to bridge the call ... (I have no idea what I am talking about) rgds pos
Hi, From: "Peer Oliver schmidt" <posde@theinternet.de>> >>I have 4569 opened and forwarded/NATed to my *. I am on the same network > >>as the * server, a friend is remote. After about a minute you loose the > >>connection. > > > This is another problem and it happens for me too (known bug, whichseems to> > be related with the re-registration which occurs at 60s). > > Maybe those two problems are related to each other, i.e. IAX2 tries to > bridge the call ... (I have no idea what I am talking about) >I think that the call is allways passed through the * server if IAX(2) is used. BR, Dan