<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"> 
  <channel>
  <title>Presence 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, 13 Feb 2012 11:25:43 EST</pubDate>
  <lastBuildDate>Mon, 13 Feb 2012 11:25:43 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>LDAP server fails to respond to a connection test query, Fixed CSCtw47559</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw47559</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Client cannot connet (stays disconnected) - Open ldap issue
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
None
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
press &quot;Apply&quot; and client connects successfully

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw47559</guid>
</item>
<item>
<title>Jabber for Mac tries to tftp download non-existent CSF device, Fixed CSCtw44595</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw44595</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Summary:
Jabber for Mac assumes on CSF device name when it cannot find CSF device from CUPS. Jabber for Mac assumes device name from JID of the user which can cause it to query for wrong CSF device name to call manager.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Jabber for Mac for some reason is not able to find CSF device associated with a user
&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=CSCtw44595</guid>
</item>
<item>
<title>CUPC 8.5 buddy status doesn&#39;t change if buddy CUPC PC is forced shutdown, Open CSCtu39341</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtu39341</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CUPC 8.5 buddy status doesn&#39;t change if buddy CUPC PC is forced shutdown. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Steps to reproduce -
1) Set CUPC to &quot;Busy&quot; for UserA
2) UserB sees UserA as Busy
3) UserB force shuts down workstation, which caused cupc to force shutdown as well
4) UserB still sees UserA as &quot;Busy&quot; even UserA is offline
5) When UserA logs back into CUPC that status changes accordingly
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Exit out of CUPC before shutting down windows


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtu39341</guid>
</item>
<item>
<title>CUPC Client cannot login when Special Character is in the Password, Fixed CSCtx89637</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx89637</link>
<description>Symptom:

Auto Login Fails on Startup of CUPC, manual login works after auto fails
&lt;br&gt;
Conditions:

Special Character in Password
&lt;br&gt;
Workaround

Remove special character

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx89637</guid>
</item>
<item>
<title>Mapping of LDAP attributes to multiple CUPC fields breaks Add Contact, Fixed CSCsg17732</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg17732</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

The &quot;Add Contact to Group...&quot; menu is greyed out, for contacts that should be able to be added.

or 

Right click the contact return by the search, and then click add contact to group, select the group, everything looks available but after click add, the contact is not added to the group, no error shown on the screen
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Mapping more than one CUPC field to the same LDAP attribute results in the attribute being assigned to only one field, in an implementation-dependent way.  A recent change in the implementation has exposed this defect.

Because the CUPS default is to map both &quot;UserID&quot; and &quot;IM&quot; to &quot;uid&quot;, there is a high probability of trouble reports from this configuration.

It also happened to customer who would like to map userID to telephoneNumber in callmanager and CUP, because CUPC field bussinessPhoneNumber is also mapped to telephoneNumber, so this bug is triggered.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Remove the default mapping of &quot;uid&quot; to &quot;IM&quot;.
Do not map the LDAP attribute (e.g., &quot;uid&quot;) which is assigned to &quot;UserID&quot; to any other CUPC field (such as &quot;IM&quot;).

For scenario that userID is mapped to telephoneNumber, remove the mapping of businessPhonenumber to telephoneNumber, and change it to map to &quot;ip phone&quot; and then populate &quot;ip phone&quot; in AD for phone number
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

When checking in CUPC client detail log, the following error is shown:

2008-01-14  16:40:49,348 [0x120] INFO  LCMiddleware -  (MWMSG_EIM_LOOKUPCONTACTEMPTYNAME)  EPASInterfaceManager::LookupContact() - alias name is  empty

2008-01-14 16:41:15,516 [0x120] ERROR LCWIN32UI -  (WINUI_ERROR_ADD_TO_CONTACTS_FAILED) Failed to Add Contacts from Search  Results


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsg17732</guid>
</item>
<item>
<title>Jabber for Mac should support the same attributes for photos as CUPC, Open CSCtw40214</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw40214</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Photos are not displayed within Jabber for Mac because it can not pull them based on certain attributes.  Jabber for Mac does not currently support the same attributes that CUPC does to pull photos from a web server. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Use sAMAccountName as Jabber for Mac recognizes this attribute and will pull photos accordingly.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw40214</guid>
</item>
<item>
<title>DSCP settings can&#39;t be set in Vista OS the way they are in XP, Terminated CSCsl50789</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl50789</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

DSCP settings cant be set in Vista OS the way they are in XP
&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;

Cisco Unified Personal Communicator sets DSCP settings using the Counterpath SDK to the custom values dictated by Cisco policy.  

While this works in XP, Vista changes the methods used to define DSCP parameters so the old methods no longer work (all DSCP settings default to 0).  V

Vista does allow setting some Windows defined defaults but these do not follow Cisco policy.  To set custom values, you need to be an Administrator (or so it appears now).  We are still investigating with Microsoft for an API level access to change the DSCP settings dynamically.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsl50789</guid>
</item>
<item>
<title>Custom status not reflected correctly on CUPC after Phone goes off DND, Open CSCtx63624</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx63624</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CUPC status displays (RED - DND) CUSTOM STATUS in (Green - Available) Color
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Steps to Reproduce:

-Manually Set &quot;In a Meeting&quot; (Created as Custom RED Status) 
-LOCK PC 
-UNLOCK PC 
-Go off DND from the Desk Phone Itself 
-Will notice CUPC changing the Jelly from RED (DND) to Green (Available), however the Custom Message still shows &quot;In a Meeting&quot;

This only happens if the PC is locked an unlocked. If the PC is not locked this doesn&#39;t happen.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Don&#39;t Lock the PC after setting the DND status


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx63624</guid>
</item>
<item>
<title>CUP,Release QBE Session on BYE w/o &lt;MonitorStop&gt; to workaround MOC issue, Open CSCtr66310</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtr66310</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
In some cases MOC sends BYE although it has NOT sent an INFO with a CSTA &lt;MonitorStopr&gt;.
It is MOC defect, however the result is that the DN line cannot be reacquired again by the CTI Gateway on CUP, as the CTI Manager on CUCM thinks that the line is still acquired.

The reason this occurs is that CUP tears down the CSTA session on receipt of the BYE. As part of this tearing down, internal session control blocks are destroyed which also hold the session-expires timer. 
As a result the timer will never fire and so CUP will never tears down the QBE session, so the line remains acquired from the CTI Manager&#39;s point of view.

In order to prevent the line from remaining acquired, CUP needs to release the QBE Session on receving a BYE w/o first having received a INFO with CSTA&lt;MonitorStop&gt;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
MOC --- OCS --- CUP --- CUCM --- IP Phone
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restart the CTI Manager on CUCM.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtr66310</guid>
</item>
<item>
<title>CUPS 8.5.2 Core Dumping due to routeEmbedTemplate on receipt of traffic, Fixed CSCtq65613</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq65613</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

SIP Proxy core dumps
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
After the addition of a new routeEmbedTemplate, the SIP Proxy cores on receipt of new traffic
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Restart the SIP Proxy

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq65613</guid>
</item>
<item>
<title>SNMP requests timeout after period of idleness, Open CSCts98273</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCts98273</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
After upgrading a CUP server with a valid SNMP configuration to CUP 8.6. All SNMP requests sent to the serverl will timeout and not be processed.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restart the &#39;SNMP Master Agent&#39; service.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCts98273</guid>
</item>
<item>
<title>Cisco Jabber for Mac will not register softphone, Open CSCtx55581</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx55581</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When CUCM is defined by hostname or FQDN under System &gt; Server, Cisco Jabber for Mac will not register in softphone mode.
&lt;br&gt;

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

Change how the CUCM servers are defined in System &gt; Server to IP Address

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx55581</guid>
</item>
<item>
<title>FRA French Localization breaking javascript so unable to add app user, Open CSCtw58511</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw58511</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Unable to add application user on presence server CUP CUPS
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
French locale is installed on the server and browser language is set to French
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
There is an unescaped French translation that breaks the JavaScript. If you set your browser to English language you can add your application user that way.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw58511</guid>
</item>
<item>
<title>IP in Fed Domain for L2 upgrade from 7.xto8.x Causing XCP not to start, Fixed CSCtx48575</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx48575</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
IP Address in federated domain Domain for L2 upgrade from 7.xto8.x Causing XCP not to start 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Having Federated domian configured as IP address
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Deleting the federated domain configured and restarting XCP services or configure Federated domain as hostname prior upgrade.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx48575</guid>
</item>
<item>
<title>CUPC 8.5.5 registry setting that will enable video on, Open CSCtx35525</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx35525</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
No option to do a video call by default
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx35525</guid>
</item>
<item>
<title>CUPC Chat Window Closes when Closing Outlook Email with ESC Key, Open CSCtx66063</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx66063</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

The following unexpected behavior with CUPC 8.5(5) occurs when using Outlook 2010 and CUPC on the same machine and hitting the ESC key to close an Outlook 2010 message. When hitting the ESC key to close an Outlook 2010 email message, the CUPC chat window will also close. 

Steps to reproduce:
Chat window closing when closing an email message. Note does matter if application are on the same or separate screens. (Steps below, can repeat at will)
1) Open email message making it the active window 
2) Go over to CUPC to type a message to anyone and send 
3) Mouse back over to email message clicking it to make it the active window 
4) Click the ESC button to close the active email window 
5) Your last active chat window will also close at that time 
&lt;br&gt;

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

Normal Use
&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=CSCtx66063</guid>
</item>
<item>
<title>SAN certificate is not supported with the CUPS, Fixed CSCti65997</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCti65997</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
SAN certificate is not supported with the CUPS
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
We need to get the exchange integration documentation under review and possibly earlier versions to have a note that states that the Subject Alternate Name in a certificate are currently not used on the Presence Gateway security settings.  Only the Subject Common Name is used.
&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=CSCti65997</guid>
</item>
<item>
<title>7845-I2 file system goes into read-only: IBM RAID Driver not installed, Fixed CSCtr00304</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtr00304</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
The presence server file system goes into read only.
This is the cup equivalent for 
CSCtq52199    IBM RAID Driver 1.1.5-24702 not installed with 8.5.1 SU1
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUP 8.5.x, likely only after an upgrade
running MCS 7835-I2 or MCS 7845-I2
Verify with show hardware, if you are running raid driver 1.1.5-2455 you are vulnerable and you would need to either install the cop file or upgrade to a version that has the fix before the  system runs into this issue. If you do get your system in read only, follow the instructions of this field notice:
http://www.cisco.com/en/US/ts/fn/632/fn63270.html
&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=CSCtr00304</guid>
</item>
<item>
<title>CA user move operations fails to migrate DB information, Fixed CSCti40757</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCti40757</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When a user is reassigned from one CUP node to another in a cluster, any offline messages which may have been sent to that user before the user was reassigned, will not be moved to the users new CUP node.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
When a user is moved from one CUP node to another in a cluster, the Cisco UP Config Agent attempts to move offline messages and roster upgrade queue database tables to the new node for that user. This operation is currently failing due an issue with the IDS Client SDK provided by IBM.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Before reassigning the user, please have the user login via their preferred CUP client, so that they can receive any stored offline messages from their old CUP node. Once the user has read their offline messages, please immediately reassign them to their new CUP node.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCti40757</guid>
</item>
<item>
<title>Rosters on one of the presence nodes goes to a disabled state., Open CSCtt88811</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt88811</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
  Unable to add contacts to the buddy list.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
  Unable to add contacts assigned to the same presence server in the subcluster as the user.
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Need to contact tac and look at the system rosters from root.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt88811</guid>
</item>
<item>
<title>No controls in Actve Conv. window after hang up during incoming call., Fixed CSCtl79842</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtl79842</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
While on a call another incoming call is received. End the call with the first person while the second call is still incoming.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Expected Outcome:
The first call is ended gracefully and the Active Conversation window closes correctly.

Actual Outcome:
The Active Conversation window does not close and loses all controls. The only thing the user can now see is the header of the window which reads Active Conversation.
&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=CSCtl79842</guid>
</item>
<item>
<title>Jabber for Mac should document what attibutes can be used for photos, Fixed CSCtw39154</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw39154</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Cisco Jabber for Mac should document what attributes can be used to pull photos from a web server.  Jabber for Mac is not able to pull all the attributes that CUPC can.
&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=CSCtw39154</guid>
</item>
<item>
<title>Click to Call dll is causing problems to &#39;Business Objects&#39; application., Open CSCtx42286</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx42286</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Click to Call and a SAP Application called &#39;Business Objects&#39; seem to use the same dll (log4cxx.dll) with Microsoft Office applications. The result is that BO add-in fails to load when Click to Call is enabled. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Running CUPC 8.5.3 on the same client PC where BO application is also installed.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Disable Click to Call add-in with the following Reg Key:

For excel, modify the key value of LoadBehaviour from 3 (enable) to 1 (disable)
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Excel\Addins\Cisco.ClickToCall.Excel.Connect\

Likewise, for Powerpoint make the same change here
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Powerpoint\Addins\Cisco.ClickToCall.Powerpoint.Connect\




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx42286</guid>
</item>
<item>
<title>Admin GUI: User Mgmt -&gt; End User -&gt; Logged-in CUPC error, Fixed CSCtq01630</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq01630</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

In CUPS under User Management &gt; End User, if you select the drop down for find &quot;Logged-in Cisco Unified Personal Communicator&quot; you will see users that are logged in as well as users that have logged in and then logged out.  CUPS keeps a cache of all users logged in and does not clear it when a new search is performed.  Because of this, when you search this field, you will find users who are logged in or who have previously logged in but are no longer logged in.
&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=CSCtq01630</guid>
</item>
<item>
<title>Upgrade from 8.6(1) to 8.6(3) is failing, Open CSCtx65532</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx65532</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Upgrade from 8.6(1) to 8.6x fails
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

When you have associated 3rd party compliance servers with the cup servers 

CUP admin pages ----&gt; Messaging ---&gt; Compliance

alternatively if the FTExtDbProcessNodeMap table is not blank

run sql select * from FTExtDbProcessNodeMap
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

1.before upgrade remove the assiciation from the 3rd party compliance server and cup servers
2. ensure that FTExtDbProcessNodeMap is blank
run sql select * from FTExtDbProcessNodeMap
3.Perform the upgrade
4. Associate the 3rd partly compliance servers with the CUP servers as before 




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx65532</guid>
</item>
   
</channel>
</rss>

