[cisco-voip] Cisco IP Phones Problem
Lelio Fulgenzi
lelio at uoguelph.ca
Thu Aug 4 14:37:38 EDT 2011
On the other hand, I like the factory default process for testing system/network changes because it tests things out of the box. I've not done that before and been bitten because the phone had enough of it's configuration to continue without a specific ACL entry. ;)
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
----- Original Message -----
From: "Ryan Ratliff" <rratliff at cisco.com>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Cc: "cisco-voip (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net>, "Jason Aarons (AM)" <jason.aarons at dimensiondata.com>
Sent: Thursday, August 4, 2011 2:34:40 PM
Subject: Re: [cisco-voip] Cisco IP Phones Problem
The other thing that's worth pointing out is that factory resets are really supposed to be an action of last resort. It should not be an alternative to actual troubleshooting (ie packet captures, phone logs, etc) because unless you get lucky you'll end up right back where you started (best case) or in a much worse place than you were before (worst case).
-Ryan
On Aug 4, 2011, at 2:25 PM, Lelio Fulgenzi wrote:
This has been a very informative thread. It really highlights how something we're used to, although in and of itself has not change, behaves differently when a downstream action has changed.
I _almost_ installed a new SIP COP file on my TFTP server the other day. Had I done that and performed a factory reset it would have thrown me for a loop as well and it would have been me, not Jason who started this thread. ;)
Lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
----- Original Message -----
From: "Ryan Ratliff" < rratliff at cisco.com >
To: "Jason Aarons (AM)" < jason.aarons at dimensiondata.com >
Cc: "cisco-voip ( cisco-voip at puck.nether.net )" < cisco-voip at puck.nether.net >
Sent: Thursday, August 4, 2011 2:04:18 PM
Subject: Re: [cisco-voip] Cisco IP Phones Problem
>From the same document I sent earlier.
Performing a Factory Reset
When you perform a factory reset of the Cisco Unified IP Phone, the following information is erased or reset to its default value:
• CTL file—Erased
• LSC—Erased
• User configuration settings—Reset to default values
• Network configuration settings—Reset to default values
• Call histories—Erased
• Locale information—Reset to default values
• Phone application—Erased (phone recovers by loading the appropriate default load file (term75.default.loads, term71.default.loads, term70.default.loads, term65.default.loads, or term45.default.loads) depending on the phone model)
In the process of recovering the phone application the first thing the phone will do is load whatever the default load on the server DHCP is pointing it to. If that's a SIP load you get SIP and if it's SCCP then you'll get SCCP. After the default load is obtained the phone will reboot to it and then proceed with a normal boot process. If the phone is still provisioned in CUCM (and DHCP option 150 is pointing to the correct server) then it will load whatever load it's SEPmac.cnf.xml file points to. If this is a different load than what the phone got via the default file then it will proceed to upgrade again.
In the end the phone should be back in the state it was before you did the factory reset, minus whatever problem caused you to do the factory reset. If the problem still exists then you didn't need to do the factory reset to begin with.
Please feel free to unicast me your SR number and I'll follow up on it.
-Ryan
On Aug 4, 2011, at 1:37 PM, Jason Aarons (AM) wrote:
I never expected a restore factory default to do anything but wipe the configured settings (tftp, callamanger,etc) versus downloading a new load and or changing from SCCP/SIP. Is this a bug, since the GUI doesn’t have a way to change whether default load is SCCP vs SIP?
This should be documented somewhere, TAC had no idea and sent me new phones.
The other workaround to create a SCCP device with that MAC also works on a per device basis.
From: Ryan Ratliff [mailto:rratliff at cisco.com]
Sent: Thursday, August 04, 2011 11:38 AM
To: Lelio Fulgenzi
Cc: Jason Aarons (AM); cisco-voip ( cisco-voip at puck.nether.net )
Subject: Re: [cisco-voip] Cisco IP Phones Problem
Yup, just install an SCCP load but be aware that it will change device defaults.
-Ryan
On Aug 4, 2011, at 9:29 AM, Lelio Fulgenzi wrote:
Thanks Ryan - That answers my question about how the default load is changed.
But raises another one, if the last COP you installed was SIP, but you want the default load to be SCCP, how do you go about changing it? Can you simply reinstall the latest SCCP load again?
Thanks, Lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
----- Original Message -----
From: "Ryan Ratliff" < rratliff at cisco.com >
To: "Lelio Fulgenzi" < lelio at uoguelph.ca >
Cc: "Jason Aarons (AM)" < jason.aarons at dimensiondata.com >, "cisco-voip ( cisco-voip at puck.nether.net )" < cisco-voip at puck.nether.net >
Sent: Thursday, August 4, 2011 9:25:35 AM
Subject: Re: [cisco-voip] Cisco IP Phones Problem
If you did a factory reset and the phone switched to a SIP load then it just means the default load on the TFTP server was SIP. This will be determined by the last load file you installed via cop file on the server.
-Ryan
On Aug 4, 2011, at 9:20 AM, Lelio Fulgenzi wrote:
That's bizarre. All the documentation still refers to that key sequence. I wonder if it's something to do with the CCM config that says upgrade to SIP if no SCCP phone exists.
Were these phones configured in CCM?
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
----- Original Message -----
From: "Jason Aarons (AM)" < jason.aarons at dimensiondata.com >
To: "Lelio Fulgenzi" < lelio at uoguelph.ca >
Cc: "cisco-voip ( cisco-voip at puck.nether.net )" < cisco-voip at puck.nether.net >
Sent: Thursday, August 4, 2011 9:13:57 AM
Subject: RE: [cisco-voip] Cisco IP Phones Problem
Nope. Saw it with 7942 phones last year with 8.5x load at a customer. I thought I bricked the phone. Did it again. Bricked another phone. Did RMAs as no one could tell me what was wrong. Next customer I did same, noticed under Settings > Device Info it was a SIP load on the phone and put 1-1 together.
Maybe if it’s unplugged from network it won’t do that? Not sure.
From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Thursday, August 04, 2011 9:11 AM
To: Jason Aarons (AM)
Subject: Re: [cisco-voip] Cisco IP Phones Problem
are you joking?
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
From: "Jason Aarons (AM)" < jason.aarons at dimensiondata.com >
To: "Adewale2" < adewale2 at yahoo.com >, cisco-voip at puck.nether.net
Sent: Thursday, August 4, 2011 9:09:04 AM
Subject: Re: [cisco-voip] Cisco IP Phones Problem
That no longer does a factory reset, you just changed to a SIP load.
Register the device in callmanager as a SIP device, then delete and create it as a SCCP device, let it register and it will change loads back to SCCP.
I’m not sure what the new factory default sequence is, but whoever decided to change the sequence should be reprimanded. It tooks me awhile to figure out what was happening when I thought I was reseting phones back to factory default.
Other option is to RMA the phone and get a SCCP back.
Jason Aarons
Consultant
Dimension Data
904-338-3245 mobile
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Adewale2
Sent: Thursday, August 04, 2011 8:59 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Cisco IP Phones Problem
Hello ,
I am having problem with Cisco IP Phones i used factory reset ( 123456789*0#) for; It is just showing Upgrading and Cisco Logo.
Could anyone advice on what to do please
Thanks in Advance
Addy
itevomcid
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
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/20110804/5eb2873f/attachment.html>
More information about the cisco-voip
mailing list