<?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, 20 May 2013 09:54:01 EDT</pubDate>
  <lastBuildDate>Mon, 20 May 2013 09:54:01 EDT</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>9951 loses audio on active call when link with pc port is disconnected, Fixed CSCuf93609</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf93609</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When the cable between 9951 and the pc connected to the pc port gets disconnected during an active call there is no audio anymore, the call stays active.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Running firmware version 9.3(2)ES10 or ES12, does not happen with 9.3(2)
&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=CSCuf93609</guid>
</item>
<item>
<title>6900 series phones do not show correct time, Fixed CSCuf66550</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf66550</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
6900 phones are having an issue with showing the correct time.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Issue occurs only with firmware 9.3.3.2 on CME 8.6.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Downgrade to 9.1.1.2

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf66550</guid>
</item>
<item>
<title>894x phones crashing randomly when run Andtek service, Fixed CSCug28861</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug28861</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

894x phones crashing randomly after upgrading their firmware from 9.3.1 to 9.3.2.

Intermittent, sometimes they run for days, sometimes the crash after 5 minutes, 
&lt;br&gt;


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

phone crash or freeze sometime, when customer run Andtek service on phone.
&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=CSCug28861</guid>
</item>
<item>
<title>894X appends DHCP internal domain name to FQDNs when querying DNS, Open CSCug79506</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug79506</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
If 8941 or 8945 phone receives a domain name via DHCP that is not the same as the domain name of the CUCM nodes, and if DNS is enabled on the cluster, then the 8941 or 8945 phones fail to register. The phone appends the internal domain name to the FQDNs for the CUCM nodes whent sending DNS queries.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
DHCP advertises an internal domain name to the phones (e.g. companyinternal.net)
DNS is enabled on the CUCM cluster
The FQDNs for CUCM nodes use a domain name that is not the same as what is advertised by DHCP (e.g. company.com)
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Do not advertise an internal domain name to the 894X phones via DHCP.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug79506</guid>
</item>
<item>
<title>9971 auto dials the Speed Dial and BLF SD as Phantom calls, Fixed CSCuf13779</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf13779</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
9971 Dials the Speed Dials, DN, BLF SD as Phantom Calls
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Side effect of CSCue47224
&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=CSCuf13779</guid>
</item>
<item>
<title>When the ethernet connectivity is lost from the 8961 PC port RTP is lost,   CSCug29185</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug29185</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When the Ethernet connectivity is lost from the 8961 PC port RTP is lost
When you plug out the Ethernet cable from the PC port of the phone, the RTP stream gets disconnected. This happens too, when you shut down the PC connected to the PC port
&lt;br&gt;

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

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug29185</guid>
</item>
<item>
<title>JPN: CIPC: MBCS service names are garbled, Fixed CSCua46584</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCua46584</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
JPN: CIPC: MBCS service names are garbled.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Cisco IP Communicator 8.6.2.0

CUCM: 9.0.1.10000-12
Locale Installer: cm-locale-ja_JP-9.0.1.9902-222.cop.sgn

Windows 7 Professional SP1 (32bit) JPN
Windows XP SP3
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Manually set encoding via the registry:


Location: [HKEY_CURRENT_USER\Software\Cisco Systems, Inc.\Communicator\Device\device.settings.servicenames]

Name: val3
Type: REG_SZ
Value: name of the encoding you want (e.g. UTF-8)

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCua46584</guid>
</item>
<item>
<title>Reset of phone makes the plantronics headset not to work, Fixed CSCuc34084</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuc34084</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Reset/Reboot of phone makes the plantronics headset not to work
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Reset or reboot of the 7962 phone with load 9-2-1-S makes the plantronics headset not to work. Seems like the firmware missing EHS specification.9.3.1 also has same issue. Specially affects when phone locale is not English.Customer faced this issue when they used German po locale.
&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=CSCuc34084</guid>
</item>
<item>
<title>7937 phone unregister and/or drop calls due to missing CDP packets, Fixed CSCud93628</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud93628</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
7937 phones unregister and/or drop active calls.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Running any firmware version including all 1.4(4) versions other than 1.4(4)ES51 or 1.4(4)ES87.

The phone console logs show:
|cdp |5|00|cdp: Missed 2 Switch CDP pkts, Looking for DATA/Access VLAN 
|cfgNe|3|00|Native vlan 4095. Voice vlan 4095. 
|cfgNe|3|00|Vlan changes: Will get another dhcp lease.

The VLAN change causes the phone to change VLANs because it believes CDP packets are missing even when it they are not.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Disable CDP on the switchport the 7937 is connected to and setup the switch port as an access port with the voice VLAN assigned as the access VLAN.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud93628</guid>
</item>
<item>
<title>Onhook dialing does not work when speaker phone is disabled on 89XX/99XX,   CSCue04738</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCue04738</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Onhook dialing does not work on 89XX/99XX phones.  
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Dial a number while the handset is onhook.  Lift the handset.  The phone will not dial the number nor can the Call softkey be pressed because it is disabled.  This only occurs when the speak phone is disabled on the phone and on firmware versions 9.3(1) and 9.3(2).
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Downgrade to firmware 9.2(4) which does not have this problem.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCue04738</guid>
</item>
<item>
<title>IP phone 8961 VID v05 not compatible with VXC 2111 and VXC 2112, Fixed CSCue80035</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCue80035</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Latest hardware release of IP phone 8961, VID v05, is not compatible with VXC 2111 and VXC 2112

The phone shows the message &quot;VXC is now connected&quot; and &quot;VXC has been disconnected&quot; in a loop.  

VXC 2111 and VXC 2112 work fine with 8961 v04.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
VXC client connected to 8961 using POE or with the external power adapter (power cube).
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None.
&lt;br&gt;

&lt;B&gt;Further Information&lt;/B&gt;
The issue was resolved, hardware version in image is not changed but
change 68- number.

Some change details on TAN and PID level:
TANs are version up, e.g. 68-4510-03 -&gt; 68-4510-04
PIDs are revision up, and VID rolls up. E.g. CP-8961-C-A-K9= -D0 V04 -&gt;CP-8961-C-A-K9= -E0 V05
HW version(stored in flash) is not changed.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCue80035</guid>
</item>
<item>
<title>3905 plays incorrect ringbacktone when NETWORK LOCALE is set to AU or UK, Open CSCug61605</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug61605</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

When we place an internal call using a 3905 with Network Locale set to Australia or United Kingdom the ringback tone heard is not right.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
When the network locale is set to Australia or United Kingdom
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use any other network locale than Australia or United Kingdom.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug61605</guid>
</item>
<item>
<title>Only the Default Windows Audio Device option is avail in Audio settings, Terminated CSCue02849</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCue02849</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Both the Audio Tuning Wizard and the IPC Preferences show only the &quot;Default Windows Audio Device&quot; - they do not show any headsets or on-board audio devices, except under the ringer section.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Laptops using IDT Audio device and Windows 7
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None as this is not a CIPC issue.

IDT has provided a fix for the APO issue (All current &quot;Win8 ready&quot; drivers released to both HP and Dell include a workaround for the APO format negotiation issue which prevents CIPC from enumerating additional audio devices in some cases.).

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCue02849</guid>
</item>
<item>
<title>BLF Speeddial Presence Subscription does not work after firmware upgrade, Fixed CSCud80854</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud80854</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

BLF Speed Dial on a 6945 phone does not work after phone firmware upgrade.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This occurs after a phone firmware upgrade for 6945 on SIP Firmware. SIP 9.3(1) to SIP 9.3(1)ES4 firmware versions are affected.

For 6921/41/61 Phone models, refer the defect CSCuc77089.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Reset the phone or use SCCP firmware.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud80854</guid>
</item>
<item>
<title>69xx phones do not play multicast audio during phone calls, Fixed CSCtd87007</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtd87007</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
For 69xx phones, no multicast audio is heard when the phone is on a call.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
69xx phones like 6941,6961,6921. 
&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=CSCtd87007</guid>
</item>
<item>
<title>79XX phones autodial number from directory when going offhook, Fixed CSCuf85411</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf85411</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
79XX phones will auto dial a number from one of the directories.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
Phone is running 9.3(1)ES11
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Reset the phone to fix the auto dial issue when it occurs. No workaround to prevent it from happening again.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf85411</guid>
</item>
<item>
<title>3905 Locale: The issues occur to the Locale of Arabic., Fixed CSCts30499</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCts30499</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
3905 Locale: The issues occur to the Locale of Arabic (United Arab Emirates).
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
No
&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=CSCts30499</guid>
</item>
<item>
<title>Enerywise Issue on 69xx phones, Open CSCug86591</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug86591</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

The switch is configured for Energywise feature to put the phone into sleep (level 2) and wake up (level 10). The only configuration on the CUCM Phone config page is the Energywise Domain &amp; Energywise endpoint security secret for the phone to participate in the Energywise domain configured on the switch. The option &quot;Allow EnergyWise Overrides&quot; on the CUCM Phone Config page needs to be enabled as well. 

The phone should ideally wait for the signal from the switch as the wake up timer is configured on the switch. However, the 69xx phone sends a Fire in time based on CUCM &quot;ON TIME&quot; config to switch even though this option is disabled on the CUCM Phone config page. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

When the sleep and wake up time is configured on the switch Energywise configuration instead of the CUCM Phone config page. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

The wake up issue only occurs when the phone is configured to get into sleep mode (Level 2). If however the phone is sent into shutdown mode (Level 0) the phone wake up at the correct time configured on the switch. Therefore, as a work around we can put the phone into shutdown mode from sleep mode right before the wake-up time, else the phone will wake up only on the time configured on the CUCM Phone config page. i.e

!
interface FastEthernet0/0
energywise level 2 recurrence importance 80 at 02 12 * * *
energywise level 0 recurrence importance 80 at 17 11 * * *
energywise level 10 recurrence importance 80 at 17 12 * * *
!

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug86591</guid>
</item>
<item>
<title>ATA 187 provides its uptime instead of local time to analog phones., Fixed CSCud88926</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud88926</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

ATA 187 showing passing its uptime to analog phones instead of actual time.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

When the phone rings; ATA 187 sends caller ID signal to the analog phone between the first and the second ring (with name, phone number, TIME and date information).

In the current scenario; instead of sending the actual time; ATA 187 is sending its uptime in the signal.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Not applicable

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud88926</guid>
</item>
<item>
<title>8945 Video is unmuted on existing call if incoming 2nd call is CFNA, Open CSCug71056</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug71056</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Video gets unmuted even though &quot;Auto Transmit Video&quot; is set to OFF.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

--SIP Firmware (seen in 9-3-2-12)
--If an 8945 Phone has &quot;Auto Transmit Video&quot; set to OFF, the video will be on mute  but once we get a 2nd call on the same line and it gets CFNA to another extension / voicemail, the video on the phone automatically gets unmuted and the existing party can now see the &quot;caller on 8945 side&quot; .
&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=CSCug71056</guid>
</item>
<item>
<title>Phone does not release the call when going on-hook, Fixed CSCuc71497</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuc71497</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Call is not getting released when going on-hook on the phone
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Phone 7962/42, first seen with 9-3-1-1S
During the active call the phone receives a TCP RST on the established signaling socket
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Press softkey end-call

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuc71497</guid>
</item>
<item>
<title>99xx phones - line status stuck on hold state - phantom hold, Fixed CSCub40585</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCub40585</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
phone line status stuck in hold status after call has already cleared.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
99xx with shared line.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
selecting the line will clear the status.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCub40585</guid>
</item>
<item>
<title>3905 IP phone shows &quot;rejected&quot; on CUCM if we delete and add it back, Open CSCug88894</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug88894</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
3905 IP phone shows &quot;rejected&quot; on CUCM after we delete the phone from the CUCM and add it back or add the IP Phone for the first time. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Happens with already registered IP phones and sometimes on new IP phones. 3905 IP Phone will display as &quot;registering&quot;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Hard reset the IP Phone or factory reset the IP phone.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug88894</guid>
</item>
<item>
<title>Third gen phones (TNP) may reload when receiving crafted packets, Fixed CSCtb03394</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb03394</link>
<description>






&lt;B&gt;Symptom:&lt;/B&gt;
A crafted IP packet may cause third generation IP phones to reload.






&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;
If the crafted packet is received during a call, the call will be lost.














</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtb03394</guid>
</item>
<item>
<title>Xfer call bounces back when picked up @ ~same time as 2nd xfer keypress, Open CSCty35673</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCty35673</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
~~~~~~~~~~~~~~~~~
Occasionally, recipients of a transferred call pick up their ringing phone and hear dead-air. The transferring party finds that the call they think they transferred returns to them.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
~~~~~~~~~~~~~~~~~
SIP phone acting as transferring party (e.g. observed on Cisco 8961 IP Phone)

The recipient of a transferred call answers their phone right before the transferring party presses the second transfer key-press. 
The transferring party is thinking that they were making a blind transfer, but signaling begins for a consultative transfer.
A race condition arises where CUCM starts to set up media between the transferring party and the recipient of a transfer, but then the media immediately needs to be torn down before the initial setup is complete. In the meantime, new media is being set up between the transferred party and the recipient of the transferred call. This overlapping signaling is not processed correctly by both the CUCM and phone.

These symptoms are more likely to be identified as a repeating pattern by receptionists who manually answer and transfer calls.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
~~~~~~~~~~~~~~~~~
None. Education/Modification of user behavior might reduce the likelihood of experiencing this issue - e.g. tell the transferring party that if they do a blind-transfer they do so quickly *and* informing recipients of transferred calls not to pick up immediately.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCty35673</guid>
</item>
<item>
<title>CUCI-Lync msiexec command documentation missing some options, Open CSCug25254</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug25254</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

CUCI-Lync documentation for msiexec command line install does not include all features available.

Reference:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucimoc/8_5/english/installguide/deploying_installation.html#wpxref81070

Specifically, table 5-1 should include the JRE component as an installable feature.
&lt;br&gt;

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

After command line install clients may see a CSF error ?Unable to find a supported Java Runtime Environment?.&quot;

The Java Run-time Environment (JRE) can be included as installed feature as part of the CLI install.
&lt;br&gt;


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

The Java Run-time Environment (JRE) can be included as installed feature as part of the CLI install.  The install syntax will be something like the following...

msiexec /i CiscoUCIntegrationTMforMicrosoftLyncK9.msi /q ADDLOCAL=&quot;CUCIMOC,JRE,Word,Excel,SmartTags,InternetExplorer,Firefox,PowerPoint&quot;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug25254</guid>
</item>
<item>
<title>69xx phones in hunt group are not showing alerting name of hunt pilot, Fixed CSCtn80214</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtn80214</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
69xx phones which are part of a hunt group for which on the hunt pilot an alerting name is configured are not showing this alerting name. 79xx phone do show the alerting name.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
N/A
&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=CSCtn80214</guid>
</item>
<item>
<title>IP Phones - Improve transmit voice call quality when using the speaker, Open CSCug29229</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug29229</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
On conference calls, a user with a cisco ip phone in the speaker mode, has difficulties to interrupt other people.
The other participants on the call will hear the voice of the user in lower volume an choppy.
The issue is worst the higher is the speaker volume.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
Seen on CUCM 8.5 and using 9951 phones. But it should be the same on other phone models, reproduced the same on a 7975.
This is only reproducible if there are at least other 2 participants in the conference call continuously talking previously to the user starting to talk.
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Lower the speaker volume.
This effect is a consequence of the echo cancellation on the phones. This is an enhancement request to see if this behavior could be improved.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug29229</guid>
</item>
<item>
<title>8945 SCCP Predot number is disappeared on Call history when using redial, Fixed CSCuf24528</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf24528</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Originally, if a 8945 phone user places a call to PSTN side(e.g DN 9xxxx), 9 is stripped by route-pattern(pre-dot option 9.xxxx)(when using mgcp VG), however, the user can see all of numbers(including &quot;9&quot;) by fixing code(CSCud08735). 
So the user is able to place a call by selecting the previous number from the call history.
However, if the customer places a call by &quot;Redial&quot; Softkey instead of selecting the previous number from CallHistory, a new number(created by &quot;Redial&quot; Softkey) is displayed with pre-doted number again.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
using &quot;Redial&quot; key
&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=CSCuf24528</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>69xx phon model won&#39;t restrict read access to the netw setting, Fixed CSCug47488</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug47488</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
on 69xx phones and 39x5  models, when disabling or restricting access to the Settings menu, the option to see the Phone Information is still present. If enabled, and you press the Settings button, it shows up &quot;Applications (4 items)&quot;, if restricted, shows &quot;Applications (3 items)&quot; and if disabled, it will display &quot;Applications (2 items)&quot;, but Phone Information is always present, so an attacher (I guess) can get a hold of the Callmanager&#39;s IP  and so forth.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 8.6.x 9.1.x 

I was able to test in the lab as follow:
CUCM 8.6.2.22900-9 with the same firmware customer is 9.2.2 running on the 6905 phones...... same behavior
CUCM 8.6.2.22900-9 with 9.2.2.es3 firmware  running on the 6905 phones  ........Same behavior
CUCM 9.1.1.20000-5 with the same firmware customer is running 9.2.2 on the 6905 phones...... same behavior
CUCM 9.1.1.20000-5 with 9.2.2.es3 firmware  running on the 6905 phones  ........Same behavior

I did test by disabel and restricted Settings Access on the phone.
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
none
&lt;B&gt;More Info:&lt;/B&gt;



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug47488</guid>
</item>
<item>
<title>8945 SIP various network locales make phone unresponsive, Fixed CSCuc52986</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuc52986</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
An 8941 or 8945 SIP Phone will freeze when applying a network locale.  
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This issue has been observed with the Brazilliand and Netherlands locale on phone firmware version 9.3(1).  Other locales may be affected.
&lt;br&gt;

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

Use an earlier version version of the phone firmware such as 9.2(3)

OR

Use English network Locale and reset the power on the phone.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuc52986</guid>
</item>
<item>
<title>sender phone number should not contain special characters, Open CSCug61971</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug61971</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
For some call flow, customer has special characters in the Sender phone number which is sent along to the Voicemail.
Now when the user is trying to listen to the VVM, he gets the below messages.

Unable to play visual voicemail files for voicemail left from calls through sip trunk/ICT, Notification tab shows following:
---
Conversation History Error. MessagePlayer Message Buffering failed (generic). [1754]
VoiceMail Error. MessagePlayer Message Buffering failed (generic). [1754]
--
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCILync ver 8.6(2.20758) CSF ver 8.5(6)-4.5.84
Call flow:
Phone 1 -&gt; CUCM 1 -&gt; ICT -&gt; CUCM 2 -&gt; Phone 2 left a vm. 
Phone 1 -&gt; SIP trunk -&gt; CUCM -&gt; Phone left a vm
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
We need to have Documentation that &quot;Sender phone number should not contain special characters&quot; Otherwise customer will run into CSCud43751.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug61971</guid>
</item>
<item>
<title>correct QED for CIPC device to show security by default is not supported, Fixed CSCtz35916</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtz35916</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
1 - CUCM 8.6 Unified Reporting Tool shows the Cisco IP Communicator device supports security by default feature.  This is not accurate.
2 - Phone services that use https (for example, extension mobility) does not work.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
1 - Run the Unified Reporting Tool, Unified CM Phone Feature List report on CUCM 8.6 
2 - CUCM 8.6 and CIPC 8.6
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
None for CUCM 8.6.  Customers will need to upgrade to CUCM 9.x or higher.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtz35916</guid>
</item>
<item>
<title>Switching from speaker to handset doesn&#39;t work on 6961, Fixed CSCtx96913</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx96913</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Occasionally switching from speaker to handset by going off-hook during an active call will not switch the audio to handset mode properly.  In this case the audio remains active through the speaker.
&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=CSCtx96913</guid>
</item>
<item>
<title>Cannot make second call on 6945 when first call is on hold, Terminated CSCub96236</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCub96236</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

6945 Phones cannot make second call by holding the first one when registered with CME on 9.3.1 firmware and all lower version. 
&lt;br&gt;

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

Phone displays the below message when the second call is attempted after holding the active first call. 

The message &quot;Unable to create a call; the maximum number of calls for this line has been reached...&quot; popped up

operation are
 1. First call established
 2. Hold
 3. cannot make a New Second call
&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=CSCub96236</guid>
</item>
<item>
<title>69xx adds invalid &lt;xml&gt; tag to HTTP response parse error on app, Fixed CSCuf48279</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf48279</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Informacast basic broadcast to exclusively 6921 phones doesn&#39;t work and it gives the message: &quot;We are sorry, no devices could be activated. Your broadcast will not be completed.&quot;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Customer has a Singlewire integration for paging which works by sending an HTTP Request to the phone to join a multicast stream. The integration seems to work with the phone firmware 9.3(1) on the 69xx. However, after upgrading to 9.3(3) the phones are adding an additional tag to the HTTP POST. The result is that the Singlewire application is unable to parse the phone&#39;s response, and when the page ends the Singlewire application does not instruct the phone to leave the multicast stream.

sccp &amp; sip all have this issue. this is reported by customer on 6945 phone, CSCue94926.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Upgrade phone to 9.3.3ES2 or later that includes fix.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf48279</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>8945 SCCP Predot number(of route pattern) is disappeared on Call history, Fixed CSCud08735</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud08735</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When 8945 phone user places a call to PSTN side(e.g DN 9xxxx), 9 is stripped by route-pattern(pre-dot option 9.xxxx)(when using mgcp VG)
In this case, the user just can see pre-dot number removed number only on IPPhone call history info(e.g. xxxx) even the phone user actually hit 9xxxx when he tried to place a call.

So the phone user should hit a whole number again(9xxxx) - not able to use call history info for redial.

It is reproducible and always happens.	
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
- CUCM version: 8.6.2.20000-2
- Firmware: 9.3.2 / 8945 phone / SCCP
Actually, this issue didnt happen on 9.2.3.5, customer experiences this issue on 9.3.1ES3 and 9.3.2 version.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Downgrade firmware version(9.2.3.x)

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud08735</guid>
</item>
<item>
<title>IP Phone SSL VPN Support For Non Default Port Numbers, Open CSCtz42052</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtz42052</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When connecting an IP phone to an SSL VPN the phone fails to connect with the message: &quot;Username and Password Failed&quot;.

The phone console logs display the following.

1388: NOT 21:42:07.005090 VPNC: do_login: sending (HTTPS) login request...
1389: NOT 21:42:07.006790 VPNC: do_login: waiting for login response
1390: NOT 21:42:07.011024 VPNC: do_login: got login response
1391: NOT 21:42:07.011906 VPNC: process_login: HTTP/1.1 200 OK
1392: NOT 21:42:07.012590 VPNC: process_login: login code: 200 (ok)
1393: ERR 21:42:07.013240 VPNC: process_login: login failed, &#39;webvpn=&#39; not found in cookie
1394: ERR 21:42:07.013925 VPNC: do_login: process_login failure
1395: WRN 21:42:07.015437 VPNC: ssl_state_cb: TLSv1: write: alert: warning:close notify
1396: NOT 21:42:07.017413 VPNC: vpn_stop: de-activating vpn
1397: NOT 21:42:07.018356 VPNC: vpn_set_auto: auto -&gt; auto
1398: NOT 21:42:07.018946 VPNC: vpn_set_active: activated -&gt; de-activated
1399: NOT 21:42:07.019565 VPNC: set_login_state: LOGIN: 1 (TRYING) --&gt; 3 (FAILED)
1400: NOT 21:42:07.020234 VPNC: set_login_state: VPNC : 1 (LoggingIn) --&gt; 3 (LoginFailed)
1401: NOT 21:42:07.020883 VPNC: vpnc_send_notify: notify type: 1 [LoginFailed]
1402: NOT 21:42:07.021552 VPNC: vpnc_send_notify: notify code: 11 [LoginFailure]
1403: NOT 21:42:07.022167 VPNC: vpnc_send_notify: notify desc: [no valid session cookie]
1404: NOT 21:42:07.022779 VPNC: vpnc_send_notify: sending signal 28 w/ value 13 to pid 13
1405: ERR 21:42:07.023444 VPNC: protocol_handler: login failed
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
The webvpn port has been changed from the default port of 443.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Use the default port number for webvpn of 443 to allow the phone to connect.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtz42052</guid>
</item>
<item>
<title>ATA 187 unregister from CUCM for branch offices, Fixed CSCtx91035</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx91035</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
ATA 187 unregisters from branch office in customer&#39;s setup
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
It occurs on ATA 923 load.
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Need to power cycle the device.


</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx91035</guid>
</item>
<item>
<title>Session key ignored after call ended on 9951 and 9971 phones, Fixed CSCuc42087</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuc42087</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

After a call is ended, the session key does not cause the phone to go off hook.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

This occurs if the session key is pressed directly after the call is ended.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Wait an extra 2 seconds before pressing the session key after the call is ended.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuc42087</guid>
</item>
<item>
<title>CIPC Hang when recording enabled, Fixed CSCuf08772</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf08772</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CIPC will hang, forcing the end-user to terminate the program and re-open it
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CIPC with recording enabled
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
disable recording

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf08772</guid>
</item>
<item>
<title>6921 &quot;Missed Call Log&quot; History empty when running SCCP9-3-1-3, Fixed CSCue50467</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCue50467</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

6921 &quot;Missed Call Log&quot; History empty when running SCCP9-3-1-3
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

No particular trigger. Occurs always.
&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=CSCue50467</guid>
</item>
<item>
<title>From outlook meeting unable to call meeting organizer using ribbon, Open CSCug84763</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug84763</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Click to call not always showing call options for organizer in ribbon 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Selecting a meeting in outlook, looking at the call options in the ribbon
&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=CSCug84763</guid>
</item>
<item>
<title>6945 shows packet loss when VAD enabled, Open CSCug81944</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug81944</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

6945 phones reports packet loss while using comfort noise with VAD enabled though there is no actual packet loss.

Phones generate comfort noise when VAD is enabled and silence detected on a call. During the time when these comfort noise packets are used, IP phone expects packets and hence reports packet loss to the CUCM when there is no packet loss as such in the call.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

6945 phones running firmware version SCCP 9-3-3-2-ES1 with VAD enabled.
&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=CSCug81944</guid>
</item>
<item>
<title>The 3rd phone with shared line can&#39;t cBarge the call succeed., Fixed CSCud42579</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud42579</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Steps:
1. Register 4 phones to cucm;
2. Configure line2 as shared line of phone2,phone3 and phone4(DN:321011);
3. Configure privacy to  &quot;off&quot; of   phone2,phone3 and phone4;
4. Phone1 makes a call to shared line(321010 -&gt; 321011);
5. Phone2 line2 answer the call;
6. Phone3 line2 cBarge the call by pressing session key;
7. Phone4 line2 try to cBarge the call by pressing session key.
Result:
Phone4 line2 has no response after pressing session key.
Expected result:
Phone4 can cBarge the call succeed.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
The 3rd phone with shared line can&#39;t cBarge the call succeed.(Phone load: 9-3-2-2 works)
&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=CSCud42579</guid>
</item>
<item>
<title>JPN+KOR: 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>CUCILync - Disabled menu to remove people from Conf call showing, Fixed CSCtz63692</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtz63692</link>
<description>&lt;B&gt;Symptom: CUCILYNC unable to remove participant from a conferenct call&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Conditions: Option is greayed out&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Workaround:Participant needs to hang up call themselves&lt;/B&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtz63692</guid>
</item>
<item>
<title>Request to support 4096 size key certificates, Open CSCtj44859</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtj44859</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
7925 / 7921 not working with 4096 bit keys
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CA or cert uploaded on the phone has a 4096 bit key
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
use 2048 bit key



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtj44859</guid>
</item>
<item>
<title>8945 SCCP firmware reporting incorrect jitter during video calls, Fixed CSCug69210</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug69210</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Jitter values are inaccurate on an 8945 when a video call is taking place. Example: Actual jitter: about 1, Reported: 100. 
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
SCCP firmware 9.3(2)
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Take a pcap from the phone PC port (using Span to PC Port) or a SPAN from the switch and run that through a voip analyzer.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug69210</guid>
</item>
<item>
<title>7937 Intermittent Choppy Voice, Fixed CSCth58770</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCth58770</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Intermittent Choppy Voice on CP-7937 phones.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
This is observed when the phones have a data vlan assigned together with a voice vlan. The broadcast packets in the data vlan are causing the problem.
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Remove the data vlan from the phone. Allow only the voice vlan on the switch port.


As outline in the 1.4.4 Release note, the 7937 only carries voice traffic, only need single vlan.
http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7937g/firmware/englis
h/1_4_4/release-notes/7937rn144.html#wp108400

Support for Voice and Data VLANs
The Cisco Unified IP Conference Station 7937G uses a single 10/100BaseTx Ethernet LAN connection to communicate with the switch port. Because this connection carries only voice traffic, the switch port should belong to a single VLAN.  This means that you must configure a voice VLAN for the phone to function properly. You cannot configure voice and data VLANs on the same switch port.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCth58770</guid>
</item>
<item>
<title>6945 phones are displaying time one hour off regardless of timezone., Open CSCug57121</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug57121</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
6945 phones running an ES load of SCCP firmware are showing the time one hour behind regardless of the timezone they are set to use. 
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 8.6.2.22043-2 and ES load SCCP6945.9-3-3-2-ES1 
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Use the timezone option (GMT-X:##) &lt;normal timezone&gt;X&lt;dst timezone&gt;  
Example: (GMT-8:00) PST8PDT and reset the phones using that Date/Time group.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug57121</guid>
</item>
<item>
<title>Unable to uninstall CUPC 8.5.5 from command line, Fixed CSCub06302</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCub06302</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;


Unable to uninstall CUPC from CLI. using the following:

When I try to do CiscoUnifiedPersonalCommunicatorK9.exe /S /v&quot;/uninstall /qn&quot;,

I get the following error:

&quot;This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid windows installer patch package.&quot;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

none
&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=CSCub06302</guid>
</item>
<item>
<title>79xx phones intermittently play load comfort noise, Terminated CSCug50605</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug50605</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When 79xx phones call Unity Connection in secure SIP integration, the comfort noise packets sent by Unity Connection are intermittently decoded incorrectly which results in bad quality audio for a user.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
CUCM 8.6.2
CUC 8.6.2ES44.22900-44
79xx phones with  SCCP41.9-2-3S or SCCP41.9-3-1SR1-1S firmware. 
Possible other firmware as well.
Secure SIP integration between CUCM and CUC
Secure RTP between SCCP phones and CUC
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Enforce CUC to use only the G.729 codec.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug50605</guid>
</item>
<item>
<title>Directed Call Park BLF button doesn&#39;t work after Powering on or failover, Open CSCug84234</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug84234</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
After powering on the CP-6961 or failing over to the Secondary CUCM, calls are not parked even when pressing the Directed Call Park BLF button.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
The button works after resetting the phone from the CUCM Admin GUI or pressing &quot;**#**&quot; on the IP Phone.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug84234</guid>
</item>
<item>
<title>ATA187 units requires a reload to regain connectivity to CUCM, Fixed CSCuc82525</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuc82525</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
ATA187 unregisters randomly and shows status &quot;Rejected&quot; con CUCM configuration.
This is seen to happen after the ATA has been working normally for a long time. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
ATA 187 running firmware 9.2.2 registered to Call manager for a long time.
Only port 1 is configured. Port 2 is unused.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Configure a dummy DN on the 2nd port of the ATA, so it stops
downloading CNF file from TFTP server.





</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuc82525</guid>
</item>
<item>
<title>Enhance echo cancellation capabilities on 7937, Open CSCud78163</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud78163</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Enhancement Request to improve the echo cancellation behavior on 7937 when installed at conference rooms with high acoustics.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Conference rooms with large glass walls would cause high acoustics.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Covering the glass walls with blinds and usage of dampeners would reduce the acoustics.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud78163</guid>
</item>
<item>
<title>Incorrect UDP port binding due to missing RTCP hold port, Fixed CSCud76361</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud76361</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
6921 IP Phone crashes during use, especially during transfers
This happens intermittently/infrequently, perhaps once or twice per day with heavy use of the phone
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
6921 SIP Phone
Heavy use of Transfer
&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=CSCud76361</guid>
</item>
<item>
<title>Communicator-&#39;No Compatible Sound Devices&#39; when diff wavein waveout name, Fixed CSCsa65866</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa65866</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

IP Communicator Audio Tuning Wizard shows nothing in the dropdown selection boxes, and when
Communicator is launched, it gives a messages stating:

&quot;There are no compatible sound devices installed on this computer.&quot;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Attempting to install/use IP Communicator on a system that has different names for the Playback
(wave out) and Recording (wave in) devices.

In this particular system, opening the Sound and Multimedia control panel, and clicking the Audio tab, 
we saw the following:

Sound Playback
Preferred device:
Realtek HD Audio rear output

Sound Recording
Preferred device:
Realtek HD Front Green Jack

As these names are different, IP Communicator will not recognize these devices.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Use a USB headset, which will be recognized by IP Communicator.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa65866</guid>
</item>
<item>
<title>EAP-TLS on phone fails leading to phone freeze with Load 9-3-1SR2, Fixed CSCug63713</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug63713</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
79xx phones running EAP-TLS freeze randomly.Which means the phone doesn&#39;t response to any key-input. Display is frozen. ICMP (ping) is working, but dot1x (EAP-TLS) and http are not responding. At this point it is also unregistered in CUCM
&lt;br&gt;Workaround is to hardly reset the phone by plugging off the network cable (Power over Ethernet), to bring the phone up.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
79xx Phone running EAP-TLS, with load 9-3-1-SR2

&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=CSCug63713</guid>
</item>
   
</channel>
</rss>
