Or take the most approach of do nothing. My personal favorite is to use codecs where QoS matters less, like iLBC, OPUS, etc.
So many business are getting rid of the QoS capable WAN and just doing VPNs, even if they have fancy names that make it sound better than public internet. Sent from my iPhone > On Jan 3, 2017, at 2:25 PM, Ben Amick <[email protected]> wrote: > > So, I know this is an age old question that’s debated, but I’ve been > wondering if anyone here has a perspective here in regards to QoS for > softphones. Obviously, with hardphones, you usually partition a separate VLAN > with AutoQoS/DSCP tags, but that isn’t applicable with softphones. > > I’ve heard of three different options in the past, neither of which seem to > be very simple to deploy, but all seem to be Jabber-centric. > 1. Configuring windows to perform DSCP tagging, and do DSCP QoS on the > switches they are connected to, as well as trusting the device. Problems: > Requires users to be local admins, openings for abuse and network impact due > to blind PC trust. > 2. Configuring your switches with an access list that recognizes the > ports Jabber does outbound to attach DSCP tags to them. Problems: Other > programs could theoretically use those ports > 3. Installing Medianet services on all jabber clients; Configure all > switches for medianet tagging. Problem: (I think?) Requires newer switches to > use, maybe needs an additional server (I vaguely remember possibly needing > prime collab?)? > > Maybe I’m missing some things, but what approach have you guys taken for > softphone/Jabber QoS? And on top of that, what options are there for CIPC (I > know there’s the auto qos trust cisco-softphone for cisco switches, but I > don’t believe there’s a solution other than #1 for non-cisco switches)? > > Ben Amick > Telecom Analyst > > > Confidentiality Note: This message is intended for use only by the individual > or entity to which it is addressed and may contain information that is > privileged, confidential, and exempt from disclosure under applicable law. If > the reader of this message is not the intended recipient or the employee or > agent responsible for delivering the message to the intended recipient, you > are hereby notified that any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this communication > in error, please contact the sender immediately and destroy the material in > its entirety, whether electronic or hard copy. Thank you > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
