<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"> 
  <channel>
  <title>CM Hot Issues from Cisco TAC</title>
  <link>http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_tech_note09186a0080937324.shtml</link>
  <description>Hot Issues from Cisco TAC.  Please click the link for complete details.</description>
  <language>en-us</language>

  <managingEditor>wsisk@cisco.com (Wes Sisk)</managingEditor>
  <webMaster>news-at-cisco-rss@cisco.com (Cisco Newsroom)</webMaster>
  <pubDate>Mon, 23 Nov 2009 10:50:08 EST</pubDate>
  <lastBuildDate>Mon, 23 Nov 2009 10:50:08 EST</lastBuildDate>
  <generator>PERL</generator>

  <docs>http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_tech_note09186a0080937324.shtml</docs>
  <ttl>10080</ttl>

<item>
<title>CUCM is not sending Daylight Saving Time updates , Fixed CSCsy25150</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy25150</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 Certain models of Cisco IP Phones (first generation) fail to get the time
 information from the Cisco Unified Communications Manager server component.
 Cisco IP Phone Models: 7905, 7910, 7912, 7920, 7921, 7925, 7935, 7936, 7937, 7940,
 7960, 7985.
 
 Time of Day routing (ToD) in CUCM is also affected.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 Any second generation IP Phone registered to Cisco Unified Communication
 Manager 5.X-7.X where Daylight Savings Time changes are in affect.
 
 Affects the start of DST in March for the following timezones:
 * Newfoundland Standard/Daylight Time (GMT-03:30)
 * Atlantic Standard/Daylight Time (GMT-04:00)
 * Eastern Standard/Daylight Time (GMT-05:00)
 * Central Standard/Daylight Time (GMT-06:00)
 * Mountain Standard/Daylight Time (GMT-07:00)
 * Pacific Standard/Daylight Time (GMT-08:00)
 * Alaskan Standard/Daylight Time (GMT-09:00)
 * Argentina Standard/Daylight Time (GMT-03:00)
 * Montevideo, Uruguay Standard/Daylight Time (GMT-03:00)
 * Pacific SA Daylight Time (GMT-04:00
&lt;br&gt; 
 &lt;B&gt;Workarounds:&lt;/B&gt;
 Workaround #1:
 Do nothing and wait for time to automatically correct.
 US timezones automatically correct on March 15, 1 week late. 
 Argentina timezones automatically correct on March 22, 1 week late.
 --------------------------
 
 Workaround #2:
 Apply a temporary configuration workaround. Note this workaround will have to
be removed when system is patched or after March 15 (March 22 for Argentina),
whichever comes first.
 a. Using CUCM Admin go to: System---Date / Time Group
 b. Create new Date / Time group with one hour extra of local time.
 c. Go to System --- Device pool
 d. Create a New Device pool and assign the (one hour extra Date time group) to
this device pool.
 e. Assign the new Device pool to and Cisco IP Phones that are displaying the
incorrect time.
 f. use BAT or BPS to apply to specific groups based on
(devicemodel,currentdevicepool).
 
 Make similar changes for Time of Day call routing repeat schedules.
 
 NOTE: This change will have to be backed out after patching the system or
after March 15 (March 22 for Argentina), whichever happens first.
 --------------------------
 
 
 Workaround #3:
 Apply a patch from Cisco.com.  This patch works on all Versions of CUCM 5.x-7.x
 
 Software Download Center path:
 Voice and Unified Communications  &gt; Cisco Unified Communications Manager
 Version 7.0  &gt; Unified Communications Manager/CallManager Utilities  &gt; UCM COP
 Files
 
 Hyperlink:
 
 http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=UCM+COP+Files&amp;mdfid=281941895&amp;sftType=Unified+Communications+Manager%2FCallManager+Utilities&amp;optPlat=&amp;nodecount=2&amp;edesignator=null&amp;modelName=Cisco+Unified+Communications+Manager+Version+7.0&amp;treeMdfId=278875240&amp;treeName=Voice+and+Unified+Communications&amp;modifmdfid=&amp;imname=&amp;hybrid=Y&amp;imst=N&amp;lr=Y
 
 The same patch file is used for all versions of CUCM Versions 5.x-7.x
 
 &lt;b&gt;&lt;i&gt;Do not install this patch on subscriber server.  It is for publisher
only.&lt;/i&gt;&lt;/b&gt;
 
 A new patch has been released.  The original patch documentation advised to
only install on publisher.  However, some users attempted patch subscribers and
an extermely few of those experienced catastrophic failure.  That failure is
captured in CSCsy33380.
 
 The original patch and corresponding md5hash were:
 ciscocm.dst_march_2009.cop.sgn d4f5e2562982f9fdaf4446be2ae08df1
 
 The new patch and corresponding md5hash are:
 ciscocm.dst1_march_2009.cop.sgn d60c522e294a3ca9e7cceaeda51dc181
 
 
 A Field Notice is posted on this issue here: 
 http://www.cisco.com/en/US/customer/ts/fn/632/fn63213.html
 
 Please follow the steps listed in the Field Notice to follow up if you have
questions.
&lt;br&gt; 
 
 
 &lt;B&gt;Further Information:&lt;/B&gt;
 The workaround is only a patch to correct time issues for the week of 
 March 8 - March 15, 2009 for US
 March 15 - March 22, 2009 for Argentina
 
 Any timezone which changes on Friday or Saturday is actually addressed by
CSCsy33379.
 
 After that time will be correct until DST ends in November.  Additional
permanent fixes have been released to correct DST fallback in November and to
remove changes for this specific patch so that DST will begin and end correctly
correctly in 2010.

The following Cisco Unified Communication Manager versions containing the fixes
are now on CCO:

5.1.3.7000-5 (5.1(3f))

6.1.3.3000-1 (6.1(3b))

6.1.3.3190-1 (6.1(3b)SU1)

7.0.1.11002-4 (7.0(1)SU1a)

7.0.2.20000-5 (7.0(2a))

If you are running a Cisco Unified Communication Manager Engineering Special
(ES), please check the &quot;Fixed-In&quot; field of this bug (CSCsy25150) and CSCsy33379
to find out what ES version contains the fixes. 

Please check the Cisco Communications Manager Software Compatibility Matrix to
verify your upgrade path.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy25150</guid>
</item>
<item>
<title>UCM is not sending DST updates on Friday, Saturday , Fixed CSCsy33379</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy33379</link>
<description>
None
 &lt;B&gt;Symptom:&lt;/B&gt;
 Cisco Unified Communications Manager does not send Daylight Saving Time
updates for:
 - Time of Day routing (ToD), and 
 - for these Cisco IP Phone models: 
    CP-7905, CP-7910, CP-7912 CP-7920, CP-7921, CP-7925, CP-7935, CP-7936,
CP-7937, CP-7940, 
    CP-7960, CP-7985.
&lt;br&gt; 
 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 This vulnerability only exists for a Device Pool that uses the Date / Time
group of time zones, where DST changes on a Friday or Saturday.
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 Please see CSCsy25150 for workaround details.
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy33379</guid>
</item>
<item>
<title>dbnotify client removed, unable to reset phones , Fixed CSCso93220</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso93220</link>
<description>Symptom:
	Cannot reset phones.  Resetting a phone from the phone webpage does not 
	reset the phone.
	
	show tech notify shows ccm has been removed from the list
	
	Cannot login via Extension Mobility - login indicates success, but profile does 
	not get applied.
&lt;br&gt;	
Conditions:
	UNKNOWN - an intermittent issue.
&lt;br&gt;	
Workaround:
	Restart the callmanager service.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso93220</guid>
</item>
<item>
<title>Critical BIOS Update for MCS 7825-I2 fails to boot after Oct 1, 2009 , Fixed CSCta43460</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta43460</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Starting October 1, 2009 the MCS 7825-I2 servers will not boot properly. These may run any of the Cisco Unified Communications products.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Customer is running an affected product on MCS 7825I2 with BIOS version 1.43 or earlier. details of hardware model and BIOS version can be found by running platform admin CLI command &quot;show hardware&quot;.
&lt;br&gt; 
&lt;B&gt;Workaround:&lt;/B&gt;
For Windows 2003 based products obtain upgrade from Cisco.
For Linux based appliance products obtain upgrade from Cisco.
For Windows 2000 based products Cisco will not be releasing a patch as those products have passed End of Software Maintenance in the End of Life process.
&lt;br&gt;

&lt;B&gt;Further Information&lt;/B&gt;
CM5.1(3): If upgrading CM5.1(3) and currently running an Engineering Special (ES) obtain the latest 5.1(3)ES here:
http://tools.cisco.com/support/downloads/go/ReleaseType.x?optPlat=&amp;isPlatform=Y&amp;mdfid=280735907&amp;sftType=Unified+Communications+Manager+Updates&amp;treeName=Voice+and+Unified+Communications&amp;modelName=Cisco+Unified+Communications+Manager+Version+5.1&amp;mdfLevel=Software%20Version/Option&amp;treeMdfId=278875240&amp;modifmdfid=null&amp;imname=&amp;hybrid=Y&amp;imst=N

Version 5.1(3.7109.1) under the All Releases, Engineering Specials Section.
Note this download is a patch only, denoted by &quot;k9-patch-es&quot; in the filename, and will only patch earlier 5.1(3) versions.

5.1(3) train has a special issue, CSCsm37017, that is fixed in 5.1(3)ES but not fixed in 5.1(3g).  This fix is present in all 5.1(3)ES after 5.1.3.2104-1. Attempting to upgrade from a 5.1(3)ES that includes this fix to 5.1(3g) will fail with this error:

error in installdb_l2.log:
09/24/2009 09:39:27.543 installdb|*ERROR* Error executing &quot;insert into processnodeservice (devicenamemonitorflag,devicetypemonitorflag,enable,filetraceflag,fkprocessnode,includenondevicetraces,isactive,maxfilesize,numfiles,numlines,numminutes,outputdebugstringflag,pkid,priority,restrictserver,tkservice,tracelevel,usercategories,usexml) values (&#39;F&#39;,&#39;T&#39;,&#39;T&#39;,&#39;T&#39;,&#39;6e85a7a0-669d-4ec1-9d67-1bf4c811d797&#39;,&#39;F&#39;,&#39;T&#39;,1,10,10000,1440,&#39;F&#39;,&#39;68e7183f-1340-4f94-928b-3f385de70fae&#39;,0,&#39;F&#39;,93,63,15,&#39;F&#39;): [Informix][Informix ODBC Driver][Informix]Missing key in referenced table for referential constraint (informix.tk_processnodeservice_tkservice).|

There are other fixes that may cause similar failures.  Those failures may appear as:
10/03/2009 01:15:05 AppInstall|cmdExec: Command: /partB/usr/local/bin/base_scripts/env.sh nice -n 19 /usr/sbin/chroot /partB /usr/local/cm/script/5.1.3.8000-4/cm-dbl-install L2 PostInstall 5.1.3.8000-4 5.1.3.7107-1 /usr/local/cm/ /partB/usr/local/cm/ /var/log/install/install_log_091003004108.log -- failed with failure code 1|&lt;LVL::Warn&gt;
10/03/2009 01:15:05 AppInstall|Internal Error, File:instMain.c:1501, Function: handlePhase(), Failed to exec command: &quot;/partB/usr/local/bin/base_scripts/env.sh nice -n 19 /usr/sbin/chroot /partB /usr/local/cm/script/5.1.3.8000-4/cm-dbl-install L2 PostInstall 5.1.3.8000-4 5.1.3.7107-1 /usr/local/cm/ /partB/usr/local/cm/ /var/log/install/install_log_091003004108.log&quot;|&lt;LVL::Critical&gt;
10/03/2009 01:15:05 upgrade_install.sh|Cleaning up download...|&lt;LVL::Info&gt;

In both cases the appropriate action is to upgrade to the CUCM ES 5.1(3.7109.1) or later.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta43460</guid>
</item>
<item>
<title>Perm Gen memory low after activation/deactivation cycles , Fixed CSCsy70968</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy70968</link>
<description>
Symptom:
 CPU spike while activating and deactivating services in SA page
 OR
 Tomcat log shows &quot;java.lang.OutOfMemoryError: PermGen space&quot;
&lt;br&gt; 
 Conditions:
 CPU spike while activating and deactivating services in SA page
 OR
 Java PermGen memory becomes low on repeated activation/deactivation or
start/stop of Cisco web services such as CAR.
&lt;br&gt; 
 Workaround (for the OutofMemory issue):
 To recover:

- Restart Tomcat.

To avoid the issue:

- Disable the CAR web service
- Do not stop/start other web services available in the Serviceability GUI.

Additional Info:
Please see CSCta20132.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy70968</guid>
</item>
<item>
<title>Intermittently silence packets streamed from MOH &amp;/or ANN Server , Fixed CSCta10219</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta10219</link>
<description>Symptom:
after invoking Music on Hold server several times, unicast moh did not play music on hold.  Music on hold may be invoked by hold, transfer, conference, park, or other features.
&lt;br&gt;
Conditions:
UCM 6.1(4) and unicast music on hold server invoked several times.
ANN could be affected by this behavior as well
&lt;br&gt;
Workaround:
Upgrade to a version with fix for this issue.

Alternate Workaround:
(a) Configure each MOH audio source ID for multicast
and (b) Configure each MOH server to multicast
and (c) All Media Resource Groups (if any are defined) must NOT have multicast enabled

This should result in MOH servers sending out multicast but also able to send out unicast MOH on same MOH resources.

This would not require making any network (router) changes to forward multicast MOH packets as long as Media Resource Groups (MRG) are not configured to enable multicast MOH.

One Drawback:
  The MOH servers will be transmitting multicast streams for each MOH source and MOH codec so this may add some network traffic to the local network.  These multicast streams will be continuous and running at all times.  The MOH server(s) will be sending the MC stream(s) to the local router but as long as the router is NOT configured to forward the moh multicast packets the lan traffic will be minimal.  By default, routers do not forward multicast moh packets.

No workaround known for ANN issues.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta10219</guid>
</item>
<item>
<title>CUCM 7.1.2 file system read-only mode after EXT3 Journal aborted error , Fixed CSCta73022</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta73022</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
  
 File system goes to read only mode.

The following may be seen in the (RTMT-System Logs) or &quot;messages&quot; file on the
local server:
-------
kern 2 kernel: EXT3-fs error (device sda2): ext3_journal_start_sb: Detected
aborted journal

kern 2 kernel: Remounting filesystem read-only 
-------

You could also see the following in the (RTMT-Application Logs) or
&quot;CiscoSyslog&quot; file:
-------
SyslogSeverityMatchFound events generated:  SeverityMatch - Critical kernel:
EXT3-fs error (device sdb1) in start_transaction: Journal has aborted 

or

SyslogSeverityMatchFound Detail: At Tue Sep 01 23:01:03 CDT 2009 on node
10.120.200.33, the following SyslogSeverityMatchFound events generated: 
SeverityMatch - Critical kernel: EXT3-fs error (device sdb1) in
start_transaction: Journal has aborted

------------------------------
      To determine whether the root (/) partition is still writable, enter the
     following from CLI:
     utils iothrottle enable
     
     You should see the following message:
      &quot;I/O throttling has been enabled&quot;
     
     utils iothrottle disable
     
     You should see the following message:
      &quot;I/O throttling has been disabled&quot;
     
      To determine whether the /common partition is still writable, enter the
     following from CLI every 2 minutes:
     
     file list activelog syslog/* detail
     
     You should see the size of the file &quot;CiscoSyslog&quot; change, for e.g.
     
     589,219  CiscoSyslog
     
     and then approx. 2 minutes later:
     
     589,550  CiscoSyslog
&lt;br&gt;
        
      &lt;B&gt;Conditions:&lt;/B&gt;
   
      Following hardware models are susceptible to the problem when installed or
     upgraded to CUCM or Unity Connection release 7.1.2.20000-2:
            MCS 7835-I2 servers
            MCS 7845-I2 servers
            or
            customer-provided IBM xSeries x3650
      
      CUCM/UC release can be identified from the product banner displayed on system
     console. Another way to find out CUCM/UC release is to run platform admin CLI
     command &quot;show version active&quot;.
      
      Hardware model can be identified by running platform admin CLI command 
  &quot;show hardware&quot;.
&lt;br&gt;        
      &lt;B&gt;Workaround:&lt;/B&gt;
   
      If experiencing above problem for specified CUCM/Unity Connection release and hardware 
   models, then apply the following workaround:
  
            1. Boot the system using the recovery disk (version 7.1.2.10000-16 or 
    later)
            2. From the recovery CD menu select option &#39;f&#39; to run file system 
   check
            3. When completed select option &#39;q&#39; to quit recovery CD
            4. eject the CD when prompted and reboot the system
      
      &lt;B&gt;Additional Information:&lt;/B&gt;
     
    ***If you think you are running into this defect, please collect the 
   following:
     
     1) show hardware
     2) active syslog/* files
     3) &quot;utils create report hardware&quot; (DSA)

Any customer that have had the r/o problem on the /common partition and recovered via reboot and/or Recovery CD should consider doing an upgrade to a CUCM or UC version w/ the CSCta73022 fix, then doing a DRS backup, fresh install the same CUCM or UC version, and restore.  Reason being is the /common partition is common to both the inactive and active (upgraded) UCM and as such, will still potentially have broken files and or directories.  The fresh install would remove this possibility.

If the customer doesn&#39;t known which partitions were affected and no record exists, the above procedure should be followed verbatim.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta73022</guid>
</item>
<item>
<title>Continuous start/stop of webapps  leads to permgen memory low , Fixed CSCta20132</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta20132</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Tomcat has run out of Permgen memory. The majority of web services are still available, but some might fail to respond. Example, Extension Mobility logins may be refused.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Multiple manual restarts of large web services like CAR can lead to exhaustion of Java PermGen memory. Specifically activation/deactivation or start/stop of Cisco web services such as CAR through the Serviceability pages.  Estimates for 7.1 releases is in the neighborhood of 40 restarts of CAR.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

To recover:

- Restart Tomcat.
- Inclusion of fix for CSCsy70968 eliminates likelihood of occurence due to DRS backups.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta20132</guid>
</item>
<item>
<title>7828-H3 server goes down with Journal Aborted error , Fixed CSCsv49493</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv49493</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Phone services will go down, and server will only be semi-responsive. Local console access will show the following error constantly scrolling across the screen.
EXT3-fs error (device sd(8,6)) in start_transaction: Journal has aborted
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
During normal operation services will go down. Reboot will bring services back up for a while, anywhere between a couple hours and a couple days. Seen most frequently on
MCS7828-H3-K9/BE but has been reported on MCS7825-H2-IPC1 and MCS7825-H3. This defect is for the MCS7828-H3 servers only.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Shut down the server, and remove the first hard drive until a final fix is available.
If server still fails, try switching to the other drive. Watch during boot up for any errors which might indicate hardware failure (SMART errors in particular).
If server stills fails on 2nd drive, leave one drive in, and reinstall CUCM.
&lt;br&gt;
&lt;B&gt;Further Information&lt;/B&gt;
This issue was tracked to a firmware problem on the hard drives. A firmware update is available on cisco.com. Please download the readme and iso for 7828h3-hddfwupdate-v11 under the MCS 7828-H3 Unified Communications Manager Appliance. 
Direct link:
http://tinyurl.com/mkrbxa 


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv49493</guid>
</item>
<item>
<title>Cluster Manager on subscriber node log info alarm every 3 min , Fixed CSCtc27081</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc27081</link>
<description>
 
  
  
  
  
  
  
  &lt;B&gt;Symptom:&lt;/B&gt;
  
  
  
  
  
  
  
  Following alarm is seen in the CUCM Application Logs CiscoSyslog every 3 min
 on all of the subscriber nodes.
  
  Sep 23 14:59:53 CBNA-CUCM-S11 local7 6 clm: 1354: Sep 23 19:59:53.212 UTC : 
 %CCM_CLUSTERMANAGER-CLUSTERMANAGER-6-CLM_PeerState: Current ClusterMgr session
 state. Node&#39;s Name or IP:CBNA-CUCM-P Node&#39;s State:POLICY_INJECTED App ID:Cisco
 Cluster Manager Cluster ID: Node ID:CBNA-CUCM-S11
&lt;br&gt;  
  &lt;B&gt;Conditions:&lt;/B&gt;
  
  
  
  
  
  Every 3 min all of the subscriber nodes in a CUCM cluster will run a
 connectivity test to the Publisher node via the Cluster Manager service. At the
 end of this test the subscriber nodes logs an Informational alarm unnecessarily
 as there is no change of Policy states. The alarm is informational only and no
 action needs to be taken on it.
&lt;br&gt;  
  &lt;B&gt;Workaround:&lt;/B&gt;
  
 To avoid the excessive alarms and log entries the connectivity test may be
 turned off:
 
 1) obtain a remote account
 2) Stop Cluster Manager from admin CLI:  
         &quot;utils service stop Cluster Manager&quot;
 3) Stop the automated connectivity test using the remote account: 
         &quot;/usr/local/platform/bin/clm/clm_ctl set clm_network_test_timer 0&quot; 
 4) Start Cluster manager from the admin CLI: 
         &quot;utils service start Cluster Manager&quot;
  
This does *NOT* turn off the alarms if the network (pub or sub) goes down.  The
only thing the automated connectivity test does is to scan the network for
possible packet loss to the private ports.  In an established environment that
usually occurs with the introduction of a new firewall into the network.  
&quot;utils network connectivity test&quot; can still be issued manually.  
  
  
  
&lt;br&gt;  
  &lt;B&gt;Further Problem Description:&lt;/B&gt;
  
  
  
  
  
  
  
  
  
  
  
  
  
 
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc27081</guid>
</item>
<item>
<title>LastRedirectDN is incrct after call is transfered to Unity for call park , Fixed CSCtb68182</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb68182</link>
<description>


&lt;B&gt;Symptom:&lt;/B&gt;
Call park or hold fails in &quot;CUEAC - CISCO UNIFIED ENTERPRISE ATTENDANT CONSOLE&quot; when the call is transferred from unity or unity connection.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;


Call park or hold fails in &quot;CUEAC - CISCO UNIFIED ENTERPRISE ATTENDANT CONSOLE&quot; when the call is transfered from unity or unity connection.

Call flow:

User calls from Number &quot;A&quot; to &quot;B&quot; (another user) - unity connection picks up the calls and plays the user greeting - &quot;0&quot; is pressed which is mapped to the call handler - Call handler is set to do a supervise transfer to route point in CUEAC - Call is transferred and Operator picks up the call.
 
Caller (&quot;A&quot;) requests operator to  park the call- Operator parks the call. But
the call is never parked and caller hears the ring ( RNA situation) instead of hold music.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None 
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

As per the logs looks like When the call is offered at park number last redirect party is not the operator number but is the voice mail pilot number  so this breaks the application logic.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb68182</guid>
</item>
<item>
<title>IBM Director Agent reports defunct drive - false RAID alert , Open CSCtb66354</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb66354</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
IBM ServeRAID defunct drive messages seen in system syslog file.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Under normal operations IBM Director Agent reports a drive to be defunct, and logical drive to be offline. A bit later, the IBM Director Agent reports logical drive to be in normal state again. This may be seen intermittent, sometimes a few times a day, sometimes once every week or month.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None as issue is in the IBM driver. Need newer RAID driver to avoid the false alerts.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
This issue is only a cosmetic issue and does not have any impact on the system other than triggering alerts. Note that IBM Director Agent may also see a real drive issue and report that, so it&#39;s recommended to closely monitor the system if you see these messages to make sure both drives in the logical drive is working properly. The normal message usually appears within a few minutes after the incorrectly reported defunct drive message.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb66354</guid>
</item>
<item>
<title>Cisco CallManger and Cisco CTIManager services crash , Fixed CSCso96280</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso96280</link>
<description> &lt;B&gt;Symptom:&lt;/B&gt; UCM (Linux based) CCM / CTI services will restart after 248 day runtime with ccm-SDL trace indicating:
SdlTimer Services - Avoided negative deltaTime:
ExpirationTime: -21474766.-250000, NextPollTime: 21474836.470000,
SleepTime: 61.0
&lt;br&gt;
&lt;B&gt;Condition:&lt;/B&gt; after 248 days of uptime
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
  
Schedule a reboot of affected nodes before 248 days elapse (since last reboot).

 Use CLI &quot;show status&quot; to determine uptime since last reboot

You must reboot the server to restart the timer to 248 days.  CM and CTI service restarts alone will not reset the timer.





</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso96280</guid>
</item>
<item>
<title>BAT Inserts Only First 10 Ports Of VG224 , Fixed CSCtd08748</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd08748</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
While inserting VG224 SCCP, we get the following message after the 10th port :
491 The specified name has invalid characters or is not formatted correctly for this device type.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 7.1.3
Issue not faced in CUCM 7.1.2 and below
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Insert VG224 as MGCP instead of SCCP
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
01. The first 10 ports insert fine
02. Issue from 11th port onwards
03. GW inserts fine when MGCP selected instead of SCCP
04. GW inserts fine on CUCM 7.1.2
05. Issue 100% recreatable in lab on a 7.1.3 box
 
This is what I see in the BPS logs :
2009-11-06 18:10:10,552 DEBUG [Thread-11] common.LogWrapper  - GatewayDBManager::ExecuteInsert|Error code : 491
java.sql.SQLException: 491
 at com.informix.jdbc.IfxSqli.a(IfxSqli.java:3171)
 at com.informix.jdbc.IfxSqli.E(IfxSqli.java:3484)
 at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2328)
 at com.informix.jdbc.IfxSqli.receiveMessage(IfxSqli.java:2244)
 at com.informix.jdbc.IfxSqli.c(IfxSqli.java:1244)
 at com.informix.jdbc.IfxSqli.executeExecute(IfxSqli.java:2170)
 at com.informix.jdbc.IfxSqli.executeExecute(IfxSqli.java:2107)
 at com.informix.jdbc.IfxResultSet.b(IfxResultSet.java:378)
 at com.informix.jdbc.IfxStatement.a(IfxStatement.java:1299)
 at com.informix.jdbc.IfxStatement.executeImpl(IfxStatement.java:1269)
 at com.informix.jdbc.IfxStatement.c(IfxStatement.java:989)
 at com.informix.jdbc.IfxStatement.execute(IfxStatement.java:875)
 at com.cisco.ccm.bps.gateway.InsertGateway.ExecuteInsertList(Unknown Source)
 at com.cisco.ccm.bps.gateway.InsertGateway.fnExecuteSql(Unknown Source)
 at com.cisco.ccm.bps.gateway.InsertGateway.InsertRecords(Unknown Source)
 at com.cisco.ccm.bps.gateway.InsertGateway.insert(Unknown Source)
 at com.cisco.ccm.bps.service.TransactionController.selectTransaction(Unknown Source)
 at com.cisco.ccm.bps.service.ScheduledJobHandler.run(Unknown Source)
Caused by: java.sql.SQLException
 at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:395)
 at com.informix.jdbc.IfxSqli.E(IfxSqli.java:3489)
 ... 16 more
2009-11-06 18:10:10,564 DEBUG [Thread-11] common.LogWrapper  - GatewayDBManager::ExecuteInsert|Exception : java.sql.SQLException: 491
2009-11-06 18:10:10,565 DEBUG [Thread-11] common.LogWrapper  - DBManager::getDBErrorMessage|Query : SELECT name FROM typedberrors WHERE enum =&#39;491&#39;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd08748</guid>
</item>
<item>
<title>CDP.sys causing nonpaged pool memory leak identified by Mdl tag , Fixed CSCsj37081</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj37081</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
 
 After the CCM server has been running without a reboot for several months the
 server will be becoming sluggish and ultimately become unresponsive on the
 network or console causing phones to unregister.  After the server is rebooted
 the following error may be found in the system event log. 
 
 ==========
 Event Type:    Error
 Event Source:    Srv
 Event Category:    None
 Event ID:    2019
 Date:        10/10/2006
 Time:        9:32:21 AM
 User:        N/A
 Computer:    CCM1
 Description:
 The server was unable to allocate from the system nonpaged pool because
 the pool was empty.
 For more information, see Help and Support Center at
 http://go.microsoft.com/fwlink/events.asp. 
 ==========
 
 Note that this system event log error may be triggered by other applications
 than the Cisco CDP Driver running on the CCM server.  CDP.sys was determined to
 be the cause of this particular bug only after months of log gathering and
 analysis by Micro
 @soft.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
ATTENTION:  The initial fix for this defect, CSCsj37081, is incomplete.  The complete requires fix for CSCsk10239.

 
CCM 4.1(3) with any Engineering Special (ES) before 136
CM 4.1(3) with any SR before SR7
CM 4.2(3) with any Engineering Special (ES) before 56 
CM 4.3(1) with any Engineering Special (ES) before 22

 MCS OS version 2000.4.4sr3a
 CDP Protocol Driver version 4.0.0000.0
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 Disable the CDP driver by following the procedure below.
 1) On the CCM server select: Start &gt; Programs &gt; Administrative Tools &gt;
 Computer Management.
 2) In the left pane, expand the tree and click on Device Manager under System
 Tools.
 3) From the main menu, select View &gt; Show hidden devices.
 4) In the right pane, expand Non-Plug and Play Drivers.
 5) Right click on CDP Protocol Driver and select properties.
 6) On the General tab set Device usage to &quot;Do not use this device (disable)&quot;.
 7) You will be prompted to reboot for changes to take affect.
 8. After the server comes back up follow steps 1-4 and you should notice a red
 X beside the CDP Protocol Driver.
 
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj37081</guid>
</item>
<item>
<title>clarify timezones for legacy/non-legacy phone loads , Fixed CSCtc52241</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc52241</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
All phone loads that come with CM 7.1.3 are considered legacy phone loads, but because there is no documentation covering this, it&#39;s assumed that this is talking about really old phone loads.

Traditionally &quot;legacy&quot; phones have referred to:
12SP+ or 30VIP phones
7940/7960 phones
7970 phone loads before 6.0(4).

However in this context &quot;legacy&quot; means any 3rd gen phone version before 9.0(2).  3rd gen phones include:
7911,7941,7942,7961,7962,7970,7971,7906,7945,7965,7975

The following phone models should not be affected:
7905, 7912, 7940, 7960


What happens is when a time zone that doesn&#39;t have the * is configured,phones with firmware version prior to 9.0(2), will use GMT and not what they are configured to use. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM 7.1.3.1000-11
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Have to use a time zone that has a *. Some documentation that discusses the phone load will resolve what is a legacy and non-legacy phone load.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc52241</guid>
</item>
<item>
<title>When dialing the extension you get a blank page for certain users , Fixed CSCtb52252</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb52252</link>
<description>Symptom:

when dialing the extension customer gets a blank page for certain users
&lt;br&gt;
Conditions:

With Extension Mobility
Active Directory
CUCM 7.1(2) and 6.1(4)

The user locale has special characters (like ) in the string &#39;Use Extension Mobility&#39;
&lt;br&gt;
Workaround:
Associate a device with the user.
&lt;br&gt;
Further Problem Description:

In the logs you will find:

2009-07-28 12:35:33,333 DEBUG [http-8443-19] webdialer.WebdialerServlet
- Entering doProcessHTTPRequest()
2009-07-28 12:35:33,337 ERROR [http-8443-19] webdialer.WebdialerServlet
- Exception Caught:java.lang.IllegalArgumentException: Control character

in cookie value, consider BASE64 encoding your value
2009-07-28 12:35:33,337 DEBUG [http-8443-19] webdialer.WebdialerServlet
- WebdialerServlet::doMakeCall():device name=null
2009-07-28 12:35:33,337 DEBUG [http-8443-19] webdialer.WebdialerServlet
- WebdialerServlet::sendToPage():uri/jsp/CallFailed.jsp
HASHTABLE:{PROFILE=com.cisco.ccm.webdialer.UserProfile@6b83f93c,
REASON=2}
2009-07-28 12:35:33,338 DEBUG [http-8443-19] webdialer.WebdialerServlet
- reqURI:/webdialer/Webdialer
2009-07-28 12:35:33,338 DEBUG [http-8443-19] webdialer.WebdialerServlet
- reqURL:https://x.x.x.x:8443/webdialer/Webdialer
2009-07-28 12:35:33,338 DEBUG [http-8443-19] webdialer.WebdialerServlet
- filteredKey:PROFILE
2009-07-28 12:35:33,338 DEBUG [http-8443-19] webdialer.WebdialerServlet
- filteredValue before replacing the control characters with their
escaped equivalents: com.cisco.ccm.webdialer.UserProfile@6b83f93c
2009-07-28 12:35:33,338 DEBUG [http-8443-19] webdialer.WebdialerServlet
- filteredKey:REASON
2009-07-28 12:35:33,339 DEBUG [http-8443-19] webdialer.WebdialerServlet
- filteredValue before replacing the control characters with their
escaped equivalents: 2
2009-07-28 12:35:33,339 DEBUG [http-8443-19] webdialer.WebdialerServlet
- Request:org.apache.catalina.connector.RequestFacade@a657c 
RESPONSE:org.apache.catalina.connector.ResponseFacade@8cdd0cDISPATCHER:o
rg.apache.catalina.core.ApplicationDispatcher@44857
2009-07-28 12:35:33,357 ERROR [http-8443-19] webdialer.WebdialerServlet
- WebdialerImpl::sendToPage() got an exception for:/jsp/CallFailed.jsp
null
2009-07-28 12:35:33,357 DEBUG [http-8443-19] webdialer.WebdialerServlet
- sendToPage() got an exception
java.lang.NullPointerException

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb52252</guid>
</item>
<item>
<title>HardwareFailure alert is raised due to iLO 2 Communications Error , Fixed CSCsl74589</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl74589</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

HardwareFailure alert is raised as a result of the following message seen in the System Event logs (messages)

 On Tue Dec 11 00:46:52 EST 2007 on node 172.18.10.10 , the following HardwareFailure events generated: hwStringMatch - hpasmxld[4500]: Failed GET SENSOR READING, sensor 9  hwStringMatch - hpasmxld[4500]: iLO 2 Communications Error - Attempting synchronization! 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This alert is raised as a result of the following logs

Nov 14 16:16:32 claire daemon 3 hpasmxld[4545]: Failed GET SENSOR READING, sensor 9 
Nov 14 16:16:32 claire daemon 3 hpasmxld[4545]: iLO 2 Communications Error - Attempting synchronization! 
Nov 14 16:17:17 claire daemon 3 hpasmxld[4545]: check_ilo2: Failed to get BMC Device Id! 
Nov 14 16:18:02 claire daemon 3 hpasmxld[4545]: The iLO 2 reset / synchronization process has FAILED!  
Nov 14 16:18:02 claire daemon 3 hpasmxld[4545]: CRITICAL ERROR:  Resetting HP Advanced System Management Stack! 
Nov 14 16:18:02 claire daemon 3 hpasmxld[4545]: The iLO 2 Management Processor is not responding!
Nov 14 16:18:02 claire daemon 3 hpasmxld[4545]:  
Nov 14 16:18:02 claire daemon 3 hpasmxld[4545]: CRITICAL ERROR:  Resetting HP Advanced System Management Stack!

iLO 2 on this server has 1.35 Firmware revision. Initially the above logs were thought to occur due to an iLO firmware issue and this defect updated the iLO firmware to the latest version at the time. However this was not the root cause.

The root cause was later identified as the same root cause that lead to CSCsr23111 - &quot;HP SNMP Agent stops unexpectedly leading to HardwareFailure alert&quot;. The root cause was the fact that HP SNMP agents were unexpectedly stopping without generating a core file. As a defensive mechanism to ensure SNMP agents are maintained and restarted in case they unexpectedly stop a watchdog was implemented via CSCsm98609 - &quot;Platform CLI show environment temperature fails due to missing hpasmd&quot;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None, this particular instance of HardwareFailure Alert doesn&#39;t indicate a critical hardware failure on the system that could impact call processing.

CSCsr23111 addresses the root cause of this defect and is first fixed in CUCM ES version 6.1(2.1108-1)

CSCsm98609 first fixed in ES 6.1(2.1104-1)

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl74589</guid>
</item>
<item>
<title>CUCMBE and standalone,  Edit Cisco Unity User, Server Not Found error , Fixed CSCso43615</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso43615</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Select &quot;Edit Cisco Unity User&quot; from from the Related Links menu on the End User
page or Directory Number page returns &quot;The page cannot be displayed&quot;. 

Sometimes the when you go to End User Page, search for a user and try to edit
the user, you will get a blank page. 
&lt;br&gt;
 &lt;B&gt;Conditions:&lt;/B&gt;
 
Successfully completed &quot;Create Cisco Unity User&quot;
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
Change the hostname to the IP address in the URL

If you are getting a blank page, please go to System -&gt; Application -&gt; and hit
find. Choose the UC and change the hostname from &lt;HOSTNAME&gt; to
&lt;HOSTNAME&gt;.localdomain. This should fix the issue. This may or may not be
traffic affecting.

The workaround solves the issue to only those end users who are linked to the application server with &quot;.localdomain&quot; in its name. If while creating Cisco Unity User for an end user, an application server that does not have &quot;.localdomain&quot; is used, then the issue still exists. Unfortunately, there can only be one Application Server in the system with &quot;.localdomain&quot;. The only way to fix the issue completely is to upgrade.


This issue is completely resolved starting in versions 
006.001(004.1105.001)
006.001(003.3216.001)
&lt;br&gt;
&lt;B&gt;Further Information&lt;/B&gt;
Full fix also requires fix for CSCso58752.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso43615</guid>
</item>
<item>
<title>Unified Reporting showing the Sub not reachable , Fixed CSCsv21137</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv21137</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When running Unified reporting tool in 6.1.2 and specifically the Database summary report it reports one or more of the subs not reachable.

You can confirm subs are indeed reachable with &#39;utils dbreplication status&#39; and seeing all the replicates.  &#39;utils network connectivity&#39; can also confirm connectivity between nodes.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Subs can ping by hostname and confimred all the tables are good and in sync.  Issue occurs with mismatch in case between hostname and database, example: server1 vs. SERVER1.  This defect is triggered by CURT using case sensitive search on hostname.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
set database and platform servername to same case.
&lt;br&gt;
&lt;B&gt;Further Information&lt;/B&gt;

Debugging information if required:
GRT uses an HTTPS query from the publisher to each subscriber in the cluster to retrieve information.  In this case that HTTPS query is failing.  In order to troubleshoot why the HTTPS access is failing:

1. verify web page is working on each subscriber.  point a browser to https://&lt;host&gt;:8443/grt  replacing host with each subscriber CM one at a time.  You should be prompted for authentication.  you will not be able to authenticate as the password is not available.  This will confirm the process on each subscriber is working

2. verify the publisher has https access to each subscriber.  use the CLI command &#39;utils network capture&#39; on the publisher to start a packet capture running collecting all traffic to subscriber IP addresses.  Restrict to port 8443 to reduce traffic.  then attempt to generate GRT.  then review the packet capture.  the contents of the https stream will be encrypted but you can confirm the TCP session is properly established from publisher to each subscriber.  you may also be able to capture the status of the tcp session with the cli command &#39;show ports open regexp 8443&#39;.

3. after that it is up to each subscriber to execute code to collect required information. if that is failing it will appear in the tomcat and grt logs on the local subscriber. 

Acquiring Debug Level Traces from CURT
To enable Debug Level traces from Cisco Unified Reporting Tool aka GRT or CURT:
   1. Login to desired Cisco Unified Call Manager machine through a web browser of your choice.
   2. From the drop down list, left of Navigation on the top right corner of the web page, select Cisco Unified Serviceability and click Go.
   3. On the main menu place your mouse over Trace, and then click on Configuration.
   4. Select the appropriate server and click Go.
   5. Select the System Services service group and click Go.
   6. Select the Cisco Common User Interface service and click Go.
   7. Make sure that the &quot;Trace On&quot; check-box is checked.
   8. Under Trace Filter settings change Debug Trace Level to Debug and click Save.
   9. Now navigate to Cisco Unified Reporting via the top right drop down list on the webpage.
  10. Select the report you wish to acquire traces on and generate the report.

To retrieve the logs:
Method 2 (Requires Real Time Monitoring Tool):

   1. Open RTMT and connect to desired machine.
   2. Check the All Servers check-box or individual ones for Cisco Common User Interface then click Next.
   3. Set appropriate time frame and appropriate directory where you want log files downloaded to.
   4. Click finish. After the tool is finished downloading the files they should be located in the folder selected.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv21137</guid>
</item>
<item>
<title>CDR SSH user incorrect causing wrong file permissions in CUCM (GGSG Req) , Fixed CSCsz99841</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz99841</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Cluster Manager will update ccmservice user SSH security keys whenever a new node is added or removed from the cluster
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CDR Agent cannot send CDR files from sub to pub using sftp.

This is because SFTP is initiating a connection using the user &#39;ccmservice&#39;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

i) Stop CDR Agent service on Call Processing Node

ii) Gain root access via remote access support account. And then
  Copy over the authorized keys in the specific user&#39;s SSH directory:

/home/sftpuser/.ssh/authorized_keys file to
/home/ccmservice/.ssh/authorized_keys

Root CLI command:
cp /home/sftpuser/.ssh/authorized_keys /home/ccmservice/.ssh/authorized_keys

iii) Start CDR Agent service on Call Processing Node.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

This was caused by changes that were made to tighten up file permissions around the CUCM file structure.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz99841</guid>
</item>
<item>
<title>DST: Update CM to Olson version 2009p , Fixed CSCtc85618</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc85618</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
CM needs updated to Olson version 2009p






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
UCM 4.3(2) - 7.1(3)




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
For Argentina (primary TZ currently affected) - place phones into Greenland TZ for the affected period.



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
Updates will be made available shortly for 7.1(3) which has a built in TZ Update feature.  Prior releases do not have this TZ update functionality.














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc85618</guid>
</item>
<item>
<title>Change default value for Disable Non-Registered SCCP Keepalives to False , Fixed CSCsa67496</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa67496</link>
<description>Symptom:
High memory usage by ccm.exe process.
If left alone long enough --- 
Event ID 2109 The server was unable to allocate from the system nonpaged pool
because the pool was empty. 
Event ID 7011 Timeout (30000 milliseconds) waiting for a transaction response
from the Cisco CallManager service. 
Event ID 7031 The Cisco CallManager service terminated unexpectedly.  
It has done this 1 time(s).  
The following corrective action will be taken in 60000 milliseconds: 
Restart the service.
&lt;br&gt;
Conditions:
High number of TCP session to TCP port 2000.  A client initiates the session,
then abandons the session.  The TCP session stays in the ESTABLISHED state on
the server.  &#39;netstat -an&#39; on the server will show the TCP session on the
server.   Netstat shows the session as established even though the client has abandoned the
session.  ccm.exe never closes the session.
&lt;br&gt;
Workaround:
Change the system parameter Disable Non-Registered SCCP Keepalives to False and restart CallManager.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa67496</guid>
</item>
<item>
<title>SLP_srvreg process spikes CallManager CPU , Fixed CSCta21676</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta21676</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

slp_srvreg process consumes 90% of the CPU power.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

During normal operation.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

&quot;utils snmp hardware-agents restart &quot; on the Admin prompt of the CallManager server experiencing the high CPU

Restart Call Manager if it doesn&#39;t help.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta21676</guid>
</item>
<item>
<title>Timezone wrong on 3rd gen phones after upgrade from 5.1.3 to 7.1.3 , Fixed CSCtc81478</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc81478</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

After UCM is upgraded from 5.1.3 to 7.1.3  the 3rd Gen phones will
display incorrect time. They will always show GMT time.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This only happnes if you upgrade directly to 7.1.3 from 5.1.3, the timezone tables are not marked as legacy as they should be

releated to defect CSCtc52241
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

DE will post Workaround via root or you may be able to upgrade to 6.1.3 then 7.1.3
need to confirm that

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc81478</guid>
</item>
<item>
<title>Installing respin on ES should not be allowed , Fixed CSCsr88057</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr88057</link>
<description>

 
 
 
 
 
 
 &lt;B&gt;Symptom:&lt;/B&gt;
 
 CUCM L2 Upgrade fails with message &quot;Internal Error&quot;.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 #1 The active CUCM version is an ES version.  For example, 5.1.3.2105
 #2 The upgrade version is a base version (respin).  For example 5.1.3.4000.
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 You may try one of the following options:
 
 #1 If the previous active version was a base version, try to switch back to
that base version and upgrade to the new base version:
 a) On CLI, type &quot;show version active&quot;.  If the inactive version is a base
version (e.g. 5.1.3.2000), continue to step b, otherwise try option #2.
 b) On CLI, type &quot;utils system switch-version&quot; to switch to the inactive
version.  System will reboot to base version (e.g. 5.1.3.2000)
 c) Upgrade to the new base version (e.g. 5.1.3.4000)
 
 Please note: This option will wipe out any ES fixes.  If this is not the
desired outcome, please use option 2 below.  This could also potentially lose
configuration changes committed since the last upgrade.
 
 #2 Open a TAC case to get the ES (Engineering Special) file based on the new
base version.  For example, ES 5.1.3.4105 (or above).
&lt;br&gt; 
 &lt;B&gt;Further Problem Description:&lt;/B&gt;
 
 Any build number ending with 000 (for example, 5.1.3.2000, 5.1.3.4000, etc.)
is a base version.  A base version may not contain all the ES fixes in the
previous base version.  For example, 5.1.3.4000 may not contain all ES fixes in
5.1.3.2105.
 
 A build number increased in 1000th place is called &quot;respin&quot;.  A respin may
contain security patches (PSIRT fixes) and select critical fixes.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr88057</guid>
</item>
<item>
<title>CUCM 7 restarts B channel of a PRI causing active call to drop ,   CSCsy28403</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy28403</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Active call through MGCP controlled PRI is dropped. Debug of Q931 messages show that CUCM sent RESTART message.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
First seen in CUCM ver 7.0.1.11000-2
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restarting CUCM service is the workaround. 
Resetting gateway does not help clear the issue.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy28403</guid>
</item>
<item>
<title>CUCM CDP driver should be bi-directional receiving info from neighbor , Open CSCsj66908</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj66908</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CM cannot receive CDP information from peer L2 device.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM connected to a device that supports CDP.  CDP information could be used to identify conditions such as speed/duplex mismatch.  Currently CDP on CUCM does not support receiving CDP advertisement, only sending advertisement.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Manually verify peer switch id.  use &#39;show cdp neighbor&#39; on the switch.  Manually verify interface speed and duplex settings.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
This is an enhancement request for the CDP component of the VOS used with Cisco Unified applications.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj66908</guid>
</item>
<item>
<title>7.1.2a subscriber install fails to connect to publisher , Fixed CSCta66767</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta66767</link>
<description>
  
    &lt;B&gt;Symptom:&lt;/B&gt;
    Subscriber fails to connect to publisher during install.
&lt;br&gt;    
    
    &lt;B&gt;Conditions:&lt;/B&gt;
    Defect condition appears when publisher is installed from factory boot
   image with an upgrade to 7.1.2.
   IPM|(CAPTURE) isftp using password failed (12). Trying sftp using keys.
   or
   IPM|(CAPTURE) isftp using password failed (15). Trying sftp using keys.
   can be seen in the install.log of the subscriber affected
 
 OR
 
   Defect condition can also appear when you hit SKIP instead of PROCEED when
 installing a publisher WITH the upgrade during install option - in this
 scenario, the connectivity test to the publisher will fail during the
 installation of the subscriber. In this particular scenario, there is no way to
 check the install log on the subscriber, just check for the conditions
 mentioned in the workaround below - same workaround applies.  You can view the
attached screenshots for more details.
&lt;br&gt;  
    
    &lt;B&gt;Workaround:&lt;/B&gt;
    Contact TAC to perform workaround.
    
    Workaround is as follows:
    
    1) Login to pub w/ remote support account.
    2) cp -p /usr/local/platform/conf/platformConfig.xml
   /partB/usr/local/platform/conf
    3) Continue with the subscriber install.
    
  
  
 
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta66767</guid>
</item>
<item>
<title>RTMT Alert to warn customer of lack of Tracing , Open CSCtc23823</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc23823</link>
<description>ENHACEMENT:
We should have CCM generate an RTMT Alert Automatically continuously when Time period of traces decreases to less than 24hrs (For CCM/CTI SDI/SDL) or when traces are not set to detailed saying &quot;Warning, You do not have enough tracing to be able to identify possible problems&quot;. This would set expectations for the customer before a TAC case is opened and give customers an opportunity to correct it.  


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc23823</guid>
</item>
<item>
<title>publisher NTP down if configured NTP down or unreliable , Fixed CSCsk70971</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk70971</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
The subscriber CUCMs NTP will not sync to the publisher when the external NTP server is unreachable. 

Other symptoms include failing database replication or failure to setup database replication.  
15 minutes clock variation on any replication reset will prevent replication setup.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
The external NTP server configured on the publisher is unreachable and the cluster has been rebooted.  This can also be triggered if there is intermittent connectivity to the publisher.  Fluctuation in round trip time to the publisher can also cause this.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restore connectivity to an external NTP source.  Stabilize IP connectivity between publisher and all subscribers in the cluster.  Stabilize the round trip time between publisher and all subscribers.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk70971</guid>
</item>
<item>
<title>CCM cored when making call while updating call pickup group , Fixed CSCsl01006</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl01006</link>
<description>Symptom:
CCM cored when making call while updating call pickup group. This issue only happened once and isn&#39;t reproducible.
&lt;br&gt;
Condition:
Updating call pickup group and making call immediately
&lt;br&gt;
Workaround:
N/A

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl01006</guid>
</item>
<item>
<title>TCP port 2000 goes to close wait state and phones failover to the backup , Open CSCtd03811</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03811</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;
 Phones fail-over from the node they are registered to the fail-over node. The show network status shows that the port 2000 is in close_wait state. and new tcp connections on port 2000 is rejected.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
&lt;br&gt;


&lt;B&gt;Workaround:&lt;/B&gt;
To restart call manager service.






</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03811</guid>
</item>
<item>
<title>CCM admin user config page blank after syncing user to unity connection ,   CSCsw97577</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw97577</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
When the user is configured on  the call manage with the Device and Primary extension. Synced the user to the Unity connection we see the user configuration page for that user displays blank on the call manager server web interface
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
User should be imported to the Unity connection 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw97577</guid>
</item>
<item>
<title>After CM 4.2.3 ES26, third generation phones update gives CDP warning , Fixed CSCsi52910</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi52910</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;
CM 4.2.3
After applying ES26

update , modification on any Third generation IP Phones , 7941/7961/7970 , From CCM Administration page after updating 4.2.3 ES26  pops up  Error message 

&quot;Cisco Discovery protocol CDP : switch Port: Warning! CDP should only be disabled on the Network Port if the phone is connected to non-switch.
For further details , consult the call Manager Administration guide.
Note If you clicked update just prior to receiving this message, the update operation did not occur.PLease click ok and then click update again to save your changes.&quot;

Click OK

Second time message comes again with same description including VT Advantage .

click OK 


The update does take effect though.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Applied ES26 on Call Manager 4.2.3 . Issue started after applying ES26
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

All IP Phones are connected to Cisco Switches and have CDP  enabled .
It does not matter If the third generation IP Phone is registered or not registered with call Manager.Message pops up on both the cases for all third generation IP Phones.

7940,7960 Phones does not have this problem.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi52910</guid>
</item>
<item>
<title>Inbound H323 call to UCM 7.1.3 gets silence forcaller and then drops , Fixed CSCtc48579</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc48579</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Inbound H.323 call to UCM 7.1.3 gets silence for PSTN caller for 10-15 secs and call drops.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Ver: 7.1.3.10000-11

UCM SDI traces may show:

10/01/2009 21:35:32.628 CCM|ProcessH225Message::decodeUuie ** ERROR  rc=4
D0081S: End of input reached before message was fully decoded; check PDU #5 &#39;H323-UserInformation&#39;

or:
In Failed UUIE:
10/01/2009 21:35:32.628 CCM|Ie - H225UserUserIe -- IEData= 7E 02 01 05 20 80 06 00 08 91....

Length is spanned over 2 bytes
02 01  in Hex [ 201 ] = 513 [ in decimal ]
Since second byte is &quot;01&quot; we , return from the retrieveUuie function.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
If working version of UCM is still in inactive partition switch back to the previous version.  this appeared to work in version 6.1.4.1190-3 but appears broken in 7.1.3.10000-11.

At least one installation had this problem with IOS Versions before 12.4(24)T1 but not on or after that version.  If the H.323 integration is to an IOS gateway consider upgrading to this IOS version.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc48579</guid>
</item>
<item>
<title>Serviceability: Add NIC alert in event of CM vs. switch mismatch , Fixed CSCsd71282</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd71282</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CUCM has speed/duplex with attached switch.  Alarm is only generated on the switch.  No failure is reported on the CM server.  This is true even when both switch and server support CDP.  With fully functional CDP it is possible to detect mismatch.  Currently CM CDP does not support receiving CDP advertisement from switch.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CM connected to Cisco switch.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Manually verify speed and duplex settings or check for errors on switch.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd71282</guid>
</item>
<item>
<title>PMR 71259 dbmon db connections increase due to odbc hang , Fixed CSCsz09666</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz09666</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Number of connections to the database slowly increasing at a rate of roughly 2 connection a minute. Eventually this causes the database to run out of virtual shared memory, causing a database outage on this node.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Network interruption between subscriber and publisher causes subscriber&#39;s dbmon connection cleaner thread to hang.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Manually restart Database Layer Monitor
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Under this condition in the database ccm.log we can see steady climb of Maximum Server Connections. This can be seen with &quot;file view activelog cm/log/informix/ccm.log&quot; or &quot;file tail activelog cm/log/informix/ccm.log&quot; from the CLI

09:24:29  Maximum server connections 129
09:29:29  Checkpoint Completed:  duration was 0 seconds.
09:29:29  Checkpoint loguniq 51, logpos 0xe545018, timestamp: 0x8e110f8

09:29:29  Maximum server connections 139
09:34:29  Checkpoint Completed:  duration was 0 seconds.
09:34:29  Checkpoint loguniq 51, logpos 0xe5da018, timestamp: 0x8e13f55

09:34:29  Maximum server connections 149
09:39:29  Checkpoint Completed:  duration was 0 seconds.

In Dbmon DBL traces unlike normal operations there is no Cleaner thread logs.

admin:file search activelog cm/trace/dbl/sdi/dbmon/dbl*.log Free

Searching path: /var/log/active/cm/trace/dbl/sdi/dbmon/dbl*.log

Search completed

admin:

Normally when Cleaner thread is in operation we should see similar traces to below.

04/14/2009 14:27:58.088 dbl|   DriverManager::FreeConnection() Removing oldest connection [15]|&lt;NID::localhost&gt;&lt;LVL::Detailed&gt;&lt;MASK::0001&gt;


This issue will be somewhat mitigated by
CSCsz09998 DBMON Cleaner Thread needs a watchdog similar to NotifyThread
This causes dbmon to restart by generating a core file.  The core file will cite intentional abort due to cleaner thread hang or due to cleaner thread not running in the last 10 minutes.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz09666</guid>
</item>
<item>
<title>Cannot upgrade from CUCM 5.1.3 to CUCM 7.0.1 , Fixed CSCsl21150</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl21150</link>
<description>
  &lt;B&gt;Symptom:&lt;/B&gt;
 Upgrade from 5.1.3.4111-1 or lower to 7.0.1 fails, giving the following error:

    &#39;The directory was located and searched but no valid options or upgrades 
 were available. Note, a machine cannot be downgraded so option and upgrade 
 files for previous releases were ignored.&#39;
&lt;br&gt;  
  &lt;B&gt;Conditions:&lt;/B&gt;
 Upgrading from 5.1.3.4111-1 or lower to 7.0.1 using an SFTP/FTP server installed on Windows.
&lt;br&gt; 
  &lt;B&gt;Workaround:&lt;/B&gt;
 1. Use an SFTP server installed on UNIX/LINUX.
 
 2.Burn the unzipped directory to a DVD and perform a local DVD upgrade.

 For e.g. for upgrading from a 5.1.3.ES to 7.0.1.ES: 
   a. unzip cisco-ipt-k9-patch7.0.1.11101-1.sgn.zip which will result in a 
      directory &quot;cisco-ipt-k9-patch7.0.1.11101-1&quot;.
   b. Copy this directory in its entirety to the DVD and then from the
      &quot;Software Installation/Upgrade&quot; option, select &quot;DVD/CD&quot; as the source.
 
  &lt;B&gt;Additional Workaround:&lt;/B&gt;
 In the event that neither of the above options is possible, 
 please contact TAC so they can provide you with a patch.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl21150</guid>
</item>
<item>
<title>sysappl mib is not responding , Fixed CSCsh72473</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh72473</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

SNMP MIB SYSAPPL table wont respond on CCM 6.0.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
After installing CCM 6.0 freshly.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

  Contact Cisco TAC for workaround

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh72473</guid>
</item>
<item>
<title>ConfList Softkey does not display members of a MeetMe Conference , Open CSCsa91857</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa91857</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

&quot;ConfList&quot; softkey is not active during MeetMe conference.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

User creates a MeetMe conference.  When attendees start to join, the creator of the MeetMe conference presses the &quot;ConfList&quot; softkey to display attendees.  User will receive the following message on the IP Phone:

&quot;This Key is Not Active&quot;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

User has to create a Ad-Hoc Conference to be able to use the &quot;ConfList&quot; softkey to display a list of conference attendees.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa91857</guid>
</item>
<item>
<title>DRS stuck in CCMDB backup if many CDR files in Preserved folder , Fixed CSCsl16967</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl16967</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Callmanager 5.1.3 is able to backup the components to SFTP server successfully earlier, but as with the system running and the CDR records starting to build up, the backup start to fail at some stage.
&lt;br&gt;
Condition:
huge set of CDR/CMR files may accumulate in Preserve folders (e.g 110,000) caused a big backup.log file exceeded 1 MB(e.g  20MB)

Typical Scneario:
Customer does not want to use CAR but using third party billing server instead and CAR loader is disabled, in callmanager 5.1.3, this  can result in large number of CDR/CMR accumulated in Preserve folder.
&lt;br&gt;
Workaround:

In 5.1.3 and later
Stopping CAR service will not stop accumulating flat CDR Files.

To clean up the CDR files temporarily to that DRS can proceed,

1. stop the CDR Agent service on all servers in the cluster, so no new CDR files will be pushed to the publisher.

2. check to make sure all the files have been pushed to the billing server(s), do the following command 

ls -R /var/log/active/cm/cdr_repository/destination*

to make sure there is no symbolic link in any of the subfolders

3. Stop CDR Repository Manager, CAR Scheduler and CAR Web Service on the publisher

4. remove all the files under /var/log/active/cm/cdr_repository/preserve/&lt;date&gt; that have been accumulated. And remove all the symbolic links under /var/log/active/cm/cdr_repository/car/&lt;date&gt; with the following commands,

rm -rf /var/log/active/cm/cdr_repository/preserve/*
rm -rf /var/log/active/cm/cdr_repository/car/*


5. restart CDR Repository Manager, CAR Scheduler, CAR Web Services on the publisher.

To stop further accumulation of CDR files, start CAR Scheduler service, set the loader to schedule to continuously loading, load CDR only.

1. create a ccmadmin account if not yet in user group management on ccmadmin page
2. log in to CAR, go to System-&gt;Scheduler-&gt;CDR Load,
3. check &quot;Continuous Loading 24/7&quot; and &quot;Load CDR only&quot; boxes
4. click &quot;update&quot;
5. goto System-&gt;Database-&gt;Configure Automatic Database Purge,
6. set both &quot;Min Age of Call Detail Records&quot; and &quot;Max Age of Call Detail Records&#39; to 1
7. click &quot;update&quot;
8. go to Report Config-&gt;Automatic Generation/Alert
9. For each report, select &quot;Disabled&quot; status and click &quot;Update&quot;


Finally, restart CDR Agent service on all the servers.

workaround for DRS :
1. Restart DRS Master Agent and Local Agent.
2. Delete the backup.log from location /common/drf



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl16967</guid>
</item>
<item>
<title>CM6.0:Co-Res:Kernel panic : No init found try passing init , Terminated CSCsh78294</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh78294</link>
<description>


&lt;B&gt;Symptom:

On the console the error keeps coming up frequently which  doens&#39;t allow the customer to login.  

 *EXT3-fs error (device sd(8,6)) in start_transaction : Journal has aborted.*
&lt;br&gt;



&lt;B&gt;Conditions:

MCS 7825 H3 servers running CUCM 5.1 or 6.0 

Server Not respoding due to File System Errors and not accessible via GUI/CLI. 
&lt;br&gt;


&lt;B&gt;Workaround:None. Contact TAC&lt;/B&gt;


Hard reboot to recover the server
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh78294</guid>
</item>
<item>
<title>AD account locked after 1st unsuccessful attempt to log in to CCMuser , Fixed CSCsy95139</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy95139</link>
<description>User account is locked in Active Directory after the 1st unsuccessful attempt to log on to the CCMuser web page. 
CCM is sending 3 bindRequest for the same user in few milliseconds during LDAP authentication for a single attempt

&lt;B&gt;Symptom:&lt;/B&gt;
After a single unsuccessful attempt to log onto the CCMuser webpage, End user &quot;Account is locked out&quot; on Active Directory. 
In the sniffer capture we can see that the CallManager is sending the biungRequest for the same user 3 times for a single attempt. Verified the same in the traces on CM in lab. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Account Lockout Policy in Domain Security Policy has threshold value as 3 
LDAP authentication with Win2003
CM: CUCM 6.1.3.1000-16 (customer use)
CM: CUCM 7.0.2.10000-8
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Customers may change the LDAP server to allow more invalid login attempts to mitigate the effects of this single login failure causing lockout.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy95139</guid>
</item>
<item>
<title>CFwdAll does not work for Secondary lines from Softkey ,   CSCdx37915</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdx37915</link>
<description>CallForwardAll button does not work for secondary line appearances from the phone
&quot;CFwdAll&quot; softkey on a multiline appearance phone. Pressing the secondary line 
appearance button followed by the CFwdAll softkey yields a reorder tone. 
Primary line appearance can be forwarded just fine. Additionally, the secondary 
line appearances can be forwarded by the end user from the ccmuser page.
&lt;br&gt;
Workaround:  Use the ccmuser page for the CFwdAll funtionality.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdx37915</guid>
</item>
<item>
<title>Update HP SAS HDD firmware HP Critical Advisory, c01186030. , Fixed CSCsl04537</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl04537</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
The HP SAS hard drives may randomly become inaccessible during normal operation. When this occurs, the drives will remain inaccessible even after resetting the drives or controller or after rebooting the server.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Will be applicable to 7835H2/45H2 -- these have 72GB 10K SAS Single Port 2.5&quot; disks.
Impacted hard drive models are as specified in customer advisory at http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01186030
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Boot with the latest Cisco Firmware Update CD. This will automatically detect hardware and hard drives, and update the firmware if applicable.

This utility can be found here (registered Cisco.com users only):
http://tools.cisco.com/support/downloads/go/Tree.x?mdfid=279568007&amp;mdfLevel=Model&amp;treeName=Voice+and+Unified+Communications&amp;modelName=Cisco+7845-H1+Media+Convergence+Server&amp;treeMdfId=278875240&amp;hybrid=Y

Please select the applicable server and download the appropriate ISO image, i.e. FWUCD-2.1.1-H.iso

The readme file may be downloaded or found in the root of the CD.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl04537</guid>
</item>
<item>
<title>XSS in ccmuser within phone personal address book , Fixed CSCsy82517</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy82517</link>
<description> 
&lt;B&gt;Symptom:&lt;/B&gt;
User  can enter scripts into CCMUser personal address book
&lt;br&gt; 
&lt;B&gt;Conditions:&lt;/B&gt;

User  must have valid login id/password 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

none

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy82517</guid>
</item>
<item>
<title>Partition change on CTI Port yields CtiLineOpenLineRes Result=0x8ccc0005 , Open CSCtd34220</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd34220</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

IPCC Mobile Agent login may fail with &quot;Timeout limit was exceeded&quot; even though the given LCP/RCP CTI Ports show registered within the CCMAdmin web page.

The following signature may be found the CTI SDL traces.
=====
021262694| 2009/11/13 01:29:48.073| 007| SdlSig-O  | CtiLineOpenLineReq                    | NA RemoteSignal               | CTIRegistrar(7,100,*,*)         | CTIDeviceLineMgr(7,200,18,1)    | (0,0,0,0).0-(*:*)                       | [R:NP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0] mAsyncResponse = 805626 Name=LCP5000F66001 LH=7|375 Line=66001 Partition=PREVIOUS-PARTITION TimeOut=0 FilterBitmap=0x98 Auto Accept Status=0
=====
Note: The Partition value shown in the above signal will indicate the name of the previous partition assigned to the CTI Port line/DN.  And there is never another attempt by the application or CTI Manager to open the line with the newly configured partition.

This results in the following error response.
=====
021262695| 2009/11/13 01:29:48.074| 007| SdlSig-I  | CtiLineOpenLineRes                    | ready                         | CTIDeviceLineMgr(7,200,18,1)    | CTIRegistrar(7,100,45,1)        | (0,0,0,0).0-(*:*)                       | [R:NP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]AsyncResponse=805626 Name=LCP5000F66001 LH=7|375 Result=0x8ccc0005 Auto Accept Status=0
=====

The following two error signals may also be found in the CTI SDL trace.  The second error signal listed below may also be thrown as a system alarm in the CUCM application event log and as a SyslogSeverityMatchFound alert in RTMT with corresponding email notification if email notification is configured.
=====
021262699| 2009/11/13 01:29:48.074| 007| AppError  |                                       |                               | CTIDeviceLineMgr(7,200,18,1)    |                                 |                                         | LineOpen failed.  Removing Lines

021262705| 2009/11/13 01:29:48.102| 001| AlarmErr  |                                       |                               |                                 |                                 |                                         | AlarmClass: CtiManagerAlarmCatalog, AlarmName: kCtiLineOpenFailure, AlarmSeverity: Error AlarmMessage: , AlarmDescription: Unable to open the line, AlarmParameters:  UNKNOWN_PARAMTYPE:CTI Connection Id:1, DeviceName:LCP5000F66001, DirNum:66001, Partition:PREVIOUS-PARTITION, UNKNOWN_PARAMTYPE:Reason .:-1932787707, AppID:Cisco CTIManager, ClusterID:StandAloneCluster, NodeID:taclab9cucm,
=====
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This problem may occur if the partition on the line of a CTI Port (LCP or RCP) is changed to a new value while the CTI Port is currently registered/InService and working problem.  The PG may not receive notification of the partition change.  This may allow the &quot;device&quot; to be in a registered/InService state, but the &quot;line&quot; may be stuck in an &quot;OutOfService&quot; state.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Option 1: Attempt to unassociate and reassociate the affected CTI Port(s) from/to the application user (ex. PGUser)

Option 2: Delete the affected CTI Port(s) completely.  Then re-add the CTI Port(s) and lines.  Then associate the CTI Port(s) to teh application user (ex. PGUser).

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd34220</guid>
</item>
<item>
<title>Incoming call sent to standby SNRD in CUCM , Fixed CSCsy71437</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy71437</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Customer is getting &quot;CallsActive&quot; greater than 30 on E1 PRI Gateways in
RTMT Performance Monitor using Table View. 
Perf Counter from CLI shows bad counters:

admin:show perf query counter &quot;Cisco MGCP PRI Device&quot; CallsActive

 - Perf class Cisco MGCP PRI Device(CallsActive) has values:
    btn_ahukpbxgwa::S1_DS1-0 -&gt; CallsActive                    = 33

show perf query shows 33 CallsActive on a E1PRI that had only 14 calls active.

Counters not resetting RTMT Cisco UCM 6.1.2.1001-4. System has been upgraded to 6.1.2.1001-4 since original problem was discovered.  Issue has happened again where counters do not appear to clear correctly resulting in a 30 channel link being reported as having more calls active when this is not possible. Restarting the CM service resets the counters but eventually they build up again after a few days.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 6.1.2.1000-13 or 6.1.2.1004-1 with MGCP gateways and E1PRIs.  
After a few days of traffic show perf counters and RTMT reports show CallsActive of greater than 30.  If cm service is restarted, counters clear and then build up again after a few days.


This specific issue is triggered by use of Mobility or Single Number Reach.  It is exacerbated by SDL links going out of service.  This may be caused by loss of connectivity between nodes, rebooting servers, or restarting callmanager service.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
If cm service is restarted, counters clear and then build up again after a few days.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
















</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy71437</guid>
</item>
<item>
<title>timer for H225d stuck in shutting_down status needed , Fixed CSCtb09231</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb09231</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

h225d stuck in shutting_down status indefinitely
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

unknown
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

reset the CM node affected
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

there are countless unforeseen permutations in which h225d could be stuck in shutting_down status. 
All of those permutations (reasons) would be in the end invalid, because the process simply should not be stuck in shutting_down for an infinite time, instead a timer should be added to stop the process after an alloted time and perhaps raise and alarm/error when this timer pops. Allowing trace review as opposed to be service disruptive like it is now.
This itself would not get root cause of why it was stuck in shutting_down but instead allow the customer to continue course calls through such GW without disruption (trace analysis would be done to find RCA when possible).......

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb09231</guid>
</item>
<item>
<title>RTMT generates directory connection and replication alarms , Fixed CSCsc85141</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc85141</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

RTMT generates directory replication and connection alerts in a Call Manager cluster when directory replication appears to be functioning normally.

The following RTMT alerts are seen while the directory service is up and running.

[RTMT-ALERT] DirectoryReplicationFailed
Directory replication failed .
Monitored precanned object has value of 0.

[RTMT-ALERT] DirectoryConnectionFailed
Directory connection failed .
Monitored precanned object has value of 0.

No corresponding DC Directory error messages are seen in the Windows Application Event log.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

A Call Manager 4.1(3) cluster running RTMT with more than one subscriber will attempt to test replication status by creating the following object.

&quot;ou=zTestReplStatus--(, ou=CCN, o=cisco.com&quot;

All servers will attempt to create and delete the same object, creating a race condition. RTMT generates alerts regarding the failed replication tests caused by this condition.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

If directory replication is not actually broken then this is only a cosmetic issue.

One possible workaround is to disable RTMT alerts for directory replication and connection errors. This workaround has the limitation of not being notified when actual directory replication errors exist.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc85141</guid>
</item>
<item>
<title>HP SNMP Agent stops unexpectedly leading to HardwareFailure alert , Fixed CSCsr23111</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr23111</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

HardwareFailure alert is raised after detecting the following message in the System Event Logs

On Tue Dec 11 00:46:52 EST 2007 on node 10.1.1.1, the following HardwareFailure events generated: hwStringMatch - hpasmxld[4500]: Failed GET SENSOR READING, sensor 9  hwStringMatch - hpasmxld[4500]: iLO 2 Communications Error - Attempting synchronization!

Upon this alert other functions that depends on the HP SNMP agents stops to work. These include responses to SNMP get requests against the various CPQ MIBs doesn&#39;t return a response. Platform CLI &quot;show environment&quot; gives error.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

HP SNMP agent unexpectedly stops which triggers the above symptoms. Platform CLI command &quot;utils snmp hardware-agents status&quot; command indicates hpasmxld service is stopped.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Restart the platform snmp hardware agents using &quot;utils snmp hardware-agents restart&quot;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr23111</guid>
</item>
<item>
<title>ForwardAll CFA removed from CCMUser page , Fixed CSCsk86705</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk86705</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Call Forward All / Forward All / FwdAll / CFA not available in CCMUser page.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CM 5.1(3) with Enterprise parameter &#39;Show Call Forwarding&#39; Enterprise Parameter set True.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
There were supposed to be 3 options for Enterprise Parameter &#39;Show Call Forwarding&#39; Enterprise:
True, False, Show Only Forward All.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk86705</guid>
</item>
<item>
<title>Phone mask not being used in SIP Diversion Header for CFA calls , Open CSCso92803</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso92803</link>
<description>None







&lt;B&gt;Symptom:&lt;/B&gt;
External phone number mask not being used in sip diversion header for Forwarded calls.





&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CCM version 6.1.1.2501-2

Inbound call on sip trunk.  Only last 4 digits are collected as per sip trunk sonfig since 
internal extensions are 4 digit.

Call is CFA to external PSTN number via same SIP trunk.

Calling party value on the sip trunk is selected as   ORIGINATOR

In the diversion header,  just the 4 digit internal extension of phone is used

This causes the call to be rejected by SIP call agent who does not recognize the internal 
extension (forwarding station).





&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
If we select the calling party value on sip trunk = First redirecting party

Then SIP software doesn&#39;t care about the malformed RDN information and call works



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;















</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso92803</guid>
</item>
<item>
<title>CAR Report is inaccurate when date matches number of calls , Fixed CSCsx94848</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx94848</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CAR Report is inaccurate regarding call classification.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This can occur if there are the same number of a type of call as the date.  For example, if there are 6 internal calls on January 6th then the report for Jan 6th might be inaccurate.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

There is no workaround for this issue.  You can query the CAR DB directly to get accurate data.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx94848</guid>
</item>
<item>
<title>Need the ability to insert a pause in speed dial , Open CSCdp25864</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdp25864</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CUCM dialing to destination that requires pause followed by additional digits.  This may be dialing out and entering a long distance access code or similar.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
Attempting to create a speed dial to reach such a destination.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None.
&lt;br&gt;

&lt;B&gt;Further Problem Description:&lt;/B&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdp25864</guid>
</item>
<item>
<title>CCM core calling out MGCP PRI when receiving empty UserUser IE , Fixed CSCta98856</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta98856</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;

ccm process cores when calling out an MGCP PRI.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM receives an empty UserUser IE from the PSTN
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None...or switch to h323.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta98856</guid>
</item>
<item>
<title>Call not cleared when MWI comes in via SIP notify , Fixed CSCtd02385</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd02385</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Call not cleared when MWI comes in via SIP notify. 
This problem exists when Unity integration is SIP or the new SCCP StationMwiNotificationMessage.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;

MWI comes in via SIP notify, which goes across an ICT. Call across ICT is not torn down after MWI operation is completed.

When CUCM 7.1.2 is integrated with Unity Connection 7.1.2 by Skinny, MWI is notified by a StationMwiNotificationMessage message. A call triggered by the message won&#39;t tear down.
If either version is older than 7.1.2, OffhookWithCpgn is used for MWI notification. As a result, this problem won&#39;t occur.

Upon receiving SsInfoReq, MessageWaitingManager creates a new MessageWaiting instance with message interface type set to ON_NET_CMI. In this case, the MWI Activate APDU sent earlier is received. As a result, CallManager invokes clearCall to send SsClearCallReq to Cc. MessageWaiting rejects sending the SsClearCallReq if the message interface type set to ON_NET_CMI.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd02385</guid>
</item>
<item>
<title>&#39;utils network connectivity&#39; reports false negatives stuck in bad state , Fixed CSCsq34466</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq34466</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 
 &#39;utils network connectivity&#39; reports failure on subscriber server even though
connectivity exists.
 
 The test continues for give false negatives.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 Rebooting the server in the middle of running the command can cause the test
to get stuck in this error state. The network connectivity test is also run
automatically every 3 min in order to proactively test network connectivity
failure events. If the server is rebooted in the middle of the automatic test
it can also cause future tests to get stuck in this error state.

cluster manager logs show connectivity check running continuously:
11/24/2008 10:27:36.003 clm|Connectivity test is Running|
11/24/2008 10:27:36.004 clm|Connectivity test is Running|
11/24/2008 10:33:36.005 clm|Connectivity test is Running|
11/24/2008 10:33:36.005 clm|Connectivity test is Running|
11/24/2008 10:39:36.007 clm|Connectivity test is Running|
11/24/2008 10:39:36.007 clm|Connectivity test is Running|
11/24/2008 10:45:36.001 clm|Connectivity test is Running|
(continues repeating)
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 Cisco TAC can reset the status of this test if it is stuck in this state.
 
 The workaround is the following:
 1) Get a root admin account (remote_account)
 2) Stop the &quot;Cluster Manager&quot; service from the admin cli:
 utils service stop Cluster Manager
 3) Reset test from the root cli:
 Enter: /usr/local/platform/bin/clm/clm_ctl set clm_connectivity_test disable
 Enter: /usr/local/platform/bin/clm/clm_ctl set clm_connectivity_test_results 1
 4) Start the &quot;Cluster Manager&quot; service from the admin cli:
 utils service start Cluster Manager



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq34466</guid>
</item>
<item>
<title>Adobe Reader browser plugin does not work with CiscoTSP installed , Fixed CSCsx60768</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx60768</link>
<description> &lt;B&gt;Symptom:&lt;/B&gt;
Cannot open Adobe Reader web browser plugin.
Plugin exits with error.
&lt;br&gt; 
&lt;B&gt;Conditions:&lt;/B&gt;
Cisco CUCM TSP is installed.
Using browser plugin and not just standalone reader.

Issue tested with Reader version 9.0
&lt;br&gt; 
&lt;B&gt;Workaround:&lt;/B&gt;
Change settings in Adobe Reader preferences:
Unselect the Adobe&gt;Adobe Reader 9&gt;Edit&gt;Preferences&gt;Internet&gt;Display PDF in
browser. 
Unacceptable if you need to use the browser plugin - as this disables it.
&lt;br&gt; 
&lt;B&gt;Further Problem Description:&lt;/B&gt;
CiscoTSP install copies ace.dll and stlport_vc6 into the system32 folder, which
causes an incompatibility between the Cisco version of ace.dll, and the Adobe
version of ace.dll.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx60768</guid>
</item>
<item>
<title>CUCM upgrade fails with message &quot;unable to mount the local file system&quot; , Fixed CSCsm55596</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm55596</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
Upgrading from 5 or 6 to 6.1 version
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Upgrading to 6.x versions.  7.x and above are not affected.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Must obtain a remote account and run the /usr/sbin/updfstab system utility.  Then verify there is a /mnt/cdrom and /etc/fstab contains cdrom.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm55596</guid>
</item>
<item>
<title>MGCP gateway unavailable after sdl linkoos and then link in service , Fixed CSCtb44229</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb44229</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 
 After SDL Link flap, unable to make outbound calls across MCGP gateway using
route list (even though route list shows as registered).
 
 Inbound calls across same gateway work.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 An SDLLinkOOS event is observed.
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 Resetting the route list resolves the issue.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb44229</guid>
</item>
<item>
<title>MaxForwardsToDn leaks causing Forward Loop Detection with Call Forward , Terminated CSCse19548</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse19548</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Call forward fails because the Forward Loop Prevention is falsly triggered due to a leak in the MaxForwardsToDn counter.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Normal(maybe busy or heavy call volume) to a DN
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Restarting CCM will obviously reset the counter, but there is also a way to manually reset the counter as well. 
 
Procedure for resetting the max forwards to DN counter (if supported by version of CCM)
- Go off hook on a phone that is registered to CCM that has the high counter
- enter &quot;**##*30               (enables codes)
- Go off hook again
- enter &quot;**##*35                (clears the max hop counters)


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse19548</guid>
</item>
<item>
<title>Change password doesn&#39;t take effect from Default credential policy page , Fixed CSCsr93148</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr93148</link>
<description>&lt;b&gt;Symptom:&lt;/b&gt; 
User Must Change does not take effect when creating a new user.
&lt;br&gt;
&lt;b&gt;Conditions:&lt;/b&gt; 
User Must Change (at next login) is not taking effect for users created with the default credential setting.
&lt;br&gt;

&lt;b&gt;Workaround:&lt;/b&gt; 
Best way to ensure User Must Change is to create a new credential policy, setting all fields as you want configured.  Then, when adding a user, be sure to use that credential policy for the user.  Note that the current implementation considers the Does Not Expire flag when checking for User Must Change.  If the Does Not Expire flag is &quot;true&quot;, then User Must Change will be ignored.  To ensure User Must Change at next login, be sure to uncheck Does Not Expire box.
&lt;br&gt;
&lt;b&gt;Further Problem  Description:&lt;/b&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr93148</guid>
</item>
<item>
<title>Memory leak causing many processes to be killed by OOM Killer , Fixed CSCsz11007</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz11007</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Many CUCM processes are killed some causing things like Web access and
alerting to be out. This may also impact AMC/RTMT, DRS backups and the ability to collect CDR records.


The OOM Killer reports some stats when it kills processes.  One of the stats seem to point to the depletion of lowmem memory (as shown below):
...
Apr  5 10:46:54 server1 kern 4 kernel: Normal free:3696kB min:3728kB low:7456kB high:11184kB active:204kB inactive:276kB present:901120kB pages_scanned:396 all_unreclaimable? yes
...
Apr  5 10:46:54 server1 kern 4 kernel: Normal: 0*4kB 0*8kB 1*16kB 1*32kB 1*64kB 0*128kB 0*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 3696kB
...
&lt;br&gt;


&lt;B&gt;Conditions:&lt;/B&gt;
Memory leak eventually causes the system OS to start killing processes.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Disabling CSA (&lt;B&gt;utils csa disable&lt;/B&gt;) prevents this problem.
After this problem occurs, rebooting the system will restore the system to operational state.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
A process with a memory leak starts to allocate too much lower memory. In order to protect the operating system kernel, the OS starts to kill processes using lower memory. This will cause various services to fail depending on which ones are killed by the OS.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz11007</guid>
</item>
<item>
<title>CUCM Not clearing Transfer Instance table entry from Transfer Table , Fixed CSCsz89270</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz89270</link>
<description>Symptom:
-----------
CAD/IPCC transfer using CUCM are failing because there is no response from CUCM.
&lt;br&gt;

Condition:
-------------
Observed with QSIG and CUCM: 7.0
&lt;br&gt;
Workaround:
---------------
None. Need to update if something comes up later.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz89270</guid>
</item>
<item>
<title>display isdemo on license page in ccmadmin , Fixed CSCso33442</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso33442</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CallManager service does not start when switch version back to previous version.  Application syslog and CM SDI traces show:

NoFeatureLicense - No feature license found.

AlarmName: NoFeatureLicense,
AlarmSeverity: Error AlarmMessage: , AlarmDescription: No feature
license found.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CM was not fully licensed prior to upgrade.  There are 3 types of licenses required:
1. CM_NODE
2. PHONE_UNIT
3. SW_FEATURE

It appears some licenses are being cut that do not include SW_FEATURE license.  This works fine until system is upgraded.  Upgraded system appears to function properly.  If switch-version back to old version then CM service does not start.

To check for demo licenses from CLI:
&lt;cmd&gt;run sql select * from licenseinfo&lt;/cmd&gt;
look for any row with isdemo=t
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Obtain SW_FEATURE license.  SW_FEATURE license can be uploaded after switch version back to old version.
&lt;br&gt;

&lt;B&gt;Further Problem Description:&lt;/B&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso33442</guid>
</item>
<item>
<title>Update needed for N America DST changes in 2007 , Fixed CSCsf07523</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsf07523</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
On 2006-03-11 02:00a, DST doesn&#39;t take effect on the CCM server
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Cisco Unified CallManager 3.3(5), 4.1(3), 4.2(1), 5.0(4a)
Cisco IPT OS 2000.4.3a and below
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Manually adjust the time on the server.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

rs

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsf07523</guid>
</item>
<item>
<title>Steps for Password recovery for CallManager Admin, OS users , Fixed CSCsq88384</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq88384</link>
<description>&lt;B&gt;Symptoms&lt;/B&gt;

Headlines for &quot;Recovering Administrator and Security Passwords&quot; and &quot;Recovering Administrator Passwords&quot; sections in Cisco Unified Communications Operating System Administration Guide suggest that you can recover passwords. 
&lt;br&gt;
&lt;B&gt;Conditions&lt;/B&gt;

Cisco Unified CM 6.X and 7.0
&lt;br&gt;
&lt;B&gt;Workaround&lt;/B&gt;

Cisco Unified Communications Manager does not support recovery of administration or security passwords. If you lose these passwords, you must reset the passwords.  You can find information on resetting passwords in the Cisco Unified Communications Operating System Administration Guide and in the Release Notes for Cisco Unified Communications Manager.

Tip: The Cisco Unified Communications Operating System Administration Guide calls the section &quot;Recovering the Administrator or Security Passwords,&quot; instead of &quot;Resetting the Administrator or Security Passwords.&quot;  Access the &quot;Recovering the Administrator or Security Passwords&quot; section to reset the passwords.

&lt;B&gt; Further Description &lt;B&gt;

Here is an example of the information that you can find in the Cisco Unified Communications Operating System Administration Guide for 7.0(1).

&quot;If you lose the administrator password or security password, use the following procedure to reset these passwords.

To perform the password recovery process, you must be connected to the system through the system console, that is, you must have a keyboard and monitor connected to the server. You cannot recover a password when connected to the system through a secure shell session.

The security password on all nodes in a cluster must match. Change the security password on all machines, or the cluster nodes will not communicate.

You must reset each server in a cluster after you change its security password. Failure to reboot the servers (nodes) causes system service problems and problems with the Cisco Unified Communications Manager Administration windows on the subscriber servers.

During this procedure, you must remove and then insert a valid CD or DVD in the disk drive to prove that you have physical access to the system.

Procedure

01. Log in to the system with the following username and password:

Username: pwrecovery
Password: pwreset

The Welcome to platform password reset window displays.

02. Press any key to continue.
03. If you have a CD or DVD in the disk drive, remove it now.
04. Press any key to continue.

The system tests to ensure that you have removed the CD or DVD from the disk drive.

05. Insert a valid CD or DVD into the disk drive.

For this test, you must use a data CD, not a music CD. The system tests to ensure that you have inserted the disk.

06. After the system verifies that you have inserted the disk, you get prompted to enter one of the following options to continue:

Enter a to reset the administrator password.
Enter s to reset the security password.
Enter q to quit.

07. Enter a new password of the type that you chose.
08. Reenter the new password.

The password must contain at least 6 characters. The system checks the new password for strength. If the password does not pass the strength check, you get prompted to enter a new password.

09. After the system verifies the strength of the new password, the password gets reset, and you get prompted to press any key to exit the password reset utility.&quot;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq88384</guid>
</item>
<item>
<title>CUCM CDP reports wrong duplex after reboot with Network Failover enabled , Fixed CSCsy08872</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy08872</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Connected switch erroneously reports a duplex mismatch:

Mar 19 15:00:54.073 EST: %CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on FastEthernet0/24 (not half duplex), with cm701.cisco.com bond0 (half duplex).
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Using network failover / NIC teaming on a Cisco Unified Communications Manager 7.x server.
Server has been rebooted (or rebooted after upgrading) since enabling network failover.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Disable CDP on the switch ports the CUCM server is connected to:
     no cdp enable

OR

Do the following workaround on the CUCM server:
This workaround is only effective until the next reboot of the system. It must be applied after every reboot.
**Note that this workaround interrupts network connectivity briefly to the server and will likely be service impacting***

-Disable network failover:
     execute &quot;set network failover dis&quot; from the CLI
-Restart the &quot;Cisco CDP&quot; service:
     Go to Tools -&gt; Control Center - Network Services
     Select the server in question
     Select the radio button next to the &quot;Cisco CDP&quot; service located in the &quot;System Services&quot; section
     Click the &quot;Restart&quot; button
-Enable network failover:
     execute &quot;set network failover ena&quot; from the CLI


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy08872</guid>
</item>
<item>
<title>Device in registered state but not issuing Dial Tone on offhook , Fixed CSCsm55689</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm55689</link>
<description>
 &lt;B&gt;Symptom:&lt;/B&gt;
 
 No dialtone after going offhook on a phone. CallManager doesn&#39;t respond to the Off-hook event or the 
NewCall softkey.
&lt;br&gt;
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 Using phone with Shared lines and multiple nodes in the cluster.
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
Resetting a phone may temporarily recover the problem.
&lt;br&gt; 
 &lt;B&gt;Further Problem Description:&lt;/B&gt;
 
This issue was caused by the fix for CSCsm20067


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm55689</guid>
</item>
<item>
<title>RemoveServerFromDB.bat needs to be provided and correct , Fixed CSCee69769</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCee69769</link>
<description>Symptom:

Documentation on using the RemoveServerFromDB.bat and RemoveSubscription.bat
scripts is incorrect, and these scripts are not provided by default on the
CallManager servers.
&lt;br&gt;
Conditions:

Attempting to remove a subscriber from the network.
&lt;br&gt;
Workaround:

Obtain corrected copies of the RemoveServerFromDB.bat and
RemoveSubscription.bat scripts from Cisco TAC.




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCee69769</guid>
</item>
<item>
<title>CAR reports should write to common partition, active partition full , Fixed CSCsj95433</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj95433</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

RTMT may generate the following alert.
=====
LowActivePartitionAvailableDiskSpace partition has 3 percent of available disk space
=====

Running the following command from a remote access (root) account will show that the reports found in this path are consuming 300+MB of disk space.
=====
du -sh /usr/local/thirdparty/jakarta-tomcat-5.0.28/webapps/carreports/reports/*
=====
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This problem may occur when most or all of the automatically generated reports have been enabled and archived for the longest configurable time.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Contact Cisco TAC who can gain root access to the server and delete the CAR reports which are consuming the disk space to capacity. No folders should be deleted, only report files can be deleted. Otherwise, CAR will get into error.

Unnecessary CAR reports can be disabled for scheduled generation. Log in CAR as CAR administrator, go to Report Config-&gt;Automatic Generation/Alert, for EACH unwanted report select &quot;Disable&quot; status AND Update.

CSCsl16440 addresses the bug where intermediate files are left on the disk when file generation fails, resulting in disk usage accumulation. Customer needs to upgrade to the version that has the fix for CSCsl16440.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj95433</guid>
</item>
<item>
<title>CTI heartbeat timeout; provider closing. , Fixed CSCsl36547</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl36547</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

      Alarm apear on CCM box - %%CCM_CTI-CTI-2-
kCtiProviderCloseHeartbeatTimeout: CTI heartbeat timeout; provider closing
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

      When the Provider is not closed from a client PC before the PC is shutdown
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

      Close the applications before shutting down client PC. 
      On TSP client PC, disable &quot;Remote Access Connection Manager&quot; service as this service opens a provider with CTI and it can not be stopped.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl36547</guid>
</item>
<item>
<title>DRS Direct Backup stuck for freeFTPd server when tar size grow over 1GB. , Terminated CSCsm21349</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm21349</link>
<description>RELEASE NOTE

&lt;B&gt;Symptom:&lt;/B&gt;

When we try to SFTP any file directly to the freeFTPD 1.0.11 SFTP server (taking a backup) we are getting stuck at a stage where the file reached .99 GB size in the SFTP location. It never grows more than 1 GB. The actual data to be backed up is over 20 GB.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;

The folder of more than 1 GB size is tarred (GNU tar 1.13.25) to stdout. An output stream is created using a third party library, between stdout and the SFTP server. The output of the tar command is directed to remote server (freeFTPD). The JDK version used is 1.5.13 (The code is in java.). We are performing here an uploading function.

The file transfer is initiated successfully and the file size in this particular case is more than 1 GB. At the stage when the file size in SFTP server has reached .99 GB, the transfer process is stuck. The file inside the SFTP folder never goes above .99 GB (not size on disk). The whole process works fine when the tarred file size is less than 1GB or the SFTP is a native Linux one or Cygwin or OpenSSH. So basically the SFTP for data greater than 1 GB fails only for freeFTPD server.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
All other FTPD servers other than freeFTPd will work. Cigwin, OpenSSH, native linux SFTP server all can be used instead of freeFTPd as a work around.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

freeFTPd team has informed that this is a known issue.  FreeFTPd/OpenSSHd is no longer developed and is unsupported for DRF backups now.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm21349</guid>
</item>
<item>
<title>Call Forward Policy set to Activating Device/Line CSS from GUI , Open CSCtd23479</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd23479</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Need provision to be able to modify CFA CSS from GUI page
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
When Call Forward Policy set to Activating Device/Line CSS, if Admin through GUI selects forwarding CSS as &#39;None&#39;, that should take effect just as it does when CFA is enabled through phone
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Forward through phone instead of GUI

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd23479</guid>
</item>
<item>
<title>BAT.XLT file does not have option to associate user to device line , Open CSCsu50648</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu50648</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;

Cannot associate user to line of device like IP Phone and CUPC using BAT
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

BAT.XLT file does not have option for end user association with line of devices.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

System administrators have to manually associate the user to line by going into line configuration of each device like IP Phone and CUPC.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu50648</guid>
</item>
<item>
<title>CAR stops loading due to more than max records in less than min days , Fixed CSCsy24114</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy24114</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CAR stops loading new records.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CAR exceeds 2 million records in billing and error tables.  CAR purges to min days but still more than 2 million records remain. CAR cannoot load any more records.

Either need min days to be lower, like hardcoded to 1, or relax rules allowing to purge as necessary for loading independent of min days.

Problem is exacerbated by CM service parameter &lt;b&gt;CDR Log Calls with Zero Duration&lt;/b&gt; set to true.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Change min days to 1.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
This is an enhancement request.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy24114</guid>
</item>
<item>
<title>ccmuser: HTTP 404 error when click on Line Settings/Speed  Dial button , Fixed CSCsr82280</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr82280</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When logging in to the CUCM web admin page you will configure a CUMC device &quot;cumc1&quot; from CCMAdmin and assign the Owner ID and Mobility User ID to &quot;user1&quot;, then login to ccmuser page as user1.
Click on User Options-&gt;Device, then select &quot;cumc1&quot;
Click on &quot;LIne Settings&quot; button, got an error page:

HTTP Status 404 - /ccmuser/no-u/pdate-access.jsp
------------------------------------------------------
type Status report

message /ccmuser/no-u/pdate-access.jsp

-------
This will also happen with other devices configured and may even occur whenever you click on &quot;Device&quot;
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;

Happens only inside the CUCM web user page.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

N/A

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr82280</guid>
</item>
<item>
<title>&quot;User Must Change at Next Login&quot; means user cannot change pwd. , Fixed CSCsl76193</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl76193</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When the credential policy for a user is set to &quot;User Must Change at Next Login&quot; the user must change PIN but then is not able to login  to CCMuser at all.    

 When trying to log into Extension Mobility via the phone, the user is repeatedly prompted for the PIN and receives &quot;[209]-Change PIN&quot;. (this is working as designed)
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Observed with both CUCM 6.0.1.2109-1 and 6.0.1.2104-1.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Do not use the option for &quot;User Must Change at Next Login&quot;.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl76193</guid>
</item>
<item>
<title>BAT uninstall leaves orphaned COM objects , Open CSCsk68493</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk68493</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
CM ES/SR and OS SR Installations exit during StopServices while it is stopping
the COM Objects.  When looking under the Component Services, the BAT and
BATFiles have multiple entries
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 Uninstall of BAT leave orphaned IIS COM objects that need to be deleted.
Reinstallation of BAT creating new entries.
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 To delete the BAT and BATFiles COM objects
 
 1. Go to Start &gt; Programs &gt; Administrative Tools &gt; Component Services
 2. Expand Component Services-&gt;Computers-&gt;My Computer-&gt;COM+ Applications
 3. In the right hand side window you will see IIS com objects for BAT and BATFiles
 4. Right click the object and click on &#39;Properties&#39;
 5. Go to the &#39;Advanced&#39; tab
 6. Under &#39;Permission&#39; uncheck &#39;Disable deletion&#39;
 7. Click on ok
 8. Delete that object.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk68493</guid>
</item>
<item>
<title>With &#39;Disable Speakerphone&#39; checked, call does not terminate when hung , Fixed CSCtc81822</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc81822</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When the &#39;Disable Speakerphone&#39; option is checked on the Phone Configuration page and the call is made, from that phone and when the handset is hung. The call does not terminate. Need to press &#39;End Call&#39; soft key to end it.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This issue is in release 7.1.2.32018-1 and 7.1.2.32017-1 only, due to defect CSCtb70529, as the fix for which broke the functionality.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Press &#39;End Call&#39; soft key to terminate the call.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc81822</guid>
</item>
<item>
<title>Cores:Change password window doesn&#39;t open for Application/End user , Fixed CSCsv21153</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv21153</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When a user enabling &quot;User Must Change at Next Login&quot; attempts to login CUC Admin or CPCA,
HTTP 500 error occurs.

This problem does not occur on Unity Connection 7.0(1).
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Cisco Unity Connection 7.0.2.10000-38 (CUCM 7.0.2.10000-18).
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
No workaround.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv21153</guid>
</item>
<item>
<title>PMR 70525 Service core after rebooting firewall between CUCM nodes , Fixed CSCsr41156</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr41156</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Multiple application/services unexpectedly restart and generate a core after a network outage that interrupts the communication between the Publisher and subscriber nodes. The services that gets impacted could be several. Example services are ccm, CTLProvider, CiscoSyslogSubAgt, dbmon, ipvmsd, RISDC.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

The unexpected restarts occurs after a network outage that could involve firewalls and as a result communication between the Publisher and Subscriber is interrupted. Upon the restoration of the connectivity services could restart and generate a Core file.

This issue is triggered by:
loss of connectivity between CM nodes - this could be due to network instability, network inspection, or network firewall
restart of informix on publisher
reboot of publisher
frequent adjustments of clocks by NTP


&lt;b&gt;utils core analyze&lt;/b&gt; may resemble the following for a core by the ccm process:
  ====================================
 backtrace
 ===================================
 #0  0x00f1ab4e in _OdbcIntType2Definition () from /usr/local/cm/lib/libthcli.so
#1  0x00eeb431 in _OdbcProcessDesc () from /usr/local/cm/lib/libthcli.so
#2  0x00ee9ba1 in _OdbcAsfSendRecv () from /usr/local/cm/lib/libthcli.so
#3  0x00edc407 in _OdbcPrepare () from /usr/local/cm/lib/libthcli.so
#4  0x00ec9e96 in _OdbcPrepareStmt () from /usr/local/cm/lib/libthcli.so
#5  0x00ec2bc0 in _OdbcExecDirect () from /usr/local/cm/lib/libthcli.so
#6  0x00ec2a70 in __SQLExecDirect () from /usr/local/cm/lib/libthcli.so
#7  0x00ec297c in SQLExecDirect () from /usr/local/cm/lib/libthcli.so
#8  0x001d047f in odbc::Statement::execute (this=0xba4086f0, sql=@0x46b2498) at /view/rbeathar-6_x_mainline-raw/vob/ccm_tpl/release/include/stlport/stl/_string.h:1066
#9  0x001d06a0 in odbc::Statement::executeQuery (this=0xba4086f0, sql=@0x46b2498) at statement.cpp:717
#10 0x001531a8 in dbl::Connector::executeQuery (this=0x46b2470, sql=@0x46b2498) at /vob/ccm/Common/Include/DBL2/connector.h:167
#11 0x082eac7d in CFastAccess::ExecuteQuery (this=0x46b2460) at /vob/ccm/Common/Include/DBL2/connector.h:167 

Though the nature of this core means many signatures are possible.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Best mitigation efforts are to:
1. use good NTP sources that are consistent, reliable, and available
2. stabilize network between CM nodes.  Any loss of network connectivity even down to aborted TCP session is detrimental to system behavior.
3. maintain publisher and specifically publisher informix or &quot;A Cisco Db&quot; service uptime as much as possible.

Otherwise no permanent fix exists to avoid unexpected service restarts.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr41156</guid>
</item>
<item>
<title>Transfer failure when operator transfers  caller to ICM  route point , Fixed CSCsj72525</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj72525</link>
<description>None







&lt;B&gt;Symptom:&lt;/B&gt;
Transfer failure experienced by agents when transfering pstn caller to another skillgroup 





&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Callmanager 4.2.3 ES34
ICM 7.0 sr4

PSTN callers are connected to operator and when they try to transfer the caller to another skill 
group by dialing ICM route point, they are unable to complete the transfer successfully.




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Operator should complete the transfer only after they are connected to destination. Supervised 
transfers should not be affected by this defect


&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;















</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj72525</guid>
</item>
<item>
<title>MOH-USB-AUDIO device stops streaming audio on reconnection and reboot , Fixed CSCsk21806</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk21806</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

MOH-USB-AUDIO external sound device for MOH stops streaming audio after configuration,  reconnection and server reboot
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Fresh install of 5.1.3
Configure MOH-USB-Audio for external sound source
Configure Phone to use External sound source. 
External sound MOH does not work on some server models, after configuration.

Reboot server after configuration is done. 
External sound MOH does not work on some server models, after cold reboot. 
External sound MOH does not work on some server models, after unplugging MOH-USB-Audio from USB port and reconnected.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

In some cases Unplugging and reconnecting MOH-USB-Audion from USB port, may fix issue. 
In some cases Rebooting Server may fix issue.
On some server models there is no work around.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk21806</guid>
</item>
<item>
<title>Mobile connect ignores CUCM calling party transformation , Fixed CSCsx01971</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx01971</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CUCM ignores all cucm transformations
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 6.1 SNR
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx01971</guid>
</item>
<item>
<title>Authentication with LDAPS fails due to Failed to connect to LDAP Server , Fixed CSCsr68519</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr68519</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

User authentication on CCMUser pages fail with error &quot;Failed to connect to LDAP Server&quot;. All Enduser authentication requests through the Tomcat web interfaces fail. LDAP directory or authentication configuration changes also fail indicating a null error while attempting to connect to the configured LDAP servers
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Tomcat Security Logs (IMS logs) available under tomcat/logs/security/log4j/security*.log indicates the following error message

2008-07-31 13:58:44,583 ERROR [http-8443-Processor39] impl.AuthenticationLDAP - makeConnection: CommunicationException - javax.naming.CommunicationException: 10.1.1.1:636 [Root exception is java.net.SocketException: Unconnected sockets not implemented]
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Restart Cisco Tomcat services

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr68519</guid>
</item>
<item>
<title>IBM SNMP agent cimserver process has apparent memory leak , Fixed CSCsl71487</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl71487</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
 
RTMT and perfmon counters show the cimserver process to consume increasing amounts of memory on IBM MCS servers.  cimserver gradually consumes the majority of available virtual memory over a period of several weeks and eventually causes the server to hang.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
The cimserver memory leak can only occur on IBM MCS servers.  All existing field cases have occurred on the 7825-I3.  Cisco Dev Eng. and IBM PE team have reproduced the memory leak on other IBM server models.  The likelihood of encountering a cimserver memory leak is fairly slim.

The current field cases have occurred on CUCM versions 5.1.2.3000-2, 5.1.3.1000-12, 6.0.1.1000-37, 6.0.1.2000-3, and 6.0.1.2000-4, and on UC 2.0.  It&#39;s believed the cimserver memory leak can occur on any 5.1+ or 6.x version of CUCM, CUP 1.x-6.x, and UC 2.x.
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
A workaround is implemented with CSCsm71662.  Download cop file ciscocm.CSCsm71662.cimserver.snmp.leak.cop.sgn from cisco.com:

   1. Navigate to Software Search:
       http://www.cisco.com/kobayashi/sw-center/index.shtml

   2. In the search box enter &#39;CSCsm71662&#39;
       The download is presented in the search results.

Next, in the Cisco Unified OS Administration GUI, select Software Upgrades-&gt;Install/Upgrade, Remote Filesystem, enter the directory, remote server of the cop file, a user name and password to the client machine with the cop file, select sftp transfer protocol, and proceed with the upgrade.
&lt;br&gt; 
 &lt;B&gt;Further Problem Description:&lt;/B&gt;

IBM has provided a fix for this memory leak, which has been integrated into CUCM 5.1(3d), 6.1(3), 7.0(1), and will be available in the next ES release of 6.1(1) and 6.1(2) as of June 10, 2008.  Newer releases of CUCM will incorporate this fix.  Upgrades to other CUCM versions from versions for which the cop file was applied, will require that the cop file be re-applied after the upgrade.

The cop file attached to this defect is a workaround that automatically restarts the IBM DIrectory Agent SNMP cimserver process (dacimom) every Sunday at midnight.  It also automatically restarts the dependent net-snmp.org snmpd process.  Restarting these processes results in the recovery of previously used memory back to the OS.

How do I determine whether this issue is affecting my server?

The cimserver memory leak problem can be determined by inspecting Perfmon RIS logs or RTMT.  The Perfmon logs will show cimserver memory use exceeding 350 KB.  RTMT will report an error alert indicating that available virtual memory has fallen below 30% and that cimserver is using the majority of virtual memory.  E.G.,

    &quot;%CCM_RTMT-RTMT-3-RTMT-ERROR-ALERT: This alert is generated by RTMT AlertMgr. Alert Name:LowAvailableVirtualMemory Alert Detail: On Tue Sep 18 03:40:53 MDT 2007 on node edmunity. Available virtual memory below 30 Percent. cimserver (1552 MB) uses most of the memory.&quot;

Monitoring software such as CUOM, IBM Director, or HP Insight Manager may generate an event indicating the cimserver process stopped and subsequently started.  Any such events occuring at midnight Sunday are attributable to the automatic restart set up by this cop file.

Also, please note that CSCta99636 is the defect to track the fix for this issue on MCS-7828 servers.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl71487</guid>
</item>
<item>
<title>Empty String for TSPCall with NULL Pointer as lpsDisplay &amp; 0 as dwSize , Fixed CSCta17894</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta17894</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

Phone default prompts and missed call details are not visible after a display message notification call via CiscoTSP.

Per CiscoTSP API documentation, phoneSetDisplay function call with &quot;NULL Pointer&quot; as lpsDisplay &amp; &quot;0&quot; as dwSize should clear the custom posted phone display message, however with latest TNP devices it is not the case.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

IP Devices 7941/61, 7970/71 etc...




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Reseting the device should help.



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta17894</guid>
</item>
<item>
<title>AAR doesn&#39;t work when called extension has remote destination associated , Open CSCtc97854</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc97854</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

AAR does not work when the called DN has a remote destination associated
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM 6.X and higher
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Calling from PhoneA to PhoneB and there is not enough Bandwidth, 
when AAR is configured the call will be rerouted using the AAR functionality.

If however the called DN has a remote destination associated (Mobile connect) 
and there is not enough bandwidth, AAR will not kick in.
The call to the remote destination will succeed when proper call distribution is setup using Routelist/routegroups and the selected gateway is within either the same location as PhoneA or has a location assigned which has enough bandwidth (taken that we have enough bandwidth for phone&#39;s A location)

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc97854</guid>
</item>
<item>
<title>CCM 5.0.3a CAR 10012 Database error , Fixed CSCse61454</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse61454</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;

trying to generate either the CAR User or Deive Report we get the error message: &quot;10012 Database Error&quot;.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CCM 5.0.3
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

none



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse61454</guid>
</item>
<item>
<title>Due to the extra transfer button press the StationCdpc is not cleaning u , Fixed CSCsu70206</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu70206</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

User cannot receive calls as Busy trigger is hit.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Due to the extra transfer button press the StationCdpc is not cleaning up the LineCdpc process associated with it, so we have a memory leak and we have a situation where all subsequent calls to this directory number will fail.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Reset the IP Phone or restaert callmanager service

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu70206</guid>
</item>
<item>
<title>TFTP subscriber not updated , Fixed CSCtc90948</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc90948</link>
<description>SYMPTOM:
When phone is connected to the network first, it registers and works well. 
However, when deleting the phone from CCMAdmin, the phone is never able
to register back to callmanager when it is added again (autoregistration is
on)
For some reason sometimes the phone tries to register with the old DN.
So even if we manually add the phone back in to CCMAdmin with a different
DN, the phone still tries to register with its old DN and CUCM rejects it.

CONDITIONS:
CUCM 7.1(2)a (PUB + SUB)

TROUBLESHOOTING:
+ Change notification: Comes thRough OK
+ Looks like the problem is on the TFTP side
Publisher TFTP is OK
Subscriber TFTP is not OK
From the logs  I went through the logs. Found that in Scrub() function we are loosing device delete notification on sub. That&#39;s the reason config files obtained from pub and sub is different.

WORKAROUND:
Point phones to use PUB as primary TFTP as PUB has a good copy of TFTP

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc90948</guid>
</item>
<item>
<title>CUCM fails to ACK the 200 OK after blind transfer over SIP trunk , Fixed CSCtb01167</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb01167</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

After blind transferring a call the transfer destination gets one-way voice
and eventually the call disconnects
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This issue is first observed with CUCM 7.1(2) with following topology:

Calling Party A --- SIP trunk --- CUCM/Called Party B --- SIP trunk Transfer destination Party C

A calls B and B blind transfers to C
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Instead of blind transferring the call perform a consult transfer
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Once the transfer is completed and part C answers the call, SDP/media will be re-negotiated.
The final SIP 200 OK from PartyA/SIP trunk will not be ACK&#39;ed by CUCM resulting in observed behaviors

NOTE: 
This will also cause the Calling party name not displayed when the call comes to the final transferred number In this call flow. 







</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb01167</guid>
</item>
<item>
<title>CTI tears down provider, issues CAPF profile, CUEAC doesn&#39;t accept calls , Fixed CSCtd26755</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd26755</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Operator console works for while (anywhere between 2 to 6hrs), and then cannot receive further calls 

=&gt; Restarting the whole CUEAC server fixes the issue temporarily (client restart does not help).
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Software is 
CUEAC 3.0.1.4 
CUCM 7.1(2)_21900-5 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Reboot CUEAC server
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
This should started in sync with when the CUCM cluster was configured for security. Seems like CTI is having issues with CAPF profiles (even after being removed for testing).

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd26755</guid>
</item>
<item>
<title>Phones info exporting  is not working , Fixed CSCsq55185</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq55185</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
The problem is whole phones info not exporting by phone export on Bulk
menu.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Version 6.1.1.2000-3
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
There is no workaround.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
It had been verified by a DE.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq55185</guid>
</item>
<item>
<title>Media Streaming App should have a jitter-buffer and discard dup packets , Open CSCtc20227</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc20227</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Garbled audio when using CUCM Software MTP
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Network configuration issue causing duplicate rtp stream. (i.e Asymmetrical routing in a HSRP environment)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Resolve routing issue, use other MTP resources.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc20227</guid>
</item>
<item>
<title>add ability to collect IBM DSA logs from platform CLI , Fixed CSCsv59702</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv59702</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
For hardware failure IBM service needs DSA report from IBM servers.   Currently there is no way to generate this from platform CLI.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
IBM hardware platform experiencing hardware failures.  For HP platforms the CLI command &lt;b&gt;utils recreate report hardware&lt;/cmdBold&gt; generates inventory for HP service.  This is an enhancement request to have &#39;utils create report hardware&#39; generate DSA report when the platform is IBM.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Obtain a bootable disk from IBM that includes the DSA utility.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
&lt;b&gt;utils create report hardware&lt;/cmdBold&gt; was created for HP platforms as part of CSCsi30296.  This is an enhancement to generate similar report for IBM service.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv59702</guid>
</item>
<item>
<title>Outbound calls fail due to missing dial plan(s) after DRS restore , Fixed CSCsk86351</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk86351</link>
<description>
 &lt;B&gt;Symptom:&lt;/B&gt;
  Nederlands Dial Plan calls stopped working after DRS restore
&lt;br&gt;  
  &lt;B&gt;Conditions:&lt;/B&gt;
  
  Steps followed at customer site:
  
  1. 5.1.2.3000-2 (5.1(2b))
  2. Nederlands Dial Plan installed on all nodes
  3. DRS backup
  4. Reimage
  5. DRS restore on all nodes
  6. reboot cluster
&lt;br&gt;  
  &lt;B&gt;Workaround:&lt;/B&gt;
  
 When doing a restore of a Cisco Unified Communications Manager system where 
a fresh install of the server is done and Restore of DRS is performed the 
following steps must be performed:

	1: Backup cluster
	2: Do fresh install of the server
	3: Install the dial plans required 
	4: Do restore from DRS backup
	5: Restart server.

When doing a restore of Cisco Unified Communications Manager system where a 
fresh install of the server is NOT done and Restore of DRS is performed the 
following steps must be performed. 

	1: Backup the cluster
	2: Do restore from DRS backup
	3: Restart server

Here is a link on how to install Dial plans
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/5_0/idp/dpdep502.htm

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk86351</guid>
</item>
<item>
<title>CSS of phone Device not included for Visual Notification of Call Pickup ,   CSCsz13275</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz13275</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Visual Notification of a call to a phone within a Call Pickup group is not displayed on the screen of phones within that Call Pickup Group but pickup functionality, using the Pickup SoftKey, is working as expected.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
The Calling Search Space of the Line does not include the partition of the Call Pickup Group, but the Calling Search Space of the Device does include that partition.

i.e. The CSS at the Device level is not being taken into account when determining whether to display Visual Notification.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Configure the Calling Search Space of the Line to include the partition of the Pickup Group.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz13275</guid>
</item>
<item>
<title>Enabled Size Safe for Button Templates does not Display All Options , Fixed CSCtc73124</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc73124</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When configuring or updating devices the Administrator does not find all compatible Button Templates in the drop down list. They are unable to find compatible 7970/71 Button Templates for 7975. And cannot find compatible 7975 Button Templates for 7970/71.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Extension Mobility users that log in/out on 7970/71 and 7975 phones.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc73124</guid>
</item>
<item>
<title>ST: careless upgrade too easily triggers db version sync error detection , Fixed CSCsd71588</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd71588</link>
<description>Symptom: CallManager service can not go up after two upgrade.
&lt;br&gt;
Condition: If  a user didn&#39;t reboot a just upgraded server or an upgrade failed and then try a newer version software upgrade,  there is a good opportunity that the DB on this server will get out of sync with publisher.

WORKAROUND

Re-Install (fresh) the subscriber.  This will force it to sync db names with the pub.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd71588</guid>
</item>
<item>
<title>DeviceEventReceiptMonitoringTimer Does Not Get Restarted , Fixed CSCso53416</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso53416</link>
<description>Symptom:
	Lots of UCM trace files written.
	Millions of these events written, per single CIPC:
		CCM|StationInit: (0014350) StationMediaPathEvt.
&lt;br&gt;	
Conditions:
	Normal.
&lt;br&gt;	
Workaround:
	None.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso53416</guid>
</item>
<item>
<title>Dusting no longer work after end the call on RD side, Cdcc Leak , Fixed CSCsx54244</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx54244</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

Can not move (i.e. Dusting) an active call from Remote Destination (such as cell phone or
home phone) to associated enterprise deskphone.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Try to move an active call from Remote Destination to associated enterprise deskphone, but hang up the call from Remote Destination prior to the call being answered from associated enterprise deskphone.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

No workaround.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

N/A


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx54244</guid>
</item>
<item>
<title>MNC/BT device specific change on a SL restarts all shared line devices , Fixed CSCsz14440</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz14440</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

CUCM running 6.1.4, after making to the dn config for a particular skinny phone from cucm admin page, If the same number is shared with lines on multiple devices, then after the change might trigger the device reset of all the devices in the shareline appearance.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
This impacts the devices in a shared line group.  
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
No workaround
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

If user makes changes to the directory number say ring setting from ring only to flash etc., this triggers the auto-reset for all the devices that shares the same directory number.  This causes unnessary reset of all the devices in the shared line group.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz14440</guid>
</item>
<item>
<title>CURT report gives errors when System -&gt; Server entry is FQDN , Open CSCtd26478</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd26478</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Errors seen in Unified Reports, such as the Cluster Overview and Database Status report. The reports aren&#39;t able to find that anything is installed on the nodes or be able to gather any information on the nodes.

Errors are shown in the reports such as &quot;The cucmserver.example.com server is provisioned in the Database but not installed&quot;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Having System -&gt; Server entries as fully-qualified domain names (i.e. &quot;cucmserver.example.com&quot; instead of just &quot;cucmserver&quot; or &quot;10.1.1.1&quot;)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Configure System -&gt; Server entries as IP addresses or hostnames instead of fully-qualified domain names (FQDNs), if possible.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd26478</guid>
</item>
<item>
<title>TAPI user association needs better reliability , Fixed CSCso52736</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso52736</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Users unable to control certain extensions using TSP or jtapi
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
This can occur using TSP or jtapi and CTI call control such as contact center.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Reboot the CUCM server or  restart both CCM and CTIManager services to have the device asscotiation take effect.

There is no known workaround to prevent this happening during runtime.  The recovery once it happens is to reboot as noted above.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso52736</guid>
</item>
<item>
<title>Core dump on Subs on Cisco Unified Auditing Tool (CUAT) , Fixed CSCtc73623</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc73623</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

running Show tech network commands on Cisco Unified Auditing Tool (UCAT) caused two core dumps on subscriber servers. no affecting services.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

on customer cucm 6.1.2 cluster, running CUAT tool got two coredumps.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

no workaround at the moment.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc73623</guid>
</item>
<item>
<title>add service parameter for progress-&gt;disconnect translation , Fixed CSCsb92313</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsb92313</link>
<description>&lt;B&gt;Symptom: &lt;/B&gt;
When using CCM as a gateway between a Qsig network and an ISDN PSTN network callers from the pstn may not hear busy signal when calling a busy subscriber within the qsig network.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
If PSTN does not cut-through until a CONNECT message is received.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
none
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
if a pbx within the qsig network is signaling the busy user via a &quot;progress&quot; message and is supplying local busy tone, the pstn caller will not hear it because the pstn has not cut through yet.

&lt;B&gt;Additional Info:&lt;B&gt;
As part of the fix, a new service parameter was added called &quot;convert Progress to disconnect&quot;;on enabling which the conversion takes place from Progress to Disconnect. But the defect was reopened as the service parameter was not functioning and so there was an additional fix put in Feb&#39;2009 which is required for the service parameter to work.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsb92313</guid>
</item>
<item>
<title>MGCP: Need configurable timer waiting for FXS onhook when call ends , Fixed CSCsc83528</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc83528</link>
<description>Stmptom:
 FXS ports may get reset and unregistered when FAX call ends.
&lt;br&gt;
Condition:
 Cisco CallManager release 4.1(3)
 Any type of Cisco MGCP Voice gateway with FXS port
&lt;br&gt;
Workaround:
 None


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc83528</guid>
</item>
<item>
<title>IBM DA tier1slpinst proc has erroneous LD_LIBRARY_PATH , Fixed CSCsj81116</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj81116</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

Library path of IBM Director Agent was errorneous.  This problem exhibited itself in syslog/messages as invalid pointers in free calls.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Problem was exhibited on IBM servers.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

NA.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj81116</guid>
</item>
<item>
<title>ICT-Based Adhoc Conference Induces Signaling Trombone Effect , Open CSCtc82033</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc82033</link>
<description>Symptom:
	CCM was not processing calls.
&lt;br&gt;	
Conditions:
	Join two adhoc-conference bridges across an ICT.
	Leave the original adhoc conference.
&lt;br&gt;	
Workaround:
	None - restart the CCM service on the affected server.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc82033</guid>
</item>
<item>
<title>CAR Admin Guide should more clearly state who gets what reports mailed , Fixed CSCsz27267</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz27267</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CAR Reports are being mailed to users other than CAR Administrators.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This will occur when &#39;mailing option&#39; is checked on CAR Admin Guide.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

This is expected.   Individuals/end users get the individual bill summary reports, managers get the individual and department bill summary reports, top n reports, and qos summary report, and CAR Admins get all Pregenerated reports that are enabled.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz27267</guid>
</item>
<item>
<title>CCM 6.1.2 crashes due to SsInvokeFeatureReq , Fixed CSCsw27327</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw27327</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CCM 6.1.2.1000-13 Cluster
ccm crashed in Call Control while processing
SsInvokeFeatureReq. Triggered when the signal is sent across nodes in shared line case.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CCM 6.1.2.1000-13
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

&lt;b&gt;utils core analyze &lt;/b&gt; output shows:
====================================
backtrace
===================================
#0  basic_string (this=0x9cddb418, __s=@0x8) at /vob/ccm_tpl/linux/include/stlport/stl/_string.h:390
#1  0x0837569e in _STL::list&lt;_STL::basic_string&lt;char, _STL::char_traits&lt;char&gt;, _STL::allocator&lt;char&gt; &gt;, _STL::allocator&lt;_STL::basic_string&lt;char, _STL::char_traits&lt;char&gt;, _STL::allocator&lt;char&gt; &gt; &gt; &gt;::_M_create_node (this=0x2b07dc0, __x=@0x8) at /usr/include/c++/3.2.3/new:89
#2  0x08375fe2 in _STL::list&lt;_STL::basic_string&lt;char, _STL::char_traits&lt;char&gt;, _STL::allocator&lt;char&gt; &gt;, _STL::allocator&lt;_STL::basic_string&lt;char, _STL::char_traits&lt;char&gt;, _STL::allocator&lt;char&gt; &gt; &gt; &gt;::insert (this=0x2b07dc0, __position={&lt;_STL::_List_iterator_base&gt; = {_M_node = 0x0}, &lt;No data fields&gt;}, __x=@0x8) at /vob/ccm_tpl/linux/include/stlport/stl/_list.h:300
#3  0x08375581 in _STL::list&lt;_STL::basic_string&lt;char, _STL::char_traits&lt;char&gt;, _STL::allocator&lt;char&gt; &gt;, _STL::allocator&lt;_STL::basic_string&lt;char, _STL::char_traits&lt;char&gt;, _STL::allocator&lt;char&gt; &gt; &gt; &gt;::operator= (this=0x2b07dc0, __x=@0x4a) at /vob/ccm_tpl/linux/include/stlport/stl/_list.h:95
#4  0x0836b956 in CcmUrl::operator= (this=0x2b07d54, fCcmUrl=@0xb5e31dc4) at /vob/ccm/Common/Include/Url/CcmUrl.hpp:157
#5  0x084c578b in Cc::wait_SsInvokeFeatureReq (this=0xbe668b78, s=@0xb5e31cd8) at /vob/ccm/Common/Include/CallManager/TDCLCpShares.hpp:5099
#6  0x084e9c1f in Cc::fireSignal (this=0xbe668b78, sdlSignal=@0xb5e31cd8) at /vob/ccm/Common/Include/Sdl/SdlProcessBase.hpp:164
#7  0x09cd31c9 in SdlProcessBase::inputSignal (this=0xbe668b78, rSignal=0xb5e31cd8, traceType=SignalRouterThread, highPriority=0, normalPriority=1, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:370
#8  0x09ce931d in SdlRouter::callProcess (this=0xe3c7330, _sdlSignal=0xb5e31cd8, _deleteSignal=@0x2b0834f, _traceType=SignalRouterThread, _hp=0, _np=1, _lp=0, _vlp=0, _lzp=0, _dbp=0) at SdlRouter.cpp:355
#9  0x09ce8dd8 in SdlRouter::scheduler (sdlRouter=0xe3c7330) at SdlRouter.cpp:265
#10 0x007f065f in ACE_OS_Thread_Adapter::invoke (this=0xeaa5dd8) at OS_Thread_Adapter.cpp:93
#11 0x007f0492 in ace_thread_adapter (args=0x8) at Base_Thread_Adapter.cpp:121
#12 0x006a7dd8 in start_thread () from /lib/tls/libpthread.so.0
#13 0x00296d1a in clone () from /lib/tls/libc.so.6


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw27327</guid>
</item>
<item>
<title>Missing directory caused Install to fail , Fixed CSCsi11993</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi11993</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
Callmanager upgrade failed  because of missing dir.  Log file shows:

manager.OutputRecorder.readNextLine - Next line = [ls:
/common/download/6.0.0.9941-11/Cisco/base_scripts/upgrade_manager.sh: No such
file or directory]
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
3 node cluster.  Pub and two subs.   Upgrade from 6.x version to 6.x version.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Problem is triggered by improper access of the installStatus.do web page.  To
avoid encountering this problem:
Execute the upgrade using the &quot;Reboot&quot; option.
Do not bookmark the URL of &quot;installStatus.do&quot; and refresh during the upgrade.
Access the install status through the os admin menu for Install/Upgrade.
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi11993</guid>
</item>
<item>
<title>Unified OS - Browser hangs trying display certificate with 4096-bit key , Fixed CSCsv32209</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv32209</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 
 Cisco Unified OS Admin web page hangs when attempt to display a certificate
with 4096-bit key is made. (CUCM,Connection and CUP)
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 Cisco Unified OS v6.0(2), v6.0(3), v6.0(4),v7.0.(2),v7.1.(2)
&lt;br&gt; 
 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 Use certificates that are created with 1024-bit key

 &lt;B&gt;Additional Info:&lt;B&gt;

 Once you are in this state, you cannot view any other certs. unless you
restart Tomcat service from CLI:

utils service restart Cisco Tomcat



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv32209</guid>
</item>
<item>
<title>TFTP NAKs Requests After Group Level Changes , Fixed CSCsx73956</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx73956</link>
<description>Symptom:
	TFTP responds to file requests with ERROR 3.
	(Disk Full or Processing Allocation Exceeded)
&lt;br&gt;	
Conditions:
	When a group level change is made when HTTP-based connections (IP Communicators) 
	request invalid files (not present on the server). 
	
	The TFTP service gets into a loop until all HTTP connections go to 0 or they are idle for 
	at least 10 * 10 (100) seconds.
&lt;br&gt;	
Workaround:
	None - restart the TFTP service.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx73956</guid>
</item>
<item>
<title>undesired format for MTP device name in RTMT alert MedialistExhausted , Fixed CSCta05208</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta05208</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 During the load run, in RTMT alert MedialistExhausted, MTP device name is in
undesired format - pkid instead of name.
&lt;br&gt;
 &lt;B&gt;Conditions:&lt;/B&gt;
  Execute loadrun and observe the RTMT alert MedialistExhausted.
&lt;br&gt;
 &lt;B&gt;Workaround:&lt;/B&gt;
 none



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta05208</guid>
</item>
<item>
<title>JTAPI stops distributing events for EM inservice on different partition , Open CSCtd15162</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd15162</link>
<description>Symptom
-----------
Agent logs in at phone1, then logs into phone 2 using the same EM profile, so he&#39;s automatically logged out from phone 2.  After the agent logs in at phone1, CTI/JTAPI sees this temporarily as a shared line, until the logged out occurs.  This appears to cause the in/out-of-service events to be not to be sent.
&lt;br&gt;
Condition
-----------
Unknown
&lt;br&gt;
Workaround
---------------
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd15162</guid>
</item>
<item>
<title>Globalized number does not get localized on transfer destination , Open CSCtd09842</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd09842</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 
 When transferring a call, on the transfer destination the calling number does 
not get localized.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 CUCM version supporting Calling party normalizations (globalization and 
localization of the calling number).
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 None
&lt;br&gt; 
 &lt;B&gt;Further Problem Description:&lt;/B&gt;
 
 Example.
 The system has a calling transformation pattern which transforms &#39;+&#39; to &#39;00&#39;
 and in below example both Phone B and C have it configured
 
 PSTN (CLID : +32XXXXXXXX) -Calls -- Phone B - Phone C
 
 On Phone B we will see 0032XXXXXXXX (local) and as alternate +32XXXXXXXX 
(global)
 When Phone B transfers to Phone C and the transfer is completed 
 Phone C will see +32XXXXXXXX.
 This happens both for blind and consult transfer.
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd09842</guid>
</item>
<item>
<title>Should ignore &quot;Waiting on IPMI initialization&quot; for HardwareFailure alert ,   CSCsr92354</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr92354</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

&quot;Waiting on IPMI Initialization&quot; seen on console after reboot.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This message can occur after a system reboot on the console.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Ignore this message as it is typically harmless.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr92354</guid>
</item>
<item>
<title>configurable CCMAdmin timeout , Open CSCsj45520</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj45520</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Browser session to CCMAdmin times out after 30 minutes and user must re-authenticate.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Browser session to CCMAdmin idle for 30 minutes with CM6.x.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None.  Reauthenticate after 30 minutes of inactivity.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
This is an enhancement request to allow configuration of web session timeout.  Please contact Cisco account team or Cisco Product Manager for status, details, and updates about this enhancement request.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj45520</guid>
</item>
<item>
<title>&quot;utils dbreplication reset all&quot; displays misleading failure message , Fixed CSCso82088</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso82088</link>
<description>
Symptom:

Once database replication is stopped on all the nodes and then if the &#39;utils
dbreplication reset all&#39; command is executed on the Publisher - it fails with
following error:

admin:utils dbreplication reset all
Replication reset is in progress. Replication setup will continue in background.
Please watch RTMT replication state on all nodes. It should go from 0 to 2.
When all subs have an RTMT Replicate State of 2, replication setup is complete.
If RTMT Replicate State shows 4, there is an error in replication setup.
DbMon correctly signalled
command failed -- Enterprise Replication not active  (62)

command failed -- Enterprise Replication not active  (62)

admin:
&lt;br&gt;
 
Workaround:
-----------
None

The replication eventually establishes successfully. Use the following command
to verify the replication status on all nodes in the cluster:

&quot;show perf query class &quot;Number of Replicates Created and State of Replication&quot;

If the Replicate_State counter in the output of above command is 2, then it
means that replication is good.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso82088</guid>
</item>
<item>
<title>&#39;Unified CM Cluster Overview&#39; gives incorrect WAN delay as acceptable , Fixed CSCsr11010</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr11010</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

The &#39;Unified CM Cluster Overview&#39; report from the Cisco Unified Reporting tool
shows as acceptable RoundTripDelay 40msec.
For CUCM 6.1 the acceptable RTT has been increased to 80msec
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM 6.1
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

none
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

For more information on the RTT, please consult the SRND
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/6x/models.html#wp1044078

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr11010</guid>
</item>
<item>
<title>ATA186 currently takes up 2 DLUs, it needs to take up 1 DLU. , Fixed CSCsg70752</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg70752</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

ATA consumes 2 DLUs (Device License Unit) per PORT  to register it to CallManager 5.0,
though Cisco.com says that ATA consumes 2 DLUs per DEVICE.
http://www.cisco.com/application/pdf/en/us/customer/products/ps6164/c2079/cdccont_0900aecd80503151.pdf
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;

There is no workaround.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg70752</guid>
</item>
<item>
<title>Export CDR/CMR not working in CAR , Fixed CSCsb18851</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsb18851</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

The feature CDR/CMR is not working properly. When the data is very less, the systems shows an error : 10011: Error: Contact System Administrator. For large data sometimes the CDR/CMR&#39;s are downloaded properly while at other times it shows 0 KB downloaded.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CM 4.1(3)SR1.

Check the CAR log file C:\CiscoWebs\art\std.err and check for this text:
java.lang.UnsatisfiedLinkError: executeCommand
	at com.cisco.art.general.ServiceControl.executeCommand(Native Method)
	at com.cisco.art.general.ServiceControl.executebcpCommand(ServiceControl.java:62)
	at com.cisco.art.controller.CtrCallDetailExport.exportDump(CtrCallDetailExport.java:321)
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
None
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
The first fix for CSCsa65681 checked into 4.1(3)ES28 was incomplete.  This feature is still broken in 4.1(3)sr2 and 4.1(3)sr3.  The proper fix was integrated in 4.1(3)es47

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsb18851</guid>
</item>
<item>
<title>MOH stops working Intermittently , Fixed CSCsd05660</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd05660</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

MOH stops working Intermittently. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

When the MOH stops workings, users are hearing blank audio. IP Voice Media Streaming is not having the RxStream of the audio source file cause of this CallManager is streaming blank audio.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Reset MOH servers (or) re-adding the audio source file (or) clicking update on the audio source files, resumes MOH stream for couple of days.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd05660</guid>
</item>
<item>
<title>Restore fails when BARS installed as Backup-server on CRS Server , Terminated CSCef31285</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCef31285</link>
<description>Symptom:
Restore of CRS fails.
&lt;br&gt;
Condition:
CRS standalone server is configured as backup server.

WorkAround:
Not a supported configuration. Refer C-comments.
Install backup target on CRS server and restore from CCM server (configured as 
backup server).


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCef31285</guid>
</item>
<item>
<title>Error/status msg indicating mismatched keys in the CSR &amp; identity cert , Fixed CSCtc77187</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc77187</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Following is the error/status message displayed when mismatched keys in the CSR and identity certificate. This happens when the generate  CSR tab is hit more that once. 

The requested command 
[sudo/usr/local/platform/bin/CertMgmt.pydecodeop:importtype:certsunit:tomcatsrc-cert:%2Fusr%2Flocal%2Fplatform%2Fupload%2Fcerts%2F%2Ftomcat.dercert-dir:%2Fusr%2Flocal%2Fplatform%2F.security%2Ftomcat%2Fcertskey-dir:%2Fusr%2Flocal%2Fplatform%2F.security%2Ftomcat%2FkeysrootCA-cert:PENNONI-COLO-PKI-01-CA.pemtrust-dir:%2Fusr%2Flocal%2Fplatform%2F.security%2Ftomcat%2Ftrust-certslogfile:%2Fvar%2Flog%2Factive%2Fplatform%2Flog%2Fcert-mgmt.logresultfile:%2Fvar%2Flog%2Factive%2Fplatform%2Flog%2Fcertde-info.xmldescription:Self-signed+certificate]
could not be executed.
&lt;br&gt;




&lt;B&gt;Conditions:&lt;/B&gt;
This happens when the generate  CSR tab is hit more that once.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Will need to get the CSR signed from the CA and upload certs again



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc77187</guid>
</item>
<item>
<title>CDR Repository Manager stops sending CDR files due to no response , Fixed CSCso76228</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso76228</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Billing server stops receiving CDR/CMR flat files after some time. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Intermittent. Configure billing server with &quot;FTP&quot; connection. 

Note: To confirm this issue, make sure to change the CDR Repository Manager trace level to &quot;DEBUG&quot; first, then reproduce the problem. After that, check the logs to see if the corresponding thread stops after printing out &quot;setupDataPort(): &lt;--&quot;. 

For example: 
...
executeCommand(): FTP command with &lt;CRLF&gt; = [STOR //cdr_CCM-PUB-Cluster_01_200902261835_64931
]
2009-03-13 11:07:08,059 DEBUG [Thread-5] sftpapi.FTPConnection (FTPConnection.java:375) - getServerReply(): &lt;--&gt;
2009-03-13 11:07:08,059 DEBUG [Thread-5] sftpapi.FTPConnection (FTPConnection.java:392) - getFullServerReply(): &lt;--&gt;
2009-03-13 11:07:08,060 DEBUG [Thread-5] sftpapi.FTPConnection (FTPConnection.java:398) - getFullServerReply(): reply=150 Opening data channel.
2009-03-13 11:07:08,060 DEBUG [Thread-5] sftpapi.FTPConnection (FTPConnection.java:379) - getServerReply(): return 150 Opening data channel.
2009-03-13 11:07:08,060 DEBUG [Thread-5] sftpapi.FTPConnection (FTPConnection.java:663) - setupDataPort(): response to command[STOR //cdr_CCM-PUB-Cluster_01_200902261835_64931] = 150
2009-03-13 11:07:08,060 DEBUG [Thread-5] sftpapi.FTPConnection (FTPConnection.java:675) - setupDataPort():return true (isPositivePreliminaryResponse)
2009-03-13 11:07:08,061 DEBUG [Thread-5] sftpapi.FTPConnection (FTPConnection.java:676) - setupDataPort(): &lt;--

(... after the &#39;Thread-5&#39; in this example was simply waiting forever for a response from the FTP server ...) 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Restart CDR Repository Manager (note: problem can potentially come back again), or simply change to use &quot;SFTP&quot; to send CDR files instead. 
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
N/A.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso76228</guid>
</item>
<item>
<title>Receiving encoding exceptions in tomcat log , Fixed CSCsx52934</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx52934</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;
Tomcat Exception appear in the $TOMCAT_HOME/logsCatalina.out log
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
When user access the  CCMAdmin User Configuration or User Group Configuration page.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Does not affect functionality so no work around is needed.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx52934</guid>
</item>
<item>
<title>Subscriber NTP Reference in ntp.conf not updated on Pub Hostname Change , Fixed CSCsy71974</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy71974</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Subscriber&#39;s NTP reference to Publisher on OS Admin page still shows former publisher hostname.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This can occur after changing the Publisher hostname.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Contact TAC to manually fix the ntp.conf file.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy71974</guid>
</item>
<item>
<title>Callmanager does not support multirate bearer cap for speech calls , Fixed CSCsw91440</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw91440</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
Speech only call failes from Tandberg video server  to PSTN.
 





&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Tandberg video server is contected via a gatekeeper controlled trunk to CUCM and its configured for speech only mode. 

Tandberg send the right setup to CUCM :

Transfer Capability: Speech, Transfer Mode: Circuit Mode , Transfer Rate: Multirate. 64 kbps base rate, Rate = 64kbps, = 1 B channels , Layer 1 Protocol: CCITT V.110 and X.30 rate adaptation 

But CUCM change the setup when sending the call to the gateway :

Transfer Capability: Speech, Transfer Mode: Circuit Mode , Transfer Rate: Multirate. 64 kbps base rate, Rate = 0kbps, = 0 B channels , Layer 1 Protocol: 

Gateway rejects the call with :

RELEASE_COMP pd = 8  callref = 0xADF5
Cause i = 0x85E4 - Invalid IE contents




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Configure Tandberg server for auto mode (video/speech) instead.



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;













</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw91440</guid>
</item>
<item>
<title>Need a cop file for 5.1.3e to fix upg rules for L2ing to a 7.1(x) vers , Fixed CSCsy23628</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy23628</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

Cannot upgrade from 5.1.3.x release because system will not see a 7.1(x) upgrade file as a valid upgrade file.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

If attempting to upgrade to 7.1(x)  from one of the following versions:
5.1.3.6000-2
5.1.3.6101-1
5.1.3.6102-1
5.1.3.6103-1

system will not see a 7.1(x) upgrade file as a valid file due to a bug in the upgrade path logic.




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

1.) Upgrade to a 5.1.3 ES greater than or equal to 5.1.3.6104 and then upgrade to desired 7.1(x) release.
or
2.) Upgrade to the 5.1.3.7000 respin when available
or
3.) Upgrade to a 7.0.x release and then upgrade to desired 7.1(x).


&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;













</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy23628</guid>
</item>
<item>
<title>Need to add Russian time zones (with DST) , Fixed CSCsj18634</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj18634</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Cisco Call Manager does not support DST Timezones, used in Russia (except Moscow Timezone, GMT+3)
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

During DST switchover IP Phones, assigned to any timezone but Moscow, do not adjust time.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Manually change timezone for all IP Phones, assigned to non-Moscow time zones. (twice every year).



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj18634</guid>
</item>
<item>
<title>CM 6.1 Webdialer keeps asking for login with Null userid , Fixed CSCsm85167</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm85167</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When a new user created in AD, tries to login to the Web dialer page, A Web dilaer window pops up stating &quot;Authentication failed. Please try again. User ID : null / Password : Blank&quot;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CM 6.x
LDAP Integration
LDAP Authentication
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Type the same user id with which we logged in (step 2) then we can access the normal Web dialer page



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm85167</guid>
</item>
<item>
<title>When using Italian Locales the displayed info of a CFA call is incorrect , Open CSCtd26263</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd26263</link>
<description>

 
 
 
 
 
 
 &lt;B&gt;Symptom:&lt;/B&gt;
 When using Italian Locales the displayed info of a CFA call is 
incorrect &quot;PER&quot; instead of &quot;VIA&quot;
 
 A calls B, B has a call forward all to C.  The display on C shows:
 
 Devia A
 Per B
 per B (incorrect)
 
 The correct translation should be:
 Devia A
 Per B
 via B 
 
 
 
 
 
 
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 
 
 
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 
 
&lt;br&gt; 
 &lt;B&gt;Further Problem Description:&lt;/B&gt;

In English the incorrect display is:

Call from A
to B
to B

Correct display should be:

Call from A
to B
by b


 
 
 
 
 
 
 
 
 
 
 
 
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd26263</guid>
</item>
<item>
<title>CTI Route Points stuck in state=WaitforRegister after ccm.exe crashes , Fixed CSCsk43187</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk43187</link>
<description>None







&lt;B&gt;Symptom:&lt;/B&gt;
CTI route points show registered but when calls are made to these route points you get a busy 
signal






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CM version 4.2.3 ES41
ccm.exe crashes  and route points  do not come back in service.

CTI manager looses SDL link with primary ccm process and then establishes link with backup ccm.
Due to the number of cti devices it goes into throttling state.

Even though all the devices show register, from cti perspective a lot of devices are stuck in 
state=WaitforRegister.



&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Manually unassociate/reassociate the route points with the application user.



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;















</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk43187</guid>
</item>
<item>
<title>Phone Button Template for 7941/7942/7945- show all templates , Fixed CSCsx98267</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx98267</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
The phone button template field displays all the template available.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Go to device-&gt;phone. choose the 7945/7941/7942 phone and now go to the phone config page of 7945/7941/7942 sip/sk. and go to phone button template field , here its list all the models template.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
None



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx98267</guid>
</item>
<item>
<title>MOH file upload fails due to lack of disk space , Fixed CSCsk61129</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk61129</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Upon upgrade to appliance model (CM 5.x, 6.x) users cannot upload large (200MB+) MOH files because of space constraints on active partition. When an upload is attempted users get &#39;insufficient disk space error&#39; 
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
This happens for large MOH files that could be uploaded in CM 4.x but in CM 5.x, 6.x these uploads fail because of disk space constraints on active partitions. MOH files are stored in active partition which has free space ranging between 8% - 2%. This amount of space is not enough for upload of large MOH files.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
At present the only option is to upload a smaller sized MOH file.
Use a third-party utility such as Adobe Audition to &quot;resample&quot; the source file to a lower sample rate such as 16khz which will reduce the size of the source file.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk61129</guid>
</item>
<item>
<title>Restrict SNR calls From Routing to Unsupported Trunks , Open CSCtc91356</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc91356</link>
<description>Symptoms/Issue:
SNR calls routed to MGCP FXO lock-up the port. This defect has been created to enhance the mobility feature to
- either block SNR calls from routing over the unsupported trunks or
- allow graceful handling of the call flow to avoid port lock ups.


FXO Port Status:
The &quot;show voice call summary will show 


mh007ro001#show voice call summary 
PORT           CODEC    VAD VTSP STATE            VPM STATE
============== ======== === ==================== ======================
0/3/2         g711ulaw  n  S_CONNECT             FXOLS_REMOTE_RELEASE     
&lt;br&gt;

Workaround:
Ensure that Rerouting CSS of the Remote Destination Profile do not point to Route Patterns that contain FXO ports (or other unsupported trunks)


The following doc describes the supported SNR trunks:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/mobilapp.html
(See: Guidelines and Restrictions for Unified Mobility)

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc91356</guid>
</item>
<item>
<title>BARS intermittently fails with COM+ error and the process becomes hung , Fixed CSCsa93522</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa93522</link>
<description>
Symptom:
 
 BARS process becomes stuck in progress.  The following events are logged to 
the application event viewer:
 
 4/22/20052:00:35 AMCisco BARS SchedulerNoneNone
1N/AXXXXXThe description for Event ID ( 1 ) in 
Source ( Cisco BARS Scheduler ) cannot be found. The local computer may not 
have the necessary registry information or message DLL files to display 
messages from a remote computer. The following information is part of the 
event: [-2147023170] Automation error
 The remote procedure call failed. .
 
 4/22/20052:00:30 AMCOM+ErrorSVC4097N/A
XXXXXXThe run-time environment has detected an inconsistency in 
its internal state. Please contact Microsoft Product Support Services to 
report this error.  *** Error in __FILE__(926): Application image dump 
failed. C:\WINNT\system32\com\dmp\{B40435C4-79D6-4F02-89C9-2C125A4A631F}
_2005_04_22_02_00_29.dmp
 
 4/22/20052:00:29 AMCOM+ErrorSVC4194N/A
XXXXXXThe system has called a custom component and that component 
has failed and generated an exception. This indicates a problem with the 
custom component. Notify the developer of this component that a failure has 
occurred and provide them with the information below. 
 Component Prog ID: 
 Server Application ID: {B40435C4-79D6-4F02-89C9-2C125A4A631F}
 Server Application Name: BARS
 The serious nature of this error has caused the process to terminate.
 Exception: C0000005
 Address: 0x77FBDB24
 Call Stack: 
 ntdll!RtlMoveMemory + 0x1B
 BARS + 0x56B39
 BARS + 0xE0089
 BARS + 0xDA7D4
 OLEAUT32!DispCallFunc + 0x15D
 MSVBVM60!BASIC_CLASS_Invoke + 0x259
 MSVBVM60!BASIC_CLASS_Invoke + 0x52
 OLEAUT32!UserEXCEPINFO_free_local + 0x57D
  + 0x84188778
&lt;br&gt; 
 Condition:
 
 This has been observed with BARS version 4.0.7
&lt;br&gt; 
 Workaround:
 
 While doing a backup/restore using IP address, a proper mapping between IP 
and DNS (using WINS or lmhosts file) is required to correctly access the 
system. Missing configuration would lead to failures.
 
 Please verify that all the configuration settings(WINS/DNS/lmhosts) are 
correct which could be one reason that you are hitting this issue.
 
 As a workaround, Instead of IP, configure this server (data source server) 
using the server name for backups.
&lt;br&gt;  
 
 Further Description:
Update BARS 4.0(12) or later if the same problem occurs after applying the 
workaround.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa93522</guid>
</item>
<item>
<title>Show Hardware command does not show Serial number of server , Fixed CSCso99275</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso99275</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
&#39;show hardware&#39; from cli and gui does not display serial number of the server
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 6.x and above. Issue does not exist with CUCM 5.x (GUI)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use SNMP to find the serial number from the CLI:
-An SNMP community string (at least readonly) must be configured, if this hasn&#39;t already been done. The following doc discusses configuring a community string:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/service/6_0_1/admin/sasnmpv1.html#wp1063451
In the below example, the community string is &quot;public&quot;.

-Use the following command from the CLI of the server you wish to find the serial number for:

(for HP servers)
utils snmp walk 2c public 127.0.0.1 .1.3.6.1.4.1.232.2.2.2.1.0

(for IBM servers)
utils snmp walk 2c public 127.0.0.1 .1.3.6.1.4.1.2.6.159.1.1.60.1.1.3.6.115.121.115.116.101.109


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso99275</guid>
</item>
<item>
<title>Extraneous SetRTPDTMFPayload console and RTMT errors , Fixed CSCsz79506</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz79506</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

SetRtpDtmfPayload no log event or not MTP/CRA for APP

is seen in the system log at regular intervals.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CCM is issuing a request that is valid for MTP, but the media device receiving this request is not an MTP.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

No workaround.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

This is not call control or performance affecting.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz79506</guid>
</item>
<item>
<title>CUCM incorrectly handles H245 address collision, address comparison , Fixed CSCtb24325</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb24325</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
H.245 negotiation fails to negotiate when facilities with h245address are sent after connect.  The CUCM has the numerically higher IP address than the device it is signaling with, and does not initiate a new connection.  Alternatively, it can have the lower connection and reset a current connection to switch to the higher IP address endpoint&#39;s open port.

This may cause certain features like fax and DTMF to fail, as well as call failure because of H.245 negotiation.

The CUCM algorithm for &quot;numerically higher IP address&quot; is also incorrect, and does not function correctly if both IP addresses are not either above 128 or below 128 in the octets that require comparison.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
This happens with certain CUCM versions when fast start is initiated before connect, and H.245 happens after connect, particularly with Facility messages.  The H.245 collision is timing dependent, and may be an intermittent problem because of this.

This is the part of the H.323 specification that is not correctly implemented:

8.2.3 Snippet:
In the event that both endpoints simultaneously initiate the separate H.245 connection, the endpoint
with the numerically smaller h245Address shall close the TCP connection it opened and use the
connection opened by the other endpoint. For purposes of comparing the numeric values of
h245Address, each octet of the address shall be individually compared beginning with the first
octet of the OCTET STRING and continuing through the OCTET STRING left to right until
unequal numeric octet values are found. Comparison shall first be performed on the network-layer
address element of h245Address and, if found to be equal, then on the transport (port) address
element.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Use SIP when possible.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb24325</guid>
</item>
<item>
<title>Failed to Assign Phone Service via BulkAdmin , Fixed CSCsq10764</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq10764</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Assign Phone Services via BulkAdmin Fails.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Assign Phones services using Bulk
BulkADmin --&gt; Update Phones --&gt; &quot;Assign IP Phone Services&quot; --&gt; &quot;Add all services from this template&quot;

&quot;Edit Phone Services&quot; shows Service &quot;Extension Mobility&quot; is subscribed to the selected template.


Job file shows following Error

SEP001AA1A80A84 Could not position within a file via an index.BAT Exception : 
UpdatePhone::getTeleSubServicesPkids
Result Summary :
UPDATE for 0 PHONES passed.
UPDATE for 1 PHONES failed.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq10764</guid>
</item>
<item>
<title>SMDI Message Corruption , Fixed CSCtb60229</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb60229</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

corrupted SMDI messages appear in CMI service
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM 6.1, high volume of SMDI messages during a failover situation, SMDI messages will show up as corrupted in CMI traces, and not processed properly.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Restart CMI service

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb60229</guid>
</item>
<item>
<title>Unable to Modify Exsisting Route List Names , Fixed CSCsu25397</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu25397</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Once you have created Route List you cannot modify its name
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;

No Special Conditions
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu25397</guid>
</item>
<item>
<title>CN of CSR and CA signed cert is case sensitive. , Fixed CSCsz51678</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz51678</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
CUCM 7.0 will do a case sensitive comparison when comparing a certificate&#39;s subject name to that of a CSR that was generated on CUCM.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
If the hostname is &quot;SERVER&quot;, the CSR will have &quot;SERVER&quot; as the subject CN, and the certificate will have a subject CN of &quot;server&quot;.  This will cause an error and not allow you to upload the certificate since the CSR subject doesn&#39;t match the certificate&#39;s subject due to a case sensitive comparison.




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None





</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz51678</guid>
</item>
<item>
<title>need tracing to track packet in/out in SNMP (individual get/response) , Open CSCtc85547</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc85547</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;

need tracing to track packet in/out in SNMP (individual get/response).
Picture the following:
app 1) sends packet a) doing snmp bulk
app 2) sends packet b) doing snmp get
cucm process and executes only one of them...
there&#39;s not even a way to track from the snmp master agent traces that we received a given packet with a transaction number!!!
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;

all current cucm branches
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

none

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc85547</guid>
</item>
<item>
<title>CUCM cluster clock syncronization drift if Publisher NTP server is down ,   CSCsw14629</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw14629</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

NTP Clock synchronization is off within a cluster. Services such a Database is reporting time is not synchronized.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

When a cluster has external NTP clock configured and that clock source is unavailable for some reason Publisher node will stop synchronizing its clock with the rest of the cluster nodes. This causes all nodes to drift independently of each other. This condition could lead to major DB replication failures that depends on all nodes part of the DB replication network clocks&#39; to be in sync all the time. Other services such as AMC, or RISDC could also be impacted due to the clocks being out of sync.

The following can be seen in the Informix Database logs (ccm.log) indicating the cluster nodes clocks are out of sync.

17:40:48  CDR NIF site: 9 &lt;g_bdc_tftp_02_ccm6_1_3_1000_9&gt; clocks differ by 17 seconds
17:40:48  Warning - The operating system time of day clock at the
           remote site differs from the local site. This can
           slow down the data-sync apply performace at the
           target server. This happens only if timestamp or 
           stored procedure conflict resolution rules are
           being used.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

No way to keep the cluster&#39;s clock in sync when the Publisher node can not reach the external NTP clock source. You can how ever disable NTP synchronization to an external source that way at least the cluster&#39;s clock can stay in sync.



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw14629</guid>
</item>
<item>
<title>Virtual Directory shutdown generates IIS log app event warning , Terminated CSCeb80203</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCeb80203</link>
<description>Symptom:

The following warning is observed repeated in the Application Log in the 
Event Viewer:

Event Type:	Warning
Event Source:	Active Server Pages
Event Category:	None
Event ID:	9
Date:		6/25/2003
Time:		12:49:42 PM
User:		N/A
Computer:	CM-PUBLISHER
Description:
Warning: IIS log failed to write entry,   Script timed out. The maximum amount 
of time for a script to execute was exceeded. You can change this limit by 
specifying a new value for the property Server.ScriptTimeout or by changing the 
value in the IIS administration tools.. 
For additional information specific to this message please visit the Microsoft 
Online Support site located at: http://www.microsoft.com/contentredirect.asp.


This warning is followed by the following information message:

Event Type:	Information
Event Source:	Active Server Pages
Event Category:	None
Event ID:	4
Date:		6/25/2003
Time:		12:49:44 PM
User:		N/A
Computer:	CM-PUBLISHER
Description:
Service stopped. 
&lt;br&gt;


Conditions:

This appears 20-21 minutes after the last access to a web page.
&lt;br&gt;

Workaround:

There is no known workaround. However, is no noticible impact other than the
presence of this warning in the App Log.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCeb80203</guid>
</item>
<item>
<title>Redialing does not work with calledPartyTransformation on gateway , Fixed CSCtc98136</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc98136</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When a call is placed to the PSTN everything is working fine with overlap digits.  
The issue is when they press redial, as only first 5 digits of the called number are used and the call fails because the number is incomplete.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 7.1.3:
following call routing to the PSTN:

Translation-Pattern 
Pattern: 00.[1-9]!
Urgent Priority
PreDot
Prefix Digits (Outgoing Calls) +49
---------------------
Route-Pattern
\+49XXXX
with Overlap Sending
---------------------

MGCP Gateway
Called Party Transformation-Pattern 
\+49.XX!
Predot 
Prefix Digit 0
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
The workaround is not to use translation pattern   , but to configure the translation-pattern as route-pattern.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc98136</guid>
</item>
<item>
<title>CM6.0:Mobility:One Way audio for Calls resumed on Desk IP Phone , Fixed CSCsh88353</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh88353</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

One-Way audio for mobile calls when resumed on Desk IP Phone. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
PSTN (MGCP PRI gateway) --&gt; Callmanager 4.X --&gt; Gatekeeper --&gt; Callmanager 6.0 --&gt; IPPhone. 

One way audio is encountered in the above setup for mobile calls resumed on IP Phone.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh88353</guid>
</item>
<item>
<title>LDAP Authentication configuration for CUCMBE needs to always point to GC , Open CSCtd14205</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd14205</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

In a CUCMBE configuration with LDAP Authentication configured to Microsoft Active Directory, Unity Connection IMAP connections can result in high CPU for IMAP service, or Core dumps of IMAP service in Unity Connection.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCMBE versions 7.1.2 and 7.1.3 where CM LDAP authentication is not pointed to a Global catalog/GC port in an Active Directory environment. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Change the CM LDAP Authentication LDAP server information to point to a Global Catalog server, and a GC port
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Currently the documentation only indicates to use a GC port if a Global Catalog server is defined in the LDAP server information, otherwise use port 389 for the server defined.
According to the Unity Connection BU, for Active Directory LDAP implementations, this setting must be a Global catalog server using a GC port, as if not, it can lead to issues with the IMAP service on UC. We need the documentation changed to reflect this requirement explicitly.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd14205</guid>
</item>
<item>
<title>Platform CLI show environment temperature fails due to missing hpasmd , Fixed CSCsm98609</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm98609</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
&lt;b&gt;show environment&lt;/b&gt; command gives the following error

admin:show environment fans 
Internal CLI error detected, please try again.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This error occurs when of one of the necessary platform agents is not running. Running &lt;b&gt;utils snmp hardware-agents status&lt;/b&gt; could indicate if the following is seen 

 hpasmxld is stopped...[  OK  ]

Then the error occurs
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Restart the platform snmp hardware agents and try the command again. use &lt;b&gt;utils snmp hardware-agents restart&lt;/b&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm98609</guid>
</item>
<item>
<title>evaluate increase the number of threads available for snmp master agent , Open CSCtc85744</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc85744</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

Request to evaluate increase the number of threads available for snmp master agent
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

all current cucm branches
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

none, if you exceed the 10 (currently allowed) threads in snmp master agent it will choke and stop processing requests...

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc85744</guid>
</item>
<item>
<title>AC Client freeze during Call Volume Race Conditions , Fixed CSCsk02272</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk02272</link>
<description>Symptom:
------------
Under heavy call conditions AC Client has a phantom stuck call
and also AC Client freezes.
&lt;br&gt;
Conditions:
------------
Mostly observed under Call Volume periods.
CM 5.1.2.
&lt;br&gt;
Workaround:
---------------
No known workaround. Restarting  TCD Service should clear the phantom call
and unfreeze the AC client.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk02272</guid>
</item>
<item>
<title>Not enough traces to figure out the problem , Open CSCtc95471</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc95471</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Not enough traces to figure out the problem
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM 7.1.2.21900-5

Older phone load device gets reject when trying to register.
Add phone to CUCM admin page.
When phone is plugged in, it tries to retrieve old phone load version but gets rejected.

Not enough traces to figure out the problem
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc95471</guid>
</item>
<item>
<title>Call Manager does not support MCID on STCAPP Analog Device , Open CSCtc56549</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc56549</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Call Manager Controlled STCAPP FXS Port support MCID softkey event and can be triggered by pressing &quot;***&quot; on ANL Phone Keypad. However, Call Manager reject the MCID softkey event that send by ANL device with err &quot;&#39;That key is not active here&#39;&quot;.  In addition, we could not configure any customized softkey template with &quot;MCID&quot; softkey for ANL Device.

Thus, There is no way to mark the incoming call to CCM controlled ANL device as malicious call, even though the Stcapp Device support MCID FAC. 

Reference:
http://www.cisco.com/en/US/docs/ios/voice/fxs/configuration/guide/fxssccpsplmft.html
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
Call Manager Controlled SCCP FXS device 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
NO


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc56549</guid>
</item>
<item>
<title>Error observed in  CCM dmin page while accessing through IE7. ,   CSCsk61648</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk61648</link>
<description>Description:

Symptom:
There is an error in the CCMAdmin page through IE7
&lt;br&gt;
Condition:
1.Use XP with IE7 or VISTA as iclient machine.
2.Open CCMadmin page from the client machine.
3.Hit to continue to this website(not recommended) button.
4.Now CCMAdmin page will  come up.
5.In this Admin page please there is a &#39;&#39;cerificate error&#39;&#39; observed .
6.Click on  the cerificate error.It will through an error as&#39;&#39; invalid certificate&#39;&#39; .

Error:Certificate invalid   
&lt;br&gt;

Workaround:
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk61648</guid>
</item>
<item>
<title>Upgrading to 7.1.x from 7.0(2a)SU1 , Fixed CSCtc98999</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc98999</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

upgrade to any CUCM 7.1.x version from  7.0(2a)SU1  is  supported , but is not documented in the compatability matrix 

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr.html#wp43011
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

upgrade to any CUCM 7.1.x version from  7.0(2a)SU1  
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

The upgrade paths for 7.0(2a)SU1 should be the same as for 7.0(2a). 7.0(2a)su2 is also missing, as is 6.1(4a) from several spots, and 7.1(2a)su1 and need to address this in the next documentation release 


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc98999</guid>
</item>
<item>
<title>External Phone Number Mask Applied to finalcalledparty in Hunt-List CDR , Open CSCsm42428</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm42428</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

The &quot;finalcalledparty&quot; field in the calldetail record found on a Cisco Unified Communications Manager server is populated with the value of an external phone number mask after a call is placed to a hunt list.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This will occur if the &quot;Show Line Group Member DN in finalCalledPartyNumber&quot;  is set to true and a calls is made to a hunt list.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Remove the external mask from the DN in the hunt list.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm42428</guid>
</item>
<item>
<title>UCM Features and service guide does&#39;nt list CIPC as suported Phone , Open CSCtc89273</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc89273</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

UCM Features and service guide does&#39;nt list CIPC as suported Phone
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CIPC 7.03 with UCM 7.X
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

In the UCM  7.12 Feature and services guide in Cisco Unified Mobility Chapter under Section System Requirement,  it says

Mobile Connect and Mobile Voice Access work with Cisco Unified IP Phones 7906, 7911, 7941/61, 7962/42, 7970/71, 7975 that are running SIP or SCCP.

CIPC 7.03  supports Mobile Connect  and it is not listed



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc89273</guid>
</item>
<item>
<title>Request for CUCM 6 Corporate directory to display names First name first , Open CSCtd00651</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd00651</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;

Corporate directory in CUCM will only list and sort names in a last name basis.
Wish to implement an option to choose listing order.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Regular use
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Not applicable


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd00651</guid>
</item>
<item>
<title>Job Status shows as InComplete in Job Scheduler page , Fixed CSCsz79330</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz79330</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Job Status shows as InComplete in Job Scheduler page
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

1. Goto Bulk Administration -&gt; Phones -&gt; Update Lines  page
and Perform a query based on Unassigned DN.
2. Select the DN and select the fields that need to be modified using the check box in front of the field and give the required values for the fields. Give the description for the job and submit the job.

Expected behavior: BAT should perform the above task successfully.

Observed behavior: The Job Status is showing as InComplete in Job Scheduler page.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

None.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz79330</guid>
</item>
<item>
<title>Callmanagers do not have all timezones included in Date/Time Group , Fixed CSCsc14339</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc14339</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
User cannot add or select certain time zones in Cisco Callmanager Date/Time Group. The time zones are not listed and do not observe the same times as any other timezones. For example,  Santiago, Chile
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
These other time zones are not included in 3.3, 4.0 or 4.1.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Choose a different timezone that will correspond to the correct time (will need to be changed twice a year if daylight savings time is observed)

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc14339</guid>
</item>
<item>
<title>MOH is not played for a parked Call on a IP Phone. , Fixed CSCsc85660</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc85660</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

MOH is not played for a parked Call on a IP Phone. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CCM 4.1(3) with Phone Load 7.2(3.2)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc85660</guid>
</item>
<item>
<title>Cannot generate CAR reports - getting db errors returned in the message , Fixed CSCsm01916</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm01916</link>
<description>







&lt;B&gt;Symptom:&lt;/B&gt;

In CAR logs, see the following error:

Caused by: java.sql.SQLException: INFORMIXSERVER does not match either 
DBSERVERNAME or DBSERVERALIASES.
        at com.informix.jdbc.IfxSqliConnect.&lt;init&gt;(IfxSqliConnect.java:971)
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;




&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;

Need root access to implement workaround.

1. Backup existing prefs.xml file in /usr/local/cm/conf/dbl directory on CCM 
server.

2. Manually update the prefs.xml in /usr/local/cm/conf/dbl directory on CCM 
server. Change the informix server value for the jdbcurl_car entry to match 
that of the informix server value listed in jdbcurl entry. Save the changes 
and exit.

3. Restart CAR Web Service and CAR Scheduler service.
&lt;br&gt;

&lt;B&gt;Further Problem Description:&lt;/B&gt;















</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm01916</guid>
</item>
<item>
<title>CCMAdmin allows incorrect DHCP subnet configuration to be saved. , Open CSCtd34096</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd34096</link>
<description>
Symptoms:
 --------------
 Ccmadmin page does not generate an error if DHCP Subnet configuration is
wrong. It saves the configuration without checking whether the Start and End
IPv4 addresses are valid. 
 
 If a particular DHCP subnet is incorrectly configured, the DHCP server on
Cisco Unified Communications Manager server may not respond properly to DHCP
requests that were received on other correctly configured subnets.
&lt;br&gt; 
 
 Workaround:
 -----------------
 Manually ensure that all parameters for the DHCP Subnet configuration are correct.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd34096</guid>
</item>
<item>
<title>ES install fail on Sub after cluster IP addresses are changed , Fixed CSCsj35064</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj35064</link>
<description>
 &lt;B&gt;Symptom:&lt;/B&gt;
- 3 node Cluster, Pub &amp; 2 Subs
- CCM 5.1.1.3113-1
- hosts &amp; .rhosts verified to have the correct IP&#39;s &amp; names

Attempting to install ES 5.1.2.1101-4 from 5.1.1.3113-1 via SFTP or FTP fail
after the Pub &amp; Sub&#39;s have their IP Addresses changed. The ES may be installed
via DVD.

Upgrade logs show the Sub is attempting to SFTP to the Pub&#39;s old IP Address to
get the platformConfig.xml.

06/20/2007 11:34:35 primNodeVerify.sh|Download
/usr/local/platform/conf/platformConfig.xml file from 10.13.100.10|&lt;LVL::Info&gt;
&lt;br&gt;

 &lt;B&gt;Conditions:&lt;/B&gt;
Publisher has previously changed IP address.
&lt;br&gt;
 &lt;B&gt;Workaround:&lt;/B&gt;
Contact Cisco TAC and provide remote access for manual workaround.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj35064</guid>
</item>
<item>
<title>DCD tries to bind to renamed CallManager servers , Terminated CSCec21799</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCec21799</link>
<description>Symptom:

Application Event Viewer logs warning messages in regards to DCDirectory&#39;s 
ability to bind to a remote server.  The following message is an example:

Event Type:	Warning
Event Source:	DCDirectory
Event Category:	Administrator 
Event ID:	7441
Date:		9/4/2003
Time:		5:19:07 AM
User:		N/A
Computer:	XXXXXXX
Description:
(DSA BIND/UNBIND(37) Proc 468, Sev 14)
           DC Directory Server has failed to determine the IP address of a
           remote machine, which is configured by hostname either as knowledge
           or for replication.
           (gethostbyname() call failed).
             Remote host name:    EXTMOB
             Return code from system call       11001

In this case the Remote host name:  EXTMOB is a nonexistant servername within
the cluster.
&lt;br&gt;
Condition:

This has been observed when servers within a cluster get rebuilt with a different
name than what they were originally assigned.  In this case, the initial build
of the server was named EXTMOB however when the server was rebuilt it had a different
name.  DCD remains unaware of the status of the EXTMOB server.
&lt;br&gt;
Workaround:

From a command prompt on the publisher run the clean_publisher command.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCec21799</guid>
</item>
<item>
<title>fail to free up transcoder count when TRP involved , Fixed CSCsy38898</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy38898</link>
<description>None
&lt;B&gt;Symptom:&lt;/B&gt;
occasionally transcoder resources are not free up, therefore, the RTMT active transcoder counter is
not sync with active transcoder counter in the IOS gateway.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
This might happen if phone with TRP involved in a call with the transcoder, and then media
redirection such as hold/resume happens to the call.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
doing a &quot;no sccp&quot; &quot;sccp&quot; to the gateway resets the counter.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy38898</guid>
</item>
<item>
<title>DRS MA Hangs with KeepAlive.run, network disconnect detected for host , Fixed CSCsi80320</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi80320</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 
 During the Backup Process, the DRS Status page would hang and backup would never complete. In some 
cases the DRF Master and Local Agent Services would not start  and the following error will be noticed in 
the LA traces : &quot;Keep.Alive.run,Network Disconnect detected for host&quot;
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 DRF has been impcated due to the JDK version upgrade. The older Alarms JNI will not work as expected 
with the current version of JDK.
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
The workaround requires remote access to the server. Please contact TAC for the same.
This fix is available in 5.1(2b)/5.1.2.3000-2 and 5.1(3)/5.1.3.1000-12. Please upgrade to one of those 
versions or later.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi80320</guid>
</item>
<item>
<title>Cisco IPVMS no free USR buffers , Fixed CSCsv34390</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv34390</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

The IpVms media streaming driver encounters a shortage of large (8K) buffers that are used in streaming MOH and Announcements.  The IpVms media driver outputs an error message to the system log &quot;no free USR buffers&quot;.

The audio will sound &quot;choppy&quot; since blocks of audio data is dropped.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Using multicast MOH increases the probability of this problem occurring.  Also, using Cisco Wideband MOH codec will increase the possibility of having this issue.  Using multiple multicast MOH audio sources will gradually increase probability. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Periodically (daily) restarting of the CUCM server is about the only workaround as this will reset the buffer pool being used.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv34390</guid>
</item>
<item>
<title>Change Notification Fails -  DBLCNQueue Counts Rise - DBL Ptr Corruption , Fixed CSCse41788</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse41788</link>
<description>Symptom:
	Device modification, CFA and MWI fails.  DBLCNQueue table (New, Old, Head) 
	counts never get worked off.
&lt;br&gt;
Conditions:
	Normal operating conditions.
&lt;br&gt;
Workaround:
	Reboot server.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse41788</guid>
</item>
<item>
<title>aar not invoked if called number is the same as redirect number , Fixed CSCtd12682</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd12682</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Phone 1 (3227041111) calls Phone 2 (3227042222) - Note: Phone 2&#39;s AAR Mask = empty so if AAR were invoked AAR would call &#39;3227042222&#39; which is the exact same number Phone 1 originally dialed. 

In this situation AAR is never invoked.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Later versions of CUCM 6.1(3), the issue was introduced within a later 6.1(3) engineering special

In all versions of CUCM 6.1(4)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Ensure that a different DN is called when trying to invoke AAR

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd12682</guid>
</item>
<item>
<title>CTI-RP show unknown status after clusterwide reset , Fixed CSCsw94999</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw94999</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
Some CTI route points and ports do not registered back after customer restarts the ccm.exe service in all servers in the cluster.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Because the state of the Device object is not in &quot;ready&quot; state, the CtiDeviceResetReq is ignored by the Device object. Because this signal is ignored, a DeviceCloseDeviceReq is never sent to close StationD and any DeviceOpenDeviceReq sent to StationD receives a response of CTIERR_DEVICE_SHUTTING_DOWN. Note that the StationCtiD code already handles the scenario where the StationOutputReset is received before the DeviceOpenDeviceReq (this already causes a response of CTIERR_DEVICE_SHUTTING_DOWN to be returned).




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restart processes again



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw94999</guid>
</item>
<item>
<title>Unable to create ssl cert with friendly hostname , Fixed CSCsr68571</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr68571</link>
<description>Symptom:

End user receiving a warning about an invalid certificate when connecting
to the CCMUser pages.
&lt;br&gt;
Conditions:

End users attempts to connect to CCMUser web page via a &quot;friendly&quot; URL,
which has a different host.domain name than the actual publisher server.
&lt;br&gt;
Workaround:

CUCM 6.x cert creation process is described in documentation here:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cucos/6_1_1/cucos/iptpch6.html#wp1046223

Unlike in CUCM 4.x, this process does not allow the administrator to change the CN of the cert.

Workaround would be to have the end-user connect to the actual CUCM host.domain name.

Potential alternative workaround would be to change the server to the &quot;friendly&quot; hostname,
generate the CSR, and then change the hostname back to the original.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr68571</guid>
</item>
<item>
<title>7.1(3) RN should mention SFTP/FTP Server in addition to DVD , Fixed CSCtd34850</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd34850</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

The CUCM 7.1(3) release notes state a nonbootable DVD Is required, even though it is not required if the upgrade is performed use a remote file server using FTP/SFTP.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This is in the CUCM 7.1(3) Release notes.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Ignore the section about using a DVD, and just use a FTP/SFTP server.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd34850</guid>
</item>
<item>
<title>SCCP phone can&#39;t dial a 24 digit DN onhook or via personal directory , Fixed CSCsu71797</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu71797</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

SCCP phone can&#39;t dial a 24 digit DN onhook or via personal directory. Get &quot;call cannot be completed as dialed&quot; / reorder.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Using SCCP phone to dial a 24 digit number via onhook dialing, personal directory, or similar.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Dial DN with the phone offhook

OR

Disable Enbloc dialing by setting the &quot;Enbloc Dialing&quot; Product Specific parameter on the Device page to &quot;Disabled&quot; (available in CUCM versions with the fix for CSCta96468).

Fix for this issue will be available in Unified CM 8.0 and later.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu71797</guid>
</item>
<item>
<title>Large Phone Unregistrations leads to critical alarms being dropped , Fixed CSCsj20653</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj20653</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Critical alarms being dropped when large number of phones unregister at the
same time.  Syslog shows:

104 messages were dropped
24 messages were dropped
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

When there is a large number of phones unregistered at the same time.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Not applicable.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
Syslog drops are created by fix for CSCsg75347.  Drops are currently necessary
to prevent call processing interruptions.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj20653</guid>
</item>
<item>
<title>no icon for 7925 in CMadmin after Dev pack install to add support , Open CSCsz35217</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz35217</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Icon for 7925 appears as broken link in ccmadmin page
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
cucm 6.0.1a (6.0.1.2000-4)
cmterm-devicepack6.0.1.3116-1.cop.sgn
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
device still functions normally, despite missing icon. Solution requires root access by TAC.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz35217</guid>
</item>
<item>
<title>SIP Core when parsing SDP for RightFax , Fixed CSCtc98393</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc98393</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

SIP Cored as it was unable to process the SDP, as The connectionAddress passed to inet_pton was NULL.
This core was generated due to communication with RightFax.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Please make sure that you have this issue with RightFax trunk.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

N/A

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc98393</guid>
</item>
<item>
<title>catalina.out file gets too big when there is problem to start tomcat , Fixed CSCso50705</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso50705</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
Cisco Tomcat service log catalina.out file grows very large in size and stops to get rotated. The file could 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Under certain error conditions such as Database problems or Certificate problems Tomcat services or applications running within Tomcat we could be logging excessive amount of data in the catalina.out log file. This excessive logging error condition interferes with the log file management system and interrupts file rotation.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None to restore the log file rotation or clean up the excessive catalina.out file manually. Contact TAC who can assist further.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso50705</guid>
</item>
<item>
<title>CDR Load status shows Unsuccessful if it is interrupted by DRS backup , Open CSCsy90529</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy90529</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CDRs are inserted into the CAR database properly (i.e. you can search the CDRs and run reports), but the CDR Load status shows &quot;Unsuccessful&quot; status in the Event Log output (obtained from System -&gt; Log Screens -&gt; Event Log).
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This condition can occur if a DRS backup starts while CDR Loading is in progress.

When DRS backup begins, it sends an interrupt to the CAR Scheduler process to stop the CDR Loading process. When the CDR Loader begins at it scheduled time subsequently, it updates all unfinished jobs to reflect the &#39;Unsuccessful&#39; (-2) status, because these jobs couldn&#39;t finish due to previous interrupt (that was triggered by the backup operation).

To verify whether you are encountering this situation, look for the following information in the CAR Scheduler traces:

(1)
An interrupt which stops the CDR loading. This interrupt will be observed whenever the DRS backup operation initiates:

INFO  [ShutdownHandlerThread]
services.SchedulerShutdownHandler - run(): --&gt;

-- and --

(2)
The following snippet which will indicate that the CDR Load job status is set to Unsuccessful:

 INFO  [main] services.Scheduler - sendAlarm():
CARSchedulerJobError alarm for 2 VARIOUS JOBS job: [JobName-&gt;2 VARIOUS
JOBS,FailureCause-&gt;Update unfinished (InProgress / Scheduled) jobs from
tbl_event_log.,FailureDetail-&gt;CAR Scheduler restarted, update ALL 2 job(s)
with status: &#39;-1&#39;,&#39;-3&#39; to status: &#39;-2&#39;.]


&lt;B&gt;Note::&lt;/B&gt;

In most instances, the CDRs are actually inserted correctly into the CAR database. In this case, the &quot;Unsuccessful&quot; status is cosmetic.

However, if the CDRs are not being inserted into the CAR database and you see &quot;Unsuccessful&quot; status, then the problem might be different (i.e. unrelated to the behavior described by this bug).

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy90529</guid>
</item>
<item>
<title>Critical update for x206m/x306m BIOS to fix 1.42/1.43 BIOS issue , Fixed CSCta40345</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta40345</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
    
The on-board HostRAID controller is not detected during POST on a x306m server
running version 1.42 or 1.43 of the system BIOS when the 10/01/2009 date is
reached or set to later.
    
The OS is not found, since the HostRAID controller is not detected and the
BIOS configuration/setup menu is no longer accessible.
&lt;br&gt;    
&lt;B&gt;Conditions:&lt;/B&gt;
    
The BIOS system date of 10/01/2009 is reached or set to later when running
BIOS version 1.42 or 1.43 on a x306m (MCS-7825-I2).
    
If you are past the 10/01/2009 date, you may run the offline IBM Dynamic
Systems Analysis CD to determine the current version of the BIOS the system is
running.
    
If you are prior to the 10/01/2009 date, you may press the F1 key during POST
to enter the BIOS setup menu and check the current BIOS version.
    
Alternatively, you may insert the latest Cisco Firmware Update CD (FWUCD) and
it will determine what version of the BIOS is currently running and if the
update is applicable.
&lt;br&gt;    
&lt;B&gt;Workaround:&lt;/B&gt;
    
Upgrade the BIOS to a version later than 1.43 using the latest Cisco FWUCD
(version 2.3(1) or later).
  
A field notice has been issued
http://www.cisco.com/en/US/ts/fn/632/fn63255.html outlining the workaround and
where you can download the latest FWUCD.iso file that contains the 1.45 bios
version.
Please follow the steps in the readme file for the FWUCD 2.3.1 to upgrade the bios.
  
Note: for customers that need to run a fresh install with older media after
10/01/2009, you will need to select &quot;Upgrade During Install&quot;. The upgrade
during install needs to be to a version that contains the fix for this defect.
 You may be required to use the FWUCD.iso to recover the server before you can
install the CUCM software.
&lt;br&gt;    
&lt;B&gt;Further Problem Description:&lt;/B&gt;
    
See complete details at
  
http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&amp;lndocid=MIGR-5078576
    
   
   
  
  
 
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta40345</guid>
</item>
<item>
<title>BAT: Changing Sidecar Load on Device changed Sidecar to 7914 , Open CSCtd28803</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd28803</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

For phones with 7915 or 7916 Side Car configured  with a load ID.  Run a query (doesn&#39;t matter if its all devices or just 1). When updating the load ID from a value to none and running the process it changes the side car device on all phones from the previously assigned device to the 7914.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

All known versions of CM for linux experience this issue.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Run another query on same devices and change the 7914 back to the previously assigned device.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd28803</guid>
</item>
<item>
<title>Certificate management doesn&#39;t allow apostrophe (&#39;) in OU ,   CSCtd07881</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd07881</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When on CUCM CLI try to run &quot;set web-security&quot; command, apostrophe in organization name doesn&#39;t get accepted.  Certificate management blocks this character.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 7.0.2.21900-10
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd07881</guid>
</item>
<item>
<title>bat.xlt allows max 30 characters for &#39;mailid&#39; value for end user , Fixed CSCtc79177</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc79177</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

bat.xlt allows max 30 characters for &#39;mailid&#39; value for end user. However, this field can be up to 255 characters in the DB.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

When configuring &#39;users&#39; or &#39;update users&#39; sheet in bat.xlt file
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Export the data from xlt to the BAT txt file, and edit the resulting file before uploading it onto CUCM.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc79177</guid>
</item>
<item>
<title>network flapping fails clustermanager and causes replication failure , Fixed CSCsx07438</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx07438</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

In &#39;show open ports regexp 8500&#39; it is seen that another process then clm (cluster manager) is bound to UDP port 8500. 

The correct output should be similar to : 

admin:show open ports regexp 8500
 Executing.. please wait.
 clm        4575       root    6u  IPv4    17966       UDP *:8500 
 clm        4575       root    7u  IPv4    17967       TCP *:8500 (LISTEN)

Incorrect is when another process then clm is bound to 8500, such as :

modprobe 2305 root 6u IPv4 12116 UDP *:8500
modprobe 2305 root 7u IPv4 12117 TCP *:8500 (LISTEN)
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
This failures occurs in CM 6.x.  This is triggered by loss of connectivity between nodes or restarting clustermanager(clm).  CM 7.x should not experience this failure.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Only known workaround is to reboot the server on which this is seen.
&lt;br&gt;
&lt;B&gt;Further Information:&lt;/B&gt;
The fix implemented prevents clm from reloading iptables which prevents removing and reinserting kernel modules.  This fix should address this issue and CSCsx72862 where kernel hangs during kernel module remove/insert and is recovered by ASR.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx07438</guid>
</item>
<item>
<title>rmcm initializing and jtpa out of service , Fixed CSCta62713</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta62713</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;
RMCM stay at initializing and jtapi stay at out of service
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Initial config or after changing the password on the uccx for rmcm and jtapi and update it gives updated successfully
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Go to ccm jtapi and rmcm user page and uncheck credential for &quot;password can&#39;t be changed&quot; and save, then go to uccx and change password for rmcm and jtapi user.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta62713</guid>
</item>
<item>
<title>CCMUser page special character error clears forwarding settings , Fixed CSCtd18892</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd18892</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Call Manager 5.1.3 the ccmuser page does not escape special characters in the line text table field.  Updating the line text field after getting an error due to special characters in the field causes the call forward settings to be lost.
&lt;br&gt;


&lt;B&gt;Conditions:&lt;/B&gt;
Enter a special character (such as apostrophe) in the line text label of the ccmuser page and click save.  You&#39;ll get this error:

Update failed. A syntax error has occured.

Correct the line text label by removing the special character, and click save.  You&#39;re call forward settings on the line are erased.
&lt;br&gt;


&lt;B&gt;Workaround:&lt;/B&gt;
Avoid using special characters in the line text label.  If you do get an error from using a line text label with special characters, log out of the ccmuser page and then log back in to update the line text label with something that does not contain special characters.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd18892</guid>
</item>
<item>
<title>RTMT CallsInProgress counter constantly increases on callmanager , Fixed CSCsv64565</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv64565</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

RTMT counter CallsInProgress constantly increases on CUCM 6.1(2)
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
- incoming call over MGCP PRI QSIG
- callback activated
- once user becomes available we send Facility
- receiving back Setup/w FACILITY ccRingout
- shortly after that receiving back Release/w FACILITY ccCancel
- terminating call but Cdcc process not stopped which leads to CallsInProgress counter to increase with time
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
none
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv64565</guid>
</item>
<item>
<title>vg224 virtual port registration issues. . . , Fixed CSCsx52822</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx52822</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

VG224 Auto Configuration is not working due to virtual port registration issues
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Configure VG224 in the CM GUI and VG224 autoconfiguration on the VG224 IOS Gateway.  A &quot;show sccp&quot; will show that the sccp virtual port is not registering.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

User has to perform a &quot;no ccm-manager sccp&quot; &quot;ccm-manager sccp&quot; on the VG224 gateway to force an update.  
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

None


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx52822</guid>
</item>
<item>
<title>End user Config page is blank , Fixed CSCso58752</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso58752</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
End user configuration page is blank.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM and Unity Connection
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
Full fix also requires fix for CSCso43615.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso58752</guid>
</item>
<item>
<title>CM 5.1 - Tomcat web certificate regeneration fails ,   CSCsi51295</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi51295</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

The customer cannot access the CCM admin web page or connect to the the server using RTMT as both use SSL 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

New Installation. The customer did not put in the FQDN in during install. Go to Cisco Unified OS administration, Security -&gt; Certificate management. Regenerate certificate and choose Regenerate Self-Signed Cert and pick Tomcat
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi51295</guid>
</item>
<item>
<title>Cannot configure CCMUser traces via serviceability web page , Fixed CSCsm37017</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm37017</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When configuring the traces on the serviceability web page, there is no CCMUser option to select. There is no way to change the default CCMuser trace level.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Checked on 5.1, 6.0 and 6.1
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
No workaround.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
Please note that once you have upgraded to a 5.x version containing this fix, any attempt to upgrade to a 6.x version that DOES NOT also have this fix will fail.

For example, once running 5.1.3.2104-1 or later 5.1(3) ES, you cannot upgrade to 6.1(1) [6.1.1.1000-11] or 6.1(1a) [6.1.1.2000-3]. You must upgrade to 6.1(1b) [6.1.1.3000-2] or 6.1(2) [6.1.2.1000-13] in order for the upgrade to be successful.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm37017</guid>
</item>
<item>
<title>Multicast MOH does not work when SIP EP/trunk is put of hold by an EP , Fixed CSCsq76611</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq76611</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When a SIP end point /Trunk is put on hold by another end point, multicast MOH will not work since the CCM will send a ptime of 80 (packetization) in the Multicast Invite to the SIP Endpoint/ Trunk given that MTP required is not checked.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Check MTP required and allocate MTP resource.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq76611</guid>
</item>
<item>
<title>JTAPI error -1932787643 when Apps is answering a consult call , Fixed CSCsd56416</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd56416</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When a call is transfered to an IPCC script, we sometime have a IPCC message that says that there&#39;s technical problems and the call can&#39;t be transfered. From IPCC perspective, the MIVR logs shows CCNException errorCode = -1932787643.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
IPCC tries to answer the call at the same time as consult transfer is completed by the caller.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Put a 2 sec delay before the accept step in the IPCC script
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
From the IPCC perspective, the apps thread that calls the JTAPI answer method is not released,
and therefore it is not able to respond to the Open Logical Channel event on its other thread
(due to synchronization of the two threads). JTAPI is supposed to release the thread immediately.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd56416</guid>
</item>
<item>
<title>HP agents v7.8.1 incorrectly reports fan status degraded , Terminated CSCsu99994</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu99994</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Customers using HP agents v7.8.1 which were added via CSCsr23111 may see false reports of fan status degraded or thermal warnings on 7835H-3.0GHz servers.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Only seen on HP DL380 G3 servers running HP agents v7.8.1 which is included in some versions of CallManager 5.1(3)es, 6.1(1)es, and 6.1(2)es code.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Revert to a version of software with an older set of HP agents, such as 7.8.0

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu99994</guid>
</item>
<item>
<title>CUCM accepts a called party transformation pattern that begins with a + ,   CSCtc81932</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc81932</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
CUCM accepts a called party transformation pattern that begins with a +.  Such a pattern will not be properly applied to calls when added to a device.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
Add a called party transformation that begins with an unescaped + sign 
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Prefix the pattern with an escape character (\) 
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc81932</guid>
</item>
<item>
<title>CUCM reboots by ASR with intermittent connectivity between nodes ,   CSCsx72862</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx72862</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Some servers in the cluster (normally NOT all servers) may be automatically rebooted if ASR is enabled, or hang if ASR is disabled.

When server hung with ASR disabled, no console ouput from the server, no network connectivity to the server and cold boot of the server is the only way to recover it. Netdump is setup but did not collect any kernel panic when the problem happened.

If ASR is enabled, server will be automatiically rebooted by ASR in the frequency as a few times per day to once/twice per two days.

file view system-management-log
0157 Critical       08:13  02/11/2009 08:13  02/11/2009 0001
LOG: ASR Detected by System ROM

In CiscoSyslog (application logs), the following messages have been continueously repeating throughout the logs every few seconds.

Feb 18 18:33:41 clay-voip-cm0 local7 6 : 41778: Feb 18 07:33:41.451 UTC :  %CCM_CLUSTERMANAGER-CLUSTERMANAGER-6-CLM_PeerState: Current ClusterMgr session state. Node&#39;s Name or IP:clay-voip-pres0 Node&#39;s State:INITIATOR App ID:Cisco Cluster Manager Cluster ID: Node ID:clay-voip-cm0
Feb 18 18:33:49 clay-voip-cm0 local7 6 : 41779: Feb 18 07:33:49.131 UTC :  %CCM_CLUSTERMANAGER-CLUSTERMANAGER-6-CLM_PeerState: Current ClusterMgr session state. Node&#39;s Name or IP:clay-voip-pres0 Node&#39;s State:POLICY_INJECTED App ID:Cisco Cluster Manager Cluster ID: Node ID:clay-voip-cm0

The above log messages were ONLY observed in the problem/rebooting servers in the cluster, NOT in the working servers.


Alternatively the last messages that appear in the system log file (messages file) may be:
Feb 23 01:39:59 myserver kern 4 kernel: ip_tables: (C) 2000-2002 Netfilter core team
Feb 23 01:39:59 myserver kern 4 kernel: ip_conntrack version 2.1 (16384 buckets, 131072 max) - 304 bytes per conntrack
Feb 23 01:39:59 myserver local7 5 iptables_orig:  succeeded
&lt;time of reboot reported in ASR&gt;
Feb 23 01:51:50 myserver syslog 6 syslogd 1.4.1: restart (remote reception).
Feb 23 01:51:50 myserver local7 5 syslog: syslogd startup succeeded
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

it has been observed, but not limited to:

A unused CUP server (presence installed and inserted into cluster,  but not used or deployed) enter into &quot;READ-ONLY&quot; like state, iptable failed to be open and cluster manager on presence keep talking to cluster manager in callmanager to inject policy.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

1. reboot the problem presence server.
2. take the unused problem presence server offline.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Replace the whole server did not help the situation, During investigation, it has been observed that the unused presence servers in the newtork have caused these significant amount of messages in callmanager cluster (more than 30000 cluster manager messages per day in application log). it is also observed that these unused presence servers are in state simlar to a READ-ONLY file system. cluster manager on the presence servers failed to open iptable to inject policy,.As a result, cluster manager of CUP have been bounced between INITIATOR and POLICY_INJECTED state due to failed to open/update iptable, this has caused cluster manager on callmanager keep starting/stopping iptables and reloading kernel module.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx72862</guid>
</item>
<item>
<title>Error -Locale update error: File not found.Please check TFTP server IP , Open CSCtb23856</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb23856</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;
Every time selecting the CiscoTSP001.tsp and click configure buttong getting this below error
Locale update error: file not found. Please check the TFTP server IP.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
When CUxAC installed on the any server (vmware or non-vmware environment)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Delete the TFTP server ip and then add it later and save. 
phone and modem -&gt;advanced -&gt;ciscoTSP001.tsp -&gt;config -&gt;TFTP config -&gt;delete the IP and click ok, then go back and input the cucm tftp server IP and save.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
Have not seen any functionality affecting but not sure and would like to get this error resolved


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb23856</guid>
</item>
<item>
<title>Callmanager TOD routing not updated with DST patches , Fixed CSCsh81747</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh81747</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Time of Day routing is still 1 hour off in US timezones after applying DST 
patch
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CallManager patched for DST, running in a US timezone, using TOD routing. This 
is applicable from CallManager version 4.1 onwards only. This bug is not applicable to 3.3.5 version and 5.X versions.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

CallManager TOD can be configured with two options from Route Partition. The options are either:

- Use specific Time Zone (You can select Time Zone from the drop down list)
- Use Originating Device Time Zone.

If the system has been patched for DST either with an ES version with the fix for CSCsf07523 or with the standalone DST patch for, the second option (Use Originating Device Time Zone) would work correctly.

Depending on the specific system, a possible workaround would be to set it to &quot;Use Originating Device Time Zone&quot;

If the situation is such that &#39;Use specific Time Zone&#39; if needed, then the fix for this defect is required.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh81747</guid>
</item>
<item>
<title>L2 Upgrade takes too long/hangs , Fixed CSCsz22187</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz22187</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

L2 upgrade from 6.1.2 to 6.1.3 takes too long.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Inactive partition has version 6.1.1 or lower with CDRREP logs in excess of 500,000.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Wait for upgrade to finish (it will finish eventually), or, manually delete the CDRREP logfiles.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz22187</guid>
</item>
<item>
<title>Dual Monitor support for Attendant Console , Terminated CSCsb46132</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsb46132</link>
<description>Problem:
Ac not fully supported on PC with dual monitors

Scenario:
Console running on PC with 2 monitors.
In case Console is run on dual monitor PC and is not displayed on default monitor , some pop up messages like info / error may be displayed on default monitor .
This creates usability issues
&lt;br&gt;
Workaround:
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsb46132</guid>
</item>
<item>
<title>Registered CTI route point  gets fast busy when calling it , Fixed CSCsu02856</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu02856</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
Calling a registered a CTI routepoint gets fast busy







&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Calls can be placed using IP phones to call directly to the CTI route point or parts of call center calls, when customer calls the Tollfree number, and this tollfree number ( CTI route point ) is associated with a dial-number in ICM
The problem seems to be happening after the Callmanager where the CTI route point is registered goes out of service and then comes in services and the CTI route point registers back.

 




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Disassociate the pg user with the CTI route point and associate it back.



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;













</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu02856</guid>
</item>
<item>
<title>Subscriber node starts throwing MaxCallsReached Error with CVP 4.0 load , Fixed CSCsg28679</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg28679</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

H.323 transfers from CVP  to SCCP devices on CCM fail.  Call Manager logs start showing MaxCallsReached (Maxium Calls Reached) errors.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Run a load with 3 calls/second for a call rate with 300 consecutive calls.  We have 1 publisher and 2 subscibers.  All devices are Skinny Camelot devices for the load test.

The call flow for the test is as follows:

- All call come to CVP and caller receives IVR treatment initially 
- For 60% of the calls, the call is transferred to an available agent (one xfer to CCM from CVP) 
- For 40% of the calls, the call is transferred to an available agent initially(agent 1) and then the agent 1 will initiate a transfer via CTI Route Point to agent 2.  CVP will transfer the call to agent 2 from agent 1. 
- If not enough agents in the agent 2 pool are available then, caller will queue until an agent becomes available 

After about 5 hours, CCM starts showing the MaxCallsReached symptom.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Recycle Call Manager subscribers



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg28679</guid>
</item>
<item>
<title>New CDP.sys driver is only copied to C:\Program Files\Cisco\Bin\ , Fixed CSCsk10239</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk10239</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
After installing CUCM 4.1(3)es119 through 4.1(3)es122, the new CDP.sys driver from CSCsj37081 is only copied to C:\Program Files\Cisco\Bin\
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
All CUCM installations from 4.1(3)es119 through 4.1(3)es122,
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk10239</guid>
</item>
<item>
<title>Incorrect SNMP sysOID for 7825H4 server model , Fixed CSCta35604</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta35604</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CER unable to discover phones registered to one callmanager 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Incorrect SNMP sysOID reported for callmanager installed on 7825H4 server.  SNMP sysOID for all 7825H models (including 7825-H4) should be 1.3.6.1.4.1.9.1.583, but the below example  output shows the final digits as 853.
admin:utils snmp get 1 test  1.2.3.4 .1.3.6.1.2.1.1.2.0

This command may temporarily impact CPU performance.

Continue (y/n)?y

iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.9.1.853
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;

Create a remote account, contact Cisco TAC, and provide remote access to implement workaround.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta35604</guid>
</item>
<item>
<title>Unable to delete a presence group from the CM admin paget , Open CSCtd37021</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd37021</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Cannot delete presence group from the CM admin page though there are no dependencies.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;

If the device is configured for a presence group and it once had extention mobility enabled , the entry is added to the &quot;extensionmobilitydynamic&quot; table. 
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;

Delete the device and add it to remove its entry from the &quot;extensionmobilitydynamic&quot; table.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Every single time we enable an IP  phone with extension mobility its entry is added into the &quot;extensionmobilitydynamic&quot; table but it is not removed even after disabling extension mobility for that IP phone.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd37021</guid>
</item>
<item>
<title>BLF Speeddial Not Present on Fallback , Terminated CSCtb98085</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb98085</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

CallManager BLF issue: Phone A have a BLF speedial to phone B (the 2 phones are registered on subscriber 1). If subscriber 1 fail, Phones A and B register on subscriber 2 and BLF speedial continue to work. When subscriber 1 comes back, phones A and B register again to subscriber 1. At this time, the BLF speedial doesn&#39;t appear on the phone.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

during fall back
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

reset the phone brings back the speed dial option. 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb98085</guid>
</item>
<item>
<title>hostagt and snmp_master_agt consumes high cpu constantly , Fixed CSCsm74316</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm74316</link>
<description>Host agent and SNMP Master agent consumed high CPU 
&lt;B&gt;Symptom:&lt;/B&gt;
CPU usage for host agent and snmp master agent becomes high
IN the output of the command &lt;b&gt;show process load&lt;b&gt;  
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
During a scenario of community string configuration and restart of the SNMP Master Agent, host agent is unable to communicate with master agent which leaves it with high CPU occupancy.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
   --&gt; After SNMP configuration changes before restarting SNMP Master Agent service, stop the Host Resources Agent  first from the serviceability webpage (Tool-&gt;ControlCenter Network Services-&gt;(Select Server)-&gt;(look for Platform Services in which Host Resources Agent should be slected for STOPPING)

  ---&gt;Then Restart SNMP Master Agent (Tool-&gt;ControlCenter Network Services-&gt;(Select Server)-&gt;(look for Platform Services in which SNMP Master Agent should be slected for RESTARTING)

  ---&gt; After the SNMP Master Agent comes up successfully, start Host Resources Agent (Tool-&gt;ControlCenter Network Services-&gt;(Select Server)-&gt;(look for Platform Services in which Host Resources Agent should be slected for STARTING)
&lt;br&gt;
 &lt;B&gt;Further Problem Description:&lt;/B&gt;



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm74316</guid>
</item>
<item>
<title>Clean up external address when call to PSTN fails , Fixed CSCtb60026</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb60026</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
JTAPI client over time and under load exhibits ever-increasing CPU utilization and working-set size expansion






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
This symptom can manifest itself during IP Contact Center Outbound Option call load.  This is seen when a large number of calls to PSTN fail. This in turn slow the systems and results in call failures, which increase in frequency as the JTAPI client CPU utilization grows and grows.



&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restarting the Peripheral Gateway restarts the JTAPI Gateway process and the JTAPI client. 


&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
JTAPI client maintains a hash table for external addresses which can grow and grow without being trimmed.  This causes the CPU consumption and working-set size issues.












</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb60026</guid>
</item>
<item>
<title>JTAPI problem during conference calls. , Fixed CSCsi97912</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi97912</link>
<description>Symptoms: During Join/DirectXfer operations the calls are selected by CTI and later left selected after the operation is completed. This causes further join/direct xfer operations on same device to include the surviving call in resulting join/direct xfer implicitly, eventhough user has not specified it in the request. 
&lt;br&gt;
Condition: 4.1.3 CCM
&lt;br&gt;
Workaround: none

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi97912</guid>
</item>
<item>
<title>commonName field in generated Tomcat CSR does not contain domain name , Open CSCtd36375</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd36375</link>
<description>Symptom:

When you 

1. configure the domain by issuing the command &quot;set network domain exampledomain.local&quot;
-&gt; this will reboot the node
2. generate a tomcat CSR
3. Verify the CSR (from root)
-&gt; &quot;openssl req -noout -in /usr/local/platform/.security/tomcat/keys/tomcat.csr -text&quot;

=&gt; you will notice that the CN Field only contains the hostname and not the FQDN as configured.
&lt;br&gt;
Conditions:

Verified on 6.1.4.1211-1 
(issue not seen in 6.1.3.2000-1)
&lt;br&gt;
Workaround:

1. Generate the tomcat certificate through OS Admin page. This self
signed certificate will be generated with CN=FQDN and will be stored in
.tomcat.keystore.

2. Contact TAC to create a root account using the remote support tool, get TAC to connect to
the node by ssh and execute following commands.

cd /usr/local/platform/.security/tomcat/keys

cat .tomcat.passphrase | keytool -certreq -alias tomcat -sigalg
SHA1withRSA -keysize 1024 -file .tomcat.csr -keystore
../certs/.tomcat.keystore   

&gt;&gt;&gt; this will generate new csr.

chown certbase:ccmbase .tomcat.csr

chmod 755 .tomcat.csr

3. openssl -req -in .tomcat.csr -text    
.&gt;&gt;&gt;&gt; check subjectName to verify CN=FQDN and other fields also.

4. Download CSR through OS Admin page and get it signed by CA and
upload it again.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd36375</guid>
</item>
<item>
<title>Disabling Extension mobility through update phones fails , Fixed CSCsl40789</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl40789</link>
<description>

 &lt;B&gt;Symptom:&lt;/B&gt;
 Update Phones fails with error &quot; No LOGOUT device profile, login/logout not 
allowed&quot; 
 run the following CLI and the value for ikdevice_defaultpreofile is empty 
string instead of NULL (please replace the name SEPXXXXXXXX to be the proper 
device name):
    run sql select ikdevice_defaultprofile from device where name 
= &#39;SEPXXXXXXXX&#39;
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 For 6.X release only.
 1)Select few phones which are enables with extension mobility.
 2)And the a user is logged into the phones with a device profile
 3)Now select the update check box for Extension mobility option and 
Extension mobility disabled.
 4)And Select the check box for log out users before update.
 5)The update job fails with error.
 
  No LOGOUT device profile, login/logout not allowed
&lt;br&gt; 
 
 &lt;B&gt;Workaround:&lt;/B&gt;
 There are two workarounds available, please just apply one. 
 1) Run the following CLI command (please replace SEPXXXXXXXX with the proper 
device name):
     run sql update device set ikdevice_defaultprofile = NULL where name 
= &#39;SEPXXXXXXXX&#39; 
 2) Go to phone configuration page for the device, uncheck the box for 
extension mobility and save the configuration, then re-check the box for the 
extension mobility. 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl40789</guid>
</item>
<item>
<title>Multicast Music On Hold does not work across intercluster trunks , Fixed CSCdw18642</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdw18642</link>
<description>Symptom:

Held users may not hear Music On Hold even if it is configured.
&lt;br&gt;

Condition:

This will happen if the held device and holding device are registered to 
different CallManager clusters and the call was placed via Intercluster 
Trunk. Also this will only happen when the holding CallManager is using 
Multicast Music On Hold.
&lt;br&gt;

Workaround:

Use Unicast Music On Hold for Intercluster Trunk gateway devices.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdw18642</guid>
</item>
<item>
<title>Not able to import certificate due to special character in CN of Cert. , Fixed CSCsv76010</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv76010</link>
<description> &lt;B&gt;Symptom:&lt;/B&gt;
 
 When trying to upload a certificate on OS Administration web page, getting error:
  &quot;\/usr/bin/openssl\ terminated with error 1&quot;
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 There are two consecutive special characters in CN attribute.  For example
 
 CN = 
 
 &quot;//&quot; is considered as a special character because  target filename is getting
created from CN.
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
None. Upgrade to a version that has this bug fixed.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv76010</guid>
</item>
<item>
<title>MVA hairpinning doc should have step for Route Pattern in CM to H.323 GW , Fixed CSCsy33261</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy33261</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

The Features and Services Guide in 6.0(1) and 7.0(1) do not contain the step for configuring a Route Pattern in CallManager to point to the H.323 gateway, in the list of steps to configure MVA with Hairpinning
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

When configuring MVA with hairpinning, a Route Pattern needs to be created on the CallManager, to direct the incoming call to the H.323 gateway, so that the IVR script will be played. The Features and Service Guide for 6.0(1) [under Mobile Connect and Mobile Voice Access], and 7.0(1) [under Cisco Unified Mobility] don&#39;t mention creating a route pattern in the list of steps required to configure MVA using Hairpinning

Also, the Features and Services Guide for 6.0(1) version of CallManager should replace destination-number with destination-pattern in the list of steps to configure MVA using PRI, as well as Hairpinning.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy33261</guid>
</item>
<item>
<title>CUCM 7.0 Backup failure with linux OpenSSH based SFTP servers , Fixed CSCsv34475</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv34475</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
 
DRS unable to sftp to backup location if backup device is linux sftp server
&lt;br&gt; 
&lt;B&gt;Conditions:&lt;/B&gt;
 
This problem is seen on CallManager version 7.0.1 and UC version 6.1 if a linux based sftp server
is used as a backup device. The &#39;add device&#39; operation fails. 
The fix have been added to 7.X and above. The fix is not available on 6.X versions.
&lt;br&gt; 
&lt;B&gt;Workaround:&lt;/B&gt;
You can apply any one of the two suggestions given below:-
Either:- Use other sftp servers like FreeFTPD as workaround in case of CUCM product. When backup files are larger than 1GB FreeFTPD will fail and DRS will hang due to a known issue CSCsm21349.  Due to this FreeFTPD should not be used for Unity Connection where backups often exceed 1GB, but rather another SFTP server should be used such as TitanSFTP, Cygwin, or OpenSSH for Windows.

Or:- Edit /etc/ssh/sshd_config (on OpenSSH based sftp server) to contain the following line
PasswordAuthentication yes
This would enable tunneled clear text passwords.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv34475</guid>
</item>
<item>
<title>CAR scheduler error with To duration greater than 1000 , Fixed CSCsm21968</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm21968</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CAR scheduler reports exceptions in the log referencing java.lang.NumberFormatException.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

In CAR Report Config -&gt; Rating Engine -&gt; Duration a value greater than 999 is configured.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Make sure the above value is less than 1000.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Example of the full error from the CAR log:

ERROR [DailyCdrLoad] controller.CtrLoader - run(): Unexcepted error or error from CDR Delivery Helper class.
java.lang.NumberFormatException: For input string: &quot;10,000&quot;
            at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
            at java.lang.Integer.parseInt(Integer.java:477)
            at java.lang.Integer.parseInt(Integer.java:518)
            at com.cisco.ccm.car.controller.CtrLoaderUtil.computeCharge(CtrLoaderUtil.java:1039)
            at com.cisco.ccm.car.controller.CtrLoadDumpRecords.processDumpAdhocConferenceRecords(CtrLoadDumpRecords.java:2564)

In this case the value is set to 10000 and you can see that the formatting of this number results in a comma being inserted after the value is pulled from the database.  The number cannot be parsed with the comma inserted.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm21968</guid>
</item>
<item>
<title>CAR DRS fails as car does not deactivate services using FQDN , Fixed CSCsq11246</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq11246</link>
<description>Symptom:

After upgrading to CUCM version is 6.0.1.2124-1, customer is unable to run Disaster Recovery Backups. Backup fails during the &quot;Invoking CAR Services deactivation Script&quot; stage. CAR services can not be stopped and the backup fails.
&lt;br&gt;

Conditions:

Log File:
2008-04-28-12-55-29_b_cucmpub_ccm_ccmdb.log=================================
==============
======
Server : CUCMPUB
Feature : CCM
Component : CCMDB
Time Completed: 2008-04-28-12-56-45
Result Code : 101
Result String : ERROR
=====================================================
Stopping CAR services prior to taking DB backup 
CDRREP: Invoking CAR Services deactivation Script
CDRREP: Checking CAR services status, please wait ...
CDRREP: CAR Scheduler initial status is - activated
CDRREP: CAR Web Service initial status is - activated
CDRREP: Deactivating Cisco CAR Scheduler using hostname CUCMPUB
CDRREP: Could not deactivate Cisco CAR Scheduler using HostName CUCMPUB
CDRREP: Deactivativating Cisco CAR Scheduler using HostIP 192.x.x.x
CDRREP: Could not deactivate Cisco CAR Scheduler using HOSTIP 192.x.x.x
CDRREP: Exiting CAR services deactivate script with error code 99
CAR services failed to stop; backup cannot proceed until all CAR services
are stopped.
TERMINATING 


----&gt; BEGIN Standard Output
Stopping CAR services prior to taking DB backup 
Service Manager is running
Cisco CAR Scheduler[STARTED]
Service Manager is running
Cisco CAR Scheduler[STARTED]
CDRREP: Could not deactivate Cisco CAR Scheduler using HOSTIP 192.x.x.x
CAR services failed to stop; backup cannot proceed until all CAR services
are stopped.
TERMINATING 
&lt;br&gt;

Workaround:

Manually stop CAR and the back up works.

Also as a workaround please ask the customer to set the server name to &quot;CUCMPUB&quot; from ccmadmin page as the hostname is CUCMPUB. Car uses the hostname to deactivate the services before DRS starts.  Hence changing the server name from ccmadmin pages would help customer schedule DRS backups without manual intervention.

Also ideally we recommend that the customer change the hostname in database as well as cli if they change the server name at any point. Currently the server name in database and cli does not match in the customer machine.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq11246</guid>
</item>
<item>
<title>CUCM increase voicemail port limit , Fixed CSCsl30744</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl30744</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Unity version 7.x supports up to 200 ports registered to a single CUCM cluster for each Unity server.  Using the Voicemail Port Wizard in CUCM 5.x, 6.x, 7.x you are unable to add more than 144 ports with the wizard.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Relevant to Unity 7.x where more than 144 ports are configurable with one Unity server.  Need to change parameter in CUCM from a drop-down list to a variable field that will account for future changes in Unity that may allow more VM ports to be added.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Manually add Unity ports in CUCM configuration.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl30744</guid>
</item>
<item>
<title>JTAPI reports NullPointer Exception while removing observers , Fixed CSCsz16024</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz16024</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
JTAPI reports Null pointer Exception while removing the observers once after logs out from a device.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Exact scenario is:
Application Opens Provider
Adds observers to device A and
User logs into device A by extension mobility and then logs out
Remove observers from device A - Here JTAPI reports Null pointer Exception
 at com.cisco.jtapi.IntraProviderAddress.removeObserver
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz16024</guid>
</item>
<item>
<title>ADP is not deleted when deleting IP Phone , Fixed CSCsl33794</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl33794</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When deleting IP Phone with checking &quot;Enable Extension Mobility Feature&quot; 
and selecting &quot;Use Current Device Settings&quot;, its ADP (Autogenerated Device Profile)
is not deleted.

As a result, If the same IP Phone is added and &quot;Use Current Device Settings&quot; is selected,
the following error occurs and the updata is failed:
========================================
Method call failed. (4)
Details:
Error No. -2147219964 (0x80040604):
CDBLException Dump: [Method call failed]
========================================
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
Cisco Unified CallManager 4.3(1), 4.3(1)ES14
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
To uncheck &quot;Enable Extension Mobility Feature&quot; before deleting IP Phone.
&lt;br&gt;

&lt;B&gt;Further Problem Description:&lt;/B&gt;
To use Extension Mobility on an IP Phone which ADP is not deleted, it&#39;s necessary to make a User Device Profile and select it by selecting &quot;Select a User Device Profile&quot; in &quot;Log Out Profile&quot;.
That is, to use UDP instead of ADP.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl33794</guid>
</item>
<item>
<title>CTI Route Point Status Unknown after Cluster Restart , Fixed CSCsl92892</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl92892</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
Clusters that have &gt; 3 CTI Nodes some CTI Route Points remain in an &quot;Unknown&quot; status. This could be different CTI RP each time the cluster is restarted.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Clusters with &gt; 3 CTI nodes.




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None - (Not Supported - Associating RP to application user ac consistently results in successful registration)



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;













</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl92892</guid>
</item>
<item>
<title>Line status info (CFA icon) not updated in real-time for AC client , Fixed CSCsu54774</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu54774</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CFA icon not getting updated in real-time after upgrade to 6.1.2-1111
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CCM version 6.1.2-1111
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
Issue seen after upgrade from CCM 6.1.2.1000 to 6.1.2-1111.

Have test in the lab, and we see similar intermittent issue of the CFA icon.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu54774</guid>
</item>
<item>
<title>CM fails to start if not in CM grp- ERROR readStationRegistrationProfile , Fixed CSCsk12127</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk12127</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CallManager does not start successfully. CCM traces will show similar:

08/14/2007 09:28:57.687 CCM|dBProcs - readStationRegistrationProfileList(): mStationConfigList finished get ODBC object|&lt;CLID::StandAloneCluster&gt;&lt;NID::CCM001&gt;
08/14/2007 09:28:57.687 CCM|dBProcs - ERROR readStationRegistrationProfile, ccm = [CCM001]|&lt;CLID::StandAloneCluster&gt;&lt;NID::CCM001&gt;
08/14/2007 09:28:57.703 CCM|Db - DBL exception when loading StationRegistrationProfile table - restart CCM|&lt;CLID::StandAloneCluster&gt;&lt;NID::CCM001&gt;&lt;CT::2,100,82,1.1&gt;&lt;IP::&gt;&lt;DEV::&gt;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

-Running a version of code containing the fix for CSCsc29848, such as CM 4.1(3)ES120
-CM server in question isn&#39;t a member of a CallManager group.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Place the CallManager which won&#39;t start in a CallManager Group. This CallManager Group must be used by at least one Device Pool and this Device Pool must be used by at least one Device. Otherwise the Workaround will not function and the same symptoms will be seen.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk12127</guid>
</item>
<item>
<title>Error selecting IPMA Service on 7962 / 7965 IP Phones , Fixed CSCtc84711</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc84711</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When the user logs onto the phone using extension mobility then selectiing the IPMA service button, there is an error message button displayed on Managers IP Phone.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM version:  7.1.3.10000-11
Phone model:  7962 &amp; 7965
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc84711</guid>
</item>
<item>
<title>CUCM should not allow 6.x dialplans to be installed on 7.x , Fixed CSCsy74086</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy74086</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

From the CCMAdmin page, Call Routing &gt; Dial Plan Installer.  After clicking the install button when trying to install a dialplan the webpage does nothing.  It doesn&#39;t install and there is no error.  The dialplan can&#39;t be used because it never installs.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Running CUCM 7.x and have mistakenly installed a 6.x only dialplan on a 7.x CUCM server.  
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;

Contact TAC, they&#39;ll apply the workaround/fix for this to your server.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy74086</guid>
</item>
<item>
<title>End User Page Error: Access to the requested resource has been denied , Fixed CSCsu99802</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu99802</link>
<description>Issue:
Customer has a user with a last name of Shreffler. When adding this user to the CUCM End user page the CCM errors out with the following message:
&quot;Access to the requested resource has been denied.
The attempted action was a violation of security protocols and will not be allowed. Please try another action.&quot;

Cause:
If any text field on the Add End User Page contains the string HREF the above error will be generated.
&lt;br&gt;
Further Problem Details:
This problem effects all CUCM pages that allow text input.

Work Around: Try not to use HREF withing the string being added

Versions Effected: All CUCM 6.X

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu99802</guid>
</item>
<item>
<title>CUPS single-node enabled for replication causes DDRBlock ,   CSCsk67670</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk67670</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;

Users unable to login to ccmadmin on Presence server in single Presence node deployment because webpage won&#39;t load when accessing Presence server.

Users unable to login on the CUP client and get Unknown Login Failure

Power off/on of Presence server does not restore functionality
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Presence Server is running 1.0.3 version software in a single-node configuration.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

In a single-node configuration only, replication needs to be turned off using the following CLI commands:

utils dbreplication stop
utils dbreplication dropadmindb

Before a 2nd node is added to a single-node configuration to which the preceeding workaround has been applied, the following CLI command needs to be executed to turn replicatin back on:

utils dbreplication reset all
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
When logged on to a remove access account, the &quot;onstat -m&quot; command produces output which contains &quot;Blocked:DDR&quot;.  For example:

$ onstat -m
IBM Informix Dynamic Server Version 10.00.UC4X9   -- On-Line -- Up 03:32:28 -- 191944 Kbytes
Blocked:DDR

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk67670</guid>
</item>
<item>
<title>DOC: Default Device Profile cannot be assigned to Device /Device Profile , Open CSCtd14476</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd14476</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Cisco Unified Communications Manager Features and Services Guide had references to associating Default Device Profile to Users / Device / Device Profile
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None.

Ignore the statement where you need to associate Default Device Profile. You can associate Device Profiles to Users and not Default Device Profiles.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd14476</guid>
</item>
<item>
<title>IPMA Call Redirected To Manager Instead Of Busy Tone , Open CSCtd03873</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03873</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
-- A UCM upgrade from 7.0 to 7.1 has led to a change in the way IPMA
behaves when a call, offered to the manager is diverted to her assistant
who is already on another call with the busy trigger set to 1.
-- Call flow: IP Phone --&gt; IPMA CTI RP --&gt; Manager -- DivAll --&gt;
Assistant (Who is on another call).
-- On UCM 7.0, the caller hears a busy tone. On UCM 7.1, the call is
re-directed back to the manager.
-- The customer has a requirement for the busy trigger to be 1 and wants
the pre-upgrade behavior in UCM 7.1
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
-- The issue is reproducible in the lab:
   UCM versions: 7.1.2.20000-2 / CM 7.0.2.20000-5
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03873</guid>
</item>
<item>
<title>BAT: Removing Sidecar from Device does nothing , Fixed CSCtd28821</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd28821</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

if there is a sidecar configured and you use a BAT query and attempt to run an update to assign none, it doesn&#39;t do anything.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

All known version of CM for Linux
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Remove the sidecar at the device level.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd28821</guid>
</item>
<item>
<title>Update needed for E South America DST changes , Terminated CSCsg55762</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg55762</link>
<description>Symptom:
IP Phones in (GMT -3:00) Brasilia display time one hour ahead of the actual time. 
&lt;br&gt;
Conditions:
Issue is notices with the following ...
CCM Version 4.1(3) sr3b
Phone Load - 8.0(4.0)

I would assume that this affects all CCM Versions. 
&lt;br&gt;
Workaround:
Instead of using (GMT -3:00) Brasilia, you can use (GMT-3:00) Buenos Aires. This is specific to the Brasilia Timezone. 
&lt;br&gt;
Further Problem Description

Brazil does not use static daylight saving time dates. The start dates and the end dates for daylight saving time in Brazil are different each year. In the Microsoft products that are listed in the &quot;Applies to&quot; section, the default time zone for Brazil is (GMT -3:00) Brasilia. This article describes how to modify the default behavior of the start dates and the end dates for daylight saving time for the (GMT -3:00) Brasilia time zone to reflect the actual daylight saving time start and end dates for Brazil. 

The default start and end dates for daylight saving time for the (GMT -3:00) Brasilia time zone in Windows are as follows:
 Daylight saving time starts at 02:00 A.M. on the third Sunday in October. 
 Daylight saving time ends at 02:00 A.M. on the second Sunday in February. 

The &quot;actual&quot; daylight saving time start and end dates that are implemented in Brazil for the years 2006 and 2007 are as follows: 
 Daylight saving time starts on November 5, 2006. 
 Daylight saving time ends on February 25, 2007. 

The states that included are do Rio Grande do Sul, Santa Catarina, ParanA, SAo Paulo, Rio de Janeiro, EspArito Santo, Minas Gerais, GoiAs, Mato Grosso, Mato Grosso do Sul, and Distrito Federal. By using the default (GMT -3:00) Brasilia time zone settings, Windows-based computers in the affected states of Brazil do not correctly interpret time that is related to the transition to daylight saving time.

See MS Article ID 317211. This article was previously published under Q317211


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg55762</guid>
</item>
<item>
<title>Cisco Unified Reporting Database Status mismatch on Rhosts and Sqlhosts , Fixed CSCsk71021</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk71021</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Cisco Unified Reporting Database Status report always indicates there is a mismatch between the Publisher and the Subscriber nodes&#39; Rhosts and Sqlhosts files
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This condition could occur if the publisher is installed with an uppercase hostname but when the subscriber&#39;s are installed the hostname is entered in lowercase. This mismatch of uppercase and lower case entry during installation is valid since name resolution is not case sensitive however the Database Status reports that compare these files are performing at this time case sensitive checks.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

There is no workaround to get the report to perform none case sensitive matching. Perform manual inspection of the files using the detailed section of the report and as long as the hostnames are matching in the Rhosts and SQLhosts files the case mismatch could be ignored.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk71021</guid>
</item>
<item>
<title>CAR should include trunks in utilization reports , Open CSCsk87140</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk87140</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Calls through an H.323 or SIP Trunk do not show up in the gateway utilization
reports in the CDR Analysis and Reporting Tool on Cisco Unified Communications
Manager. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Using the Gateway Utilization report to monitor trunk utilization. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk87140</guid>
</item>
<item>
<title>CUCM 5.1.2.1106-1 Core file on cdcc ccFacilityInd , Fixed CSCsk24962</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk24962</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CallManager Core
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Looking at sdl trace and backtrace, maybe related to a coding issue for error checking. We have a scenario when processing a CcFacilityInd message and the ci is zero and the dSide is SIDE_NONE. When we got to function Cdcc::storeMonitorEntries(), we did not return when it was SIDE_NONE. Then we went into the iterator that might have cause this CM core.
 
From sdl-074, the last signal was  CcFacilityInd.
006615289| 2007/08/13 11:08:35.449| 004| SdlSig-Q | CcFacilityInd | tcc_intercept | Cdcc(4,100,159,19408) | Cc(4,100,160,1) | (4,100,124,1).26740-(*:172.29.113.14) | CI= 77044024 FDataType=0opId=0invokeId=0resultExp=0 NotifInd= ni.niid=39 ni.l=0 ni.nnd=0

(gdb) bt
#0  0x084ff167 in Cdcc::storeMonitorEntries (this=0xbc02f3d8,
    fSide=SIDE_NONE, fSsType=67108869)
    at /vob/ccm_tpl/linux/include/stlport/stl/_list.h:126
#1  0x084feb54 in Cdcc::sendSsDataInd (this=0xbc02f3d8, fCi=0,
    fCCMFeatureData=@0x3269b20, fSsType=67108869, fBcc=1600611584,
    connectedNumberInfo=1600611584, connectedNameInfo=1600611584)
    at ProcessCdcc.cpp:22585
#2  0x08506d7c in Cdcc::processQ931FacAndInvokeFeature (this=0xbc02f3d8,
    fOperationIeId=20, fInvokeId=1600611584, fQsigUtil=@0x326b2a0,
    fQ931Fac=@0xbc041268, fSide=SIDE_B, fBcc=BASIC_CALL_FACILITY,
    connectedNumberInfo=DoNotTakePrecedence,
    connectedNameInfo=DoNotTakePrecedence) at ProcessCdcc.cpp:24528
#3  0x084ed33b in Cdcc::processCCMFeatureData (this=0xbc02f3d8, fSide=SIDE_B,
    fBcc=BASIC_CALL_FACILITY, fConnectNumberInfo=DoNotTakePrecedence)
    at ProcessCdcc.cpp:19948
#4  0x08490763 in Cdcc::tcc_intercept_CcFacilityInd (this=0xbc02f3d8,
    s=@0xbc5837c8) at ProcessCdcc.cpp:9433
...
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk24962</guid>
</item>
<item>
<title>Cannot add user to group (java.sql.SQLException: Could not position ...) , Fixed CSCsy54534</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy54534</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Get error message:
Update failed. java.sql.SQLException: Could not position within a table (informix.enduser).
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Trying to add a User ID to a new User Group while logged in with that same UserID.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Login with another User ID so that you aren&#39;t trying to add a User Group to the same user you are currently logged in as.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy54534</guid>
</item>
<item>
<title>IP Phone Headset operation causes user confusion , Terminated CSCdr52509</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdr52509</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Headset and handset on IP Phone are always simultaneously active.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

The operation of the headset and display LEDs causes user confusion:

1. The Headset is always active during handset operation with
   no Headset LED lit (Headset expected to not be active).
 
2. Press the Headset button from Handset operation and Handset
   remains active until put back in the cradle.

3. When switching from Headset to Speaker, Headset LED remains lit
   but the headset is not functional (which is correct but the LED
   should not be lit).

4. When switching from Headset to Handset, the Headset LED goes
   out but remains active (Handset and Headset both work).

5. While using Headset during a call, the Headset LED remains lit
   when the other side terminates the call.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

No Workaround


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdr52509</guid>
</item>
<item>
<title>CAR Systemoverview report failure causing active partition full , Fixed CSCsl16440</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl16440</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

large number of files are accumulated under /usr/local/thirdparty/jakarta-tomcat/webapps/carreports/reports/pregenerated/SystemOverview, when monthly system overview report failes
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

configure CAR to run monthly system overview report
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Disable monthly system overview report.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl16440</guid>
</item>
<item>
<title>servM process Increases in memory use with every backup , Fixed CSCsk62547</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk62547</link>
<description>Description:

ServM process Vmsize increases on a daily basis over a period of time

Symptom:

ServM process Vmsize increases on a daily basis over a period of time irrespective
of whether a backup(DRF) is done or not.
&lt;br&gt;
Conditions:

Normal running condition(irrespective of whether a DRF is done or not)

Work-around:

Unknown.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk62547</guid>
</item>
<item>
<title>IDP Installer Page lists innacurate version information , Open CSCtc79181</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc79181</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

IDP Installer page is listing a 1.x IDP version as available to install despite a later version COP file having been applied.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This occurs when a 2.x or later IDP COP file is applied.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Verify via &quot;show version active&quot; (CLI) or Show-&gt;Software (OS Admin) that the correct version COP file has been applied, then proceed with the install as if the IDP Installer page was listing the correct version.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc79181</guid>
</item>
<item>
<title>CM 7.0 F&amp;S Gd shud mention SNR call to RD uses LRG of originating party , Fixed CSCsy27318</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy27318</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When using Mobile Connect (Single Number Reach) in conjunction with Local Route Groups, the Standard Local Route Group to the Remote Destination is being chosen based on the Device pool of the Calling party in terms of Mobile Connect. The Features and Services Guide for CallManager 7.x should mention that in the Interactions/Restrictions of either Local Route Groups or Cisco Unified Mobility
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Scenario recreated in lab
-------------------------------

Route Group 1 - contains only H.323 gateway 14.48.20.35 (configured with correct dial peers to complete the call to the remote destination) 

Route Group 2 - contains only H.323 gateway 14.48.20.112 (not configured with any dial peers, to complete the call to the remote destination)
 
Device pools :
 
Default (contains &#39;Route Group 1&#39;)
Device Pool 2 (contains &#39;Route Group 2&#39;)
 
Called party : 1013 (in device pool Default) - Has RDP too in device pool Default, and RD 4.2011
Route pattern : 4.2xxx points to route list &#39;Mobility Route List&#39;, which points to &#39;Standard Local Route Group&#39;
 
Scenario 1 :
 
Calling party : 1023 (in device pool Default) - call extended to 1013, and the Remote Destination 2011. Call routed successfully through gateway 14.48.20.35
 
Scenario 2 :
 
Calling party : 1027 (in device pool &#39;Device Pool 2&#39;) - call extended to 1013, but not the Remote Destination 2011. Routing of call through gateway 14.48.20.112 (LRG points to that of the device pool of the originating calling party), which has nothing configured, as hence call fails.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None, as of now. Once route list is found, the logic inside route list does not know it is SNR call or regular PSTN direct call. Therefore the Standard Local Route Group is being chosen based on the Device pool of the Calling party as usual.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy27318</guid>
</item>
<item>
<title>CAR not able to load CDR flat files after W1 migration , Fixed CSCsl69542</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl69542</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
After upgrade from callmanager 4.x to callmanager 6.0.1, CAR is not able to load CDR flat files into CAR DB. 
When CDR load failed, in CAR scheduler traces, one can see errors like: 
2008-08-08 00:04:14,349 ERROR [DailyCdrLoad] beans.EBErrorIdMap -save(): SQL Error while saving data (...) java.sql.SQLException: Unique constraint informix.pktbl_error_id_map_01) violated
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Upgrade from callmanager 4.x to callmanager 6.0.1 with CAR. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
First, please stop the CAR services (can be done from serviceablity web page or root): 
1. Cisco CAR Scheduler
2. Cisco CAR Web Service

Then, run the following queries from CLI:

1. run sql Select max(Error_Record_Id) from car:tbl_error_id_map
2. run sql Select max(Error_Record_Id) from car:tbl_billing_error

&lt;value A&gt; returned from #1, &lt;value B&gt; returned from #2. 

Take the bigger number of the two values returned. Let&#39;s assume it&#39;s &lt;value A&gt;. 

Then use the &lt;value A&gt; and run the following query:

*********************************** IMPORTANT NOTE!!! *******************************************
PLEASE BE SURE YOU ARE RUNNING THE UPDATE QUERY BELOW WITH THE &#39;WHERE&#39; 
CLAUSE ON THE &#39;MAX_ERROR_RECORD_ID&#39; COLUMN ONLY, OTHERWISE IT CAN 
CORRUPT OTHER COLUMNS IN tbl_system_preferences TABLE AND CAR 
APPLICATION WILL NOT FUNCTION PROPERLY AFTERWARDS!!! 
*******************************************************************************************************

Run sql update car:tbl_system_preferences set param_value= &lt;value A+1&gt; where param_name=&#39;MAX_ERROR_RECORD_ID&#39;

Finally, start the CAR services back again: 
1. Cisco CAR Scheduler
2. Cisco CAR Web Service

Now, you can check the CAR tables records count from CAR&#39;s page of &quot;Manual-Purge&quot; -&gt; 
&quot;Table Information&quot; periodically, make sure CAR starts loading CDR records into CAR DB 
properly after applying the workaround.  
Please note that depending on the number of pending/left-over CDR flat files available (after 
the time of the last loading failure), it can take some time to finish loading all of the pending 
CDR records back into CAR DB.  So, check the &quot;Table Information&quot; periodically to see if 
the latest CDRs are loaded yet.  Another tips is to change the CAR scheduler trace level to 
&quot;INFO&quot; if it is not already done so, this will speed up CDR loading, too. 


FOR EXAMPLE: 
======================================================= 
/usr/local/cm/bin/controlcenter.sh &quot;Cisco CAR Web Service&quot; stop
/usr/local/cm/bin/controlcenter.sh &quot;Cisco CAR Scheduler&quot; stop

If &quot;max(Error_Record_Id) from car:tbl_error_id_map&quot; returns 100, and 
&quot;max(Error_Record_Id) from car:tbl_billing_error&quot; also returns 100, then 
please update &#39;MAX_ERROR_RECORD_ID&#39; as 101, such as: 

run sql update car:tbl_system_preferences set param_value=&#39;101&#39; where param_name=&#39;MAX_ERROR_RECORD_ID&#39;;

/usr/local/cm/bin/controlcenter.sh &quot;Cisco CAR Web Service&quot; start
/usr/local/cm/bin/controlcenter.sh &quot;Cisco CAR Scheduler&quot; start
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

When CDR load failed, in CAR scheduler traces, one can see errors like: 

2008-08-08 00:04:14,349 ERROR [DailyCdrLoad] beans.EBErrorIdMap -save(): SQL Error while saving data (...) java.sql.SQLException: Unique constraint informix.pktbl_error_id_map_01) violated

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl69542</guid>
</item>
<item>
<title>CallManager Network Services blocked after heavy load , Fixed CSCsr69611</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr69611</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CallManager service stops accepting new registration requests. New or old phones are not able to establish new TCP/TLS connection with Callmanager service.

&lt;b&gt;show network status search 2000&lt;/b&gt; indicates several new connections have messages stuck in the Receive Queue.

For example:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address             State
tcp        53      0 10.87.11.10:2443            10.87.29.10:59575           ESTABLISHED 20177/ccm           off (0.00/0/0)
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This rare condition is observed after experiencing one or more SDL Link Out of Service events which could be caused by a network outage that interrupts communication in between Callmanager nodes. This event could trigger an unexpected condition where CallManager&#39;s Network Services operations gets blocks and it stops receiving new messages over the network.

In this condition where CallManager Service&#39;s Network Services thread is not operational a quick telnet in to SCCP signaling port 2000 could also confirm that it is blocked and not processing any incoming messages. When experiencing this failure the telnet attempt will never connect. Under normal conditions it should connect and then Closed automatically.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None. CallManager service needs to be restarted in order to restore Network Services functionality.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

There is also evidence of this issue in the CM SDL traces. Look for a large number of StationResponseTimer from SdlTimerService to numerous StationD processes.  This regex may help:
StationResponseTimer.*?StationD.*?SdlTimerService

In the results verify the line does not end with &quot;Destination process does not exist&quot;.  For lines where this message occurs the StationD process was already shutdown most likely by a TCP FIN or TCP RST inbound from the network.  If there are large number of these type of events there may be an issue with a firewall device between CUCM and the SCCP endpoints.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr69611</guid>
</item>
<item>
<title>Client Disconnect causes temporary spike in ThreadCount , Fixed CSCsm40545</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm40545</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
ThreadCount for ACServer goes up as soon as there is a n/w outage. 





&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
N/w connectivity issues between ACServers and between ACServer and ACClient



&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restart ACService


&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm40545</guid>
</item>
<item>
<title>FTP incompatibility causes &quot;Not enough disk space&quot; upgrade failure , Fixed CSCsi91410</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi91410</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
An upgrade fails indicating there is not enough disk space to complete the upgrade even though there is enough disk space.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
An upgrade is done using remote method via FTP.




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use a different upgrade method (such as SFTP or LOCAL) or use different FTP server software.



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
The problem here is that the FTP server software returns back a negative size value when CUC&#39;s FTP client issues a LIST FTP directive to the server.  This causes CUC upgrade software to believe the size of the file is much larger than it really is and it causes the software to think there is not enough disk space to contain the file.  The negative size value is most likely due to the fact that the FTP server software cannot deal with file characteristics where the file size is &gt;2GB.  CUC development has noticed this in CUC software since files of that size are not commonly downloaded using FTP.














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi91410</guid>
</item>
<item>
<title>H323 Gateway lost from route-group route-list , Terminated CSCsz17342</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz17342</link>
<description>Symptom:
cucm 6.1.2.1112-2
H323 Gateway lost from route-group route-list during outbound call.
Inbound calls work.
Callmanager does not send H.323 Setup to gateway.  
&lt;br&gt;
Workaround:

changed device pool on gateway.  reset gw from cucm admin page.
changed back to correct device pool on gateway. reset gw from
cucm admin page.
Now outbound calls work
&lt;br&gt;
Further Problem Description:

see following in cucm trace
CCM|RouteListCdrc::whichAction -- DOWN (Current
Group) =
CCM|RouteListCdrc::executeRouteAction: SKIP_TO_NEXT_MEMBER

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz17342</guid>
</item>
<item>
<title>Unable to switch versions , Fixed CSCsm10419</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm10419</link>
<description>
Symptom: Switch version fails with the error: &quot;Sync after switch version failed!&quot;.
&lt;br&gt; 
Conditions: Switch versions from:

 - Cisco Unified Communications Manager 6.1.1.9901-36 to 6.1.1.1000-1
 - Cisco Unified Presence Server 6.0(5) to 7.0(5)
&lt;br&gt; 
Workaround: 

 - contact Cisco TAC for assistance to use the remote support account
 - rm /tmp/dbname and try switch versions again



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm10419</guid>
</item>
<item>
<title>CAR Fails to Update Database URL after Hostname Change , Fixed CSCsv39851</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv39851</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Not able to access CAR pages, CDR records not getting loaded to CAR db. Logs can show errors like:

Caused by: java.sql.SQLException: com.informix.asf.IfxASFException:
Attempt to connect to database server (oldhostname_ccm6_1_2_1000_13) failed.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This can occur after changing the server hostname following the documented procedure. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

1. With root access, backup the existing file of /usr/local/cm/conf/dbl/prefs.xml on CUCM server. (i.e. cp /usr/local/cm/conf/dbl/prefs.xml /usr/local/cm/conf/dbl/prefs.xml.BAK) 

2. Manually update/modify /usr/local/cm/conf/dbl/prefs.xml. Change the hostname &amp; informixserver values for the &#39;jdbcurl_car&#39; entry to match that of the hostname &amp; informixserver values listed in &#39;jdbcurl&#39; entry. Save the changes and exit.
For example,  if you see prefs.xml with something like:  
&lt;entry key=&quot;jdbcurl_car&quot; value=&quot;jdbc:informix-sqli://OLDHOST:1500/car:informixserver=oldhost_ccm6_1_2_1000_13;user=dbcarsch;IFX_LOCK_MODE_WAIT=20&quot;/&gt;
&lt;entry key=&quot;jdbcurl&quot; value=&quot;jdbc:informix-sqli://NEWHOST:1500/ccm6_1_2_1000_13:informixserver=newhost_ccm6_1_2_1000_13;&quot;/&gt;

Change jdbcurl_car line to:
&lt;entry key=&quot;jdbcurl_car&quot; value=&quot;jdbc:informix-sqli://NEWHOST:1500/car:informixserver=newhost_ccm6_1_2_1000_13;user=dbcarsch;IFX_LOCK_MODE_WAIT=20&quot;/&gt;

This can be done by: 
/usr/local/cm/bin/pryftool --system cm --hive dbl --set jdbcurl_car=&quot;jdbc:informix-sqli://NEWHOST:1500/car:informixserver=newhost_ccm6_1_2_1000_13;user=dbcarsch;IFX_LOCK_MODE_WAIT=20&quot;

3. Afterwards, restart &#39;Cisco CAR Web Service&#39; &amp; &#39;Cisco CAR Scheduler&#39; services.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv39851</guid>
</item>
<item>
<title>Cisco TSP crashes when app sends multiple LineOpen/PhoneOpen , Fixed CSCsk99178</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk99178</link>
<description>Symptoms:
TSP Crash/Freeze when application sends multiple LineOpen/PhoneOpen against the same device at the same time.
&lt;br&gt;
Conditions:
TSP 5.1(1.3-6)
&lt;br&gt;
Workaround:
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk99178</guid>
</item>
<item>
<title>TAPS doesn&#39;t uninstall COM object , Open CSCso43781</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso43781</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

Similar to CSCsk68493 for BAT, and happens after this workaround.
CM ES/SR and OS SR Installations exit during StopServices while it is stopping
the COM Objects, when shutting down IIS (Default Web Site//root/TAPS).

14:22:23: CRITICAL ERROR: Uninitialized variable - &quot;NumAddFail&quot; 






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CallManager v4.x with BAT/TAPS




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Please follow the same workaround for this IIS COM+ application object:

To delete the TAPS COM+ objects
 
 1. Go to Start &gt; Programs &gt; Administrative Tools &gt; Component Services
 2. Expand Component Services-&gt;Computers-&gt;My Computer-&gt;COM+ Applications
 3. In the right hand side window you will see IIS com objects for TAPS
 4. Right click the object and click on &#39;Properties&#39;
 5. Go to the &#39;Advanced&#39; tab
 6. Under &#39;Permission&#39; uncheck &#39;Disable deletion&#39;
 7. Click on ok
 8. Delete that object.

Also delete IIS-{Default Web Site//root/TAPS} object manually.

Make sure that the following services are running on the server:
- All of Cisco services except CSA
- COM+ Event System
- DC Directory Server
- Distributed Transaction Coordinator
- IIS Admin Service
- World Wide Web Publishing Service




&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso43781</guid>
</item>
<item>
<title>CM 5.0 - not able to add static routes , Open CSCse56091</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse56091</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
right now, callmanager 5.0 is not capable of adding static routes when default gateway that is not able to handle routing protocols is present.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Callmanager 5.0
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
set the default gateway to a device that can handle routing protocols

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse56091</guid>
</item>
<item>
<title>process core due to File size limit exceeded , Fixed CSCsk21012</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk21012</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Services started by servM trying to write the servM&#39;s deleted log file.  RTMT
alarms for coredump file generated.
&lt;br&gt; 
&lt;B&gt;Conditions:&lt;/B&gt;
When a chatty child process of servM writes to a deleted log file, and
the file limit crosses a limit, the process terminates.

This can affect any process started by ServM including ccm, cti, ac, and others.
 
For ccm process this condition is exacerbated by failed device registration attempts.  2 vg248s with all 48 ports failing to register will cause CM to core within a 14 day period.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restart the service.
&lt;br&gt; 
&lt;B&gt;Further Problem Description:&lt;/B&gt;
&lt;b&gt;utils core analyze&lt;/cmdBold&gt; cli command against result core file
includes the following as part of the output::

Program terminated with signal 25, File size limit exceeded




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk21012</guid>
</item>
<item>
<title>NZDP Pattern Failures for 018 &amp; 0161! , Fixed CSCtd11587</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd11587</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

NZDP Pattern Failures for 018 &amp; 0161!
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

its applicable to all the versions.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd11587</guid>
</item>
<item>
<title>Unable to create remote access account , Fixed CSCtb52188</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb52188</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Unable to create remote access account through the CLI.  Output will look similar to:
admin:utils remote_account enable
admin:utils remote_account status

Error reading response file for status (30)
Remote Support
Status         : disabled
Decode Version : 1
admin:

Other times when you SSH into a server, you may see java exceptions such as:
java.io.FileNotFoundException: /var/log/active/platform/log/cli00024.log (No space left on device)
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Software Release Version: 7.0.1.11000-2
Platform Release Version: 2.0.0.1-1
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
To enable a root account you need to free some space on the server.  One way to accomplish this is by lowering the Low (LogPartitionLowWaterMarkExceeded) and High (LogPartitionHighWaterMarkExceeded) Mark threshold for disk space. This may allow you to quickly create and enable the remote access account to allow you to gain root access to investigate why the disk is full.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb52188</guid>
</item>
<item>
<title>CEF core due to invalid incoming QBE message header , Fixed CSCso02381</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso02381</link>
<description>&lt;B&gt;Symptoms:&lt;/B&gt;
Cisco Extended Function (CEF) stopped under specific condition.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
CEF receives invalid message.  
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
 Upgrade to a version with the fix.
&lt;br&gt;

&lt;B&gt;Further Information:&lt;/B&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso02381</guid>
</item>
<item>
<title>No video when inter-op between MTP and HD H323 video EP over SIPICT , Fixed CSCsz40502</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz40502</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When SCCP video EP calls H323 Tandberg HD video EP over SIPICT, if there is pass thru capable MTP or TRP inserted in the caller cluster, there is no video.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Pass thru capable MTP or TRP inserted in the calling cluster, and terminating party is H323 video endpoint with higher H264 profile level (e.g. Tandberg HD).
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Disable H264 or remove MTP.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

N/A.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz40502</guid>
</item>
<item>
<title>Stored procedure was not replaced correctly on Sr1 Installation , Fixed CSCsb76677</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsb76677</link>
<description>

Stored procedure was not replaced correctly on Sr1 Installation

&lt;B&gt;Symptom:&lt;/B&gt;

Phones failed to register if we reset Phone from CCMAdmin or Hardreset. CCM DBL logs print the following:
08/30/2005 23:37:33.479 DBLCCM|   CConnectionHolder::getString[CFoFDestination] *ERROR* [libodbc++]: Column CFoFDestination not found in result set
08/30/2005 23:37:33.479 DBLCCM|--&gt;CDBLException::CDBLException(ex=0x00000040, moreInfo=[libodbc++]: Column CFoF 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Installing 4.1(3)sr1.   Stored prodecdure being updated while SQL has locked it.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Short Term: Restart of ccm.exe service.
Long Term - Reinstall 4.1(3)sr1
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Sr1 installer failed to update the Stored procedure mentioned above due to SQL briefly locking it.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsb76677</guid>
</item>
<item>
<title>the order of signal &quot;MXCapabilitiesIncoming&quot; and &quot;MXFarEndCapsIncoming &quot; , Terminated CSCtd04124</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd04124</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;

This is a    H323 (FastStart, MTP checked ) ----MTP - MTP -----H323 (FastStart, MTP checked call.)
In this call, I notice that both H245 IF has received MXCapabilitiesIncoming and MXFarEndCapsIncoming signal.
The problem is that both signals have assigned the video capability into mPeerVidDataCap. And as you can see  below, the capability can be MTP&#39;s cap or FarEnd &#39;s cap.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

The issue was found testing with CUCM 6.1.4 The issue does not happens with CUCM 6.1.1 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

H245Interface.(110) (good call)
 
1
SdlSig-I
MXCapabilitiesIncoming
MediaExchange(1,100,110,100)
2009/10/07-13:14:28.152

2
SdlSig-I
MXFarEndCapsIncoming
MediaExchange(1,100,110,100)
2009/10/07-13:14:28.153

 
 
H245Interface.(111)(failed call)
fastStart
1
SdlSig-I
MXFarEndCapsIncoming
MediaExchange(1,100,110,103)
2009/10/07-13:16:30.802

2
SdlSig-I
MXCapabilitiesIncoming
MediaExchange(1,100,110,103)
2009/10/07-13:16:30.802

 
 
 


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd04124</guid>
</item>
<item>
<title>CUC Unable to mount local file system when attempting to install locales , Fixed CSCsr20224</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr20224</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CUC Install Software page reports &quot;Unable to mount locale file system&quot; and console shows &quot;ide-scsi: hdc: unsupported command in request queue (0)&quot; when attempting to install locale files.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Unity Connection 2.1 on a MCS7845I2-K9-UCA1.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Log on as root and issue the following commands (ignore errors if any):
rm -f /dev/cdrom
mknod /dev/sr0 b 11 0
ln -sf /dev/sr0 /dev/cdrom
** Changes will be lost on reboot and need to be reapplied **
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
This issue is not observed on HP servers when using the same install media.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr20224</guid>
</item>
<item>
<title>Status flags need to be cleared at restart , Fixed CSCsl57661</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl57661</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Loader failing.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

MANUAL_PURGE_STATUS flag is set as 1 in tbl_system_preferences table.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Reset the MANUAL_PURGE_STATUS value back to 0. Run the following command as a workaround

&lt;b&gt;run sql update car:tbl_system_preferences set param_value=0 where param_name=&#39;MANUAL_PURGE_STATUS&#39;&lt;/b&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl57661</guid>
</item>
<item>
<title>Got error &quot;Login is unavailable (210)&quot; when select EM URL , Fixed CSCsz02222</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz02222</link>
<description>Symptom: 

Extension Mobility App will fail to initialize.  Eventually this will cause the Databe to block access.
&lt;br&gt;
Condition: 

When Extension Mobility App trys to initialize it logs into the Database as unknown user.

10:31:42  listener-thread: err = -951: oserr = 0: errstr =
Unknown@DCCCM01: Incorrect password or user Unknown@DCCCM01 is not known
on the database server.
10:31:44  listener-thread: err = -951: oserr = 0: errstr =
Unknown@DCCCM01: Incorrect password or user Unknown@DCCCM01 is not known
on the database server.
10:31:45  listener-thread: err = -951: oserr = 0: errstr =
Unknown@DCCCM01: Incorrect password or user Unknown@DCCCM01 is not known
on the database server.

Work around:  

There is no work around at this time.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz02222</guid>
</item>
<item>
<title>Personal address book does not stop processing application dial rules , Open CSCtd31786</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd31786</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;






Personal Address book is processing application dial rules differntly compared to click 2 call. It looks like it keeps processing where as it should stop processing once it found a match
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;




example:
+ Application Dial Rule #1
 Number Begins With: 00
 Number of Digits: 6
 Total Digits to be Removed: 1
 Prefix With Pattern: 0
+ Application Dial Rule #2
 Number Begins With: 0
 Number of Digits: 6
 Total Digits to be Removed: 0
 Prefix With Pattern: 0
(+ translation pattern 00XXXX to strip 00 and so it goes to 4-digit extn on phone)

I call number 001003 from IP Phone 1001 using:
+ with click to call (casanova): Call works (display on phone shows call to 1003) 
+ with PAB: call fails (display on phone shows call to 0001003)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Users should add numbers exactly as they should be dialed when entering into the Personal Address Book. 


none
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;













</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd31786</guid>
</item>
<item>
<title>BARS: Warning generated when backing up Service URL , Fixed CSCsd39789</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd39789</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
During backup of a system, the BARS log will generate the warning&lt;BR&gt;
&lt;I&gt;[Warning] Failed to copy URL Services page from remote machine &lt;machine-name.company.com&gt;. Files can be backed up only from backing up server. Backup URL Services page manually.&lt;/I&gt;
&lt;br&gt;
&lt;B&gt;Conditions&lt;/B&gt;
There are 2 conditions that can cause this:

1. the Services URL under enterprise parameters is confiugred using an IP Address.
BARS will attempt a reverse DNS lookup of this IP to get a name and compare that to the local hostname.  BARS uses the equivalent of &#39;nslookup&#39; so DNS resolution is required.  BARS does not use default windows name resolution that you get with ping -a &lt;ip_address&gt;.  If the reverse DNS lookup returns an FQDN such as myserver.mycompany.com the BARS comparison will fail.

2. the Services URL under enterpriese parameters is configured as a fully qualified domain name.
This warning will be generated if the hostname specified in the Service URL is a fully qualified machine name.  The BARS application will use only the local host name when determining if the local host is the location of the Services  URL.   Backup completes successfully after this warning.
&lt;br&gt;
&lt;B&gt;Workaround&lt;/B&gt;
For condition 1 above: confiugre DNS server to perform reverse resolution and only return hostname

For condition 2 above: Change the Service URL from a fully qualified host name to the hostname of the server.  

Then rerun the backup.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsd39789</guid>
</item>
<item>
<title>speed dial do not break dial tone ,   CSCtd11303</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd11303</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;







CCM is configured with &quot;Speed Dial Await Further Digits&quot; parameter is set to True
Speed dial do not break the dial tone
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;





1-	CCM is configured with &quot;Speed Dial Await Further Digits&quot; parameter is set to True
2-	A sped dial is configured with 15
3-	A route pattern for PSTN is 15XXXXXXXXXX
1-	Press speed dial
2-	Get dial tone
3-	Start to dialing 5554441234 the dial tone do not break until finished to dial the full number. Them the call goes normal.

If using the handset 

1-      Take handset off hook
2-      Press speed dial, get a dial tone
3-      Dial 5, and immediately the dial tone stops. 
4-      Dial the final digits, aka 55441234 and the call goes normal. 
&lt;br&gt;




&lt;B&gt;Workaround:&lt;/B&gt;




none
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;


























</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd11303</guid>
</item>
<item>
<title>User Authentication over SSL link to LDAP fails for CTI Manager. , Fixed CSCso60232</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso60232</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CUPC end points in desk phone mode use QBE to establish connection to CUCM. When CUPC end point comes up CUCM authenticate the user with LDAP as configured in System-&gt;LDAP pages. When CTI Manager try to authenticate the user with LDAP over SSL connection it fails. CTI Manager complains Unknown CA.

The User Authentication passes over SSL link to LDAP by CUCM user administration, CUP authentication etc.  It fails only from CTI Manager.

CUPC end points in Desk Phone mode can not come up because of this issue.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso60232</guid>
</item>
<item>
<title>Using TAPS/BPS in 5.X/6.X requires double the licenses , Fixed CSCsi43015</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi43015</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Deploying phones via TAPS requires twice the number of licenses a cluster needs.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

na
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

purchase double the licenses

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi43015</guid>
</item>
<item>
<title>Japan  IDP stripping 1DIGIT-AREA-CODE , Open CSCtd14041</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd14041</link>
<description>1DIGIT-AREA-CODE being stripped in 6.1.3.3201-1 for japan dial plan. 

Works in 6.1.3.3000-1. Stopped working after upgrade.

Issue was found in the Internation Dial Plan.  

Customer scenario:
6.1.3.3201-1  1 pub , 1 sub
9.@ route pattern configured with Route filter LONG-DISTANCE-ACCESS and   VOIP-050-ACCESS 

DDI instruction : Predot configured at the Route Pattern or at the Route filter/Route Group



&lt;B&gt;Symptom:&lt;/B&gt;

1DIGIT-AREA-CODE being stripped in 6.1.3.3201-1 for japan dial plan. 

Works in 6.1.3.3000-1. Stopped working after upgrade.

Issue was found in the Internation Dial Plan.  
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;

6.1.3.3201-1  
9.@ route pattern configured with Route filter LONG-DISTANCE-ACCESS and   VOIP-050-ACCESS 
DDI instruction : Predot configured at the Route Pattern or at the Route filter/Route Group
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;


&lt;B&gt;Workaround:&lt;/B&gt;

Replace the 9.@ route pattern with 9.XXXXXXXX pattern.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd14041</guid>
</item>
<item>
<title>You are not a valid Mobile Phone user Displayed with Mobility softkey , Fixed CSCsg64857</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg64857</link>
<description>&lt;br&gt;Condition

While hitting the Mobility Softkey when in Connected State, the following is displayed on Ip Phone &quot;You are not a valid Mobile Phone User&quot;
&lt;br&gt;
Workaround

Assign a user id to the actual MM Profile Line created.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg64857</guid>
</item>
<item>
<title>MCS 7816-H3 servers have performance issues showing  High %  I / 0 Wait , Fixed CSCsm83603</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm83603</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

MCS-7816-H3 servers will experience HIGH %IO WAIT
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

MCS-7816-H3 servers running any VOS (Voice Operating System) based version of an Application, like CM 6.1, will experience performance issues due to high %IO WAIT. 

This is caused by malfunctioning BIOS settings meant to enable the Hard Drive Write Cache

&lt;B&gt;Solution/Workaround:&lt;/B&gt;
1. The permanent solution Upgrade to a version that contains a BIOS upgrade, as indicated by the Integrated-In Field of this defect

2. A suitable workaround is to apply the following COP file, which does NOT contain a BIOS upgrade, but instead contains a utility that enables Write cache outside of the BIOS settings.
-ciscocm.CSCsm83603EnableCache7816-1.1.cop.sgn
-A readme for the above COP file can provide additional information
&lt;br&gt;

&lt;B&gt;Further Problem Description:&lt;/B&gt;
-The BIOS Settings are set correctly, but they do not function properly

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm83603</guid>
</item>
<item>
<title>Bat.xlt Suport With MS Excel 2007 , Open CSCtb11811</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb11811</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Microsoft excel 2003 used to have a limitation to a maximum of 256 columns. Microsoft excel 2007 increase this limitation to 16000. 
 
Customer is experiencing problems when using the BAT.xlt file to create user device profiles if he add more than 256 columns. He received the following error.
The total number of columns on the sheet will exceed 256(as per limitation in MS Excel). 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
When bat.xlt is opened with MS Excel 2007 and more than 256 columns need to be added
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None at the moment. PERS.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb11811</guid>
</item>
<item>
<title>utils dbreplication reset for single node fails, reset all works , Fixed CSCsy60287</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy60287</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When trying to fix replication, if you issue the CLI command &quot;utils dbreplication reset &lt;nodename&gt;&quot; 
the node name listed does not receive the replication reset signal and replication stays broken.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This is present in all existing versions of 6.1(3).
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Use &quot;utils dbreplication reset all&quot; instead of specifying the nodename directly.  This should not 
impact the working nodes and the broken node will receive the reset signal.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy60287</guid>
</item>
<item>
<title>&quot;Hunt group&quot; not translated to German , Fixed CSCtc96791</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc96791</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
When logging off hunt group in CUCM 7.x with German locales we are getting message &#39;aus Huntgroup abgemeldet&#39; instead of &#39;aus Sammelanschlu abgemeldet&#39;.
Sammelanschlu should be German translation for hunt group.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 7.x, any phone models
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc96791</guid>
</item>
<item>
<title>CSS can not be deleted, but there is no dependency records , Fixed CSCsu96442</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu96442</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
A CSS can not be deleted, but there is &quot;no dependency records&quot; for the CSS

An error message comes up on CallManager Administration at this time.

The error message is:
The pkid column in the callingsearchspace table in the database is being referenced from another table. Please check the dependency records and remove the reference and the try the delete again.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
- Calling Search Space
- Bulk Administration
- After the Line Template is dissociated with a Phone Template
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
Remove a hidden Line Template, first.
1. Select a Phone Template on Bulk Administration
Bulk Administration &gt; Phones &gt; Phone Template
2. Click Line[1] - Add a new DN
3. Select Back to Find/List on Line Template Configuration
4. Delete the Line Template


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu96442</guid>
</item>
<item>
<title>ASN.1 ROSE OID Encoding and Calling Name in setup msg using PRI QSIG , Fixed CSCtc68166</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc68166</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Outbound calls over QSIG gateway fail 
or 
supplementary services like calling name, connected name, callback etc.. fail
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM 7.X and higher

QSIG configuration :
Serviceparameter - QSIG variant = ECMA
Serviceparameter - ASN.1 ROSE OID Encoding  = ECMA (GLOBAL)

Gateway - QSIG Variant = No Changes
Gateway - ASN.1 ROSE OID Encoding  = No Changes
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Configure on gateway

Gateway - QSIG Variant = ECMA
Gateway - ASN.1 ROSE OID Encoding  = ECMA (GLOBAL)
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

With the configuration documented under conditions, CUCM will encode the Facility/Rose Invoke as ECMA / Local while it is expected to be ECMA / Global. (as configured on the remote PBX)
Depending on the remote PBX configuration/type the call will get released or Rose Invoke will get rejected.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc68166</guid>
</item>
<item>
<title>CUCM should allow selection of CSS used for redirect , Open CSCso91760</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso91760</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

A redirect performed by a Cisco or 3rd party application via CTI/QBE may use an unexpected Calling Search Space which results in unexpected or blocked call routing behavior.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

A JTAPI application can explicitly specify the Calling Search Space (CSS) of a Redirect using any one of the following three values.

ADDRESS_SEARCH_SPACE
This indicates that the redirect should be done using the search space of the redirect controller&#39;s address.

CALLINGADDRESS_SEARCH_SPACE
This indicates that the redirect should be done using the search space of the calling address.

DEFAULT_SEARCH_SPACE
This indicates that the redirect should be done using the search space that is the default for the implementation. The default is to use the calling address&#39;s search space.

Otherwise, the application can leave the CSS parameter of the Redirect to a null value which will also result in CUCM using the original calling device&#39;s CSS.

By default, when an application does not explicitly set the CSS of a Redirect to ADDRESS_SEARCH_SPACE or CALLINGADDRESS_SEARCH_SPACE, CUCM will use the original calling device&#39;s CSS.

This behavior is NOT intuitive and not known and/or understood by 99% of the customer/partner architects/administrators who design/implement these solutions. This knowledge gap is likely due   to the fact that this behavior is not well documented (if documented at all).

For example, even the latest CUCM 6.X SRND does NOT mention anything about which CSS is used during a JTAPI initiated Redirect even though the SRND goes into great depth about which CSS is used for most (if not all) other scenarios (for Device, Line, Call Forwarding, etc)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/6x/uc6xsrnd.pdf

Therefore, most Cisco Unified Communications customer/partner architects/administrators would assume that the CSS of the device which is performing the redirect (ie CTI RP, CTI Port, Agent Phone, etc) would be used rather than the CSS for the original calling device.

It seems that the application should always explicitly set the CSS within the redirect if they want to guarantee that the correct CSS is used.  But when the application sets the Redirect CSS to &quot;DEFAULT_SEARCH_SPACE&quot; or leaves it null CUCM should have the ability to decide (via a new configuration parameter) if the original calling device CSS or redirecting device CSS is used.

This is a request for an enhancement which would allow a CUCM administrator to configure which CSS CUCM should use (original calling device CSS or redirecting device CSS) IF the CSS parameter of a Redirect is NOT explicitly set to &quot;ADDRESS_SEARCH_SPACE&quot; or &quot;CALLINGADDRESS_SEARCH_SPACE&quot; by the application.   The default setting of the new configuration parameter should be set to a value which results in the current default behavior of using the CSS of the original calling device. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Some applications have a configuration parameter which be set to specify weather to use the original calling device CSS or redirecting device CSS.

Otherwise, a redesign of the CUCM dial plan may be required to achieve expected call routing for CTI redirects.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso91760</guid>
</item>
<item>
<title>CCMCIP device query is case sensitive, while CUCM login is not , Fixed CSCsy15719</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy15719</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 
CUCM user login succeeds, but CCMCIP device list retrieval fails for same user.
CUCIMOC uses CCMCIP login and can run into this issue.  When it does, following
error is displayed during login &quot;Failed to sign in. Failed to connect to CCMCIP
authentication server&quot; 
&lt;br&gt;
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 Situation occurs when user&#39;s CUCM user ID case differs from CCMCIP database
entries for this user.  CUCM login is NOT case sensitive, where CCMCIP is.
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 Standardize the case for user IDs (all lower, for example).
&lt;br&gt; 
 &lt;B&gt;Further Problem Description:&lt;/B&gt;
 
 None.
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy15719</guid>
</item>
<item>
<title>AC Client Unable to Transfer Call without First going into Connect State , Fixed CSCsc65234</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc65234</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Unable to Transfer Call from AC Client GUI.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

AC Client User is trying to transfer (drag and drop) a call into a speed dial while the call is still rining.
And Transfer fails.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Go offhook on the rining call and then do the transfer.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsc65234</guid>
</item>
<item>
<title>MGCP FXS port call failure when only one port is configured , Fixed CSCsy04822</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy04822</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Calls to MGCP gateway fail. Specifically when the call is answered by MGCP port.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Seen when a gateway has multiple ports enabled for MGCP, but CUCM is configured for only few of the ports.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Configuring all the ports in CUCM should resolve the issue.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy04822</guid>
</item>
<item>
<title>Calls from Unity AA display VM port number on phone display prompt line , Fixed CSCse49959</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse49959</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When Unity transfer mode is set to &quot;release to switch&quot; (blind transfer), calls to IP phones transferred from Unity Auto Attendant display the Unity VM port number on the phone&#39;s display prompt line (just above softkeys).

This is an issue with the 7920 wireless phone because users rely on the display prompt line to see 10-digit Caller ID numbers. The 7920&#39;s calling plane is too small to display 10-digit numbers.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Calls to IP phones from Unity Auto Attendant.
CM 4.1(3),  Unity 4.0(5), and IP phone 7920 load 3.0 - also affects other versions.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCse49959</guid>
</item>
<item>
<title>Gateway Utilzation CAR Jsp pages are throwing error , Fixed CSCso17334</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso17334</link>
<description>                RELEASE NOTE TEMPLATE                       

Symptom:

Gateway Utilzation CAR Jsp pages are throwing error
&lt;br&gt;
Conditions

Gateway Utilization CAR pages are throwing error. This issue is intermittent and sometimes we are able to see the pages without error.

Route &amp; Line Group Utization having Day of Week &amp; Day of Month reports are throwing datadbase error for a particular range of date (One day Gap). The same can be seen for Gateway Utilization , Route / Hunt List &amp; Route Pattern / Hunt Pilot Utilzation links.
&lt;br&gt;
Workaround

Login to the CAR pages by typing the user name exactly as it is configured (case-sensitive).


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso17334</guid>
</item>
<item>
<title>Callerid matching does not work with MVA using hairpinning configuration , Fixed CSCsl85853</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl85853</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

When having hairpin configuration for Mobile Voice Access, the caller id of the remote destination is not recognised by IVR.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

When having hairpin configuration for Mobile Voice Access, the caller id of the remote destination is not recognised by IVR, so user cannot be identified without the caller id.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Enter the Remote destination on the prompt to identify the remote destinationan and rest works fine. 
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

&quot;When using hairpinning with Mobile Voice Access, users calling into the system will not be automatically identified by their callerID.  Instead users will have to manually key in their remote destination number prior to entering their PIN number.&quot;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl85853</guid>
</item>
<item>
<title>User insert or update via BAT can fail at permission group assignment , Open CSCtd03607</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03607</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

User insert or update via BAT can fail if permission groups are to be assigned to the user. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This can happen if user groups are not listed sequentially in the bat file.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Make sure that in the bat file the list of permission groups starts at position 1 (&quot;USER GROUP 1&quot;) and that there are no empty positions between the groups.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03607</guid>
</item>
<item>
<title>Resume from MMOH, call has 1-way audio or 3 sec delay for 2 way audio , Fixed CSCsz51676</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz51676</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Call resume after Multicast MOH hold, has one way audio, or 3 seconds delay to re-establish two way audio.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Multicast MOH over ICT/H.323 trunk which is supported since CUCM 7.1.2

&lt;B&gt;Wokaround:&lt;/B&gt;
Use Unicast MOH instead

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz51676</guid>
</item>
<item>
<title>CUCM Admin password reset gives false negative after unsuccessful reset , Open CSCtd17258</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd17258</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Receive error &quot;Error: the password has NOT been reset.&quot; when providing an valid password to the admin password recovery tool
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Using the OS admin password recovery procedure where at some point previously on this system an invalid password has been previously entered during the password recovery procedure (either because the provided password was too short, was based on a dictionary word, or because the two passwords typed didn&#39;t match)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Ignore the &quot;Error: the password has NOT been reset.&quot; status message and press Ctrl-C to end the password recovery session. Even though that error was given, the new password just entered will work to successfully login to the OS admin.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd17258</guid>
</item>
<item>
<title>Call Park DN allocation algorithm reversion , Fixed CSCtc77181</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc77181</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

After upgrading to Cisco Unified Communications Manager (CUCM) 7.0 or higher call park directory numbers are allocated in different way than in the previous version.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM 7.0 or higher.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None, this is non-modifiable behavior.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

In versions of CUCM prior to 7.0 call park numbers were assigned in order, with no repetition until all numbers had been used.
In CUCM 7.0 this behavior was changed such that call park numbers are assigned in a top-down manner, always taking the first free number in the range of numbers allocated to the feature.

In systems where the call park feature is heavily utilized this new behavior can lead to users picking up the wrong call if the original call has reverted back to the parking party and another user has parked a call.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc77181</guid>
</item>
<item>
<title>RTMT hangs at Loading, Please Wait... after installing CUCM 4.3.2 ES05 , Fixed CSCsu86458</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu86458</link>
<description>Symptoms
RTMT hangs at Loading, Please Wait after installing CUCM 4.3.2 ES05
&lt;br&gt;
Conditions
CUCM 4.3.2 ES05
&lt;br&gt;
Workaround
1. Install RTMT on any machine, it by default installs at 
C:\Program Files\Cisco\CallManager Servicability

2. Copy jre1.5.0_14 folder(install this JRE version on a PC and you can get the folder from C:\Program Files\Java) 
to C:\Program Files\Cisco\CallManager Servicability\JRE

3. Replace the content of run.bat
(Found in C:\Program Files\Cisco\CallManager Servicability\jrtmt) 
with
..\JRE\jre1.5.0_14\bin\java  
-Dsun.java2d.d3d=false-Xbootclasspath/a:.;.\Lib\xerces.jar;.\Lib\log4j.jar;.\Lib\jcchart45
0J.jar;.\Lib\collections.jar 
-jar JRtmt.jar

4. Double click on run.bat
(Found in C:\Program Files\Cisco\CallManager Servicability\jrtmt)

5. If double click does not work, open Command Prompt
    - cd C:\Program Files\Cisco\CallManager Serviceability\jrtmt
    - issue run.bat and now you&#39;ll be prompted for login to RTMT. This should work.

6. So everytime you want to use RTMT you&#39;ll have to use run.bat and 
creating a shortcut for run.bat on desktop will not work.

Reason
We are hitting an UnsupportedClass Exception which is because of the different JRE used while compiling the code and while launching RTMT.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu86458</guid>
</item>
<item>
<title>CCM AXL 4.2(3) Special character handling , Fixed CSCsk51620</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk51620</link>
<description>Symptoms
-------------
When you insert user thru AXL, it stores the data as it is. Since 4.x supports only Latin characters, you cannot specify utf-8 characters while inserting. If utf-8 characters are specified, then the information stored in Directory will not be the same as specified.  
When you retrieve data thru AXL, all user information are converted to UTF-8 and responded in UTF-8 format.  
If you use the same data from getUserResponse and try to update the user, AXL will throw an error as it will not find an entry for the userId. As a workaround, you would need to convert the getUserResponse data to Latin encoding and use that information in updateUser. 
For ex. if you add an user with userId as &#39;????????????&#39; (Latin encoded), the data stored will be same. But when you retrieve this user using GetUserReq or ListUserByName, then in the response you will get the userId as &#39;???????????????????????...&#39; which is UTF-8 encoded. The response will also specify the encoding type as UTF-8. From your application, you can convert the data back to required encoding. In this case, you may want to convert the data back to Latin format.
&lt;br&gt;
Conditions
------------
Problem seen only in Windows versions of CM, only while latin to utf-8 conversions.
&lt;br&gt;
Workaround
---------------
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk51620</guid>
</item>
<item>
<title>Annunciator leak on H.323 call with Unrestricted Digital media , Fixed CSCtb62843</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb62843</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Leak of Annunciator resources within CUCM.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
* PSTN Gateway with T1 / E1 configured as an H.323 Gateway pointing towards CUCM.
* CUCM using Annunciator for H.323 calls.
* the incoming call is an Unallocated number.
* the incoming call is actually a data call with the ISDN SETUP having Transfer Capabilities like these :

       Bearer Capability i = 0x8890
                Standard = CCITT
                Transfer Capability = Unrestricted Digital
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
1. Configure the IOS gateway as following

interface Serial x/y:15
 isdn incoming-voice voice

2. Use a translation-rue on the IOS gateway to block the calling number sending incoming data calls.
3. configure the called number as a DN in CUCM so that it no longer triggers Annunciator.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
The Annunciator resource is allocated, but when the media fails to negotiate due to the other end attempting to establish a data call, the annunciator resource is never released.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb62843</guid>
</item>
<item>
<title>DRS restore of CCMDB fails on new built PUB when contacting SUBs , Fixed CSCsr91903</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr91903</link>
<description>
 &lt;B&gt;Symptom:&lt;/B&gt;
  During the Disaster Recovery System (DRS) restore on a newly built publisher,
 the CCMDB component of the restore will results in a warning.
  For 7.0(1), CUCM cluster has more than one node CCMDB logs say &quot;No Subscriber
to be restored since it is a Single Node installation&quot;. Restore status does not
indicate any warning. 
&lt;br&gt;  
  &lt;B&gt;Conditions:&lt;/B&gt;
  If the Communications Manager database needs to be restored on a freshly
 installed Publisher and the Subscriber servers are currently up and
 operational, the restore will not complete properly causing the re-installation
 of all subscriber servers in the cluster.
&lt;br&gt;  
  &lt;B&gt;Workaround:&lt;/B&gt;
  For 6.1(2) CUCM Release
  During the restore process the Publisher is not made properly aware of the
 subscribers in the cluster.  After the fresh installation of the Cisco Unified
 Communications software, but prior to running the DRS restore, the subscriber
 servers need to be added to system-&gt;server within Cisco Unified CM
Administration. 
  If you run into this issue install the Cisco Unified Communications Manager
 software once again on the publisher server and complete the workaround above.

  For 7.0(1) CUCM Release

  1. Fresh install publisher
  2. DRS Restore on publisher
  3. Reboot publisher (CLI:utils system restart)
  4. Wait for few minutes after publisher is up. 
  5. Restore subscribers from publisher (CLI:utils dbreplication
forcedatasyncsub all), run on publisher. 
  6. Reboot subscribers (CLI:utils system restart)
  7. Drop admin DB on subscribers (CLI:utils dbreplication dropadmindb) 
  8. Drop admin DB on publisher (CLI:utils dbreplication dropadmindb) 
  9. Reset replication (CLI:utils dbreplication reset all)
  10. Reboot publisher (CLI:utils system restart)
&lt;br&gt;

  &lt;B&gt;Further Description:&lt;/B&gt;
  Proper way to restore a publisher without reinstalling the subscribers:
  1) Fresh install Publisher with same version of the backup and current
 subscribers. Reboot server.
  2) All subscribers must be online.  Do not shut down subscribers.
  3) On the publisher
  Access to CCMAdmin page through url https://&lt;Server IP&gt;:8443 then navigate to
 system-&gt;server and add all existing subscribers.  If DNS is not being used add
 servers by IP address.
  3) Navigate to DRS page from Navigation drop down proceed with restore
 procedure.  Don&#39;t need to activate any services prior to restore.
  4) Login to the DRS pages using the platform admin user name and password
  5) From DRS main page, select Backup -&gt; Backup Device.  
   -Enter Device name (i.e Network_Backup) and sftp info then Click Save
  6) Navigate to the Restore -&gt; Restore Wizard.  
   -Select Device Name (i.e NETWORK_BACKUP) then Click Next
   -Select CCM and CDR_CAR then Click Next
   -Select CCM and CDR_CAR on Publisher node only then Click Restore 
  7) After restore has successfully completed reboot all servers in the cluster
 (publisher first) navigating to Cisco Unified OS Administration and selecting
 Settings -&gt; Version -&gt; Restart
  
  
  
 
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr91903</guid>
</item>
<item>
<title>Missing date column entries in tbl_system_preferences fail car scheduler , Fixed CSCsm34263</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm34263</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Reports or CDR Loading fail in CAR, causing missing CAR reports and accumulated CDR/CMR files unprocessed to CAR database. 

this is caused due to missing max_date, min_date,cdr_max_date OR cdr_min_date from tbl_system_preferences.
the following line can be seen in car scheduler / car web service trace:
&quot;loadCurrentData(): &lt;column-name&gt; does not exist in tbl_system_preferences, restore to its default&quot;

Follow steps below to confirm which entry is missing:

1. check MIN_DATE value: 
admin: run sql select param_value from car:tbl_system_preferences where param_name=&#39;MIN_DATE&#39;
 
2. check CDR_MIN_DATE value. admin: run sql select param_value from car:tbl_system_preferences where param_name=&#39;CDR_MIN_DATE&#39; 

3. check MAX_DATE value: admin: run sql select param_value from car:tbl_system_preferences where param_name=&#39;MAX_DATE&#39; 

4. check CDR_MAX_DATE value. admin: run sql select param_value from car:tbl_system_preferences where param_name=&#39;CDR_MAX_DATE&#39;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CAR&#39;s &#39;tbl_system_preferences&#39; table is missing MIN_DATE, MAX_DATE, CDR_MIN_DATE, or CDR_MAX_DATE column, or a combination of the four columns.  This usually happens after W1/L2 migration. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Identify which column(s) are missing in tbl_system_preferences table (this can be done either by looking at the CAR scheduler trace and search for ERRORm, or it can simply be done by querying directly on tbl_system_preferences table via CLI to find out which one(s) are missing: &quot;admin: run sql select * from car:tbl_system_preferences&quot;) 

If any of these four columns is missing, insert it back to the table with the following logic: 
- If MIN_DATE is missing, find CDR_MIN_DATE value and insert such value as MIN_DATE to tbl_system_preferences. 
- If CDR_MIN_DATE is missing, find MIN_DATE value and insert such value as CDR_MIN_DATE to tbl_system_preferences. 
- If both MIN_DATE &amp; CDR_MIN_DATE are missing, insert &#39;01/01/1970&#39; to both columns to to tbl_system_preferences. 
- If MAX_DATE is missing, find CDR_MAX_DATE value and insert such value as MAX_DATE to tbl_system_preferences. 
- If CDR_MAX_DATE is missing, find MAX_DATE value and insert such value as CDR_MAX_DATE to tbl_system_preferences. 
- If both MAX_DATE &amp; CDR_MAX_DATE are missing, insert &#39;01/01/1970&#39; to both columns to to tbl_system_preferences. 

In any of the above cases, once Loader starts and load new files, it will populate the correct values for these columns again, based on the records being loaded. 

For example, if CDR_MIN_DATE is missing:
1. Get MIN_DATE value. 
admin: run sql select param_value from car:tbl_system_preferences where param_name=&#39;MIN_DATE&#39;
2. Get the value from above, eg: 01/01/2008, then run: 
admin: run sql insert into car:tbl_system_preferences values(&#39;CDR_MIN_DATE&#39;, &#39;01/01/2008&#39;);

For example, if MAX_DATE is missing:
1. Get CDR_MAX_DATE value. 
admin: run sql select param_value from car:tbl_system_preferences where param_name=&#39;CDR_MAX_DATE&#39;
2. Get the value from above, eg: 02/14/2008, then run: 
admin: run sql insert into car:tbl_system_preferences values(&#39;MAX_DATE&#39;, &#39;02/14/2008&#39;);
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
N/A.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm34263</guid>
</item>
<item>
<title>set web-security CLI command not allowing spaces for O, OU, L, ST, and C , Fixed CSCsq53869</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq53869</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

set web-security command does not allow spaces or special characters for Org, Org. Unit,
Location, State and Country.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

set web-security does not allow spaces or sepcial characters in the command arguments.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq53869</guid>
</item>
<item>
<title>Enhanced MWI StationMwiNotificationMessage only uses device CSS not line , Fixed CSCta99556</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta99556</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

MWI on/off calls fail when using new Enhanced MWI integration.
Trace analysis shows that CCM is only using the Voicemail port&#39;s Device CSS when looking for the MWI On/Off DN, instead of using the normal Line:Device CSSes concatenated.

07/12/2009 19:31:41.457 CCM|StationInit: (0000009) StationMwiNotificationMessage mwiTarget=7121004 mwiCtrl=2101 msgsWaiting=1 totalVm(-1/-1) priVm(-1/-1) totalFax(-1/-1) priFax(-1/-1)|&lt;CLID::StandAloneCluster&gt;&lt;NID::pub712&gt;&lt;CT::1,100,39,1.1721&gt;&lt;IP::10.48.43.52&gt;&lt;DEV::CiscoUM1-VI1&gt;&lt;LVL::State Transition&gt;&lt;MASK::0020&gt;
07/12/2009 19:31:41.458 CCM|MessageWaitingManager::ssInforeq - Bad mwiOnOffDn=2101 passedCSS=89e9564e-5589-2ff0-946c-d9548dcb4bba|&lt;CLID::StandAloneCluster&gt;&lt;NID::pub712&gt;&lt;CT::1,100,39,1.1721&gt;&lt;IP::10.48.43.52&gt;&lt;DEV::CiscoUM1-VI1&gt;&lt;LVL::Error&gt;&lt;MASK::0800&gt;
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;

MWI DN is located in a CSS only reachable from the Line CSS of the VM port, not reachable via the Device CSS
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Ensure that the MWI On/Off DN is in a partition reachable via the Device CSS applied to the Voicemail Ports.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta99556</guid>
</item>
<item>
<title>Certificate management doesn&#39;t allow apostrophe (&#39;) in OU , Fixed CSCtd03662</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03662</link>
<description>                            --&gt;

&lt;B&gt;Symptom:&lt;/B&gt;
When on CUCM CLI try to run &quot;set web-security&quot; command, apostrophe in organization name doesn&#39;t get accepted.  Certificate management blocks this character.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 7.0.2.21900-10
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03662</guid>
</item>
<item>
<title>International Strip Digits should be empty for devices other than H323 g , Fixed CSCta14530</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta14530</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
The following errors appears when making configuration changes. Can also happen when resetting a SIP Trunk:

SQL Error (-746): 25256
International Strip Digits should be empty for devices other than H323 gateways and trunks and MGCP T1/E1 PRI and BRI gateways
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Systems with fresh install or upgrade to any 7.0(x) release, followed by upgrade to 7.1(2) release. SIP Trunks were created or modified before upgrade to 7.1(2).
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
From the console CLI execute the following command:

&lt;cmd&gt;run sql update device set internationalprefix = &#39;Default&#39;, internationalstripdigits = null, nationalprefix = &#39;Default&#39;, nationalstripdigits = null, subscriberprefix = &#39;Default&#39;, subscriberstripdigits = null where tkproduct = 95 and (internationalprefix &lt;&gt; &#39;Default&#39; or nationalprefix &lt;&gt; &#39;Default&#39; or subscriberprefix &lt;&gt; &#39;Default&#39;)&lt;/cmd&gt;
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
A hidden value inserted into the database by web pages in 7.0 does not migrate correctly to 7.1. The migration issue then causes the above error when a SIP Trunk&#39;s database record is updated directly or indirectly (e.g., associated Route Pattern is changed). The error condition can be cleared after migration to 7.1(x) without any loss of data using the SQL statement shown in the Workaround.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta14530</guid>
</item>
<item>
<title>BAT insert of SCCP VG224 does not add virtual endpoint , Fixed CSCsw43113</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw43113</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Unable to reset a SCCP controlled VG224 which was added via BAT.  
TSP errors logged in the CUCM application event log.

%CCM_CALLMANAGER-CALLMANAGER-3-TspError: Error in TSP. Port IsoEthPort:0 Port DSL:0 Name of Device:ANBBBBBBBBBBFFF App ID:Cisco CallManager Cluster ID:StandAloneCluster Node ID:CUCM
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM 6.0, 6.1, or 7.0 with SCCP VG224 gateways added via BAT.   Issue does not occur if they are added via CCMAdmin.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

To stop the VG224 from trying to register the virtual endpoint.
On gateway, enter CLI:
&lt;b&gt;
   config t
      no ccm-manager sccp
&lt;/b&gt;

To get the virtual endpoint created you need to delete the VG224 in CCMAdmin and recreate it manually.  If you do not wish to manually configure the ports you can use BAT to export the gateway data, delete the VG224 from CCMAdmin, re-add just the gateway via CCMAdmin, then use BAT to import the individual ports.  
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

A similar issue exists with AXL device inserts and is resolved via CSCsq58858, fixed in CUCM 7.0(1).

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw43113</guid>
</item>
<item>
<title>Call Manager can not do a hookflash on a fxo line with Call Waiting , Terminated CSCdv71088</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdv71088</link>
<description>Release Note:

Symptom:  Ip phone cannot answer call waiting beep sent by the telco

Problem: Call Manager does not have the means to send the H245 message to the 
gateway to answer the Call Waiting call
&lt;br&gt;
Workaround: Create a hunt group of FXO so the call always comes in on a new trunk
and now use Call Waiting on the PSTN (use Call Manager call waiting).


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCdv71088</guid>
</item>
<item>
<title>UC:&quot;User Must Change at Next Login&quot; does not work with &quot;Does Not Expire&quot; ,   CSCsy86283</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy86283</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When checking &lt;b&gt;User Must Change at Next Login&lt;/b&gt; and &lt;b&gt;Does Not Expire&lt;/b&gt; for Web application password at the same time, Password Change window does not appear and a user can login Unity Connection without changing a password.

The settings for Voice Mail can work correctly.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
Unity Connection is standalone, not a Business Edition.
Version is 7.0.2.10000-38.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
No workaround.
&lt;br&gt;

&lt;B&gt;Further Description:&lt;/B&gt;
This problem can be resolved by upgrading CUC version to 7.1, then setting &quot;CSCsr93148&quot; in &quot;Cisco Support Use 2&quot; in Enterprise Parameter.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy86283</guid>
</item>
<item>
<title>AXL Service Stuck in Contacting Offline Subscribers , Fixed CSCta95472</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta95472</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Customer is using 3rd party software &quot;FCS&quot; to config/deploy ip phones via AXL.  
An AXL user with all the access was created on CCM. DB sync&#39;ed OK. 
AXL running on both pub and sub. FCS points to pub ip addr.

When both pub and sub are online, the FCS works fine. 
When they shutdown the switchport to sub or unplug the network cable of sub (around 16:34 Jul 2), 
the pub ccmadmin page can be opened and operate normally, RTMT can connect to pub. that&#39;s expected. 

However, once they start an update to the phones via FCS, the ccmadmin of pub freezed and didn&#39;t 
respond. 
RTMT lost connection to pub. FCS update failed. After several attempt, FCS gives up trying and then 
access to ccmadmin and RTMT to pub connection restored.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Make sure all the subscribers online when doing AXL query/update.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta95472</guid>
</item>
<item>
<title>handle leak with h323 calls , Fixed CSCsk54103</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk54103</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
CallManager shows increased memory utilization and handle count over time when
processing H.323 calls.  With 0 calls active netstat shows active sessions to
h323 call control port 1720:

5.x or 6.x:
admin:show open ports regexp h323
Executing.. please wait.
ccm       25124    ccmbase   26u  IPv4 16353054       TCP
10.48.24.51:h323hostcall-&gt;10.18.110.45:62110 (ESTABLISHED)
ccm       25124    ccmbase   64u  IPv4 63026323       TCP
10.48.24.51:h323hostcall-&gt;10.18.110.45:52300 (ESTABLISHED)
ccm       25124    ccmbase  220u  IPv4 10847054       TCP *:h323hostcall (LISTEN)

4.x:
C:\Program Files\Cisco\Trace\SDL\CCM&gt;netstat -an | findstr 1720
  TCP    10.18.110.45:1720     0.0.0.0:0              LISTENING
  TCP    10.18.110.45:52300    10.48.24.51:1720       ESTABLISHED
  TCP    10.18.110.45:52301    10.48.24.51:1720       ESTABLISHED
  TCP    10.18.110.45:52303    10.48.24.51:1720       ESTABLISHED
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CM processing H.323 calls.  Specifically SDL traces show:
H225cdpc created:
000921744| 07/09/19 11:02:19.365| 001| Created   |                            
          |                               | H225Cdpc(1,100,38,1545)         |
H225D(1,100,39,11)              |                                         |
NumOfCurrentInstances: 10

H225cdpc stopping:
lab\413\sdl_ccm\SDL001_100_000006.txt(1886): 000921799| 07/09/19 11:02:19.396|
001| Stopping  |                                       |                      
        | H225Cdpc(1,100,38,1545)         | H225Cdpc(1,100,38,1545)         | 
                                       | NumOfCurrentInstances: 9

H225cdpc requesting TCP session:
000921819| 07/09/19 11:02:19.396| 001| SdlSig    | TcpStartSessionReq         
          | wait                          | H225Handler(1,100,40,1)         |
H225Cdpc(1,100,38,1545)         | (1,100,38,1545).1-(*:*)                 | [NP
- PQ: 0]	PID=(100,1,39,11)
000921830| 07/09/19 11:02:19.396| 001| Created   |                            
          |                               | SdlTCPConnection(1,100,132,3140)|
SdlTCPConnector(1,100,133,1545) |                                         |
NumOfCurrentInstances: 92
000921856| 07/09/19 11:02:19.412| 001| SdlSig    | Start                      
          | start                         | SdlTCPConnection(1,100,132,3140)|
SdlTCPConnection(1,100,132,3140)| (1,100,132,3140).1-(*:*)                | [HP
- NQ: 8]

After this the SDLTCPConnection is never stopped.  This results in TCP session
staying open.  Session will be maintained by TCP keepalives even though no h225
setup message is extended over this session.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Once sessions are leaked there is no simple online recovery.  You can run
TCPView on CallManager and force the sessions closed.  Otherwise, restart
CallManager to clear the tcp ports/handles and free associated memory.

To minimize leak change the CallManager service
parameter &#39;H225 TCP Timer&#39; to a value of 10 or higher.  Higher values decrease
risk of leak, but leak will still happen intermittently even at max value.






</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsk54103</guid>
</item>
<item>
<title>Tomcat gets OutOfMemoryError due to insufficent Java PermGen memory , Fixed CSCsm78770</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm78770</link>
<description>&lt;B&gt;Update:&lt;/B&gt;
This specific issue only affects CM5.1 versions.  It does not apply to CM6.x 
This issue is resolved in the following versions:
5.1(2.3129.1)
5.1(3.2111.1) 
5.1(3.3000.1)  aka 5.1(3b)

The issue is associated with using multiple webapps on the CM server.  Example
webapps are ccmadmin, ccmservice, iptplatform, extension mobility, axl, CAR,
SOAP CDROnDemandReporting, etc.  The more webapps in use the more likely to
encounter this issue.

Simply locating a &quot;OutOfMemory&quot; error in Tomcat&#39;s catalina.out log does NOT indicate the server is suffering from this defect. 

&lt;B&gt;Symptom:&lt;/B&gt;
 80% Virtual Memory usage Tomcat experiences OutOfMemoryError. Tomcat VMRSS
 grows over 500MB
 
 In tomcat logs, catalina.out and localhost_log &quot;exception
 java.lang.OutOfMemoryError&quot; and &quot;Allocate exception for servlet&quot; are seen.
    
    When in this state, not able to login EM, CCMAdmin web pages, seems CAR stops
   responding.   
    Tomcat shows started, however doesn&#39;t seem to be functional.
    
    &lt;b&gt;Proactively Monitoring:&lt;/b&gt;
    
    1. show perf query class &quot;Cisco Tomcat JVM&quot; 
    2. show perf query counter &quot;Memory&quot; &quot;% Mem Used&quot; 
    3. show perf query counter &quot;Memory&quot; &quot;% Mem Used&quot; 
    4. show perf query counter &quot;Memory&quot; &quot;% VM Used&quot; 
    5. :show perf query instance &quot;Process&quot; &quot;cmoninit&quot; 
    The output from above commands need to be captured twice a day and reported to
   TAC.
    
   Please collect the following additional logs if you encounter this issue:
   From RTMT if accessiable: 
   
   1. All Cisco AMC Service logs 
   2. AXL Web Service logs 
   3. CallManager User Web Service 
   4. Cisco Callmanager Admin 
   5. Cisco Extension Mobility 
   6. Cisco Extension Mobility Application 
   7. Cisco Tomcat Stats Servlet 
   8. Even Viewer - Application log, 
   9. Event Viewer - System.log 
   10. Cisco Tomcat logs 
   11. Cisco Tomcat Security Logs 
   12. Security Logs 
   
   If no RTMT access, use ssh to collect the logs with sftp as 
   
   file get activelog tomcat/logs/axl/log4j/* 
   file get activelog tomcat/logs/ccmadmin/log4j/* 
   file get activelog tomcat/logs/dbl/log4j/* 
   file get activelog tomcat/logs/security/log4j/* 
   file get activelog tomcat/logs/catalina* 
   file get activelog tomcat/logs/localhost* 
   file get activelog syslog/* 
   file get activelog cm/log/amc/alertlog/* 
   file get activelog cm/log/amc/calllog/* 
   file get activelog cm/log/amc/devicelog/* 
   file get activelog cm/log/amc/PerfMonLog/* 
   file get activelog tomcat/logs/em/log4j/* 
   file get activelog tomcat/logs/tomcatstats/log4j/* 
   
   And capture the output from the following CLI for some specific performance
   counters 
   
   1. show perf query class &quot;Cisco Tomcat JVM&quot; 
   2. show perf query counter &quot;Memory&quot; &quot;% Mem Used&quot; 
   3. show perf query counter &quot;Memory&quot; &quot;% Mem Used&quot; 
   4. show perf query counter &quot;Memory&quot; &quot;% VM Used&quot; 
   5. :show perf query instance &quot;Process&quot; &quot;cmoninit&quot; 
   
   6. 3rd party, special usage, etc......
 
  7. Does customer actively use:
 CAR
 Extension Mobility
 CUOM
 
 and do the URL&#39;s for each reference the affected server?  
&lt;br&gt;   
   &lt;b&gt;Workaround:&lt;/b&gt;
There is one, please contact TAC for workaround and to make sure the necessary data has been collected.
    
Stop/Restart  tomcat service with CLI command:
utils service restart Cisco Tomcat
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Note, VMRss and the CLI command show perf query class &quot;Cisco Tomcat JVM&quot; cannot be used to troubleshoot or even predict this issue.  The memory in question, Java&#39;s permgen, is not broken out from the rest of the JVM memory.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm78770</guid>
</item>
<item>
<title>License Manager causes a registration loop with Auto Registration , Open CSCta36165</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta36165</link>
<description>Symptoms:
Devices that are currently registered will not register again if they are reset. Extension Mobility login may be successful, but the phone will not register when the DataBase change notification is attempted.
Slow access to CCM web pages.  Database change notification times out.
&lt;br&gt;
Condition:
CUCM 6.1.3
Auto Registration is enabled. 
All License DLU&#39;s are in use.
Any new device that attempts to register will cause Call Manager to become unresponsive.
&lt;br&gt;
Workaround:
Disable AutoRegistration. Increase License DLUs.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta36165</guid>
</item>
<item>
<title>CCM uses internal msec ptime for SIP exceeds max sent by remote side , Fixed CSCso03508</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso03508</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

This defect may cause symptoms similar to but not limited to the following:
*Complete silence on a connected call
*Calls that are released by the calling endpoint upon reception of a connect msg from CCM
*Asynchronous packetization in an RTP stream (Transmitting 20 msec per packet while receiving 30 msec etc...)
*One-way audio
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

*An endpoint uses SIP to set up an RTP stream to another CCM controlled device. The called device can be anything.
*The packet size proposed by the calling party differs from what CCM has configured for its *preferred &lt;codec&gt; millisecond packet size&quot; service parameter.
*SIP Trunk


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCso03508</guid>
</item>
<item>
<title>Restricted CallingPartyNumberPi changes to Allowed when Forwarding , Fixed CSCtc78996</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc78996</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;

When Callmanager forwards external call, in which the CallingPartyNumberPi is Restricted,  to an external number it changes calling party presentation indicator to allowed.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 7.0.2.21900-10
CallingPartyNumberPi on Route pattern and GW  have the default settings.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;

none


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc78996</guid>
</item>
<item>
<title>CTI didnot report a failure response to application , Open CSCtd34150</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd34150</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CTI didnot report a failure response to application when the appl. is trying to record a call which is in ringback state (non-connected) 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

IN CUCM 6.1.3.2000
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

N/A



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd34150</guid>
</item>
<item>
<title>CUCM sends an ARQ with srcCallSignalAddress ipAddress= 0.0.0.0 , Fixed CSCta13502</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta13502</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
On calls received via a Gatekeeper controlled ICT CUCM sends an ARQ with srcCallSignalAddress ipAddress= 0.0.0.0 rather than preserving the IP address it received in the H225 Setup.  When Gatekeeper has a security ACL it responds with an ARJ and the calls fail.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Inbound calls received by CUCM 7.0(2) cluster via a Gatekeeper controlled ICT.




&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Modify Gatekeeper ACL to allow 0.0.0.0 address.



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;













</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCta13502</guid>
</item>
<item>
<title>More than 5 Agreements should be allowed for LDAP sync. , Open CSCsg96397</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg96397</link>
<description>

&lt;B&gt;Symptom:&lt;/B&gt;

CallManager 5.0.4 only allows 5 LDAP agreements to be added. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This was found when customer needed to add 14 agreements based on current AD configuration.  Customer has 14 containers that include both IP phone users and non-IP Phone users.  
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None:  besides re-structure of AD to support 5 agreements.  
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

This needs to be able to support more than 5 agreements so that the customer can add as many agreements as necesary to an existing AD structure that includes IP Phone users and non-IP Phone users in the same container.  
                        


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg96397</guid>
</item>
<item>
<title>Phone accessed directory receives hex equivalent of special characters , Fixed CSCsx74918</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx74918</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Personal fast dial on CallManager builds above 21014. Special characters sent back from the CallManager contain the hex code equivalent and not the actual character.

Tested on 7.0.1.21014 and 7.0.1.21020-1.

Steps to reproduce:
Enter a personal fast dial in the CCM User page using the web. In the number, use + or #.
Then view the number using the phone - The phone displays %2B for the plus symbol, and %23 for the Pound.
This is not the phone rendering the character differently, it&#39;s sent to the phone like this in the XML from the CallManager.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Tested on 7.0.1.21014 and 7.0.1.21020-1.
Personal fast dials.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Use base CallManager build.
Don&#39;t use special characters.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsx74918</guid>
</item>
<item>
<title>Status &amp; IP not properly associated on Find &amp; List Phone Page , Fixed CSCsl70392</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl70392</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Under Device &gt; Phone the Status and IP address are not properly associated with the correct devices in the list when multiple devices are listed.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

CUCM prior to 6.1.1.2104 performing a phone search that returns multiple results.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

View the device status on the Phone page, or narrow the search so only a single phone is displayed.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl70392</guid>
</item>
<item>
<title>Preventive code changes for SUN&#39;s bug on handling Brazil DST , Fixed CSCsv47100</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv47100</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Missing CDR records in CAR db, or CAR migration fails.  That&#39;s due to partition creation got stuck (looping forever) while creating a particular date partition. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

With CUCM running Java JRE 1.4.2 or earlier version, and publisher in cluster is in a particular timezone like the Brazil&#39;s.  And partitions creation runs during CDR loading or after CDR-Reload or during migration upgrade, around the Daylight saving date (DST).  
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

You can first try applying the latest tzupdater patch published by SUN, see if that fix it. If not, then although not recommended, you can temporarily change the system timezone so the DST transition date is not included in the neccessary date partitions creation range. 
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

N/A. 


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv47100</guid>
</item>
<item>
<title>CLI prints long exception if unable to access log directory , Terminated CSCsu05586</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu05586</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
User tries to login to the CLI and sees a long expetion stack dump.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
This issue can happen when the common partition gets corrupted.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
This error does not keep the user from accessing the CLI.  However, the user should still get support since their common file system is corrupted and needs to be fixed.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu05586</guid>
</item>
<item>
<title>ParkDN is not OnHold while the call is parked , Fixed CSCtc38841</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc38841</link>
<description>
Symptom:
When Application monitors PARK DN line and the call is parked,  ParkDN should be OnHold call state but it is not. 
&lt;br&gt;Condition:
     The problem was exposed with CUCM 8.0 but it is also applied to CUCM 7.1.X  caused by CTI component.
&lt;br&gt;
Workaround:
     None
&lt;br&gt;
Further Problem Description:
With this problem, there is no indication whether the call parked or not by monitoring Park  number.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc38841</guid>
</item>
<item>
<title>Abandoned PublishEPA causes unexpected DND updates , Fixed CSCsy80245</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy80245</link>
<description>Symptom:
IP Phones go in and out of DND without user intervention.
&lt;br&gt;
Conditions:
IP Phones were registered with a different node at some point.
&lt;br&gt;
Workaround:
Restart the ccm service on the node that has the abandoned PublishEPA&#39;s


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy80245</guid>
</item>
<item>
<title>CAT: CCMPD: XML Error 4 shown in personal directory speed dial , Fixed CSCsi23959</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi23959</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
In the ip phone Directories-&gt; Personal Directory -&gt;Personal Fast Dials is returning:
 
    Error XML[4]:error analisi
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CCM 5.1.1.2000-2
cm-locale-ca_ES-5.1.1.0-1.cop.sgn
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use spanish locale instead of catalan.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Issue is that Title element returned exceeds the 32 characters as per http://www.cisco.com/univercd/cc/td/doc/product/voice/vpdd/cdd/5_0/ipphsv/ip502apb.htm , so we are violating the XML schema of the ip phone


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi23959</guid>
</item>
<item>
<title>Insert/Update Phone Template in BAT produces Error No. error message , Fixed CSCsi74554</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi74554</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When inserting/updating a phone template in BAT, the user receives a pop-up from the web page that says simply: &quot;Error No.&quot;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

User is attempting to insert a template for a 7941/61/70/71. Maybe others. The 70/71 won&#39;t insert at all, and the 7941/61 will insert depending on whether the CSS and AAR CSS is defined.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Uninstall BAT and reinstall from plugins page in CCM.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsi74554</guid>
</item>
<item>
<title>French: Missed calls display incorrect , Fixed CSCtc91413</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc91413</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

IP phone when using French Localel shows multiple missed calls as &quot;x appel en abscences&quot;. 

3 missed calls for example, the information printed on phone screen is &quot;3 appel en abscences&quot; where it should be &quot;3 appels en abscence&quot;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc91413</guid>
</item>
<item>
<title>Bad/Corrupted capCount Values Cause CM Service Restart ,   CSCsg88251</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg88251</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CM service restart.  Access Violation in DrWtsn32.log and user.dmp generated.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

4.1(3)sr2, capCount value in SCCP capabilities response message seems bad/corrupt...

10/26/2006 16:03:42.447 CCM|StationInit:   TCPPid = [10.100.132.307] CapabilitiesRes ERROR capCount=1412235271|&lt;CLID::StandAloneCluster&gt;&lt;NID::10.0.2.202&gt;&lt;CT::2,100,119,1.54126947&gt;&lt;IP::10.8.135.130&gt;&lt;DEV::SEP00170E01097F&gt;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg88251</guid>
</item>
<item>
<title>RTMT emails do not include domain in from field of SMTP header , Fixed CSCsf08244</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsf08244</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
 Email alerts from RTMT may not be delivered to recipients.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 RTMT alerts currently do not supply a domain in the from field of the SMTP
header.  
 Example packet capture of problem:
 Simple Mail Transfer Protocol
     Command: MAIL FROM:&lt;RTMT_Admin&gt;\r\n
         Command: MAIL
         Request parameter: FROM:&lt;RTMT_Admin&gt;
 

AMC logs show:
alertmgr.SendMail - SendMail::send: got address exception=
javax.mail.internet.AddressException: Missing domain in string ``RTMT_Admin@&#39;&#39;  
&lt;br&gt;
 &lt;B&gt;Workaround:&lt;/B&gt;
 assign the fully qualified domain name to the servers involved using the
following CLI:
 
 set network dns primary &lt;your primary dns IP address&gt;
 set network dns secondary &lt;your secondary dns IP address&gt;
 set network domain &lt;node.company.com&gt;
 
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsf08244</guid>
</item>
<item>
<title>transfers from unity fail with no callstate 5 , Fixed CSCsh98605</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh98605</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
transfers from Unity fail with either call being dropped or ring no answer.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Call comes into a Unity AA and is then transferred to a DN that is CFA to VM (back to the same Unity server). 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

set Unity to use supervised transfer instead of blind (release to switch) transfer.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh98605</guid>
</item>
<item>
<title>BAT RDP Insert overwrites existing CFA CSS / Secondary CFA CSS settings , Fixed CSCsy47891</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy47891</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Existing Call Forward All CSS and Secondary Calling Search Space for Forward All are getting overwritten by the values set in the Remote Destination Profile Template&#39;s Line Template settings.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Using Bulk Administration to insert Remote Destination Profiles sharing a line with existing phones. This would be expected behavior if the &quot;Override existing configuration&quot; box is checked. However, this is occurring when the &quot;Override existing configuration&quot; box is _not_ checked when initiating the Insert in BAT / Bulk Administration.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Configure the desired CFA CSS and Secondary CFA CSS on the RDP Template&#39;s line template settings so that they are the same as the existing values.

OR

Insert the Remote Destination Profiles without using an RDP Template. This requires that the Desk Phone MAC address also be provided in the CSV file (in the form of SEP&lt;MAC&gt;, as shown in the Bulk Administration webpage example).

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsy47891</guid>
</item>
<item>
<title>Unable to proceed with CUCM upgrade using the GUI, inhibit CM6.x upgrade , Fixed CSCsq74206</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq74206</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 Unable to upgrade to a lter version of CUCM due to a script error on internet
explorer
 Generally can see
 
 Error:
 line 574
 char 2
 object expected
 code: 0
 
 url: https://&lt;ip add of CM&gt;/cmplatform/install.do
&lt;br&gt; 
 
 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 trying to upgrade to a later version of CUCM via the GUI
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
Restart the Cisco Tomcat service from the platform cli:
&lt;b&gt;utils service restart Cisco Tomcat&lt;/cmdBold&gt;
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsq74206</guid>
</item>
<item>
<title>CFNA timer shouldn&#39;t start after 2nd transfer into an existing instance , Fixed CSCsv99508</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv99508</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Call flow:
6105----call--6021-----cti-port59512------6801 agent-----transfer--- mgcp----fincal party PSTN number. 

After about 12 seconds  between 6105 and PSTN number, caller 6105 was disconnected and PSTN was forwarded to 6801&#39;s voicemail unexpectedly. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

None.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

The CFNA timer should not be started for the PSTN call alerting after the second transfer into an existing forwarding instance

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsv99508</guid>
</item>
<item>
<title>Add service parameter to choose call park allocation method , Open CSCtc81990</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc81990</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;

The Call Park feature allocates park numbers differently after upgrading to CUCM 7.0.  There is no way to choose how this allocation operates.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

No specific conditions other than CUCM which uses the call park feature.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

CUCM 7.0 and later without the fix for CSCtc77181 will allocate park DNs in a top-down manner, always using the first available number in the range when it is available.  Prior to CUCM 7.0 and in any version with the fix for CSCtc77181 park DNs are allocated using a least-recently-used algorithm which will cause DNs to cycle and not be reused frequently.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

The purpose of this enhancement is to introduce a CUCM Service Parameter to allow customers to choose how call park DNs are allocated.  The default behavior should be the least-recently-used method introduced with CSCtc77181.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc81990</guid>
</item>
<item>
<title>7.1(2b)su1 upgrade rules to prevent install over ineligible ES&#39;s , Fixed CSCtb50376</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb50376</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Upgrades from CUCM 7.1(2b)su1, also known as 7.1.2.31900-x, don&#39;t display any es&#39;s less than or equal to 7.1.2.310xx-x as valid upgrades.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Only applicable for customers running CUCM 7.1(2b)su1, also known as 7.1.2.31900-x. The upgrade rules included with this fix prevent customers from installing an Engineering Special that does not contain all of the fixes in 7.1(2b)su1.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Upgrade to an es in the 7.1.2.32xxx-x range or higher


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb50376</guid>
</item>
<item>
<title>incoming calls not getting ring back from annunciator ,   CSCtc43866</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc43866</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Callers get only one ringback and then silence, until cal is answered.l
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
6.1.4 with Annunciator configured for ringback.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restart the IPVMSA service
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc43866</guid>
</item>
<item>
<title>CCM does not respond to an OLC if TCS/MSD happens too quickly after ECS , Fixed CSCsj87963</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj87963</link>
<description>&lt;pre&gt;
&lt;B&gt;Symptom:&lt;/B&gt;

Calls drop or cannot be resumed after using a feature such as hold, park or transfer. This type of issue would also cause issues for things such as moving an established call into an ad-hoc conference.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

*Any version of callmanager without this fix
AND

*Failing calls traverse an H.323 gateway or trunk.
or
*Originate from an h.323 phone or other similar device.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

none
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

This issue is OLC being consumed in cap exchange state due to ECS/TCS/MSD happened too quick. Related bug is CSCsh46915 and CSCsh96614 tries to fix it in basic call but looks like it does not cover this case for peer ECS/TCS/MSD.

In a packet capture, once can observe an inbound OLC towards CCM that is never acknowledged, when the holding/transferring side of the connection tries to resume.


&lt;/pre&gt;
&lt;br/&gt;
Download:&lt;br/&gt;















&lt;br/&gt;
&lt;pre&gt;
One or more of the following links will take you to an emergency
patch called an Engineering Special or ES. If you are not directly
experiencing this problem, we encourage you to select or wait for a
formally tested fix in an upcoming major, minor, maintenance, or
service release. Installing any interim emergency patch or ES on a
production system poses a risk of instability due to the specific
and targeted testing it receives. If you believe you are currently
experiencing this problem, no suitable tested release is listed
here, and you cannot wait for a later release, please select the
link for the ES built for your system. To identify the version you
must have before installing an ES you remove &quot;_ES??&quot; from the
version listed below. That will give you the version of the tested
base release you may install a given ES over. Be sure to read the
release notes or Readme file before running the patch installer.
&lt;/pre&gt;
&lt;br/&gt;


&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;http://www.cisco.com/cgi-bin/tblbld/tablebuild.pl?swpath=fbcd5fa9bb195e488075a4652353573f&quot;&gt;CVP4.0(2)_ES5&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;br/&gt;


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsj87963</guid>
</item>
<item>
<title>Unified Reporting shows few components missing after upgrade , Fixed CSCsz94171</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz94171</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Fresh Install on Publisher installed RPM packages like hpdiags (HP package), cactus &amp; comps (OS packages), as cactus and comps are needed for Fresh installation.

After L2 upgrade,  the cactus and comps packages are removed as we do not need them on upgrade. This is not correctly displayed in the Unified reporting tool.

The Unified reporting tool shows the components shifted.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
L2 upgraded to 6.1.3.1105-3 
L2 upgraded to 6.1.2.1125-1
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsz94171</guid>
</item>
<item>
<title>Unable to update Primary Phone field for IP Communicator , Fixed CSCsu87543</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu87543</link>
<description>






&lt;B&gt;Symtom:&lt;/B&gt;

Using BAT we can&#39;t  update the Primary Phone field for IP communicator






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CallManger 6.12



&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;



&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu87543</guid>
</item>
<item>
<title>DST for Mexico Timezones (PST and MST)  not available in CallManager , Fixed CSCsh39509</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh39509</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
There is no option to select for &#39;Pacific Standard Time (Mexico)&#39; and &#39;Mountain Standard Time (Mexico)&#39; in Date/Time Group Configuration and CCM CLI. Affecting users in Mexico who use Mexico PST or Mexico MST will be using US-based daylight saving time. Their Linux CCM servers and phones will be 1 hour ahead from time when US DST start to Mexcio DST start and 1 hour behind from time when Mexico DST end to US DST end.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Starting 2007 and after applying the fix for US DST adjustment starting 2007 (CSCsf07523).
Cisco Unified CallManager 3.3(5), 4.1(3), 4.2(1), 5.0(4), 5.1(1)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Manually adjust time on server if CallManager is not serving both US and Mexico region.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsh39509</guid>
</item>
<item>
<title>Original Calling Party Number not updated after Blind Xfer to RD. , Open CSCtd03855</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03855</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Calling Party Number is not updated after blind xfer to mobile connect user. 
Remote destination displays the redirecting party number.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 7.x
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
N/A
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
Example call flow
PSTN calls PhoneA
PhoneA transfers the call to PhoneB
PhoneB has remote destination configured
PhoneA completes the transfer
When call is placed to remote destination the calling number is showing up as PhoneA




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd03855</guid>
</item>
<item>
<title>Cannot insert null into a null column TelecasterSubscribedParameter , Fixed CSCsu97248</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu97248</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
 
 Receiving error Insert Phones fails with an error &quot;IP service parameter error,
cannot insert a null into a column. Description: TelecasterSubscribed
Parameter.FKTelecasterServiceParameter&quot;.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 
 This can occur if you are trying to insert phones with a service subscriber
from an exported phone csv. Parameters were not exported along with correct
services. For ex, if Service1 does not have any parameters and Service2 has
some parameters then Service2&#39;s parameters would get associated with Service1.
&lt;br&gt;
 
 &lt;B&gt;Workaround:&lt;/B&gt;
 
 Edit the exported file for the service parameters and place them against the
correct Phone services.
 In this case the text file has Phone Service - &quot;Cisco Meeting Place&quot; &#39;s
parameters associated to Extension Mobility.
 So associate the correct parameters to the service and import the edited text
file.
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsu97248</guid>
</item>
   
</channel>
</rss>
