Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <51128> Message-ID: <[email protected]>
Hello everybody, I'm facing a challenge here in Belgium. I want to promote Open Source with SipXecs against closed software using Axon (http://www.nch.com.au/pbx/index.html). Here is the configuration, this is not my design but the owner doesn't want to change it because it works with Axon and various phones out of the box. SipXecs (192.168.1.248 ----------->FW (with ports open)<---->VPN<----->FW---- Phones (192.168.3.0/24) --> FW The problem is on the 192.168.3.0/24 range there are two gateways, one in VPN to 192.168.1.0 and the other, on the same range, going to the internet. By changing the gateway, you choose provider X and VPN or provider Z (no VPN). By adding a remote worker in this case (range 10.10.10.0/24) all calls from or to 192.168.1.0/24 are working both way with sipxecs (voice too we can hear each other). But the problem is remote workers (10.10.10.10) to phones in 192.168.3.0/24 with no VPN, if the 10 range call no problem, if the 192.168.3.0 is calling the 10.10.10.0/24 I can hear them but they can't hear me :( The Sipxecs is well configured with all NAT options, and the two firewalls in VPN are MonoWall. My questions are: For Intranet Subnets, what happens if you got remote workers in the same range (here for example 192.168.3.0/24) ? I got a phone announcing itself with x-sipX-privcontact=192.168.3.100%3A5060 shall it be routed with SBC if I don't define 192.168.3.0/24 in intranet subnets, also what will happen if I define 192.168.3.0/24 ? Also, why with Axon (which is a B2BUA I think) all is good directly without having to disable ALG or uncheck ICE in X-Lite ? The only differences with SipXecs is that the Axon is dual homed, one connection with public IP in the DMZ, the other in the 192.168.1.0/24 range Many thanks for your answers. Regards, _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
