CUCM 8.6.2 Subscriber is down!!!!

Hi,
Can anyone please help me in this I have got 2 clusters of CUCM 8.6.2 one is Pub and another one is Sub. In the cluster there are 4 nodes
1. CUCM - Pub
2. CUPC
3. UCCX
4. UCXN
1. CUCM - Sub
2. CUPC
3. UCCX
4. UCXN
This complete structure is in VMware. Today my Sub went down completely and all the phones are now registered to PUB. When I went to see in VSphare client to see what is going on I saw that in the CUCM node --> console it is rebooting automatically and is then giving error and asking to insert Recovery disk. When I tried to ping other nodes in the cluster they were completely fine no problems in it. Please see the attached error file. I will really thankful if any one able to help me out in this.
Thank You,
Kind Regards
Rohit Mangotra.

Hi Rohit,
Download the recovery iso from this location and boot up the subscriber from this iso.
http://software.cisco.com/download/release.html?mdfid=283782839&flowid=26422&softwareid=282074294&release=8.6%282a%29&relind=AVAILABLE&rellifecycle=&reltype=latest
Once there it will give you the option to run an automatic or manual file system check. Try the automatic one first and if it does not work then try manual file system check. Thes kind of issues can occur because of improper shutdowns and may lead to reinstallation of sub in case the recovery disk does not fix the issue.
HTH
Manish

Similar Messages

Cucm 7.1.3 cisco DB down on Publisher

Dear Experts,
Database communication error while login into Publisher admin.and from subscriber i can see in unified reporting CM Cluster overview active services status A cisco DB down on Publisher cucm version 7.1.3 1 publisher and 1 subscriber on MCS 7816I4 below are the cli dbrelication status
I have resarted the publisher from OS Admin but no luck.any other workaround highly appreciated.
admin:utils dbreplication status
-------------------- utils dbreplication status --------------------
Traceback (most recent call last):
File "/usr/local/cm/bin/DbReplStatus.py", line 98, in ?
fout = open(tmpOutputFile, 'w');
IOError: [Errno 30] Read-only file system: '/tmp/ReplicationStatus.2012_12_26_08_44_59.out'
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 Audit Event 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[STARTED]
Cisco CDR Repository Manager[STARTED]
Cisco CTIManager[STARTED]
Cisco CTL Provider[STARTED]
Cisco CallManager[STARTED]
Cisco CallManager Admin[STARTED]
Cisco CallManager Attendant Console Server[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 Extended Functions[STARTED]
Cisco Extension Mobility[STARTED]
Cisco Extension Mobility Application[STARTED]
Cisco IP Manager Assistant[STARTED]
Cisco IP Voice Media Streaming App[STARTED]
Cisco License Manager[STARTED]
Cisco Log Partition Monitoring Tool[STARTED]
Cisco Messaging Interface[STOPPED] Component is not running
Cisco RIS Data Collector[STARTED]
Cisco RTMT Reporter Servlet[STARTED]
Cisco SOAP - CDRonDemand Service[STARTED]
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]
Cisco UXL Web Service[STARTED]
Cisco Unified Mobile Voice Access Service[STARTED]
Cisco WebDialer Web Service[STARTED]
Host Resources Agent[STARTED]
MIB2 Agent[STARTED]
Native Agent Adapter[STARTED]
SNMP Master Agent[STARTED]
SOAP -Log Collection APIs[STARTED]
SOAP -Performance Monitoring APIs[STARTED]
SOAP -Real-Time Service APIs[STARTED]
System Application Agent[STARTED]
Primary Node =true

Hi John,
Were there any changes made recently?
Can you send the outputs for the following:
From the Pub:
show status
utils diagnose test
utils ntp status
show network eth0 detail
show tech network hosts
utils network ping
utils network host
utils network host
From the Sub:
show status
utils diagnose test
utils ntp status
show network eth0 detail
show tech network hosts
utils network ping
utils network host
utils network host
utils network connectivity
Regards,
Harmit.

Do phones automatically failover when a Subscriber is down?

We are running CUCM 8.6 with one publisher and two subscribers. One of the subscribers has failed and we are now running off only one subscriber. In this mode, we are experiencing a number of minor problems with the phones including:
Time on handsets using incorrect format. (shows as 24hour when it should be 12 hour)
Phones keep ringing after the extension has beenanswered.
One-Way voice.
Calls dropping out when put on hold
Unable to pickup call when it's put on hold.
Are the phones meant to automatically failover to the other subscriber when one fails? Or do we need to manually reboot the handsets for this to take place?
Also, is all functionality meant to be available when running in the degraded mode?

Hi Robert,
The phones should automatically failover to the backup subscriber if the backup subscriber is added in the Callmanager group which is assigned to the device pool of the IP phone. For issues like one way audio and dropped calls you also need to check that the media resources like Transcoder , CFB , MTP etc have backup servers defined, else you will experience issues where these resources are requested but they are unregistered as the only subscriber which is defined for them is down.
HTH
Manish

CUCM & CUP 9.1 subscriber cluster

Dear
I am trying to install CUP subscriber which is in different sub cluster than the publisher , I am not able to add the subscriber I get the error attached I have enabled access-list as a IP between the servers, but still it is prompting me with the same error,
Also I am getting the error on CUCM subscriber as per the attached.
I have done according to the link below but no success.
http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-version-60/109486-cm-configuration-validation-error-00.html
thanks

Hi Samuel,
Please verify that the subscriber entry is present under CUP Publisher topology and CUCM Application servers list.
HTH
Manish

Unable to view 7841 Ip Phones on CUCM Subscriber

We have a new CUCM BE 6000 ver 9.1.2 implementation, with a CUCM Publisher and a Subscriber servers
As we have Cisco 7841 Ip Phones, we installed on both servers the recommneded device pack (cmterm-devicepack9.1.2.11013-1.cop.sgn) as specified on link: "http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/devpack_comp_mtx.html"
After we restarted CUCM cluster, we can add, view, modify 7841 Ip Phones on Publisher server ONLY , these Cisco 7841 are registered on CUCM Subscriber ,and they areworking good .
But when we try to view/modify these Cisco Ip Phones 7841 on Subscriber server we got this error:
"Unmapped Exception /usr/local/cm/db/xml/xml/Phone_7841_SIP_display_instance.xml (No such file or directory)"
And we are unable to access them on Subscriber server.
We also run "utils dbreplication status" on both servers and got :
"No Errors or Mismatches found.
Replication status is good on all available servers"
....when I viewed generated file.
We also run "Unified CM Database status" report and got Replicate state= "2 Good " ob Subscriber server.
But the situation is the same, Could any of you have an idea about this kind of problem??
Thanks a lot in advanced.
Enrique

Hi ev1205,
Re-install the cop file on the subscriber and restart the subscriber server. This should fix the problem.
Errors like this indicate that the cop.sgn file was not installed correctly on the server.
The fact that the phone is registered on the subscriber indicates that the model type is present in the tables, but maybe other details specific to this model were not installed correctly.
Thanks
Sreekanth

CUCM Group Configuration- question about phones failing to secondary callmanager

I wanted to get clarification about how exactly phones will register to the secondary or tertiary servers if the link to the primary fails.
I have a 3 server CUCM cluster. 1 subscriber that some phones register to is separated from the other 2.
When the link to that sub goes down, the phone should then register to the secondary server of its Cisco Unified CallManager Group configuration, correct?
If this is true, then my next question is how long does it take to then failover to the secondary server?
SRST is not involved in this, it's just the CUCM Group Config. Any help clarifying how phones behave in this situation?

I found my own answer in the Cisco Press Troubleshooting Cisco IP Telephony book, page 155:
"The TFTP configuration file received by the IP phone has a list of up to three CallManagers
for registration purposes. The order of CallManagers indicates their priority. The first is the
highest-priority CallManager for the IP phone. It is the first place the IP phone attempts to
register. The highest-priority CallManager is also called the primary CallManager.
When the IP phone registers with its primary CallManager, it also establishes a standby
TCP connection to the next-highest–priority available CallManager, sometimes called the
standby CallManager, secondary CallManager, or backup CallManager.
The IP phone knows that there is an alternative CallManager for quick failover if it loses connectivity
with its primary CallManager.
At any given point in time, the CallManager to which the phone is registered is its active
connection. The CallManager node that has a standby TCP connection for the IP phone is
the standby connection.
Failover occurs under two conditions:
• If the TCP connection between the IP phone and the primary CallManager goes down.
Incidentally, stopping the CallManager service on a server causes all the TCP connections
to be closed and all the IP phones on that server to register to their standby.
• If CallManager has not responded to three consecutive KeepAlive messages sent from
the IP phone.
Any number of network-related issues could cause the TCP connection to go down. When
the IP phone registers with its standby CallManager, it registers with an alarm indicating
why it failed over.
Under the second condition, CallManager fails to respond to three consecutive KeepAlives.
The IP phone sends a KeepAlive message every 30 seconds by default. CallManager should
answer each KeepAlive the IP phone sends with an acknowledgment message. If
CallManager fails to respond to three consecutive KeepAlive messages, the IP phone marks
the connection as “bad.” The IP phone does not tear down the TCP connection, but it does
not attempt to re-register with the “bad” CallManager either. It continues sending
KeepAlive messages to the “bad” CallManager until CallManager tears down the TCP
connection. This delay gives CallManager time to respond if it recovers quickly. After 10
minutes, the IP phone removes the “bad” tag and again tries to establish communication
with CallManager using KeepAlive messages in the process just described. During this
time, the IP phone attempts to establish a connection with its secondary CallManager (or
its tertiary if the secondary is not available) and registers if possible.
If a call is in progress when an IP phone detects the loss of a TCP connection, the IP phone
does not fail over until the call is finished. If CallManager fails to respond to three consecutive
KeepAlive messages while an IP phone has an active call, the IP phone again waits
until the call is finished before registering to its standby CallManager."
Hope that helps someone else in the future.

7942s randomly lose connection to CUCM Thru VPN Tunnel

One of my remote branches has 7 7942s plugged into a 2960 POE and then to a 2901. The computer are connected to the telephone tandum.
1.All the phones dont drop at the same time (maybe 2 or 3 together)
2.The VPN Tunnel never drops when the phones lose the CUCM.(Computers are still online and able to see the network on other side of tunnel)
3.The computer that is connected to the dropped phone does not lose connectivity to the inside network or thru the vpn tunnel (whether in fallback mode or connected or in transit)
4. when a couple of phones are down, I can reach both CUCMs. (Publisher and Subscriber)
Any help would be appreciated.

Hi Earl,
Try to do wire shark and see if you can capture anything.
Its looks like keep live message dropping some where before they reaching phones. Is there high utilization on site?
Check if any firewall filtering packets.
Phone reboots itself and tries to register again. Check interface if there is any watchdog timers error.
Please do rate if the given information helps
Thanks

Subscriber Crashed

Hi, this evening i had this issue at my office publisher and subscriber went down, i still dont know exactly why
We are using call manager 4.0
When i step into the cpd publiser was off and subscriber was on, but i couldnt reach it by ping.
I think that they have rebooted due to a temperature issue, and critical file of subscriber have been corrupted in the process (i know that for sure)
I have a couple of questions about it
1. How do i reinstall de subscriber, i know the configuration, but i allways have done it in a lab enviroment, never on a "real" call manager and i cant get the proccess started, in the boot order is selected Cd as first option but allways boot from the corrupted installation
2. How can i found out what happened? im assuming that i lost all the iformation on subscriber, but im sure that it happened the same to the publisher, there is any kind of system logs in the call manager 4.0 or the windows server that can tell me what happened in order to avoid this kind of problems in the future?
Thanks for your help in advance, this is my first "serious problem" since im into voice ip and in this position so all help will be greatly apreciated
Regards.
Cesar

I am assuming that your Publisher is OK and that your Subscriber won't boot or you're getting some sort of critical error upon system startup...in other words, I'm skipping troubleshooting and going to the root of the question.
1) How do you rebuild the Subscriber? You need to rebuild the Sub from scratch using the CD or DVD for your version of CUCM. I suspect that you may be missing a boot sequence message that says something to the effect of "To boot from CD, press ...." and if you don't, the system will boot as it normally would. So, you need to rebuild the Subscriber to the exact OS patch level and CCM patch level as the Publisher. You should also re-use the hostname and IP settings or you will need to add a "new" Sub in CCM Administration on the Publisher before you add it to the cluster.
2) How do you find out what happened? Well, you have Windows OS logs that are of most value if you believe you had an environmental issue. However, these types of issues are sometimes difficult to run down. If you rebuild the Subscriber, the logs will get wiped out so you'll have to go by what you find on the Publisher. Dont forget to check the Dr. Watson logs as well.
Hailey
Please rate helpful posts!

No ringbacktone for inbound calls with cucm 8.6

Hi,
we have this problem from many days...
we have two branches with cucm cluster(Publisher and Subscriber) at Head office and cisco untiy.The branches are connected to Head office through MPLS vpn and all the ip phones are registred to publisher located at headoffice.
our setup is like below
HO and BR2 having SIP lines and BR1 has PSTN Lines.
we implement greetings for head office and 2 branches at Headoffice Unity.
when any call comes to headoffice gateway the greetings will be played and call will be diverted to the appropriate extension.everything is fine.
But the problem is when the call comes to Branch gateway and the greetings will be played and the call gets diverted to the IP phone to which the caller dialed the extension. but the caller is not hearing the ringback tone while the extension is ringing. and the caller cannot know whether the extension is ringing or the call got disconnected.
i tried to change the " Send h225 User Information Message" in service parameters from "Use ANN for Ring Back" to H225 Info for call Progress Tone"
whenever i am changing to "H225 Info for call Progress Tone" then the branches problem getting solved but Headoffice getting the same problem.
please can anyone help............................

Hi Carlo,
Thankyou for the Response...
here is the Runn config for BR1 Connected to PSTN lines....
voice-card 0
dspfarm
dsp services dspfarm
voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
h323
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g711alaw
codec preference 3 g729r8
codec preference 4 g729br8
voice class h323 1
h225 timeout tcp establish 3
interface Tunnel100
description " Tunnel JED-RYD "
bandwidth 2048
ip address 10.10.0.1 255.255.255.252
tunnel source 172.31.217.202
tunnel destination 172.31.3.18
interface FastEthernet0/0
description DAMMAM Local LAN
no ip address
duplex auto
speed auto
interface FastEthernet0/0.20
description JEDDAH Local LAN
encapsulation dot1Q 20
ip address 192.168.20.5 255.255.255.0
interface FastEthernet0/0.21
description JEDDAH VOICE VLAN
encapsulation dot1Q 21
ip address 192.168.21.5 255.255.255.0
h323-gateway voip interface
h323-gateway voip bind srcaddr 192.168.21.5
interface FastEthernet0/1
ip address 172.31.217.202 255.255.255.252
duplex auto
speed auto
router eigrp 200
network 10.10.0.0 0.0.0.3
network 192.168.20.0
network 192.168.21.0
no auto-summary
router bgp 65412
no synchronization
bgp log-neighbor-changes
neighbor 172.31.217.201 remote-as 65000
no auto-summary
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 192.168.20.1
ip route 192.168.20.50 255.255.255.255 192.168.20.1
ip http server
ip http access-class 23
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
access-list 23 permit 10.10.10.0 0.0.0.7
control-plane
voice-port 0/0/0
supervisory disconnect dualtone mid-call
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
timing hookflash-out 500
timing guard-out 300
timing sup-disconnect 50
connection plar opx 2050
impedance complex2
description STC
caller-id alerting dsp-pre-allocate
voice-port 0/0/1
supervisory disconnect dualtone mid-call
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
timing hookflash-out 500
timing guard-out 300
timing sup-disconnect 50
connection plar opx 2050
impedance complex2
description STC
caller-id alerting dsp-pre-allocate
voice-port 0/0/2
supervisory disconnect dualtone mid-call
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
timing hookflash-out 500
timing guard-out 300
timing sup-disconnect 50
connection plar opx 2050
impedance complex2
description STC
caller-id alerting dsp-pre-allocate
voice-port 0/0/3
supervisory disconnect dualtone mid-call
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
timing hookflash-out 500
timing guard-out 300
timing sup-disconnect 50
connection plar opx 2050
impedance complex2
description STC
caller-id alerting dsp-pre-allocate
voice-port 0/2/0
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
connection plar 2022
shutdown
impedance complex2
description STC
voice-port 0/2/1
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
shutdown
impedance complex2
description STC
voice-port 0/3/0
supervisory disconnect dualtone mid-call
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
timing hookflash-out 500
timing guard-out 300
timing sup-disconnect 50
connection plar opx 2050
impedance complex2
description STC
caller-id alerting dsp-pre-allocate
voice-port 0/3/1
supervisory disconnect dualtone mid-call
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
timing hookflash-out 500
timing guard-out 300
timing sup-disconnect 50
connection plar opx 2050
impedance complex2
description STC
caller-id alerting dsp-pre-allocate
voice-port 0/3/2
supervisory disconnect dualtone mid-call
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
timing hookflash-out 500
timing guard-out 300
timing sup-disconnect 50
connection plar opx 2050
impedance complex2
description STC
caller-id alerting dsp-pre-allocate
voice-port 0/3/3
supervisory disconnect dualtone mid-call
no battery-reversal
input gain -3
output attenuation -3
echo-cancel coverage 32
cptone BE
timeouts initial 5
timeouts interdigit 3
timeouts call-disconnect 3
timeouts ringing 5
timeouts wait-release 1
timing hookflash-out 500
timing guard-out 300
timing sup-disconnect 50
connection plar opx 2050
impedance complex2
description STC
caller-id alerting dsp-pre-allocate
sccp local FastEthernet0/0.21
sccp ccm 192.168.12.190 identifier 1 priority 1 version 5.0.1
sccp ccm 192.168.12.189 identifier 2 priority 2 version 5.0.1
sccp
sccp ccm group 1
associate ccm 1 priority 1
associate ccm 2 priority 2
associate profile 1 register CONFJEDRAW
associate profile 2 register TRNJED
associate profile 3 register MTPJED
switchover method immediate
switchback method immediate
switchback interval 15
dspfarm profile 2 transcode
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
maximum sessions 2
associate application SCCP
dspfarm profile 1 conference
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
shutdown
dspfarm profile 3 mtp
codec g729r8
maximum sessions software 250
associate application SCCP
shutdown
dial-peer voice 1 pots
dial-peer voice 1000 voip
description To CallManager - SBWPMPUB
destination-pattern [1-5]...
progress_ind progress enable 8
voice-class codec 1
voice-class h323 1
session target ipv4:192.168.12.190
dtmf-relay h245-alphanumeric
no vad
dial-peer voice 9001 pots
description ** 02-6140294(outgoing) **
destination-pattern [^2].T
port 0/0/1
dial-peer voice 9002 pots
description ** 02-6140295(outgoing) **
destination-pattern [^2].T
port 0/0/2
dial-peer voice 9003 pots
description ** 02-6140296(outgoing) **
destination-pattern [^2].T
port 0/0/3
dial-peer voice 9004 pots
description ** 02-6140293(outgoing) **
destination-pattern [^2].T
port 0/0/0
dial-peer voice 290 pots
incoming called-number .
direct-inward-dial
dial-peer voice 9006 pots
description ** 02-6529323(local) **
destination-pattern [^0].T
port 0/3/0
dial-peer voice 9010 pots
description ** 02-6578249(local) **
destination-pattern [^0].T
port 0/3/1
dial-peer voice 9011 pots
description "to pstn service"
shutdown
destination-pattern 0.T
port 0/3/3
dial-peer voice 9009 pots
description "to pstn service"
shutdown
destination-pattern [^0].T
port 0/3/2
dial-peer voice 9005 pots
destination-pattern .T
dial-peer voice 1001 voip
description To CallManager - Subscriber
destination-pattern [1-5]...
progress_ind progress enable 8
voice-class codec 1
voice-class h323 1
session target ipv4:192.168.12.189
dtmf-relay h245-alphanumeric
no vad
dial-peer voice 1002 voip
description " TO Unity Greetings"
destination-pattern 2050
progress_ind progress enable 8
voice-class codec 1
voice-class h323 1
session target ipv4:192.168.12.190
dtmf-relay h245-alphanumeric
no vad
dial-peer voice 1003 voip
description " TO Unity Greetings"
destination-pattern 2050
progress_ind progress enable 8
voice-class codec 1
voice-class h323 1
session target ipv4:192.168.12.189
dtmf-relay h245-alphanumeric
no vad

9971 registred/unregtistred with KEM - CUCM 8.6.2

Hello,
I have little problem with 9971+KEM. 9971 with no attached KEM works fine - 3 Line's + 3 BLF. If I connect KEM to phone (configure Phone button template, add KEM in CUCM to phone, set Subscribe CSS) phone also works fine. If I only add 1 or 2 BLF to KEM, phone starts re-registering to: secondary CUCM, then to SRST Gateway, then to Primmary CUCM, then to ... etc. and all BLF's on phone and KEM change to SD buttons icon. Firmware is 9.3.4.24. CUCM version is 8.6.2. I use power cube 4 (48Watts).
Thanks for any help.
Phone + KEM and configured only with Speed Dial buttons also works fine.
Wiadomość była edytowana przez: Marcin Szydelko

Surprisingly, it has made it all the way to 10.5(x) with the same info and the same error...
I did found a method to change it via root access, and you might not require root access, but I can't tell for sure as I would need to look at exactly what the contents of the file that TAC changes, but apparently it's just the platformConfig.xml that they need to change and reboot.
If that's the case, using the utils import config using pretty much all the same info, except the country, would end up with the same outcome.
Again, not 100% sure but theory says that should do the trick, you can run that thru TAC if you open the case and see what they think about it.

Schedule time to shut down cisco IP phones

Dear All,
i would like to ask if there is any way to schedule time on CUCM 7 allowing us to shut down cisco ip phones during week ends, and which cisco ip phone models that support this feature.
regards

Hassan,
I'm no phone guy but if you want to POWER OFF the phones outside office hours there are serious implications to consider.
If your phones have PCs connected to them, there's a large chance that when the phones go off, the PCs will not be able to reach the network (because VoIP phones do not have bypass functionality).
Another thing is in an emergency, no one can make outgoing/incoming calls.
If this is what you want then you could try EnergyWise if you don't have acess to your CUCM services. Let's say you want to power off your phones at midnight and power up by 5am the next morning (weekdays):
!Globalenergywise domain security shared-secret energywise importance 60! Time Rangetime-range ONabsolute start 05:00 01 March 2013periodic weekday 5:00 to 23:59time-range OFFabsolute start 00:00 01 March 2013periodic weekday 0:0 to 5:00! Interfaceinterface GigabitEthernet0/1energywise level 10 recurrence importance 70 time-range ONenergywise level 0 recurrence importance 70 time-range OFFenergywise importance 60

CUCME and CUCM Licensing

I would like to know how to register the licenses ordered for IP Phones to be registered and uploaded
in to CUCME and CUCM.
I searched a lot of documents but cant find out a proper answer. Could someone help me out on this issue, as I am having 2 projects, 1 with CUCME and 1 with CUCM. The customer have ordered for Licenses, but i dont know how to register it.
Please help

No, the whole process really is what I've written above. The license file is purchasesd from Cisco, but once you have that file there is no further involvement with Cisco, it's all done on the CUCM.
You license the CUCM to accept a certain number of devices, and then as you add phones to the CUCM the license totals will go down.
The licenses are in units. So say you apply a license file that contains 1000 units. If you look in the License Calculator, it will tell you how many units each type of phone would use up.
Every time you add a phone (or sometimes a feature such as Mobility) it will use up a certain number of units as shown in the Calculator, and if you ever remove that phone later (say because it needs replaced because of a fault or for a newer model), the units are returned. So for example, a Cisco 7945 IP phone takes up 4 units each, whereas a 7975 uses up 5 units each.
Once you run out of units it won't let you add any more phones until you either remove some devices to get the units back, or you apply more units.

Cisco CUCM 6.0 service can not start

Hi,
Last week our CUCM 6.0 server service was down, the IP phone can not register and can not used browser to access CUCM server, use ssh client to access was ok. We have tried to restart system several times, but the system still not work.
I execute "utils service list" command, it show :
admin:utils service list
Requesting service status, please wait...
System SSH [STARTED]
Cluster Manager [STOPPED] Service Not Started
Service Manager [Not Running]
Warning: Service Manager need to be running for all Call Processing Applications
Service Manager [Not Running]
Warning: Service Manager need to be running for all Call Processing Applications
Please help to advise how to recovery this system?
Best Regards,

Did you get any error message ( asking for recovery disk ) during server reboot ?
If yes, then you need to download the Recovery software for your CUCM version from CCO ( or look for the Recovery disk in your media set received with CUCM ), here it is
http://www.cisco.com/cisco/software/type.html?mdfid=282421166&catid=278875240&i=rp
Also refer the document http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a0080b1f305.shtml
Recovery disk should fix any issues caused due to any file corruption etc & start all the important services.
Pls rate the post if it helps.
GP.

Cisco CUCM 6.1.5 CodeYellowExit alarm(s) received

Hi,
I am running Cisco CUCM ver.6.1.5 & two CUCMs acting as Publisher & Subscriber, Total Phones registered on CUCM is 94.
The Problem that I am facing i used to receive the below Alarm & I noticed the CPU is hitting 85% on both CUCMs so I found the Process called CCM is utilizing 80% of CPU usage.
From Tue Feb 23 23:38:05 AST 2010 to Tue Feb 23 23:59:05 AST 2010 on node 172.30.145.4, there are 1 CodeYellowEntry alarm(s) and 1 CodeYellowExit alarm(s) received. On Tue Feb 23 23:58:35 AST 2010, the last CodeYellowEntry alarm generated: CodeYellowEntry AverageDelay : 31 EntryLatency : 20 ExitLatency : 8 SampleSize : 10 TotalCodeYellowEntry : 26 HighPriorityQueueDepth : 0 NodeID : CUCM-A
Note:
I had disabled all Traces for all CUCM types but still the problem exist.
I had enough MEM & CPU.
Please Advice !!!
Best Regards,
Mohanad

Did you recreate your whole cluster, just as it is in production, on UCS???
I did the procedure from 6.1(5) and 7.1(5) and had no problems.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

AQ Subscriber not reciving notification after database restart

Hi All,
I am currently working on moving some code from two synchronous processes to be asynchronous (not part of critical code path), to do this I have been using one Advanced Queue with two PLSQL registered subscribers.
when we first moved the code into test it was working fine and the data would be processed from the queue quite quickly.
however we then had to restart the database for another reason and after that I noticed that queue was slowly building up with nothing moving from the "READY" state.
having a look at aq$<queue_table>s the two subscribers are still shown and it appears like the user id still has the correct grants and priviledges. I have also checked to make sure that the aqtm_processes is still > 0 and that the QMNC and EMN0 backgroud processes are in v$bgprocess.
Can anybody else suggest what i might have missed? I do not want to have to drop and recreate the queue and subscribers whenever the database needs to come down.
Also I know if the subscriber was down and then bought back up it would not process the backlog but is there anyway of getting it to do this?
almost forgot to mention we are running:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit
Cheers,
Chris

Hi,
I had not set the paramater the DBA had set it and i think their reasoning was:
[http://download.oracle.com/docs/cd/B19306_01/server.102/b14257/componet.htm#sthref339]
"Oracle strongly recommends that you do NOT set AQ_TM_PROCESSES = 0"
although reading a few lines up from there:
"Oracle recommends, however, that you leave the AQ_TM_PROCESSES parameter unspecified and let the system autotune"
As there is another planned outage this weekend i will try resetting the paramater to see if the queues are still dequeueing correctly:
alter system reset AQ_TM_PROCESSES scope=spfile sid='*'
If they are not dequeueing I will try stopping and starting them however I would prefer not to have to do this as then whenever a new queue is introduced with subscribers we would need to add to the scripts run after db startup.
I did find out that removing the subscriber and then recreating it will cause the subscribers to work again but i would prefer to not have to do this after every db restart.
Thanks for pointing me to the AQ_TM_PROCESSES and i will see if that helps :)

CUCM 8.6.2 Subscriber is down!!!!

Similar Messages

Maybe you are looking for