[cisco-voip] how to control default load (for factory reset) for phones
Tim Smith
tim.smith at enject.com.au
Wed Jan 22 21:43:18 EST 2014
In the newer firmware the phones use HTTP on port 6970 to transfer config / firmware etc from “TFTP” server.
Due to the size of some of the loads these days, and your slower links, much more efficient than poor old TFTP
Definitely open that guy up and you should getter some better transport.
Cheers,
Tim.
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Thursday, 23 January 2014 12:48 PM
To: Jeremy Bresley
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] how to control default load (for factory reset) for phones
I can understand deleting the app on the phone without comparison, after all, you're probably using a factory reset to fix something that's gone wrong, maybe even corrupt software. But not comparing the software identified in either the default load or phone configuration page seems very odd.
I also noticed that the phone is trying to communicate to the TFTP server via TCP port 6970. We don't have that port open, so there are quite a few retries. I suspect that might be causing some of the delay. I'm gonna try opening it up and see if that fixes things.
Funny thing is, documentation <http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/port/8_0_1/portlist801.pdf> states that TCP port 6970 is used for inter server communications Centralized TFTP Server and Alternate TFTP server.
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519‐824‐4120 Ext 56354
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: "Jeremy Bresley" <brez at brezworks.com<mailto:brez at brezworks.com>>
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Wednesday, 22 January, 2014 8:21:33 PM
Subject: Re: [cisco-voip] how to control default load (for factory reset) for phones
I've seen this with 7945/7965s as well, on both CUCM and CME's. My understanding is that the termXX.default.loads file is downloaded on a factory reset or new phone, it installs that version, then once it registers it downloads the firmware specified in the XML configuration file for the phone.
I don't know of any workaround for this, as this seems to be the expected behavior. It does suck when you've got 20-30 phones on the far end of a single T1 that need to be upgraded and they have to download the files twice.
You can use this behavior to your advantage if you have a bunch of old phones that require the bridge firmware, you use the bridge firmware for the termXX.default.loads and then have your normal load set as the default. We've done this several times on some of our CMEs to keep from having to manually upgrade phones to get them to upgrade to the 9.3.X firmware we have as a standard.
Jeremy "TheBrez" Bresley
brez at brezworks.com<mailto:brez at brezworks.com>
On 1/22/2014 5:02 PM, Lelio Fulgenzi wrote:
Reading the document (http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7962g_7942g/6_0/english/administration/guide/7962trb.html), it states the following. I can see wanting to delete the app, I can live with that. But why does it upgrade again if the load is the exact same? I'm guessing there is no comparison made?
________________________________
When you perform a factory reset of the Cisco Unified IP Phone, the following information is erased or reset to its default value:
* Phone application—Erased (phone recovers by loading the term62.default.loads file or the term42.default.loads file, depending on the phone model)
________________________________
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519‐824‐4120 Ext 56354
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: "Lelio Fulgenzi" <lelio at uoguelph.ca><mailto:lelio at uoguelph.ca>
To: "Brian Meade (brmeade)" <brmeade at cisco.com><mailto:brmeade at cisco.com>, "cisco-voip voyp list" <cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net>
Sent: Wednesday, January 22, 2014 5:56:42 PM
Subject: Re: [cisco-voip] how to control default load (for factory reset) for phones
ok, back to the 7942/62...
I'm working on a test system where I recently uploaded SCCP42.9-3-1SR2-1S, so I suspect that that action changed the term62.default.loads. When I compare the two files, aside from the binary information at the top, they are quite similar (see below). But for some reason, when I perform a factory reset on a 7962, when it downloads the term62.default.loads file, it also downloads all the software again (the version it's already on), and then, once that's done, it downloads the files again! This is what I was hoping to avoid. This whole process can take over 15 minutes (actually, I think a little longer).
What gives? Is this the desired/expected behaviour?
________________________________
term62.default.loads
#
# This file contains a list of archive image files that will be requested by the
# RELEASE load version 9-3-1ES13
#
#HARDWARE_COMP_1 5
jar42sccp.9-3-1ES13.sbn
cnu42.9-3-1ES13.sbn
apps42.9-3-1ES13.sbn
dsp42.9-3-1ES13.sbn
cvm42sccp.9-3-1ES13.sbn
________________________________
SCCP42.9-3-1SR2-1S.loads
#
# This file contains a list of archive image files that will be requested by the
# RELEASE load version 9-3-1ES13
#
#HARDWARE_COMP_1 5
jar42sccp.9-3-1ES13.sbn
cnu42.9-3-1ES13.sbn
apps42.9-3-1ES13.sbn
dsp42.9-3-1ES13.sbn
cvm42sccp.9-3-1ES13.sbn
________________________________
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519‐824‐4120 Ext 56354
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: "Brian Meade (brmeade)" <brmeade at cisco.com><mailto:brmeade at cisco.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca><mailto:lelio at uoguelph.ca>
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net>, "Daniel Pagan" <dpagan at fidelus.com><mailto:dpagan at fidelus.com>
Sent: Wednesday, January 22, 2014 4:13:33 PM
Subject: RE: [cisco-voip] how to control default load (for factory reset) for phones
Lelio,
That is correct. The 7960s don’t ask for the termXX files after factory reset:
[cid:image001.png at 01CF1841.0E96F9F0]
They just use what’s in the config file or the XMLDefault in an auto-reg scenario.
Brian
From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Wednesday, January 22, 2014 12:32 PM
To: Brian Meade (brmeade)
Cc: cisco-voip voyp list; Daniel Pagan
Subject: Re: [cisco-voip] how to control default load (for factory reset) for phones
I just wanted to come back 'round to this. I have a large number of 7940s and 7960s that I need to confirm this for, and there is no termXX.default.loads file for them.
I recalled having to use a TFTP client to get the XMLDefault.cnf.xml file, and it still exists in v7. The file does not exist on disk, only in memory, hence, needing a TFTP client. Taking a look at it, it shows:
<snip>
<loadInformation7 model="Cisco 7960">P0030801SR02</loadInformation7>
<loadInformation8 model="Cisco 7940">P0030801SR02</loadInformation8>
<snip>
I'm pretty sure this is the file that the 7940s and 7960s use to see what load to use upon factory reset.
Can anyone confirm this?
Lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph
519‐824‐4120 Ext 56354
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: "Brian Meade (brmeade)" <brmeade at cisco.com<mailto:brmeade at cisco.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, "Daniel Pagan" <dpagan at fidelus.com<mailto:dpagan at fidelus.com>>
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Wednesday, November 13, 2013 12:34:41 PM
Subject: RE: [cisco-voip] how to control default load (for factory reset) for phones
So just to update everyone. It does indeed load the termXX.default file first after a factory reset so that will contain whatever the last firmware uploaded to the system was whether that was SCCP or SIP:
[cid:image002.jpg at 01CF1841.0E96F9F0]
Brian
From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Wednesday, November 13, 2013 12:26 PM
To: Daniel Pagan
Cc: cisco-voip voyp list; Brian Meade (brmeade)
Subject: Re: [cisco-voip] how to control default load (for factory reset) for phones
Thanks for confirming my suspicions/experience Dan. And Thanks for confirming (?) that you can re-install the latest firmware to update those termXX-default files. I was not aware that this could be done.
However, I'm not sure that it's necessary on each node, but only on the TFTP server(s) I believe.
---
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<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: "Daniel Pagan" <dpagan at fidelus.com<mailto:dpagan at fidelus.com>>
To: "Daniel Pagan" <dpagan at fidelus.com<mailto:dpagan at fidelus.com>>, "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, "Brian Meade (brmeade)" <brmeade at cisco.com<mailto:brmeade at cisco.com>>
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Wednesday, November 13, 2013 12:14:37 PM
Subject: RE: [cisco-voip] how to control default load (for factory reset) for phones
If I’m following you correctly, then what I should add is that a customer experienced an issue similar to what you’re describing. Factory resetting an IP phone would result in the phone receiving SIP firmware even though it was provisioned as an SCCP device in CUCM. To remedy this, I re-installed their current SCCP firmware on all cluster nodes to update the termXX.default files. Since the most recent firmware installed was SCCP based, factory defaulted IP phones stopped installing SIP firmware and defaulted back to SCCP.
Hope this helps
- Dan
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Daniel Pagan
Sent: Wednesday, November 13, 2013 12:05 PM
To: Lelio Fulgenzi; Brian Meade (brmeade)
Cc: cisco-voip voyp list
Subject: Re: [cisco-voip] how to control default load (for factory reset) for phones
Please correct me if I’m wrong, but I recall hearing the protocol selected for a default/factory reset device is determined by the latest phone firmware installed in a CUCM cluster. From what I recall, the latest firmware installation will update the termXX.default.loads file, which in turn determines the default protocol to be used (sip vs sccp).
- Daniel
From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Wednesday, November 13, 2013 11:53 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 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<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: "Brian Meade (brmeade)" <brmeade at cisco.com<mailto:brmeade at cisco.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: "cisco-voip voyp list" <cisco-voip at puck.nether.net<mailto: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<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1
________________________________
From: "Brian Meade (brmeade)" <brmeade at cisco.com<mailto:brmeade at cisco.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, "cisco-voip voyp list" <cisco-voip at puck.nether.net<mailto: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
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140123/f7efbf36/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 17809 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140123/f7efbf36/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 39134 bytes
Desc: image002.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140123/f7efbf36/attachment.jpg>
More information about the cisco-voip
mailing list