<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>[Asterisk-Users] Asterisk Behind NAT</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText9485 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2><<<FONT
face="Times New Roman">Alternatively, I'm open to any suggestions that would
work>></FONT></FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Like you I read about and NAT and the problems.
After a few days unsuccessful battling I gave up. Instead of using SIP
directly, we've taken SIP numbers with a VoIP service provider and receive calls
using IAX from the VoIP provider.</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>I guess you could do the same yourself: have an
instance of Asterisk outside your firewall holding just SIP definitions and a
simple dialplan to direct calls to and an Asterisk instance within a firewall
using IAX that has a complete dialplan. I'm sure the VoIP providers that
offer SIP->IAX and IAX->SIP, such as the one we use, are doing more and
that there are some gotchas. But its an idea.</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT size=2>Bill Seddon</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> asterisk-users-bounces@lists.digium.com on
behalf of sammy ominsky<BR><B>Sent:</B> Mon 2/28/2005 9:03 PM<BR><B>To:</B>
Asterisk Users<BR><B>Subject:</B> [Asterisk-Users] Asterisk Behind
NAT<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Hi all,<BR><BR>I've done quite a bit of reading, and I see that
it's going to be<BR>difficult, but as a last-ditch effort before implementing a
suggestion<BR>I don't like at all, I figured I'd ask...<BR><BR>Has anyone
successfully put an asterisk box on an internal network<BR>behind a NAT device
and been able to connect with SIP from outside? <BR>The real point behind
all this is to implement QoS for the voice<BR>traffic, and putting a third box
in front of the asterisk and NAT boxes<BR>has been deemed "too
expensive".<BR><BR>Currently, asterisk has a public IP, as does the NAT box
behind which<BR>all the office machines sit. If it can be done, the NAT
box would be<BR>the best place to do the QoS, so why not ask,
right?<BR><BR>Alternatively, I'm open to any suggestions that would work.
I've been<BR>handed this challenge on my first day on a new job...
:/<BR><BR>Thanks,<BR><BR>---sambo<BR><BR>_______________________________________________<BR>Asterisk-Users
mailing list<BR>Asterisk-Users@lists.digium.com<BR><A
href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</A><BR>To
UNSUBSCRIBE or update options visit:<BR> <A
href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</A><BR><BR><BR></FONT></P></DIV>
</BODY>
</HTML>