Server
Distro: Debian Testing (Squeeze)
FreeSWITCH ver.: 1.0.6
Client (Dual-Boot Setup)
Problem: Both Windows Vista Ultimate 64-Bit and Ubuntu 10.04 LTS versions of Ekiga, including SFLphone in Ubuntu 10.04 seems to be ignored by FreeSWITCH. FreeSWITCH fails to register.
In the client side, the Windows firewall gets turned off for testing while everything in iptables under Ubuntu has everything set to accept in the filter section.
In the server side, the firewall configuration is quite basic.
- eth0: Cable Modem plugged in via USB cable
- eth1: nVidia Gigabit that connects to my 1Gbit switch
Code:
# Generated by iptables-save v1.4.4 on Tue Jun 8 23:01:56 2010
*mangle
:PREROUTING ACCEPT [19:1057]
:INPUT ACCEPT [19:1057]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [20:4456]
:POSTROUTING ACCEPT [20:4456]
COMMIT
# Completed on Tue Jun 8 23:01:56 2010
# Generated by iptables-save v1.4.4 on Tue Jun 8 23:01:56 2010
*filter
:FORWARD ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -p tcp -m tcp -m multiport -j ACCEPT --dports 22,25,53,80,5060,5080,10000
-A INPUT -p udp -m udp --dport 10000:20000 -j ACCEPT
-A INPUT -p udp -m udp -m multiport -j ACCEPT --dports 5060,5080
-A FORWARD -i eth1 -o eth0 -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -i eth1 -j ACCEPT
-A INPUT -m state -i eth0 --state ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -m state -i eth0 -o eth1 --state ESTABLISHED,RELATED -j ACCEPT
COMMIT
# Completed on Tue Jun 8 23:01:56 2010
# Generated by iptables-save v1.4.4 on Tue Jun 8 23:01:56 2010
*nat
:PREROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
-A POSTROUTING -o eth0 -j MASQUERADE
COMMIT
# Completed on Tue Jun 8 23:01:56 2010
I even turn on the SIP tracer for my internal profile (sofia profile internal siptracer on) and enable debugging (F8 key) but it did not give me the response when I try to register my softphone with FreeSWITCH.
If I start FreeSWITCH in my server side, I'll get this:
Code:
2010-07-08 18:29:16.425593 [INFO] switch_nat.c:410 Scanning for NAT
2010-07-08 18:29:16.425824 [DEBUG] switch_nat.c:167 Checking for PMP 1/5
2010-07-08 18:29:16.676130 [DEBUG] switch_nat.c:167 Checking for PMP 2/5
2010-07-08 18:29:17.176383 [DEBUG] switch_nat.c:167 Checking for PMP 3/5
2010-07-08 18:29:18.176886 [DEBUG] switch_nat.c:167 Checking for PMP 4/5
2010-07-08 18:29:20.177883 [DEBUG] switch_nat.c:167 Checking for PMP 5/5
2010-07-08 18:29:24.179894 [ERR] switch_nat.c:198 Error checking for PMP [general error]
2010-07-08 18:29:24.179926 [DEBUG] switch_nat.c:415 Checking for UPnP
2010-07-08 18:29:37.355052 [DEBUG] switch_nat.c:115 No InternetGatewayDevice, using first entry as default (http://10.0.0.1:6544/getDeviceDesc).
2010-07-08 18:29:37.356919 [INFO] switch_nat.c:430 No PMP or UPnP NAT devices detected!
My question is, should I be concerned about this?
Here's how it's setup:
Cable Modem
|
| <- Dynamically Changing Public IP Address*
|
Server (FreeSWITCH, DNS Server, DHCP Server, etc.)
| <- 10.0.0.1 for LAN
| <- 10.0.0.0/8
|
\---Clients (Home Theater PC, Netbook, etc.)
* I use ZoneEdit with cron to keep my zone info up-to-date.
Asterisk + FreePBX works very well, but I plan to do away with Asterisk + FreePBX and switch myself over to FreeSWITCH, which is what I'm trying to do.
Update:
Hey guys, At first I came here to ask for help, as I've been doing a lot of searches, but what I did not know about is that I can manually set the local_ip_v4 variable in vars.xml. That is the answer I found here:
http://old.nabble.com/where-do-varia...d20699388.html
So if you have an IP address provided by your ISP for eth0, like for example, 1.0.5.4 and your private IP address for eth1 is 10.0.0.1, then FreeSWITCH will just use 1.0.5.4 as a public IP address. But if you have eth0 as a LAN interface and use eth1 as a gateway interface to the Internet, then FreeSWITCH will just use 10.0.0.1 instead, which is a private IP address.
So anyway, without the local_ip_v4 set, it'll just use whatever IP address is assigned to the first network interface. In my case, it's eth0 and having a public IP address automatically assigned to local_ip_v4 by FreeSWITCH would only be possible if I register my softphone from outside my home. That's like saying that my private IP address is assigned to an external profile while my public IP address assigned by my ISP gets assigned to an internal profile. It does not make any sense.
One thing that would make sense is to provide a variable that allows you to specify which network interface connects to an internal network, like so:
Code:
<X-PRE-PROCESS cmd="set" data="internal-net-iface=eth1"/>
Whatever you change could affect the variable of local_ip_v4 that FreeSWITCH automatically assigns to. But one thing that I like to mention is that I'm not that comfortable with using a mailing list to make such a feature request.
I hope I can be of help to anyone who has a similar setup like mine.
