News aggregator

Symptom: The users are not prompted to change the password when log in to the voice mail.
Conditions: If the minimum length of PIN has been increased.
Workaround: Execute the command "username generate pin empty" to initialize each user's account.

Problem Description: On H323 slow start calls into CME, with SIP to CUE, calls may fail to connect, and will disconnect with timer expiry (value 102), due to CUE not responding to a SIP REINVITE. This is a race-condition, so the issue being observed will be intermittent in nature. Additional Information: This issue is a result of CUE dropping the RE-Invite when it is sent to CUE by CME soon after the ACK is sent to CUE. Resolution: This issue is fixed on CUE 3.1.1.

Symptom: When an internal IP-Phone A calls the IVR on CUE and the IVR does Semi attendant transfers the call to an IP-Phone B configured with a CFNA to Voicemail system, the IP-Phone A doesn't hear nothing. it seems that cue is sending the refer for transfer to VM, and cme is releasing the call.
Conditions: CUE 7.0.3
Workaround: none

Problem Description: ISM CUE module is in a reboot loop after connecting to CCM 7.1.3. Symptom: Module reboots with the following error: Signature Verified Errors for telephony_infrastructure_manifest: Checksum mismatch on : /usr/wfavvid/jtapi.jar Application level programs verification FAILED! rebooting ...
Workaround: none

None Basic Description No e-mails notifications are received from Cisco Unity Express. Reload of CUE starts sending and receiving new mails however old messages get stuck in the queue.
Workaround One workaround is to disable message notification on a system wide basis and enable it again. If this does not work, take a backup of both data and config and restore it back right away. Reloading clears the queue as the queues do not get backed up.

Symptom: CME 7.0 Unable to do Blind Transfer to any contacts using Phonebook/Local Directory contacts.
Conditions: Steps to reproduce: 1. Receive/Place a call 2. Call is answered 3. Options > Trnsfer > Phone displays Transfer 4. Press Ph Book > Choose the number > Press Dial. 5. Phone displays "Handle current call" and then dials the number selected. 6. After 3-4 secs, phone Display - "AutoDial Cancelled!". 7. And then few sec more the call goes on hold.
Workaround: Use Full consult Or Dial the number manually not using directory

Symptoms: ========= Cisco Unified CallManager Express (CUCME) Bulk Speed Dials configured with 1-second pauses via the comma special character do not actually honor the pause request. Consider for example the Bulk Speed Dial with tag index 1: 1,"912345678901,,,,,78901,,,,67890123",Cisco Systems,append When this Speed Dial is called up and terminated to an analog FXO voice-port (say), the digits which are played out to the PSTN/PBX are: "91234567890178901" and this is observed with the following characteristics: (1) There actually doesn't appear to be a 1-second pause between digits. The time-delta between digits played out the analog FXO voice-port normally is about 200ms, and remains so even though the 1-second comma characters are present. All the digits are back-to-back. (2) The commas are considered as individual digits in the to-be-dialed-string, and we only seem to buffer up to 24 such digits. In the example above the "67890123" digits are never played because they are beyond the 24-digit boundary.
Conditions: =========== This behaviour will be observed on all CUCME installations from version 3.2.4 onwards where the Bulk Speed Dial feature has been configured, and the to-be-dialed-string includes pauses and has in excess of 24 digits.
Workaround: =========== It will be necessary to manually dial the digits and bypass the Speed Dial. Update (April 04, 2008): ======================== Upon further investigation of the functionality of the Bulk Speed Dial feature it has been found that the feature is working as designed. The following summarizes the findings: (A) Current SCCP specification is for a 24-digit boundary, but the bulk speed- dial feature can buffer up to 48-digits. When the CSV file defining the Bulk Speed Dials is processed there is no check and warning message generated which lets users know that we will not dial more than 24-digits at a time. For improved serviceability it is highly desirable that a warning message be provided indicating the restriction. (B) The field showing the digits-to-be-dialed string in "show telephony-service bulk-speed-dial" is currently limited to 20 characters even though from (A) we can play up to 24 digits. The field display length should be increased to show the proper number of digits which the user can expect to have played out when the bulk speed-dial is accessed. (C) If the destination for the digits-to-be-dialed string is to be a POTS dial-peer with a variable-length match criteria `T', then if the pause period between sets of digits in the string is longer than the interdigit timeout then it is possible that after the call is connected we may successfully play out the remaining (delayed) digits for further call routing. In general however, the interdigit timeout is probably longer than what is needed to be able to get sufficient total pause time, send the digits we wish, and still be able to stay within the 24-digit SCCP limit. The available documentation describing the Bulk Speed Dial feature will be updated to include a discussion of these caveats (A) through (C).

Symptom: A CME router may unexpectedly reload due to bus error when a UCCX unregisters from the CME.
Conditions: Nothing beyond the UCCX unregistering from the CME is known at this time
Workaround: None known

Symptom: user login to Extension Mobility EM on IP phone. -enters username and password. -hits submit softkey -phone shows loggin in .. updating locale.... -phone display screen stays and gets stuck there and it does not shows new profile and DN on the phone, untill user press the exit softkey 3 times. - same behaviour is noticed on EM logout. which again requires 3 times exit softkey to press.
Conditions: CME recently upgraded from 4.2 to 7.0 login to Extension mobility on IP phone.
Workaround: None
Further Problem Description: Issue wasn't noticed in CME 4.3 . but after upgrade to 7 ,consistently shows on almost all types of phones causes annoying behaviour.

Symptom: cme on c3825-advipservicesk9-mz.124-24.T1.bin one ephone UNREGISTER_ABNORMAL, the other ephone with shared DN will stop sending BLF prsense subscription. for example ephone 34 button 1:5 2:4 ephone 61 blf-speed-dial 1 ... button 1:5 2:4 when ephone 34 unregister, ephone 61 stop sending presence subscription
Conditions:
Workaround:
Further Problem Description:

Below is the max ephone numbers per platform as the results of this commit. 1. 2811 : CME 42 / SRST 42 2. 2821 : CME 58 / SRST 58 3. 2851 : CME 110 / SRST 110 4. 2801 : CME 30 / SRST 30 5. 3825 : CME 185 / SRST 340 6. 3845 : CME 262 / SRST 720

Symptom: After a license upgrade from 48 to 64 user license on a UC520, the Cisco 500 series phone registration fails with the following errors in debug ephone register output: Error: Device Id 80000 Configured Device Id -1 StationSPCPRegisterTokenReject sent on socket 4
Conditions: Problem is seen when registering any 500 series phone to a CME on UC520 platforms. The problem only occurs when the ephone tag value for this phone registration is 56 or higher.
Workaround: Use an ephone tag that is of lower numerical value. Ephone 55 or lower will work.

Symptom: When on a call, on the primary number of an overlay set, and you receive a 2nd call on the 2nd DN of an overlay set...caller-id for the 2nd call shows up fine during ringing state. Once answered caller-id for the 2nd call disappears, but stays active/flashing for the first call that is on hold.
Conditions: Assume the below sample configuration: ephone-dn 4 dual-line number 6400 huntstop channel no huntstop ephone-dn 5 dual-line number 6400 preference 1 huntstop channel no huntstop ephone 3 mac-address 000C.30B1.98B4 type 7960 button 1c4,5 2:6 A call to 6400, ephone-dn 4, works fine...caller-id shows up during ringing and after answer just fine. if I then call 6400 again while ephone-dn 4 is still busy, ephone-dn 5 begins ringing on the busy phone...and this phone displays the caller-id just fine. Put the first call on hold, answer the 2nd call...and when it's answered the caller-id goes blank, the pop-up box goes gray...no more caller-id. This does not happen when calling over PRI or SIP, only when calling in over FXO port or from another local SCCP phone on the same CME.
Workaround: None

Symptom:MOH may hav static at regular intervals
Conditions:UC520 running IOS 15.01
Workaround:Increasing file buffer with "'moh-file-buffer " will decrease the frequency of the static.

Symptom: CCME port becomes stuck in a SEIZED state when integrated with Unity TSP and set to dialout MWI, which prevents any future MWI from being set through that port
Conditions: CCME integrated with Unity / Unity Connection running TSP 8.1(3) or earlier
Workaround: Reset the MWI port in CCME OR for Unity Connection: increase the timing interval to 1500ms by going to "Port-Group" and modify the "Delay between requests" setting, then restart Unity Connection OR for Unity: open the \CommServer\InitLib\Cisco0002.ini file in Notepad, then add the following lines at the end of the file: [Configuration] MinimumMWIRequestInterval=1500 Save your changes, then restart Unity Additional Information By increasing the timer to 1500ms, the TSP will wait 1500ms between placing MWI calls out the same port. This should allow the CCME enough time to finish processing the last call, and prevent the port from becoming stuck in a SEIZED state. However, this will introduce a slight delay in MWI, if you have a lot of requests queued up. Depending on your hardware and environment, you could get away with setting this value as low as 500ms, but 1500ms is a safe bet across the board.

Symptom: Missed calls not reported.
Conditions: When a DN has overlays configured, any unanswered calls to that particular DN are not reported as Missed calls.
Workaround: Remove overlays from the DN in the configuration.

Symptom: When using the TransVM (transfer to voicemail) soft key, the softkey does not operate as expected unless it is used before trying a Transfer.
Conditions: If a full consult transfer is attempted, and the called party elects not receive the transfer (but would like a voicemail), the caller who initiated the transfer cannot use the TransVM softkey because the functionality is missing. It does not permit the dialing of the voice mailbox extension (as it would had the full consult transfer not been attempted).
Workaround: The work around without upgrading to code which provides this fixed softkey feature is to have a dial peer which would transfer say to *### to get to the voicemail of extension ###.
Further Problem Description:

Symptom: steps: 1.shutdown cucm service.SCCP Phone 7911 registered with SRST 2. Keep the phone on hook 3. Press "New Call" softkey, nothing happen.
Conditions:
Workaround:
Further Problem Description:

Symptom: Memory leak due to the Skinny Msg Serve process.
Conditions: Observed on a C2851 running 12.4(22)T1.
Workaround: None.
Further Problem Description:

Symptom: Free memory is decreasing due to Presence Process
Conditions: Problem is experienced on a c2851 platform running c2800nm-spservicesk9-mz.124-20.T.bin The 12.4(20)T IOS version is bundled with CME 7.0
Workaround: None
Further Problem Description: