<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font size="-1"><font face="Helvetica, Arial, sans-serif">Jared,<br>
<br>
thank you for your answer.<br>
<br>
As I said in my previous mail, I'm using a Zyxel NBG-419 router (which
normally supports VoIP and QoS). Firewall is disabled on the Zyxel.<br>
<br>
The MV-374 only accepts IP-address, not a FQDN. Will give it another
try though...<br>
<br>
The answer from Portech-support : "use STUN".<br>
<br>
Even if the NAT rewrites the IP-address/port combination, why is it a
problem for the Portech and not for the IP-phones (Grandstream &
Snom) ? They all communicate on port 5060 --> 5064 (several
SIP-accounts)<br>
<br>
<br>
Jonas.<br>
<br>
</font></font><br>
Jared Smith wrote:
<blockquote cite="mid:1271951636.3278.2.camel@localhost.localdomain"
type="cite">
<pre wrap="">On Thu, 2010-04-22 at 17:45 +0200, Jonas Kellens wrote:
</pre>
<blockquote type="cite">
<pre wrap="">All goes well when the gateway is connected directly to the
internet... It's when it is behind NAT the 401 is sent from
Asterisk...
</pre>
</blockquote>
<pre wrap=""><!---->
Is the device registering to an IP address, or do a DNS name? What type
of NAT firewall are you using?
This reminds me of a problem I had years ago with a Cisco PIX firewall,
where it would rewrite IP addresses in the SIP Request URI, causing the
authentication to fail. One solution was to have it register to a
fully-qualified domain name instead of an IP address, so that the
Request URI wouldn't get overwritten.
It's certainly worth a shot...
--
Jared Smith
Digium, Inc.
</pre>
</blockquote>
</body>
</html>