Hi Tony
In my inGate setup
eth0 private ipaddr of lan INSIDE 192.168.10.0/24
eth1 is Internet ITSP
eth2 private ipaddr is where SIPX_LAN lives 192.168.20.2/24
Internal phones are on eth2 dhcp/ddns and can place and receive calls presently.
Both STUN and Remote NAT Traversal in "Remote SIP Connectivity" module are turn
ON.
Presently 2 STUN public ipaddr in ALIAS and
proposed add 1 private ipaddr in ALIAS 192.168.20.3
Under this scenario; What is being required to be set in sipX to get x-lite 4.0
to remote (from Internet) to register?
----- Original Message -----
From: Tony Graziano
To: [email protected] ; [EMAIL PROTECTED]
Sent: Monday, October 27, 2008 12:40 PM
Subject: Re: [sipx-users] How to get x-lite 4.0 to register frominGate/SBC
->sipX
No tricks.
This assumes ETH0 is on the network where sipx is installed.
ETH0 has to have two IP's bound to it. The ALIAS (second IP) needs to be the
one used by sipx for siptrunk/gateway addressing.
No change is necessary on ETH1.
This way registration occur on the main private IP, but trunking traffic
happens on the ETH0 ALIAS IP.
This also means the dialplan in the ingate needs to reflect the ALIAS IP
instead of the main ETH0 IP.
It also assumes remote sip connectivity is turned on. Here we use DNS SRV for
everything, so no reconfig for counterpath is needed based on network location.
>>> "voice" <[EMAIL PROTECTED]> 10/27/2008 12:07:01 PM >>>
?
Hi
Has anyone gotten x-lite 4.0 to register from remote location through inGate
=> sipX? I have gotten it to ring on remote laptop from an AT&T phone but will
not register from remote laptop. What's the trick?
r
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
