Jared,
the Portech SIMbox is registering to a DNS name. The firewall is off and
the NAT is a Zyxel NBG-419 router.
No mather what port I set, It is not working :
--- SIP read from my_public_ip:5070 ---
REGISTER sip:sip.sipserver.tld SIP/2.0
Via: SIP/2.0/UDP
When I
comment out the port-parameter (then it defaults to 5060), it is still
the same...
[Apr 22 09:32:49]
--- Transmitting (NAT) to my_pub_ip:5064 ---
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.23:5064;branch=z9hG4bKc46696a2b5;received=my_pub_ip
From: "SIM
3-1"
Try reseting the Gateway (soft reset of the settings) and use only IE to do
the setup again. Nothing else comes to my mind.
Also, create a simple extension in Asterisk or if you are using FreePBX you
don't need to tamper with any ports stuff.
-Bruce
On Thu, Apr 22, 2010 at 3:37 AM, Jonas
I'm using
Firefox on Fedora but I don't think the problems lies there.
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...
It must be some NAT-thing combination in how the
GSM-gateway/Zyxel-router sends the
On Thu, 2010-04-22 at 17:45 +0200, Jonas Kellens wrote:
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...
Is the device registering to an IP address, or do a DNS name? What type
of NAT firewall are you using?
Jared,
thank you for your answer.
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.
The MV-374 only accepts IP-address, not a FQDN. Will give it another
try though...
The answer from Portech-support :
Take out the router/firewall and connect directly to the net to test your
NAT problem theory.
On Thu, Apr 22, 2010 at 12:15 PM, Jonas Kellens jonas.kell...@telenet.bewrote:
Jared,
thank you for your answer.
As I said in my previous mail, I'm using a Zyxel NBG-419 router (which
normally
As I already
said 2 times earlier in this thread : when I connect directly to the
internet, then the registration goes through normally. So according to
me it is definitely a NAT-problem. Don't need to find this out another
20 times.
Just don't know just what setting is needed when the
