I found one step to upgrading from SCCP to SIP that makes all the difference.
Add: tftp-server flash:SIP000011112222.xml (i think that's the filename from memory - I just copy and paste from the debug tftp events). To your config using the real MAC address (of course). Don't ask me why this works but watch the "deb tftp events" without doing this and then with doing this when the phone boots up and you'll find it works. Forget having to go through all the other steps that Cisco suggest - just do Otto's steps plus this one and it'll work every time. Regards, Roger On Sun, Apr 4, 2010 at 10:53 AM, Otto Sanchez <[email protected]> wrote: > Why not get proficient in doing that?, although it will save time doing > that with the UCM, perhaps you will have to do it at your everyday job (you > won't have a UCM close to you everytime, right?). I have seen so many > problems in this list related to not having the proper sip phone firmware > when registering them with UCME, that the first thing I would double check > before converting from one protocol to another using the UCM, is the phone > load version in UCM and compare it with the supported version of UCME, > should the version is higher in UCM, I would choose the UCME as my tftp > server for upgrading, > > How would I do it with UCME? > > The key here is to rely on the universal application loader of the phone > and the phone configuration/firmware files in the tftp, then configure your > phone as usual on the UCME, so, lets say you want to convert a sccp phone to > sip with UCME, follow these guidelines, > > 1.- Shut down the phone port > 2.- Remove the sccp (telephony-service) configurations for that phone and > disable auto-register > 3.- Make sure the phone tftp configuration is no in the tftp, sh > telephony-service tftp will help, if still there recreate the cnf files in > telephony service > 4.- Create the tftp bindings for all the firmware files, the compatibility > matrix will help here to see what are the proper files and the one you > should use with the load command in the voice register global configuration > 5.- Configure sip as you always do (registrar server, bind commands, allow > sip to sip communications, voice register global including the load command > and create profile, voice register pool and voice register dn) > 6.- Verify the xml config file for the sip phone is in the flash or the > default location, sh voice register tftp will help > 7.- Turn on the phone > 8.- See the debug tftp events output > > This procedure applies with newer software supporting universal application > loader, > > Try that at your home lab and let us know the results, > > Helpful reading at: > > http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cuipph/7960g_7940g/mgcp/firmware/matrix/frmwrup.html > > HTH, > > > On Fri, Apr 2, 2010 at 8:05 PM, Matthew Berry <[email protected]>wrote: > >> Ugh... So that basically means that I need to get proficient at upgrading >> firmware in CUCME instead of using CUCM to move firmware from SCCP to SIP? >> If that's the case, then I need to find a good document on that procedure. >> I've walked through Cisco's documents on this upgrade procedure and found >> them to have deprecated commands and errors. >> >> Any suggestions, Otto? >> >> >> >> Matthew Berry >> >> *A+, CCENT, CCNA, CCNA Voice, CCVP, CCIE Written* >> >> >> >> *Gmail:* ciscovoiceguru >> >> *Skype:* ciscovoiceguru >> >> *Twitter:* ciscovoiceguru >> >> *1st Lab Attempt: *Aug 16, 2010 >> >> On 4/2/2010 6:30 PM, Otto Sanchez wrote: >> >> Matthew, >> >> I experienced a similar behavior before, matching the sip phone firmware >> to the ucme version as per the compatibility matrix, solved my problem, >> >> hth, >> >> On Thu, Apr 1, 2010 at 10:30 AM, Matthew Berry >> <[email protected]>wrote: >> >> For the past few weeks, I've noticed a problem with my BR2 Phone 4 SIP >> phone sitting at my desk. It will register just fine when I start my life. >> I have to change the "id mac" and enter "authenticate register" into the >> "voice register global" section. >> >> However, I noticed that it will common unregister and reregister. My gut >> reaction is that it is a timeout issue that could easily be remedied with a >> modification to a SIP timer. However, I'm not sure if this is an issue >> that others have seen or if it's just me. >> >> Below is the latest status messages from the phone. One additional note >> is that I see it throwing local errors, CTL errors, and DNS errrors. If not >> asked to address those issues in the real lab, would I still lose points for >> such errors? >> >> 10:52:07 DNS Unknown Host >> 10:52:08 Error Updating Locale >> 10:52:08 Error Updating Locale >> 10:52:44 File Not Found : CTLFile.tlv >> 10:52:44 No CTL installed >> 10:52:44 SEP00215555D1F6.cnf.xml >> 10:52:53 DNS Unknown Host >> 10:52:53 DNS Unknown Host >> 10:52:54 Error Updating Locale >> 10:52:54 Error Updating Locale >> -- >> >> Matthew Berry >> >> *A+, CCENT, CCNA, CCNA Voice, CCVP, CCIE Written* >> >> >> >> *Gmail:* ciscovoiceguru >> >> *Skype:* ciscovoiceguru >> >> *Twitter:* ciscovoiceguru >> >> *1st Lab Attempt: *Aug 16, 2010 >> >> _______________________________________________ >> For more information regarding industry leading CCIE Lab training, please >> visit www.ipexpert.com >> >> >> >> >> -- >> Regards, >> >> Otto Sanchez >> CCIE #25592 (Voice) >> Support Engineer - IPexpert, Inc. >> URL: http://www.IPexpert.com >> >> > > > -- > Regards, > > Otto Sanchez > CCIE #25592 (Voice) > Support Engineer - IPexpert, Inc. > URL: http://www.IPexpert.com > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
