CUCM 8.6 DB commnication error

Dear al
 i have PUB & SUB  CUCM 8.6 version on UCS plateform due to power failure in data center both the servers got illegally shutdown after restoring the power we restarted both the server after checking the service list  " A Cisco DB[STOPPED]  Component is not running" & while logging through GUI it is prompting DB communication error in PUB but on SUB all the services are in starting state. please advice how to rectify the same.

Hi
Try to restart your A cisco DB service via following CLI :
utils service start A Cisco DB
If it is still not starting, most likely, file system/DB has been corrupted due to improper power down of the server. You can try to Use recovery CD and check if that helps, else the last option would be to rebuild and do a DRS restore, from backup before the power down or using "Restore from Sub" option.
Regards
Aditya

Similar Messages

  • CUCM 9.X version RTMT Error - LSIESG_AlertIndication 500605B005F63930 Consistency Check inconsistency logging disabled on VD 00/0

    Hi ,
    I am getting the below error on RTMT on CUCM 9.1 Version running on MCS 7835-I3-K9-CMD2 Error 
    At Sat May 24 03:12:40 IST 2014 on node , the following HardwareFailure events generated: 
    hwStringMatch : May 24 03:12:23 ASHISH-CM01 daemon 4 Director Agent:
    LSIESG_AlertIndication 500605B005F63930 Consistency Check inconsistency logging disabled on VD 00/0 (too many inconsistencies) Sev: 3.
    AppID : Cisco Syslog Agent
    ClusterID : 
    NodeID : ASHISH-CM01
     TimeStamp : Sat May 24 03:12:23 IST 2014 
    hwStringMatch : May 24 03:12:23 ASHISH-CM01 daemon 4 Director Agent:
    LSIESG_StorageVolume_Modified 500605B005F63930 Consistency Check inconsistency logging disabled on VD 00/0 (too many inconsistencies) Sev: 3.
    AppID : Cisco Syslog Agent
    ClusterID : 
    NodeID : ASHISH-CM01
     TimeStamp : Sat May 24 03:12:24 IST 2014
    Does anybody has any idea on the same.
    Your inputs would be appreciated ..
    Regards,
    Ashish Bagla

    Hello,
    Did you find the origins of the alerts? I have the same on 2 defferent servers about at the same time of the night a Saturday night too.
    Looks like bug CSCts69041
    Thansk,
    Hervé Jacquemin

  • MCS 7825 & CUCM 5.1 File system error

    I have 2 7825's running CUCM 5.1. Every time we have a power outage/spike or unclean shutdown, the systems do not come back up cleanly. Unrecoverable filesystem errors are most common. While I can do a reload and restore this is not the preferred way to operate. Is anyone familiar with similar issues with the 7825's? An UPS will solve my power issue but it will not solve unclean shutdowns.

    i'd say to backup those servers and then use the disaster recovery CD
    Using the Disaster Recovery Disc
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/upgrade/6_1_2/upgrd612.html#wp51549
    HTH
    java
    if this helps, please rate

  • CUCM 9.1.1 Critical Error on Install

    Hi All,
    I'm trying to install CUCM 9.1.1 on UCS Blade (UCS B200 M2, PID: N20-B6625-1).
    I keep getting Critical Error as soon as the install startes the Database installation. It is a new install and i'm using OVA template from Cisco website
    Your help will be much appreciated.
    Thanks
    Mohammed

    Hi Mohammed,
    that's a common problem of CUCM 9.1.1.20000-5 setup on Vmware: it doesn't seem to be related to some hardware incompatibility (I tried the installation on three different infrastructures, with the same error), but just a problem of this release.
    The only solution I found was to install 9.1.1.10000-11 (or a previous version) and then apply the 9.1.1.20000 patch during the setup: probably you will still get a critical error, but the installation process seems to complete correctly...at least in my case.
    I'm still waiting for an official answer from Cisco TAC.
    Gianmaria

  • Cucm 5.1 manual backup error

    Hi,
    I have problem with callmanager 5.1 back-up, I have been running SFTP server to dump backup. But i am getting error in backu history.
    Pl help
    Regards,
    Nishit

    Here are the steps for the backup
    Step 1 Navigate to the Disaster Recovery System. Log in to Cisco Unified
    CallManager Administration, choose Disaster Recovery System from the
    Navigation menu in the upper, right corner of the Cisco Unified CallManager
    Administration window, and click Go.
    The Disaster Recovery System Logon window displays.
    Step 2 Log in to the Disaster Recovery System by using the same
    Administrator username and password that you use for Platform
    Administration.
    Step 3 Navigate to Backup>Storage Location. The Storage Location window
    displays.
    Step 4 Choose the number of backup files to store on a network directory.
    Step 5 Choose one of the following storage destination options and enter the
    appropriate field values:
    *Tape Device-Stores the backup file on a locally attached tape drive. Choose
    the appropriate tape device from the list.
    *Network Directory-Stores the backup file on a networked drive accessed
    through an SFTP connection. Enter the following required information:
    -Server name: Name or IP address of the network server
    -Path name: Path name for the directory where you want to store the backup
    file
    -User name: Valid username for an account on the remote system
    -Password: Valid password for the account on the remote system
    Step 6 To update these settings, click Save.
    Step 7 Continue with either a manual or a scheduled backup.

  • CUCM 10.5.1 - getting error when adding or updating a phone

    We just upgraded from 8.5 to 10.5.1 last weekend.  Have an issue when trying to add or make changes to a phone that the following error occurs:
    "Add failed.  The Insert privilege is required for this operation"   I do not get this error but the client service desk does.  I mimic my permissions with one of the client services desk and had them try again and still no change.  When they make a change, the change does save.  However adding phones is not allowed resulted in the same error.
    Anyone else run into this?

    Hello,
    Either Publisher is down or DB replication is broken with it. When we change any configuration, the changes will be written on the publisher and it replicates it to the subscriber even if the changes were done on a subscriber webpage.
    Thank you,
    Shadi

  • CUCM 7.X : Code yellow error

    Hello,
    I am having Publishre & subscriber running with version 7.X, but subscriber gives out an error of "Code Yellow" and suddenly logged out IP phones start ringing. Followinng are logs. Need help.
    there are 1 CodeYellowEntry alarm(s) and 0 CodeYellowExit alarm(s) received.
      On {Date & Time}, the last CodeYellowEntry alarm generated:
      CodeYellowEntry
    AverageDelay : 679
    EntryLatency : 20
    ExitLatency : 8
    SampleSize : 10
    TotalCodeYellowEntry : 7
    HighPriorityQueueDepth : 0

    Hi Manish,
    Thank you for the detailed information.
    I have gone through the logs of RTMT and found following errors.
    Dec 23 09:12:49, XXXXX, Notice,  Director Agent, : LSIESG_AlertIndication 500605B001EFB0A0 Battery relearn will start in 5 hours Sev: 2., 20281.
    Dec 23 15:10:21, XXXXX, Notice,  Director Agent, : LSIESG_AlertIndication 500605B001EFB0A0 Battery relearn completed Sev: 2., 20296
    Dec 23 17:37:47, XXXXX, Critical,  Director Agent, : LSIESG_AlertIndication 500605B001EFB0A0 Battery has failed and cannot support data retention. Please replace the battery Sev: 7., 20304
    =========================
    Also Output of "show hardware" displays"Battery Replacement required : Yes"
    Battery Back Up Information:
    ==========================
    BBU status for Adapter: 0
    BatteryType: iBBU
    Voltage: 4024 mV
    Current: 0 mA
    Temperature: 26 C
    BBU Firmware Status:
      Charging Status              : None
      Voltage                      : OK
      Temperature                  : OK
      Learn Cycle Requested        : No
      Learn Cycle Active           : No
      Learn Cycle Status           : OK
      Learn Cycle Timeout          : No
      I2c Errors Detected          : No
      Battery Pack Missing         : No
      Battery Replacement required : Yes
      Remaining Capacity Low       : No
      Periodic Learn Required      : No
    Can you please help here too. Thanks in advance!!!!!!!!!!

  • EXT3-fs error (device sda6): in CONSOLE of CUCM 9.1

                       Hello my friends,
    After several days of having my CUCM working properly, the CUCM show me EXT3-fs error (device sda6): xxxxxx , my TFTP service is down and never go UP again. I restart the server and the problem didnt go away.
    Any idea whats going on????
    Someone know what troubleshooting can i do?
    I appreciate your help....
    CUCM 9.1
    ESXi 5.1
    Attache the ERROR

    Hello Jaime,
    I do have the backup, but i didnt do the recovery, i reinstall all the server again, rigth now its good and all the services are UP. But what if it happens again. =(
    Are you sure nothing happened to the server or wherever you have the vmdks???
    The server does not show any kind of alerts. 
    Im goint to download some infomation from the console of the server just to check everything its fine with the vmdks.
    Have you heard about a BUG in ESXi5.1 when you install CUCM 9.1 ??
    Thanks for you answer

  • CUCM returns internal service error for un-allocated numbers

    Setup...
    ITSP----sip---CUBE1------sip----CUCM
         ------sip----CUBE2-----sip---CUCM
    Calls come in via the ITSP to CUBE via SIP. CUBE then send the call to CUCM via sip signalling. This call is matched to a xlation pattern in CUCM, which then xlates the called number to an internal extension.
    The issue that was brough to my attention recently is that when users dial an unallocated number within the DDI range, the calls go into a loop. So I pulled up the traces and to my horror, CUCM doesnt send un allocated/un assigned number back to CUBE rather cucm sends an internal service error...Hence CUBE continues to another dial-peer which matches the secondary CUCM and then finally tries another dial-peer which is for outbound calls to the ITSP. As a result of this, ITSP sends the call back to our CUBES and the call goes into a loop...An excerpt of the trace is shown below:
    5668923: .Nov 21 10:26:04.120: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
    Received:
    INVITE sip:[email protected]:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.106.38.24:5081;branch=z9hG4bKjk1ufl30dok1h9v7f070.1
    From: <sip:[email protected]:5060;user=phone>;tag=1919469313-1385029564105-
    To:  <sip:[email protected]>
    Call-ID: [email protected]
    CSeq: 1025047397 INVITE
    Contact: <sip:[email protected]:5081;transport=udp>
    Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
    Accept: application/media_control+xml,application/sdp,multipart/mixed
    Supported:
    Max-Forwards: 69
    Content-Type: application/sdp
    Content-Length: 206
    v=0
    o=BroadWorks 21539594 1 IN IP4 10.106.38.132
    s=-
    c=IN IP4 10.106.38.132
    t=0 0
    m=audio 18792 RTP/AVP 18 0 8 101
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    a=ptime:20
    a=fmtp:18 annexb=no
    5668924: .Nov 21 10:26:04.122: //-1/28D1E35FAE8C/CCAPI/cc_api_display_ie_subfields:
       cc_api_call_setup_ind_common:
       cisco-username=08834433593
       ----- ccCallInfo IE subfields -----
       cisco-ani=sip:[email protected]:5060;user=phone
       cisco-anitype=0
       cisco-aniplan=0
       cisco-anipi=0
       cisco-anisi=0
       dest=sip:[email protected]:5060
       cisco-desttype=0
       cisco-destplan=0
       cisco-rdie=FFFFFFFF
       cisco-rdn=
       cisco-rdntype=0
       cisco-rdnplan=0
       cisco-rdnpi=-1
       cisco-rdnsi=-1
       cisco-redirectreason=-1   fwd_final_type =0
       final_redirectNumber =
       hunt_group_timeout =0
    5668925: .Nov 21 10:26:04.122: //-1/28D1E35FAE8C/CCAPI/cc_api_call_setup_ind_common:
       Interface=0x20E01378, Call Info(
       Calling Number=sip:[email protected]:5060;user=phone,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
       Called Number=sip:[email protected]:5060(TON=Unknown, NPI=Unknown),
       Calling Translated=FALSE, Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE,
       Incoming Dial-peer=1, Progress Indication=NULL(0), Calling IE Present=TRUE,
       Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=11209976
    5668926: .Nov 21 10:26:04.122: //-1/28D1E35FAE8C/CCAPI/ccCheckClipClir:
       In: Calling Number=sip:[email protected]:5060;user=phone(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
    5668927: .Nov 21 10:26:04.122: //-1/28D1E35FAE8C/CCAPI/ccCheckClipClir:
       Out: Calling Number=sip:[email protected]:5060;user=phone(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
    5668928: .Nov 21 10:26:04.122: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    5668929: .Nov 21 10:26:04.122: :cc_get_feature_vsa malloc success
    5668930: .Nov 21 10:26:04.122: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    5668931: .Nov 21 10:26:04.122:  cc_get_feature_vsa count is 179
    5668932: .Nov 21 10:26:04.122: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    5668933: .Nov 21 10:26:04.122: :FEATURE_VSA attributes are: feature_name:0,feature_time:743075624,feature_id:8589877
    5668934: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/cc_api_call_setup_ind_common:
       Set Up Event Sent;
       Call Info(Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
       Called Number=(TON=Unknown, NPI=Unknown))
    5668935: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/cc_process_call_setup_ind:
       Event=0x229E6D50
    5668936: .Nov 21 10:26:04.122: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
       Try with the demoted called number 441115248457
    5668937: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/ccCallSetContext:
       Context=0x287E5458
    5668938: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/cc_process_call_setup_ind:
       >>>>CCAPI handed cid 11209976 with tag 1 to app "_ManagedAppProcess_Default"
    5668939: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/ccCallProceeding:
       Progress Indication=NULL(0)
    5668940: .Nov 21 10:26:04.122: //-1/xxxxxxxxxxxx/CCAPI/ccGetMemPoolFromContainer:
       mempool not found from usrContainer(27E94C5C)
    5668941: .Nov 21 10:26:04.122: //-1/xxxxxxxxxxxx/CCAPI/ccCreateMemPoolInContainer:
       Mempool(2948E434) created in usrContainer(27E94C5C)
    5668942: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/ccCallSetupRequest:
       Destination=, Calling IE Present=TRUE, Mode=0,
       Outgoing Dial-peer=20, Params=0x2BCAEA00, Progress Indication=NULL(0)
    5668943: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/ccCheckClipClir:
       In: Calling Number=sip:[email protected]:5060;user=phone(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
    5668944: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/ccCheckClipClir:
       Out: Calling Number=sip:[email protected]:5060;user=phone(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
    5668945: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/ccCallSetupRequest:
       Destination Pattern=44T, Called Number=901115248457, Digit Strip=FALSE
    5668946: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/ccCallSetupRequest:
       Calling Number=sip:[email protected]:5060;user=phone(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
       Called Number=901115248457(TON=Unknown, NPI=Unknown),
       Redirect Number=, Display Info=
       Account Number=08834433593, Final Destination Flag=TRUE,
       Guid=28D1E35F-51CE-11E3-AE8C-8F4D5D7E5E41, Outgoing Dial-peer=20
    5668947: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/cc_api_display_ie_subfields:
       ccCallSetupRequest:
       cisco-username=08834433593
       ----- ccCallInfo IE subfields -----
       cisco-ani=sip:[email protected]:5060;user=phone
       cisco-anitype=0
       cisco-aniplan=0
       cisco-anipi=0
       cisco-anisi=0
       dest=901115248457
       cisco-desttype=0
       cisco-destplan=0
       cisco-rdie=FFFFFFFF
       cisco-rdn=
       cisco-rdntype=0
       cisco-rdnplan=0
       cisco-rdnpi=-1
       cisco-rdnsi=-1
       cisco-redirectreason=-1   fwd_final_type =0
       final_redirectNumber =
       hunt_group_timeout =0
    5668948: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/ccIFCallSetupRequestPrivate:
       Interface=0x20E01378, Interface Type=3, Destination=, Mode=0x0,
       Call Params(Calling Number=sip:[email protected]:5060;user=phone,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
       Called Number=901115248457(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
       Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=20, Call Count On=FALSE,
       Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
    5668949: .Nov 21 10:26:04.122: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    5668950: .Nov 21 10:26:04.122: :cc_get_feature_vsa malloc success
    5668951: .Nov 21 10:26:04.122: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    5668952: .Nov 21 10:26:04.122:  cc_get_feature_vsa count is 180
    5668953: .Nov 21 10:26:04.122: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    5668954: .Nov 21 10:26:04.122: :FEATURE_VSA attributes are: feature_name:0,feature_time:743086152,feature_id:8589878
    5668955: .Nov 21 10:26:04.122: //11209977/28D1E35FAE8C/CCAPI/ccIFCallSetupRequestPrivate:
       SPI Call Setup Request Is Success; Interface Type=3, FlowMode=1
    5668956: .Nov 21 10:26:04.122: //11209977/28D1E35FAE8C/CCAPI/ccCallSetContext:
       Context=0x2BCAE9B4
    5668957: .Nov 21 10:26:04.122: //11209976/28D1E35FAE8C/CCAPI/ccSaveDialpeerTag:
       Outgoing Dial-peer=20
    5668958: .Nov 21 10:26:04.122: //11209977/28D1E35FAE8C/CCAPI/cc_api_call_proceeding:
       Interface=0x20E01378, Progress Indication=NULL(0)
    5668959: .Nov 21 10:26:04.124: //11209977/28D1E35FAE8C/SIP/Msg/ccsipDisplayMsg:
    Sent:
    INVITE sip:[email protected]:5060 SIP/2.0
    Via: SIP/2.0/TCP 192.168.40.54:5060;branch=z9hG4bK222733C1466
    Remote-Party-ID: <sip:[email protected]>;party=calling;screen=no;privacy=off
    From: <sip:[email protected]>;tag=35AE4FA-F40
    To: <sip:[email protected]>
    Date: Thu, 21 Nov 2013 10:26:04 GMT
    Call-ID: [email protected]
    Supported: timer,resource-priority,replaces,sdp-anat
    Min-SE:  1800
    Cisco-Guid: 0684843871-1372459491-2928447309-1568562753
    User-Agent: Cisco-SIPGateway/IOS-12.x
    Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
    CSeq: 101 INVITE
    Timestamp: 1385029564
    Contact: <sip:[email protected]:5060;transport=tcp>
    Expires: 180
    Allow-Events: kpml, telephone-event
    Max-Forwards: 68
    Content-Type: application/sdp
    Content-Disposition: session;handling=required
    Content-Length: 355
    v=0
    o=CiscoSystemsSIP-GW-UserAgent 8736 4303 IN IP4 192.168.40.54
    s=SIP Call
    c=IN IP4 192.168.40.54
    t=0 0
    m=audio 21236 RTP/AVP 18 0 8 100 101
    c=IN IP4 192.168.40.54
    a=rtpmap:18 G729/8000
    a=fmtp:18 annexb=no
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:100 X-NSE/8000
    a=fmtp:100 192-194
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    5668960: .Nov 21 10:26:04.124: //11209976/28D1E35FAE8C/SIP/Msg/ccsipDisplayMsg:
    Sent:
    SIP/2.0 100 Trying
    Via: SIP/2.0/UDP 10.106.38.24:5081;branch=z9hG4bKjk1ufl30dok1h9v7f070.1
    From: <sip:[email protected]:5060;user=phone>;tag=1919469313-1385029564105-
    To:  <sip:[email protected]>
    Date: Thu, 21 Nov 2013 10:26:04 GMT
    Call-ID: [email protected]
    CSeq: 1025047397 INVITE
    Allow-Events: kpml, telephone-event
    Server: Cisco-SIPGateway/IOS-12.x
    Content-Length: 0
    5668961: .Nov 21 10:26:04.126: //11209977/28D1E35FAE8C/SIP/Msg/ccsipDisplayMsg:
    Received:
    SIP/2.0 100 Trying
    Via: SIP/2.0/TCP 192.168.40.54:5060;branch=z9hG4bK222733C1466
    From: <sip:[email protected]>;tag=35AE4FA-F40
    To: <sip:[email protected]>
    Date: Thu, 21 Nov 2013 10:26:04 GMT
    Call-ID: [email protected]
    CSeq: 101 INVITE
    Allow-Events: presence
    Content-Length: 0
    5668962: .Nov 21 10:26:04.128: //11209977/28D1E35FAE8C/SIP/Msg/ccsipDisplayMsg:
    Received:
    SIP/2.0 500 Internal Server Error
    Via: SIP/2.0/TCP 192.168.40.54:5060;branch=z9hG4bK222733C1466
    From: <sip:[email protected]>;tag=35AE4FA-F40
    To: <sip:[email protected]>;tag=4622451~ffa80926-5fac-4dd6-b405-2dbbc56ae9a2-475524409
    Date: Thu, 21 Nov 2013 10:26:04 GMT
    Call-ID: [email protected]
    CSeq: 101 INVITE
    Allow-Events: presence
    Content-Length: 0
    5668963: .Nov 21 10:26:04.128: //11209977/28D1E35FAE8C/CCAPI/cc_api_call_disconnected:
       Cause Value=41, Interface=0x20E01378, Call Id=11209977
    5668964: .Nov 21 10:26:04.128: //11209977/28D1E35FAE8C/CCAPI/cc_api_call_disconnected:
       Call Entry(Responsed=TRUE, Cause Value=41, Retry Count=0)
    5668965: .Nov 21 10:26:04.128: //11209976/28D1E35FAE8C/CCAPI/ccCallReleaseResources:
       release reserved xcoding resource.
    5668966: .Nov 21 10:26:04.128: //11209977/28D1E35FAE8C/CCAPI/ccCallSetAAA_Accounting:
       Accounting=1, Call Id=11209977
    5668967: .Nov 21 10:26:04.128: //11209977/28D1E35FAE8C/CCAPI/ccCallDisconnect:
       Cause Value=41, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=41)
    5668968: .Nov 21 10:26:04.128: //11209977/28D1E35FAE8C/CCAPI/ccCallDisconnect:
       Cause Value=41, Call Entry(Responsed=TRUE, Cause Value=41)
    5668969: .Nov 21 10:26:04.128: //11209977/28D1E35FAE8C/CCAPI/cc_api_call_disconnect_done:
       Disposition=0, Interface=0x20E01378, Tag=0x0, Call Id=11209977,
       Call Entry(Disconnect Cause=41, Voice Class Cause Code=0, Retry Count=0)
    5668970: .Nov 21 10:26:04.128: //11209977/28D1E35FAE8C/CCAPI/cc_api_call_disconnect_done:
       Call Disconnect Event Sent
    5668971: .Nov 21 10:26:04.128: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
    5668972: .Nov 21 10:26:04.128: :cc_free_feature_vsa freeing 2C4A9840
    5668973: .Nov 21 10:26:04.128: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:
    5668974: .Nov 21 10:26:04.128:  vsacount in free is 179
    5668975: .Nov 21 10:26:04.128: //11209976/28D1E35FAE8C/CCAPI/ccCallSetupRequest:
       Destination=, Calling IE Present=TRUE, Mode=0,
       Outgoing Dial-peer=21, Params=0x2AA85790, Progress Indication=NULL(0)
    5668976: .Nov 21 10:26:04.128: //11209976/28D1E35FAE8C/CCAPI/ccCheckClipClir:
       In: Calling Number=sip:[email protected]:5060;user=phone(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
    5668977: .Nov 21 10:26:04.128: //11209976/28D1E35FAE8C/CCAPI/ccCheckClipClir:
       Out: Calling Number=sip:[email protected]:5060;user=phone(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
    5668978: .Nov 21 10:26:04.128: //11209976/28D1E35FAE8C/CCAPI/ccCallSetupRequest:
       Destination Pattern=44T, Called Number=901115248457, Digit Strip=FALSE
    5668979: .Nov 21 10:26:04.128: //11209976/28D1E35FAE8C/CCAPI/ccCallSetupRequest:
       Calling Number=sip:[email protected]:5060;user=phone(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
       Called Number=901115248457(TON=Unknown, NPI=Unknown),
       Redirect Number=, Display Info=
       Account Number=08834433593, Final Destination Flag=TRUE,
       Guid=28D1E35F-51CE-11E3-AE8C-8F4D5D7E5E41, Outgoing Dial-peer=21
    5668980: .Nov 21 10:26:04.128: //11209976/28D1E35FAE8C/CCAPI/cc_api_display_ie_subfields:
       ccCallSetupRequest:
       cisco-username=08834433593
       ----- ccCallInfo IE subfields -----
       cisco-ani=sip:[email protected]:5060;user=phone
       cisco-anitype=0
       cisco-aniplan=0
       cisco-anipi=0
       cisco-anisi=0
       dest=901115248457
       cisco-desttype=0
       cisco-destplan=0
       cisco-rdie=FFFFFFFF
       cisco-rdn=
       cisco-rdntype=0
       cisco-rdnplan=0
       cisco-rdnpi=-1
       cisco-rdnsi=-1
       cisco-redirectreason=-1   fwd_final_type =0
       final_redirectNumber =
       hunt_group_timeout =0
    5668981: .Nov 21 10:26:04.128: //11209976/28D1E35FAE8C/CCAPI/ccIFCallSetupRequestPrivate:
       Interface=0x20E01378, Interface Type=3, Destination=, Mode=0x0,
       Call Params(Calling Number=sip:[email protected]:5060;user=phone,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
       Called Number=901115248457(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
       Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=21, Call Count On=FALSE,
       Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
    5668982: .Nov 21 10:26:04.128: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:
    Question is why such a behaviour by CUCM. Is it because the call is sent to a xlation pattern first..Any remedies?
    Please rate all useful posts
    "opportunity is a haughty goddess who waste no time with those who are unprepared"       

    This is for the benefit of anyone who experience a similar issue like this..
    Cisco CUCM and CUBE by default do not drop a call when it receives a 486  busy, 404 not found or out of bandwidth. They reroute for all cause codes other than Out of Bandwidth, User Busy, and Unallocated Number.
    For CUCM, the value of the associated service parameters for the Cisco Call Manager service determines the rerouting decision for those cause codes. The Cluster wide Parameters (Route Plan) : Stop Routing on Out of Bandwidth Flag, Stop Routing on User Busy Flag, and Stop Routing on Unallocated Number Flag service parameters, determines what re-routing decision happens in this scenario.
    All well and good fro CUCM, but what about CUBE...
    We can also tell CUBE what to do in this circumstances just as with CUCM. The magic is to use the voice hunt command
    #conf t
    no voice hunt unassigned-number
    no voice hunt invalid-number
    no voice hunt user-busy

  • CUCM OS Administration Page Not There in CUCM 8.6

    No option for  CUCM OS Administration Page in navigation menu in CUCM 8.6
    Unable to access CUCM OS Administration page.
    following error came while using  url  http://<ip-address>/cmplatform
    HTTP Status 404 - /cmplatform
    type: Status report
    message: /cmplatform
    description: The requested resource (/cmplatform) is not available.

    Try restarting tomcat
    Also please post in the right forum, this one is for video over ip
    Sent from Cisco Technical Support iPad App

  • Problem migrating CUCM 7.1.5 to 9.1(2) (Jump Upgrade)

    Hello all,
    I am facing an issue when trying to upgrade from CUCM 7.1.5.30000-1 to 9.1(2) over UCS following the jump upgrade procedure.
    I have installed 7.1.5 CUCM software on the UCS using the 9.1(2) ova. (two nodes cluster), and after that restored the CUCM backup.
    I have loaded "ciscocm.refresh_upgrade_v1.3.cop" file before the upgrade on both nodes.
    The connectivity with NTP server is good.
    The upgrade file I am using is "UCSInstall_UCOS_9.1.2.11900-12.sgn".
    The installation begins on Publisher but after three hours and when it is ending it fails. I have checked the installation logs and this is what it shows:
    05/23/2014 17:45:51 component_install|(CAPTURE) Fri May 23 17:41:46 2014 cm-dbl-install DEBUG: cm-dbl-install [0]|<LVL::Debug>
    05/23/2014 17:45:51 component_install|(CAPTURE) Fri May 23 17:41:46 2014 cm-dbl-install DEBUG: <--|<LVL::Debug>
    05/23/2014 17:45:51 component_install|File:/opt/cisco/install/bin/component_install:756, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
    05/23/2014 17:45:51 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:269, Function: refresh_upgrade(), failed to refresh_upgrade infrastructure_post components|<LVL::Critical>
    05/23/2014 17:45:51 post_install|File:/opt/cisco/install/bin/post_install:911, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -refresh-upgrade failed (1)|<LVL::Error>
    05/23/2014 17:45:51 post_install|Exiting with result 1|<LVL::Info>
    05/23/2014 17:45:51 post_install|INSTALL_TYPE="Refresh Upgrade"|<LVL::Debug>
    05/23/2014 17:45:51 post_install|Process refresh upgrade failure|<LVL::Info>
    05/23/2014 17:45:51 post_install|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]|<LVL::Debug>
    05/23/2014 17:45:51 post_install|Retore grub.conf from grub.conf.recovery|<LVL::Info>
    05/23/2014 17:45:51 post_install|Copy recovery file, /grub/boot/grub/grub.conf.recovery, to /grub/boot/grub/grub.conf|<LVL::Debug>
    05/23/2014 17:45:51 post_install|Retore of grub.conf complete|<LVL::Info>
    05/23/2014 17:45:51 post_install|Invalidate upgrade partition|<LVL::Info>
    05/23/2014 17:45:51 post_install|Removing master RPM|<LVL::Debug>
    05/23/2014 17:45:52 post_install|Removing /etc/opt/cisco/install.conf|<LVL::Debug>
    05/23/2014 17:45:52 post_install|Invalidate any product configuration file|<LVL::Debug>
    05/23/2014 17:45:52 post_install|Setting product and deployment version attributes in /etc/opt/cisco/install/conf/callmanager_product.conf to 0.0.0.0000-0000|<LVL::Debug>
    05/23/2014 17:45:52 post_install|Cleanup refresh upgrade staging areas|<LVL::Debug>
    05/23/2014 17:46:14 post_install|Parse argument status=upgrade.stage.error|<LVL::Debug>
    05/23/2014 17:46:14 post_install|_set_upgrade_status_attribute: status set to upgrade.stage.error|<LVL::Debug>
    05/23/2014 17:46:14 post_install|File:/opt/cisco/install/bin/post_install:580, Function: handle_refresh_upgrade_failure(), Refresh upgrade failed. Trying to reboot to currently active version.|<LVL::Error>
    05/23/2014 17:47:19 hardware_check.sh|Initializing hardware library on boot|<LVL::Info>
    05/23/2014 17:47:19 ServerApiManager|In main with args -|initialize|- called file |/usr/local/bin/base_scripts/server_api_manager.sh| - and current mode=HSSI_Mode |<LVL::Debug>
    05/23/2014 17:47:19 ServerApiManager||Method: initialize args: |- current mode=HSSI_Mode completed with code [0]|<LVL::Debug>
    05/23/2014 17:47:19 ServerApiManager|In main with args -|initHardwareLibrary|- called file |/usr/local/bin/base_scripts/server_api_manager.sh| - and current mode=HSSI_Mode |<LVL::Debug>
    05/23/2014 17:47:19 ServerApiManager|Sam_reset being called|
    I think it is similar to this other case: https://supportforums.cisco.com/discussion/12181161/cucm-vm-715-912-migration-error#comment-9719721
    Can anyone help me with this? I am stuck on the migration.
    Thanks!!
    Héctor

    Just for the record. I found the solution to my problem. Checking more logs I read this:
    The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.
    "/usr/local/cm/script/cm-dbl-ontape_backup-install RU PostInstall 9.1.2.11900-12 7.1.5.30000-1 /usr/local/cm/ /common/component/database /common/log/install/capture.txt " terminated. Exceeded max time (240)
    The system will now halt.
    So I accessed the Dissaster Recovery Section on CUCM and deleted the tape backup device that was configured there. After deleting it the upgrade went well.

  • Install CUCM 8.6 on VMWARE ESXi 5.0 Failed

    Dear All,
    I want to install CUCM 8.6 on Virtual Machine. I'm using VMWARE ESXi 5.0 version for the VM server.
    The installation CUCM 8.6 failed with error says:
    "the hardware you are using is not supported for this prodcut"
    I already disable LRO on the host ESXi 5.0, but still failed.
    is need to install the VMTOOLs before I install CUCM?
    CUCUM 8.6 support VMWARE Version ESXi 5.0?
    Thanks
    Regards,
    Krisna

    Actually for CUCM 8.5 and before it's RHEL 4, for CUCM 8.6 it's RHEL 5 (32 bit).
    I used the available OVA for my lab and it worked fine:
    1 vCPU
    2304 MB RAM
    80 GB HDD
    Not sure about compatibility with ESXi 5 and the VM machine v8 but above works for ESXi 4.1.
    If it still doesn't work, try using the same settings as you would in a ESXi 4.1 install.
    HTH
    java
    If this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • Accessing performance counters in CUCM version 6 and above

                       I do know that the older versions of CUCM allows access to windows performance counters using perfmon as explained in this doc
    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/4_0_1/ccmsrvs/ssperf.html
    However in the later versions of CUCM which runs on Linux OS, is there any way that these counters are made available apart from the RTMT?
    I  have included monitors for CUCM using SNMP, however certain error conditions such as DB replication etc are not available using SNMP. What is the best way I can capture these parameters if I dont have the RTMT?
    Thanks in advance
    Roycey

    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Windows/9_1/JABW_BK_E4CC9599_00_environment-configuration-guide/JABW_BK_E4CC9599_00_environment-configuration-guide_chapter_01.html
    As to the other post, just copy the URL and remove partner/

  • SX20, CUCM 10.5 and VCS

    Hi,
    I have added my two units of SX20 in CUCM 10.5 via sip and both are registered and calling each other. 
    Can some guide us whats the usage if vcs expressway? and how to make video call outside the network?
    Whats is role of codec and where ?
    Regards,

    VCS side is Ok. We tried using TLS verifiy on and off.
    The problem is the CUCM that do not accept the certificate, it present this message: “CSR SAN and Certificate SAN does not match” and this can be due to the bug CSCur46416 (the running version is 10.5(1.10000.7)).  Another person said that he uploaded the certificate, but when I checked the certificate wasn´t there and even trying to generate another CSR and certificates, the CUCM always present the same error message.
    We´ll open a SR on TAC to point us the best way to fix it.
    Regards

  • Error while determining CCM version -2

    Hi,  I have Call Manager 8.6 and CUE 8.6 but I got this error every time that I want import the CTI Ports. I thought it was a problem with CUE but I have installed 4 more CUE´s and I got the same error in all of them. The web login and Jati login are correct. Have anyone had the same problem?

    I have same error - when viewing ASA logs at a central site, I see lots of traffic from working CUEs on 80 and 8443 and 443 when looking for ports on CUCM. on the sites that are failing I guess there is some king of inspection from local ASAs I have no access to causing traffic not to get fully through to the cucm. I think the error is not telling the full story. I am sure this is a firewall issue?
    I am trouble shooting with my provider as the failing sites i only see port 80 hit my central ASAs when scanning for ports on the cucm. I will let you know the outcome.

Maybe you are looking for