2005 1:34 PM
To: 'Asterisk Users Mailing List - Non-Commercial Discussion'
Subject: RE: [Asterisk-Users] SPA and NAT traversal
> In your second option using a STUN server would I need to setup my
> own STUN server?
No, use FWD or xten's STUN servers.
--
Nabeel Jafferali
X2
The only way you ll be able to call extension to extension is if
Asterisk is on the same node behind the nat. like the extensions or if
each extension is on a different node. I run a proxie server and have
ran through this problem many time. I bet you can call out bound to the
outside world j
> In your second option using a STUN server would I need to setup my
> own STUN server?
No, use FWD or xten's STUN servers.
--
Nabeel Jafferali
X2 Networks
www.x2n.ca
T: 1.647.722.6900
1.877.VOIP.X2N
F: 1.866.655.6698
___
Asterisk-Users mailing li
rcial Discussion'
Subject: RE: [Asterisk-Users] SPA and NAT traversal
> Thank you for your reply. There is a wealth of information on the
> wiki, etc. I turned on RTP debug and the SPA is not sending it's
> public IP it is sending it's NAT IP (192.168.1.100) so *'s RTP
>
> Thank you for your reply. There is a wealth of information on the
> wiki, etc. I turned on RTP debug and the SPA is not sending it's
> public IP it is sending it's NAT IP (192.168.1.100) so *'s RTP
> packets are going nowhere...
Do I understand your question correctly:
You have an SPA behin
Jim Sturtevant wrote:
Thank you for your reply. There is a wealth of information on the wiki,
etc. I turned on RTP debug and the SPA is not sending it's public IP it is
sending it's NAT IP (192.168.1.100) so *'s RTP packets are going nowhere...
nat=yes makes Asterisk use the public IP that is in
you going to keep it
to yourself? :-)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Eric Wieling
Sent: Saturday, April 09, 2005 11:25 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] SPA and NAT traversal
Jim St
Jim Sturtevant wrote:
I was hoping someone might help me diagnose a NAT issue with an SPA-2000 and
my * server.
My SPA is behind a NAT accessing a server which is also behind a NAT but SIP
and RTP ports are forwarded to it.
My SPA can successfully register. It can call another extension which i
I was hoping someone might help me diagnose a NAT issue with an SPA-2000 and
my * server.
My SPA is behind a NAT accessing a server which is also behind a NAT but SIP
and RTP ports are forwarded to it.
My SPA can successfully register. It can call another extension which is
inside the * local
