: Lee Goodman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 11, 2003 10:04 AM
Subject: Re: [Asterisk-Users] running * on a VPN gateway
I just tried this, I set the bindaddr=outside NAT address and my sip
registration messages now have the correct ip address in the VIA
field
break the SIP thread. As
the registration messages work fine.
Lee Goodman
- Original Message -
From: Ian Blenke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 10, 2003 3:23 PM
Subject: Re: [Asterisk-Users] running * on a VPN gateway
Lee Goodman wrote:
Could
If like me you run * on a VPN (or multihomed) gateway and want to serve
remote SIP clients, make sure you have
bindaddr = 192.168.0.1 ; or whatever is your box's private IP
otherwise * might bind to its public IP and send it as return address in
the SIP call setup, which will (should) be
PM
Subject: [Asterisk-Users] running * on a VPN gateway
If like me you run * on a VPN (or multihomed) gateway and want to serve
remote SIP clients, make sure you have
bindaddr = 192.168.0.1 ; or whatever is your box's private IP
otherwise * might bind to its public IP and send it as return
On Wednesday 10 September 2003 02:02 pm, Lee Goodman wrote:
Could the bindaddr=x.x.x.x be a way to make * work through a NAT?
I have * and a few 7960 phones behind a NAT. I am trying to
register with a proxy on the outside of the NAT. Registration is
ok, but the VIA field has my inside NAT ip
Lee Goodman wrote:
Could the bindaddr=x.x.x.x be a way to make * work through a NAT?
I have * and a few 7960 phones behind a NAT. I am trying to register with a
proxy on the outside of the NAT. Registration is ok, but the VIA field has
my inside NAT ip address (192. 168.0.7). So the proxy doesn't