CUCM 9.1.2 -- 10.5(2) failure

Hi All,
I am trying to upgrade our CUCM from 9.1.2(SU2) --> 10.5(2) (UCSInstall_UCOS_10.5.2.10000-5.sgn.iso)
I believe I have performed all the upgrade requirements:
Our hardware is Cisco UCS with old "Medium" UCS Tested Reference Configuration for 2500 users. Each node has 2 x vCPUs.
9.1.2(SU2) tp 10.5(2) is documented as a "Direct Upgrade"
I have/had at least 30GB free in the common partition on each node
ciscocm.version3-keys.cop has been installed on all nodes
I did not install the refresh_upgrade COP file, as I am upgrading from 9.1.2 (i.e. not pre-version 8.5)
The virtual machine specification meets all the requirements for 10.5(2)
The installation goes for approx 1.5 - 2hrs before it does "Post-installation" tasks where is fails at item 6 or 6 of "Installing database component"
Th install log shows:
01/24/2015 17:24:02 component_install|File:/opt/cisco/install/bin/component_install:807, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
01/24/2015 17:24:02 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:273, Function: refresh_upgrade(), failed to refresh_upgrade infrastructure_post components|<LVL::Critical>
01/24/2015 17:24:02 post_install|File:/opt/cisco/install/bin/post_install:961, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -refresh-upgrade failed (1)|<LVL::Error>
01/24/2015 17:24:02 post_install|Exiting with result 1|<LVL::Info>
01/24/2015 17:24:02 post_install|INSTALL_TYPE="Refresh Upgrade"|<LVL::Debug>
It seem very similar to the following Cisco support forum issue : https://supportforums.cisco.com/printpdf/12334191; however, I have been unable to remove the AUNP dial plan; I suspect because I have quite a number of route patterns using it and do not wish to remove them.
I upgraded the dial plan as an attempt to rectify the issue, however the upgrade still fails.
Any ideas would be much appreciated.
Thanks
Kent

I've run into this issue on several upgrades and always dread seeing a xxNP in use, the way i get around this is by exporting the route patterns, Bulk Administration > Export and select it from there.
TAC will then need to get Root access to remove the xxNP's (all of them) and then the upgrade will succeed.
Once the upgrade is completed and you have installed the xxNP you then need to export the route patterns again from the v10.x server as you will need to edit the header.txt stored within the .tar file. Copy 'CCM : master-10.5.1.11901-1.i386' section from the 10.x export and replace the one in the 9.x export.
You can then import the CUCM 9.x route patterns in CUCM 10.x
Hope this helps,
Richard

Similar Messages

CUCM-VCS Integration VCS B2BUA Encryption Call Failures

All,
I have the following scenario:
CUCM 9.1.2SU1
VCS X8.1.1
MX300 endpoints (CUCM registered)
We are not running in mixed mode on CUCM
We want media streams with external call parties to be encrypted. We do have TLS end-to-end but I don't believe we can support SRTP to the MX300s registered to UCM w/o provisioning mixed mode (based on Cisco docs). So, we are attempting to use Media encryption policy on the VCS. Specifically, we set one of the traversal client zone to use "Best effort". This works for most calls but we have seen a couple of calls fail.
From end user perspective, failures manifest as a call that gets connected and is immediately torn down.
On the VCS, we will see the following when looking at the call history:
The B2BUA Encryption component is disconnected after ~3 seconds. The disconnect reason is: B2BUA disconnected call on the ingress saying "mismatched transport type in answer".
Based on context clues, this points to TLS negotiation. The thing is, if I set the media policy back to "auto" then the call connects fine and the transport is TLS. At least, it reports TLS on my VCS-C and VCS-E.
Any pointers that someone is willing to toss my way?
Thanks in advance,
Bill (@ucguerrilla)

Won't help but I have a very similar but slightly different scenario with:
CUCM 9.1
VCS 8.2.2
Jabber 10 or CUCM registered TC endpoint
As for settings:
CUCM-VCS SIP trunk is TCP not encrypted (never got it to work following the doc step by step....)
VCS-C to VCS-E is TLS as setup on the doc.
On the VCS-C, the DNSZone Media Encrytion mode is set to "Auto"
Some SIP calls work perfectly (i.e. the Cisco test endpoints) but some users have issues. Dialing partners' cloud service video-conference, the call connects and gets dropped immediately. I created myself a trial account on that service to test and can reproduce it all the time. I can see the call coming in my cloud service client and when I accept it it just drops.
On the VCS-C,
I see a SIP 200 OK
an then a call component status=disconnected type=B2BUA
State
Inactive
Start time
2014-11-11 16:51:22
Duration
5 seconds
Disconnect reason summary
disconnected
Disconnect reason details
B2BUA disconnected call on the Egress saying "Received 'Request Timeout' to mid-dialog request"
But on the VCS-E in the call history, I only see and "408 request timeout".
When I call my Jabber account from that service it works well. But in that case the second call component with type B2BUA shows:
State
Inactive
Start time
2014-11-11 17:14:02
Duration
40 seconds
Disconnect reason summary
BYE
Disconnect reason details
Egress disconnected call
Tag
3d14cee5-01ad-4468-9e3b-e0925dde15d4
Box call serial number
1bc2473f-2a09-4dea-8ffd-a7e88a3ef05b
Have also no clue of what is happening

PG JTAPI and CM failure, how to connect with others?

Hi All;
The main site has UCCE side A (RGR-a,PG-a, HDS&ICM&Webview-a), CVP servers and VXML Servers, Gatekeeper, two Voice Gateways and Cluster of CUCM (publisher and 3 subscribers).
Disaster Recovery site has UCCE side B (RGR-a, PG-a, HDS&ICM&Webview-a), CVP Servers and VXML Servers, Gatekeeper, two Voice Gateways and 3 CUCM all subscribers while the publisher in the main site, so the CUCM are clustered with main site.
If the CUCM in the main site had a failure (the publisher and the 3 subscribers), what are the needed configuration need to be done in the main site at the UCCE side A to let it able to communicate with the CUCM subscribers in the Disaster Recovery? Is this failover possible to be autmatic or I have to do it manual?
Your kindly advise is highly appreciated.
Regards
Bilal

Hi Bilal,
one PG can connect to only one CUCM CTI Manager. The redundancy is within the PG A and PG B.
So, if the CTI Manager that the PG A connects fails, PG B JGW process will be become active and will communicate with CTI Manager that PG B connects.
Now, that the connectivity of PG to CTI Manager. But the CTI RP's may register to different Subscriber depending on how the callmanager group is defined on device pool that is assigned to CTI RP.
You should have the Callmanager group for the CTI RP such that it contains both main site and fail over site call managers.
Here are some scenarios.
lets say, you have
sub1 and sub2 on main site
sub3 and sub4 on recovery site
PGA connect to sub1 CTI manager, and PGB connects to sub3 CTI manager. Callmanager group (sub1, sub2, sub3 and sub4 in order) for the CTI RP contains all the call managers
Failure Scenario:
1. If sub2 fails - JGW process on PG B will be active. But CTI RPs will be registered to sub2
2. if sub1 fails, JGW process will reamin active on PG A. but RPs will be registered to sub2
3. if both sub1 and sub2 fails, JGW process will be active on PG B and RPs will be registered on sub3
Hope this helps.
Thanks
- abu

CUCM 9.1.2 Backup Failure

Hi, everybody,
I have a problem with CUCM 9.1.2 when it tries to do a backup, an error is displayed on the CUOM intitled: CISCO DRF FAILURE
and when I lookup at the 'Recommanded Task', it says:
"Verify that /common/drf has the required permission and enough disk space for the DRF user. Check the application logs for further details".
so my question is : What and/or how can I get to the directory /common/drf and check the permissions and the disk space for the DRF user ??
your help will be really appreciated, guys.
thanks.

Thank you for your tip, venperum,
I saw that thread when I was researching on the internet.
The probleme is that I don't have only one CUCM, I have a cluster of:
- 2 CUCMs,
- 1 CUC,
- CUCMIMP 9,
- CUAC 9,
- VM for DRS feature,
- CUCM playing as a TFTP server
I tried to open the console of the CUCM publisher, I entered my login credentials:
user:
password:
I got this command prompt shown in the pic: CLI prompt.PNG
Linux commands doesn't apply here, the only commands that applies are listed in the pic commands on cucm cli.PNG
so, my question is how to get to the root mode shown in the thread you refered me to, and at what VM ? knowing that I logged in the DRS VM, I didn't find the directory: /common as shown below in the pic: No directory common.PNG
So, how to get into the root mode, and at what virtual machine should I log into ??
Thanks, again.

CUCM failover to subscriber failure!

Hi everyone!
I have a CUCM cluster of one publisher and one subscriber, active version 7.0 and inactive version 5.1.3
The pubslisher failed due to a power failure, the Cisco DB wasn't starting at all, and there was no DRS backup. Anyway, I did an upgrade from 5.1 to 7.0 again on the publisher while the telephony was operational normally on the subscriber node.
After the upgrade, I uploaded the Publisher's and Subscriber's licenses, I added back all the changes done to the CUCM between the databases of 5 and 7 (manually added by comparing to the subscriber's) and I replicated to the subscriber when I was done and the replication state was good '2'. And I took an immediate DRS backup.
However, the problem appeared when I restarted the CUCM's publisher node and none of the phones registered with the subscriber node. I thought it was a network problem or server going slow. I turned the publisher off for around 20 mins and nothing changed.
The configuration of the Call Manager group is correct, the licenses are correct, everything seem to be ok. When the phones are registered with the publisher, I can see them registered from the subscriber's phone page but when I stop the publisher, they turn to 'unknown'.
Does anyone have any clue why this is happening? Do I have to upgrade the subscriber again from 5 to 7? I just had this clue in mind, it doesn't make sense to me since replication is working fine between the servers.
One more thing, I use FreeSshd to do the DRS backup on an XP machine, it wasn't connecting on my laptop with Windows 7. What are you guys using on Windows 7? Tried a search result on Google but nothing worked.
Thank you for reading and for tips!
Regards,
Mazen

Hi Mazen,
I think you are on the right track with your thought of re-building
the Subscriber
You would be hitting this CUCM 5.x restriction;
Replacing the Publisher Node
Complete the following tasks to replace the Cisco Unified CallManager publisher server. If you are replacing a single server that is not part of a cluster, follow this procedure to replace your server.
Caution If you are replacing a publisher node in a cluster, you must also reinstall all the subscriber nodes and dedicated TFTP servers in the cluster, after replacing the publisher node. For instructions on reinstalling these other nodes types, see the "Replacing a Subscriber or Dedicated TFTP Server Node" section
Follow the references in the For More Information column to get more information about a step.
Table 4 Replacing the Publisher Node Process Overview
Description For More Information
Step 1
Perform the tasks in the "Server or Cluster Replacement Preparation Checklist" section.
"Server or Cluster Replacement Preparation Checklist" section
Step 2
Gather the necessary information about the old publisher server.
"Gathering System Configuration Information to Replace or Reinstall a Server" section
Step 3
Back up the publisher server to a remote SFTP server by using the Disaster Recovery System (DRS) and verify that you have a good backup.
"Creating a Backup File" section
Step 4
Get the new license and verify it before system replacement.
You only need a new license if you are replacing the publisher node.
See the "Obtaining a License File" section.
Step 5
Shut down and turn off the old server.
Step 6
Connect the new server.
Step 7
Install the same Cisco Unified CallManager release on the new server that was installed on the old server, including any Engineering Special releases.
Configure the server as the publisher server for the cluster.
"Installing Cisco Unified CallManager on the New Publisher Server" section
Step 8
Upload the new license file to the publisher server.
"Uploading a License File" section
Step 9
Restore backed up data to the publisher server by using DRS.
"Restoring a Backup File" section
Step 10
Reboot the publisher server.
Step 11
Perform the post-replacement tasks in the "Post-Replacement Checklist" section.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/5_1/clstr513.html#wp87717
Cheers!
Rob

Installation failure-CUCM 8.6.2 on MCS7845i3

Hello.
I was trying to install CUCM 8.6.2 on MCS7845I3 server with correct memory and disk,good battery, up-to-date server firmware, but keep getting this error
"Critical Error
The hardware you are using is not supported for this product.
Installation will now halt".
Can anyone please maybe advise me what could be the reason? I believe I'm using a good bootable DVD which was from Cisco originally.
Thank you so much for your kind advice in advance.

Hi,
you can run the commands show memory size , show memory count and show hardware from CLI.
regds,
aman

CUCM installation failure

Hello,
we want to install Cisco Unified Connection Manager 10.0.1.10000-24
on VM (VMware ESXi 5.1.0 build 1064113).
The installation failed with this error:
INSTALLATION FAILED - Make sure the serial port for this VM connected to a new empty file before continuing
even if we connect a temporary file the file is unreadable
Thanks
Oronzo

Oronzo,
Were you able to install CUCM 10? I just installed mine tonight. The installation seems to have gone well without issue. However, at the Linux prompt, none of the account I specified during the installation seems to work. I am wondering if there's a web site I need to use to login and if so what is that link? Lastly, how many CUCM instances do I need to install? I can I just make use of one CUCM or do I have to install a publisher and a subscriber?
Thanks,
Lim

CTSMan 1.9.1 and CUCM 8.6.2 sync problems Error 502407

Hi,
I ran into recent problem synchronizing CUCM 8.6.2(b) into CTSman 1.9.1
CTSMan is getting an Error message: 502407
Details
ID:
502407
Severity:
critical
Module:
DiscoveryMgr
SubModule:
CTIAdapter
Summary:
Communication to Unified CM failure
Recommendation:
Verify CCM App User credentials. Verify CTIManager service is activated on the primary application server.
Message:
Unable to create CTI adapter to Unified CM 'CUCM-xxx' because Provider is null.
I researched this earlier in CTSman admin guides, and this error points to CUCM CTI Manager service to be restarted. I did restart this as well as other services, including CUCM hardware itself and, but in vain.
Among other things, i followed the CUCM/CTSman guides when bringing CUCM into CTSman to: created an application user account within CUCM and allocate a proper permissions/user groups etc... it was done.
Among other things there are other servers like Exchange being synchronized with it ( had problems with it earlier that dealt with certificates, it was corrected.).
Can anyone help with this issue.
Responses will be greatly appreciated.
Thank you.

Thanks Manish again for this.
I did get few MediaReosurceListExhausted events from RTMT alerts but was not paying much attention to them. Location bandwidth settings have been checked and increased a bit for sites which were repeatedly getting these events. I will monitor to see if that reduces these alerts. Could you please advise how I can verify it is hitting the maximum limit?
I have also raised this with Cisco TAC and some cores were found on the CUC subscriber server. We seemed to have run into a bug according to Cisco TAC as in here https://tools.cisco.com/bugsearch/bug/CSCug61581/?reffering_site=dumpcr and both CUC servers have been upgraded to 8_6_2_24901_1. It has fixed cores and we are now monitoring the voicemail service for few days to see if it will reoccur.
Regards,

CUCM 8.6 Call Forwarding to External Number Issue

Hello,
Call forwarding worked without problems, we could forward our phones to external numbers and everything was ok, when somebody called to my phone, I could got the call to my cell phone.
But now when I forward my phone to external number and try to call to my phone I get busy trigger.
We didn't change configuration or install any update.
I think its my ISP-s problem, to whom we have SIP Trunk.
I don't understand log file, so can you tell what is the problem?
Here is log:
057729XXXX is called party, cell phone number
original calling party number is 240XXXXX, but it is forwarded to 2484XXX
INVITE sip:2484XXX@ISP-IP:5060 SIP/2.0
Via: SIP/2.0/UDP MY-CUCM-IP:5060;branch=z9hG4bK1003a84126249
From: <sip:057729XXXX@MY-CUCM>;tag=4052091~294be736-ce3b-450f-a7f1-c801f3cc9a7e-27746002
To: <sip:2484XXX@ISP-IP>
Date: Wed, 18 Dec 2013 13:34:18 GMT
Call-ID: 16d82e80-2b11a45a-c43e7-84450d0a@MY-CUCM-IP
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM8.6
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Cisco-Guid: 0383266432-0000065536-0000191815-2219117834
Session-Expires: 1800
P-Asserted-Identity: <sip:057729XXXX@MY-CUCM-IP>
Remote-Party-ID: <sip:057729XXXX@MY-CUCM-IP>;party=calling;screen=yes;privacy=off
Contact: <sip:057729XXXX@MY-CUCM-IP:5060>
Max-Forwards: 68
Content-Type: application/sdp
Content-Length: 215
v=0
o=CiscoSystemsCCM-SIP 4052091 1 IN IP4 MY-CUCM-IP
s=SIP Call
c=IN IP4 MY-CUCM-IP
t=0 0
m=audio 29790 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
|2,100,56,1.173711429^MY-CUCM-IP^MTP_3
17:34:18.526 |EnvProcessUdpPort - EnvProcessUdpHandler::fireSignal() varId = 2|2,100,56,1.173711429^MY-CUCM-IP^MTP_3
17:34:18.526 |EnvProcessUdpHandler::fireSignal - SEND: index = 2, handler = 0xb2d59c98|*^*^*
17:34:18.526 |EnvProcessUdpPort::fireSignal - SEND, destination = ISP-IP:5060|*^*^*
17:34:18.526 |EnvProcessUdpPort - EnvProcessUdpHandler::send(buff, 1172, ISP-IP:5060)|*^*^*
17:34:18.536 |EnvProcessUdpHandler::handle_input - handle = 334|*^*^*
17:34:18.536 |EnvProcessUdpHandler::handle_input   Status: 0, Id: 2|*^*^*
17:34:18.536 |//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 358 from ISP-IP:[5060]:
[12623361,NET]
SIP/2.0 100 Trying
Call-ID: 16d82e80-2b11a45a-c43e7-84450d0a@MY-CUCM-IP
CSeq: 101 INVITE
From: <sip:057729XXXX@MY-CUCM-IP>;tag=4052091~294be736-ce3b-450f-a7f1-c801f3cc9a7e-27746002
To: <sip:2484XXX@ISP-IP>;tag=sip+1+b3a00013+867def6a
Via: SIP/2.0/UDP MY-CUCM-IP:5060;branch=z9hG4bK1003a84126249
Server: CISCO-SBC/2.x
Content-Length: 0
|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/Stack/Info/0x0/ccsip_spi_get_msg_type returned: 2 for event 1|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/Stack/Transport/0x0/context=(nil)|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/Stack/Transport/0x0/gConnTab=0xf484290, addr=ISP-IP, port=5060, connid=2, transport=UDP|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/Stack/Info/0x0/Return existing connection for port 5060 connId 2|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/Stack/Info/0x0/Checking Invite Dialog|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/Stack/Info/0xb1b50c90/INVITE response with no RSEQ - disable IS_REL1XX|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_TRYING value=500 retries=3|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/Stack/States/0xb1b50c90/0xb1b50c90 : State change from (STATE_SENT_INVITE, SUBSTATE_NONE) to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_EXPIRES value=180000 retries=0|2,100,230,1.4901096^ISP-IP^*
17:34:18.536 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_start_timer: type=SIP_TIMER_EXPIRES value=180000 retries=0|2,100,230,1.4901096^ISP-IP^*
17:34:18.561 |EnvProcessUdpHandler::handle_input - handle = 334|*^*^*
17:34:18.561 |EnvProcessUdpHandler::handle_input   Status: 0, Id: 2|*^*^*
17:34:18.561 |//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 396 from ISP-IP:[5060]:
[12623362,NET]
SIP/2.0 403 Forbidden
Call-ID: 16d82e80-2b11a45a-c43e7-84450d0a@MY-CUCM-IP
CSeq: 101 INVITE
From: <sip:057729XXXX@MY-CUCM-IP>;tag=4052091~294be736-ce3b-450f-a7f1-c801f3cc9a7e-27746002
To: <sip:2484XXX@ISP-IP>;tag=sip+1+b3a00013+867def6a
Via: SIP/2.0/UDP MY-CUCM-IP:5060;branch=z9hG4bK1003a84126249
Server: CISCO-SBC/2.x
Content-Length: 0
Contact: <sip:ISP-IP:5060>
[12623363,NET]
ACK sip:2484XXX@ISP-IP:5060 SIP/2.0
Via: SIP/2.0/UDP MY-CUCM-IP:5060;branch=z9hG4bK1003a84126249
From: <sip:057729XXXX@MY-CUCM-IP>;tag=4052091~294be736-ce3b-450f-a7f1-c801f3cc9a7e-27746002
To: <sip:2484XXX@ISP-IP>;tag=sip+1+b3a00013+867def6a
Date: Wed, 18 Dec 2013 13:34:18 GMT
Call-ID: 16d82e80-2b11a45a-c43e7-84450d0a@MY-CUCM-IP
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0
INVITE sip:2484XXX@ISP's-Other-IP:5062 SIP/2.0
Via: SIP/2.0/UDP MY-CUCM-IP:5062;branch=z9hG4bK1003a95b8f3900
From: <sip:057729XXXX@MY-CUCM-IP>;tag=4052092~294be736-ce3b-450f-a7f1-c801f3cc9a7e-27746002
To: <sip:2484XXX@ISP's-Other-IP>
Date: Wed, 18 Dec 2013 13:34:18 GMT
Call-ID: 16d82e80-2b11a45a-c43e8-84450d0a@MY-CUCM-IP
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM8.6
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Cisco-Guid: 0383266432-0000065536-0000191816-2219117834
Session-Expires: 1800
P-Asserted-Identity: <sip:057729XXXX@MY-CUCM-IP>
Remote-Party-ID: <sip:057729XXXX@MY-CUCM-IP>;party=calling;screen=yes;privacy=off
Contact: <sip:057729XXXX@MY-CUCM-IP:5062>
Max-Forwards: 68
Content-Type: application/sdp
Content-Length: 215
v=0
o=CiscoSystemsCCM-SIP 4052092 1 IN IP4 MY-CUCM-IP
s=SIP Call
c=IN IP4 MY-CUCM-IP
t=0 0
m=audio 29792 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
|2,100,56,1.173711431^MY-CUCM-IP^MTP_3
17:34:18.567 |EnvProcessUdpPort - EnvProcessUdpHandler::fireSignal() varId = 0|2,100,56,1.173711431^MY-CUCM-IP^MTP_3
17:34:18.567 |EnvProcessUdpHandler::fireSignal - SEND: index = 0, handler = 0xa6b4d7c0|*^*^*
17:34:18.567 |EnvProcessUdpPort::fireSignal - SEND, destination = ISP's-Other-IP:5062|*^*^*
17:34:18.567 |EnvProcessUdpPort - EnvProcessUdpHandler::send(buff, 1177, ISP's-Other-IP:5062)|*^*^*
17:34:18.569 |EnvProcessUdpHandler::handle_input - handle = 335|*^*^*
17:34:18.569 |EnvProcessUdpHandler::handle_input   Status: 0, Id: 0|*^*^*
17:34:18.569 |//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 394 from ISP's-Other-IP:[5062]:
[12623365,NET]
SIP/2.0 100 trying -- your call is important to us
Via: SIP/2.0/UDP MY-CUCM-IP:5062;branch=z9hG4bK1003a95b8f3900;rport=5062
From: <sip:057729XXXX@MY-CUCM-IP>;tag=4052092~294be736-ce3b-450f-a7f1-c801f3cc9a7e-27746002
To: <sip:2484XXX@ISP's-Other-IP>
Call-ID: 16d82e80-2b11a45a-c43e8-84450d0a@MY-CUCM-IP
CSeq: 101 INVITE
Server: kamailio (3.3.1 (x86_64/linux))
Content-Length: 0
17:34:18.587 |//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 375 from ISP's-Other-IP:[5062]:
[12623366,NET]
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP MY-CUCM-IP:5062;branch=z9hG4bK1003a95b8f3900;rport=5062
Call-ID: 16d82e80-2b11a45a-c43e8-84450d0a@MY-CUCM-IP
From: <sip:057729XXXX@MY-CUCM-IP>;tag=4052092~294be736-ce3b-450f-a7f1-c801f3cc9a7e-27746002
To: <sip:2484XXX@ISP's-Other-IP>;tag=dc6a4ae7
CSeq: 101 INVITE
Reason: Q.850;cause=0;text="unknown"
Content-Length: 0
|2,100,230,1.4901099^ISP's-Other-IP^*
[12623367,NET]
ACK sip:2484XXX@ISP's-Other-IP:5062 SIP/2.0
Via: SIP/2.0/UDP MY-CUCM-IP:5062;branch=z9hG4bK1003a95b8f3900
From: <sip:057729XXXX@MY-CUCM-IP>;tag=4052092~294be736-ce3b-450f-a7f1-c801f3cc9a7e-27746002
To: <sip:2484XXX@ISP's-Other-IP>;tag=dc6a4ae7
Date: Wed, 18 Dec 2013 13:34:18 GMT
Call-ID: 16d82e80-2b11a45a-c43e8-84450d0a@MY-CUCM-IP
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0

SIP/2.0 403 Forbidden error
If your router is sending a SIP/2.0 403 Forbidden error to the SIP server you are registered to, there is a good chance your router is blocking the incoming call due to the toll-faud prevention feature that was added to IOS version 15.1(2)T.
How to Identify if TOLLFRAUD_APP is Blocking Your Call
If the TOLLFRAUD_APP is rejecting the call, it generates a Q.850       disconnect cause value of 21, which represents ‘Call Rejected’. The       debug voip ccapi inout command can be run to       identify the cause value.
Additionally, voice iec syslog can be       enabled to further verify if the call failure is a result of the toll-fraud       prevention. This configuration, which is often handy to troubleshoot the origin       of failure from a gateway perspective, will print out that the call is being       rejected due to toll call fraud. The CCAPI and Voice IEC output is demonstrated       in this debug output:
%VOICE_IEC-3-GW: Application Framework Core: Internal Error (Toll fraud call rejected):
IEC=1.1.228.3.31.0 on callID 3 GUID=F146D6B0539C11DF800CA596C4C2D7EF
000183: *Apr 30 14:38:57.251: //3/F146D6B0800C/CCAPI/ccCallSetContext:
   Context=0x49EC9978
000184: *Apr 30 14:38:57.251: //3/F146D6B0800C/CCAPI/cc_process_call_setup_ind:
   >>>>CCAPI handed cid 3 with tag 1002 to app "_ManagedAppProcess_TOLLFRAUD_APP"
000185: *Apr 30 14:38:57.251: //3/F146D6B0800C/CCAPI/ccCallDisconnect:
   Cause Value=21, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
The Q.850 disconnect value that is returned for blocked calls can also       be changed from the default of 21 with this command:
voice service voip
ip address trusted call-block cause
How to Return to Pre-15.1(2)T Behavior
Source IP Address Trust List
There are three ways to return to the previous behavior of voice       gateways before this trusted address toll-fraud prevention feature was       implemented. All of these configurations require that you are already running       15.1(2)T in order for you to make the configuration change.
Explicitly enable those source IP addresses from which you would like           to add to the trusted list for legitimate VoIP calls. Up to 100 entries can be           defined. This below configuration accepts calls from those host           203.0.113.100/32, as well as from the network 192.0.2.0/24. Call setups from           all other hosts are rejected. This is the recommended method from a voice           security perspective.
voice service voip
ip address trusted list
ipv4 203.0.113.100 255.255.255.255
ipv4 192.0.2.0 255.255.255.0
Configure the router to accept incoming call setups from all source           IP addresses.
voice service voip
ip address trusted list
ipv4 0.0.0.0 0.0.0.0
Disable the toll-fraud prevention application completely.
voice service voip
no ip address trusted authenticate
Two-Stage Dialing
If two-stage dialing is required, the following can be configured to       return behavior to match previous releases.
For inbound ISDN calls:
voice service pots
no direct-inward-dial isdn
For inbound FXO calls:
voice-port
secondary dialtone

Problem with installing CUCM on MCS-7816-I5

Hi to all.
I have a problem with installing CUCM 8.6.1 on new MCS-7816-I5 (IBM) hardware. The problem is that installation loops in restart after upgrading MCS firmware. Actualy, installation does not sucessfully upgrade firmware, so every time it detects old firmware and trying to upgrade it.
I also tried update MCS firmware with downloaded Firmware Update Utility 3.6.5 CD from Cisco downloads, but it also fails.
Does anyone have idea what's going on? Is this a Cisco failure or IBM server failure?
Here is some details from log file generated with this Firmware Update Utility 3.6.5:
==============
Initial Selection
Machine Type: 4251 OS: SLES 10 Arch: 64 bit
IsPartition: 0
Update:   IBM System x uEFI update for x3200 M3 /3250 M3
Severity: Critical
Reboot:   Reboot Required to take effect
UpdateID: ibm_fw_uefi_gye142a_linux_32-64 Requisite:None
Version: 1.08 (GYE142A)
Install: 1.06 (GYE135A)
Select:    Yes
Update:   IBM Dynamic System Analysis
Severity: Recommended
Reboot:   Reboot Required to take effect
UpdateID: ibm_fw_dsa_3.20_dsyt75x_linux_32_64
Requisite:None
Version: 3.20 (DSYT75X)
Install: 3.01 (DSYT60K)
Select:    Yes
Update:   IBM Online SAS/SATA Hard Disk Drive Update Program
Severity: Critical
Reboot:   Not Required
UpdateID: ibm_fw_hdd_sas-1.08.01_linux_32-64
Requisite:None
Name:     WD2502ABYS-23B7A0 (/dev/sg0)
Version: 02.03B07
Install: 02.0
Select:    Yes
Update:   Integrated Management Module Update
Severity: Critical
Reboot:   Not Required
UpdateID: ibm_fw_imm_yuoo84c_linux_32-64 Requisite:None
Version: 1.22 (YUOO84C)
Install: 1.10 (YUOO57H)
Select:    Yes
IBM Command Line IMM Flash Update Utility v1.05.03 Licensed Materials - Property of IBM
(C) Copyright IBM Corp. 2009,2010 All Rights Reserved.
LAN-over-USB device not configured.
Error connecting to IMM using IP address 169.254.95.118.
Please verify the LAN over USB interface is configured properly and active.
Error flashing firmware: 3
IBM Command Line IMM Flash Update Utility v1.10.11 Licensed Materials - Property of IBM
(C) Copyright IBM Corp. 2009,2010 All Rights Reserved.
Refreshing LAN-over-USB IP address. This may take several minutes.
Attempting to discover the IMM(s) via SLP.
Error connecting to IMM using IP address 169.254.95.118.
Please verify the LAN over USB interface is configured properly and active.
Error flashing firmware: 10
(C) Copyright IBM Corp.2010. All Rights Reserved.
FdrvWL -- Flash Drive(s)                                     3.10.08.19
   1 Ada:0 SID:0   PN:44E9172:42C0463 SN:1J242783 FW:02.03B07              T:13 FW:Ok
AdaNbr(Type)      DevFnd Flashed(SAS SATA) NbrFailed
0(onBoard)           1       0   0    0          0
                       1       0   0    0          0 Error(s)
Update completed successfully. <-- THIS SUCCESS, BUT EVERY TIME IT UPGRADEING AGAIN FROM OLD VERSION, LIKE NEVER REALY UPGRADED TO NEWER VERSION
IBM Command Line IMM Flash Update Utility v1.10.11 Licensed Materials - Property of IBM
(C) Copyright IBM Corp. 2009,2010 All Rights Reserved.
Refreshing LAN-over-USB IP address. This may take several minutes.
Attempting to discover the IMM(s) via SLP.
Error connecting to IMM using IP address 169.254.95.118.
Please verify the LAN over USB interface is configured properly and active.
Error flashing firmware: 10
===========================
Thanks,
Sinisa.

Hi Sinisa,
It almost sounds like this bug;
CSCtn81201
Incorrect "Hardware Configuration Error" due to hardware setup errors
Symptom:
Refresh upgrade stops with IMM device detection, and then server being reported as unsupported
Conditions:
in-band USB interface was disabled, which is configurable via IBM system X or IMM (browser) interfaces.
Workaround:
change the in-band usb interface settings to enabled.
Related Bug
Status
Fixed
Severity
4 - minor
Last Modified
Aug 17,2011
Product
Cisco Unified Communications Manager (CallManager)
Platform
Dependent
Technology
nav
1st Found-in
8.6(0.99081.3)
Fixed-in
8.6(1.96000.1), 9.0(0.95070.38), 9.0(0.95070.39), 8.6(1.99989.1), 8.6(1.95050.1), 9.0(0.96000.1), 8.6(1.97011.2), 8.6(1.95190.40), 8.6(1.97011.1), 8.6(0.95180.9), 9.0(0.95010.1), 8.6(1.95020.1), 8.6(1.95040.1), 8.6(0.98000.50), 8.6(0.98000.17), 8.6(0.99981.2), 8.6(1.10000.1), 8.6(1.99986.1), 8.6(1.95020.58), 8.6(1.96000.51), 8.6(1.10000.43)
Cheers!
Rob

Install of CUCM 8.6.1.10000-43 on VMWare fails on installing progmeter

Hi, Everyone
First time post here, and first time installing CUCM (any version).
I built a VM using a downloaded OVA template for CUCM 6.5.1.10000-43, and the install fails with a critical stop. Once I figured out how to dump logs to the virtual serial port, and looked at the install.log, I found the following information that looks like where the install failed (these are the only LVL::Error and LVL::Critical messages in the log).
It looks like install failed to install the progmeter application component.
Does anyone know what this app does? Any ideas on why it might have failed to install and possible workaround?
I may already have the answer to the question, as I'm attempting install on a VM running on VMWare vServer (rather than ESX/ESXi/vSphere). It is possible that simply being on an unsupported configuration is my problem. I'm trying to work with the equipment immediately available to me, but fully understand that I may have set myself up for failure by even attempting this.
Any help is appreciated greatly.
Regards,
Sean C
INSTALL LOG SNIPPET
08/17/2011 17:51:51 component_install|File:/opt/cisco/install/bin/component_install:743, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
08/17/2011 17:51:51 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:155, Function: install(), failed to install application components|<LVL::Critical>
08/17/2011 17:51:51 post_install|File:/opt/cisco/install/bin/post_install:869, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -install failed (1)|<LVL::Error>
08/17/2011 17:51:51 post_install|Exiting with result 1|<LVL::Info>
08/17/2011 17:51:51 post_install|INSTALL_TYPE="Basic Install"|<LVL::Debug>
08/17/2011 17:51:51 post_install|File:/opt/cisco/install/bin/post_install:570, Function: check_for_critical_error(), check_for_critical_error, found /common/log/install/critical.log, exiting|<LVL::Error>
08/17/2011 17:51:52 post_install|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]|<LVL::Debug>
08/17/2011 17:51:52 display_screen|Arguments: "Critical Error" "The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.
"/opt/cisco/install/callmanager/scripts/cm_msa_post.sh install PostInstall 8.6.1.10000-43 8.6.1.10000-43 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt " terminated. Exceeded max time (360)
The system will now halt.
Continuing will allow you to dump diagnostic information before halting." "Continue"|<LVL::Debug>

Hi,
Has anyone found a fix for this?
I am trying to run call manager 8.6.1 on the following enviroment
VMware ESXI 4.1
4GB of RAM
80 GB HDD Space
I have allocated the VM one CPU
In regards to vsergeyey reponse I have checked the network adapter and this is flexible.
I have run the OVA template firstly before mounting the image
I have tried installing numerous times.
Each and every time near the "Installing Database Component" I get the following error;

HELP - Modify user group by bulk un CUCM 8.6

Hi guys,
I am having problem by update/modify user group on CUCM.
There are already some users within user group with admin privileges. That should be changed, so I created a group with some privileges and then I tried to change the usergroup by bulk. but the bulk ADDS the usergroup to the correct and maintain both.
After that I decided to have 2 rows, for the same user, one for the group with empty space (to delete it), and another with the new usergroup. But CUCM does not either do that. it sills maintain the user group..
Does anyone has successfully changed the user group by bulk?
I will appreciate your advices.
Update Users - Custom File
Begin Time : 04/29/2015 13:46:41
Query :
Update Users in CUCM_1L_Template.csv
Failure Details :
users Error Code Error Description
******** NO ERROR FOUND ********
Result Summary :
UPDATE for 2 USERS passed.
UPDATE for 0 USERS failed.
End Time : 04/29/2015 13:46:41
Kind Regards.
Juan Gerardo Hernandez
CCNP Voice

That's correct, what you're seeing is WAD, this topic has been discussed plenty of times before, the only option you have is SNR

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

Conference call failure

I am part of a non-profit that irregularly holds board meetings via a Skype audio conference call. We usually have 7-8 members, all free skype users, in on the calls, but on our last one we had 10. It was an utter failure. Most members could not hear all of the contributions made by others -- audio would cut out while they were speaking. Several couldn't hear anyone else talk for long stretches. At least one never heard anyone else at all. When we had conferences with the fewer number, one particular person had these kind of problems (which I attributed to her connection speed), but not everyone had them as happened this time. Even the host (chairman) was having the same difficulties. He thought we may have crossed some threshold in going from 8 to 10. After nearly an hour of struggling to make ourselves heard, we gave up on the audio and did a few crucial agenda items via chat before ending the call.
Would having the host of the conference call be a premium user possibly eliminate such problems, or do we have to address the Internet connection speed of the host? (Or both, maybe?)
It is really difficult for this non-profit to get its board members together at one time. It can take a month or more to re-schedule after a failure like this. We need something reliable, which was why we chose Skype in the first place.

What protocol are you running on the GW??
MGCP? H323?
If H323, have you properly configured the codecs??? H323 uses G729 by default if nothing is configured.
CUCM CFB only supports G711 and for MOH to work with other codecs you need to enable them under IPVMS service parameters.
HTH
java
If this helps, please rate
www.cisco.com/go/pdihelpdesk

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.

CUCM 9.1.2 -- 10.5(2) failure

Similar Messages

Maybe you are looking for