For the phones, you will need to manually configure the TFTP server to point at the UC520 (192.168.10.1 by default) and ensure that that subnet is configured to route across the VPN - if you haven't already done that.
Yes I am using manually configured crypto maps as per the document you've linked to.
I've checked the routes on the SRP and it points to the tunnel (ipsec0) for 192.168.10.0/24.
What appears to be happening however is that when I try a traceroute from an internal host on the 192.168.10.0 network (the UC520 end) to an internal host on the 192.168.15.0 network (the SRP520 end) the route heads off to the internet, not the VPN tunnel? Also the counters aren't increasing on the ACL in place as per the instructions.
I think the config document mentioned earlier is missing a section on excluding the VPN traffic from the NAT process?
So I've now got the VPN running and traffic is happily traversing between both sides however the handset isn't registering. I think this is because the SRP doesn't know the route to the 10.1.1.0 or the 10.1.10.0 networks, and it doesn't seem possible to add these routes manually. Is this correct or can I add these routes manually and select the ipsec0 interface as the next hop?
Hello, This article will describe how to configure PPTP VPN on the new
RV340/345 routers from the Small Business series. RV340/345
Configuration The first step is to enable the PPTP Server: Go to VPN ->
PPTP Server Change PPTP Server: from Off to On Selec...
Article ID:5748 Use TheGreenBow VPN Client to Connect with RV34x Series
Router Introduction A Virtual Private Network (VPN) connection allows
users to access, send, and receive data to and from a private network by
means of going through a public or share...
Article ID:5728 Configure a Teleworker VPN Client on the RV34x Series
Router Objective The Teleworker VPN Client feature minimizes the
configuration requirements at remote locations by allowing the device to
work as a Cisco VPN hardware client. When the T...