<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Jabber for Android QoS marking in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2118998#M179577</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You don't have to worry about if Jabber marks the upstream IP traffic. You, instead, need to care about two other things:&lt;/P&gt;&lt;P&gt;- The Jabber is running on WMM copmatible client; that it will send correct 802.11e data for your priority traffic.&lt;/P&gt;&lt;P&gt;- Your SSID is configured correctly for QoS (Platinum/Voice QoS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the&amp;nbsp; 802.11e data sent by the client is voice data, and your SSID is mapped for voice QoS then the upstream traffic will automatically be mapped for the corresponding voice DSCP (EF - 46).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this helpful document:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00807e9717.shtml" rel="nofollow"&gt;http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00807e9717.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amjad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;p.s: the above is correct for Cisco Wireless LAN Controllers. If you use other vendor or standalone APs then let us know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: blue;"&gt;Rating useful replies is more useful than saying &lt;SPAN style="color: green;"&gt; "&lt;SPAN style="text-decoration: underline;"&gt;Thank you&lt;/SPAN&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 02 Dec 2012 05:59:15 GMT</pubDate>
    <dc:creator>Amjad Abdullah</dc:creator>
    <dc:date>2012-12-02T05:59:15Z</dc:date>
    <item>
      <title>Jabber for Android QoS marking</title>
      <link>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2118997#M179576</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I haver a question about Jabber for Android.&lt;/P&gt;&lt;P&gt;Does Jabber mark upstream IP Packet with DSCP value?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would use Jabber on Android Tablet in a WLAN. I need DSCP marking to use 802.11e.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another question: where I find a list of "Jabber compatible" Android device?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 06:08:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2118997#M179576</guid>
      <dc:creator>carletto.riemma</dc:creator>
      <dc:date>2021-07-04T06:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber for Android QoS marking</title>
      <link>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2118998#M179577</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You don't have to worry about if Jabber marks the upstream IP traffic. You, instead, need to care about two other things:&lt;/P&gt;&lt;P&gt;- The Jabber is running on WMM copmatible client; that it will send correct 802.11e data for your priority traffic.&lt;/P&gt;&lt;P&gt;- Your SSID is configured correctly for QoS (Platinum/Voice QoS).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the&amp;nbsp; 802.11e data sent by the client is voice data, and your SSID is mapped for voice QoS then the upstream traffic will automatically be mapped for the corresponding voice DSCP (EF - 46).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this helpful document:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00807e9717.shtml" rel="nofollow"&gt;http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00807e9717.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Amjad&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;p.s: the above is correct for Cisco Wireless LAN Controllers. If you use other vendor or standalone APs then let us know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: blue;"&gt;Rating useful replies is more useful than saying &lt;SPAN style="color: green;"&gt; "&lt;SPAN style="text-decoration: underline;"&gt;Thank you&lt;/SPAN&gt;"&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 02 Dec 2012 05:59:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2118998#M179577</guid>
      <dc:creator>Amjad Abdullah</dc:creator>
      <dc:date>2012-12-02T05:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber for Android QoS marking</title>
      <link>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2118999#M179578</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Carletto,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no way for us to mark wireless traffic (as we normally do in wired networking). It's depend on the application &amp;amp; wireless network driver of the WMM capable device.Also original DSCP marking of the packet will not be the deciding factor when it comes to wireless QoS. It will be the 802.11e/WMM_UP set up in 802.11 frame will determine who gets the priority in wireless media.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I haven't test this with Android. But I have tested this with iphone4 with platinum QoS settings on WLC.Even though we expect iphone will classify RTP traffic (voice) into 802.11e/WMM_UP 6 &amp;amp; then AP map this into EF as per cisco baselining, you will see IPhone will clasify this traffic as video (WMM_UP of 5). This is true for IP communicator used in windows laptop as wireless client. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Therefore this traffic will go as AF41 (not EF) in outer CAPWAP header from AP to WLC and subsequenty wired site of your network(again all depend on how you configure QoS on your AP &amp;amp; WLC connected swtich ports &amp;amp; original packet DSCP value changes when it comes to destingation). I would assume Android devices behave the same (but you have to test it to confirm)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Certain Applications (like Polycom Real Presence - Video Conference client application) do not these classification. I used it for ipad2 for testing &amp;amp;&amp;nbsp; all video traffic go as Best Effort in 802.11 frames. Therefore those sort of traffic will not get any priority over other traffic (as everyhing goes as BE) in wireless media.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 07:04:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2118999#M179578</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2012-12-06T07:04:32Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber for Android QoS marking</title>
      <link>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2119000#M179579</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Rasik: in conclusion, it is application dependent ti mark or not the 802.11 header with platinum traffic.&lt;BR /&gt;Is that what you want to say?&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 15 Dec 2012 15:05:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2119000#M179579</guid>
      <dc:creator>Amjad Abdullah</dc:creator>
      <dc:date>2012-12-15T15:05:50Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber for Android QoS marking</title>
      <link>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2119001#M179580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hi Amjad,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not exactly, this is how I understand it &amp;amp; summarize ....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Within the wireless cell traffic get prioratized based on 802.11e or WMM User Priority value(UP).AP does not have any control over what UP values set by clients on its wireless frame.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. How end user device set WMM_UP in wireless frame is application/ device's driver dependant.( eg RTP traffic coming from 7921 phone set to UP=6 in 802.11 frame header where&amp;nbsp; as RTP traffic coming from Jabber client in iPhone set UP=5 in 802.11 frame header )&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Point number 2 is the one I wanted to highlight based on my testing conducted. Hope this is clear... &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 16 Dec 2012 07:09:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/jabber-for-android-qos-marking/m-p/2119001#M179580</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2012-12-16T07:09:55Z</dc:date>
    </item>
  </channel>
</rss>

