Does your client control the router at his site? If so set up SNMP
and run MRTG or Cricket. The latest Cricket and genRtrConfig will
collect
not only bandwidth but errors and buffer drops. The latter are often
correlated with the stutters he sees. Cricket will also monitor the
CPU of the router in case that is what is running out of gas.
Second, if he does control the router, shrink the buffers! Buffering up
lots of VOIP packets that get dropped does no one any good. This may
adversely impact Citrix which is very finicky and can perform very
poorly
over a WAN.
While it would be meaningless once it left the local network, you could
configure everything at the client site for QOS with a class for VOIP, a
class for Citrix and a class for everything else. Since it is a Cisco
router,
you would want the LLQ on the WAN with the VOIP going into the low
latency
queue, the Citrix traffic going into a high priority queue and
everything
else going into a low priority queue.
