separate llqs for voice and video are recommended. Cisco MCM software can be added to the 3810 to provide gatekeeper and QoS proxy function. Recommend setting IP Prec 4 for video and 5 for voice application.
video BW = app b/w + 10% overhead for IP + 5% overhead for frame. So you will need about 440k for video alone. Then add voice and data requirements. CIR value on frame should be set higher than the aggregate multimedia traffic expected at any given time.
Version 12.2.5 mainline in the 3810 supports multiple priority q's. You can use IP Prec markings to push the approptiate traffic to the right q. The QoS Proxy in the MCM which can also be loaded on the 3810 can do the packet TOS fields for you.
turns out that they are running VoFR, not VOIP over frame.
I'm applying a traffic shaping map class for the voice. Can I also apply a service policy for the video and if so, where is the service-policy command applied, under the voice map-class or dlci or sub-interface ?
What mechanism is used to tag the video traffic? I know with the Cisco IP phones for example, the actual phone will tag the traffic then on the routers you can classify this traffic. I'm not sure, however, how this would be done for video. I've the design guide, but it doesn't really touch on this that I can see.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...