NEED MORE INFO Connecting to Incredible Pi behind NAT

[sarichter]

You dont have a dns on your phone, you can install travelin man on it like if it was a web page for autenthication

The travelin man 3 tutorial said to set it up that way so I did. Either way, I see no 'web page' authentication in the tutorial. Where is that?

Still haven't gotten my phone to connect to the Pi yet outside the network.

 

[wardmundy]

This goes back to Message #14. I thought we were clear before on the problem, but here we go again. If IPtables is disabled and you still cannot connect to your Raspberry Pi from outside your LAN, then there is something wrong with your router setup. We can't fix that! Either get a new router, properly configure the one you have, get a new softphone that can register, or live with not being able to connect from outside the LAN. Those are the only options! This really is NOT a Raspberry Pi or Incredible PBX problem. Sorry.

 

[wardmundy]

I checked his router and it was fine you could ping it from the outside, what could the problem be?

Pinging a router from outside is only one piece of the router puzzle. The router needs to be properly configured to pass SIP traffic internally to the Raspberry Pi.

 

[sarichter]

Pinging a router from outside is only one piece of the router puzzle. The router needs to be properly configured to pass SIP traffic internally to the Raspberry Pi.

And to my knowledge... it should be. I have forwarded the correct ports, I have disabled SIP ALG (netgear's worthless attempt at prioritizing that), and the Pi sits on a reserved IP on my network. The setup really isn't rocket science. However, if the router is still blocking it then I have no idea why it is doing that. I actually had the same issue with my previous router that was running Tomato. I couldn't get that to work either... and again, I have yet to find a tutorial anywhere on the web (or here) that goes into detail on setting up a router any further than the items I just listed. Is there a depository of information anywhere else that I can read and try to figure out the issue?

 

[sarichter]

Pinging a router from outside is only one piece of the router puzzle. The router needs to be properly configured to pass SIP traffic internally to the Raspberry Pi.

And also... in post #26, I stated that I got a different error when I took IPtables down behind the router. I got an 'auth forbidden' message which is completely different then when IPtables was up. So that tells me that it's not the router completely. The router might be disrupting traffic, but something about asterisk is not accepting information and providing the correct information back to Sipdroid.

 

[miguel]

Travelin man

 

[miguel]

Flash the router with ddwrt

 

[sarichter]

Flash the router with ddwrt

Not this router... I haven't found anywhere where this one is compatible so I'm not going to do it.

 

[Hyksos]

damn... Let's unwind.

On your Pi:
iptables -P INPUT ACCEPT
iptables -F
iptables -nL

in this order and the last one should output an empty ruleset.

Now disconnect all other internal phones.

Then on the Pi:
asterisk -rvvvvvvvvvv
Leave that open and running.

Connect your remote phone....

While you do that, watch the window where you have asterisk -rvvvvvvvvvv running. It should show stuff when the phone reaches asterisk.
You see nothing there?
Ok do asterisk -rvvvvvvvvvv (if your still in it, no need to do it again)
then do "sip set debug on" IN the asterisk cli your just opened.

Then try the remote phone again while watching the asterisk cli where you typed sip set debug on.

Now what is the results:
what is the remote phone saying
what do you see in the asterisk cli.

 

[miguel]

What is the router model?

 

[miguel]

I could tell you if you gave me the router model

 

[miguel]

Were you able to get it to work?? Post your solution

 

[miguel]

Was this issue resolved?

 

[sarichter]

Was this issue resolved?

No, and I have no idea or direction to work in at this point.