Thanks for the reply,
I didn't even notice the TCP change.
I tried setting the ProxyServerTransport) to TCP & port 9060 and I'm able to ping 54.209.126.237 from my house.
The obi200 at my parents house is still not registering according to the obi portal.
What I posted was a copy & paste from the RT tech.
What I really don't understand is that if RT auto configures SP1 why would the ports still be set at 5060?
This is from my house, not exactly sure what it means but it looks like only port 5060 supports SIP.root@antixC700:/home/me# nmap -p 9060 -sU 54.209.126.237
Starting Nmap 6.00 (
http://nmap.org ) at 2014-11-30 01:38 EST
Nmap scan report for
ec2-54-209-126-237.compute-1.amazonaws.com (54.209.126.237)
Host is up (0.021s latency).
PORT STATE SERVICE
9060/udp open|filtered unknownNmap done: 1 IP address (1 host up) scanned in 0.61 seconds
root@antixC700:/home/me# nmap -p 9060 -sT 54.209.126.237
Starting Nmap 6.00 (
http://nmap.org ) at 2014-11-30 01:38 EST
Nmap scan report for
ec2-54-209-126-237.compute-1.amazonaws.com (54.209.126.237)
Host is up (0.021s latency).
PORT STATE SERVICE
9060/tcp filtered unknownNmap done: 1 IP address (1 host up) scanned in 0.29 seconds
Port 5060root@antixC700:/home/me# nmap -p 5060 -sT 54.209.126.237
Starting Nmap 6.00 (
http://nmap.org ) at 2014-11-30 01:44 EST
Nmap scan report for
ec2-54-209-126-237.compute-1.amazonaws.com (54.209.126.237)
Host is up (0.022s latency).
PORT STATE SERVICE
5060/tcp filtered sipNmap done: 1 IP address (1 host up) scanned in 0.28 seconds
root@antixC700:/home/me# nmap -p 5060 -sU 54.209.126.237
Starting Nmap 6.00 (
http://nmap.org ) at 2014-11-30 01:44 EST
Nmap scan report for
ec2-54-209-126-237.compute-1.amazonaws.com (54.209.126.237)
Host is up (0.022s latency).
PORT STATE SERVICE
5060/udp open|filtered sipNmap done: 1 IP address (1 host up) scanned in 0.62 seconds