[cisco-voip] how to control default load (for factory reset) for phones

[Lelio Fulgenzi]

Thanks again Brian. Those steps make sense, and it's what I've used in the past. I'm going to go away and do those factory resets as I mentioned and see if anything is up in my current configuration, i.e. a phone upgrading to SIP first then SCCP after a factory reset, or upgrading to a higher SCCP version first, then downgrading to the version in the device defaults page. I know this may sound bizarre, but as I mentioned, I'm 99% sure it has happened. 

Are all phones supposed to download the SCCP version first because of the "shipped from factory" setting, or are some models different from others? Perhaps that's what I'm running into and it's something I won't be able to change? 

Lelio 



--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Data Centre and Communications Facilities 
Computing and Communications Services (CCS) 
University of Guelph 

519‐824‐4120 Ext 56354 
lelio at uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 

----- Original Message -----

From: "Brian Meade (brmeade)" <brmeade at cisco.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca> 
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net> 
Sent: Wednesday, November 13, 2013 11:46:18 AM 
Subject: RE: [cisco-voip] how to control default load (for factory reset) for phones 



Lelio, 

So let’s walk through this process step by step. Let’s consider the phone is added in CallManager as a SIP Phone. 

1. Factory reset initiated which causes it to revert to SCCP firmware shipped from factory. 
2. Phone downloads SEP<MAC>.cnf.xml from its TFTP server received via DHCP which should have the SIP load name specified from the Device Defaults. 
3. Phone should then upgrade directly to that new SIP firmware. 

The main thing that usually go wrong here is that the phone might not be able to directly upgrade to that new firmware load from the load it was shipped with. To do this, you need to upload the necessary interim firmware versions in CallManager. You can then manually set the “Phone Load Name” on the device config in CallManager to have it upgrade to the interim firmware. So keep the Device Default as the final firmware you want the phone to go to and use the Phone Load Name individually on the phone to jump through interim firmwares. Onc that’s done, you can remove the manally set Phone Load Name from the phone’s configuration page in CUCM so that it will just use the Device Defaults in the future. 

Thanks, 
Brian 



From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca] 
Sent: Wednesday, November 13, 2013 11:34 AM 
To: Brian Meade (brmeade) 
Cc: cisco-voip voyp list 
Subject: Re: [cisco-voip] how to control default load (for factory reset) for phones 



Thanks Brian. I see that those are updated as you mention, but my concern is more about the factory reset behaviour. 

For example, starting point is firmware v9 SCCP installed, at that point if i factory reset a phone, it should bring up v9 SCCP. 

Let's say then, I install v9.5 SIP for testing. The process of installing that firmware updates the default file on the server that it uses in the event of a factory reset. I'm almost positive this happened to me. I don't think I can install software that is already installed in order to update this file. And I'm not sure how modifying the device defaults page will help since it's stuck on SIP. I can see how updating the version would help for the existing protocol. 

I will spend some time with my phones and my existing cluster to see what happens when a factory reset is done on each phone. 

But any other comments would be greatful. 

Lelio 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Data Centre and Communications Facilities 
Computing and Communications Services (CCS) 
University of Guelph 

519 ‐ 824 ‐ 4120 Ext 56354 
lelio at uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 

----- Original Message -----


From: "Brian Meade (brmeade)" < brmeade at cisco.com > 
To: "Lelio Fulgenzi" < lelio at uoguelph.ca >, "cisco-voip voyp list" < cisco-voip at puck.nether.net > 
Sent: Wednesday, November 13, 2013 11:25:27 AM 
Subject: RE: [cisco-voip] how to control default load (for factory reset) for phones 
Lelio, 

When a firmware or device pack is installed, the device defaults under Device->Device Settings->Device Defaults should update with the new load names for SIP and/or the SCCP firmware. IF the phone is added in CallManager, whatever protocol it is set for will determine which phone load name (SCCP or SIP) is put in the phone’s SEP<MAC>.cnf.xml config file. 

If the phone is not already added in CallManager and you’re using auto-registration, the file will use what the “Auto Registration Phone Protocol” (SCCP or SIP) is set for under System->Enterprise Parameters. 

Brian 



From: cisco-voip [ mailto:cisco-voip-bounces at puck.nether.net ] On Behalf Of Lelio Fulgenzi 
Sent: Wednesday, November 13, 2013 11:13 AM 
To: cisco-voip voyp list 
Subject: [cisco-voip] how to control default load (for factory reset) for phones 



>From what I recall, the default load, i.e. SCCP vs SIP, is controlled by a file, which is, in turn, created/updated whenever a new firmware or device pack is installed on the server. Can anyone confirm this, or, help me understand how to manipulate these files? 

I want to make sure, going forward, that if I make changes to my system, if we have to reset a phone with factory reset steps, that it doesn't download SIP first, then SCCP, or download a higher version of SCCP only to have to downgrade. 

I've seen this happen on my cluster but have also heard about it on the list as well. 

Thanks! 

Lelio 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Data Centre and Communications Facilities 
Computing and Communications Services (CCS) 
University of Guelph 

519 ‐ 824 ‐ 4120 Ext 56354 
lelio at uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20131113/b251dcbb/attachment.html>