<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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>And the ARC SC replacement simply stinks! Our receptionists say we have taken 3 steps backwards in functionality. Painful doesn’t begin to describe it..<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Geoffrey S. Rhodes<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Director of Information Technology<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Robinson, Bradshaw & Hinson, P.A.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>101 N. Tryon St., Suite 1900<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Charlotte, NC 28246-1900<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>704.377.2536<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>704.339.3488 (fax)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="mailto:grhodes@rbh.com">grhodes@rbh.com</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><img border=0 width=131 height=54 id="Picture_x0020_2" src="cid:image001.jpg@01CBD37D.DE30BD60"><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Buchanan, James<br><b>Sent:</b> Sunday, February 20, 2011 2:32 PM<br><b>To:</b> David Lee; cisco-voip@puck.nether.net<br><b>Subject:</b> Re: [cisco-voip] CallManager 7x to 8.5(1) and Attendant Console<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The old version is totally gone with 8. The service doesn’t exist—it has been totally removed. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>You will definitely want to get the 60 day trial of the new ARC AC. This is not a one-to-one replacement of the old Attendant Console, so you’ll want to see for yourself what you’re getting into. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'>James Buchanan </span></b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7E7E7E'>|</span><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'> Technology Manager, UC </span></b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7E7E7E'>|</span><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'> <b>South Region </b></span><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7E7E7E'>|</span><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'> Presidio Networked Solutions <br>12 Cadillac Dr, Suite 130, Brentwood, TN 37027 </span></b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7E7E7E'>|</span><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'> </span></b><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7E7E7E'><a href="mailto:jbuchanan@ctiusa.com">jbuchanan@presidio.com</a><br></span></b><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'>D: 615-866-5729</span></b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'> </span><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7E7E7E'>| <b>F:</b> </span><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'>615-866-5781</span></b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'> | </span><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7E7E7E'><a href="http://www.presidio.com/">www.presidio.com</a></span></b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#1F497D'> <o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";color:#7F7F7F'>CCIE #25863, Voice</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>David Lee<br><b>Sent:</b> Sunday, February 20, 2011 1:24 PM<br><b>To:</b> cisco-voip@puck.nether.net<br><b>Subject:</b> [cisco-voip] CallManager 7x to 8.5(1) and Attendant Console<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>The old AC is supported until v7.x IF you are doing an upgrade from previous versions. It is not supported if it's a fresh install, but if you have the installation file, it will probably work. Once you hit v8, the support is completely withheld. You will have to buy one of the re-branded ARC attendant consoles. Please see this link for more details. <br><br><a href="http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/end_of_life_notice_c51-499091.html">http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps7046/ps7282/end_of_life_notice_c51-499091.html</a><br><br>Just an FYI - the ARC ACs come with a 60 day trial, so the customer have some time to buy the license if they "forgot" to buy it. (Personally, I wouldn't try to get the old AC to work with v8 simply because Cisco specifically say it's not supported, and I don't want to install anything that is not officially supported.)<o:p></o:p></p><div><p class=MsoNormal>On Sun, Feb 20, 2011 at 12:00 PM, <<a href="mailto:cisco-voip-request@puck.nether.net">cisco-voip-request@puck.nether.net</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Send cisco-voip mailing list submissions to<br> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>or, via email, send a message with subject or body 'help' to<br> <a href="mailto:cisco-voip-request@puck.nether.net">cisco-voip-request@puck.nether.net</a><br><br>You can reach the person managing the list at<br> <a href="mailto:cisco-voip-owner@puck.nether.net">cisco-voip-owner@puck.nether.net</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of cisco-voip digest..."<br><br><br>Today's Topics:<br><br> 1. Re: CUCM Upgrade (Buchanan, James)<br> 2. Re: CUCM Upgrade (Lelio Fulgenzi)<br> 3. Re: CUCM Upgrade (Buchanan, James)<br> 4. Re: CUCM Upgrade (Lelio Fulgenzi)<br> 5. Re: CUCM Upgrade (Buchanan, James)<br> 6. Re: CCM7 day to day admin tips ? (Tony Edwards)<br> 7. Re: R: R: Phones randomply reset (Karen Cheng)<br> 8. CallManager 7x to 8.5(1) and Attendant Console<br> (Jason Aarons (US))<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sat, 19 Feb 2011 13:07:15 -0500<br>From: "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>><br>To: "H, Tim" <<a href="mailto:TimH@trstone.com">TimH@trstone.com</a>>, "<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>"<br> <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: Re: [cisco-voip] CUCM Upgrade<br>Message-ID:<br> <<a href="mailto:853687641CF93E40B362F112A3D8F3CE1724B85B@SOEXCH01.Presidio.Corp">853687641CF93E40B362F112A3D8F3CE1724B85B@SOEXCH01.Presidio.Corp</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>I had a customer do this last Sunday. The only change was the firmware. Attendant Console was unaffected. If you don't want to deal with the firmware, you could hard code the firmware on the phones until you are ready for the jump because the old firmware will stay on the server.<br><br>James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions<br>12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><mailto:<a href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</a>><br>D: 615-866-5729 | F: 615-866-5781 | <a href="http://www.presidio.com" target="_blank">www.presidio.com</a><<a href="http://www.presidio.com/" target="_blank">http://www.presidio.com/</a>><br>CCIE #25863, Voice<br><br><br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of H, Tim<br>Sent: Saturday, February 19, 2011 8:13 AM<br>To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Subject: [cisco-voip] CUCM Upgrade<br><br>All,<br><br>I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15. I'm aware of the firmware jump as you have to upgrade to 8.52sr1 or whatever, but is there anything else I need to be cautious about? Looks like the attendant console might change a bit in the version jump, but should still function?<br><br>Any other caveats that anyone have ran into would be helpful.<br><br>Thanks,<br>Tim<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/62f89fe9/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/62f89fe9/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 2<br>Date: Sat, 19 Feb 2011 13:09:30 -0500 (EST)<br>From: Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br>To: "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>><br>Cc: "<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: Re: [cisco-voip] CUCM Upgrade<br>Message-ID: <<a href="mailto:6328DC44-8AED-4C39-9EAF-F10F43FF6E88@uoguelph.ca">6328DC44-8AED-4C39-9EAF-F10F43FF6E88@uoguelph.ca</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>You could also change the device defaults firmware config parameters.<br><br>Sent from my iPhone<br><br>On Feb 19, 2011, at 1:07 PM, "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>> wrote:<br><br>> I had a customer do this last Sunday. The only change was the firmware. Attendant Console was unaffected. If you don?t want to deal with the firmware, you could hard code the firmware on the phones until you are ready for the jump because the old firmware will stay on the server.<br>><br>><br>><br>> James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions<br>> 12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><br>> D: 615-866-5729 | F: 615-866-5781 | <a href="http://www.presidio.com" target="_blank">www.presidio.com</a><br>><br>> CCIE #25863, Voice<br>><br>><br>><br>><br>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of H, Tim<br>> Sent: Saturday, February 19, 2011 8:13 AM<br>> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Subject: [cisco-voip] CUCM Upgrade<br>><br>><br>><br>> All,<br>><br>><br>><br>> I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15. I'm aware of the firmware jump as you have to upgrade to 8.52sr1 or whatever, but is there anything else I need to be cautious about? Looks like the attendant console might change a bit in the version jump, but should still function?<br>><br>><br>><br>> Any other caveats that anyone have ran into would be helpful.<br>><br>><br>><br>> Thanks,<br>><br>> Tim<br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/243b20d4/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/243b20d4/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 3<br>Date: Sat, 19 Feb 2011 13:13:11 -0500<br>From: "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>><br>To: Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br>Cc: "<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: Re: [cisco-voip] CUCM Upgrade<br>Message-ID:<br> <<a href="mailto:853687641CF93E40B362F112A3D8F3CE1724B85E@SOEXCH01.Presidio.Corp">853687641CF93E40B362F112A3D8F3CE1724B85E@SOEXCH01.Presidio.Corp</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>No, that won?t do it because the upgrade will change it to the latest version. It would need to be changed on the phones.<br><br>James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions<br>12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><mailto:<a href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</a>><br>D: 615-866-5729 | F: 615-866-5781 | <a href="http://www.presidio.com" target="_blank">www.presidio.com</a><<a href="http://www.presidio.com/" target="_blank">http://www.presidio.com/</a>><br>CCIE #25863, Voice<br><br><br>From: Lelio Fulgenzi [mailto:<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>]<br>Sent: Saturday, February 19, 2011 12:10 PM<br>To: Buchanan, James<br>Cc: H, Tim; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] CUCM Upgrade<br><br>You could also change the device defaults firmware config parameters.<br><br>Sent from my iPhone<br><br>On Feb 19, 2011, at 1:07 PM, "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><mailto:<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>>> wrote:<br>I had a customer do this last Sunday. The only change was the firmware. Attendant Console was unaffected. If you don?t want to deal with the firmware, you could hard code the firmware on the phones until you are ready for the jump because the old firmware will stay on the server.<br><br>James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions<br>12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><mailto:<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>><br>D: 615-866-5729 | F: 615-866-5781 | <a href="http://www.presidio.com" target="_blank">www.presidio.com</a><<a href="http://www.presidio.com" target="_blank">http://www.presidio.com</a>><br>CCIE #25863, Voice<br><br><br><br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of H, Tim<br>Sent: Saturday, February 19, 2011 8:13 AM<br>To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: [cisco-voip] CUCM Upgrade<br><br>All,<br><br>I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15. I'm aware of the firmware jump as you have to upgrade to 8.52sr1 or whatever, but is there anything else I need to be cautious about? Looks like the attendant console might change a bit in the version jump, but should still function?<br><br>Any other caveats that anyone have ran into would be helpful.<br><br>Thanks,<br>Tim<br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><mailto:<a href="mailto:cisco-voip@puck.nether.net">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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/6feda7d3/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/6feda7d3/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 4<br>Date: Sat, 19 Feb 2011 13:20:06 -0500 (EST)<br>From: Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br>To: "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>><br>Cc: "<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: Re: [cisco-voip] CUCM Upgrade<br>Message-ID: <<a href="mailto:7056B91F-D4C6-40CF-A38F-9B05AE87FEAB@uoguelph.ca">7056B91F-D4C6-40CF-A38F-9B05AE87FEAB@uoguelph.ca</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>If I'm not mistaken, you can upgrade the publisher first, change the device defaults, then upgrade the subs. We've been doing something similar on 4.1 for years.<br><br>Sent from my iPhone<br><br>On Feb 19, 2011, at 1:13 PM, "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>> wrote:<br><br>> No, that won?t do it because the upgrade will change it to the latest version. It would need to be changed on the phones.<br>><br>><br>><br>> James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions<br>> 12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><br>> D: 615-866-5729 | F: 615-866-5781 | <a href="http://www.presidio.com" target="_blank">www.presidio.com</a><br>><br>> CCIE #25863, Voice<br>><br>><br>><br>><br>> From: Lelio Fulgenzi [mailto:<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>]<br>> Sent: Saturday, February 19, 2011 12:10 PM<br>> To: Buchanan, James<br>> Cc: H, Tim; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Subject: Re: [cisco-voip] CUCM Upgrade<br>><br>><br>><br>> You could also change the device defaults firmware config parameters.<br>><br>> Sent from my iPhone<br>><br>><br>> On Feb 19, 2011, at 1:07 PM, "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>> wrote:<br>><br>> I had a customer do this last Sunday. The only change was the firmware. Attendant Console was unaffected. If you don?t want to deal with the firmware, you could hard code the firmware on the phones until you are ready for the jump because the old firmware will stay on the server.<br>><br>><br>><br>> James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions<br>> 12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><br>> D: 615-866-5729 | F: 615-866-5781 | <a href="http://www.presidio.com" target="_blank">www.presidio.com</a><br>><br>> CCIE #25863, Voice<br>><br>><br>><br>><br>><br>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of H, Tim<br>> Sent: Saturday, February 19, 2011 8:13 AM<br>> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Subject: [cisco-voip] CUCM Upgrade<br>><br>><br>><br>> All,<br>><br>><br>><br>> I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15. I'm aware of the firmware jump as you have to upgrade to 8.52sr1 or whatever, but is there anything else I need to be cautious about? Looks like the attendant console might change a bit in the version jump, but should still function?<br>><br>><br>><br>> Any other caveats that anyone have ran into would be helpful.<br>><br>><br>><br>> Thanks,<br>><br>> Tim<br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/1058b488/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/1058b488/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 5<br>Date: Sat, 19 Feb 2011 13:21:34 -0500<br>From: "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>><br>To: Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>><br>Cc: "<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: Re: [cisco-voip] CUCM Upgrade<br>Message-ID:<br> <<a href="mailto:853687641CF93E40B362F112A3D8F3CE1724B85F@SOEXCH01.Presidio.Corp">853687641CF93E40B362F112A3D8F3CE1724B85F@SOEXCH01.Presidio.Corp</a>><br>Content-Type: text/plain; charset="utf-8"<br><br>Yes, you could do that and that would definitely keep your phones from getting the new firmware. Good idea!<br><br>James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions<br>12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><mailto:<a href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</a>><br>D: 615-866-5729 | F: 615-866-5781 | <a href="http://www.presidio.com" target="_blank">www.presidio.com</a><<a href="http://www.presidio.com/" target="_blank">http://www.presidio.com/</a>><br>CCIE #25863, Voice<br><br><br>From: Lelio Fulgenzi [mailto:<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>]<br>Sent: Saturday, February 19, 2011 12:20 PM<br>To: Buchanan, James<br>Cc: H, Tim; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] CUCM Upgrade<br><br>If I'm not mistaken, you can upgrade the publisher first, change the device defaults, then upgrade the subs. We've been doing something similar on 4.1 for years.<br><br>Sent from my iPhone<br><br>On Feb 19, 2011, at 1:13 PM, "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><mailto:<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>>> wrote:<br>No, that won?t do it because the upgrade will change it to the latest version. It would need to be changed on the phones.<br><br>James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions<br>12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><mailto:<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>><br>D: 615-866-5729 | F: 615-866-5781 | <a href="http://www.presidio.com" target="_blank">www.presidio.com</a><<a href="http://www.presidio.com" target="_blank">http://www.presidio.com</a>><br>CCIE #25863, Voice<br><br><br><br>From: Lelio Fulgenzi [mailto:<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>]<br>Sent: Saturday, February 19, 2011 12:10 PM<br>To: Buchanan, James<br>Cc: H, Tim; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: Re: [cisco-voip] CUCM Upgrade<br><br>You could also change the device defaults firmware config parameters.<br><br>Sent from my iPhone<br><br>On Feb 19, 2011, at 1:07 PM, "Buchanan, James" <<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><mailto:<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>>> wrote:<br>I had a customer do this last Sunday. The only change was the firmware. Attendant Console was unaffected. If you don?t want to deal with the firmware, you could hard code the firmware on the phones until you are ready for the jump because the old firmware will stay on the server.<br><br>James Buchanan | Technology Manager, UC | South Region | Presidio Networked Solutions<br>12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | <a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a><mailto:<a href="mailto:jbuchanan@presidio.com">jbuchanan@presidio.com</a>><br>D: 615-866-5729 | F: 615-866-5781 | <a href="http://www.presidio.com" target="_blank">www.presidio.com</a><<a href="http://www.presidio.com" target="_blank">http://www.presidio.com</a>><br>CCIE #25863, Voice<br><br><br><br><br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of H, Tim<br>Sent: Saturday, February 19, 2011 8:13 AM<br>To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><mailto:<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: [cisco-voip] CUCM Upgrade<br><br>All,<br><br>I'm getting ready to upgrade our CUCM cluster from 7.02 to 7.15. I'm aware of the firmware jump as you have to upgrade to 8.52sr1 or whatever, but is there anything else I need to be cautious about? Looks like the attendant console might change a bit in the version jump, but should still function?<br><br>Any other caveats that anyone have ran into would be helpful.<br><br>Thanks,<br>Tim<br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><mailto:<a href="mailto:cisco-voip@puck.nether.net">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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/6cc5ec9f/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20110219/6cc5ec9f/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 6<br>Date: Sun, 20 Feb 2011 10:38:38 +1100<br>From: Tony Edwards <<a href="http://tonyedwards.rs" target="_blank">tonyedwards.rs</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>><br>To: Anthony Holloway <<a href="mailto:avholloway%2Bcisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>><br>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] CCM7 day to day admin tips ?<br>Message-ID:<br> <AANLkTimMn_4xmUBtu-5oUvth8aUODXUC02jpGYjx=<a href="mailto:DVB@mail.gmail.com">DVB@mail.gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>your modified url works , Anthony :-) thanks for that.<br><br>tony<br><br><br><br>On Fri, Feb 18, 2011 at 2:09 AM, Anthony Holloway <<br><a href="mailto:avholloway%2Bcisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>> wrote:<br><br>> Close, but it should look like this:<br>><br>><br>> <a href="http://192.168.10.100:8080/emapp/EMAppServlet?device=SEP1234567&userid=testuser&seq=99999" target="_blank">http://192.168.10.100:8080/emapp/EMAppServlet?device=SEP1234567&userid=testuser&seq=99999</a><br>><br>> Anthony<br>><br>> On Thu, Feb 17, 2011 at 5:03 AM, Tony Edwards <<a href="http://tonyedwards.rs" target="_blank">tonyedwards.rs</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>>wrote:<br>><br>>> hi Stephen,<br>>><br>>> thanks for your unifiedfx advise.i will check them out shortly.<br>>><br>>><br>>><br>>> hi Bernard,<br>>><br>>> thanks a lot for your detailed explanations. great work indeed.now , can i<br>>> please ask you couple of questions on what you said below.<br>>><br>>> With EM Login URL syntax, is the following correct ?<br>>><br>>> <a href="http://%3c192.168.10.100%3e:8080/emapp/EMAppServlet?SEP1234567=%3cleSEP1234567%3e&userid=%3cle">http://<192.168.10.100>:8080/emapp/EMAppServlet?SEP1234567=<leSEP1234567>&userid=<le</a> testuser>&seq=<le 99999><br>>><br>>> where my pub ip is 192.168.10.100 and user pin is 99999 and the device<br>>> name SEP1234567.<br>>><br>>> Also , let us say , if I have 100 users whom I wants to remote login to<br>>> their EM profiles , let us say after some maintenance works on the cluster,<br>>> shall I have to run this URL on my http gui single time every user ? or can<br>>> I bulk them up all in one go ?<br>>><br>>> secondly, with my vg224 display , yes , i did try with show endpoints to<br>>> yes , but when you click on end points , she will show me ip adds and<br>>> descriptions ...etc. but if i click on vg device itself , then it show me<br>>> all ports in a serial fashion like , 0/1 , 0/2 , 0/3..etc<br>>><br>>> but still , it will not show me what i used to have with in ccm4 like<br>>> following with both port vs dn mappings such as,<br>>> 0/1 - 1011<br>>> 0/2 - 1012<br>>> 0/3 - blank<br>>> 0/4 - 1014<br>>> .<br>>> .<br>>> .<br>>> 0/24 -1024<br>>><br>>> ...etc<br>>><br>>><br>>> thanks<br>>><br>>> tony<br>>><br>>> On Wed, Feb 16, 2011 at 10:03 PM, Bernhard Albler <<br>>> <a href="mailto:bernhard.albler@gmail.com">bernhard.albler@gmail.com</a>> wrote:<br>>><br>>>> Hi Tony,<br>>>><br>>>><br>>>> ><br>>>> > 1) my ccm 7x admin gui keeps on logging me out , so how i can make my<br>>>> login a permanent for few hours at least , let us say 8am to 5pm , if not<br>>>> for any longer ?<br>>>> ><br>>>> Known issue, i believe this is not fixable right now. See CSCsj45520 for<br>>>> details<br>>>><br>>>> ><br>>>> > 2) how can remote login my users across wan ? cause , i heard that<br>>>> there is a url with which you can remotely login any extension mobility user<br>>>> , even though you can logout the same user via device gui section ?<br>>>> ><br>>>> Two options<br>>>> 1.)Use AXL (quite easy to do). There is even an example script to do<br>>>> this in the pyaxl distribution from TU Chemnitz<br>>>> (<a href="http://www.kra-se.de/pyAXL/" target="_blank">http://www.kra-se.de/pyAXL/</a>)<br>>>> 2.)You can always use the normal EM Login URL in the following form:<br>>>> <a href="http://%3cucm%3e:8080/emapp/EMAppServlet?device=%3cle">http://<ucm>:8080/emapp/EMAppServlet?device=<le</a> device>&userid=<le<br>>>> username>&seq=<le highly secret pin code of the user><br>>>> Devicename includes SEP + the mac.<br>>>> For this to work you need to know the pin of the user<br>>>><br>>>> > 3) with in my previous ccm4 platform , i use to have a vg224 gui<br>>>> display under device menu i.e and in this display , there used to be very<br>>>> useful info or "ports vs associated dn Numbers" mapping and you used to see<br>>>> which ports are vacant ..etc after the ccm7x migration , i could not display<br>>>> similar useful info unfortunately. so , is there any way i can extract this<br>>>> vg224 ports vs dn numbers view ?<br>>>> ><br>>>> Hmm, not sure which view you mean. did you check the GW view with<br>>>> "show endpoints" set to yes?<br>>>><br>>>><br>>>> > 4) speaking of display , another display i found very useful in my<br>>>> previous ccm4x platform was that , you can actually navigate between<br>>>> "device/mac + loged out dn ( i.e base dn with out any extension mobility or<br>>>> device profile dn) + loged in dn ( i.e with device profile dn). Is there any<br>>>> way , i can view similar 3 way mappings with in ccm7 admin gui ?<br>>>> ><br>>>> So the DB model for a EM login has changed quite a bit. Logins are now<br>>>> done just via a relational association.<br>>>> You have two options:<br>>>> 1.)go via Device->Actively logged in Devices. Just be aware that<br>>>> whenever you click on the device you will get the logged out dn there<br>>>> 2.)Dependency records. Newer CCM versions will show a Dependency<br>>>> record for the extensionmobilitydynamic table (unfortunately labeled<br>>>> as "null"). So this gives you some info as well<br>>>> 3.)run the following query on the cli<br>>>> run sql select <a href="http://d.name" target="_blank">d.name</a>,d.description,np.dnorpattern as<br>>>> loggedoutdn,emdn.dnorpattern emdn from device d,device<br>>>> profile,extensionmobilitydynamic em,devicenumplanmap<br>>>> dnmp,devicenumplanmap dnmp2,numplan np,numplan emdn where<br>>>> d.pkid=dnmp.fkdevice and dnmp.fknumplan=np.pkid and d.pkid=em.fkdevice<br>>>> and em.fkdevice_currentloginprofile=profile.pkid and<br>>>> profile.pkid=dnmp2.fkdevice and dnmp2.fknumplan=emdn.pkid<br>>>> this should at least give you a bit a easy view who is logged in where<br>>>> (no navigating from there though :-( )<br>>>><br>>>> cheerio<br>>>> bernhard<br>>>><br>>><br>>><br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> <a href="mailto:cisco-voip@puck.nether.net">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>>><br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20110220/910c0fa5/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20110220/910c0fa5/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 7<br>Date: Sun, 20 Feb 2011 22:40:02 +1000<br>From: Karen Cheng <<a href="mailto:kaz.cheng@gmail.com">kaz.cheng@gmail.com</a>><br>To: Mauro Celli <<a href="mailto:mauro.celli@2000net.it">mauro.celli@2000net.it</a>><br>Cc: "<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: Re: [cisco-voip] R: R: Phones randomply reset<br>Message-ID:<br> <AANLkTi=nfxnai1kujrNFO==<a href="mailto:d_TqZ5GFcUeSbFanOWtKM@mail.gmail.com">d_TqZ5GFcUeSbFanOWtKM@mail.gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br><br>Heya,<br><br>Judging from your logs it seems more to do with path changes/vlan changes.<br>What type of switches and phone firmware are you running?<br><br>Are they attached to a stack of switches? If so are there multiple paths<br>in/out or spanning-tree loop that could be directly associated to your voice<br>vlan?<br><br>Regards<br><br>Karen<br><br>On Fri, Feb 18, 2011 at 10:34 PM, Mauro Celli <<a href="mailto:mauro.celli@2000net.it">mauro.celli@2000net.it</a>>wrote:<br><br>> The phones reset only when i press some key.<br>> If i leave in stand-by, no reset occured.<br>><br>> Another log. in this PAE: SIGIPCFG received... is missing<br>><br>> NOT 11:45:09.533159 CDP-D: catchipcfg:getdhcpinfo IP:1001497 domain:<br>> <a href="http://fiphre1.2000net.it" target="_blank">fiphre1.2000net.it</a> chngVal:1<br>> NOT 11:45:09.576221 CDP-D: catchipcfg:getdhcpinfo IP:1001497 domain:<br>> <a href="http://fiphre1.2000net.it" target="_blank">fiphre1.2000net.it</a> chngVal:1<br>> NOT 11:45:09.581101 tftpClient: request server 0 ---> 1.1.254.3<br>> ERR 11:45:09.583327 RTSOLD: opvvlan:4095->4095 advvlan:4096->4096<br>> ERR 11:45:09.587012 RTSOLD: LINK -> LINK<br>> ERR 11:45:09.587784 RTSOLD:address mode changed..<br>><br>><br>><br>><br>><br>> Da: Daniel [mailto:<a href="mailto:dan.voip@danofive.id.au">dan.voip@danofive.id.au</a>]<br>> Inviato: venerd? 18 febbraio 2011 02:52<br>> A: Mauro Celli<br>> Cc: Stephen Welsh; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Oggetto: Re: [cisco-voip] R: Phones randomply reset<br>><br>> I agree with Stephen,<br>><br>> We see alot of restarts from DHCP issues, we run DHCP from the router and<br>> IP conflict logging is a pain as you start to run out of IPs real quick so<br>> we turn logging off.<br>><br>> The other issue could be the "Maximum Number of Registered Devices" call<br>> manager service parameter. When we got to over 5000 phones weird things<br>> started with phone reboots and registration. Changed the value to fit our<br>> cluster and all is ok.<br>><br>><br>> On Fri, Feb 18, 2011 at 8:32 AM, Mauro Celli <<a href="mailto:mauro.celli@2000net.it">mauro.celli@2000net.it</a>><br>> wrote:<br>> This is observed in multiple installation,<br>> 7945 7970 7975 are those who restarted more...<br>> Poe is ok...<br>><br>> -----Messaggio originale-----<br>> Da: Stephen Welsh [mailto:<a href="mailto:stephen.welsh@unifiedfx.com">stephen.welsh@unifiedfx.com</a>]<br>> Inviato: gioved? 17 febbraio 2011 22:51<br>> A: Mauro Celli<br>> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Oggetto: Re: [cisco-voip] Phones randomply reset<br>><br>> Nothing I can tell from the logs, but I've seen this when there is more<br>> phones in a subnet/VLAN than there is IP Addresses, as some phones fight for<br>> an IP address lease.<br>><br>> Stephen<br>><br>> On 17 Feb 2011, at 21:03, Mauro Celli wrote:<br>><br>> ><br>> > We have an issue in some IP phones,it keep resetting randomly.<br>> > Below is an extract from one of the console logs from the phone.<br>> ><br>> > Can anyone interpret what exactly is causing the restart?<br>> ><br>> > Note,i have disabled cdp and lldp in cucm phone properties with no<br>> success...<br>> > Thanks<br>> ><br>> > NOT 16:08:49.258777 PAE: SIGIPCFG received...<br>> > NOT 16:08:49.262716 CDP-D: catchipcfg:getdhcpinfo IP:10014aa<br>> domain:xxx.xxx.xx chngVal:1<br>> > NOT 16:08:49.307331 CDP-D: catchipcfg:getdhcpinfo IP:10014aa<br>> domain:xxx.xxx.xx chngVal:1<br>> > NOT 16:08:49.322263 tftpClient: request server 0 ---> 10.1.254.3<br>> > ERR 16:08:49.324461 RTSOLD: opvvlan:4095->4095 advvlan:4096->4096<br>> > ERR 16:08:49.327917 RTSOLD: LINK -> LINK<br>> > ERR 16:08:49.328677 RTSOLD:address mode changed..<br>> > NOT 16:08:49.345190 tftpClient: request server 1 ---><br>> > ERR 16:08:49.355400 RTSOLD: opvvlan:4095->4095 advvlan:4096->4096<br>> > ERR 16:08:49.361458 RTSOLD: LINK -> LINK<br>> > NOT 16:08:49.365233 tftpClient: request server 0 ---> 10.1.254.3<br>> > NOT 16:08:49.372982 ESP: server 0 = 1.1.254.3<br>> > NOT 16:08:49.382033 tftpClient: request server 1 ---><br>> > NOT 16:08:49.384385 ESP: server 1 =<br>> > NOT 16:08:49.395732 tftpClient: request server6 0 ---> ::<br>> > NOT 16:08:49.396802 ESP: server 2 = ::<br>> > NOT 16:08:49.417733 tftpClient: request server6 1 ---> ::<br>> > NOT 16:08:49.420555 ESP: server 3 = ::<br>> > NOT 16:08:49.423144 ESP: send ADMIN, logging = 1, shell = 0, ipconfig = 1<br>> > NOT 16:08:49.443032 tftpClient: request server6 0 ---> ::<br>> > NOT 16:08:49.449721 tftpClient: request server6 1 ---> ::<br>> > NOT 16:08:49.465934 JVM: Startup Module Loader|cip.cfg.ConfigManager:? -<br>> ConfigManager PropertyChanged: device.settings.network.ipstacksstate<br>> > NOT 16:08:49.467530 JVM: Startup Module Loader|cip.cfg.ConfigManager:? -<br>> ConfigManager IP_STACKS_STATE changed<br>> > NOT 16:08:49.469131 JVM: Startup Module Loader|cip.cfg.ConfigManager:? -<br>> IPv4 state=DHCP BOUND<br>> > NOT 16:08:49.470741 JVM: Startup Module Loader|cip.cfg.ConfigManager:? -<br>> IPv6 state=STACK TURNED OFF<br>> > WRN 16:08:49.478478 SECD: WARN:getCTLInfo: ** phone has no CTL<br>> > WRN 16:08:49.483464 SECD: WARN:getCTLInfo: ** phone has no CTL<br>> > NOT 16:08:49.493588 tftpClient: request server 0 ---> 10.1.254.3<br>> ><br>> ><br>> > Cordiali saluti<br>> > Mauro Celli (work in progress...)<br>> ><br>> ><br>> ><br>> ><br>> ><br>> > _______________________________________________<br>> > cisco-voip mailing list<br>> > <a href="mailto:cisco-voip@puck.nether.net">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>><br>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">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>><br>> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20110220/32e4a7f7/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20110220/32e4a7f7/attachment-0001.html</a>><br><br>------------------------------<br><br>Message: 8<br>Date: Sun, 20 Feb 2011 09:15:12 -0500<br>From: "Jason Aarons (US)" <<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>><br>To: "cisco-voip (<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)"<br> <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>Subject: [cisco-voip] CallManager 7x to 8.5(1) and Attendant Console<br>Message-ID:<br> <<a href="mailto:4E38DB0A1959B04C8C83EDCF069B53ED0C9D80A82D@USISPCLEXDB01.na.didata.local">4E38DB0A1959B04C8C83EDCF069B53ED0C9D80A82D@USISPCLEXDB01.na.didata.local</a>><br><br>Content-Type: text/plain; charset="us-ascii"<br><br>I understood the Attendant Console Service/TCD is no longer present in CallManager 8.x, is it 8.0 or 8.5(1).<br><br>So if they had 7x with the migrated Attendant Console and go to 8.5(1) the old AC application should stop working. I just haven't tested it. Are the services gone completely under Serviceability ? AC used TCD right?<br><br><br>-----------------------------------------<br>Disclaimer:<br><br>This e-mail communication and any attachments may contain<br>confidential and privileged information and is for use by the<br>designated addressee(s) named above only. If you are not the<br>intended addressee, you are hereby notified that you have received<br>this communication in error and that any use or reproduction of<br>this email or its contents is strictly prohibited and may be<br>unlawful. If you have received this communication in error, please<br>notify us immediately by replying to this message and deleting it<br>from your computer. Thank you.<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="https://puck.nether.net/pipermail/cisco-voip/attachments/20110220/f5698b40/attachment-0001.html" target="_blank">https://puck.nether.net/pipermail/cisco-voip/attachments/20110220/f5698b40/attachment-0001.html</a>><br><br>------------------------------<br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">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><br>End of cisco-voip Digest, Vol 88, Issue 19<br>******************************************<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></body></html>