Hello @osman.elhanafy ,
EIGRP metric manipulation can be performed by using offset-lists on both the spokes and the hub that should not transmit and reiceve video traffic.
However, this is possible only if all the video endpoints both in the sites and in the central site have their own dedicated IP subnet.
Because EIGRP metric manipulation happens for prefix not for single end user hosts.
access-list 10 permit 192.168.10.0 0.0.0.255
router eigrp 100
offset-list 10 20 out tunnel 1
(to be checked the exact syntax of the command can be different)
offset-list {access-list-number | access-list-name} {in | out} offset [interface-type interface-number]
see
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_eigrp/command/ire-cr-book/ire-i1.html?dtid=osscdc000283#wp4196374404
on the hub all the remote video IP subnets should be processed by the ACL used by offset-list. This is done on the tunnel that should not be used as the offset will increase the delay component that is cumulative in EIGRP composite metric.
If this is not true, and video endpoints are just hosts in normal data IP subnets you should use PBR policy based routing to identify video traffic both on hub router(s) and on the spoke site routers.
If you have two DMVPN tunnels and two hubs PBR is possible and easy to achieve.
Hope to help
Giuseppe
