I think by far and away the quickest and best way is to not do firmware uploads on CME- do it on UCM. That means you set your TFTP to be the PUB and add the device in the UCM db wth the correct protocol. When registered point option 150 back to CME. Do not have any TFTP statements in your CME config. Do not put the ³load² command within voice register global/telephony-s since you do not want to change the firmware during the registration back to CME. -- Vik Malhi CCIE #13890 Senior Technical Instructor - IPexpert, Inc.
Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Mailto: [email protected] Join our free online support and peer group communities: http://www.IPexpert.com/communities IPexpert - The Global Leader in Self-Study, Classroom-Based, Video-On-Demand and Audio Certification Training Tools for the Cisco CCIE R&S Lab, CCIE Security Lab, CCIE Service Provider Lab , CCIE Voice Lab and CCIE Storage Lab Certifications. From: Nara Shikamaru <[email protected]> Date: Mon, 12 Oct 2009 14:52:03 -0700 To: OSL Group <[email protected]> Subject: [OSL | CCIE_Voice] How to approach CME basic install I've gotten into the habit of copying the tftp-server syntax from CME-7-0-full-readme-v.1.0.txt, but this doesn't solve everything since the example syntax doesn't seem to have SIP loads. So, those have to be added manually. I still find the process lengthy and prone to error. If there's a mistake along the way, an SCCP phone could download a SIP load and you'll lose valuable time unscrewing it. Does anyone have a better way of doing this, or is it a matter of practive and getting REALLY good with notepad? -- -Shikamaru
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
