A 3005 does not really support qos, especially per flow like you need to properly prioritize the voip traffic.
However, since the 3005 is probably not the location that is bandwidth constrained (it better had not be) you can prioritize the traffic at the spoke (the 831).
On the 831 use the basic mqc (modular qos command line) to mark on the way into each interface, and use llq on the way out)
so on f0/0 of the router you mark such as
match protocol rtp
(or match access-group XXX) if your voip application just uses a bunch of specific udp ports, etc)
set dscp ef
match dscp ef
!here you need to determine how much of your wan
!will voice get to "OWN". After this level, the
!packets will be policed in this config, becareful
!prevent crypto from hiding markings, etc
!if you have a tunnel0 interface use there
!if the tunnel interface is used for vpn
ip nbar protocol-discovery
service-policy input qosmarking
service-policy output qosaction
Now do the same thing for the inbound, only since vpn traffic is coming from the 3005 you cant really go by markings, as the 3005 wont mark traffic that way... You just need to make an egress policy on f0/0 to boost voice and limit everything else... so using incoming ip source of 3005 network's voip server is bests...
! 184.108.40.206 is the voip host in the 3005 side of the
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :