• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 540
  • Last Modified:

Remove Callmanager

Ok this is driving me nuts.  I had previously converted a Cisco 7940 to a SIP by changing the TFTP IP and having it load up newer versions of the firmware 7.4.

I recently had to reset the phone and it reverted back to a cisco with callmanager 7.2 firmware on it.

Having a problem now trying to manually set IP info, where when I give the phone a restart it will try to connect to a setting int here called CallManager1 with some off  what looks like a local IP.  I cant seem to edit this IP or get the phone to connect to the TFTP server I set it up as.  

Any help would be appreciated.
0
Matt Grofsky
Asked:
Matt Grofsky
  • 3
  • 2
1 Solution
 
Matt GrofskyAuthor Commented:
Let me re state my question slightly differently

I'm having an odd problem where I reset 7940 from a SIP phone to factory default and am trying to set it up to TFTP to download latest firmware and config files.

Problem I'm having is I cant change that callmanager IP and everytime the phone boots it shows opening 10.1.7.34 (have no idea what IP is) and then it goes into  Configuring CM List...I dont want call manager on there I want it just as a SIP phone any idea how I can remove this?
0
 
sallwineCommented:
What is the firmware version showing, did it revert back to a SCCP load?
0
 
Matt GrofskyAuthor Commented:

sorry Sallwine I never got an email saying this thread was updated...yes it reverted back.  If I can get in to change the TFTP server I have the latest firmware on there ready to update the phone.  Just for the life of me cant figure out how to get it to connect there, it wont let me change it.
0
 
sallwineCommented:
It sounds like you do not have a CallManager. If I am wrong and you do then you can put the new firmware in the TFTP folder and then put the file name in the Load field on the phone. If you do not, then you should be able to change the TFTP server manually on the phone. If the settings are locked then you can use **# to unlock them (when you are on the settings page). Alternatively you can also try adding an option 150 to your DHCP server, and point it to the new TFTP server.
0
 
Matt GrofskyAuthor Commented:
the 150 seemed to work thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now