Cisco ASA Latency

ASA VPNs support two primary methods of establishing VPNs: IPSec and SSL WebVPN. Typically, the IPSec tunnels are used to establish static point-to-point VPNs (bridging two networks, for example) and the WebVPN is intended for client remote access.

OpenVPN uses its own setup to establish a VPN using SSL, and while OpenVPN and WebVPN use SSL, they're not compatible with other. This doesn't mean that you can't run both - you could setup an OpenVPN server inside for firewall or on a DMZ, and the OpenVPN traffic would be just another TCP stream running over a specific port to the ASA. However, you'll need additional hardware beyond the ASA5505 to accomplish it.

I would run through these steps:

1. Before the L2L P2 is up, go ahead and ping an interesting traffic host. If everything is set up correctly, this will initiate the tunnel. Apologies if you already knew that but some do not.
2. On the ASA, ensure that you have set up a crypto map entry for the interesting traffic. What could be happening, and this is just a guess, but perhaps you do not have the correct crypto map in place and instead when the peer initiates you are establishing using the dynamic crypto map.
3. Using ASDM you can check out your connection profile and check your setting under Crypto Map and make sure that it is on "Bidirectional" rather than "answer only"
4. Finally, make sure that is not your peer that is the issue.