<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">I always struggle with the competing schools of thought on keeping things up to date.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The network guys don’t want to update anything because of more bugs, but I still feel that’s old school where we weren’t talking about the same level of exposure and frequency of updates. I like to keep up to date because I don’t like digging
a hole for myself on features, user doc, bug resolutions, compat, device packs etc. And the number of severe issues has rounded off, at least for UC where it seems the platforms are largely mature.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The 11.5 train has been great as far as not having too many issues, and having a good set of features and such backported into them from 12/12.5.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">APNs are a usability thing with Jabber for sure, I don’t know how anyone lives with that app and not having that. It would be like going back in time when I had my StarTAC and had to look at the flashing LED to see if I’d wandered out of
service or into an expensive “Roaming” area just to make sure I could receive a phone call. No thanks.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Looking forward to future support for push on Android too so we can catch those up.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> cisco-voip <cisco-voip-bounces@puck.nether.net>
<b>On Behalf Of </b>Anthony Holloway<br>
<b>Sent:</b> Friday, May 15, 2020 11:11 AM<br>
<b>To:</b> Lelio Fulgenzi <lelio@uoguelph.ca><br>
<b>Cc:</b> cisco-voip voyp list <cisco-voip@puck.nether.net><br>
<b>Subject:</b> Re: [cisco-voip] Field Notice: FN - 70555 - Legacy VoIP Mode and iOS 13 Apple Push Notification Service Changes That Affect Cisco Jabber, Cisco Webex Teams, Cisco Unified Communications Manager and IM & Presence Service, and Cisco Expressway
- Software...<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">What's funny is, this has been going on for like 4 years now.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">But just like we, as kids, always waited until the last day to complete our science fair projects, we wait on securing LDAP, moving to O365's oauth, and enabling APNs.<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Fri, May 15, 2020 at 9:49 AM Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal"><br>
Like we didn’t have enough to worry about. <br>
<br>
<br>
<a href="https://www.cisco.com/c/en/us/support/docs/field-notices/705/fn70555.html" target="_blank">https://www.cisco.com/c/en/us/support/docs/field-notices/705/fn70555.html</a><br>
<br>
<br>
Sent from my iPhone<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>