NAT'd Asterisk not Registering VoIP User

Hi,
I followed Roger's guide in the Trixbox forum to setup
my * server behind nat to work with voipuser.
Initially it did not work and i did the modifications
in sip_nat.conf and it logged in ok.
Server shutdown last night, restarted today
and it can not register !

Outgoing settings in SIP trunk:
===============================
canreinvite=no
fromdomain=voipuser.org
fromuser=lambros
host=sip.voipuser.org
insecure=very
qualify=no
secret=********
type=peer
username=lambros

sip_nat.conf
============
nat=yes
externip=myserver.dnsalias.org
localnet=192.168.2.0/255.255.255.0

In SIP peers i get:
voipuser.org:5060 lambros 120 Request Sent

Using ngrep to check the packets i see that
the request seems to come from 127.0.0.1. Is this the
correct behaviour ?

192.x.x.x:5060 -> 216.127.x.x:5060
REGISTER sip:voipuser.org SIP/2.0..Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z
9hG4bK3b510601;rport..From: <sip:lambros@voipuser.org>;tag=as1d9ce978..To:
<sip:lambros@voipuser.org>..Call-ID: 4784691567c637467fd29f1f7b84e97b [!at] 127.0 (replace the [!at] with a @)
.0.1..CSeq: 108 REGISTER..User-Agent: VOIP Server..Max-Forwards: 70..Expire
s: 120..Contact: <sip:s@127.0.0.1>..Event: registration..Content-Length: 0.


Anyone knows what might be wrong ?

Regards,
Lambros

Your ngrep output would be correct, it is the localhost that is spawning the network request.

Sip Peers output shows the server has sent a registration request, but has not received a reply.

You haven't given the full log output from a registration request, but I suspect you probably have a few lines like:-

Quote:

Jan 21 10:27:39 NOTICE[3118] chan_sip.c: -- Registration for 'rgower@sip.voipuser.org' timed out, trying again (Attempt #1301)

The SIP server here is being a tad tempermental at present, and I suspect you are a victim of its mood swing. It should clear itself shortly

Roger,
Indeed that is what i am getting.
Sunday 20:00 UK time.

Give that server some Cold and Flu stuff )

Lambros