TIPS Traveling man 3 not allowing ipad to register

[jrglass]

I added my ipad external ip with add-ip. Below is the iptable entry. I set up Zoiper but can not connect to my servers external ip but on wifi i can register. Any suggestions?
Thanks,

Jeff



ACCEPT udp -- 174.255.66.35 0.0.0.0/0 udp dpts:5060:5069
ACCEPT tcp -- 174.255.66.35 0.0.0.0/0 tcp dpts:5060:5069
ACCEPT udp -- 174.255.66.35 0.0.0.0/0 udp dpt:4569
ACCEPT tcp -- 174.255.66.35 0.0.0.0/0 multiport dports 8 0,9080
ACCEPT tcp -- 174.255.66.35 0.0.0.0/0 tcp dpt:9001
ACCEPT tcp -- 174.255.66.35 0.0.0.0/0 tcp dpt:21
ACCEPT udp -- 174.255.66.35 0.0.0.0/0 udp dpt:69
ACCEPT tcp -- 174.255.66.35 0.0.0.0/0 multiport dports 2 2,9022
ACCEPT tcp -- 174.255.66.35 0.0.0.0/0 tcp dpt:4445

 

[wardmundy]

Does iptables -nL show 174.255.66.35 entries?? Is SIP port traffic passed through your hardware-based firewall to your server?

 

[jrglass]

the address does show up in iptables -nL Whats the best log to look at to see if the packets goth through by router?

Thanks,

 

[wardmundy]

If the hardware firewall is blocking the connection, you're not going to see any entry in any of the PIAF logs. Place a call from the iPad to an internal extension and watch the Asterisk CLI. I suspect you won't see anything.

 

[jrglass]

i set the ipad on the local network, when i called an internal ext I did see the call on the CLI

 

[wardmundy]

Maybe I'm confused. What is it you're trying to do and what doesn't work??

 

[jrglass]

with phone and server both on the local network ipad works. With ipad on verizon network ipad wont register

I confirmed the ipads verizon ip is correct in the iptables.

Thanks,

Jeff

 

[Huckda]

I had that issue.. had to reset travel'n man.. don't recall how.. but was blacklisted already and needed to reset... was more'n a year ago so I don't recall exactly how I did it.... maybe I flushed iptables and restarted or something

 

[Albert S]

./secure-iptables will flush it for you and restart the TM configuration process. If you forgot to add any IP or FQDN that you've white listed, you will cut the service for those phones.

Also after finding what's your verizon IP address (can use http://mundy.org/whereub) you can try this command to make sure fail2ban did not ban it:
"fail2ban-client set asterisk-iptables unbanip <yourverizonIP>"

Ward recommended fail2ban article: http://www.fail2ban.org/wiki/index.php/Commands

 

[wardmundy]

Turn off iptables for a moment and make a test call to be sure it's an iptables issue and not a hardware firewall issue. Then you'll know where the problem lies.

service iptables stop
service iptables start

 

[vorshr]

Is it a verizon mobile connection? I had this issue with my mifi and I actually had to change my asterisk port from 5060 to 5070 and problem solved. I assume you could setup a redirect in ip table from 5070 to 5060 but not sure it would work.

Jim