<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Possibilities:
<div>CSCts83522 Unsupported phone service category prevents device registration <br>
<div>
<div><br>
</div>
<div><br>
</div>
<div>Is 192.168.5.10 the correct TFTP server?</div>
<div><br>
</div>
<div>Found at least one instance of this where devices were provisioned as wrong type in CUCM.</div>
<div><br>
</div>
<div>Try deleting the phone to clear all features and letting it re-register. Or just change the MAC address to save the existing configuration and re-add the phone as a new phone with no or minimal configuration.</div>
<div><br>
</div>
<div>Errors parsing the dateTimeSetting are also related to old phone loads (pre-olson implementation) configured with olson timezones.</div>
<div><br>
</div>
<div><br>
</div>
<div>"Parser Exception: name expected "</div>
<div><br>
</div>
<div>This makes me suspect the XML file integrity like transfer may be incomplete or corrupted in transit.</div>
<div><br>
</div>
<div>-Wes</div>
<div><br>
</div>
<div>On Nov 5, 2013, at 3:04 PM, Erick B. <<a href="mailto:erickbee@gmail.com">erickbee@gmail.com</a>></div>
<div> wrote:</div>
<br class="Apple-interchange-newline">
<div dir="ltr">The phone is registered and working.
<div><br>
</div>
<div>Just wrong time, and not updating to current firmware on server and probably not taking phone changes.</div>
<div><br>
</div>
<div>Stephen's cisco link was in right direction, but the XML parse is throwing errors on device pool section. We've made a new device pool with new settings, new date/time group and it still is having issues with parsing device pool settings. </div>
<div><br>
</div>
<div>It is downloading the cfg file file, authenticating it fine (success for that) but having issue parsing the cfg once downloaded.</div>
<div><br>
</div>
<div>
<div><span class="" style="white-space:pre">This is a 7945 with </span>SCCP45.9-2-3S, the default load is SCCP45.9-3-1SR2-1S. Most of the phones have error verifying config - multiple models. There is one 7945 with 7945.default load to not updating. </div>
<div><br>
</div>
<div>9791: NOT 13:48:21.430429 TFTP: [14]:Requesting SEP001D705EB9DA.cnf.xml.sgn from 192.168.5.10 with size limit of 550001</div>
<div>9792: NOT 13:48:21.450165 TFTP: [14]:Finished --> rcvd 9501 bytes </div>
<div>9793: NOT 13:48:21.462040 SECD: verifyFile: sgn-verify </usr/ram/SEP001D705EB9DA.cnf.xml>, 'name'[SEP001D705EB9DA.cnf.xml.sgn]</div>
<div>9794: NOT 13:48:21.464543 SECD: parseHdr(): start of pad ('T' 0x0d) at TLV 15</div>
<div>9795: NOT 13:48:21.465226 SECD: parseHdr(): skipping 1 trail bytes (pad and/or unknown TLVs)</div>
<div>9796: NOT 13:48:21.467750 SECD: parseHdr(): start of pad ('T' 0x0d) at TLV 15</div>
<div>9797: NOT 13:48:21.468668 SECD: parseHdr(): skipping 1 trail bytes (pad and/or unknown TLVs)</div>
<div>9798: NOT 13:48:21.518135 SECD: file sgn verify SUCCESS, hdr 336 byte, </usr/ram/SEP001D705EB9DA.cnf.xml></div>
<div>9799: NOT 13:48:21.518969 SECD: verifyFile: file sgn verified </usr/ram/SEP001D705EB9DA.cnf.xml>, hdrlen 336</div>
<div>9800: NOT 13:48:21.519982 SECD: verifyFile: hdr ver [2.0], and file not encr, </usr/ram/SEP001D705EB9DA.cnf.xml></div>
<div>9801: NOT 13:48:21.532024 SECD: verifyFile: 9165 byte after hdr strip, </usr/ram/SEP001D705EB9DA.cnf.xml></div>
<div>9802: NOT 13:48:21.532752 SECD: verifyFile: verify SUCCESS </usr/ram/SEP001D705EB9DA.cnf.xml></div>
<div>9803: NOT 13:48:21.551304 tftpClient: authorize file = 12, isEncr = 0 </div>
<div>9804: NOT 13:48:21.558846 SECD: lookupCTL: TFTP SRVR secure</div>
<div>9805: NOT 13:48:22.429740 JVM: Startup Module Loader|cip.cfg.t:? - Config handleTftpResponse, status=0 for file=ram/SEP001D705EB9DA.cnf.xml</div>
<div>9806: NOT 13:48:22.434950 INETD: Set IP mode 1 </div>
<div>9807: WRN 13:48:22.466548 JVM: Startup Module Loader|cip.xml.ap:parse - Encoding Updated to UTF-8</div>
<div>9808: WRN 13:48:22.468227 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'name' in element '/device/devicePool' (line=16)</div>
<div>9809: WRN 13:48:22.469870 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'name' in element '/device/devicePool/dateTimeSetting' (line=18)</div>
<div>9810: WRN 13:48:22.472332 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'name' in element '/device/devicePool/callManagerGroup' (line=38)</div>
<div>9811: WRN 13:48:22.474019 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'tftpDefault' in element '/device/devicePool/callManagerGroup' (line=39)</div>
<div>9812: WRN 13:48:22.475703 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'mgcpPorts' in element '/device/devicePool/callManagerGroup/members/member/callManager/ports' (line=49)</div>
<div>9813: WRN 13:48:22.477512 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'mgcpPorts' in element '/device/devicePool/callManagerGroup/members/member/callManager/ports' (line=65)</div>
<div>9814: WRN 13:48:22.479195 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'name' in element '/device/devicePool/srstInfo' (line=76)</div>
<div>9815: WRN 13:48:22.480925 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'userModifiable' in element '/device/devicePool/srstInfo' (line=78)</div>
<div>9816: WRN 13:48:22.482619 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'mlppDomainId' in element '/device/devicePool' (line=93)</div>
<div>9817: WRN 13:48:22.484214 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'mlppIndicationStatus' in element '/device/devicePool' (line=94)</div>
<div>9818: WRN 13:48:22.485860 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Warning: Unknown element 'preemption' in element '/device/devicePool' (line=95)</div>
<div>9819: ERR 13:48:22.487534 JVM: Startup Module Loader|cip.xml.ap: - XML Parser Exception: name expected (position:START_TAG <null>@122:2 in java.io.InputStreamReader@30ed62) (line=122)</div>
<div>9820: ERR 13:48:22.489157 JVM: Startup Module Loader|cip.cfg.t:? - ERROR PARSING CONFIG file:ram/SEP001D705EB9DA.cnf.xml</div>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Nov 5, 2013 at 1:50 PM, Andy Carse <span dir="ltr">
<<a href="mailto:andy.carse@gmail.com" target="_blank">andy.carse@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Only because I ran into this the other day, but with a 7942.<br>
Is it that it doesn't register?<br>
Mine was to do with the firmware on the handset requiring 9.3.1sr1 minimum. Shown in the console logs.<br>
</p>
<div class="gmail_quote">
<div>
<div class="h5">On 5 Nov 2013 17:43, "Erick B." <<a href="mailto:erickbee@gmail.com" target="_blank">erickbee@gmail.com</a>> wrote:<br type="attribution">
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">
<div dir="ltr">Anyone have any ideas on this? I've become pretty good at figuring out SBD issues but this one is throwing me for a loop.
<div><br>
</div>
<div>I've followed the SBD document and verified the ITL values and regenerated TVS, TFTP, Tomcat and restarted those services but can't get the 7945 to verify the config file. </div>
<div><br>
</div>
<div>The phone has ITL value of 8d50d44a707119a37dc5f66bd7149041 and the publisher server where TFTP is running also has same ITL value (show itl) command. </div>
<div><br>
</div>
<div>The subscriber server has a different ITL value. </div>
<div><br>
</div>
<div>The phones use the primary/publisher server for TFTP. </div>
<div>CUCM version is 8.6.2a SU2. The trust lists, etc have been deleted from phones and factory reset also. </div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks, Erick</div>
</div>
<br>
</div>
</div>
<div class="im">_______________________________________________<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>
</div>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
https://puck.nether.net/mailman/listinfo/cisco-voip<br>
</div>
<br>
</div>
</body>
</html>