<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<base href="x-msg://840/">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Hi Adam,
<div><br>
</div>
<div>Are you sure the ipv6 thing is not a red herring?</div>
<div><br>
</div>
<div>Have you tried removing the ITL File from the phone and/or restarting the TVS service?</div>
<div><br>
</div>
<div>If you are not aware the choice of TVS service (node IP Address) is based on the Call Manager Group configured on the phone, you could try adding all nodes to the phones CM Group to see if that helps the phone to contact a TVS service it has a matching
ITL entry for.</div>
<div><br>
</div>
<div>If you are still stuck I'm happy to host a WebEx session to share my SDB & ITL experiences, I'm the original author of PhoneView (<a href="http://www.unifiedfx.com">http://www.unifiedfx.com</a>), it's been used to help a LOT of people with SBD related
issues, never-mind countless UCM installations and upgrades.</div>
<div><br>
</div>
<div>In-case you do need to delete/manage your ITL Files, or even just get a proper view/handle on the phone firmware version of your estate you should give PhoneView a try:</div>
<div><br>
</div>
<div><a href="http://www.unifiedfx.com/phoneview/trial">http://www.unifiedfx.com/phoneview/trial</a></div>
<div><br>
</div>
<div>Thanks</div>
<div><br>
</div>
<div>Stephen</div>
<div><br>
<div>
<div>On 5 Nov 2012, at 13:51, "Pawlowski, Adam" <<a href="mailto:ajp26@buffalo.edu">ajp26@buffalo.edu</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div lang="EN-US" link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">
<div class="WordSection1" style="page: WordSection1; ">
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; ">Morning list,<o:p></o:p></span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; "> </span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; "> From what I can read, TVS has been a thrill ride for those of us lucky enough to run afoul of SBD. I’m hoping we haven’t run into such a situation here but I have a question. We just pushed
9.3.1 out to devices from 9.1.1SR1, with peer firmware sharing enabled. This went miserably and left a lot of devices stranded at 9.1.1 or at an “Upgrading” screen. Working with TAC on that but so far nothing. We began receiving reports from end users that
their directories were missing, they can’t change ringers, etc. Last time this happened we had phones that had picked up a bum ITL from a partial rollout, and we had to erase them by hand.<o:p></o:p></span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; "> </span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; "> This time that shouldn’t have been the case – it was just a firmware upgrade. However, it looks like some of the phones that have gone to 9.3.1 have decided that they want to use IPv6 when talking
to the TFTP to verify their initial configurations, when they have no TVS server list built on the device. In looking at the phone console logs, you can see that the device is in “IP mode 1” and tries to connect to TFTP, say “192.168.0.1 :: “ which is obviously
not a V6 address. We’re not running V6 so it has no address bound. No traffic leaves the phone, but, the phone says it timed out (EAGAIN) connecting to the TFTP and won’t verify the ITL/CFG/etc.<o:p></o:p></span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; "> </span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; "> What I’m looking at it is setting V6 to off at the cluster, but, I don’t see any way to repair this on affected devices (could be a large amount) other than erasing the ITL, or deploying IPv6.
Given the leg work that could go into identifying and taking care of these devices, it’s arguable as to which one would be harder at this point.<o:p></o:p></span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; "> </span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; "> Any comment on this with this firmware? Anyone else run into this miserable trouble?<o:p></o:p></span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; "> </span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; ">Adam Pawlowski<o:p></o:p></span></font></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">
<font size="2" face="Calibri"><span style="font-size: 11pt; ">SUNYAB Network and Classroom Services<o:p></o:p></span></font></div>
</div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" style="color: purple; text-decoration: underline; ">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" style="color: purple; text-decoration: underline; ">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>