Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
You can only "prioritize" traffic on a congested egress interface.
If you configuration, I'm unsure match protocol RTP will work on tunnel traffic. It should if it only matches protocol and ports, which your QoS pre-classify will "shadow". If it doesn't, you can match protocol upon ingress, tag the packet, and match the tag on egress.
PS:
BTW, egress QoS prioritization requires "congestion", and often with VPN, end-to-end bandwidth is often less than VPN routers' port bandwidths. If so, you'll need to shape. (Oh, I haven't used it, but one of the later DMVPN versions supports adaptive shaping.)
PPS:
If you equipment supports it, you might also consider using VTI tunnels rather than the other crypto maps.
