Reriy
asked on
Cisco IP Phone 7941 Problems setting Factory Default
Hello everyone! Im having problems with a Cisco IP Phones 7941. I want to issue the factory reset and I know how to do but when im booting I get stuck on the upgrading screen.
To initiate the factory reset I did this:
1.Start with the phone in a powered off state.
2.While holding the "#" key down on the keypad, apply power to the phone.
3.Keep the "#" key depressed until you see the LEDs on the phone begin a 'walking' sequence, where they walk down from top to bottom.
4.After you see the LED walk sequence begin, you can release the "#" key and enter one of the reset sequences below. You have to enter the sequence as is, any deviation from the given sequence will abort the factory reset and resume a normal boot sequence.
#Soft Reset
The code for the soft factory reset is: 123456789*0#
But I don't have a DHCPserver hooked to my phone with the "termx41.default.loads" file that I need to update the phone after a factory reset. I'm having problems finding where I do download that particular file.
Anyone know how I can get a hold of this file? Or am i doing something wrong?
To initiate the factory reset I did this:
1.Start with the phone in a powered off state.
2.While holding the "#" key down on the keypad, apply power to the phone.
3.Keep the "#" key depressed until you see the LEDs on the phone begin a 'walking' sequence, where they walk down from top to bottom.
4.After you see the LED walk sequence begin, you can release the "#" key and enter one of the reset sequences below. You have to enter the sequence as is, any deviation from the given sequence will abort the factory reset and resume a normal boot sequence.
#Soft Reset
The code for the soft factory reset is: 123456789*0#
But I don't have a DHCPserver hooked to my phone with the "termx41.default.loads" file that I need to update the phone after a factory reset. I'm having problems finding where I do download that particular file.
Anyone know how I can get a hold of this file? Or am i doing something wrong?
ASKER
Ok thanks for that link and reply. Is there a way to skip the update after the factory reset or do I have to update?
If I can't sign a service contract is there no way to get a hold of the software if I really need to update?
If I can't sign a service contract is there no way to get a hold of the software if I really need to update?
You do not need to upgrade after factory reset. These phones check for new image after every (hard/soft) reset. The image name is specified in the phone's cnf file. If the phone is running a different image, then it downloads the new image from tftp server and upgrades itself. So it will upgrade, only if you create a phone configuration file with a different image name.
As I know, Cisco provides software updates only if you have a service contract with them.
As I know, Cisco provides software updates only if you have a service contract with them.
ASKER
Yes they only provide that if you have a contract with them and I don't.....
Ok thanks on teh fact that I don't have to update the phone but how do I then workaround the updating page that shows when I boot after the factory reset?
Ok thanks on teh fact that I don't have to update the phone but how do I then workaround the updating page that shows when I boot after the factory reset?
Take a look at the following page that discusses how he images the phone.
https://supportforums.cisco.com/thread/2019804/
The image they are putting on the phone is named cmterm-7941_7961-sccp.8-5-
https://supportforums.cisco.com/thread/2019804/
The image they are putting on the phone is named cmterm-7941_7961-sccp.8-5-
ASKER
thanks for the great hint and verry much for the filename I found it now and when I get to work tomorrow i will try setting up a tftpserver to get it working!
;-) Cheers!
ASKER
sorry for the long break in the discussion... but this is the current state of the problem:
I have found the firmware that I need to update the phone with and I have a TFTP-server to transfer it with but the TFTP-server and Phone can't find eachother.....
I have downloaded a DHCP-server that could make it work? But I don't know how to operate it...
so now the question: Have I gone the totally wrong direction or what am I doing wrong?
Im using "Ubuntu 10.04" on the computer where I have the TFTP and DHCP server.
I have found the firmware that I need to update the phone with and I have a TFTP-server to transfer it with but the TFTP-server and Phone can't find eachother.....
I have downloaded a DHCP-server that could make it work? But I don't know how to operate it...
so now the question: Have I gone the totally wrong direction or what am I doing wrong?
Im using "Ubuntu 10.04" on the computer where I have the TFTP and DHCP server.
Have you set the option 150 on your DHCP server? SCCP phones use option 150 for the TFTP server, while SIP uses option 66. So option 150 should point to the ip address of your tftp server. Take a look at the following link for an example
http://www.beyondweblogs.com/post/How-to-Convert-upgrade-a-Cisco-79407960-firmware-from-SCCP-to-SIP.aspx
http://www.beyondweblogs.com/post/How-to-Convert-upgrade-a-Cisco-79407960-firmware-from-SCCP-to-SIP.aspx
ASKER
Hello abahar!
thanks for the quick reply I have not set option 150 on the DHCP server. THe link you provided is for a windows DHCP server. Im using "dhcpx" in Ubuntu 10.04 when I issue the dhcpx command I get this list:
--------------------------
cisco@cisco-laptop:~$ dhcpx
dhcpx [-v[[v]]] -i <interface> [-A]
[-D <destination>]
[-t <discovery time in secs>]
[-u <ARP time in secs>]
cisco@cisco-laptop:~$
--------------------------
How should I act?
thanks for the quick reply I have not set option 150 on the DHCP server. THe link you provided is for a windows DHCP server. Im using "dhcpx" in Ubuntu 10.04 when I issue the dhcpx command I get this list:
--------------------------
cisco@cisco-laptop:~$ dhcpx
dhcpx [-v[[v]]] -i <interface> [-A]
[-D <destination>]
[-t <discovery time in secs>]
[-u <ARP time in secs>]
cisco@cisco-laptop:~$
--------------------------
How should I act?
I found this sample dhcpd configuration for Cisco ip phone. I hope dhcpx uses the same file and syntax. Otherwise use dhcpd.
# /etc/dhcpd.conf
ddns-update-style interim;
ignore client-updates;
# Define Custom Options
option option-150 code 150 = ip-address;
# Global Config
option ip-forwarding off;
option nis-domain "domain.local";
option domain-name "domain.local";
default-lease-time 21600;
max-lease-time 43200;
subnet 192.168.117.0 netmask 255.255.255.0 {
option routers 192.168.0.1; #
Default Gateway
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option domain-name-servers 192.168.0.10;
option nntp-server 192.168.0.10;
option time-offset -18000; #
Eastern Standard Time
option option-150 192.168.200.10;
# TFTP Custom Option
next-server 192.168.200.10;
# TFTP Boot
range dynamic-bootp 192.168.0.200 192.168.0.249;
}
# /etc/dhcpd.conf
ddns-update-style interim;
ignore client-updates;
# Define Custom Options
option option-150 code 150 = ip-address;
# Global Config
option ip-forwarding off;
option nis-domain "domain.local";
option domain-name "domain.local";
default-lease-time 21600;
max-lease-time 43200;
subnet 192.168.117.0 netmask 255.255.255.0 {
option routers 192.168.0.1; #
Default Gateway
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option domain-name-servers 192.168.0.10;
option nntp-server 192.168.0.10;
option time-offset -18000; #
Eastern Standard Time
option option-150 192.168.200.10;
# TFTP Custom Option
next-server 192.168.200.10;
# TFTP Boot
range dynamic-bootp 192.168.0.200 192.168.0.249;
}
ASKER
thanks that config worked all good but the "subnet 192.168.117.0" that I changed to 192.168.0.0
At the moment I have connection between the computer running as TFTP and DHCP server and the phone. Im using dhcpd and trashed dhcpx.
A new problem have come up though. The phone is stuck in a endless loot booting up to the upgrading screen and then shows the IP 192.168.0.200 in the uper box and starts to download a file called "term41.default" then when it finish it reboots and does it all over again.
What have happend? why is it trying to download that file and why does it not respond to my put command?
At the moment I have connection between the computer running as TFTP and DHCP server and the phone. Im using dhcpd and trashed dhcpx.
A new problem have come up though. The phone is stuck in a endless loot booting up to the upgrading screen and then shows the IP 192.168.0.200 in the uper box and starts to download a file called "term41.default" then when it finish it reboots and does it all over again.
What have happend? why is it trying to download that file and why does it not respond to my put command?
ASKER
192.168.0.200 is the phones own IP why is it trying to connect to itself and downloading the file?
Hi, I haven't manually upgraded a phone image before. As I know term41.default is used only if the phone does not find the right image for its MAC address.
So do you have that firmware term41.default on your tftp server?
>192.168.0.200 is the phones own IP why is it trying to connect to itself and downloading the file?
How do you know that it is trying to download the file from itself? If you set DHCP correctly, than it should download from the ip address option 150 points to.
So do you have that firmware term41.default on your tftp server?
>192.168.0.200 is the phones own IP why is it trying to connect to itself and downloading the file?
How do you know that it is trying to download the file from itself? If you set DHCP correctly, than it should download from the ip address option 150 points to.
ASKER
Hi,
> So do you have that firmware term41.default on your tftp server?
I searched the computer im running the tftp server from and I found 3 empty textfiles named "term41.default" deleted them and connected to the phone again and it made no diff it still search for term41.default.
> How do you know that it is trying to download the file from itself? If you set DHCP correctly, than it should download from the ip address option 150 points to.
Well there is 3 small boxes on the phonescreen and in them I have a) the phones IP b) says "downloading" c) all it says is "term41.default 0k".
So by that I guess that its trying to connect to the IP on A and downloading the file in C but can't find it and then terminates and reboots.
> So do you have that firmware term41.default on your tftp server?
I searched the computer im running the tftp server from and I found 3 empty textfiles named "term41.default" deleted them and connected to the phone again and it made no diff it still search for term41.default.
> How do you know that it is trying to download the file from itself? If you set DHCP correctly, than it should download from the ip address option 150 points to.
Well there is 3 small boxes on the phonescreen and in them I have a) the phones IP b) says "downloading" c) all it says is "term41.default 0k".
So by that I guess that its trying to connect to the IP on A and downloading the file in C but can't find it and then terminates and reboots.
ASKER
> How do you know that it is trying to download the file from itself? If you set DHCP correctly, than it should download from the ip address option 150 points to.
How do I check what option 150 is pointing to?
This is my dhcpd.conf log
#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style interim;
ignore client-updates;
#Define Custom Option
option option-150 code 150 = ip-address;
#Global Config
option ip-forwarding off;
option nis-domain "domain.local";
option domain-name "domain.local";
default-lease-time 21600;
max-lease-time 43200;
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1;
#Default Gateway
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option domain-name-servers 192.168.0.10;
option nntp-server 192.168.0.10;
option time-offset -18000;
#Eastern Standard Time
option option-150 192.168.200.10;
#TFTP Custom Option
next-server 192.168.200.10;
#TFTP Boot
range dynamic-bootp 192.168.0.200 192.168.0.249;
}
# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
#subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
#subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}
# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.fugue.com";
#}
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.fugue.com;
#}
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.
#class "foo" {
# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}
#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
#}
How do I check what option 150 is pointing to?
This is my dhcpd.conf log
#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
# $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
#
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style interim;
ignore client-updates;
#Define Custom Option
option option-150 code 150 = ip-address;
#Global Config
option ip-forwarding off;
option nis-domain "domain.local";
option domain-name "domain.local";
default-lease-time 21600;
max-lease-time 43200;
subnet 192.168.0.0 netmask 255.255.255.0 {
option routers 192.168.0.1;
#Default Gateway
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.0.255;
option domain-name-servers 192.168.0.10;
option nntp-server 192.168.0.10;
option time-offset -18000;
#Eastern Standard Time
option option-150 192.168.200.10;
#TFTP Custom Option
next-server 192.168.200.10;
#TFTP Boot
range dynamic-bootp 192.168.0.200 192.168.0.249;
}
# option definitions common to all supported networks...
option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
#subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
#subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}
# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.fugue.com";
#}
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.fugue.com;
#}
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.
#class "foo" {
# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}
#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
#}
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Help me in the right way but not yet there.
http://www.voip-info.org/wiki/view/Standalone+Cisco+7941%252F7961+without+a+local+PBX