[Serusers] 483

[Nils Ohlmeier]

I oversaw that you device is not symmetric: it requests the answers send back 
to port 5060 but it sends it request from another port. Your device should 
put add the rport paramter to its via. Alternativly you can force rport 
adding at your SER (please consult the docs how to do this).

Greets
  Nils

On Friday 19 December 2003 00:49, Nils Ohlmeier wrote:
> As you can see from your own network dump, the NAT devices sends back an
> ICMP port unreachable (3:3). This means the 200 OK send from SER back to
> your device never reaches the device. Please fix your NAT device.
>
> Greets
>   Nils
>
> On Thursday 18 December 2003 21:38, jerk face wrote:
> > I'm adding the output from ngrep when my client tries
> > to register.  These packets are constantly looped.
> > Note the following changes to my logs:
> > 67.70.NAT.IP -> the IP address of the NAT server in
> > which the client is connected to
> > 67.70.SER.IP -> the IP address of my SER server
> > demosip.mydomain.com -> the DNS name of my server
> >
> > U 67.70.NAT.IP:2862 -> 67.70.SER.IP:5060
> >   REGISTER sip:demosip.mydomain.com SIP/2.0..Via:
> > SIP/2.0/UDP 67.70.NAT.IP:5
> >   060..From: hsimpson
> > <sip:hsimpson at demosip.mydomain.com>;tag=1679191039..To:
> >    hsimpson
> > <sip:hsimpson at demosip.mydomain.com>..Call-ID:
> > 1978684008 at 192.168.
> >   10.16..CSeq: 1 REGISTER..Contact:
> > <sip:hsimpson at 67.70.NAT.IP:5060>..max-fo
> >   rwards: 70..expires: 60..Content-Length: 0....
> > #
> > U 67.70.SER.IP:5060 -> 67.70.NAT.IP:5060
> >   SIP/2.0 200 OK..Via: SIP/2.0/UDP
> > 67.70.NAT.IP:5060..From: hsimpson
> > <sip:hsimpson at demosip.mydomain.com>;tag=1679191039..To:
> > hsimpson
> > <sip:hsimpson at demosip.mydomain.com>;tag=b27e1a1d33761e85846fc98f5f3a7e58.
> >05 da..Call-ID: 1978
> >   684008 at 192.168.10.16..CSeq: 1 REGISTER..Contact:
> > <sip:hsimpson at 67.70.231.21
> >   8:5060>;q=0.00;expires=60..Server: Sip EXpress
> > router (0.8.12 (i386/linux))
> >   ..Content-Length: 0..Warning: 392 67.70.USER.IP:5060
> > "Noisy feedback tells:
> >     pid=8877 req_src_ip=67.70.NAT.IP req_src_port=2862
> > in_uri=sip:demopbx.te
> >   lantek.com out_uri=sip:demosip.mydomain.com
> > via_cnt==1"....
> > ###
> > I 67.70.NAT.IP -> 67.70.SER.IP 3:3
> >   ....E..d.. at .@..6CF..CF.......P..SIP/2.0 200 OK..Via:
> > SIP/2.0/UDP 67.70.231.
> >   218:5060..From: hsimpson
> > <sip:hsimpson at demosip.mydomain.com>;tag=1679191039
> >
> > --- jerk face <jerkface2098 at yahoo.com> wrote:
> > > Here's the scenario:
> > > As of now, I can only get users to register with my
> > > SER if I don't use database authentication.  These
> > > users must also have a static IP address to
> > > register.
> > >
> > > I am now trying to get a client to register with SER
> > > from behind a NAT.  I am using a STUN server address
> > > to help with the NAT situation.  When I do this I
> > > get
> > > a 483 message.
> > >
> > > >From looking at similar posts, the problem is
> > >
> > > usually
> > > caused by setting uri=="some.domain.com"
> > > I don't have this configuration; in ser.cfg I have
> > > the
> > > following:
> > >
> > > alias="my.domain.com"
> > >
> > > if(uri==myself)
> > >
> > > Also, I am running ser-0.8.12 if that makes any
> > > difference.
> > >
> > > Does anybody know why I am getting 483 error
> > > messages?
> > >
> > > Any help is always appreciated.
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > New Yahoo! Photos - easier uploading and sharing.
> > > http://photos.yahoo.com/
> > >
> > > _______________________________________________
> > > Serusers mailing list
> > > serusers at lists.iptel.org
> > > http://lists.iptel.org/mailman/listinfo/serusers
> >
> > __________________________________
> > Do you Yahoo!?
> > New Yahoo! Photos - easier uploading and sharing.
> > http://photos.yahoo.com/
> >
> > _______________________________________________
> > Serusers mailing list
> > serusers at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers