[cisco-voip] Jabber/CIPC and QoS
Lelio Fulgenzi
lelio at uoguelph.ca
Tue Jan 10 15:55:59 EST 2017
Super. Thanks for this information.
Looks like any sort of QoS implementation is going to include a number of SME/Service Owners. Luckily we have a fairly good centralized system here. Unfortunately, not everyone is a managed desktop client, so I'm not sure we can do those group policies for everyone. But it's something we'll have to consider. Maybe in phase II or III. [😉]
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519-824-4120 Ext 56354
lelio at uoguelph.ca
www.uoguelph.ca/ccs
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: Anthony Holloway <avholloway+cisco-voip at gmail.com>
Sent: Tuesday, January 10, 2017 3:33 PM
To: Lelio Fulgenzi; Ben Amick; Dana Tong; Tom Sparks; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
If you're talking about the MS AD GPO to prevent/limit which apps can set DSCP, then no, not on the Cisco site.
I just did a quick Google search and found a discussion where one person mentioned that it's possible via CLI.
"If you want to set DSCP bits based on protocols after they leave the application (but before they make it onto the wire), use the ipfw program to setup the bits based on ports, sources, destinations and even ingress or egress. "man ipfw" for more help."
Source: QoS on MacOS X<https://groups.google.com/forum/#!topic/macenterprise/8rELMIDb9WQ>
However, this discussion<https://discussions.apple.com/thread/6645172?start=0&tstart=0> suggests IPFW is gone since Yosemite, and PF<https://en.wikipedia.org/wiki/PF_(firewall)> is now what's used.
Whether or not Apple offers a centralized management feature for PF is beyond me.
On Tue, Jan 10, 2017 at 1:13 PM Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:
Is there a similar process for Macs?
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519-824-4120 Ext 56354<tel:(519)%20824-4120>
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> on behalf of Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>>
Sent: Tuesday, January 10, 2017 2:01 PM
To: Ben Amick; Dana Tong; Tom Sparks; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
Setting the port ranges gives you two benefits:
1) You get to know exactly, and somewhat succinctly which ports will be used by Jabber for RTP (cause you already know what it is for signaling 5060). This one isn't all that great, but if you're going to write an ACL, then it's nice to write 3000 39999, versus 16384 32768. Preference I guess.
2) This one is the real winner. You get to separate your voice from your video traffic, into two different port ranges, allowing you to mark audio at EF and video at AF42, or something else. This way you can have video deteriorate by audio survive. The Sync no longer relies on same classification/marking, that's what RTCP is doing for you nowadays.
At the end of the day, the Group Policy allows you to deny programs from hijacking your markings as they leave the PC. Therefore, the switch would only ever receive trusted DSCP markings.
"For later operating systems such as Microsoft Windows 7, Microsoft implements a security feature that prevents applications from setting DSCP values on IP packet headers. For this reason, you should use an alternate method for marking DSCP values, such as Microsoft Group Policy."
Source: Jabber On-Prem Deployment Guide<http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_5/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115_chapter_010001.html>
On Tue, Jan 10, 2017 at 10:18 AM Ben Amick <bamick at humanarc.com<mailto:bamick at humanarc.com>> wrote:
Dana,
So if I understand you right, you used the SIP profile to set the ranges, GPO to mark the DSCPs, and the switches to trust DSCP.
I assume this means you used access lists to only accept the marking if from that port range? If not, why did you set the port ranges and how are you mitigating the risk of other programs hijacking your QoS?
Ben Amick
Telecom Analyst
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Dana Tong
Sent: Monday, January 09, 2017 11:29 PM
To: Tom Sparks <tsparks at taosconsulting.com<mailto:tsparks at taosconsulting.com>>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
FYI,
I’ve been working with a customer recently where we have utilised both the SIP Profile on CUCM to specify port ranges for voice /video and AD Group Policy to mark the traffic.
There are a few caveats to getting this working. It requires both a Windows registry value turned on, and some settings in the Windows QoS policy.
They had a mix of different switches. They configured the switches to “Trust DSCP”.
Hope this helps.
Cheers
Dana
From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> on behalf of Tom Sparks <tsparks at taosconsulting.com<mailto:tsparks at taosconsulting.com>>
Date: Thursday, 5 January 2017 at 11:31 am
To: "cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
I believe that medianet plugin was discontinued by Cisco. But if anyone gets it working, please let me know.
Here's a seemingly good blog on the whole topic also
https://infrastructureland.wordpress.com/2015/02/07/jabber-12/<http://cp.mcafee.com/d/avndzhJ5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJ4SYqejt-KyUyOCUMqekjtPpesRG9pAEeNSAUJSCT7PZwxNyIk5E_iDbUDt5_bFVstwzF0xYiWau6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrijV4>
Tom Sparks
Taos Consulting
Sr. Voice | Video Engineer
tsparks at taosconsulting.com<mailto:tsparks at taosconsulting.com>
+1 415.515.2391<tel:(415)%20515-2391>
On Wed, Jan 4, 2017 at 9:00 AM, <cisco-voip-request at puck.nether.net<mailto:cisco-voip-request at puck.nether.net>> wrote:
Send cisco-voip mailing list submissions to
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip<http://cp.mcafee.com/d/k-Kr4zqb3P5QQT67PtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqpJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdFYMc>
or, via email, send a message with subject or body 'help' to
cisco-voip-request at puck.nether.net<mailto:cisco-voip-request at puck.nether.net>
You can reach the person managing the list at
cisco-voip-owner at puck.nether.net<mailto:cisco-voip-owner at puck.nether.net>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. Re: CUCM Patch Insight (NateCCIE)
2. Jabber/CIPC and QoS (Ben Amick)
3. Re: Jabber/CIPC and QoS (Lelio Fulgenzi)
4. Re: Jabber/CIPC and QoS (Ben Amick)
5. Re: Jabber/CIPC and QoS (Hodgeman, Samuel)
6. Re: Jabber/CIPC and QoS (NateCCIE)
7. Re: Jabber/CIPC and QoS (Ryan Huff)
8. LiveData enhancements in UCCX 11.0 and 11.5
(Abhiram Kramadhati (akramadh))
9. Re: Jabber/CIPC and QoS (Ben Amick)
10. Re: Jabber/CIPC and QoS (Ryan Huff)
11. Re: Jabber/CIPC and QoS (Ben Amick)
12. Re: Jabber/CIPC and QoS (Ryan Huff)
13. Re: Jabber/CIPC and QoS (Evgeny Izetov)
14. 7921g-w-k9 -> 7921g-a-k9 (Tim Warnock)
15. Re: Jabber/CIPC and QoS (Ben Amick)
16. Re: Jabber/CIPC and QoS (Lelio Fulgenzi)
17. Re: Jabber/CIPC and QoS (Ryan Huff)
18. Re: 7921g-w-k9 -> 7921g-a-k9 (Ben Amick)
----------------------------------------------------------------------
Message: 1
Date: Tue, 3 Jan 2017 10:33:39 -0700
From: NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com>>
To: "'Jeffrey McHugh'" <jmchugh at fidelus.com<mailto:jmchugh at fidelus.com>>, "'Tim Franklin'"
<tim at tripplehelix.net<mailto:tim at tripplehelix.net>>, <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] CUCM Patch Insight
Message-ID: <062901d265e7$8652f4c0$92f8de40$@gmail.com<http://cp.mcafee.com/d/2DRPoQcCQm7CbFFKcfCXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CSjrNEVdTWWbybarz1EVhdTdw0O8DOVKQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6UKdGDJ2D>>
Content-Type: text/plain; charset="utf-8"
I would wait for SU2 at this point. It will be soon.
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Jeffrey McHugh
Sent: Tuesday, January 03, 2017 8:53 AM
To: Tim Franklin <tim at tripplehelix.net<mailto:tim at tripplehelix.net>>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUCM Patch Insight
Just did an SU1 upgrade, no issues reported but look into bug CSCux90747 depending on your esxi versions
I would expect SU2 soon as its named in the Expressway 8.9 release notes for some MRA feature preview
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Tim Franklin
Sent: Tuesday, January 3, 2017 10:44 AM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> <mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] CUCM Patch Insight
Just curious if anyone on this list has any feedback as to the stability of CUCM 11.5(1)SU1. I'm planning my upgrades out and I'm a bit leery to deploy it given that it's been out since November. While that speaks to no large defects to cause a deferral notice I'm also wondering if another SU is on the horizon?
Thanks
Jeffrey McHugh | Sr. Collaboration Consulting Engineer | VCP-DCV, CCNP Collaboration
<http://www.fidelus.com/<http://cp.mcafee.com/d/avndygQcz9J5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJwSYqejt-KyUyOCUMqekjtPo09Si7DJQVv3tFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdUnpJeONP>>
Fidelus Technologies, LLC
Named <http://www.fidelus.com/fidelus-technologies-named-best-unified-communications-provider-in-the-usa/<http://cp.mcafee.com/d/FZsS86Qm7CbFFKcfCXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CTPrNEVdTWWbybarz1EVhdTdw0Dp8uuTjBYtAxVXt2Y_Ijxk-F6nQbMRnQ2V3WjbJMAXbQ2WWHs9mSsGMEnmzkP93UBVgbP9-nrFK6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrYUwulxMg>> Best UC Provider in the USA
240 West 35th Street, 6th Floor, New York, NY 10001
+1-212-616-7801<tel:%2B1-212-616-7801> office | +1-212-616-7850<tel:%2B1-212-616-7850> fax | <http://www.fidelus.com/<http://cp.mcafee.com/d/2DRPoQd3hJ5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJMSYqejt-KyUyOCUMqekjtPo09Si7DJQVv3tFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdzS9S>> www.fidelus.com<http://cp.mcafee.com/d/2DRPow76Qm7CbFFKcfCXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CNNJUQsCXZt5N5BdNwQsECXCM0jIAffrFOVKQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6PNUF0vqu>
<http://www.linkedin.com/company/fidelus-technologies/products<http://cp.mcafee.com/d/2DRPow739J5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJUSYqejt-KyUyOCUMqekjtPo08-k2LEixO-bHr0JzIAffrEnDZysaDR8O-CbhGwTqt3tFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdFG6u>> <http://www.twitter.com/FidelusUCC<http://cp.mcafee.com/d/FZsScyhJ5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FIQsCTzhOrLRQn4mkT63hOyrKr01jciDfUYLwL93PSW1ci4ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdJHdfWBYi>> <http://www.facebook.com/FidelusUCC<http://cp.mcafee.com/d/1jWVIq6xAe6jqb3P5QQT67PtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqdPrNEVdTWWbybarz1EVhdTdw0DtJV2JiLbUbOgYZKwj4x8TqlblbCqOmbAaJMJZ0kIToHMd9_7wqrp78TuudwLQzh0qmXiFqFsPmiNFtd404qg8v718d2MAq8dwwq807Gc6Sn3vxTfwBrD>> <http://www.youtube.com/FidelusTraining<http://cp.mcafee.com/d/2DRPowrhouoKCCUM-rKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrp7cKc3DD-LPbZT7TxTnKnjjosVYQsLThhLR4kRHFGTusVkffGhBrwqrhhdL6zATvHEK8IFKc6zB4TsS02blrCSg_BY5V8uuTg4NSk9g8CXiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUr351jzPT>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0001.html<http://cp.mcafee.com/d/1jWVIe6x8i6jqb3P5QQT67PtPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqapJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3smAJYhfbiFqFsPmiSreuS9G_2tcjKyeKztD20XXueLrdDfr4RvxcLuZQu1NKQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6PREboVEC>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1989 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0005.png<http://cp.mcafee.com/d/FZsS82hJ5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJ5ASYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKPx0tZL7nJCPDJyqLMCnLuX_bg8CXiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrJ5z6>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1500 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0006.png<http://cp.mcafee.com/d/k-Kr4x0e3xASyMYNtddNxYTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSyMrud79K_nhshpjsod7a9KVIDeqR4INpKNnwqj-f0T5Fbv4jOQGmGncRAJCPDJyqLMDj4XEzHETpMwe-TzHSPpPSNdnUjbTLtPBE4jtFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdJPaTf-pN>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1526 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0007.png<http://cp.mcafee.com/d/avndy1J5xVyWqrz3VKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJ5YSYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKPx0tZL7nJCPDJyqLMCnLuUXBE4jtFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdHfqj0Jdb>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1450 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0008.png<http://cp.mcafee.com/d/5fHCNAqdEIfcnjjsovdTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndIzCn61PP_nVB-XzXMXHTbFFIes-qenXEETWyaqRQRrLesG7DR8OJMddEK6TzhOrLRQn4mkT63hOyrKr9PCJhbcmrIlU6A_zMdNqiTN4YJaBGBPdpbpIVXoCHY9QNeW8WWdSs83LJUWZISsZIjl-4OZXTuVq14TqlblbCqOmbAaJMJZ0kIToHMd9_7wqrp78TuudwLQzh0qmXiFqFsPmiNFtd404qg8v718d2MAq8dwwq807Gc6Sn3sYDBnprqKTZu>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1632 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/b7ece70c/attachment-0009.png<http://cp.mcafee.com/d/FZsSd6Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CQhNJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3smAJYhfbiFqFsPmiSreuS9G_2tcjKyeKztD20XXueLrdDfr4RvxcLuZPhPOQ29KQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6UmZUv97LE4AQ>>
------------------------------
Message: 2
Date: Tue, 3 Jan 2017 21:25:20 +0000
From: Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>
To: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] Jabber/CIPC and QoS
Message-ID:
<820C24BFE55F434C97807C60D4647ACE0F9D3DBB at E2k10-MB-HT1.humanarc.com<mailto:820C24BFE55F434C97807C60D4647ACE0F9D3DBB at E2k10-MB-HT1.humanarc.com>>
Content-Type: text/plain; charset="us-ascii"
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/4d9a63d8/attachment-0001.html<http://cp.mcafee.com/d/FZsS92gQ96Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CQnzrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6UJ9rUyumBiRiVCIBISsZIjl-4WoDt4tt6Xec86zDn6k7ISsZIjl-4OZXThU76XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrhqni1KHj>>
------------------------------
Message: 3
Date: Tue, 3 Jan 2017 21:35:41 +0000
From: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
To: Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>, Cisco VoIP Group
<cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
Message-ID:
<YTOPR01MB0251F94A8E59508021DD7D21AC6E0 at YTOPR01MB0251.CANPRD01.PROD.OUTLOOK.COM<mailto:YTOPR01MB0251F94A8E59508021DD7D21AC6E0 at YTOPR01MB0251.CANPRD01.PROD.OUTLOOK.COM>>
Content-Type: text/plain; charset="iso-8859-1"
good question Ben. i look forward to reading this thread.
i've been meaning to read up on mediaNet, and it seems it's more required than not, especially for QoS.
are you suggesting (with option 3) that there is software you can install on desktops? what about mobile devices?
QoS, both wired and wireless, will definitely be an interesting challenge.
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519-824-4120 Ext 56354<tel:519-824-4120%20Ext%2056354>
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://cp.mcafee.com/d/avndy0s73gArhouoKCCUMUrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrp7cKc3DD-LPbZT7TxTnKnjjosVYQsLThhLR4kRHFGTusVkffGhBrwqrhd79JUQsCXZt5N5BdNwQsECXCM0jtibvDH4-JKmJgTqlblbCqOmbAaJMJZ0kIToHMd9_7wqrp78TuudwLQzh0qmXiFqFsPmiNFtd404qg8v718d2MAq8dwwq807Gc6Sn3rccsL59Vmz-x>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> on behalf of Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>
Sent: Tuesday, January 3, 2017 4:25 PM
To: Cisco VoIP Group
Subject: [cisco-voip] Jabber/CIPC and QoS
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/0a34315c/attachment-0001.html<http://cp.mcafee.com/d/1jWVIq4zqb3P5QQT673tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqtPrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6UJ9rUyumBiRiVCIBISsZIjl-4WoDt4tt6XenRBxB5-SreuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdKt1CZLGM>>
------------------------------
Message: 4
Date: Tue, 3 Jan 2017 22:02:42 +0000
From: Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, Cisco VoIP Group
<cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
Message-ID:
<820C24BFE55F434C97807C60D4647ACE0F9D3E0F at E2k10-MB-HT1.humanarc.com<mailto:820C24BFE55F434C97807C60D4647ACE0F9D3E0F at E2k10-MB-HT1.humanarc.com>>
Content-Type: text/plain; charset="us-ascii"
From what I understand, it's not so much as "software" as it is a plugin for jabber that enables Jabber to send the medianet signaling. I don't believe it's a function of iOS/android Jabber though, but I could be mistaken
Ben Amick
Telecom Analyst
From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>]
Sent: Tuesday, January 03, 2017 4:36 PM
To: Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>; Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: Jabber/CIPC and QoS
good question Ben. i look forward to reading this thread.
i've been meaning to read up on mediaNet, and it seems it's more required than not, especially for QoS.
are you suggesting (with option 3) that there is software you can install on desktops? what about mobile devices?
QoS, both wired and wireless, will definitely be an interesting challenge.
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519-824-4120 Ext 56354<tel:519-824-4120%20Ext%2056354>
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca><mailto:lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
www.uoguelph.ca/ccs<http://cp.mcafee.com/d/2DRPoQ91MwrhouoKCCUMUrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrp7cKc3DD-LPbZT7TxTnKnjjosVYQsLThhLR4kRHFGTusVkffGhBrwqrjhdL6zATvHEK8IFKc6zB4TsS02rGhrYZoDRJORG6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrwtT4><http://www.uoguelph.ca/ccs<http://cp.mcafee.com/d/1jWVIpdEIfcnjjsosdTdEEILIFzxO9EVdEEILIFzDDSjqabbXPUVVZMSyyUqejhPuZQrCO6GOIl1hdJnor6TbCOrqKMSdKndIzCn61PP_nVB-XzXMXHTbFFIes-qenXEETWyaqRQRrLesG7DR8OJMddFFCTzhOrLRQn4mkT63hOyrKr01dR8J-uIjWSVqR3tFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdURoXVnvH>>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net><mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>>> on behalf of Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com<mailto:bamick at HumanArc.com>>>
Sent: Tuesday, January 3, 2017 4:25 PM
To: Cisco VoIP Group
Subject: [cisco-voip] Jabber/CIPC and QoS
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
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/9591b6cd/attachment-0001.html<http://cp.mcafee.com/d/FZsS72hJ5xVyWqrz3xKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJdASYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKPxEVvd7a91OO6reuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdLoauYdUu>>
------------------------------
Message: 5
Date: Tue, 3 Jan 2017 22:13:15 +0000
From: "Hodgeman, Samuel" <shodgeman at xo.com<mailto:shodgeman at xo.com>>
To: Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>, Cisco VoIP Group
<cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
Message-ID:
<94004f6f0f8646e7a51539636329908b at TXPLANEXCH101.corp.inthosts.net<mailto:94004f6f0f8646e7a51539636329908b at TXPLANEXCH101.corp.inthosts.net>>
Content-Type: text/plain; charset="us-ascii"
For option 1, using Windows... this can be implemented with Group Policies, taking it out of the hands of end users, and can be associated with specific application executable and/or specific IP address source/destination.
- Sam H
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Ben Amick
Sent: Tuesday, January 03, 2017 3:25 PM
To: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] Jabber/CIPC and QoS
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/3ef7729c/attachment-0001.html<http://cp.mcafee.com/d/2DRPoA92gQ76Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CQS3rNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6UJ9rUyumBiRiVCIBISsZIjl-4WoDt4tt6Xec-We79CzCSreuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdKKKK>>
------------------------------
Message: 6
Date: Tue, 3 Jan 2017 17:53:14 -0700
From: NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com>>
To: Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
Message-ID: <05C8F1E2-B3DA-435C-BAB4-3C8278A0A726 at gmail.com<mailto:05C8F1E2-B3DA-435C-BAB4-3C8278A0A726 at gmail.com>>
Content-Type: text/plain; charset="utf-8"
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 <bamick at HumanArc.com<mailto:bamick at HumanArc.com>> 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
> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip<http://cp.mcafee.com/d/k-Kr41ASyMYNtddNxMTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSC-rud79K_nhshpjsod7a9KVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oTqlblbCqOmbAaJMJZ0kIToHMd9_7wqrp78TuudwLQzh0qmXiFqFsPmiNFtd404qg8v718d2MAq8dwwq807Gc6Sn3oNSWLrXW>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170103/0da1ffef/attachment-0001.html<http://cp.mcafee.com/d/k-Kr3zqb3P5QQT673tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jqrxJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3smAJYhfbiFqFsPmiSreuS9G_2tcjKyeKztDbEqyWXXKreuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdUbpOd1FA>>
------------------------------
Message: 7
Date: Wed, 4 Jan 2017 01:39:30 +0000
From: Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>>
To: NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com>>
Cc: Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>, Cisco VoIP Group
<cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
Message-ID:
<BLUPR18MB0482767CF5DE727DDEE526FEC5610 at BLUPR18MB0482.namprd18.prod.outlook.com<mailto:BLUPR18MB0482767CF5DE727DDEE526FEC5610 at BLUPR18MB0482.namprd18.prod.outlook.com>>
Content-Type: text/plain; charset="us-ascii"
It's a shame really ... MPLS is far superior IMO, for many reasons. Call it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public Internet.
Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a public Comcast or Time Warner/Charter package.
On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com><mailto:nateccie at gmail.com<mailto:nateccie at gmail.com>>> wrote:
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 <bamick at HumanArc.com<mailto:bamick at HumanArc.com<mailto:bamick at HumanArc.com>>> 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
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
https://puck.nether.net/mailman/listinfo/cisco-voip<http://cp.mcafee.com/d/k-Kr3xESyMYNtddNxMTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSCedL6zATvHEK8IFKc6zB4TsSjDdqymoIToHMd9_7wrwCHIcfBisEeROQGmGncRAIrJaBGBPdpb5O5mUm-wamrIlU6A_zMddIzArLf6MnWhEwdbtFkJkKpH9oQKCy02d84fzwA6xoid46Mgd403R63rbxK3usreMyXzZC>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
https://puck.nether.net/mailman/listinfo/cisco-voip<http://cp.mcafee.com/d/2DRPoA92gO96Qm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CQTzrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUr1zcmvasqGTf>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/f9b9e92b/attachment-0001.html<http://cp.mcafee.com/d/1jWVIi3xASyMYNtddNxMTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSCqejrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6UJ9rUyumBiRiVCIBISsZIjl-4WoDt4tt6X6eCzAwqevd7ap3dDfr4RvxcLuZQu1NKQGmGncRAIn8lrxrW0FpKNnwqj-f0QSOehKYYr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6YTzlm_uR>>
------------------------------
Message: 8
Date: Wed, 4 Jan 2017 01:48:30 +0000
From: "Abhiram Kramadhati (akramadh)" <akramadh at cisco.com<mailto:akramadh at cisco.com>>
To: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] LiveData enhancements in UCCX 11.0 and 11.5
Message-ID: <5C88B902-AED4-4603-8707-A2BAE18A1181 at cisco.com<mailto:5C88B902-AED4-4603-8707-A2BAE18A1181 at cisco.com>>
Content-Type: text/plain; charset="utf-8"
Hi all,
Happy 2017!
We just published a Field Notice about LiveData stabilization enhancements done in 11.0(1)SU1 and 11.5(1)ES1.
http://www.cisco.com/c/en/us/support/docs/field-notices/642/fn64240.html
So, if you are on 11.0 or 11.5, our recommendation is to move to the above-mentioned releases. You could be running on 11.0/11.5 with no LD issues ? this is just a proactive measure.
[http://www.cisco.com/c/dam/assets/email-signature-tool/logo_07.png?ct=1421802598153]
Abhiram Kramadhati
Technical Solutions Manager
Customer Solutions Success team, CCBU
akramadh at cisco.com<mailto:akramadh at cisco.com><mailto:akramadh at cisco.com<mailto:akramadh at cisco.com>>
Phone: +61 2 8446 6257<tel:%2B61%202%208446%206257>
CCIE Collaboration - 40065
Cisco Systems Australia Pty Limited
The Forum
201 Pacific Highway
2065
St Leonards
Australia
Cisco.com<http://www.cisco.com/web/AU/>
[http://www.cisco.com/assets/social_media_icons/linkedin-16x16.png]<http://wwwin.cisco.com/marketing/corporate/brand/intelbrand/brandstrat/signature/Insert%20your%20LinkedIn%20link>
[http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think<http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif%5dThink> before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
Please click here<http://www.cisco.com/web/about/doing_business/legal/cri/index.html> for Company Registration Information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/fb4a3136/attachment-0001.html<http://cp.mcafee.com/d/5fHCN8e4wUSyMYNtddNxMTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSOepso7ffZvCnXKfL3KLsKCCMVPVEVvKyzvG8FHnjlKYVOEuvkzaT0QSPsSYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKNzF1zmkmncSsZIjl-4OZXThU76XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrS1LI>>
------------------------------
Message: 9
Date: Wed, 4 Jan 2017 02:15:06 +0000
From: Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>
To: Ryan Huff <ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>>, NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com>>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
Message-ID:
<820C24BFE55F434C97807C60D4647ACE0F9DE054 at E2k10-MB-HT1.humanarc.com<mailto:820C24BFE55F434C97807C60D4647ACE0F9DE054 at E2k10-MB-HT1.humanarc.com>>
Content-Type: text/plain; charset="us-ascii"
Yeah, I have the luck of having MPLS right now, and I don't see us going iWAN for a while for various reasons. QoS on the WAN right now even isn't my issue, it's QoS on the LAN. Right now we have a relatively flat network, and certain segments of our troupe *cough*developers*cough* seems to have made our internal traffic ugly, to the point that I may have to do an analysis of it, as we're having just random periods here and there where calls just have horrible quality, of the type you normally see fixed by QoS
Ben Amick
Telecom Analyst
From: Ryan Huff [mailto:ryanhuff at outlook.com<mailto:ryanhuff at outlook.com>]
Sent: Tuesday, January 03, 2017 8:40 PM
To: NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com>>
Cc: Ben Amick <bamick at HumanArc.com<mailto:bamick at HumanArc.com>>; Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Jabber/CIPC and QoS
It's a shame really ... MPLS is far superior IMO, for many reasons. Call it iWAN, DMVPN, AutoVPN .... whatever, it is still as Nate says, public Internet.
Try getting a 30 or 60 minute SLA with escalation after 15 minutes from a public Comcast or Time Warner/Charter package.
On Jan 3, 2017, at 7:53 PM, NateCCIE <nateccie at gmail.com<mailto:nateccie at gmail.com><mailto:nateccie at gmail.com<mailto:nateccie at gmail.com>>> wrote:
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 <bamick at HumanArc.com<mailto:bamick at HumanArc.com<mailto:bamick at HumanArc.com>>> 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
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
https://puck.nether.net/mailman/listinfo/cisco-voip<http://cp.mcafee.com/d/avndy0OcCQm7CbFFKce6XCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCShPbz0VV_HYO_tNZUtRXBQQS7evd7bZQkrZh5dqWqJTDel3PWApmU6CSkjrNEVdTWWbybarz1EVhdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jr8V6XPNI5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUrnghujSVnQnp7><http://cp.mcafee.com/d/avndzgOcxMQrhoupod7b9EV79CXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCSnQTXeffZvzhOZsQsFThWZOWr8V7AhPdTC7xTkhjmKCHtBfBgY-F6lK1FJ4SCrLOb0VVdOXMWVKVIDeqR4INpKNnwqj-f0T1dnoovaAVgtHBFkJkKpH9oT4JI2rrHEaGTc-JiLbCQnAkPhOr1vF6y0QJSBiRiVCIBziWq808Qwg-e2gq5x8Qgr10Qg0fkodIK6Y1tK-rNm>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
https://puck.nether.net/mailman/listinfo/cisco-voip<http://cp.mcafee.com/d/1jWVIi41Ae6zqb3P5QQT673tPqabbXaoUsyqejqabbXaoVVZASyyO-Y-euvsdEEK6zAQsTLt6VIxGIH5gkjrlS6NJOVICSHIdzrBPr8VBNwsY_R-pvKU-YeWZOWqr3DfCzB-Wad-EyCJtdmXPDaxVZicHs3jrapJUQsCXZt5N5BdNwQsECXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdyMRDJKUO><http://cp.mcafee.com/d/2DRPoOd2hJ5xVBwQsICzAsCrKrhhpvpj73AjhOrhhpvpj7ffICQkmnTDNPPXxJ55MQsCzCZXETdAdlBoG2yrqKMSdKndASRtxIrsKrpvjvIUY_R-d7bRPhODt7HTbFIzAuh7cTuou7th5dqWqJSk-l3PWApmU6CQPqpK_8I3DATbL3HCXCOsVHkiP5CX5u1FfUY3s4RtxxYGjB1SKmBiRiVCIBzsiSM9JKKwGHsPWRaYKrhuhjd79I5-Aq83iTqlblbCqOmdbFEw0zi13UU91Em4zh1I43h00ZhwSOUryKrT3IPkd-jE>
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170104/74ba53d8/attachment-0001.html<http://cp.mcafee.com/d/FZsScxMw91NJ5xVyWqrz3xKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJAsOUMeuvW_cLTsvu7tuVtddxPDPhO_t56_khjmKCHtVPBgY-F6lK1FJBASYqejt-KyUyOCUMqekjtPpesRG9pyPtyL0QDYu1Kbim-8DBFkJkKpH9rdDfr4RvxeC9Th7nhKNwVwxHXa3SreuS9G_2puZXEY3ztFkJkKpH9oKgGT2TQ1iPtyL0QDYu1FJAsztVUS2_id41FrJaBGBPdpb6BQQg0hF0xYs4wQb2hEwS21Ew0uEMrpsdAi0c>>
------------------------------
Message: 10
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170110/acb4ada1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OutlookEmoji-?.png
Type: image/png
Size: 390 bytes
Desc: OutlookEmoji-?.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170110/acb4ada1/attachment.png>
More information about the cisco-voip
mailing list