Hiya---

For some reason, a bunch of our 7912G phones mysteriously converted from
SCCP to SIP

We are running CM 4.01 on a publisher and a subscriber.

We had a power outage, and when the phones came back up, some were
loading the WRONG code!!! 
Needless to say, SIP isn't supported on 4.01, so we cannot even
configure the phones to use this in the interim..

The bad code WAS located in the TFTPPath on the CCM, but was NOT the
load specified in Default Settings
or on any individual phones..

Hence, we don't know why some of them switched...

Here's the SIP load that's gone into some of them
1.3.0(050414A) 

This is the SCCP load that's also available and is also in the SCCP
path.
CP7912080001SCCP060331A

We have tried the 'rescue and recovery' .zup image (I think that's
cp7912r.zup)
That does work to recover the phone, IF you can get the phone to decide
that it must go get a new load-- 
between removing the SIP image and ensuring that at least the R.zup file
is there, they seem to do OK ---
So far, that's been a whopping TWO of the phones --

How do I force a phone to get a new load, even if it's happy with what
it has?
Is there some secret way to whack the firmware on the phone, such that
it must contact the CCM for a new load? Seems like once it tries that,
it finds only the recovery image or the proper SCCP image..

Most of the SIP phones aren't doing that-- they seem to be sticking to
their guns on SIP, so to speak..

HELP!!
Half my teacher phones are down!!

thanks, Tim

Attachment:
This has been downloaded 0 time(s).

[ Post a follow-up to this message ]

OK --
 
I never saw anyone answer this at all ---
 
But, here's the workaround we found--
 
Go to the phone.
Perform a factory reset
This was the last thing under Settings/Network config for the SIP
phones.
You may need to enter the admin password of 1234
Then, as the phone reboots, wait until the logo appears, and both
LEDS are lit- one red, one green.
As soon as they go out, pull power from the phone.
When the phone comes back up, it will try to reload it's proper image.
Assuming the loads are configured correctly in the CCM, it will work.
 
We had the right load configured in default settings-
Some, but not all, of the 7912 phones IGNORED that setting, and loaded a
different image.
This reload fixed that, once the offending load was gone from the
system.
 
I have no idea why the phones chose to ignore the load programming
specified by the CCM.
No one at my vendor does either, and I don't think cisco has answered
their query about this either.
 
 

________________________________

From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Tim Reimers
Sent: Tuesday, August 22, 2006 7:39 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] HELP!! SIP to SCCP problem





Hiya--- 

For some reason, a bunch of our 7912G phones mysteriously converted from
SCCP to SIP 

We are running CM 4.01 on a publisher and a subscriber. 

We had a power outage, and when the phones came back up, some were
loading the WRONG code!!! 
Needless to say, SIP isn't supported on 4.01, so we cannot even
configure the phones to use this in the interim.. 

The bad code WAS located in the TFTPPath on the CCM, but was NOT the
load specified in Default Settings 
or on any individual phones.. 

Hence, we don't know why some of them switched... 

Here's the SIP load that's gone into some of them 
1.3.0(050414A) 

This is the SCCP load that's also available and is also in the SCCP
path. 
CP7912080001SCCP060331A 

We have tried the 'rescue and recovery' .zup image (I think that's
cp7912r.zup) 
That does work to recover the phone, IF you can get the phone to decide
that it must go get a new load-- 
between removing the SIP image and ensuring that at least the R.zup file
is there, they seem to do OK --- 
So far, that's been a whopping TWO of the phones -- 

How do I force a phone to get a new load, even if it's happy with what
it has? 
Is there some secret way to whack the firmware on the phone, such that
it must contact the CCM for a new load? Seems like once it tries that,
it finds only the recovery image or the proper SCCP image..

Most of the SIP phones aren't doing that-- they seem to be sticking to
their guns on SIP, so to speak.. 

HELP!! 
Half my teacher phones are down!! 

thanks, Tim 

Attachment:
This has been downloaded 0 time(s).

[ Post a follow-up to this message ]