7937 Firmware on CUCM 10.5

Hi guys - is there a reason why the latest firmware for 7937 doesn't ship with 10.5?
I am performing a migration from 6.1.3 to 10.5 and am looking at firmware compatibility. All the other firmware on 10.5 is a newer version, but on 6.1.3, the 7937s are running 1-4-5-7, but on 10.5, the firmware for 7937 is 1-4-4-0.
I have had a look through the release notes and can't find anything to do with any incompatibility issues or any reason to downgrade the firmware.

Cisco haven't been putting the latest 7937 firmware in device packs for well over a year. I've nagged multiple people in Cisco about this and they keep on saying "It'll be done next time", but it never is. It's just one of those things we've got to live with.
*sigh*
GTG

Similar Messages

Download Phone Firmware form CUCM by TFTP

Hi all,
I have to download a Cisco Phone Firmware from CUCM.
Would you mind to help me how to do this ?
Thanks in advance
CHAM

You would need to know the exact names of all the phone firmware files. Once you have that, you can either turn on the "TFTP Client" service on Windows 7 or use your router to download the files, using TFTP.
Windows 7:
1.) Click the 'Start Menu' and then the 'Control Panel' button.
NOTE: If you cannot locate the 'Control Panel' button follow these instructions, otherwise skip to step 2.):
Right click on the 'Start Menu' button
Left click the 'Properties' option
Left click the 'Customize...' button at the top right corner of the window that appears
Locate the 'Control Panel' option (options are in alphabetical order)
Beneath the 'Control Panel' option, there are three radio buttons
'Display as a link' (When this option is selected, the 'Control Panel' button will open a new window when clicked)
'Display as a menu' (When this option is selected, hovering the cursor over the option causes a sub-menu to open)
'Don't display this item' (The 'Control Panel' option is not available in the 'Start Menu')
Choose the desired radio button and click 'OK'
Click 'OK' on the 'Taskbar and Start Menu Properties' window
2.) Double click on the 'Programs and Features' option
3.) Click on the 'Turn Windows Features On or Off' option
4.) A new window will appear. Place a check mark in the 'TFTP Client' option and click 'OK'
5.) A window will appear with a status bar. Once this windows disappears, the TFTP client has been activated.
tftp [-i] [Host] [{get | put}] [Source] [Destination]
Top of page
Parameters
-i : Specifies binary image transfer mode (also called octet mode). In binary image mode, the file is transferred in one-byte units. Use this mode when transferring binary files. If -i is omitted, the file is transferred in ASCII mode. This is the default transfer mode. This mode converts the end-of-line (EOL) characters to an appropriate format for the specified computer. Use this mode when transferring text files. If a file transfer is successful, the data transfer rate is displayed.
Host : Specifies the local or remote computer.
put : Transfers the file Destination on the local computer to the file Source on the remote computer. Because the TFTP protocol does not support user authentication, the user must be logged onto the remote computer, and the files must be writable on the remote computer.
get : Transfers the file Destination on the remote computer to the file Source on the local computer.
Source : Specifies the file to transfer.
Destination : Specifies where to transfer the file. If Destination is omitted, it is assumed to have the same name as Source.
/? : Displays help at the command prompt.
Router TFTP:
router#copy tftp://X.X.X.X/filename flash:
Regards,
Yosh

Strategy for managing phone firmwares

Hi,
I would like your advice on phone firmware management.
We are running a big CUCM 8.6 cluster with many site offices. The phone firmware version in device defaults is 9.3
When we order new phones, we receive phones with firmware versions less than 9.3 and greater than 9.3.
When the firmware version is less than 9.3, we dont have an issue. The phones just upgrade.
When the firmware version of the new phones is greater than 9.3, then we have had issues. Phones dont do the downgrade of the firmware from a higher version to a lower version. Does Cisco support downgrade of the phone firmware from a higher to a lower version? How do we know which version downgrades have been tested by Cisco. I dont see much info about downgrade in the release notes.
How do we manage this situation?
We dont want to add the new devices with a special load as we would like all devices in our network to have the same load.
Is upgrading the phone firmware globally on CUCM on a regular basis the only solution?
Please let me know how you manage the issue of phone firmwares on CUCM?
Many thanks for your help!!
Regards
Pete

Hi Pete,
Just to add some new fun into things, you now have to watch for
new "Hardware" versions as well. This will also impact the upgrade
& downgrade determinations made by certain phones when they
look to register. So your new phones won't downgrade to the older 9.x version and
this is why you are seeing these anomalies
So if you move past 9-3-1sr1 in the general device defaults you should be good to go.
Hardware Updates
The hardware updates improve the compatibility of internal phone components.
The following table lists the updated hardware versions that require this release.
Phone Hardware Version
Cisco Unified IP Phone 7942G
15.0 and higher
Cisco Unified IP Phone 7962G
15.0 and higher
Cisco Unified IP Phone 7945G
13.0 and higher
Cisco Unified IP Phone 7965G
13.0 and higher
Cisco Unified IP Phone 7975G
12.0 and higher
Phones manufactured with these hardware versions must run Firmware Release 9.3(1)SR1 or later. The phone firmware does not allow the phone to be downgraded to releases earlier than Release 9.3(1)SR1.
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7900_series/firmware/9_3_1SR1/release_notes/P790_BK_R4E1E768_00_rn-9_3_1_sr1-7900-series_chapter_00.html#P790_RF_ND56648A_00
Cheers!
Rob
"When it comes to luck you make your own "
- Springsteen

I can't change the maximum number of calls and busy in 8941

Hi Experts,
I have 8941 model with Camera and I can't make a second call, I tried to change the maximum number of calls, but I couldn't change it's 3 just by default,
Is there any way to solve this issue?
Thanks
Mohammad Saeed

Hi Mohammad,
A firmware or cucm upgrade is required as per the following
https://supportforums.cisco.com/document/97916/sccp89459-2-2qedinstallpdf
HTH
Manish

Sccp phones unregistred

Hi all
I am upload 7937 firmware in telephony-service and recreate cnf files .
After that when restart the SCCP phones they can't registred in CME but receive DHCP IP addresses and CME IP .
I execute no load 7937 firmware and perform no cre cnf , cre cnf in telephony-service but its not helps me. Phones who not restarted working fine
sh telephony-service
CONFIG (Version=10.5)
=====================
Version 10.5
Max phoneload sccp version 17
Max dspfarm sccp version 18
Cisco Unified Communications Manager Express
For on-line documentation please see:
http://www.cisco.com/en/US/products/sw/voicesw/ps4625/tsd_products_support_series_home.html
protocol mode default
ip source-address IP port 2000
ip qos dscp:
ef (the MS 6 bits, 46, in ToS, 0xB8) for media
cs3 (the MS 6 bits, 24, in ToS, 0x60) for signal
af41 (the MS 6 bits, 34, in ToS, 0x88) for video
default (the MS 6 bits, 0, in ToS, 0x0) for serviceservice directed-pickup
load 7916-24 cmterm-7916.1-0-4-2.cop.sgn
load 7965 SCCP45.9-4-2-1S
load 6921 SCCP69xx.9-2-1-0
max-ephones 35
max-dn 50
max-conferences 4 gain 6
dspfarm units 1
dspfarm transcode sessions 0
dspfarm 1 confprof1
conference hardware
privacy
no privacy-on-hold
hunt-group report delay 1 hours
hunt-group logout DND
max-redirect 10
cnf-file location: flash:
cnf-file option: PER-PHONE
network-locale[0] RU (This is the default network locale for this box)
network-locale[1] RU
network-locale[2] US
network-locale[3] US
network-locale[4] US
user-locale[0] RU (This is the default user locale for this box)
user-locale[1] US
user-locale[2] US
user-locale[3] US
user-locale[4] US
srst mode auto-provision is OFF
srst ephone template is 0
srst dn template is 0
srst dn line-mode single
moh music-on-hold.au
time-format 24
date-format dd-mm-yy
timezone 32 Russian Standard/Daylight Time
call-forward pattern .T
transfer-pattern .T
keepalive 180 auxiliary 30
timeout interdigit 10
timeout busy 10
timeout ringing 180
timeout transfer-recall 0
timeout ringin-callerid 8
timeout night-service-bell 12
caller-id name-only: enable
system message
web admin system name
web admin customer name Customer
edit DN through Web: enabled.
edit TIME through web: enabled.
background save interval 10 minutes
Log (table parameters):
max-size: 150
retain-timer: 15
create cnf-files version-stamp Jan 01 2002 00:00:00
transfer-system full-consult
transfer-digit-collect new-call
local directory service: enabled.
Extension-assigner tag-type ephone-tag.
Call List BLF is enabled
shutdown

I perform that
Router#configuration terminal
Router(config)#no logging console
Router(config)#no logging monitor
Router(config)#service timestamps debug datetime msec
Router(config)#logging buffered 40960 debugging
Router(config)#service sequence
Router(config)#no logging rate-limit
Router(config)#exit
debug tftp events
debug ephone detail
debug ephone register
In telephony-service i recreate cnf files and have this output :
Creating CNF files
IP address required is
TCP port required is 2000
read -1 bytes from flash:/its/SEPDEFAULT.cnf file
A0
0 item(s) of type 0
Unrecognized type 0 or format
Creating new SEPDEFAULT.cnf file size 58
58 bytes written OK..
ephone add http binding flash:/its/russia_lddefault.cfg failed
ephone add http binding flash:/its/russia_gkdefault.cfg failed
ephone add http binding flash:/its/russia_ffdefault.cfg failed
ephone add http binding flash:/its/united_states_lddefault.cfg failed
ephone add http binding flash:/its/united_states_gkdefault.cfg failed
ephone add http binding flash:/its/united_states_ffdefault.cfg failed
Just few seconds and i paste log
for DN 3 chan 1 to state CALL_END
009627: Mar 5 14:48:03.437: ephone-3[2/7]:UpdateCallState DN 3 chan 1 state 10 calleddn -1 chan 1
009628: Mar 5 14:48:03.437: ephone-3[2/7]:Binding ephone-3 to DN 3 chan 1 s2s:0
009629: Mar 5 14:48:03.437: ephone-3[2/7][SEP20BBC01F9387]:Set FAC enabled (0) and dial mode (4)
009630: Mar 5 14:48:03.437: DN 3 chan 1 End Voice_Mode
009631: Mar 5 14:48:03.437: SkinnyGetCallState for DN 3 chan 1 IDLE
009632: Mar 5 14:48:03.437: called DN -1 chan 1, calling DN -1 chan 1 phone 3 incoming s2s:0
009633: Mar 5 14:48:03.437: ephone-3[2/7]:SkinnyStopMedia: normal line=1 dn=3 ch=1
009634: Mar 5 14:48:03.437: ephone-3[2/7]:SkinnyStopMedia: CloseReceive sent: normal confID=6 ref=1120
009635: Mar 5 14:48:03.437: SkinnyGetCallState for DN 3 chan 1 IDLE
009636: Mar 5 14:48:03.437: called DN -1 chan 1, calling DN -1 chan 1 phone 3 incoming s2s:0
009637: Mar 5 14:48:03.437: ephone-3[2/7][SEP20BBC01F9387]:SkinnyStopMedia: Multimedia not active
009638: Mar 5 14:48:03.437: ephone-3[2/7]:SkinnyStopMedia: StopMedia sent: normal confID=6 ref=1120
009639: Mar 5 14:48:03.437: SkinnyGetCallState for DN 3 chan 1 IDLE
009640: Mar 5 14:48:03.437: called DN -1 chan 1, calling DN -1 chan 1 phone 3 incoming s2s:0
009641: Mar 5 14:48:03.437: ephone-3[2/7]:SpeakerPhoneOnHook
009642: Mar 5 14:48:03.437: ephone-3[2/7][SEP20BBC01F9387]:Clean up activeline 1
009643: Mar 5 14:48:03.437: ephone-3[2/7][SEP20BBC01F9387]:UpdateCallState unbind phone from DN 3
009644: Mar 5 14:48:03.437: ephone-3[2/7][SEP20BBC01F9387]:ClearCallPrompt line 0 ref 0
009645: Mar 5 14:48:03.437: ephone-3[2/7][SEP20BBC01F9387]:SkinnyCheckPendingCallBackPhone scan 2 lines
009646: Mar 5 14:48:03.437: ephone-3[2/7]:SelectPhoneSoftKeys set 0 mask FFBF for line 0 ref 0
009647: Mar 5 14:48:03.437: SkinnySetCallInfoName calling dn -1 chan 1 dn 3 chan 1,calling [] called []
009648: Mar 5 14:48:03.437: SetCallInfo DN 3 chan 1 is not skinny-to-skinny
009649: Mar 5 14:48:03.437: SkinnyStopDnRecallTimer: dn 3 chan 1
009650: Mar 5 14:48:03.437: Skinny Call State change for DN 3 chan 1 CALL_END from CONNECTED
009651: Mar 5 14:48:03.437: ephone-(3) DN 3 chan 1 calledDn -1 chan 1 callingDn -1 chan 1 :: port=0 incoming
009652: Mar 5 14:48:03.437: SkinnyUpdateCstate DN 3 chan 1 cstate 2
009653: Mar 5 14:48:03.437: SkinnyGetCallState for DN 3 chan 1 IDLE
009654: Mar 5 14:48:03.437: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009655: Mar 5 14:48:03.437: ephone-3[2/7][SEP20BBC01F9387]:SkinnyUpdateCstate first phone for DN 3 chan 1 ref 1120
009656: Mar 5 14:48:03.437: ephone-3[2/7][SEP20BBC01F9387]:UpdateCState found DN 3 on line 1
009657: Mar 5 14:48:03.437: ephone-3[2/7]:SkinnyUpdateCState process cstate 2 for inactive DN 3 chan 1 line 1 (activeLine=0 whisperLine=0)
009658: Mar 5 14:48:03.437: ephone-3[2/7]:SkinnyUpdateCstate inactive (overlay) line 1 for DN 3 ref 1120 combo=0
009659: Mar 5 14:48:03.437: DN 3 chan 1 ephone-3 state set to 2
009660: Mar 5 14:48:03.437: SkinnyGetCallState for DN 3 chan 1 IDLE
009661: Mar 5 14:48:03.437: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009662: Mar 5 14:48:03.437: ephone-3[7]:SetCallState line 1 DN 3(3) chan 1 ref 1120 TsOnHook
009663: Mar 5 14:48:03.441: ephone-3[2/7]:SkinnyTrackActiveCall for line 1 ref 1120 state 2 (slot 0)
009664: Mar 5 14:48:03.441: ephone-3[2/7]:SelectPhoneSoftKeys set 0 mask FFBF for line 1 ref 1120
009665: Mar 5 14:48:03.441: SkinnyGetCallState for DN 3 chan 1 IDLE
009666: Mar 5 14:48:03.441: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009667: Mar 5 14:48:03.441: SkinnyGetCallState for DN 3 chan 1 IDLE
009668: Mar 5 14:48:03.441: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009669: Mar 5 14:48:03.441: ephone-3[2/7]:Clean Up Speakerphone state
009670: Mar 5 14:48:03.441: ephone-3[2/7]:SpeakerPhoneOnHook
009671: Mar 5 14:48:03.441: ephone-3[2/7]:Speaker is not on, SpeakerPhoneOnHook suppressed
009672: Mar 5 14:48:03.441: ephone-3[2/7][SEP20BBC01F9387]:SkinnyGetToneRef toneRef 0x0 callRef 0x460
009673: Mar 5 14:48:03.441: ephone-3[2/7]:SkinnyPhoneToneDirect: StopTone sent: normal line=1 ref=1120 tone=0x0
009674: Mar 5 14:48:03.441: Skinny StopTone sent on ephone socket [7]
009675: Mar 5 14:48:03.441: SkinnyGetCallState for DN 3 chan 1 IDLE
009676: Mar 5 14:48:03.441: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009677: Mar 5 14:48:03.441: ephone-3[2/7]:SelectPhoneSoftKeys set 0 mask FFBF for line 0 ref 0
009678: Mar 5 14:48:03.441: SkinnyGetCallState for DN 3 chan 1 IDLE
009679: Mar 5 14:48:03.441: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009680: Mar 5 14:48:03.441: ephone-3[7]:SetLineLamp 1 to OFF
009681: Mar 5 14:48:03.441: UnBinding ephone-3 from DN 3 chan 1
009682: Mar 5 14:48:03.441: ephone-3[2/7]:---SkinnySyncPhoneDnOverlays is onhook
009683: Mar 5 14:48:03.441: SkinnyGetCallState for DN 3 chan 1 IDLE
009684: Mar 5 14:48:03.441: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009685: Mar 5 14:48:03.441: ephone-3[2/7][SEP20BBC01F9387]:SkinnyArmPhoneCallbacks scan 2 lines
009686: Mar 5 14:48:03.441: ephone-3[2/7][SEP20BBC01F9387]:ClearCallPrompt line 0 ref 0
009687: Mar 5 14:48:03.441: ephone-3[2/7][SEP20BBC01F9387]:SkinnyCheckPendingCallBackPhone scan 2 lines
009688: Mar 5 14:48:03.441: SkinnyGetCallState for DN 3 chan 1 IDLE
009689: Mar 5 14:48:03.441: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009690: Mar 5 14:48:03.441: SkinnyReportDnState for overlay DN 3 chan 1 on ephone-1
009691: Mar 5 14:48:03.441: SkinnyReportDnState DN 3 chan 1 ONHOOK
009692: Mar 5 14:48:03.441: ephone-3[2/7]:SkinnyConfirmOnHookAck: dn 3 chan 1 dn_index 3 phone=2, pickupOnHook=0
009693: Mar 5 14:48:03.441: ephone-3[2/7][SEP20BBC01F9387]:ClearCallPrompt line 0 ref 0
009694: Mar 5 14:48:03.441: ephone-3[2/7][SEP20BBC01F9387]:SkinnyCheckPendingCallBackPhone scan 2 lines
009695: Mar 5 14:48:03.445: dn_tone_control DN=3 chan 1 tonetype=0:DtSilence onoff=0 pid=418
009696: Mar 5 14:48:03.445: SkinnyGetCallState for DN 3 chan 1 IDLE
009697: Mar 5 14:48:03.445: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009698: Mar 5 14:48:03.445: ephone-3[2/7]:Check toneOn state for last_phone
009699: Mar 5 14:48:03.445: SkinnyGetCallState for DN 3 chan 1 IDLE
009700: Mar 5 14:48:03.445: called DN -1 chan 1, calling DN -1 chan 1 phone -1 incoming s2s:0
009701: Mar 5 14:48:03.665: ephone-3[2/7][SEP20BBC01F9387]:Update Stats Total for DN 3 chan 1
009702: Mar 5 14:48:03.761: ephone-3[2/7][SEP20BBC01F9387]:MediaPathEventMessage Handset OFF
009703: Mar 5 14:48:03.761: ephone-3[2/7]:MediaPathEventMessage

Get error when i reset my ip phone

Hi;
I reset some 7931 and 7942 ip phone in my environment and after reseting i see the screen display "UPGRADING" and the Mac address.
Can please someone help me solve this issue.

Does the upgrade finish at all?
what you are seeing is that the firmware you are running on the phones is lower that the default firmware of CUCM/CME or whatever you are running.
=============================
Please remember to rate useful posts, by clicking on the stars below.
=============================

CUCM is loading the same firmware as on a phone.

Hello everybody,
I have a phone with the firmware: SCCP45.9-0-2SR1S.loads
Added it to CUCM v8.0.2 and CUCM loaded a new firmware to the phone, but
/Device/Device Settings/Device Default
Cisco 7965 SCP SCCP45.9-0-sSR1S Def. Standard 7965 SCCP
Why it is loading the same version of the firmware?
How to stop reload the phone?
Thank you in advance.

You need to make sure the firmware name defined in the device default phone page of CUCM matches the actual firmware name less the period before "loads" and anything to the right of the period. The first thread shows an inconssitancy between the firmware name and the listing in the device defaults..
have a phone with the firmware: SCCP45.9-0-2SR1S.loads
Added it to CUCM v8.0.2 and CUCM loaded a new firmware to the phone, but
/Device/Device Settings/Device Default
Cisco 7965 SCP SCCP45.9-0-sSR1S Def. Standard 7965 SCCP (lower case "s" should be a number 2)

CUCM, Why do we have to install firmware in every CPE?

Hi people,
I was wondering, (and I’m sure I DID read), on some CUCM documents that when we upgrade a firmware for a Phone, we have to upgrade the firmware in every CPE (Active Call Manager Node), and on the TFTP server, then do a wide cluster restarts.
Why does Cisco advise that if there is only a TFTP server and I backup TFTP server that some on the cases even don't run the Call Manager Service?
Sorry for this question,
I hope you guys borrow me some of your time, I'll appreciate it!

Manish is spot on. It is very key to understand that there is a difference between upgrading the firmware for an existing device type and adding a new device type. When upgrading the firmware of an existing device type, you only need to install the firmware cop file on the publisher node and the TFTP nodes. The former so things like Dev Defaults get updated. The latter because the TFTP nodes access their local file repository when serving files.
You have to restart the TFTP service so that the server can refresh cache. You DO NOT need to load firmware images on cluster nodes that are not running the TFTP service. In larger clusters, it is common to have nodes designated as TFTP only or as media only (or as TFTP + Media, if you walk that line).
When installing a dev pack, you typically need to update the db schema and update various web (admin/user) files (while accounting for new locales, etc.). Since the installer touches various file system locations, db tables, etc., Cisco opts to go for a UCM reload. Since you have to install dev packs on each server, that leads to the cluster reload scenario.
-Bill

CUCM V10 Phone firmware versions

Hi All, Try as I may I cannot find the documentation that specifies what versions of phone firmware is included in CUCM V10. I'm sure I found it under release notes but no, not there.
Any ideas?
Thanks Folks

Hi Paul,
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/10_0_1/delta/CUCM_BK_C206A718_00_cucm-new-and-changed-1001/CUCM_BK_C206A718_00_cucm-new-and-changed-1001_chapter_011.html#CUIP_RF_CDA0C75B_00
Table 1 Phone Firmware Versions
Phone family
Firmware release number
Cisco Unified SIP Phone 3905
9.4(1)
Cisco Unified IP Phones 6901 and 6911
9.3(1)SR1
Cisco Unified IP Phones 6921, 6941, 6945, and 6961
9.4(1)
* Cisco IP Phone 7800 Series
10.1(1)
Cisco Unified IP Phone 7900 Series
9.3(1)SR2
Cisco Unified Wireless IP Phone 792x Series
1.4(5)
* Cisco Unified IP Conference Phone 8831
9.3(3)
Cisco Unified IP Phones 8941 and 8945
9.3(2)SR1
Cisco Unified IP Phones 8961, 9951, and 9971
9.4(1)
HTH
Manish

How to know firmware version for all devices in a CUCM cluster

Hello,
We need to know the firmware version used for each one of the devices in a CUCM cluster (version 6.1)
Anybody know if we can get this info for example wit the BAT?
Thanks and regards,

You typically need to use a 3rd Party application to do this.
There are many that can do basic device information gathering, but if you are looking for a complete endpoint solution that scales to 10,000+ devices you should have a look at PhoneView from UnifiedFX (http://www.unifiedfx.com)
Thanks
Stephen

Downloading Firmware into 7975 from CUCM

Hello All,
I have Issues with a 7975 IP phone downloading firmware and registering with call manager 7.1. The IP Phone is for cts 1300 and its new whenever i connect to the cucm its shows the file SIP.75.9-0-2SR1S to be downloaded but suddenly shows Auth fail , it keeps showing the same all over. Please what do you think can be done to make me the phone register with the call manager. or is there another way that I can load the firmware into the phone without connecting to the call manager.

Search for "Auth fail" here and you will find many similar posts.
It is either that your current firmware is too old and you need 2 steps upgrade, or it may be ITL cert issue.
HTH,
Chris

Cisco IP Phone 7945-G or 7965-G screen goes blank randomly with SCCP firmware 9.2(3) on CUCM 8.6(2a)

Hello everybody,
I have the following situation:
A WAN VoIP network, with centralized call processing model (central site and few branches)
Cisco IP Phones 7945-G and 7965-G running SCCP
Cisco Unified Communications Manager 8.6(2a)
SCCP firmware Release 9.2(3) for the above mentioned hardware models
The problem that occurs randomly is that either when the firmware was SCCP firmware Release 9.2(1), or it was upgraded to SCCP firmware Release 9.2(3), approximately 5 Cisco IP Phones, the screen goes blank, the phone being still operational (but difficult to operate in such circumstances), and the problem persists until it is disconnected from PoE, and re-connected.
Please if possible, any solution to this problem is much appreciated.
Thank you in advance.
Radu

Hello again,
In addition to what I already mentioned, I would like to detail a few aspects, in order to be more specific with this behavior:
-          From the total number of Cisco IP phones which is less than 1000, this behavior happened randomly, within 1 month and 3 weeks
-          Actually, it was a total number of 8 Cisco IP phones whose display went off, 4 being located in Headquarters, and from the other 4, 3 were in the same Branch, and 1 in another Branch
-          Also, 7 IP phones are connected in non-Cisco switches with PoE, and 1 IP Phone was power supplied from AC adapter
-          initially, all existing IP phones had firmware Release 9.2(1) for 7945G and 7965G, and the mentioned behavior happened with 4 IP phones
-          then, for all IP phones, it were upgraded to firmware Release 9.2(3) for 7945G and 7965G, but problem re-appeared with other 4 IP phones
The only solution that solved the issue for each IP phone was to disconnect the power from the IP phones.
I hope that you might help me on how to get solving this problem, and I am looking forward for any useful idea or solution.
Many thanks in advance.
Regards,
Radu

"Error encountered: ERROR: Final installdb run unsuccessful" during firmware cop installation

Hi all,
Just a heads up to anyone else who encounters this error when installing device firmware cop files onto CUCM.
We were upgrading the firmware on our CUCM cluster (small - consists of 1 x Publisher and 1 x Subscriber) - running 8.0.2.40000-1
I was installing:
cmterm-7936-sccp.3-3-21.cop.sgn
cmterm-7937-1-4-4-SCCP.cop.sgn
cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn
cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn
When doing so on the publisher server - it was throwing the following error output (note that the files actually ended up on the TFTP server but devices were not picking up the new firmware):
Installation Status
File           cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn
Start Time           Thu Mar 06 19:34:24 WST 2014
Status
Error encountered: ERROR: Final installdb run unsuccessful
03/06/2014 19:33:42 file_list.sh|Starting file_list.sh|<LVL::Info>
03/06/2014 19:33:42 file_list.sh|Parse argument method=sftp|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Parse argument source_dir=/|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Parse argument dest_file=/var/log/install/downloaded_versions|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Parse argument remote_host=10.133.1.240|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Parse argument user_name=ccmadministrator|<LVL::Debug>
03/06/2014 19:33:42 file_list.sh|Calling SFTP command with metering off|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|SFTP command complete (0)|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|List file (pre-filtered):|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) RSA|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) UC|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) WIRELESS|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) asa914-k8.bin|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) cmterm-7936-sccp.3-3-21.cop.sgn|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) cmterm-7937-1-4-4-SCCP.cop.sgn|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|(CAPTURE) cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Debug>
03/06/2014 19:33:43 file_list.sh|/usr/local/bin/base_scripts/filter.sh file=/var/log/install/downloaded_versions|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Parse argument file=/var/log/install/downloaded_versions|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|No patch type specified. Optional.|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|No upgrade mode specifed. Optional.|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Current version is 8.0.2.40000-1|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "RSA"|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|INorOUT=OUT RSA: Not a signed patch file|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "UC"|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|INorOUT=OUT UC: Not a signed patch file|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "WIRELESS"|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|INorOUT=OUT WIRELESS: Not a signed patch file|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "asa914-k8.bin"|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|INorOUT=OUT asa914-k8.bin: Not a signed patch file|<LVL::Debug>
03/06/2014 19:33:43 filter.sh|Processing token "cmterm-7936-sccp.3-3-21.cop.sgn"|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|INorOUT=IN cmterm-7936-sccp.3-3-21.cop.sgn: filter passed|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|Processing token "cmterm-7937-1-4-4-SCCP.cop.sgn"|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|INorOUT=IN cmterm-7937-1-4-4-SCCP.cop.sgn: filter passed|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|Processing token "cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn"|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|INorOUT=IN cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn: filter passed|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|Processing token "cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn"|<LVL::Debug>
03/06/2014 19:33:44 filter.sh|INorOUT=IN cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn: filter passed|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|List file (post-filtered):|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) RSA:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) UC:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) WIRELESS:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) asa914-k8.bin:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7936-sccp.3-3-21.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7937-1-4-4-SCCP.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|List file (pre-structured):|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) RSA:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) UC:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) WIRELESS:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) asa914-k8.bin:1|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7936-sccp.3-3-21.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7937-1-4-4-SCCP.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:44 file_list.sh|(CAPTURE) cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn:0|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|List file (post-structured):|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE) <InstallList>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <FilteredItem type="" file="RSA" result="1"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <FilteredItem type="" file="UC" result="1"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <FilteredItem type="" file="WIRELESS" result="1"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <FilteredItem type="" file="asa914-k8.bin" result="1"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <InstallItem type="copfile" secure-file="cmterm-7936-sccp.3-3-21.cop.sgn" version="" file="cmterm-7936-sccp.3-3-21.cop" reboot="no"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <InstallItem type="copfile" secure-file="cmterm-7937-1-4-4-SCCP.cop.sgn" version="" file="cmterm-7937-1-4-4-SCCP.cop" reboot="no"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <InstallItem type="copfile" secure-file="cmterm-7941_7961-sccp.9-3-1SR2-1.cop.sgn" version="" file="cmterm-7941_7961-sccp.9-3-1SR2-1.cop" reboot="no"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE)     <InstallItem type="copfile" secure-file="cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn" version="" file="cmterm-7945_7965-sccp.9-3-1SR2-1.cop" reboot="no"/>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|(CAPTURE) </InstallList>|<LVL::Debug>
03/06/2014 19:33:46 file_list.sh|success|<LVL::Info>
03/06/2014 19:33:46 file_list.sh|file_list.sh complete (rc=0)|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Starting upgrade_validate_file.sh|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument method=sftp|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument source_dir=/|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument file_name=cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument remote_host=10.133.1.240|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Parse argument user_name=ccmadministrator|<LVL::Debug>
03/06/2014 19:34:19 upgrade_validate_file.sh|Getting patch size via sftp for cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Size of patch file = 6018125|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Total space needs = 12036250|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh| Free space : 126461788160|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|Space needed : 24072500|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|There is enough space on device to proceed.|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|success|<LVL::Info>
03/06/2014 19:34:19 upgrade_validate_file.sh|upgrade_validate_file.sh complete (rc=0)|<LVL::Info>
03/06/2014 19:34:19 upgrade_get_file.sh|Starting upgrade_get_file.sh|<LVL::Info>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument method=sftp|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument source_dir=/|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument file_name=cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument dest_dir=/common/download/|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument remote_host=10.133.1.240|<LVL::Debug>
03/06/2014 19:34:19 upgrade_get_file.sh|Parse argument user_name=ccmadministrator|<LVL::Debug>
03/06/2014 19:34:20 upgrade_get_file.sh|Starting SFTP of cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|SFTP command complete (0)|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|Download of iso file RTMTStart|<LVL::Notice>
03/06/2014 19:34:21 upgrade_get_file.sh|Create md5 "/common/download/cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn.md5"|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|MD5(/common/download/cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn)= e3:02:d3:e1:89:ff:a1:eb:0a:71:52:03:ad:d7:e2:85|<LVL::Debug>
03/06/2014 19:34:21 upgrade_get_file.sh|Create md5 complete|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|Authenticate file "/common/download/cmterm-7945_7965-sccp.9-3-1SR2-1.cop.sgn"|<LVL::Info>
03/06/2014 19:34:21 upgrade_get_file.sh|File authentication complete|<LVL::Debug>
03/06/2014 19:34:21 upgrade_get_file.sh|Download of iso file RTMTFinish|<LVL::Notice>
03/06/2014 19:34:22 upgrade_get_file.sh|success|<LVL::Info>
03/06/2014 19:34:22 upgrade_get_file.sh|upgrade_get_file.sh complete (rc=0)|<LVL::Info>
03/06/2014 19:34:24 Terminating active side processes
03/06/2014 19:34:24 Terminating active side processes done
03/06/2014 19:34:24 Terminating inactive side processes
03/06/2014 19:34:24 Calling /usr/local/bin/base_scripts/sd_killPartitionB_PIDs.sh
03/06/2014 19:34:24 Terminating inactive side processes done
(13953) Thu Mar 6 19:34:30 WST 2014
install option
(13953) Thu Mar 6 19:34:30 WST 2014
Successful untarring of option /common/download//cmterm-7945_7965-sccp.9-3-1SR2-1.cop.
(13953) Thu Mar 6 19:34:36 WST 2014
Publisher: Starting installdb... /bin/su -l informix -s /bin/sh -c "source /usr/local/cm/db/dblenv.bash /usr/local/cm ; source /usr/local/cm/db/informix/local/ids.env ; nice /usr/local/cm/bin/installdb -x /usr/local/cm/db/xml/xml"
disablenotify rc[0]
xml DSN=ccm_super /usr/local/cm/db/xml/xml
installXml rc[1]
enablenotify dsn[DSN=ccm_super]
enablenotify rc[0]
installdb Failure [-x] 1
(13953) Thu Mar 6 19:34:47 WST 2014
ERROR: Final installdb run unsuccessful
I'd read in various places to perform a CLI command "run loadxml" - which we did but it produced the following output:
admin:run loadxml
This command is processor intensive, and may take a few minutes to run.
It should only be run on the publisher.
Some services may require a restart afterwards.
This is a CPU intensive command and will take a considerable amount of time to complete. Do you want to continue (y/n)?
Starting loadxml
disablenotify dsn[DSN=ccm_super]
disablenotify rc[0]
xml DSN=ccm_super /usr/local/cm/db/xml/xml
installXml rc[1]
enablenotify dsn[DSN=ccm_super]
enablenotify rc[0]
installdb Failure [-x] 1
loadxml function complete
Failure essentially.
Note that the installation went ahead without issues on the Subscriber servers after we tried on the publisher. I believe this is due to it only copying the files to the TFTP server and not updating the database.
I also noted that the following features vanished from the CUCM Administration GUI (the menus were there but the pages came up blank):
"Enterprise Paramaters"
"Enterprise Phone Configuration"
"Service Parameters" (after selecting "server" & "service" drop down options, nothing was displayed)
Within individual "Phone Configuration" - the entire "Product Specific Configuration Layout" was missing from all devices.
I was also unable to export the 'Cisco Database Installation Service' logs from RTMT - it threw an error to the status bar at the bottom stating "Collection cancelled for node <publisher> due to the error" (and there was no error info output...joy!).
I called in TAC and Roman Kramarski assisted me via WebEx to full resolution of the issue - thanks Roman
After running "run loadxml"
We ran the following command which showed us (after much wizzing by of entries) the list of log files, the 5th or so last file in the list being the log output from the "run loadxml" output -
The command: "file list activelog /cm/trace/dbl/sdi detail date"
Our file in question happened to be called "installdb20140306-230735.log" (like I said, was about 5th from the bottom of the list)
Next we viewed the file:
"file view activelog /cm/trace/dbl/sdi/installdb20140306-230735.log"
In the file, fairly close to the top, it showed the following error message:
"23:07:35.047 |   DOMErrorReporter::fatalError *ERROR* Fatal Error at file /usr/local/cm/db/xml/xml/366X_display_instance-fxo_port_gs.xml, line 56, column 22"
This, along with the output of the run loadxml command, indicated that "/usr/local/cm/db/xml/xml/366X_display_instance-fxo_port_gs.xml" file was corrupted or incomplete.
Roman (TAC) then used the Cisco access to root in order to look at the actual file.
It was incomplete - it ended mid closure of a tag:
"<name>OutputAttenuation</n#"
(Instead of "<name>OutputAttenuation</name>" plus a whole bucketload more output.
Luckily I had a fresh install of the exact same version of CUCM just installed on in a dev environment - so Roman was able to get into that one, TFTP the file out, and then TFTP the new file in.
We moved the old corrupt file into another folder (as we renamed it initially and then ran "run loadxml" which produced the error again) - copied the new complete file into the folder - then "run loadxml" ran successfully.
admin:run loadxml
This command is processor intensive, and may take a few minutes to run.
It should only be run on the publisher.
Some services may require a restart afterwards.
This is a CPU intensive command and will take a considerable amount of time to complete. Do you want to continue (y/n)?
Starting loadxml
disablenotify dsn[DSN=ccm_super]
disablenotify rc[0]
xml DSN=ccm_super /usr/local/cm/db/xml/xml
installXml rc[0]
enablenotify dsn[DSN=ccm_super]
enablenotify rc[0]
installdb Success[-x]
loadxml function complete
NOTE that the running of run loadxml did not take that long and didn't cause any outages to my system.
After we did this - the installations went ahead successfully.
After a restart of the TFTP service on each server - firmware upgrades went ahead successfully.
Basically - you can do the initial troubleshooting of checking logs of run loadxml and then pass that detail to Cisco TAC to get them to use root access to copy a fresh version of the file across.
Hope this helps.

Hi Thanks for the information, this help me a lot, I have the same issue but with some differences, because when I search the error on the log file, I saw
08/25/2014 06:14:49.911 installdb|   DOMErrorReporter::fatalError *ERROR* Fatal Error at file , line 0, column 0
message: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=/usr/local/cm/db/xml/xml/ICS77XX_MRP2XX_display_instance-bri.xml|
08/25/2014 06:14:49.911 installdb|<--DOMErrorReporter::fatalError |
When I search the file I couldn´t find it, so I think this could be because I made a booteable ISO from an upgrade from the Cisco Page, so I go to the production server version 6.1.2 and copied the file missing into my lab and run the command "run loadxml" sucessfully, after that everything works great!
Thanks in advance for your time to post this.
Regards!

Add new type phones CUCM 4.2

Hello, i have work to buy new phones in organization. But 7900 not selling now, how i see. How i can add new types phones to my CUCM.
Thanks!

Hi Dmitry,
The "G" in the suffix of these models (like 7941G) stands for Global. The
"GE" in the 7941G-GE stands for "Gigabit ethernet" as it is a 10/100/1000
model.
Keep in mind that there are 7900 models like the 7945G/65G and
7942G/62G that are not End of Sale or End of Life and can be added to
CCM 4.2(3) with the installation of a Device Pack like the one shown below;
Firmware Versions
Cisco Unified CallManager Device Package 4.2.3(60.0) includes the following firmware versions:
Firmware
4.2(3)Devpack   60
Analog Access   WS-X6624
A00204000013   / A0034322
Digital Access   WS-X6608
D00404000032   / D0054322
Conference Bridge WS-X6608
C00104000003   / C002E031
Media Termination   Point WS-X6608
M00104000006   / M002E031
ATA18X
ATA030204SCCP090202A
7915-12 Button   Extension Module
B015-1-0-3
7915-24 Button   Extension Module
B015-1-0-3
7916-12 Button   Extension Module
B016-1-0-3
7916-24 Button   Extension Module
B016-1-0-3
IP Phone 7902g
CP7902080002SCCP060817A
IP Phone 7905g
CP7905080003SCCP070409A
IP Phone 7906G/11
SCCP11.8-4-4S
IP Phone 7912g
CP7912080003SCCP070409A
IP Phone 7920
cmterm_7920.4.0-03-02
IP Phone 7921g
CP7921G-1.3.2
P Phone 7925g
CP7925G-1.3.2
IP Phone 7935
P00503021900
IP Phone 7936
cmterm_7936.3-3-20-0
IP Phone 7937
apps37sccp.1-3-3-0
IP Phone 7941/7961
SCCP41.8-4-4S
IP Phone   7941G/7961G
SCCP41.8-4-4S
IP Phone 7942/7962
SCCP42.8-4-4S
IP Phone 7945/7965
SCCP45.8-4-4S
IP Phone 7970/7971
SCCP70.8-4-4S
IP Phone 7975
SCCP75.8-4-4S
IP Phone 7985
cmterm_7985.4-1-7-0
IP Phone 7960
P00308010100
IP Phone 7940
P00308010100
7914 14-Button Line   Expansion Module
S00105000400
http://www.cisco.com/web/software/282074299/26745/ciscocm.4-2-3-DevPack-60_readme.html
Available via this path;
Downloads Home
Products
Voice and Unified Communications
IP Telephony
Unified Communications Platform
Cisco Unified Communications Manager (CallManager)
Cisco Unified CallManager Version 4.2
Unified Communications Manager/CallManager Device Packages-4.2(3.60)
Cheers!
Rob
"Clocks go slow in a place of work
Minutes drag and the hours jerk"
-The Clash

Phone Firmware upgradation

Hi All ,
Again I am distrub you guys, I have some issue to discusses with you guys, if you have time please help me out for this.
My problem is that we a one CUCM(Ver 8.0.3) Cluster and we have more then 9000 phone device with dfferent models with more then 100 locations, like
6921
6941
7925
7937
7942
7942G
7960
7961
7962
7962
7970
but most of them are 7942G,
we already upload all new firmwares on our CUCM cluster but not using new firmware right now ,
now challenge is that that we have to upload these new firmwares site by site because we have more then 100 side and more then 9000 devices
and we are not sure that if we upload in one shot for all 9000 deveice so what kind of the issues we will face.
So my problem is that I need a information that how to upload these new firmwares site by site with minimal facsing issues, so my request to all of you that
please help and guide me , I will be thankfull to all of you.
Hop i will rceeive reply very soon.
Thanks
RS

You can upload it to your TFTP servers and then use BAT to set the FW phones need to download in batches.

7937 Firmware on CUCM 10.5

Similar Messages

Maybe you are looking for