Phone Adapter (ATA) SPA112 Issue - Possibly due to Android Phone USB Tethered WAN

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Kal1975

Occasional Visitor
My internet provider is having a problem and internet is down for many people...Rogers cable for those interested. In any case, I USB tethered my Android phone to get my home network back up. All seemed to be working. I think I came across something that wasn't working and I believe I know why...but I don't know what to do in this case. I have a SPA112 telephone adapter behind the router which is not working now.

My WAN IP address when all is working is usually a public IP address. When the Android phone is USB tethered, the WAN address is a private IP address, 192.168.42.x My home network is also NAT'ed with 192.168.1.x subnet. I guess this is a double-nat situation.

I think the double-nat is the issue. I also just noticed that I can get incoming calls but not make outgoing calls.

Is there any way to confirm what the issue is and/or whether the double-nat is the issue? If so, what do you do in a double-nat situation? Is there a workaround?

Any help is appreciated.
 

Kal1975

Occasional Visitor
Found the problem. I was using the IP Restrictions feature from my VOIP provider. I had to put in the public IP address of the Android phone into the VOIP admin screens.

Problem solved.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top