News aggregator

Symptom: CUE GUI help numbering style is wrong. it should be increasing. Now Help file shows as below Section Title Explanation Note 1. XXXXXX 1. XXXXXX 1. XXXXXX But it should be Section Title Explanation Note 1. XXXXXX 2. XXXXXX 3. XXXXXX
Conditions: With IE8 as browser
Workaround: None

Symptom: Release Notes for Cisco Unity Express 8.0 introduces a new feature "Stored Caller Name". But this information is not stated in "Table 1 Cisco Unity Express Features by Version" in "Cisco Unity Express VoiceMail and Auto Attendant CLI Administrator Guide for 3.0 and Later Versions".

Symptom: Administrator is not able to enable message notification devices for any user.
Conditions: This is seen in CUE 7.1.x.
Workaround: No workaround.

Symptom: Notifications are not generated for Once scheduled backups
Conditions: mycue# show schedule detail job tetest1 Job Name tetest1 Application backup Description Schedule Once on 06/08/2010 at 03:00 Last Run NEVER Next Run Jun 8, 2010 03:00 Active from Jun 7, 2010 until INDEFINITE Disabled Notifications voicemail: isecme_us(always)
Workaround: None

Symptom: Reports -> Real-Time Reports shows a blank white or gray page.
Conditions: It works fine with Sun JRE version 1.6.0_03 or below and does not work with Sun JRE 1.6.0_04 or above.
Workaround: - Install Sun JRE 1.6.0_03 or lower version. - Install CUE 7.0 ... (when it becomes available).

Symptom: While recording the personnel greeting, it cuts off after 10 seconds.Then once the call is hung up re-tried calling the voicemail once again to re record personal greeting, while re recording the greeting, this time it allowed the greeting to be recorded for longer than 10 seconds.
Conditions: Only when all these conditions happen: - This happens only if spoken name is recorded first. - Only happens 1st time on the call.
Workaround: Either call back in to record the personal greeting or record the spoken name after the personal greeting.

Symptom: A redirect from a Cisco Unity Express Voicemail or AutoAttendant CTI Route Point may fail.
Conditions: The problem only affects Cisco Unity Express integrations with Cisco CallManager. A customer may have a gateway, phone, or trunk configured with a calling search space which includes the partition of the CTI Route Point but not the partition of the CTI Ports. Even though the calling search space assigned to the CTI Route point includes the parition of the CTI Ports, CallManager will block/deny the call by default because CallManager's default behavior for processing JTAPI redirects is to use the original calling party's calling search space rather than the redirecting party's calling search space. JTAPI client applications have the option to tell CallManager to use the calling seach space of the redirecting party. Cisco Unity Express needs to implent a new setting which allows an administrator to select weather CUE should use the original calling party's calling search space or the redirecting party's calling search space when redirecting calls from the AA or VM CTI Route Point to a CTI Port.
Workaround: Ensure that the original calling device has a calling search space which includes the partition of the CTI Route Points, CTI Ports, and any other directory number or pattern to which the CTI application may redirect a call.

Symptom: During voice-mail recording, initial portion of the message (initial 8-10 seconds) doesn't get recorded. Sometimes the complete message doesn't get recorded.
Conditions: Happens randomly with CUE 8.0.1.
Workaround: None

Symptom: Reactive debugging in the CUE Editor does not work with UC500. The error message we get is "RMI OP can not accept calls made in RMI Protocol 1.1 for class com.cisco.wfframework.engine.rmi.RemoteWorkflowEngineImpl."
Conditions: Use the reactive debugging feature in UC500
Workaround: None
Further Problem Description:

Symptom: On CME 4.3/7.0, when issuing a 'reset' for a 7960 with a 7914 sidecar, the 7914 will fail to re-register to CME and will stay with all buttons red.
Conditions: This is observed on CME 4.3 and 7.0 for the 7960 with the 7914.
Workaround: Downgrade to 12.4(15)T7 (CME 4.1) where the issue is not seen. Another workaround is to rebuild the CNF files with the below commands. This will allow for the device to be reset a single time and register properly. Successive resets will fail until the CNF files are rebuilt again. CME#configure terminal Enter configuration commands, one per line. End with CNTL/Z. CME(config)#telephony-service CME(config-telephony)#no create cnf-files CNF files deleted CME(config-telephony)#create cnf-files Creating CNF files

Symptom: Bulk speed dial functionality from a SCCP phone registered to Cisco Unified Communications Manager Express may not work.
Conditions: This problem was observed when the user enters the digits first and then presses the dial button from a 7942 phone.
Workaround: Press the "NewCall" button and then dial the digits.

Symptoms: A Cisco router may reload due to a bus error and show the following messages: %ALIGN-1-FATAL: Illegal access to a low address 10:09:03 PDT Tue Sep 1 2009 addr=0x0, pc=0x4159DB10z , ra=0xFFFFB4DFz , sp=0x4F059900 %ALIGN-1-FATAL: Illegal access to a low address 10:09:03 PDT Tue Sep 1 2009 addr=0x0, pc=0x4159DB10z , ra=0xFFFFB4DFz , sp=0x4F059900 TLB (store) exception, CPU signal 10, PC = 0x415A2630
Conditions: The symptom is observed on a Cisco 2851 router that is running Cisco IOS Release 12.4(24)T1.
Workaround: There is no workaround.

Symptom: When adding several (more than 10) DNs to a 7916 sidecar registered to CME, the ephone will unregister
Conditions:
Workaround: n/a

Symptom: ======== Consider an ephone which is registered to Cisco Unified Communications Manager Express (CUCME) and which has Watch lines configured on some of its buttons. The output of the show ephone registered EXEC command may look like: ephone-7[6] Mac:68EF.BD28.B81E TCP socket:[4] activeLine:0 whisperLine:0 REGISTERED in SCCP ver 8/8 max_streams=1 SPCP ver 1/1 mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:14 IP:10.1.1.12 * 4423 CP-525G keepalive 2 max_line 5 available_line 5 button 1: cw:1 ccw:(0 0) dn 18 number 5066 CH1 IDLE CH2 IDLE button 2: cw:1 ccw:(0 0) dn 19 number 5067 CH1 IDLE CH2 IDLE watch(BLF on phone 8) shared with monitor-ring button 3: cw:1 ccw:(0 0) dn 20 number 5068 CH1 IDLE CH2 IDLE watch(BLF on phone 9) shared with monitor-ring Preferred Codec: g711ulaw Lpcor Type: none Username: MaxHeadroom Password: 1234 The "watch(BLF on phone N) shared with monitor-ring" statement shows me that the Watch line is provisioned properly and is monitoring the primary DN on phone N. Now consider if the customer uses Cisco Configuration Assistant (CCA) to add Watch lines to any other ephone, or to modify the Watch lines on the same ephone. After the "Apply" button in CCA is pressed the new ephone configuration is pushed by CCA to the CUCME voice router. Once the ephones re-register to CUCME the following is observed in show ephone register: ephone-7[6] Mac:68EF.BD28.B81E TCP socket:[4] activeLine:0 whisperLine:0 REGISTERED in SCCP ver 8/8 max_streams=1 SPCP ver 1/1 mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:1 caps:14 IP:10.1.1.12 * 4770 CP-525G keepalive 3 max_line 5 available_line 5 button 1: cw:1 ccw:(0 0) dn 18 number 5066 CH1 cc(03) IDLE CH2 cc(03) IDLE button 2: cw:1 ccw:(0 0) dn 19 number 5067 CH1 cc(03) IDLE CH2 cc(03) IDLE watch(BLF on phone -1) shared with monitor-ring button 3: cw:1 ccw:(0 0) dn 20 number 5068 CH1 cc(03) IDLE CH2 cc(03) IDLE watch(BLF on phone -1) shared with monitor-ring Preferred Codec: g711ulaw Lpcor Type: none Username: MaxHeadroom Password: 1234 The "watch(BLF on phone -1) shared with monitor-ring" indicates to me that the Watch line is now mapped incorrectly to some nonsense phone, and the button on that particular ephone is now permanently lit up.
Conditions: =========== This behaviour may be observed on a UC500 Voice Router installed with any release of IOS from the 15.0(1)XA family or any IOS train which supports the UC500 platform family. Cisco Configuration Assistant (CCA) is used to administer the UC500, and the user makes the attempt to configure a Watch line on an ephone registered to CUCME.
Workaround: =========== (1) The Watch line mapping issue will not persist after a reload of the CUCME Voice Router, in this case a UC500. It will be necessary to reload the Voice Router after each change to the ephones when CCA is used. (2) Configure all the ephone modifications using the IOS configuration CLI.

Symptoms: No-way audio is experienced in a hardware conference. Entering the sh voip rtp conn command will display the remote IP address as "0.0.0.0" instead of displaying the CME's IP address.
Conditions: When HW conferencing is configured, this symptom is not observed, but it is observed when the router reloads.
Workaround: Save everything under "telephony-service" (all the ephone-dns and ephones) in a notepad file and delete the configuration from the router (including telephony-service). Reload the device and paste in the saved configuration. Reloading the router again will cause the symptom to occur again.

Symptom: Intermittently IP phone agents may be unable to complete a transfer to another IP phone registered to the same CME if the call tried multiple times to reach the same agent before the agent answered. The agent's phone will report "Unable to transfer" after attempting to transfer.
Conditions: This is seen specifically on CME + UCCX integrations.
Workaround: None.

Symptom: 69xx phones display toast message "From : XXXX" when it receives an incoming call for 6 seconds and then it displays the caller id of the person.
Conditions: Observed for 8.5.3 and 8.5.4 phone firmware
Workaround: Not seen for phone firmware : 8.5.1.66.22

Symptom: A call is placed on hold from IP phone. If the user resumes the call by lifting the handset, THEN pressing the line button, the call will disconnect within 60 seconds. The precise time that it takes for the call to disconnect may vary (5-60 seconds) -Call comes in via FXO port, -User answers by lifting handset -User press 'hold' button and place handset onhook -User lifts handset THEN press the line button -Call drops after a few seconds.
Conditions: CME versions 7 and 7.1 IOS version 12.4(20)T and 12.4(24.6)T9 7960 phone load 8.0(5.0) DEBUG: Jun 2 17:05:27.160: Force ONHOOK Clean up phone 14 DN 19 chan 1(119) in state CONNECTED Jun 2 17:05:27.160: ephone-14[13/11]:UpdateCallState DN 19 chan 1 state 10 calleddn -1 chan 1 Jun 2 17:05:27.160: ephone-14[13/11]:Binding ephone-14 to DN 19 chan 1 s2s:0 Jun 2 17:05:27.160: ephone-14[13/11][SEP002155D49E80]:Set FAC enabled (0) and dial mode (4) Jun 2 17:05:27.160: DN 19 chan 1 End Voice_Mode Jun 2 17:05:27.160: SkinnyGetCallState for DN 19 chan 2 IDLE Jun 2 17:05:27.160: called DN -1 chan 1, calling DN -1 chan 1 phone -1 s2s:0 Jun 2 17:05:27.160: ephone-14[13/11]:CloseReceive Jun 2 17:05:27.160: ephone-14[13/11][SEP002155D49E80]:SkinnyStopMedia: Multimedia not active Jun 2 17:05:27.160: ephone-14[13/11]:StopMedia Jun 2 17:05:27.160: ephone-14[13/11]:SpeakerPhoneOnHook Jun 2 17:05:27.160: ephone-14[13/11][SEP002155D49E80]:Clean up activeline 1 Jun 2 17:05:27.160: ephone-14[13/11][SEP002155D49E80]:UpdateCallState unbind phone from DN 19 Jun 2 17:05:27.160: ephone-14[13/11][SEP002155D49E80]:CallPrompt line 0 ref 0: APAC Jun 2 17:05:27.160: ephone-14[13/11][SEP002155D49E80]:SkinnyCheckPendingCallBackPhone scan 6 lines Jun 2 17:05:27.160: SkinnySetCallInfoName calling dn -1 chan 1 dn 19 chan 1,calling [] called [] Jun 2 17:05:27.160: SetCallInfo DN 19 chan 1 is not skinny-to-skinny Jun 2 17:05:27.160: SkinnyStopDnRecallTimer: dn 19 chan 1 Jun 2 17:05:27.160: Skinny Call State change for DN 19 chan 1 CALL_END from CONNECTED pstn---fxo--cme---sccp--ip phone
Workaround: If the call is resumed by pressing the line button or resume before lifting handset, the call will not disconnect.

Symptom: 7921 with 1.1.3 firmware doesn't light the MWI (Message Waiting Indicator) after a power cycle of the phone when there is a voicemail message.
Conditions:
Workaround: none.

Symptom: 1) An auto-registered phone may be allocated an ephone-tag that was manually configured with a mac-address : Example : An auto-registered phone with mac-address 2222.2222.2222 is assigned an ephone tag 126 that is associated with 1111.1111.1111. CME#show run | begin ephone 126 ephone 126 video mac-address 1111.1111.1111 type 7942 button 1:126 ! CME#show ephone registered | begin ephone-126 ephone-126[125] Mac:2222.2222.2222 TCP socket:[3] activeLine:0 whisperLine:0 REGISTERED in SCCP ver 15/12 max_streams=5 mediaActive:0 whisper_mediaActive:0 startMedia:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:1 caps:10 IP:10.2.2.2 1489 CIPC keepalive 15 max_line 8 available_line 8 Preferred Codec: g711ulaw 2) When the "Extension Assigner" feature is used, phones may register without the correct dn line appearances or no lines at all.
Conditions: Auto registration is enabled
Workaround: Disable Auto registration.