<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"> 
  <channel>
  <title>Endpoints 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 10:46:43 EST</pubDate>
  <lastBuildDate>Mon, 13 Feb 2012 10:46: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>DND Option can not be changed for IP Communicator, Fixed CSCtt01052</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt01052</link>
<description>Symptoms: 

DND Option can not be changed for IP Communicator.

The only option avaliable under settings is &quot;Ringer off&quot;  . The other two options &quot;call reject&quot; &quot;use common phone profile setting&quot; are not present. This is causing the &quot;update all subscribtions&quot; to fail under the phone services for extension mobility.
&lt;br&gt;  
Conditions: 

Issue is present on 8.6.2.10000-30   release.
&lt;br&gt;

Workaround:
None


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt01052</guid>
</item>
<item>
<title>8945 phone does not show EM service, Fixed CSCtx70127</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx70127</link>
<description>Symptom:

the phone UI does not show up the extension mobility service
&lt;br&gt;
Conditions:

service provisioning = both
&lt;br&gt;
Workaround:

service provisioning= default or internal



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx70127</guid>
</item>
<item>
<title>Intermittent call recording failures via BIB, Open CSCtx84429</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx84429</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Calls to 3rd party Recording Server via BIB are failing intermittently.  CCM SDI Traces will show CUCM sending a BYE to the Recording Server with cause=47.

SDL traces will show rc=1 or result=1 being returned from the phone in the SMT Ack.

006576274 |2011/12/16 16:29:42.559 |100 |SdlSig    |StationStartMediaTransmissionAck      |restart0                       |StationD(2,100,57,1478)          |StationInit(2,100,56,1) |2,100,56,1.1724152^172.30.21.152^SEP64A0E7F6F42B |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] rc=1 ConfId=41515552 PartyId=0x200586b CallRef=41515558 transmitIpAddr=.type=0 .addr=0x{ac,1e,15,98,0,0,0,0,0,0,0,0,0,0,0,0}(172.30.21.152) Port=0

Phone debugs will show the following message.

2477: ERR 15:46:21.409419 DSP: MTTHREAD-bind error*** 125:Address already in use at host ac1e15d8 port 503e
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Call recording to 3rd party server via BIB.  Firmware affected so far appear to be 9.2.1 and higher.
&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=CSCtx84429</guid>
</item>
<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>69XX phone fails to access to the custom personal or corporate directory, Fixed CSCtw71667</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw71667</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
On personal or corporate directory, getting an error! saying  &quot; Unknown Error &quot;.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;

Using a custom corporate or personal directory the IP phone uses using the cache default value for the URL(URL (/ccmpd/pdCheckLogin.do?name=) instead the custom one URL 
&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=CSCtw71667</guid>
</item>
<item>
<title>CIPC halt in blank during startup due to corrupted registry, Fixed CSCts11852</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCts11852</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CIPC stuck in blank screen during startup because of corrupted registry hive.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

It is an intermittent issue, it could happen on all available version including 8.6.1. Upgrade version without deleting registry hive  [HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator\Device] does not help
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

1. identify the corrupted hive by searching the keyword loading halt from CIPC problem report, below traces shows that the registry hive [HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator\Device\device.calls.placed]  was corrupted.

Wed Aug 03 08:48:21.109 :  SPCL : (  4920) -RegHlp| Java_cip_props_Win32Registry_readString(val553): Win32RegistryReadValueSize return 0 length
Wed Aug 03 08:48:21.109 :   DET : (  4916) -VM| timermgr MQThread|SystemManager:? - Error preloading module &quot;Property Manager&quot;/propertymgr(3): java.lang.RuntimeException: Read Default Value Method Not Implemented device.calls.placed
Wed Aug 03 08:48:21.109 : ERROR : (  4916) timermgr MQThread|SystemManager:? - Error preloading module &quot;Property Manager&quot;/propertymgr(3): java.lang.RuntimeException: Read Default Value Method Not Implemented device.calls.placed
Wed Aug 03 08:48:22.477 :   DET : (  4916) 12:48:21a|java.lang.RuntimeException: Read Default Value Method Not Implemented device.calls.placed at cip.props.Property$DefaultableImpl.readDefaultValue(Unknown Source)
Wed Aug 03 08:48:22.477 :   DET : (  4916) -VM| timermgr MQThread|SystemManager:? - propertymgr/&quot;Property Manager&quot;, &lt;B&gt; loading halted &lt;/B&gt;

2. delete the registry hive found in step 1 and restart CIPC

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCts11852</guid>
</item>
<item>
<title>Cisco 8945 Missing External XML Directories after upgrade to 9-2-3-5, Fixed CSCtx49293</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx49293</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Cisco 8945 Phone External XML Directories do not show on Phone Firmware SCCP594X.9-2-3-5
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Cisco 8945 Phones upgraded to Phone Firmware to SCCP894x.9-2-3-5
Service Provisioning is set for Both
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
No known work around at this time.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx49293</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>Cisco 8945 Missing Extension Mobility Service after upgrade to 9-2-3-5,   CSCtx71144</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx71144</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Cisco 8945 Phone Extension Mobility Service does not show on Phone Firmware SCCP594X.9-2-3-5
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Cisco 8945 Phones upgraded to Phone Firmware to SCCP894x.9-2-3-5
Service Provisioning is set for Both
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Modify Service Provisioning to Internal - Note this will break any External XML Directories



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx71144</guid>
</item>
<item>
<title>Phone cannot send out DTMF after pressing ** during voice mail, Terminated CSCtq14847</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq14847</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Phone cannot send out DTMF after pressing ** during voice mail
Pressing number key during any call seems abnormal. (no key tone heard, no DTMF packet captured, no feedback when calling voice mail)
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
After doing the following scenario
1.Get connected with voice mail server (Unity).
2.When hearing &quot;Enter your PIN, followed by pond&quot; or &quot;Hello, Cisco unity connection messaging system ...&quot;,  press **. The call will be ended.
May need to try several times to reproduce this issue.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Reset the phone



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq14847</guid>
</item>
<item>
<title>6945 sccp: SW polling time improvement for RTL Clipping issue, Fixed CSCtq80427</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq80427</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
  the delay is from the phone sending the rtp. i.e if 6900 phone calls a Mobile phone &amp; the Mobile phone says the numbers 1,2,3 etc the 6900 phone can hear properly. However, if Mobile phone calls 6900 phone &amp; the 6900 phone user says the numbers 1,2,3 etc, the One is always lost.
 
    In another Example with two 6900 Phones, Phone 1 calls Phone 2, Phone2 picks up the call &amp; says the number 1,2,3 etc only 2,3 can be heard in the rtp stream from Phone2 to Phone1.
&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=CSCtq80427</guid>
</item>
<item>
<title>Add customer facing info for All Calls function enhancement in 9.2.2, Fixed CSCtt96205</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt96205</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
99xx model phones offer new behavior for &quot;all calls&quot; feature beginning in load 9.2(2).  That behavior is not documented.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Phone load 9.2(2) introduced the feature. 

http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/9971_9951_8961/firmware/9_2_2/release_notes/9900_8900_922.html#wp219311

However, a new device pack is required to add the new configuration option to the device specific configuration page in CCMAdmin.  

The devicepack is not yet released.
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;
1. Reference this bug for documentation about the new behavior
2. apply the new device pack to CUCM when it releases
3. configure the new option on the phone configuration page in ccmadmin


The device packs released to Cisco.com on October 28, 2011:
8.6.x dev pack
cmterm-devicepack8.6.1.21015-1.cop.sgn
cmterm-devicepack-8_6_1_21015-1_readme.docx

8.5.x dev pack
cmterm-devicepack8.5.1.13042-1.cop.sgn
cmterm-devicepack-8_5_1_13042-1_readme.docx

8.0.x dev pack
cmterm-devicepack8.0.3.23041-1.cop.sgn
cmterm-devicepack-8_0_3_23041-1_readme.docx

7.1.x dev pack
cmterm-devicepack7.1.5.34074-1.cop.sgn
cmterm-devicepack-7_1_5_34074-1_readme.docx


Update 11/15: The devicepacks above currently do not include changes to reveal the &quot;Show All Calls on Primary Line&quot; configuration option. Investigation is underway.

Update 02/09/2012: This feature is yet to be included in a device pack.  Please check back for updates regarding the defect.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt96205</guid>
</item>
<item>
<title>Default ringtones for 6945 phones not working in version 9-2-2-4, Fixed CSCtx04784</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx04784</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
customer has an issue with the chirp ring tone, users can play that continuously, however once they
hit the set button, they can see the tone as if its ringing/playing but no sound unless they hard
reboot the phone, then only they can hear the Chirp tone play again.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
problems with ringtones in the 69XX IP phones are only happening  with the firmware version 9-2-2-4. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Hard reboot of phone to bring back phone to play normally the CHIRP tones



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx04784</guid>
</item>
<item>
<title>CIPC is not supporting secure EM (HTTPS login for EM), Terminated CSCtx18810</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx18810</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CIPC is not supporting secure EM (HTTPS login for EM)
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use HTTP login for EM


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx18810</guid>
</item>
<item>
<title>Intermittently, CIPC users face one way audio issue, Fixed CSCtx80563</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx80563</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
One-way audio--CIPC user cannot hear the other party
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Receiving a PSTN call on Windows XP
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Hold and resume the call

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx80563</guid>
</item>
<item>
<title>Cisco IP Phone 9951/8961 slow offhook dial issue, Fixed CSCtx41256</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx41256</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
The digits were shown slowly on 9951/8961 when press speaker and dial digits very fast.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Dial very fast.
BLF feature enabled.
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
disable BLF subscription.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx41256</guid>
</item>
<item>
<title>7937 does not respond to EAPOL/EAP message sent by switch during 802.1x, Fixed CSCsr95344</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr95344</link>
<description>






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

7937 does not respond to EAPOL/EAP message(version 2) sent by switch during 802.1x authentication procedure,which appears only support version 1 message.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

switch:3500,3600,3700 series sends eap/eapol version 2 802.1x frames,phone does not respond to it.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

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

802.1x frame version mismatch.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsr95344</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>Video Phone: 9951 Need a knob to disable DF bit, Open CSCtq90715</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq90715</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Need an option to be able to set the DF bit to 0 on the fourth-gen-phones 9951.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
This was first identified on a fourth-gen-phone 9951 running 9-1-1 SR1 connecting to an ASA using anyconnect VPN.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
If the packets are too large use a layer 3 device in the path to clear the DF bit or ignore the DF bit so, the packets can be fragmented as needed.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
9951 phone may send large packets (1440 bytes) with the DF bit set to 1 and the MTU set to 1290. The ASA is unable to fragment these packets due to the DF bit set to 1.
More over the max value for svc mtu on the ASA is 1406 bytes to allow for DTLS  (max 94 bytes).
Use the &lt;B&gt;svc df-bit-ignore enable&lt;/B&gt; command on the ASA under group-policy associated with webvpn.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq90715</guid>
</item>
<item>
<title>Poor audio quality when the 792x is receiving unicast RTP via XML push, Fixed CSCtj65901</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtj65901</link>
<description>Symptom:
Poor audio quality when the 792x is receiving unicast RTP via XML push and proxy ARP is enabled on the AP.
There are no issues when the 792x phone is sending unicast RTP via XML push or with a standard 2 way call via SCCP.
&lt;br&gt;
Conditions:
792x phone receiving unicast RTP via XML push when the AP has proxy ARP enabled.
&lt;br&gt;
Workaround:
Disable proxy ARP or use multicast RTP.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtj65901</guid>
</item>
<item>
<title>792x stuck in DHCP mode when out of range of the supposed connected AP,   CSCto98949</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCto98949</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
792x stuck in DHCP mode when out of range of the supposed connected AP 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
N/A
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restarting the phone resolves the problem.
Going back within the range of the AP that the phone thinks it is associated to may restore connectivity.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCto98949</guid>
</item>
<item>
<title>Crash Dump due to timing, Fixed CSCtr09356</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtr09356</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
SIP Stack generates Crash Dump due to timing.
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
- ATA187
- Crash Dump
- Quick operation may be one of the conditions.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Reset ATA187, or Switch it off/on.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtr09356</guid>
</item>
<item>
<title>CMR records show null values for 6900 series phones, Fixed CSCtl12755</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtl12755</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CMR data is missing for 69xx Phones.   CUCM does display CMR data for other
phone models. 
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
69xx phones are on 9.1.1 FW.  Any FW prior to this release does not support CMR
for 69xx phones. 

Network trace taken from 69xx phone show it is sending a K-Factor data,  these
are values used to populate CMR record.. However, the format of data is
incorrect.   CUCM does not read the data and populates CMR records with null 
values
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
By upgrading the firmware version to the latest release
cmterm-69xx-sccp/sip.9-2-1-sr1-uns.cop.sgn you may be able to fix this issue
with CMR records.





</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtl12755</guid>
</item>
<item>
<title>CUCi config guide for display caller info to IE gives incorrect registry, Open CSCtx38237</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx38237</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
After configuring the &#39;Display Caller Information in Internet Explorer&#39; for CUCiLync/Moc and testing it, the feature does not seem to work.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCiLync/Moc and the 3 registry keys installed to either:

HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Client Services Framework\AdminData
or
HKEY_CURRENT_USER\Software\Policies\Cisco Systems, Inc.\Client Services Framework\AdminData
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Install the 3 keys in either:

HKEY_CURRENT_USER\Software\Policies\Cisco Systems, Inc.\Unified Communications\CUCIMOC
or
HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Unified Communications\CUCIMOC

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx38237</guid>
</item>
<item>
<title>9951 audio only, no video, for call from 9951 Tandberg C20,   CSCtq93198</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq93198</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
9951 causes audio only (no video) when calls are set up from a SIP 9951 phone to a Tandberg C20.

However, if the call is set up from the Tandberg C20 to the 9951 they don&#39;t have any issues (with video also functioning).
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Firmware 9.1(1) or 9.2(1)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Earlier, 9.0(3) firmware does not have this issue (with audio and video in both directions).



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq93198</guid>
</item>
<item>
<title>EM does not work with service provisioining set to both, Fixed CSCtx02578</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx02578</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Extension Mobility not working on 6921/6941 phones running sccp firmware 9-2-2-6
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
6921/6941 phones running firmware version 9-2-2-6
Service provisioning parameter set to both
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use previous version: 9.2(1)ES1
Change service provisioning parameter to Internal or External URL

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx02578</guid>
</item>
<item>
<title>6941/6921/6961 Ring Setting (Phone Active) doesn&#39;t work properly, Open CSCtx81179</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx81179</link>
<description>&lt;B&gt;Symptom:For IP phone 6941/6921/6961, whenever you go to the CM Web admin page select a phone, then select the line on the phone and scroll down to &quot;Ring Setting (Phone Active)&quot; selection and select Ring the phone won&#39;t respond like a 79XX phone. The phone should ring whenever a second call comes in, but it simply shows the call waiting information instead of actually ringing the phone as though it was onhook. 

&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Conditions:Maximum Number of CallsRequired Field	set to 4
Busy TriggerRequired Field set to 2  

This occurs on firmware all the way up to 9-2-2-6 and CUCM System version: 8.6.2.20000-2&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Workaround:No workaround known at this point. &lt;/B&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx81179</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>6945 phone can not handle &quot;()&quot; in corporate directory, Open CSCtx76044</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx76044</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
6945 can not dial number via corporate directory when number contains &quot;(&quot; or &quot;)&quot;, for example:
+12 (345) 6789
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Occurs only when phone number contains &quot;()&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=CSCtx76044</guid>
</item>
<item>
<title>Cisco 792x  doesn&#39;t honor URL encoding ISO-8851-1, Open CSCtx16478</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx16478</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When web pages (xml service) is set to use ISO-8859-1 the &quot;&lt;CiscoIPPhoneInput&gt;&quot; object still uses UTF-8 when sending the query string. 
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
Using IP Phone Services
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Use UTF-8 (if possible, may not help in all cases if ISO-8859-1 is required).

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx16478</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>6941 / 6961 phones may freeze after many successive calls, Fixed CSCtw93646</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw93646</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
- Same symptoms as found in CSCtw45969 
- The phone freezes in a ringing state.  Going off hook gives no dial-tone, and only menu buttons respond.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
n/a
&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=CSCtw93646</guid>
</item>
<item>
<title>6921 gets stuck due to memory allocation, Fixed CSCti43121</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCti43121</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
6921 gets stuck after several hours / days. Screen stays frozen, and time doesn&#39;t change anymore. A manual reset on the phone doesn&#39;t solve the problem, and the phone needs to be disconnected and reconnected.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
6921 with firmware 8.5(3), 8.5(4), 9.0(2) and (3)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Restart the phone by disconnecting it from the power source.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCti43121</guid>
</item>
<item>
<title>11n AP on UNII-1 doesn&#39;t demodulate ACKs from 7925G, Open CSCtx43105</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx43105</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Intermittently, a 7925G phone may experience choppy audio, or lost audio.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

7925G is associated to an Aironet 802.11n (1040, 1140, 1250, 1260, 3500) series
access point, which is in the UNII-1 band (channels 36-48).
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Some or all of these may mitigate or eliminate the problem:

1. Move the access point to a UNII-2, UNII-2 Extended or UNII-3 channel.
(This is the only known 100% workaround.)

2. Disable DTPC on the AP (e.g., on a WLC, uncheck the &quot;DTPC enabled&quot; box on
the wireless network.)

3. Configure the 6Mbps data rate as the sole mandatory rate.

4. Replace the 11n APs with 11a/g APs.
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

Although the symptoms of this bug are identical to those of the bugs CSCta65070
(9971)/CSCtg04992(7925G), this bug is experienced even when the phone is
running firmware with the CSCtg04992 fix.

This bug is intended to provide fix on the phone side.  Additionally, the bug
CSCtt67979 has been filed to explore the feasibility of implementing a workaround
on the access point side.




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx43105</guid>
</item>
<item>
<title>ALL-LANG:CIPC:UI: Olsen time zones not supported, only legacy time zones, Fixed CSCte84749</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCte84749</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Incorrect date/time is displayed on CIPC UI.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Using non-legacy time zones (Olsen time zones)
CIPC 7.0(x) connected to CUCM 8.0 or later
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use Legacy time zones

Please note that CIPC 7.0(x) is based on TNP phone load 8.3.5 and only supports the legacy time zones.  Support for the non-legacy time zones (Olsen time zones) is in TNP phone load 9.0(2).


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCte84749</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>Hissing sound is heard when the application is running, Fixed CSCtc95916</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc95916</link>
<description>






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

A background noise (hissing sound) is heard when the application is running
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Version 7.0(3).
&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=CSCtc95916</guid>
</item>
<item>
<title>792x sends SCCP as UP0 when secure SCCP is used, Fixed CSCtx08144</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx08144</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

792x sends SCCP as UP0 when secure SCCP (TCP port 2443) is used.
If non-secure SCCP is used (TCP port 2000), then the 792x phone sends SCCP as UP4 as expected.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Using the 792x phone with secure SCCP.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Use non-secure SCCP.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx08144</guid>
</item>
<item>
<title>Minimize RTP Delay from HW side when answering call on RT-Lite, Open CSCtd57345</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd57345</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
RTP delay happens when answering call on RT-Lite.
&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;
This is caused by HW limitation that charge/discharge noise would happen when answering call. And the expected delay from HW side would be 260 +/- 20 ms now. Currently to avoid any noise when picking up through speaker/softkey, the software value should be at least 280ms, which causes around 370~430ms RTP delay between MediaPathChange event and first sent RTP packet on the callee side. This is somewhat not consistent with our expectation.

Need to find out the exact delay in HW, and check whether we can improve the performance.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd57345</guid>
</item>
<item>
<title>CUPC should not write files with invalid characters for filesystem, Open CSCtt93768</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt93768</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CUPC users cannot listen to voice messages when caller ID contains special characters.
&lt;br&gt;

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

When CUPC downloads voice messages, it includes the caller ID as part of the file name. It is possible for caller ID&#39;s to contain characters such as *, ?, /, ect, which are not allowed to be part of a file name by the file system.
&lt;br&gt;

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

Remove special characters from the caller ID before the call goes to the voice mail server.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt93768</guid>
</item>
<item>
<title>Delay in starting RTP from 6941, Fixed CSCtc96381</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc96381</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Calling from any other phone model to a 69xx, after going offhook on the 69xx it takes about 2 seconds before caller and called party can hear each other. This is in the same location where other phones they are working fine. Phone are connected to the same switch and vlan of the CUCM.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
So far reproduced on 6941/61, but applicable to all 69xx series.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;
Two delays are noticed in the tests with the 6941.

- It takes about 0.14 sec before the 6941 socket is ready to receive the incoming RTP packets sent from the other phone to the desired. This causes the 6941 to generate ICMP port unreachable packet until the socket is ready.

- It takes about 0.67 seconds between the StartMediaTransmission and  the 6941 first outgoing RTP packet,

So there are about 0,81 seconds before 6941 is ready to listen and sending RTP packets. This is not an enormous time, but if user is very fast on picking up the handset this can be perceived. 
Tested in the lab, with a 7970 on speakers calling to a 6961. If the 6961 user goes off hock very fast and immediately start talking &quot;one, two, three, four, five, ...&quot;, on the 7970 only starting from &quot;two&quot; or &quot;three&quot; can be heard, so the first words are missed.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtc96381</guid>
</item>
<item>
<title>Cannot set on UPC primary phone as 6921 device, Terminated CSCto60333</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCto60333</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;	Cannot set on UPC primary phone as 6921 device
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

tested on call manager version 7.1.5 and onwards if you  try to on a unified Personal Communicator (UPC) to set the primary phone as a 6921 device we get the following error message
message &quot;Update failed. [10205] The device must use the same or fewer DLUs as its primary phone&quot; same worked perfectly on version CUCM 7.1(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=CSCto60333</guid>
</item>
<item>
<title>Cannot make a new call with disable speaker phone from 7921, Fixed CSCtl81594</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtl81594</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
7921 cannot make a new call.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Using CUCM with fixed CSCtj36878 and Checking &quot;Disable speaker phone&quot; on 7921.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Not check &quot;Disable speaker phone&quot;.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtl81594</guid>
</item>
<item>
<title>69XX phone parses incorrectly messages in Hebrew language, Fixed CSCtq94661</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq94661</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
ip phone 69XX parses incorrectly XML 
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
when XML document is sent to ip phone and contains symbols in Hebrew language, ip phone prints this symbols from right to left: instead of 2005 you see  5002 for example. 
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
pick up the handset or press any key on the phone
any of these actions changes the output on the screen to correct one

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq94661</guid>
</item>
<item>
<title>Cisco IP Phone 9971 has one-way audio after 15 minutes, Fixed CSCtq79612</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq79612</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
One way audio on 9971 phone after 15 minutes. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
9971------&gt;SIP-----CUCM------SIP--------&gt;SBC(Session border controller)-----&gt;PSTN
One-way audio when dialing into an external conference bridge

RTP sequence count resets but SSRC stays the same. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
had site increase MIN-SE timer in service parameters to 86400. This means re-invite will not
be sent to refresh timer for 12 hours

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq79612</guid>
</item>
<item>
<title>8945 SCCP: Sometimes, phone doesn&#39;t update time in header, Fixed CSCtl73175</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtl73175</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
The time on the 8945 display may not be correct.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Problem has been observed on following firmware versions:
894x SCCP894x.9-1-1-01-35
894x SCCP894x.9-1-2-SR-1
894x SCCP894x.9-2-2-0

Other 894X firmware may be affected as well.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
No known work around at this time.




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtl73175</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>9971/9951 should clearly say when power-related issues are experienced, Open CSCtj72507</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtj72507</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Currently when the 99XX phones fail the power negotiation with a PoE device when adding new hardware accessories such as the USB camera, the phone currently doesn&#39;t display a clear error message describing the problem.

You can only find out by looking at the phone debugs:

1. ssh to the IP Phone
2. Login to the phone
3. Run /usr/sbin/sdump -t
4. Review the logs. 

It could show something like this:

7417 NOT 18:10:21.008834 PWRMAN-eventPwrNeg(): curReq.valid: 1  info-&gt;curPwr: 11700  curReq.newPwr: 13500 
7418 WRN 18:10:21.008926 PWRMAN-eventPwrNeg(): power neg failed: TIMEOUT 
7419 NOT 18:10:21.063069 DMAN(1458)-isPowerAvailable(): Response from PM: NO POWER
7420 WRN 18:10:21.063400 DMAN(1458)-handleNewDevice(): Power Required is not available so rejecting device.
7421 NOT 18:10:21.063665 DMAN(1458)-parseAndHandleUdevMsg(): handleNewDevice returned Error: 128 disabling device
...
7492 NOT 18:12:11.786161 CDP-In Cfg_Idle_EvCdpDone_XIdle--CDP is Disabled and LLDP inhibited...wait for LLDP or 5 seconds

7493 NOT 18:12:11.935593 PWRMAN-eventPwrNeg(): curReq.valid: 1  info-&gt;curPwr: 11700  curReq.newPwr: 13500

7494 WRN 18:12:11.935685 PWRMAN-eventPwrNeg(): power neg failed: TIMEOUT

7495 NOT 18:12:16.787817 CDP-configSelectVLAN(): 0 OP_USE_ADMIN_DFLT:5 oper:4096 cdp:4096 lldp:4096 admin:4096 mac:0:0:0:0:0:0

7496 WRN 18:12:16.789123 CDP-cdpSetCos(): port 1, trust = 1, cos = 0

7497 NOT 18:12:31.938891 PWRMAN-eventPwrNeg(): curReq.valid: 1  info-&gt;curPwr: 11700  curReq.newPwr: 13500

7498 WRN 18:12:31.938978 PWRMAN-eventPwrNeg(): power neg failed: TIMEOUT
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
Above trace is seen when a switch is used without proper PoE support (using PoE injectors) and not running CDP/LLDP.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use a powerbrick to overcome the power negotiation issue, or use a switch which properly supports power renegotiation through CDP or LLDP.

Note: Firmware 9.0(1) only supports power renegotiating via CDP. 9.0(3) and above supports both CDP and LLDP.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtj72507</guid>
</item>
<item>
<title>CME: 9971 does not negotiate H.264 Non-interleaved packetization mode, Open CSCtx87044</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx87044</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Cisco 9971 phone may not negotiate H.264 video call if Non-interleaved packetization mode is requested. 

Example of a SDP representing H.264 non-interleaved packetization mode :

m=video 5062 RTP/AVP 109
a=sendrecv
a=rtpmap:109 h264/90000
a=fmtp:109 packetization-mode=1;profile-level-id=42C01E
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This problem was observed when the phone is registered with Cisco Unified Communication Manager Express (CUCME).
&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=CSCtx87044</guid>
</item>
<item>
<title>Phones do not failback to CUCM with 9.2.3 SIP firmware, Open CSCtx89362</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx89362</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Phones will fail to fallback to primary CUCM if the failover time lasts at least 5-6 minutes.  Subsequent calls fail on affected phones running 9.2.3 SIP firmware.
&lt;br&gt;


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

1. Do not configure SRST on CUCM.
2. SIP Phone with 9-2-3 load register with CUCM.
3. Shutdown the Cisco CallManager service on CUCM.
4. Phone will goes to failover state.
5. Wait 5 ~ 6 minutes or longer time.
6. Restart the Cisco CallManager Service
7. Phone will never fallback to CUCM.
&lt;br&gt;



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

Reset phone(s).

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx89362</guid>
</item>
<item>
<title>7925 sometimes takes 1+ second to respond to WPA M1 key message, Open CSCtt38270</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt38270</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

A wireless phone call may experience a voice gap of 1.5 - 2 seconds when it roams if using WPA2-PSK.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

7925G is configured to use WPA2/AES PSK.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Configure some key management method to avoid performing a full WPA2 key exchange
at each roam time.  For example, EAP with CCKM, or static WEP.

If using PSK, then reducing the WPA key retransmission timeout (e.g., on a WLC,
via &quot;config advanced eap eapol-key-timeout 250&quot;, may ameliorate the problem
somewhat (e.g. bring the outage duration down from 2.5 to 1.7 seconds.)
&lt;br&gt;
&lt;B&gt;Further Problem Description:&lt;/B&gt;

A wireless packet capture, or a &quot;debug client&quot; on the WLC, will show that the WLC/AP
transmit the M1 key message to the phone (and the capture shows that the phone ACKs
it), but the phone does not send its M2 key. So the WLC/AP have to retransmit the M1 key,
till finally the phone responds.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt38270</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>69XX phone fails to join multicast stream for paging audio, Fixed CSCtw85011</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw85011</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Multicast paging does not play any audio on Cisco 6921, 6941 and 6961 phones.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

The 6921-41-61 phones are registered to a Communications Manager Express system version 8.6 or higher running firmware version 9-2-1 or 9-2-2. The speakerphone button will light up green and the phone LCD will show the label configured under the paging-dn but no audio will be heard.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Downgrade the phone firmware to 9-1-1.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw85011</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>69XX phone fails to play Multicast MoH, user hears Tone on Hold instead, Fixed CSCtw85062</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw85062</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Multicast Music on Hold (MoH) does not work on Cisco 6921-41-61 phones.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Phones are running firmware 9-2-1 or 9-2-2 and are registered to a Cisco Communications Manager Express (CME) system. The 69xx user will hear three quick beep tones instead of MoH when put on hold by the other end.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Downgrade the phone firmware to 9-1-1.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw85062</guid>
</item>
<item>
<title>69xx Active call timer resets to 0 in shared line configuration, Fixed CSCtx69723</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx69723</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
In certain call flows, the active call timer may reset to 0 for 69xx phones.

It has been seen to involve calls on hold across shared lines
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
- So far this is seen with call flows involving shared lines and calls on hold
- One way to reproduce is to call between to 69xx phones and upon answering
  put the call on hold immediately (either phone).  While on hold, press the 
  Applications button twice from the phone that Hold was pressed on.
&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=CSCtx69723</guid>
</item>
<item>
<title>VVM Failover does NOT work, Open CSCtq26371</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq26371</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CSF client such as CUCILYNC can NOT failover the Visual Voice Mail (VVM) to the secondary Cisco Unity Connection server (CUC) when primary CUC is unavailable.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
VVM feature works fine with primary CUC.
&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=CSCtq26371</guid>
</item>
<item>
<title>Cisco 7975: tcp MSS is bigger than IP MTU on interface, Fixed CSCtx46579</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx46579</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Cisco 7975 announces TCP MSS 1400 which is bigger than actual MTU on physical port of phone. This creates IP fragmentation for outgoing packets.
&lt;br&gt;

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

SIP firmware.
&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=CSCtx46579</guid>
</item>
<item>
<title>7925 phone loses 5 GHz connection intermittently with OEAP600, Open CSCtn75346</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtn75346</link>
<description>Symptom:
7925 phone loses 5 GHz connection intermittently with AP600.
No connectivity issues when using 2.4 GHz.
&lt;br&gt;
Conditions:
Using AP600 and 7925 on 5 GHz.
&lt;br&gt;
Workaround:
Use 2.4 GHz or an alternate AP platform.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtn75346</guid>
</item>
<item>
<title>IP phone Anyconnect does not detect P to P VPN status after WAN outage, Open CSCtx59490</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx59490</link>
<description>Symptom:
IP Phone Anyconnect does not detect Point to Point VPN status after WAN/IP failure.
&lt;br&gt;
Conditions:
Anyconnect  phones registered to CUCM through VPN, looses IP connectivity due to WAN/ISP outage, tries to register via VPN again using its own VPN profile. Phone does not have the ability to detect that WAN/IP connectivity has been restored and will continue to try to regsiter to the call manager using its own VPN profile.
&lt;br&gt;
Workaround:
Reset the phone

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx59490</guid>
</item>
<item>
<title>6961 can lock up when answering shared line, Open CSCtx68386</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx68386</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
6961 locks up after trying to answer shared line
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
2 phones registered to CME with a shared line on both phones.
Make a call to the shared line and answer on one of the phones.
If the phone which did not answer is a 6961 and presses the shared line key, the phone will lock up and require a power recycle to recover.
&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=CSCtx68386</guid>
</item>
<item>
<title>inconsistency with cucm and ip phone for handset/headset monitor param, Fixed CSCtg89332</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtg89332</link>
<description>
&lt;B&gt;Symptom:&lt;/B&gt;
Any version of CUCM which supports the headset/handset monitor feature and any
of the following ip phones registered to it 7942/7945/7962/7965/7975.
 
Audio is played from both the handset/headset by default and so to cure this,
you can upgrade your phones firmware which is documented by the defect
&#39;CSCsz35375    Placeholder of CIA-1859: Headset/Handset Monitor&#39;
 
 After the upgrade of the firmware, the phone configuration pages state that
the handset/headset monitor parameter is disabled, when in fact it is not.
&lt;br&gt; 
 &lt;B&gt;Conditions:&lt;/B&gt;
 N/A
&lt;br&gt; 
 &lt;B&gt;Workaround:&lt;/B&gt;
Change the handset/headset monitor parameter to enabled from the phone config
page &gt; save &gt; change it back to disabled &gt; save &gt; reset the phone. This should
then apply the correct config to the phone.
 
 Alternatively, you can make any change/updates to the device so that the
phones configuration file is updated and this will also add in the
handset/headset parameter
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtg89332</guid>
</item>
<item>
<title>missed call feature request on 694x, Open CSCtu29050</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtu29050</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
missed calls do not show up on the phone. no shortcuts like the 99xx phones. is not customer friendly usage
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
missed call on 69xx phone. select the line, gives the option to make a new call unlike the 9951 phone which allows the missed calls to be checked by using the button opposite to the line. 

similar thing does not work on 694x phones  
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
none so far. 


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtu29050</guid>
</item>
<item>
<title>792x wireless phone send incorrect character in menus, Fixed CSCtx20959</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx20959</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
792x wireless phone send incorrect character when the drop down menu is visible and an international character is selected.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
When using XML menus (ie. IP Phone Services)  using locales, the 792x will send incorrect character if you press the send button before the drop down menu has disappeared. Issue has been confirmed using Scandinavian languages, but may also apply for other locales. Issue does only occur when a character after the standard English character is selected.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Wait for the dropdown menu to disappear before press send/submit.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx20959</guid>
</item>
<item>
<title>CUPC cannot play new voicemail message composed via VMO, Open CSCtr99263</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtr99263</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CUPC cannot play new voicemail&#39;s which were created via VMO
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
VMO user sends new voicemail to CUPC user
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Call into CUC with your IP Phone and send the message that way instead.

Or send the message with VMO and the recipient can listen to the voicemail via their IP Phone.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtr99263</guid>
</item>
<item>
<title>6941 Unable to disable corporate directory on sip firmware 9.2.1, Fixed CSCtt99696</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt99696</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Corporate directory is still available even though disabled under device -&gt; phone services
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
6941 SIP phone running firmware 9.2(1)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use previous firmware 9.1(1) or SCCP firmware 9.2(1)



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt99696</guid>
</item>
<item>
<title>7900 Series NOTIFY message body missing trailing CRLF, Fixed CSCtq15731</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq15731</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Calls may fail from 7900 series phone.  Call will never setup.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Traffic must go through a PIX/ASA/FWSM with sip inspection enabled.  ASA will corrupt the NOTIFY and INVITE packets.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Disable SIP inspection on firewall if possible.  Only possible if:
1) No NAT translation occurs in the path
2) Able to open up access for RTP streams in interface ACLs



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq15731</guid>
</item>
<item>
<title>SCCP/SIP IP phone should play DTMF/Sidetone when receiving RFC2833, Terminated CSCtg11675</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtg11675</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
IP phones do not play DTMF or sidetone when receiving RFC-2833 for DTMF relay. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
IP phone running SIP or SCCP firmware where the DTMF relay used on calls to PSTN, typically with SIP trunks, use RFC2833.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use OOB DTMF method. In a CUBE environment, switch to h.323 between the CUBE and CUCM and perform OOB DTMF relay (h245-alphanumeric/signal). 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtg11675</guid>
</item>
<item>
<title>PC cascaded to CP-7911 can NOT be authenticated by 802.1x, Terminated CSCsw48615</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsw48615</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
PC cascaded to CP-7911 can NOT be authenticated by 802.1x.






&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
C3560 ------- CP-7911 -------- PC
cmterm-7911_7961-sccp.8-3-4SR1.cop
c3560-ipbase-mz.122-25.SEB4

After rebooting a Phone the PC can is authenticated and connect to IP network.
But then after rebooting the PC, it can NOT be.

It occurs when Span to PC Port is Enabled.
It does NOT occurs when Disabled.

It dose NOT occur with CP-7941/61 regardless of Span to PC Port.

CP-7911 does NOT send through EAP(Request, Identity) from C3560 to PC.





&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Span to PC Port = Disabled.



&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=CSCsw48615</guid>
</item>
<item>
<title>CAST problem for video call when in deskphone mode, Fixed CSCtn26111</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtn26111</link>
<description>&lt;B&gt;Symptom:Video call fails while in deskphone mode&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Conditions:all config appears ok but video call consistently fails when in deskphone mode&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Workaround:None&lt;/B&gt;



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtn26111</guid>
</item>
<item>
<title>8945 SCCP: softkey and hardkey response time is  slow, Fixed CSCtj74474</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtj74474</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
The Phone UI response performance is much worse than RT-Lite&#39;s and also worse than the value required in EDCS-757097.
The Scrolling time and softkey processing time should be less than 100ms.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
&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=CSCtj74474</guid>
</item>
<item>
<title>JPN: CUCM: 7937: XML error occurs on Extension Mobility., Fixed CSCtl03266</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtl03266</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CUCM:JPN:7937: XML error occurs on Extension Mobility.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM8.5.1.10000-26
LI: cm-local-ja_JP-8.5.1.9902-56.cop
7937 F/W: apps37sccp.1-4-3-0
&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=CSCtl03266</guid>
</item>
<item>
<title>phone continues to ring after answered on shared line by other device, Open CSCtx89324</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx89324</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Phone B has 2 Lines out of which one line is shared with Phone D.
phone A calls first line on phone B (extension 3219)
phone C calls second line on phone B( it needs not be 3219 or just any other
shared line) which is a shared line with Phone D.
both the above calls are at same time. Now first phone B answer the first
line and then phone D answers the second call, phone B will still keep on
ringing.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&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=CSCtx89324</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>TVS Client should support same size certificate as CUCM, Open CSCtx55324</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx55324</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

&quot;Host Not Found&quot; is observed on the phone when invoking phone services.

The phone console logs show that the Phone&#39;s TVS Client is unable to authenticate the HTTPS certificate.

Follow this document to collect the phone console logs:
https://supportforums.cisco.com/docs/DOC-14178
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This will occur if the Tomcat cert on the Cisco Unified Communications Manager OS Administration Page is larger than 2048 bytes.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Use one of the following:

1.  Use a self signed certificate, with the following procedure:

A. 
admin:set cert regen tomcat

Proceed with regeneration (yes|no)? yes

Successfully Regenerated Certificate for tomcat
You must restart services related to tomcat for the regenerated certificates to become active

B.  Get a smaller signed certificate using the steps outlined here (https://supportforums.cisco.com/docs/DOC-6119)

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx55324</guid>
</item>
<item>
<title>7937 - Corporate directory search results are incorrect, Open CSCtu29681</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtu29681</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Corporate directory search results are incorrect. Search results always include 320 records in A to Z form irrespective of the search criteria.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

7937 integrated with custom corporate directory.
&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=CSCtu29681</guid>
</item>
<item>
<title>6945 sccp: SW polling time improvement for RTL Clipping issue, Fixed CSCtx78113</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx78113</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

  the delay is from the phone sending the rtp
A (6945 phone)calls B, B(any type of phone),
B picked up and A quickly says 1,2,3,4 ,5,6,7,8,9,10 and B starts to hear 5, and sometimes 6 and on 
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
Still seen in SCCP version 9.2.2 for 6945 IP 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=CSCtx78113</guid>
</item>
<item>
<title>8945 SIP Phone does not play recording tone, Open CSCtx59472</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx59472</link>
<description>Symptom:
  8945 SIP Phone does not play recording tone when the recording Tone is set to enabled under the device Phone page
&lt;br&gt;
Conditions:
none
&lt;br&gt;
Workaround:
none

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx59472</guid>
</item>
<item>
<title>CME phone does not enable speakerphone during paging after a hooklatch, Fixed CSCtw61625</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw61625</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CME IP phones may fail to auto-enable the speakerphone during a page.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
The issue occurs on IP phone firmware 9.2(1) and above.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Either of the following workarounds applies:
a) Run firmware 9.1(1)SR1 or lower.
or
b) Hit any button on the IP phone after using the phone&#39;s handset or toggling the phone&#39;s hook latch.  See &#39;Additional Details&#39; for more information on this workaround.

&lt;B&gt;Additional Details:&lt;/B&gt;
When the hook latch for the phone handset is toggled, the phone enters a bad state where speakerphone won&#39;t illuminate.  Anytime after the hooklatch is used (i.e. the handset is picked up off the cradle), the user needs to hit any button on the IP phone (i.e. keypad digit, settings, NewCall softkey, etc.) to return the phone to a state where speakerphone auto-enables on page.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtw61625</guid>
</item>
<item>
<title>Request for roaming enhancements, Open CSCtt15112</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt15112</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

A 792xG wireless phone, when roaming away from an access point, may
choose to roam to another access point whose RSSI is as low as -99 dBm.

Because communications with an AP whose RSSI is that low are rarely viable,
the phone will likely spend 3 or 4 seconds with no network connectivity, trying
but failing to associate, before it starts scanning for a new AP.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

The phone has tried, but for some reason failed, to connect with
stronger AP candidates.
&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=CSCtt15112</guid>
</item>
<item>
<title>The Digit dialed when an incoming number pops up are ignored, Fixed CSCtx02301</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx02301</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Dialed digit are ignored when  Call Notification Pop-up Window (toast)  appears on the IP Phone screen
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Firmware : 9.2(2)
CP- 6961
&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=CSCtx02301</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>9971 Phones: Dialed numbers are lost/delayed in display when dialed fast, Fixed CSCtq57371</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq57371</link>
<description>Customer is using 9971 phones with 9-1-1-ES2 firmware. 
When the phone is off-hook and the users dial in the numbers, these numbers are displayed after a second or two on the phone and also sometimes few of the digits are lost and not to be seen on the display.. The outgoing calls are not completed when the issue occurs.




</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq57371</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>All Calls shows wrong session bubble for two shared lines in one phone, Fixed CSCtb78789</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb78789</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
	AllCalls shows confusing session bubble for two shared lines in one phone
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

A  (admin) / B (boss) / C  (boss) as an example.

A&#39;s phone has a shared line with both B and C.  So 3 lines total, and then All Calls filter as well.

1) B calls C.  C does not answer (he&#39;s out golfing).
2) A answers the call on her phone.
3) A selects the &#39;All Calls&#39; filter.

At this point the session displayed in the All Calls filter says:

C
on B    (CONNECTED)

At this point we are following the current spec.  An argument could be made that this is backwards for this scenario.  It&#39;s saying that A is looking at a connected call with C on B&#39;s line, when in fact she is on a connected call with B on C&#39;s line.

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



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb78789</guid>
</item>
<item>
<title>9971 Roundtable phone placed call history shows &quot;uknown&quot;,   CSCti46360</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCti46360</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

99x1 phone Call History shows (&quot;unknown&quot;) but only for placed calls history.Go to Applications-&gt;Call History-&gt;All Calls, the called party shows as &quot;unknown&quot; plus the extension.  

If we use 7975 SCCP Phone there is no issue. The name is visible in the placed calls list. 
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;

Called place from a 99xx or 89xx phone to another phone.   Called name is not displayed on the placed calls list on the 99xx or 89xx 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=CSCti46360</guid>
</item>
<item>
<title>Conference Phones Cisco 7937 continually request for DHCP, Fixed CSCtr56885</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtr56885</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Conference Phones Cisco 7937 continually request for DHCP. DHCP 
Logs fill up. resetting the phone clears the issue for some time. The phone continues to work fine while it is sending those cont DHCP requests.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
DHCP Lease time greater than 7 days
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
1) Reset the IP Phone (Will stop the DHCP Flood, but will re-occur again)
2) Reduce the DHCP lease time to a value less than 7 days

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtr56885</guid>
</item>
<item>
<title>DEU-6941: Transfer key displayed in English, Open CSCtx54274</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx54274</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When pressing the Transfer Key in Cisco IP Phones 6941, the display prompts &quot;Enter a number to transfer&quot; in English; while German Locale is installed. All the other softkeys are displayed in German. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Issue has been observed and reproduced in:

CUCM Version: 8.5.1.13900-5
Firmware Version:  cmterm-69xx-sccp.9-2-2-6.cop
Locale Version: cm-locale-de_DE-8.5.1.2100-1.cop
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Not available.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx54274</guid>
</item>
<item>
<title>CUPC 8.x cannot handle AD Contacts that have no userId, Open CSCtq34828</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq34828</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When searching in AD results are not being displayed
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This happens when you have configured AD &#39;contacts&#39;  By default these contacts do not have the following attributes

sAMAccountName,
mail
employeeNumber
UserPrincipalName

so we cannot map those users to a userID in callmanager / CUPS

The only attribute common to both of cucm and AD is telephoneNumber 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Configure the LDAP sync using the telephoneNumber attribute and also configure the same in CUP admin pages ---&gt; Application ---&gt; Cisco Unified Personal Communicator ---&gt; Settings 
under the LDAP setting for the userID



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq34828</guid>
</item>
<item>
<title>6961 freezes after many successive calls to it while a call is on hold, Open CSCtx76428</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx76428</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
After testing the fixes for CSCtw45969 and CSCtw93646, the same symptom was discovered with a different call flow.

If a call is on hold on the 6961 and there are multiple simultaneous calls to the phone over and over, it may freeze and not respond to off-hook, etc.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
n/a
&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=CSCtx76428</guid>
</item>
   
</channel>
</rss>

