Hi guys, I've got a rather interesting situation, here. I've got an ATA registering to a FreeSWITCH(TM) (FS2), both behind NAT. So far, so good. Now, the FreeSWITCH(TM) registers to another FreeSWITCH(TM) outside the NAT (FS2), and that's where the problems start. Here's the configuration: ATA<->FS2<->NAT<->Internet<->FS1 ATA: 10.1.0.51 (behind NAT) FS2: 10.1.0.30 (behind NAT) FS1: freeswitch1.asnetinc.net (64.118.94.19) Now, here's where it gets very interesting. This is what FS1 gets when FS2 registers:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600] nta_agent: tport: Bad message
Now, where on Earth did 10.0.0.221 come from??? (I've actually hardcoded both external_rtp_ip and server_name to the public IP of the NAT in the FS2 config, but for some strange reason, FS2 apparently claims to be at 10.0.0.221, which isn't even its local IP.) As if that's not interesting enough, I get this from FS1, too, when it tries to connect to another SIP server on the public Internet:
outbound(0xb4e1e1a0): detected NAT: freeswitch1.asnetinc.net != 64.118.94.19
Now, since a forward DNS resolution claims that the inequality is false, I assume it attempted a reverse DNS lookup, which would fail (since my ISP takes forever to update PTR records). As usual, any hints, tips, tricks, ideas, suggestions, flames, questions, or (ideally) answers are greatly appreciated :-) Thank you, - Dave
Try setting your IP to stun:stun.fwdnet.net and let stun do the job. /b On May 21, 2007, at 2:20 AM, Dave wrote:
Hi guys,
I've got a rather interesting situation, here. I've got an ATA registering to a FreeSWITCH(TM) (FS2), both behind NAT. So far, so good. Now, the FreeSWITCH(TM) registers to another FreeSWITCH(TM) outside the NAT (FS2), and that's where the problems start. Here's the configuration:
ATA<->FS2<->NAT<->Internet<->FS1
ATA: 10.1.0.51 (behind NAT) FS2: 10.1.0.30 (behind NAT) FS1: freeswitch1.asnetinc.net (64.118.94.19)
Now, here's where it gets very interesting. This is what FS1 gets when FS2 registers:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600] nta_agent: tport: Bad message
Now, where on Earth did 10.0.0.221 come from??? (I've actually hardcoded both external_rtp_ip and server_name to the public IP of the NAT in the FS2 config, but for some strange reason, FS2 apparently claims to be at 10.0.0.221, which isn't even its local IP.)
As if that's not interesting enough, I get this from FS1, too, when it tries to connect to another SIP server on the public Internet:
outbound(0xb4e1e1a0): detected NAT: freeswitch1.asnetinc.net != 64.118.94.19
Now, since a forward DNS resolution claims that the inequality is false, I assume it attempted a reverse DNS lookup, which would fail (since my ISP takes forever to update PTR records).
As usual, any hints, tips, tricks, ideas, suggestions, flames, questions, or (ideally) answers are greatly appreciated :-)
Thank you, - Dave
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
It doesn't seem to help:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600]
Thanks, - Dave On Mon, May 21, 2007 at 07:49:31AM -0500, Brian West wrote:
Try setting your IP to stun:stun.fwdnet.net and let stun do the job.
/b
On May 21, 2007, at 2:20 AM, Dave wrote:
Hi guys,
I've got a rather interesting situation, here. I've got an ATA registering to a FreeSWITCH(TM) (FS2), both behind NAT. So far, so good. Now, the FreeSWITCH(TM) registers to another FreeSWITCH(TM) outside the NAT (FS2), and that's where the problems start. Here's the configuration:
ATA<->FS2<->NAT<->Internet<->FS1
ATA: 10.1.0.51 (behind NAT) FS2: 10.1.0.30 (behind NAT) FS1: freeswitch1.asnetinc.net (64.118.94.19)
Now, here's where it gets very interesting. This is what FS1 gets when FS2 registers:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600] nta_agent: tport: Bad message
Now, where on Earth did 10.0.0.221 come from??? (I've actually hardcoded both external_rtp_ip and server_name to the public IP of the NAT in the FS2 config, but for some strange reason, FS2 apparently claims to be at 10.0.0.221, which isn't even its local IP.)
As if that's not interesting enough, I get this from FS1, too, when it tries to connect to another SIP server on the public Internet:
outbound(0xb4e1e1a0): detected NAT: freeswitch1.asnetinc.net != 64.118.94.19
Now, since a forward DNS resolution claims that the inequality is false, I assume it attempted a reverse DNS lookup, which would fail (since my ISP takes forever to update PTR records).
As usual, any hints, tips, tricks, ideas, suggestions, flames, questions, or (ideally) answers are greatly appreciated :-)
Thank you, - Dave
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
it appears your might have to set ext-sip-ip and ext-rtp-ip so it can report them properly. /b On May 21, 2007, at 8:42 AM, Dave wrote:
It doesn't seem to help:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600]
Thanks, - Dave
On Mon, May 21, 2007 at 07:49:31AM -0500, Brian West wrote:
Try setting your IP to stun:stun.fwdnet.net and let stun do the job.
/b
On May 21, 2007, at 2:20 AM, Dave wrote:
Hi guys,
I've got a rather interesting situation, here. I've got an ATA registering to a FreeSWITCH(TM) (FS2), both behind NAT. So far, so good. Now, the FreeSWITCH(TM) registers to another FreeSWITCH(TM) outside the NAT (FS2), and that's where the problems start. Here's the configuration:
ATA<->FS2<->NAT<->Internet<->FS1
ATA: 10.1.0.51 (behind NAT) FS2: 10.1.0.30 (behind NAT) FS1: freeswitch1.asnetinc.net (64.118.94.19)
Now, here's where it gets very interesting. This is what FS1 gets when FS2 registers:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600] nta_agent: tport: Bad message
Now, where on Earth did 10.0.0.221 come from??? (I've actually hardcoded both external_rtp_ip and server_name to the public IP of the NAT in the FS2 config, but for some strange reason, FS2 apparently claims to be at 10.0.0.221, which isn't even its local IP.)
As if that's not interesting enough, I get this from FS1, too, when it tries to connect to another SIP server on the public Internet:
outbound(0xb4e1e1a0): detected NAT: freeswitch1.asnetinc.net != 64.118.94.19
Now, since a forward DNS resolution claims that the inequality is false, I assume it attempted a reverse DNS lookup, which would fail (since my ISP takes forever to update PTR records).
As usual, any hints, tips, tricks, ideas, suggestions, flames, questions, or (ideally) answers are greatly appreciated :-)
Thank you, - Dave
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
Okay, I added this to sofia.conf.xml on FS2, to the gateway section: <param name='ext-rtp-ip' value='$${external_rtp_ip}'/> <param name='ext-rtp-ip' value='$${external_rtp_ip}'/> ...and this is still in freeswitch.xml: <!--#set 'external_rtp_ip=stun:stun.fwdnet.net'--> I still get this on FS1, though:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600]
I tried using stunserver.org, too, and it comes out with 10.0.0.221 anyway :-( Any ideas? Thanks a bunch, - Dave On Mon, May 21, 2007 at 08:52:38AM -0500, Brian West wrote:
it appears your might have to set ext-sip-ip and ext-rtp-ip so it can report them properly.
/b
On May 21, 2007, at 8:42 AM, Dave wrote:
It doesn't seem to help:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600]
Thanks, - Dave
On Mon, May 21, 2007 at 07:49:31AM -0500, Brian West wrote:
Try setting your IP to stun:stun.fwdnet.net and let stun do the job.
/b
On May 21, 2007, at 2:20 AM, Dave wrote:
Hi guys,
I've got a rather interesting situation, here. I've got an ATA registering to a FreeSWITCH(TM) (FS2), both behind NAT. So far, so good. Now, the FreeSWITCH(TM) registers to another FreeSWITCH(TM) outside the NAT (FS2), and that's where the problems start. Here's the configuration:
ATA<->FS2<->NAT<->Internet<->FS1
ATA: 10.1.0.51 (behind NAT) FS2: 10.1.0.30 (behind NAT) FS1: freeswitch1.asnetinc.net (64.118.94.19)
Now, here's where it gets very interesting. This is what FS1 gets when FS2 registers:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600] nta_agent: tport: Bad message
Now, where on Earth did 10.0.0.221 come from??? (I've actually hardcoded both external_rtp_ip and server_name to the public IP of the NAT in the FS2 config, but for some strange reason, FS2 apparently claims to be at 10.0.0.221, which isn't even its local IP.)
As if that's not interesting enough, I get this from FS1, too, when it tries to connect to another SIP server on the public Internet:
outbound(0xb4e1e1a0): detected NAT: freeswitch1.asnetinc.net != 64.118.94.19
Now, since a forward DNS resolution claims that the inequality is false, I assume it attempted a reverse DNS lookup, which would fail (since my ISP takes forever to update PTR records).
As usual, any hints, tips, tricks, ideas, suggestions, flames, questions, or (ideally) answers are greatly appreciated :-)
Thank you, - Dave
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Use ext-sip-ip for the ip's we send in the sip packets. You probably need to use both. Mike
-----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch- users-bounces@lists.freeswitch.org] On Behalf Of Dave Sent: Monday, May 21, 2007 12:36 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Strange Reg
Okay, I added this to sofia.conf.xml on FS2, to the gateway section: <param name='ext-rtp-ip' value='$${external_rtp_ip}'/> <param name='ext-rtp-ip' value='$${external_rtp_ip}'/>
...and this is still in freeswitch.xml: <!--#set 'external_rtp_ip=stun:stun.fwdnet.net'-->
I still get this on FS1, though:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600]
I tried using stunserver.org, too, and it comes out with 10.0.0.221 anyway :-(
Any ideas?
Thanks a bunch, - Dave
On Mon, May 21, 2007 at 08:52:38AM -0500, Brian West wrote:
it appears your might have to set ext-sip-ip and ext-rtp-ip so it can report them properly.
/b
On May 21, 2007, at 8:42 AM, Dave wrote:
It doesn't seem to help:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600]
Thanks, - Dave
On Mon, May 21, 2007 at 07:49:31AM -0500, Brian West wrote:
Try setting your IP to stun:stun.fwdnet.net and let stun do the job.
/b
On May 21, 2007, at 2:20 AM, Dave wrote:
Hi guys,
I've got a rather interesting situation, here. I've got an ATA registering to a FreeSWITCH(TM) (FS2), both behind NAT. So far, so good. Now, the FreeSWITCH(TM) registers to another FreeSWITCH(TM) outside the NAT (FS2), and that's where the problems start. Here's the configuration:
ATA<->FS2<->NAT<->Internet<->FS1
ATA: 10.1.0.51 (behind NAT) FS2: 10.1.0.30 (behind NAT) FS1: freeswitch1.asnetinc.net (64.118.94.19)
Now, here's where it gets very interesting. This is what FS1 gets when FS2 registers:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600] nta_agent: tport: Bad message
Now, where on Earth did 10.0.0.221 come from??? (I've actually hardcoded both external_rtp_ip and server_name to the public IP of the NAT in the FS2 config, but for some strange reason, FS2 apparently claims to be at 10.0.0.221, which isn't even its local IP.)
As if that's not interesting enough, I get this from FS1, too, when it tries to connect to another SIP server on the public Internet:
outbound(0xb4e1e1a0): detected NAT: freeswitch1.asnetinc.net != 64.118.94.19
Now, since a forward DNS resolution claims that the inequality is false, I assume it attempted a reverse DNS lookup, which would fail (since my ISP takes forever to update PTR records).
As usual, any hints, tips, tricks, ideas, suggestions, flames, questions, or (ideally) answers are greatly appreciated :-)
Thank you, - Dave
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
What exactly do you mean by that??? Thanks, - Dave On Mon, May 21, 2007 at 12:51:44PM -0400, Michael Jerris wrote:
Use ext-sip-ip for the ip's we send in the sip packets. You probably need to use both.
Mike
-----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch- users-bounces@lists.freeswitch.org] On Behalf Of Dave Sent: Monday, May 21, 2007 12:36 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Strange Reg
Okay, I added this to sofia.conf.xml on FS2, to the gateway section: <param name='ext-rtp-ip' value='$${external_rtp_ip}'/> <param name='ext-rtp-ip' value='$${external_rtp_ip}'/>
...and this is still in freeswitch.xml: <!--#set 'external_rtp_ip=stun:stun.fwdnet.net'-->
I still get this on FS1, though:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600]
I tried using stunserver.org, too, and it comes out with 10.0.0.221 anyway :-(
Any ideas?
Thanks a bunch, - Dave
On Mon, May 21, 2007 at 08:52:38AM -0500, Brian West wrote:
it appears your might have to set ext-sip-ip and ext-rtp-ip so it can report them properly.
/b
On May 21, 2007, at 8:42 AM, Dave wrote:
It doesn't seem to help:
From: [R352928@freeswitch1.asnetinc.net] Contact: ["user" <sip:R352928@10.0.0.221:39260>] Expires: [3600]
Thanks, - Dave
On Mon, May 21, 2007 at 07:49:31AM -0500, Brian West wrote:
Try setting your IP to stun:stun.fwdnet.net and let stun do the job.
/b
On May 21, 2007, at 2:20 AM, Dave wrote:
Hi guys,
I've got a rather interesting situation, here. I've got an ATA registering to a FreeSWITCH(TM) (FS2), both behind NAT. So far, so good. Now, the FreeSWITCH(TM) registers to another FreeSWITCH(TM) outside the NAT (FS2), and that's where the problems start. Here's the configuration:
ATA<->FS2<->NAT<->Internet<->FS1
ATA: 10.1.0.51 (behind NAT) FS2: 10.1.0.30 (behind NAT) FS1: freeswitch1.asnetinc.net (64.118.94.19)
Now, here's where it gets very interesting. This is what FS1 gets when FS2 registers: > From: [R352928@freeswitch1.asnetinc.net] > Contact: ["user" <sip:R352928@10.0.0.221:39260>] > Expires: [3600] > nta_agent: tport: Bad message
Now, where on Earth did 10.0.0.221 come from??? (I've actually hardcoded both external_rtp_ip and server_name to the public IP of the NAT in the FS2 config, but for some strange reason, FS2 apparently claims to be at 10.0.0.221, which isn't even its local IP.)
As if that's not interesting enough, I get this from FS1, too, when it tries to connect to another SIP server on the public Internet: > outbound(0xb4e1e1a0): detected NAT: freeswitch1.asnetinc.net != > 64.118.94.19
Now, since a forward DNS resolution claims that the inequality is false, I assume it attempted a reverse DNS lookup, which would fail (since my ISP takes forever to update PTR records).
As usual, any hints, tips, tricks, ideas, suggestions, flames, questions, or (ideally) answers are greatly appreciated :-)
Thank you, - Dave
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Whoops, my bad, I mistyped it in the email. Here's what I actually have in the config file (sorry, no copy/paste for FS2 available here):
<param name='ext-rtp-ip' value='$${external_rtp_ip}'/> <param name='ext-sip-ip' value='$${external_rtp_ip}'/>
- Dave On Mon, May 21, 2007 at 01:15:40PM -0500, Brian West wrote:
set one ext-sip-ip not duplicate ext-rtp-ip entries.
/b
On May 21, 2007, at 11:36 AM, Dave wrote:
<param name='ext-rtp-ip' value='$${external_rtp_ip}'/> <param name='ext-rtp-ip' value='$${external_rtp_ip}'/>
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Brian West
-
Dave
-
Michael Jerris