On Wed, 22 Dec 2010 13:22:47 -0500, Bruce B bruceb...@gmail.com
wrote:
This is a NAT issue like noted before.
Try:
localnet=192.168.0.0/ http://192.168.0.0/24255.255.255.0
instead of:
localnet=192.168.0.0/24
http://192.168.0.0/24Also, make sure you have all your VPN connections as
localnet and
Hi Gilles,
If someone has a working configuration where...
1) Asterisk and some users are on a private LAN behind a NAT firewall
2) some roadwarriors, behind their own NAT firewall, are allowed to
register with Asterisk, and make/receive calls just like they were in
the office
3) the NAT
On Thu, 23 Dec 2010 15:54:59 +0100, Jeroen Eeuwes
jeroeneeu...@gmail.com wrote:
In sip.conf I have added for all the remote users the setting
canreinvite=no. The downside to that setting is that Asterisk is
always in the audio path. For my situation that does not really
matter.
Thanks Jeroen.
Hello
I have an Asterisk 1.4 server and two XLite softphones, where
Asterisk and the local XLite phone are located in a LAN behind a NAT
router, and the remote XLite phone is located elsewhere on the Net
behind its own NAT router:
http://img252.imageshack.us/img252/3749/asterisknat.png
On 22 December 2010 12:44, Gilles codecompl...@free.fr wrote:
Hello
I have an Asterisk 1.4 server and two XLite softphones, where
Asterisk and the local XLite phone are located in a LAN behind a NAT
router, and the remote XLite phone is located elsewhere on the Net
behind its own NAT
Hello,
you have a typicall nat issue. Asterisk receives messages from the phone
but cannot send any messages back (thats why it tries to resend the 200
ok message 6 times).
try setting qualify=yes to your sip peers config to keep the nat port open.
best regards
stefan
Am 22.12.10 13:44,
On Wed, 22 Dec 2010 14:31:32 +0100, Stefan Schmidt s...@sil.at wrote:
you have a typicall nat issue. Asterisk receives messages from the phone
but cannot send any messages back (thats why it tries to resend the 200
ok message 6 times).
try setting qualify=yes to your sip peers config to keep the
On Wed, 22 Dec 2010 13:18:38 +, Steve Davies davies...@gmail.com
wrote:
Look in the XLite advanced network settings and disable the 2 timeout
settings (RTP and RTCP?). This is not always necessary, but there are
sufficient cases where the packets XLite expects appear early on, but
do not
This is a NAT issue like noted before.
Try:
localnet=192.168.0.0/ http://192.168.0.0/24255.255.255.0
instead of:
localnet=192.168.0.0/24
http://192.168.0.0/24Also, make sure you have all your VPN connections as
localnet and other side subnet as localnet as well if you are using VPN.
Otherwise,
