PAP Unable to Register when VPN enabled

[newbie]

Hi,

Hopefully this is the right place for this..

I have a Linksys PAP2T running behind an Asus RT-N12 with Tomato on it. The Tomato build includes OpenVPN. The router is configured to be a VPN client to a server my ISP (Acanac) hosts. When the tunnel is established the PAP device is unable to register, according to its info page. When the tunnel is disabled the phone works fine. I have the standard UDP ports forwarded (5060,5061,6060, and 6061) and QOS enabled via this guide: http://forum.freephoneline.ca/viewtopic.php?f=14&t=1856. The VPN tunnel was created following this guide: https://community.acanac.com/acanac/vie ... iew=unread.

I would prefer to not run the OpenVPN client on one particular box and let the router handle the connection.

I think the answer to my issue may be setting up a static route, but so far I have been unsuccessful in its creation. After the route creation I am waiting for the PAP to attempt to register again before deciding that it is not working.

Any thoughts that someone may have would be appreciated.

[newbie]

Since I posted the above I have found that if I establish the vpn tunnel and then change the port that the PAP uses the phone works. Here is what I did:
- Establish tunnel, phone stops working
- Change port from 5061 to 6061
- Phone registers and works
- Take down tunnel, phone continues to work
- Enable tunnel, phone stops working
- Change port from 6061 to 5061, phone registers and works

It appears that what the port is changed to doesn't matter, just that it is changed. In my mind this seems to suggest that the tunnel is not the issue that the registering is. My thought is that my IP changes when the tunnel enables which could explain (at least in my head) why the connection drops. But when the PAP goes to re-register it fails. I can't seem to figure out why changing the port would make it work.

[curriegrad2004]

Is the IP address that your VPN provider assigns public? Because if the IP that your VPN provider provides isn't public then problems might happen with registering the ATA adapter to a server.

[newbie]

I believe the address is public, based on my understanding. Once the tunnel is established when I go to whatismyip.org the address listed is the VPN server's IP. This is a different address then when the tunnel is down, which is to be expected.

[curriegrad2004]

whatismyip.com only tells you half the story. You'll need to get more by actually ssh'ing into the router and typing ifconfig. A huge hint would be tun0 or something similar.

[newbie]

routing table when vpn tunnel is connected has tun11

[newbie]

For those that are curious, or in the off chance this helps someone in the future...

It turns out that my QOS settings stopped working when the VPN tunnel was established. All traffic became marked as unclassified. The result was that when other things were going on within the network the ATA was not given priority and could not register.