24 Jun
2003
24 Jun
'03
1:09 a.m.
I am testing Nathelper module. It works well delivering SIP messages.
However, natping-interval function seems malfunction.
The NAT scenario is simulated by a microsoft ICS. There is a Cisco ATA
behind NAT with internal address 192.168.0.2 and it's mapped to external
address 192.17.1.22. Ser is listening on external address 192.17.1.173. I
added "modparam("nathelper", "natping-interval", 5) " to the
nathelper.cfg
file.
When ATA registered to Ser, I noticed 192.168.0.2:5056(UDP) is mapped to
192.17.1.22:1025(UDP). Register is successful and call could be established
between internal ATA and external ATA(one way audio). It's expected that
Ser should send a UDP packet to 192.17.1.22:1025(UDP) every 5 seconds.
However, the UDP packet is actually sent to 192.17.1.22:260(UDP). I wonder
what's the problem?
ATA-------------------->NAT------------------------>Ser
From:192.168.0.2:5060 From:192.17.1.22:1025
To: 192.17.1.173:5060 To: 192.17.1.173:5060
ATA NAT<-------------------------Ser
From: 192.17.1.173:5060
To: 192.17.1.22:260
ATA NAT-------------------------->Ser
Destination Unreachable
26 Jun
26 Jun
6:24 p.m.
On Jun 23, 2003 at 15:09, Younger Wang <wygmail(a)yeah.net> wrote:
I am testing Nathelper module. It works well
delivering SIP messages.
However, natping-interval function seems malfunction.
The NAT scenario is simulated by a microsoft ICS. There is a Cisco ATA
behind NAT with internal address 192.168.0.2 and it's mapped to external
address 192.17.1.22. Ser is listening on external address 192.17.1.173. I
added "modparam("nathelper", "natping-interval", 5) " to
the nathelper.cfg
file.
When ATA registered to Ser, I noticed 192.168.0.2:5056(UDP) is mapped to
192.17.1.22:1025(UDP). Register is successful and call could be established
between internal ATA and external ATA(one way audio). It's expected that
Ser should send a UDP packet to 192.17.1.22:1025(UDP) every 5 seconds.
However, the UDP packet is actually sent to 192.17.1.22:260(UDP). I wonder
what's the problem?
260 is htons(1025). There was something like this fixed recently by the
nathelper module author, so please try updating to the latest cvs
(0.8.11dev34), or the latest cvs 0_8_11 pre-release (0.8.11pre34)
(cvs update/checkout -r rel_0_8_11).
Andrei
27 Jun
27 Jun
7:47 p.m.
Thanks for your details, Andrei!
Younger Wang
----- Original Message -----
From: "Andrei Pelinescu-Onciul" <pelinescu-onciul(a)fokus.fraunhofer.de>
To: "Younger Wang" <wygmail(a)yeah.net>
Cc: <serusers(a)lists.iptel.org>
Sent: Thursday, June 26, 2003 8:24 AM
Subject: Re: [Serusers] Nathelper natping-interval malfunction.
On Jun 23, 2003 at 15:09, Younger Wang
<wygmail(a)yeah.net> wrote:
> I am testing Nathelper module. It works well delivering SIP messages.
> However, natping-interval function seems malfunction.
>
> The NAT scenario is simulated by a microsoft ICS. There is a Cisco ATA
> behind NAT with internal address 192.168.0.2 and it's mapped to external
> address 192.17.1.22. Ser is listening on external address 192.17.1.173.
I
> added "modparam("nathelper",
"natping-interval", 5) " to the
nathelper.cfg
> file.
>
> When ATA registered to Ser, I noticed 192.168.0.2:5056(UDP) is mapped to
> 192.17.1.22:1025(UDP). Register is successful and call could be
established
> between internal ATA and external ATA(one way
audio). It's expected
that
> Ser should send a UDP packet to
192.17.1.22:1025(UDP) every 5 seconds.
> However, the UDP packet is actually sent to 192.17.1.22:260(UDP). I
wonder
what's the
problem?
260 is htons(1025). There was something like this fixed recently by the
nathelper module author, so please try updating to the latest cvs
(0.8.11dev34), or the latest cvs 0_8_11 pre-release (0.8.11pre34)
(cvs update/checkout -r rel_0_8_11).
Andrei
7821
days inactive
7825
days old
2 comments
2 participants
participants (2)
-
Andrei Pelinescu-Onciul -
Younger Wang