<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Yes, I've noticed that...the whole part about it not being listed means it's not supported. While I can appreciate that at a first level support, they should be able to escalate it within a reasonable time to the business unit responsible for review.<br><br>Let's face it, documentation will never be up to date. As customers we have to expect that. But at the same time if someone isn't going to update the documentation throughout the product lifecycle, they should at least review it when a customer points out an issue. And the documentation should be updated quickly after that. <br><br><br><span><br><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Scott Voll" <svoll.voip@gmail.com><br><b>To: </b>"Wes Sisk" <wsisk@cisco.com><br><b>Cc: </b>"James Brown" <James.Brown@barclayswealth.com>, cisco-voip@puck.nether.net, "Lelio Fulgenzi" <lelio@uoguelph.ca>, "Ed Leatherman" <ealeatherman@gmail.com><br><b>Sent: </b>Monday, April 4, 2011 6:04:30 PM<br><b>Subject: </b>Re: [cisco-voip] Phone/CM Locale Questions<br><br>Just had a Telepresence with John Hernandez last week. Documentation was one of the three things we talked about or the lack there of. <div><br></div><div><Rant></div><div><br></div><div>Oh, and Cisco is now on the kick of if it's not listed, it's not supported. even if the version numbers are the same........ if you can't find a doc that list support, its not.</div>
<div><br></div><div>As I told John last week, Microsoft products support there other Microsoft products. Shouldn't Cisco.</div><div><br></div><div></Rant></div><div><br></div><div>Scott</div><div><br><br><div class="gmail_quote">
On Thu, Mar 31, 2011 at 8:30 AM, Wes Sisk <span dir="ltr"><<a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>
Inline, ws.<div class="im"><br>
<br>
On 3/30/2011 2:16 PM, <a href="mailto:James.Brown@barclayswealth.com" target="_blank">James.Brown@barclayswealth.com</a> wrote:
<blockquote>
<pre>All,
Is anyone else finding the documentation around locales slightly hit and miss?
</pre>
</blockquote></div>
ws: Yes. Please voice this to your Cisco account team. There is
acute attention and action in the documentation arena at the
moment. Ears are open for customers who speak up.<div class="im"><br>
<blockquote>
<pre>So far, I have...
* Phone Only locales control the endpoint LCD language
* CM Locales provide cadence and CCMUser language
* CM Locales require an update with each CUCM major version
* PO Locales require an update with the endpoint firmware
Could anyone clarify whether a PO update really has to be applied when SCCP firmware is upgraded? </pre>
</blockquote></div>
ws: <br>
<p><b>Q: Do I need to install a new Phone Only locale every time
after I upgrade my IP phone firmware?</b></p>
Localization team only releases Phone Only Locales for FW with
changes on phone dictionaries or internationalization. In another
words, we do not have POLI release for every FW release. When
customer upgrades the firmware without upgrade their CUCM, they
should install the Phone Only locale with the same major.minor
number with the new FW. For example, if they upgrade the from FW
8.5.3 (with POLI 8.5.3) to FW 8.5.4, POLI 8.5.3 is also good for FW
8.5.4. If they upgrade FW from 8.5.4 to 9.0.1, they will need to
install POLI 9.0.1.
<div class="im"><blockquote>
<pre>And would this update need to be applied to all nodes, or just the TFTP servers? </pre>
</blockquote></div>
ws: <br>
<p><b>Q: Do locales need to be installed on every Node?</b></p>
<p>Cisco Unified Communications Locale Installer MUST be applied to
each and every Cisco Unified Communications Manager server in a
cluster, starting with the publisher. After installation has
completed, it is essential to reboot each and every platform in
order for all user and network locale changes to become fully
activated. <br>
</p>
<p><b>Q: How to use Phone Only Locales?</b></p>
<p>Cisco Unified Communications Locale Installer for Cisco Unified
IP Phones ensures localised phones are kept up-to-date with the
latest dictionaries after the firmware is upgraded. <ins>The full
Cisco Unified Communications Locale Installer for Cisco Unified
Communications Manager must be installed prior to installation
of a Phone Only locale installer</ins>. For example, with CUCM
5.1 and Firmware 8.4.3, CUCM LI 5.1.x need to be installed first,
then install Phone Only LI 8.4.3 for firmware updates. <br>
</p><div class="im">
<blockquote>
<pre>Is a cluster reboot really needed, just to load a few additional dictionary files to the phones?
</pre>
</blockquote></div>
ws: <br>
<p><b>Q: Do locales need to be installed on every Node?</b></p>
<p>Cisco Unified Communications Locale Installer MUST be applied to
each and every Cisco Unified Communications Manager server in a
cluster, starting with the publisher. <b>After installation has
completed, it is essential to reboot each and every platform in
order for all user and network locale changes to become fully
activated. </b><br>
</p><div class="im">
<blockquote>
<pre>Thanks in advance for any assistance.
Regards
James.
Barclays Wealth is the wealth management division of Barclays Bank PLC. This email may relate to or be sent from other members of the Barclays Group.
The availability of products and services may be limited by the applicable laws and regulations in certain jurisdictions. The Barclays Group does not normally accept or offer business instructions via internet email. Any action that you might take upon this message might be at your own risk.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this email or its attachments.
Internet communications are not guaranteed to be secure or without viruses. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays Group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group.
Barclays Bank PLC. Registered in England and Wales (registered no. 1026167).
Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom.
Barclays Bank PLC is authorised and regulated by the Financial Services Authority.
_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</div></div>
<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><br>
<br></blockquote></div><br></div>
</div></body></html>