Hi All,
 
I want to register my FS machine (FreeSWITCH Version 1.6.0 - git 6762f14 2015-09-03 20:36:52Z 64bit - CentOS 6.7, selinux is disabled for debugging) as endpoint at another target SIP server (1.1.1.1). This is my gateways section:
 
    <gateway name="1111">
        <param name="register" value="true"/>
        <param name="register-transport" value="udp"/>
        <param name="username" value="1111"/>
        <param name="realm" value="1.1.1.1"/>
        <param name="password" value='my_strong_pass"/>
        <param name="proxy" value="1.1.1.1"/>
        <param name="expire-seconds" value="90"/>
    </gateway>
 
The problem is - a target server at 1.1.1.1 receives absolutely no packets from my FS machine and I'm getting constant registration timeouts:
 
2015-09-21 15:01:46.764466 [ERR] sofia_reg.c:2101 487020870 Registration Failed with status Request Timeout [408]. failure #1
2015-09-21 15:01:46.864501 [WARNING] sofia_reg.c:469 487020870 Failed Registration [408], setting retry to 30 seconds.
 
Meanwhile, when I do UDP scan of port 5060 on 1.1.1.1 from FS machine, I see that port is opened:
 
[root@srv]# nmap -sU -Pn -p U:5060 1.1.1.1
Starting Nmap 5.51 ( http://nmap.org ) at 2015-09-21 15:28 EEST
Nmap scan report for 1.1.1.1
Host is up.
PORT     STATE         SERVICE
5060/udp open|filtered sip
Nmap done: 1 IP address (1 host up) scanned in 2.28 seconds
[root@srv]#
 
When I filter out port 5060 on target machine 1.1.1.1 I see appropriate lines in the log showing filtered requests:
 
Sep 21 10:39:57 sip kernel: DROP IN=eth0 OUT= MAC=00:16:3c SRC=2.2.2.2 DST=1.1.1.1 LEN=28 TOS=0x00 PREC=0x00 TTL=52 ID=10616 PROTO=UDP SPT=47229 DPT=5060 LEN=8
Sep 21 10:39:58 sip kernel: DROP IN=eth0 OUT= MAC=00:16:3c: SRC=2.2.2.2 DST=1.1.1.1 LEN=28 TOS=0x00 PREC=0x00 TTL=47 ID=23653 PROTO=UDP SPT=47230 DPT=5060 LEN=8
 
Firewalls on both machines are off for debugging:
 
[root@srv]# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
[root@srv]#
 
I've spent many hours while investigating that quest but still have no ideas on what's happening. I'll highly appreciate if someone can point on where else I can look to resolve my issue.
 
Thanks in advance
 
Mike