Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Changing Subscriber IP

Status
Not open for further replies.

reddragonuk

Technical User
May 14, 2009
8
GB
Hi

I have recently changed the IP of the subscriber (CUCM 6). Now phones are unable to register to this. On the phone the new subscriber IP is visible, and I have made sure that on the publisher the IP of the subscriber has been updated in the server section and CM servers section. I am able to ping and get access to the web interface of the subscriber.

Does any one have any ideas on why the phones are unable to register? They worked fine before the IP change.

thanks
 
Thanks for your reply, yes i am able to ping the phone from the subscriber.
 
Is anything else registered to the Sub, VM ports, Gateways, etc? Have you tried restarting the CM service/server?
 
VM ports were, however this has been corrected now, phone is still not registering.

I have just noticed under "Control Center - Feature Services" that call manager was activated, but stopped, i started the service, it ran for a few minutes and has not stopped again. This is only happening on the subscriber. Would this cause my problem?

Thanks
 
you have to change the Ip address on the ccm admin page first and then on the command line on the subcriber server, in that order. If you changed the ip address on the server first and then on the admin page, you will have serious issues and will probably have to rebuild the server per cisco tac. It happened to my publisher...go to the command line and utils service list, see if call manager and A Cisco DB are running. see example below. If not try to restart them on the command line.

admin:utils service list
Requesting service status, please wait...
System SSH [STARTED]
Cluster Manager [STARTED]
Service Manager is running
Getting list of all services
>> Return code = 0
A Cisco DB[STOPPED] Component is not running
A Cisco DB Replicator[STARTED]
Cisco AMC Service[STARTED]
Cisco AXL Web Service[STARTED]
Cisco Bulk Provisioning Service[STARTED]
Cisco CAR Scheduler[STARTED]
Cisco CAR Web Service[STARTED]
Cisco CDP[STARTED]
Cisco CDP Agent[STARTED]
Cisco CDR Agent[STOPPED] Component is not running
Cisco CDR Repository Manager[STOPPED] Component is not running
Cisco CTIManager[STARTED]
Cisco CTL Provider[STARTED]
Cisco CallManager[STOPPED] Component is not running
Cisco CallManager Admin[STARTED]
Cisco CallManager Cisco IP Phone Services[STARTED]
Cisco CallManager Personal Directory[STARTED]
Cisco CallManager SNMP Service[STARTED]
Cisco CallManager Serviceability[STARTED]
Cisco CallManager Serviceability RTMT[STARTED]
Cisco Certificate Authority Proxy Function[STARTED]
Cisco Certificate Expiry Monitor[STARTED]
Cisco DHCP Monitor Service[STARTED]
Cisco DRF Local[STARTED]
Cisco DRF Master[STARTED]
Cisco Database Layer Monitor[STARTED]
Cisco Dialed Number Analyzer[STARTED]
Cisco DirSync[STARTED]
Cisco Electronic Notification[STARTED]
Cisco Extended Functions[STARTED]
Cisco Extension Mobility[STARTED]
Cisco Extension Mobility Application[STARTED]
Cisco IP Voice Media Streaming App[STARTED]
Cisco License Manager[STARTED]
Cisco Log Partition Monitoring Tool[STARTED]
Cisco RIS Data Collector[STARTED]
Cisco RTMT Reporter Servlet[STARTED]
Cisco SOAP - CDRonDemand Service[STOPPED] Component is not running
Cisco Serviceability Reporter[STARTED]
Cisco Syslog Agent[STARTED]
Cisco TAPS Service[STARTED]
Cisco Tftp[STARTED]
Cisco Tomcat[STARTED]
Cisco Tomcat Stats Servlet[STARTED]
Cisco Trace Collection Service[STARTED]
Cisco Trace Collection Servlet[STARTED]
Host Resources Agent[STARTED]
MIB2 Agent[STARTED]
Native Agent Adapter[STARTED]
SNMP Master Agent[STARTED]
SOAP -Log Collection APIs[STOPPED] Component is not running
SOAP -Performance Monitoring APIs[STOPPED] Component is not running
SOAP -Real-Time Service APIs[STARTED]
System Application Agent[STARTED]
Cisco CallManager Attendant Console Server[STOPPED] Service Not Activated
Cisco IP Manager Assistant[STOPPED] Service Not Activated
Cisco Messaging Interface[STOPPED] Service Not Activated
Cisco Unified Mobile Voice Access Service[STOPPED] Service Not Activated
Cisco WebDialer Web Service[STOPPED] Service Not Activated
Primary Node =true
 
Thanks for your help guys. Thought i would report back on the situation.

I believe i did it in the wrong order.

The call manager service has stopped, and on trying to start the service it would run for several minutes and fail.

Possible Fix for future readers = Apparently if you put the IP back to the original on the CLI, then make the changes to the server configuration through the web interface, wait a while and then change the IP on the CLI, you can fix the problem.

By the time i found this into out i had seriously fouled the configuration so have decide to rebuild the system.

Thanks to all those who replied.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top