Table 3 Open Caveats for Cisco CallManager Release 3.0(12)
DDTS number
|
Description
|
Release-note
|
CSCdr20726
|
H.323 phone does not receive progress tones during call setup.
|
Workaround: No workaround exists.
|
CSCdr25206
|
Line state server does not update the Cisco WebAttendant.
|
Workaround: Call the phone to update the phone status or go off-hook on the phone to update the status.
|
CSCdr26521
|
A nested call forward back drives Cisco CallManager CPU usage to 100 percent.
|
For large systems, Cisco CallManager can have up to 400 voice-mail ports. The issue is the delay imposed by 400 call forward hops. As a workaround until station hunt groups are available in a future release, the number of hops should be minimized. The hops can be minimized if the calls to voice mail can be spread more evenly over the number of ports. The total number of voice mail ports should all be forwarded to each other and last voice-mail port will be forwarded back to the first port. The configuration parameter max number of hops will control the end of the search for an available port. With this setup, a search can start at any port in the list to find an available port. The call forward all and busy DN can then be configured to split the users into groups to spread the search load and increases the chances of finding an available port with fewer searches. Since the message button is a system parameter the message button will always start at the top of the list.
Workaround: The number of hops will be limited by the max number of hops configuration parameter.
|
CSCdr26539
|
A nested call forward no answer takes too much time to forward through a linear list.
|
For large systems, Cisco CallManager can have up to 400 voice-mail ports. The issue is the delay imposed by 400 call forward hops. As a work around until station hunt groups are available in a future release, the number of hops should be minimized. The hops can be minimized if the calls to voice mail can be spread more evenly over the number of ports. The total number of voice mail ports should all be forwarded to each other and last voice mail port will be forwarded back to the first port. The configuration parameter max number of hops will control the end of the search for an available port. With this setup, a search can start at any port in the list to find an available port. The call forward all and busy DN can then be configured to split the users into groups to spread the search load and increases the chances of finding an available port with fewer searches. Since the message button is a system parameter the message button will always start at the top of the list.
Workaround: The number of hops will be limited by the max number of hops configuration parameter.
|
CSCdr28947
|
Transfers from Cisco uOne to invalid extensions by pressing * 8 leave the caller in silence.
|
For example, if a user logs into a mailbox, presses * 8 to transfer, and enters an invalid extension, the transfer is attempted, but the user does not hear anything after the standard Cisco uOne prompt plays.
In this situation, the caller is on hold pending transfer completion. The transfer never completes because the extension was invalid, and reorder was returned to the uOne port. The Cisco uOne port does not recognize reorder, so no further action is taken. The caller is left on hold.
Workaround: The user can hang up the call and call the person directly. Always transfer calls through Cisco uOne using a valid extension.
|
CSCdr30366
|
User experiences a long dial tone (10-12secs) before dialing the phone via AT-2.
|
When using CTI to dial out through an AT-2 gateway, dialtone is heard for 10 to 12 seconds before the numbers are dialed.
This occured using a TAPI test tool, calling out through an AT-2 gateway with 10-digit dialing. Dialing 7 digits will cause the Cisco CallManager to wait for a timeout in case there are more digits. While waiting, this timeout period dialtone is played then the number is dialed. To avoid this, setup a route filter with LCOAL-AREA-CODE set to DOES-NOT-EXIST and END-OF-DIALING set to DOES-NOT-EXIST.
Workaround: None exists.
|
CSCdr36331
|
Going from low bit rate to low bit rate, the wrong counter is sent from a transcoder. The problem occurs when the system is configured, so a transcoder is invoked to transcode between two low-bit-rate codecs (for example, from a G.723 to a G.729).
 |
Note  Cisco CallManager Release 3.0 does not support the use of a transcoder to support low-bit-rate to low-bit-rate transcoding.
|
|
When a transcoder is invoked to transcode between two low-bit-rate codecs, the transcoder consumes the internal resources of two transcoders, but only one transcoder is allocated.
As a result, more transcoders are available to be allocated in the system than there are internal transcoding resources to support them. When all available internal transcoding resources are in use, and another transcoder is allocated and begins transcoding, the voice quality on all calls going through that transcoder device degrades noticeably and, sometimes, severely.
Workaround: Cisco highly recommends that the system be carefully configured, so that transcoding between low-bit-rate codecs is not required.
No workaround exists for this problem other than limiting the number of calls through a given transcoder device by expanding the number of transcoders available.
Having at least twice as many transcoders available as there are calls that need them at any given time should eliminate this problem.
|
CSCdr36406
|
A <CmdArg>[Object Error]<noCmdArg> error message returns when a user is added via the Cisco CallManager administration page.
|
If users have been added to the system via private scripts, the directory may not allow some userid name conflicts to occur but does not properly report the conflict. For example, a user with the userid of "jsmith@company.com" will conflict with the proposed userid of "jsmith." This problem should not appear through normal usage of the product.
Workaround: Use a different userid for the new user or access the directory directly to delete the conflicting user.
|
CSCdr36513
|
The TSP does not see login changes until bouncing back from telephony.
|
While the telephony service is running, if the username and/or password is changed, the TSP will not pick up the change unless the telephony service is stopped and started.
This occurs while the telephony service is running.
Workaround: Restart telephony.
|
CSCdr39403
|
Database notification does not work in certain situations. Updates made from the Cisco CallManager administration page are registered but not reflected in the MIB tables until the SNMP data collector or Cisco CallManager (depending on the type of update) is restarted.
|
In Cisco CallManager clusters, changes to global values in a cluster environment appear on the MIB table that is local to the change but not in all MIB tables throughout the cluster. Updates will only appear on the MIB table that is local to the change, with the following exceptions:
•When a time, region, or any static item is deleted, no MIB tables reflects the change.
•When groups and regions are added, no MIB tables reflects the change.
Workaround: Restart the SNMP data collector or Cisco CallManager to display updated values in the MIB tables. If a Cisco CallManager cluster is involved, you must restart all SNMP data collectors to show consistent values in the MIB tables throughout the cluster.
Examples (local):
•To remedy the two exceptions to local MIB table updating when deleting a time, region, or any static item, restart the SNMP data collector for the local Cisco CallManager installation to see the update reflected in the MIB table.
•When adding groups and regions to a Cisco CallManager cluster, restart the SNMP data collector, which will help to update the MIB table.
|
CSCdr41623
|
When a port on a Cisco Unicast Conference Bridge is conferenced back to itself, a feedback loop is created in the conference bridge, and all participants experience audio feedback. Even if all phones involved in the conference hang up, the conference bridge still has a feedback loop because two or more ports of the conference bridge are conferenced together, and neither has disconnect supervision.
|
Workaround: You must perform a conference bridge reset to clear the conference.
|
CSCdr43111
|
Call only forwards once if route point does not have forward on no answer.
|
Workaround: Configure a forward on no answer destination for 3000 to point to some arbitrary other phone (i.e., 1006); then, you will no longer experience the problem.
|
CSCdr43369
|
When primary database disk is full, Cisco CallManager memory rises more than 700MB.
|
Cisco CallManager memory grows unbounded.
This may occur in a standard installation when the disk is full and CDR records are being written; the CDR write to the DB fails; deletion of the CDR records causes the transaction log to grow, so no disk space is recovered.
Workaround: Most Cisco CallManager servers will have plenty of disk space (more than 10 GB). You can resolve this problem by lowering the MaxCDR service parameter, so CDR records are deleted. Then, back up the server. Backing up the server will checkpoint the database and shrink the transaction log.
|
CSCdr46216
|
Wild characters !, ?, and + do not work with translation patterns.
|
While the telephony service is running, if the username and/or password is changed, the TSP will not pick up the change unless the telephony service is stopped and started.
This occurs while the telephony service is running.
Workaround: Restart telephony.
|
CSCdr48076
|
Cisco IP Phone 7960 transfer button causes malfunction of Resume button.
|
Workaround: The workaround is for caller A to go on and off hook and then press the EndCall softkey. This will enable the Resume softkey.
|
CSCdr52476
|
Cisco IP Phone 7960 documentation does not reflect a complete list of headsets.
|
The Cisco IP Phone Administrator's Guide does not accurately reflect the supported Headset models. The overview section states: The Cisco IP Phone 7960 supports a four or six-wire headset jack (Plantronic's compatible is required) for the Cisco IP Phone 7960. The Volume and Mute controls will also adjust volume to the earpiece and mute the speech path of the headset. The headset activation key is located on the front of the Cisco IP Phone. It has been verified that not all Plantronic's compatible headsets will function in the headset jack. There needs to be documentation to list each Plantronic's headset model that is supported; otherwise, this could generate alot of support calls to CA asking what exactly is supported.
Workaround: Provide a complete list of compatible headsets.
|
CSCdr54928
|
Cisco CallManager stops using Cisco Catalyst 4000 conference bridge.
|
Workaround: No workaround exists.
|
CSCdr55953
|
SNMP requires Cisco CallManager service to be restarted for phone addition/deletion.
|
Workaround: After you add or remove an extension from a phone, you must restart the Cisco CallManager service for SNMP agent to report the new information, so User Tracking can discover the changes.
|
CSCdr57791
|
Users cannot join MeetMe conference if one number is used instead of a range.
|
Workaround: Configure a pattern for the MeetMe number. This allows the users from other Cisco CallManagers to use the MeetMe number.
|
CSCdr60978
|
A terminal drops when a user tried to do a conference transfer scenario.
|
Transfer operation will be cancelled. All the calls remain in their own call states with no impact.
This problem occurs in one of the conference transfer scenarios. A party is trying to transfer the conference consultation call during a conference call setup.
Workaround: Restart transfer operation after the conference setup completes.
|
CSCdr64159
|
Cisco CallManager does not start if DNS suffix is conf in Network Ident tab.
|
The Cisco CallManager 3.0(1) installer CD will not work with servers in Cisco CallManager 3.0(1) that are configured with DNS names.
Workarounds: Change the Cisco CallManager names from DNS names to IP addresses (and ensure reverse DNS entries exist on the DNS server for those IP addresses). Change the Cisco CallManager name to non-fully qualified DNS names and remove the DNS Suffix from the Cisco CallManager using the following procedure:
1. Right click on My Computer.
2. Select Properties.
3. Click the Network Identification tab.
4. Click Properties.
5. Click More....
6. Remove the suffix from the Primary DNS suffix of this computer box.
7. Uncheck the Change primary DNS suffix when domain membership changes box
8. Click OK for all the open dialogs -- A window prompts you to restart.
9. Restart the Cisco CallManager.
|
CSCdr65502
|
Automated install may require user to reboot after reprogramming firmware.
|
During the installation of the Cisco CallManager 3.0(1), the MCS-7830 may stop at the following point: Running array F/W Update: COMPAQ H/W Upgrade Utility 4.0.1A (R): Reprogramming Firmware: DO NOT RE-BOOT OR POWER CYCLE MACHINE!!! Development Engineering is investigating the cause. The update should not take more than a minute or two.
Workaround: Reboot the machine after about 10 minutes (to be safe) and the installation will successfully complete.
|
CSCdr66431
|
Reinstallaing a subscriber Cisco CallManager from scratch does not work.
|
When a subscriber Cisco CallManager machine is replaced or reinstalled from scratch, steps must be taken for that subscriber to function.
Workaround: The administrator must use the Cisco CallManager Administration to remove the subscriber Cisco CallManager as a server. In order to do this, all devices, Groups, Pools, etc. that reference that subscriber server must also be removed. If this is done prior to installing the replaced or refreshed subscriber machine then installation will function correctly.
|
CSCdr67468
|
H.323 gateway configured as H.225 will not work with Cisco CallManager 3.0(1).
|
When configuring a H.323 gateway between two Cisco CallManagers running 3.0(1), the device protocol must be inter-cluster trunk.
Workaround: Add this information to the gateway sections of the Cisco CallManager Administration Guide.
|
CSCdr70322
|
CAUSE for arbitrary conference is CAUSE_TRANSFER sometimes.
|
On some circumstances, the cause code for the events related to the conference operation is set to TRANSFER instead of CONFERENCE.
Workaround: Application may use the CiscoConferenceStartEv/CiscoTransferStartEv events to ensure that they are in a conference or transfer.
|
CSCdr77184
|
Call park numbers do not recycle through configured range.
|
Workaround: Go to Feature > Call Park, select a range, and click Update; or create a new range.
|
CSCdr80075
|
A need exists for the Cisco CallManager to check the assignment of lines and speed-dial keys for errors.
|
Workaround: Put all lines at the top of the button template (before speed dials) or update the phone load to version P003H300 or later.
|
CSCdr80638
|
Locations do not recognize a transcoder correctly.
|
Workaround: No workaround exists.
|
CSCdr80728
|
Automated install CD does not load Cisco Media Convergence Server 7835 (MCS7835) without locking up.
|
Workaround: Update the server BIOS.
|
CSCdr81135
|
Devices cannot be associated to user using Netscape; Javascript error displays.
|
Using Netscape 4.7 or 4.73 on different PCs, go to Global Directory, choose user, press Associate Devices, and go to User Device Assignment screen. When you check a device box, at the bottom of the browser, it displays "Javascript error: Type 'Javascript:' into Location for details." When you press update, the device does not get associated with the user.
Workaround: Use Microsoft Internet Explorer 5.0.
|
CSCdr85945
|
Incorrect help definitions appear for Hold service parameters.
|
The following two definitions are the correct service parameters.
•HoldType — Determines whether the hold light flashes more rapidly for the user who placed a call on hold when two different phones share the same directory number. Default is still F.
•ToneOnHoldTime — Determines the interval between tones when a call is on hold. Default is 10 seconds, and the value range is 3 to 99999.
Workaround: Use the preceding definitions instead of the definitions in the Cisco CallManager Administration Guide and online help.
|
CSCdr89154
|
Using MTP causes delay in audio path.
|
The scenario described in the bug may occur when using a H.323 gateway with a MTP. The media part in the Cisco CallManager cannot wait for the establishment of media signalling path on both ends before letting the devices start streaming when using a MTP device in between. Hence the AA starts streaming even before the path between the GW and the MTP was being setup. The problem does not occur when a MTP device is not used.
Workaround: None exists.
|
CSCdr97481
|
Line button does not answer call on Cisco IP Phone model 30 VIP/12 SP+ with call pickup.
|
Workaround: Use the hookflash to retrieve the call.
|
CSCds04904
|
IVR greeting is clipped through call via FXS or T1.
|
When calling to IVR through ICS7750 MRP200, greeting message from IVR is clipped. Fragment of the very first word may be missing. No functionality is affected.
Workaround: None exists.
|
CSCds07952
|
"lineAccept" fails when already in connected state.
|
For CTI ports when a call-waiting call comes in, it is automatically accepted by the CTI port. If an application tries to accept the call, an error will be returned.
This occurs under normal conditions when calls to a CTI port stay in the offering state until an application accepts or answers them. The exception is call waiting calls. If a call is already active on a line and a second call comes in, this call will be automatically accepted by CTI.
Workaround: Ignore the error from the lineAccept request.
|
CSCds09562
|
A need exists for an error code to distinguish between invalid and out-of-service extension.
|
The problem is that no distinction is made between calling a DN that is not configured in the Cisco CallManager and calling a DN that is not registered. The reason for this is that digit analysis does not know about DNs that are not registered, so calling a CTI port that is not open is the same as calling a CTI port that is not configured. To digit analysis, these are the same error.
Workaround: Provide a generic message at the application level to cover both cases.
|
CSCds09623
|
The scroll bar does not appear on Device/Phone list page.
|
Workaround: The Administration web pages are designed for a minimum display resolution of 800 x 600. This release does not support lower resolutions.
|
CSCds12355
|
Cisco CallManager reboot causes no-answer condition in random Cisco uOne in cluster.
|
Workaround: Whenever the primary Cisco CallManager is rebooted, after the primary Cisco CallManager is active, stop and start "uTel" and any other dependant services.
|
CSCds12709
|
User cannot reset/restart any phone from Cisco CallManager 3.0 Device/phone.
|
Attempting to reset any device from the Cisco CallManager Administration web pages results in a window displaying an error message similar to this: ErrorNo. 1542: CDBLException Dump: [comerror]hr: 80070424 com error Description = [][the specified service does not exist as an installed service.] Cause: The Cisco Database Layer Monitor service was not installed as a service during install or upgrade.
Workaround: Manually install the Cisco Database Layer Monitor service. Open a command window, and at the command prompt, type the following:
<CmdBold>c:\progra~1\cisco\bin\aupair.exe -service<NoCmdBold>.
To confirm that the Cisco Database Layer Monitor service is installed, open the Component Services console (Start>Programs>Administrative Tools>Component Services), and look for Cisco Database Layer Monitor in the list of Services. The service starts automatically when it is first accessed.
|
CSCds14138
|
AVVID: A need exists for the automated install to allow reinstall option.
|
Workaround: You may have to wipe the disk completely to get the install to work. Do this by downloading the Compaq System Erase Utility from Compaq.com and erasing the machine completely.
|
CSCds18615
|
Redirect to wrong address via DT24 disconnects two party call.
|
The application will not be able to reroute the call again, and the caller will hear reorder tone.
Workaround: None exists.
|
CSCds18680
|
Users cannot set URL for plug ins.
|
Workaround: Install the plug in again on the first server. URLs will be set back again.
|
CSCds19482
|
CPU usage cycles from 40% to 70% every 20 seconds.
|
Cisco CallManager Release 3.0(3) resolves this bug.
Workaround: None exists.
|
CSCds20133
|
Call Forward Back fails when Cisco CallManager attempts to use unavailable Catalyst 4000 Access Gateway Module Call Forward Back resource.
|
Workaround: In the Admin/GUI page, under the conference bridge page, set the number of parties per ad hoc conference to the number of streams that a DSP on the Catalyst 4000 Access Gateway Module provided.
|
CSCds28204
|
AVVID: Call Forward No Answer and Call Forward Back does not use device Call Search Space when forwarding.
|
Workaround: Add the Call Search Space to the Call Forward No Answer and Call Forward Back numbers.
|
CSCds30227
|
Cisco CallManager does not reroute MWI request.
|
To avoid this problem, configure Cisco uOne properly. Cisco uOne is designed to work with multiple Cisco CallManagers, so there is an .ini file where you can list all the SSMWI devices in your clusters/cloud/domain/map with corresponding range of phone numbers. So when we deal with a phone number, we look up which range it falls and use the device and host.
Workaround: None exists. This works as designed.
|
CSCds33062
|
If an MWI light is on a phone, and the CM is reset, after the user logs in to the mailbox and deletes the voice messages, the MWI light stays on.
|
Workaround: Use at least version Cisco CallManager 3.1 or use a version below Cisco CallManager 3.5(a).
|
CSCds34785
|
SQL server passwords cannot be changed.
|
Workaround: Refer to the Installation Guide instructions for changing the SQLsvc and the Cisco CallManager administration user IDs.
|
CSCds36697
|
Users cannot delete database service from service parameters configuration page.
|
Workaround: See CSCds34596 in this document for a way to remove the server from the cluster if this is the desired end result.
|
CSCds38058
|
DBL takes too long (more than 20 minutes) to return 10,000 devices.
|
Query and analysis of result set using the database layer take a long time to execute.
Workaround: None exists.
|
CSCds42397
|
Terminal services do not function.
|
Workaround: This is a Microsoft limitation.
|
CSCds48200
|
Missing Disconnected, Established & TransferEnd in conference-transfer scenario.
|
Workaround: Avoid the scenario in which one party of the call is doing consult transfer and other party from the same call is performing consult conference.
|
CSCds48216
|
Missing DisconnEv, EstablishedEv & ConferenceEnd if conference PNC transfer.
|
Workaround: Avoid cases of starting as a consult transfer and invoking consult conference without completing the transfer first or vice versa. If you start an operation, finish it, and then perform next operation.
|
CSCds49273
|
Cisco CallManager prompts for MCS & SA pass, even though there is an existing password.
|
If you have already installed one Cisco CallManager which used the latest OS CD and Cisco CallManager, give it a password for MCS and SA as cisco, for instance. Then upgrade the Cisco CallManager to the latest version. At the install completes, it will still prompt the user to enter the password for MCS and SA again.
Workaround: When Cisco CallManager is being installed, the passwords are set to default and must be changed by the user.
|
CSCds50352
|
A System Unavailable message sporadically appears on Cisco IP Phone 7960.
|
This occurs under normal operating conditions.
Workaround: None exists.
|
CSCds50413
|
Missing Disconnected, Established & TransferEnd in conference transfer scenario.
|
Workaround: No workaround exists.
|
CSCds50626
|
STIBOOT caused an exception c0000006H in module MSVBVM50.DLL at 0137.
|
Workaround: Do not remove the media during the installation. If the media is removed, restart the install.
|
CSCds50763
|
Spurious NewCall is created when a redirect is done following an unhold state.
|
Workaround: No workaround exists for either Cisco IP Phone model 12 SP+ or Cisco IP Phone model 30 VIP; however, this operations works on the Cisco IP Phone 7900 family.
|
CSCds50786
|
Users must create conference parent call before sending out conferenced events.
|
Workaround: Microsoft will not fix this bug until Service Pack 3 of Windows 2000; therefore, to work around this problem, you must configure the multiprocessor machine to use only one of the processors on that machine.
|
CSCds55389
|
Backup installation starts after the Cisco CallManager installation is exited.
|
Workaround: This works as designed. Even if the install is exited, the backup utility needs to be configured (or server chosen as target).
|
CSCds55703
|
Cisco IP Phones do not forward large NFS datagrams.
|
The phone does not forward NFS datagrams for packet sizes larger than 11832 bytes.
Workaround: Configure the network port to match the speed of the access port.
|
CSCds56040
|
A transfer from second call incorrectly connects to first call on hold.
|
A hold call is mistakenly joined together when incoming call arrives on the same line.
To reproduce this problem, hit transfer button twice on an incoming call while another call on is on hold at the same line.
Workaround: It works as design. For the Cisco CallManager Release 3.0, this is how the transfer works on a single line appearance. It will be different when secretary-boss feature is implemented in the post Cisco CallManager Release 3.1.
|
CSCds59268
|
When Call Forward No Answer is configured on a line with partition, the calls forward to Call Forward No Answer.
|
Workaround: To continue using the Personal Assistant feature, the following configuration can be used as a workaround until this problem is fixed. Using setup as example, configure the calling search space PA to has partition PA only. Phone1 with DN 2007 has calling search space of PA; then, it can only call phone3; so, when phone1 dials 2003, phone3 (Personal Assistant) will receive the call.
|
CSCds62385
|
Cisco CallManager sends alerting before connect while in progress state.
|
Workaround: No workaround exists for this problem.
|
CSCds66500
|
Directory number does not show up on Cisco WebAttendant interface.
|
Workaround: The administrator should copy one of the two databases (UsersDB1.mdb, UsersDB2.mdb) to the local machine of the Cisco WebAttendant user. After the database has been copied, click the Settings button on the WebAttendant client. This will bring up the settings dialog box where the administrator may enter the local database path of the newly copied database. The administrator must then click OK on the settings dialog and restart the WebAttendant. The draw back to this fix is that the administrator must recopy the database file every time the user information changes.
|
CSCds67113
|
Cisco IP phone does not forward Network File System (NFS) datagrams for packet sizes larger than 11832 bytes.
|
Workaround: Configure the network port to match the speed of the access port.
|
CSCds67777
|
Blind transfer cannot complete successfully.
|
Workaround: No workaround exists.
|
CSCds69228
|
Even after Cisco WebAttendant logs out, calls are still directed to an extension.
|
After an "APPARENT" logout request by a Cisco WebAttendant user, the hunt group redirected calls still arrive at a phone that is only in the hunt group as an associated number to a users. Not as specific directory numbers.
This occurred when the Cisco WebAttendant client application experienced a local crash and therefore the logout request or message was never sent to the TcdSrv server component. So from the TcdSrv's perspective the client or Cisco WebAttendant was still active and logged in. Therefore calls where still being redirected to this station or phone.
Workaround: If the client disappears for any reason (crash, network outage etc...), TcdSrv detects the loss (no keepalives) and destroys the Cisco WebAttendant logical components. This will cause the calls to be routed to other directory numbers or user that are still logged in or available. The key here is to wait for a period long enough for TcdSrv to detect the lost client (3 miniutes). So until the keepalive timer expires for a lost client calls will still be routed to the associated client phone.
|
CSCds72057
|
Incorrect information appears in call block for conference call.
|
In a third-party conference, if one of the parties drops out and is conferenced in again, then the roster is incomplete (does not show all the participants), although the user has audio path with everyone
Workaround: None exists.
|
CSCds75317
|
A lineRedirect() call back to calling party causes problems.
|
Workaround: Do not redirect the call back to the caller, which should not happen under normal circumstances
|
CSCds76447
|
Cisco plugins incomplete and install.asp for plugins incorrect
|
Cisco WebAttendant will not function correctly on some installations because of CSCds66507.
Workaround: Do not install Cisco WebAttendant.
|
CSCds77984
|
Cisco IP Phone 7960 sends unregistermessageid and phone resets
|
Cisco IP Phone 7960s randomly send an unregistermessageid to the CallManager. The phone resets and registers with the same CallManager.
|
CSCds79206
|
Request exists for capability to hardcode speed and duplex on Cisco IP Phone 7960.
|
Workaround: No workaround exists.
|
CSCds79401
|
AVVID: Audio is heard through the handset when using the headset on Cisco IP Phone 7960.
|
Workaround: No workaround exists.
|
CSCds80198
|
Call pickup does not pick up a call even when line is Call Forward All.
|
Workaround: No workaround exists
|
CSCds81268
|
Cisco WebAttendant is not supported but plugin allows the installation.
|
Workaround: As the Release Notes for Cisco CallManager Release 3.0(5a) suggest, do not install Cisco WebAttendant.
|
CSCds84446
|
AVVID: Volume from Cisco Access Digital Trunk Gateway DT-24+ to Cisco uOne is too low to hear voice mail.
|
Workaround: No workaround exists.
|
CSCds87289
|
Hunt groups made from UserIDs and line numbers cannot cross Cisco CallManagers.
|
TcdSrv in one cluster handling a pilot point call redirects a call to a hunt group member in another cluster even when the line is busy. This occurs when the line state information is shared between TcdSrv's inside clusters only. Therefore if the hunt group contains members that are in fact in other clusters the calls will alays be routed to this number even if it is active or busy.
Workaround: Keep hunt group members within the same cluster as the pilot point when ever possible.
|
CSCds88617
|
GWY_ERR_C80ERR_RESOURCEUNAVAILABLE is reported from Cisco Access Digital Trunk Gateway DT-24+..
|
Workaround: Contact the TAC for the Cisco Access Digital Trunk Gateway DT-24+ load that will fix this issue
|
CSCds88657
|
Gatekeeper calls cause memory loss and stay up after being closed.
|
Workaround: Place calls at a slower rate if using SimClient or other test software. This defect should not occur during "normal," non-automated-calling scenarios.
|
CSCdt01353
|
DBL cannot start on subscriber after upgrade to Cisco CallManager 3.0(5a)
|
The Database Layer Monitor will hang during startup and Win2000 will report "At least one service failed to start."
Workaround: None exists.
|
CSCdt02575
|
SMDI sends no or wrong info on transfer from Octel.
|
Workaround: No workaround exists.
|
CSCdt02828
|
Mute button on Cisco IP Phone 7960 enables VAD even with VAD disabled system-wide.
|
The Cisco IP Phone 7960 stops sending RTP packets when you press the mute button, even if it has been disabled via the Service Parameters SilenceSuppressionSystemWide and SilenceSuppressionWithGateways.
Workaround: None exists.
|
CSCdt04394
|
Timer set to 0 does not disable the timer.
|
Workaround: Configure Call Forward No Answer to route calls to a voice-mail system or to an attendant.
|
CSCdt05077
|
Reinstalling the subscriber Cisco CallManager with a different hostname does not take effect.
|
Workaround: Changing the server host name is not supported due to SQL server limitation on SQL server. If you need to change the server name (CM name), you must reinstall from scratch.
|
CSCdt10505
|
When phone1 is forwarded to Cisco AutoAttendant, phone2 never transfers to Call Forward No Answer destination.
|
Workaround: Assign the first DID to the route point or use a translation pattern to reroute the call.
|
CSCdt11416
|
Conference master can transfer the ability to add participants.
|
Workaround: No workaround exists.
|
CSCdt12390
|
Cisco IP Phone sends no busy tone when Cisco WebAttendant lines are full.
|
This occurs when all members in a hunt group are busy in active calls, and a new call arrives at the pilot point number. So two passes are made through the hunt group looking for a destination. If none is found, then the call drops to prevent starvation of all pilot point callers. This is the classic ACD overflow conditions that would normally be handled by a message queue or some sort.
Workaround: Make sure that the hunt group has some sort of overflow handling; such as, the last number in the HG could be a voice-mail number or pilot-point number that can always except calls. In the Cisco WebAttendant hunt group administration window, a checkbox for always Route exists. This means that even if TcdSrv knows the number is busy, it can handle more than one call at a time, so when reached in a hunt group search, TcdSrv always redirects the call to this number.
|
CSCdt13722
|
Cisco WebAttendant screen does not display call-forwarding information.
|
Workaround: No workaround exists.
|
CSCdt20517
|
Calls placed on IP phones show translated No.
|
Workaround: The problem does not occur when no translation is done, but if dial translations are required, no workaround exists.
|
CSCdt21522
|
User cannot make more than 20 729-711 transcodings with Voice Activity Detection (VAD) disabled.
|
Workaround: Set PreferedG711MillesecondPacketSize = 20msec PreferedG729MillesecondPacketSize = 20msec PreferedG723MillesecondPacketSize = 30msec SilenceSupressionSystemWide = True and False.
|
CSCdt25949
|
DB Error (objTraceList) = 1542 undefined error displays.
|
Workaround: No workaround exists.
|
CSCdt26108
|
User cannot open two lines on one Computer Telephony Integration (CTI) port.
|
Workaround: Configure the Cisco CallManager to have only one line per CTI port device.
|
CSCdt27464
|
Documents for Call Forward Answer do not mention special case of CSS set to <none>.
|
Workaround: When the Call Forward All button or Call Forward from the Cisco CallManager user administration are used, if the Calling Search Space for Call Forward All is set to <none>, the Calling Search Space that is used for Call Forward All (CFA) is the Search Space on the Line and the phone, not the Search Space that is configured for Call Forward All, which is <none> in this case. In the context of the Call Forward All Calling Search Space, <none> does not mean the NULL Calling Search Space, but rather means the combination of the line and phone Calling Search Space for the device initiating the Call Forward All.
|
CSCdt28706
|
Phones stop playing ringback after OLC.
|
Workaround: No workaround exists.
|
CSCdt29275
|
Cisco CallManager 3.0(5a) upgrades reset enterprise parameter URLs to default.
|
Workaround: After the upgrade, change the URLs to the values that existed prior to the upgrade.
|
CSCdt30332
|
Cisco Messaging Interface stops after Cisco CallManager 3.0(7) upgrades.
|
Workaround: This is not an error. A blank VoiceMailDN is an invalid configuration. If using partitions and Calling Search Spaces when configuring CMI, verify that the same partition applies to both the CMI partition and the route pattern assigned to the third-party voice-mail system.
For example:
Route Pattern 17050
Partition vm
.....
VoiceMailDn 17050
VoiceMailPartition vm
|
CSCdt30432
|
Cisco CallManager does not handle SUS/RES satisfactorily.
|
If the IP phone goes on-hook first, the Cisco AS5300 Network Access Server (NAS) will never receive a H.225 RELEASE message from the Cisco Call Manager. This will result in the calling party in the SS7 network experiencing fast-busy, or reorder tones.
In a Cisco SS7 Interconnect for Voice Gateways solution, if a call is made from an phone in the SS7 network to a Cisco Call Manager IP phone, the call will not be torn down gracefully if the IP phone goes on-hook first. The call flow is as follows:
SS7 phone -> Cisco MGC -> NI2+ -> AS5300 -> Cisco CM -> Cisco IP phone
If the IP phone goes on-hook first, the Cisco AS5300 Network Access Server (NAS) will never receive a H.225 RELEASE message from the Cisco Call Manager. This will result in the calling party in the SS7 network experiencing fast-busy, or reorder, tones. In addition, this behavior prohibits end-to-end SUSPEND and RESUME functionality from working correctly within the context of this call flow. The workaround is for the calling party in the SS7 network to hang up first.
Workaround: None exists.
Cisco CallManager does not support SUS/RES capabilities over PRI or H323. When IP phone goes on hook, the call is considered to be cleared right away.
|
CSCdt35469
|
Logging on to Cisco CallManager user pages transmits a clear text password.
|
Workaround: Choose Start > Administrative tool > Internet Information Service
Right click on CCMUser.
Click on Properties.
Select Directory Security tab.
Click Edit and set the security lever. This may only allow IE to browse the page.
|
CSCdt36334
|
Poor interface response with large number of records
|
Slow interface response in Route Plan-related screens when adding or changing records with large number (several hundreds) of records defined in Route Partition, Calling Search Space, Route Filter, Route Group and Route Lists.
Workaround: None exists.
|
CSCdt40683
|
Cisco Messaging Interface partition must match route partition when configuring Cisco Messaging Interface.
|
Workaround: If you are using partitions and calling search spaces, when configuring CMI, verify that the same partition applies to both the CMI partition, and the route pattern assigned to the third-party voice-mail system.
Example:
Route Pattern 17050
Partition vm
.....
VoiceMailDn 17050
VoiceMailPartition vm
|
CSCdt41163
|
User cannot dial complete digits.
|
User cannot dial digits when a particular translation pattern is set.
Workaround: None exists.
|
CSCdt44000
|
Call detail records are intermittently not written locally.
|
Workaround: No workaround exists.
|
CSCdt44611
|
Cisco WebAttendant Line State Server LSS is not correct when TCD starts.
|
Workaround: Take any phones that have the line state as not present off hook and put them back on hook. Any line state change will update the Cisco WebAttendant directory area.
|
CSCdt45104
|
Calls may drop when changing between Cisco WebAttendant SL lines.
|
When a multiline phone has multiple calls, taking one of the calls off hold, causes the currently active call to be disconnected.
Workaround: Allow a second or two in between clicking on calls.
|
CSCdt45118
|
Abnormally high memory usage occurs by SQL server.
|
Workaround: Turn off the BAT and ART tools; then, restart the Cisco CallManager.
|
CSCdt45861
|
Failed SetupTransfer request incorrectly modifies existing calls.
|
Workaround: The application should not be calling lineSetupTransfer() in this scenario.
|
CSCdt48558
|
A need exists to dynamically add route points for Cisco WebAttendant.
|
Workaround: No workaround exists.
|
CSCdt49265
|
The web upgrade allows user to perform a new install.
|
When the upgrade is performed, the user is not prompted with any messages stating a previous version of Cisco CallManager needs to be installed prior to continuing. The install proceeds with no noticeable errors. Following the install reboot, if the user goes to the start menu, Cisco CallManager does not appear.
Workaround: An older version of Cisco CallManager should exist on the system prior to upgrade; otherwise, the upgrade fails.
|
CSCdt49736
|
Some memory goes up when adding phones using BAT, and it never goes down.
|
Memory in dllhost, ccm, and aupair goes up and never goes down when using BAT to add a 2500 phones.
Workaround: None exists.
|
CSCdt50317
|
Cisco CallManager 3.0(7) call detail records do not move from subscriber to publisher.
|
Workaround: No workaround exists.
|
CSCdt50538
|
A shared line problem occurs when one of the phones returns from reset.
|
If a phone with a shared line appearance resets, there is no indication that the line is actively in use on another phone until the phone that just reset tries to go offhook. The phone will send an offhook message to Cisco CallManager but the display will indicate "Line in use"
Workaround: None exists.
|
CSCdt51159
|
Resetting H.225 device by any means causes AnonymousDevice failure.
|
Anonymous calls stop working when changing configuration of unrelated devices.
This problem occurs when any H.225 device is reset.
Workaround: In Release 3.0(8), none exists, but in Release 3.0(9), press the Reset Gateway button on the Gatekeeper configuration page to reset AnonymousDevice.
|
CSCdt52823
|
There are orphaned DNs listed in the View in File Route Plan Report that have no Device Name info.
|
If the DN was previously assigned to a device, when a device partition is changed the DN is orphaned.
Workaround: Assign the desired DN to a phone. Then remove the DN from the phone. The DN record will be removed from the database, and the Route Plan Report will work correctly.
|
CSCdt52841
|
Cisco WebAttendant documentation calls for read access to the wausers share, but change access is required to open the database.
|
Workaround: Allow change access to the wausers share.
|
CSCdt53938
|
Upgrade does not put BINs in nondefault TFTPPATH.
|
Workaround: Two known workarounds exist.
1) Upgrade the primary TFTP server first
2) Place the device loads on the primary TFTP server before upgrading any of the other clusters.
|
CSCdt54310
|
Call Detail Records are written incorrectly when digit manipulation is performed on Route List.
|
Workaround: Perform digit manipulation on the Route Pattern. This may cause other ill effects, such as causing the Placed Calls directory on the Cisco IP phone to not include the correct number.
|
CSCdt57270
|
Publisher and or subscriber servers have difficulty with different passwords.
|
Workaround: Use the same administrator password for the publisher and all subscriber servers.
|
CSCdt62091
|
Directory number entries remain in database.
|
Workaround: Assign the desired directory number to a phone; then, remove the directory number from the phone. The directory number record will be removed from the database.
|
CSCdt62208
|
Cisco IP Phone 7960 reports two missed calls if unanswered.
|
Workaround: Mask the problem by increasing the CallManager T301 timer so that the ringout time is greater than the PSTN ringout time.
|
CSCdt62292
|
Call from PSTN to an undefined directory number records 0 in CDR.
|
Workaround: No workaround exists.
|
CSCdt64163
|
User cannot delete partition from Cisco Callmanager.
|
Workaround: Contact TAC.
|
CSCdt65088
|
Cisco WebAttendant SL1 fails after numerous transfers.
|
Workaround: Stop and start the TCD service.
|
CSCdt65122
|
Active Directory users added with Cisco CallManager or BAT do not get valid UserID.
|
The problem occurs you enter users with Cisco CallManager or BAT, and you enter passwords with Active Directory. A valid UserID and password for User Preference Pages cannot be found.
Workaround: This bug has two workarounds.
1. Add users from Active Directory server. Set Registry entry DIRACCESS to False. Do not use BAT to add users.
2. Enable the user from the Active Directory interface; change the password. Then, you can log in.
|
CSCdt66176
|
Speed dial update delays 45 to 60 seconds on Cisco IP Phone 7960.
|
Updating speed dials from Cisco CallManager user interface takes up to 60 seconds to appear on the Cisco IP Phone 7960. Information is seen to update immediately in all databases. This happens in a multiple Cisco CallManager system running 3.0(8) where phones are registered to the subscriber. This problem also appears when updating line appearances from the Cisco CallManager Administration page. Problem: The Cisco IP Phone 7960s do not retrieve the new directory information. Regardless of the number of Cisco IP Phone 7960 updates or resets, it will take 45-60 seconds for this information to appear on the Cisco IP Phone 7960. Information is populated immediately to the databases of all Cisco CallManagers. This has been tested with multiple phone loads (P003Q301 and P003V301) with no change.
Workaround: Doing a hard reboot of all Cisco CallManagers corrects this problem.
|
CSCdt66634
|
User cannot execute find queries within Cisco CallManager.
|
Symptom: Can not use "Find" to query database within Call Manager. Get the following error when trying to query "HTTP 500.100 - Internal Server Error - ASP error Internet Information Services."
Workaround: None exists.
|
CSCdt67550
|
To change system server from a name to IP requires user to restart of the TFTP service.
|
Workaround: Go to System > Server in CallManager Administration, change the server name to its IP address. Then go to Service > Control Center, and stop and start the Cisco TFTP server.
|
CSCdt67779
|
If more than 100 Call Detail Records (CDRs) are written per the defined interval, the process stops after the first 100 and waits for the next timed interval.
|
Workaround: Shorten the defined time interval.
|
CSCdt69873
|
Corporate directory does not exist intermittently in the Cisco IP Phone 7960.
|
Workaround: No workaround exists.
|
CSCdt73651
|
Cisco WebAttendant cannot log in when lines are not contiguous on phone.
|
Workaround: Configure lines on Cisco IP Phones so that they are contiguous.
|
CSCdt73926
|
CDR CallID is reset with Cisco CallManager restart.
|
Upon examining the CDRs, you may see a large number of records with the same globalCallID_callId number.
Workaround: If Cisco CallManager must be restarted, extract CDRs before restarting Cisco CallManager. Otherwise, related records will need to be determined by examination of the time and date of the record.
|
CSCdt73926
|
CDR CallID is reset with Cisco CallManager restart.
|
Workaround: If Cisco CallManager must be restarted, extract CDRs before restarting Cisco CallManager. Otherwise, relate records will need to be determined by examination of the time and date of the record.
|
CSCdt76403
|
CDR records are incorrect when recording conference calls.
|
Workaround: No workaround exists.
|
CSCdt83560
|
User cannot change load of Cisco IP Phone 7960.
|
Cisco IP Phone 7960 will not upgrade its load. The appropriate configuration file is missing.
Workaround: 1. Connect the phone to a Cisco CallManager Release 3.1(1) to back-rev its load.
2. Build and install a Cisco CallManager Release 3.1(1) compatible configuration file for the phone.
|
CSCdt85557
|
Group call pickup with insufficient bandwidth causes failure and bandwidth miscalculation.
|
Calls fail when the bandwidth is not sufficient for group call pickup.
Workaround: None exists.
|
CSCdt86164
|
Cisco Access Digital Trunk Gateway DT-24+ power cycle causes a call to fail.
|
Workaround: Reset the Cisco Access Digital Trunk Gateway DT-24+ device.
|
CSCdt87371
|
Transfer fails after system is online for a couple of days.
|
Workaround: Reboot system.
|
CSCdt90453
|
The Conference Bridge and the MTP do not run if the server does not have a device pool that points to the Cisco CallManager group that is configured as the highest priority in the Cisco CallManager.
|
The online help for the Cisco CallManager Administration for the Conference Bridge and MTP incorrectly states that you can choose one of the available device pools or select a device pool from the drop-down menu in the Device Pool field. Workaround: The documentation and online help have been corrected to read: Choose a device pool having the highest priority within the Cisco CallManager group you are using or choose Default.
|
CSCdt90457
|
After you restart the TCD, Cisco WebAttendent GUI misses directory numbers.
|
This occurs when Cisco WebAttendent is running on a winNT client machine with normal configuration.
Workaround: Close the Cisco WebAttendant window, and open a new one; all missed information will come back to normal.
|
CSCdt91509
|
A need exists for the dialing digits to exceed 24.
|
Workaround: Decrease the number of digits in the route pattern, so the dialed digits equal less than 24.
|
CSCdt95272
|
User cannot end process on backup.
|
When trying to end process on the backup utility, the utility never ends.
If you go into Task Manager and try to end process on Backup utility viewer, the system acts as if it ends process, but the process never ends. If you start the backup process again, you will see it never stopped.
Workaround: Ctrl-alt-delete may be used to stop programs but not services. Many services can be killed this way; however, it will leave the machine in an unreliable state. Go to "cancel backup" menu selection to shut down the backup.
|
CSCdt95739
|
Caller ID overwrites a call-parked number.
|
Workaround: No workaround exists.
|
CSCdu01040
|
With G729 codec, Unity never detects silence.
|
Workaround: No workaround exists.
|
CSCdu01080
|
Digital PBX Adapter (DPA) 7630 will not allow symbols in the password field.
|
DPA 7630 running 1.0(1.5) software allows the administrator to use symbols in the password field, such as (*&^%$#@!), but then will not accept the same symbols when trying to log into the DPA.
Workaround: None exists.
|
CSCdu06412
|
Cisco CallManager incorrectly interprets the disconnect cause.
|
Workaround: Use the route group that chooses local gateway.
|
CSCdu06749
|
Echo occurs over 6608 T1 gateway.
|
Echo using Cisco Catalyst 6000 8 Port Voice E1 or T1 and Services Module VoIP gateway occurs.
Workaround: To reduce echo you may adjust the "Audio signal adjustment into IP network," "Audio signal adjustment from IP network," and "Tx-level CSU" fields under the Cisco CallManager gateway screen.
|
CSCdu09364
|
Cisco WebAttendant screen does not fit on an 800x600 screen.
|
The scroll bars are missing on the screen.
Workaround: None exists.
|
CSCdu10456
|
Transfer succeeds after first party drops.
|
Workaround: No workaround exists.
|
CSCdu14186
|
Transferred outbound calls appear as inbound in CDR.
|
When a call to the PSTN is made from an IP phone (Cisco IP Phone 7960 in this case), it is recorded as outbound. If the call is then transferred to another IP phone the second portion of the phone call is recorded in CDR as an inbound call originating from the PSTN.
Workaround: None exists.
|
CSCdu16388
|
Using Netscape causes problems with add user and associate devices.
|
Using Netscape Navigator 4.7 can result in confusing and sometimes incorrect behavior when trying to add a new user through the ICS System Manager (Configure > Call Manager > User > Add a New User). Problem 1: You fill in the new user fields correctly. Then you click on Insert. The web page shows a blank page instead of indicating success. In this case the user is actually added. The only problem is that the display is confusing to the user. Problem 2: You add a user. Click on Modify User. Then click on Associate Devices. Do a Select Search for devices. Check one of the devices returned by the search. Then click on Update. Nothing happens. In this case the device selected is not associated with the user profile you are modifying.
Workarounds: Both of the above problems can be avoided by using Internet Explorer 5.
|
CSCdu17141
|
Call from callpark cannot be retrieved.
|
Workaround: No workaround exists.
|
CSCdu20404
|
No message displays to show the administrator if the user has been created or not in Cisco CallManager.
|
Using Netscape Navigator 4.7 can result in confusing display behavior when trying to add a new user through the ICS 7700 System Manager (Configure Call Manager > User > Add a New User). Using an incorrect Manager's UserID causes Netscape to display a blank page after clicking the Insert button. It should display an error message. Giving a blank or correct Manager's UserID causes Netscape to display a blank page after clicking the Insert button. It should display a successful completion message.
Workaround: Since the correct action is taken internally by the software in each case above, this is mostly just a user confusion problem. If the user wants to completely avoid this confusion, the user can use Microsoft Internet Explorer 5, which behaves properly in both of the cases above.
|
CSCdu21141
|
A lineAnswer returns SUCCESS, but state does not change.
|
Workaround: Use blind transfer or consult transfer instead of arbitrary transfer.
|
CSCdu23382
|
Route filters do not display in exported route plan reports.
|
Workaround: No workaround exists.
|
CSCdu27800
|
Cisco WebAttendant 3.0(3.42) is installed, and user cannot uninstall previous version.
|
Workaround: Manually remove previous Cisco WebAttendant directories, shortcuts, and registry entries.
|
CSCdu32422
|
Phone call is not forwarded as indicated in the parameter ForwardNoAnswerTimeout. There is a difference of 4 seconds. This unexpected behavior only occurs when this timer is set to 20 or greater.
|
ForwardNoAnswer timer expires earlier than expected.
If the ForwardNoAnswerTimeout is set to 20, the phone call will be forwarded (If it is not answered) after 16 seconds. If this timer is set to 24, the phone call will be forwarded after 20 seconds.
Workaround: None exists.
Note: The problem is resolved in Cisco CallManager Release 3.1 and beyond with more accurate timer component.
|
CSCdu32724
|
No audio on external transfer.
|
Making an arbitrary transfer of two outside calls results in the two calls being connected but there is no media setup. The two parties cannot hear one another.
Workaround: Use a consult transfer.
|
CSCdu38419
|
H.245 packet precedence is not set properly.
|
This only occurs when the TCP connection is attempted. Once the TCP connection is established, the precedence bit is set properly on all H.245 messages.
Workaround: None exists.
|
CSCdu42536
|
Windows 2000 appears to freeze when installing on some IBM xSeries 330s, but it is actually just installing slowly.
|
Workaround: You can wait for about an hour for the install of Windows 2000 to complete. You can also select F8 upon boot up and choose Enable Boot Logging. Problem is not consistently reproducible.
|
CSCdu42662
|
Cisco CallManager does not start if you enter DNS suffices.
|
At system server page, the server configuration does not accept full name (name with DNS suffix such as callmg09.Cisco.com). CallManager will have no heart beat after rebooting.
Workaround: Use just host name such as callmg09 or IP address instead of full DNS name, callmg09.Cisco.com.
|
CSCdu45086
|
"m_DropPending" flag does not clear after it is set by lineDrop request.
|
If a lineDrop() on a call causes the call to go to the DISCONNECTED state, instead of the IDLE state, and you try to call lineDrop() again on that same call, the second lineDrop() request will fail and you may never be able to drop the call.
The problem would not occur under normal working situations. This problem was actually found because of a bug in the CTI code.
Workaround: Call lineDeallocateCall() on the call to get rid of it.
|
CSCdu45966
|
Audio cut-through delay on PSTN transfer from CTI port.
|
There is a three-second delay in the audio stream being cut through on calls transferred to or from the PSTN through an H.323 gateway.
Workaround: None exists.
|
CSCdu46744
|
Cisco CallManager holds memory during a high volume of calls.
|
During a scalability test a call volume of approximately 40000 calls per hour are originated from a Callgen router ( simulating IP phones) and terminated set of Callgens. If some calls are not answered, a memory leak is seen to occur. Over one 10 hour test, 950 megabytes of memory are used. After 4 additional hours with no call activity the memory has not been freed. Calls are simulated IP phone to IP phone. The leak is occurring when calls are not answered.
Workaround: None exists.
|
CSCdu47097
|
"MwiSearchSpace" parameter value truncated upon upgrade.
|
The MWISearchSpace parameter value for the messaging interface was truncated to 128 characters.
Workaround: None exists, or use value less than 128 characters.
|
CSCdu54108
|
Cisco WebAttendant does not start if WAUSERS share is down.
|
Workaround: Your server has to fail back before your Cisco WebAttendant will work properly.
|
CSCdu58609
|
Modifying route list parameter within existing route pattern fails.
|
Workaround: Restart the Cisco CallManager service.
|
CSCdu61188
|
H.323 calls do not provide tone on hold.
|
No tone on hold occurs when call is via H.323 trunk, but works with pri.
Workaround: None exists.
|
CSCdu62484
|
Cisco WebAttendant screen is not refreshing line updates for users.
|
Cisco WebAttendant screen is not always updating the line status of the phones.
Workaround: None exists.
|
CSCdu64285
|
Cisco CallManager stops writing to Cisco CallManager trace and event application log.
|
Workaround: None exists.
|
CSCdu69819
|
Phone with two identical DNs may have transfer problem.
|
If customer has a phone with two lines that have the same number but are in different partitions, when one line has one call active and another on hold and there is a call coming in to the second line, the transfer button might be disabled on this second line incorrectly.
Workaround: Do not create phones that have two lines with the same DN but different partitions until this bug is fixed.
|
CSCdu71087
|
Setting LINETRANSFERMODE_CONFERENCE in completeXfer should fail.
|
Application sends lineCompleteTransfer() with dwTransferMode set to LINETRANSFERMODE_CONFERENCE. This request should fail because LINETRANSFERMODE_CONFERENCE is not supported by the TSP. But, the request succeeds and the operation is treated like a transfer which is incorrect.
Workaround: Application should never set the dwTransferMode to LINETRANSFERMODE_CONFERENCE since it is not supported by the CiscoTSP.
|
CSCdu71551
|
Administrator cannot reset phones from Cisco CallManager Administration.
|
Administrator cannot change the forwarding information for IP phones or reset phones through the GUI interface.
Workaround: Reset phones manually. None exists for changing forwarding information.
|
CSCdu77516
|
Failure response from lineUnHold when consult call is offering.
|
"lineUnhold() " returns a negative response after a lineSetupConference() and before the consultation call is answered, even though the call is successfully retrieved.
Workaround: None exists.
|
CSCdu78398
|
A shared line goes off hook instead of primary line.
|
When the phone goes off hook it uses the shared line appearance instead of its primary line.
Workaround: Have the user press the primary line button before dialing.
|
CSCdu79328
|
Software conferencing stops working until IP Voice Media Streaming App restarts.
|
Users get message "No Conference Bridge Available" when attempting to conference in other users.
This can occur if you are using the software conference bridge, and it has been running for some time.
Workaround: The only way to resolve this problem is to stop/start the "IP Voice Media Streaming App" service from Call Manager Control Center
|
CSCdu83844
|
Devices do not register correctly after quick cluster reboot.
|
Workaround: Manually reboot or power cycle the devices.
|
CSCdu86461
|
No translation when DN is unregistered (gets wrong mailbox).
|
PSTN caller gets incorrect voice-mail box This may occur when called IP phone DN is un-registered, and translation pattern to that DN exists.
Workaround: None exists.
|
CSCdv01110
|
CTI does not send IDLE event after unhold failed by Cisco CallManager.
|
Unhold call request fails after unsuccesful consultWithOutMedia attempt.
Workaround: Workaround is implemented in JTAPI. It clears the connection in the disconnect method if it fails with INVALID_CALL_STATE. That "unlocks" CTIPort.
|
CSCdv03481
|
One-way audio occurs when doing CTI transfer.
|
When using a CTI application to transfer a call, a race condition can occur where a Cisco CallManager does not wait long enough for an OpenLogicalChannelAck leading to the following error message in the Cisco CallManager trace: AgenaInterface::OpenLogicalChannelAck error: ParentPid not match .
Workaround: None exists.
|
CSCdv10611
|
One-way audio on outbound calls when MTP is enabled
|
When hardware MTP is used, outbound calls from IP phone have one-way audio.
Workaround: Remove MTP.
|
CSCdv13266
|
Software conference bridge uses different RTP send/recv port breaks using NAT/PAT.
|
When using the software conference bridge or media termination point ,two different UDP/RTP ports are used, one for the TX side and another for the RX side.
This will cause problems when trying to route the RTP packets through a NAT gateway.
Workaround: None exists.
|
CSCdv15124
|
Media_SilenceSuppression value sent to phone is invalid.
|
Silence Suppression starting in calls when it is disabled.
Workaround: None exists.
|
CSCdv15163
|
SJCLSTR2D crashed when it ran out of memory.
|
Cisco CallManager may crash after consuming all of its virtual memory.
Workaround: None exists.
|
CSCdv17783
|
With shared line appearance, user cannot resume call placed on hold from another phone.
|
Workaround: Hit resume before picking up the handset.
|
CSCdv22744
|
ToneOnCallForward parameter gives one quiet beep.
|
When a customer sets "ToneOnCall Forward" parameter to true, he misses hearing the tone because it is so brief.
Workaround: None exists.
|
CSCdv26354
|
Cisco WebAttendant should NOT allow two or more lines with same DN on agent phone.
|
This might be the problem if Cisco WebAttendant agents cannot log in. This may occur when Cisco WebAttendant agents fail to login if their phones are configured with two lines that have the same directory number.
Workaround: Remove duplicate line entry.
|
CSCdv29094
|
Route loop restarts Cisco CallManager.
|
Workaround: Remove the Route Pattern from Cisco CallManager and/or PBX database.
|
CSCdv30394
|
Call.consult hit CCNException under call load.
|
Call.consult hits CCNException if there is a outstanding consult call on a line.
Workaround: None exists.
|
CSCdv31675
|
Wrong events are seen in one conference transfer scenario.
|
Workaround: None exists.
|
CSCdv31832
|
Conference parent handle missing in conference message
|
LINEDCALLSTATE_CONFERENCED message does not contain the conference parent handle when the conference has been set up manually using IP phones. The value is present if the conference was created programmatically (via lineSetupConference/lineAddToConference.)
Workaround: Identify the handle by examining the handle of the conference parent call itself. Implies control of that device.
|
CSCdv31832
|
Conference parent handle is missing in conference message.
|
LINEDCALLSTATE_CONFERENCED message does not contain the conference parent handle when the conference has been set up manually using IP phones. The value is present if the conference was created programmatically (via lineSetupConference/lineAddToConference.)
This occurred when the conference call was created manually using IP phones.
Workaround: Identify the handle by examining the handle of the conference parent call itself. Implies control of that device.
|
CSCdv32130
|
Call through VG200 gateway drops for JTAPI routing application scenario.
|
A call coming across VG200 gateway gets dropped if routing application waits beyond JTAPI Route select timeout before invoking "routeselect."
Workaround: None exists.
|
CSCdv34425
|
CMI LTN fails to increment when route group device uses port All.
|
When adding devices to a route group, users have the choice of port "All" or "1". If port "All" is selected and the route group is used for SMDI integration, then the CMI service sends LTN 0001 for all route group members. This causes SMDI integration to fail.
Workaround: Delete all devices from the route group and re-add them using port "1".
|
CSCdv36262
|
User login.asp does not accept the "/" character in the user name.
|
LINEDCALLSTATE_CONFERENCED message does not contain the conference parent handle when the conference has been set up manually using IP phones. The value is present if the conference was created programmatically (via lineSetupConference/lineAddToConference.)
The occurs when conference call was created manually using IP Phones.
Workaround: Identify the handle by examining the handle of the conference parent call itself. Implies control of that device.
|
CSCdv37532
|
On Cisco CallManager Administration window, the IP phone accepts the alpha characters for phone number attribute.
|
Cisco CallManager should throw an exception.
Workaround: None exists.
|
CSCdv37562
|
Admin cannot modify/add user if the Cisco CallManager is unplugged from the network.
|
This occur when network cable is disconnected from Cisco CallManager.
Workaround: Restore the network cable connection and add user.
|
CSCdv41896
|
Cisco CallManager sends an open logical channel message to the IP phone and gateway with an all-zero RTP address. The gateway then tries unsuccessfully to send voice traffic to 0.0.0.0.
|
This occurs when the user gets no-way audio when calling between analog phones on a PBX and IP phone.
Workaround: Restarting the Cisco CallManager temporarily fixes the problem, but it has resurfaced after a few days.
|
CSCdv43780
|
MCS Backup Utility does not have low priority by default.
|
By default, the MCS Backup Utility is installed with the process priority set to medium. In at least one case, this has caused the Cisco CallManager process to stop because of heavy processor utilization. (CSCdv34316).
Workaround: In the Backup Utility Configuration application, select Performance tab, and set the Priority to Low.
|
CSCdv44292
|
Cisco CallManager Backup Utility does not clear CDR and Cisco CallManager .DMP fails after backup.
|
Cisco CallManager available hard drive space diminishes over time.
Workaround: If hard drive space is at a premium, the CDR.DMP and CCM030x.DMP files may be removed once the MCS.TAR / MCS.STI file has been physically backed up and verified.
|
CSCdv46861
|
Meetme Conf does not end after call transferred into it from Unity
|
A call, whether from the PSTN or internal that joins a Meetme conference by being transferred from a Unity Call Handler prevents the MeetMe conference from closing when all parties have left the conference. The bridge remains up and anybody can call the bridge number and join the conference.
Workaround: None exists.
|
CSCdv46861
|
MeetMe conference does delete after a call is transferred into it by Cisco Unity.
|
A call, whether from the PSTN or internal, that joins a MeetMe conference by being transferred from a Cisco Unity Call Handler prevents the MeetMe conference from being destroyed when all parties have left the conference. The bridge remains up and anybody can call the bridge number and join the conference.
Workaround: None exists.
|
CSCdv49164
|
Subscriber install does not work with special characters in password.
|
When installing C isco CallManager Release 3.0(8) from CD, the subscriber install does complete if the passwords for the administrator and SQL SA accounts contain special characters such as "=" or "/." A message indicates that the subscriber could not authenticate successfully to the publisher.
Workaround: Change the administrator and SA passwords, so they do not contain special characters on the publisher.
|
CSCdv54488
|
Transfer button intermittently fails to work.
|
When the user pushes the Transfer button, it does not provide a secondary dial tone, and you can still hear the user on the line.
Workaround: None exists.
|
CSCdv55707
|
The DEFAULT column of ccmGroup table is incorrect.
|
The value of this column is 0 for Non-Default groups.
Workaround: None exists.
|
CSCdv55720
|
TimeZoneOffset of CMLocal is incorrect.
|
It returns 0 but the correct value should be -8.
Workaround: None exists.
|
CSCdv55900
|
Voice-mail ports are not handled correctly during a voice-mail port failure.
|
If the first configured voice-mail port (the voice mail pilot number) is not currently registered to Cisco CallManager for any reason and a phone rolls as call forward busy or call forward no answer to voice mail, the VoiceMailMaximumHopCount service parameter setting is not honored. Instead the ForwardMaximumHopCount service parameter will be used. If the ForwardMaximumHopCount is set to a number less than the total number of configured voice mail ports, the calling party may receive a reorder tone even if there are available voice-mail ports.
Workaround: Increase ForwardMaximumHopCount value to match the number of configured voice-mail ports or 50, whichever is the lesser value.
|
CSCdv56339
|
The Cisco WebAttendant version number is not correct on the Cisco WebAttendant interface.
|
If you look at the product version of the Cisco WebAttendant plugin download, it is 3.0(12.0). But on the Cisco WebAttendant interface setting, the version is 3.0(10.0).
Workaround: None exists.
|
CSCdv57272
|
Calls to ICM do not work without JTAPI bounce after Cisco CallManager updates.
|
Agents can no longer log into their phone.
This occurs because the CTI layer in the Cisco CallManager is not informed of changes on the lines of the phones when the agents try to log in their new lines the Cisco CallManager.
Workaround: Stop and Start the JTAPI process.
|
CSCdv58415
|
Calls route to the incorrect pilot point hunt group.
|
Calls destined for the members of a pilot point hunt group are incorrectly routed to the members of another pilot point hunt group.
Workaround: Restart the telephony call dispatcher services.
|
CSCdv58770
|
Updating the translation pattern causes the Cisco CallManager to reset.
|
Numerous translation patterns (750 ) using the @ symbol cause the Cisco CallManager to hang while performing digit analysis when trying to add new patterns or update existing patterns.
Workaround: Perform changes only once a day during non-peak hours. This still causes the Cisco CallManager to reset, but has less impact to users.
|
CSCdv60233
|
User admin page does not query userid added by AD.
|
After installing AD plug-in, the User admin page cannot query the user by userid. The userid is added by active directory users and computers. Duplicate by the following steps: Add a user from AD server with the following:
User Name abc
Last Name def
Userid xyz
From CCMAdmin, go to User and Global Directory page
Enter xyz for the basic search
Result: No records found matching your query
Workaround: None exists.
|
CSCdv61222
|
Unanswered blind tranfer is charged twice.
|
Blind transfer calls which are unanswered get charged for even the failed call length.
This occurs only when the blind transfer is attempted by the called party. It does not happen when the calling party is involved in the transfer.
Workaround: None exists.
|
CSCdv61441
|
MCS Backup utility should back up hosts file in addition to LMHOSTS.
|
The MCS Backup utility that ships with Cisco CallManager currently makes a backup of the LMHOSTS file on the server that is being backed up; however, it does not backup the hosts file.
Workaround: Manually rebuild the hosts file after a restore, or manually do a backup of the hosts file in case a restore is needed.
|
CSCdv61446
|
A need exists for Cisco CallManager install to check for primary DNS suffix before the install occurs.
|
On a Cisco CallManager, if you right click on My Computer, click Network Identification tab, click Properties, click more.... The Primary DNS suffix of this computer should be blank. Having anything in this space could cause install problems. The install wrapper should check this field before allowing Cisco CallManager to be installed.
Workaround: Remove anything in the primary DNS suffix prior to installing Cisco CallManager.
|
CSCdv63172
|
User cannot drag and drop the dial button on speed-dial numbers.
|
If you drag the dial button and drop it on any speed dial number, the function does not work. It works the first time after the speed-dial button was assigned a DN number. Next time the SL line of the Cisco WebAttendant goes off hook and does nothing.
Workaround: Drag the speed-dial button and drop on the dial button.
|
CMTerminals -- Firmware
|
|
CSCdr53488
|
Cisco IP Phone 7960 did not work after a Cisco CallManager was stopped and then restarted after about a 30 minute interval.
|
Workaround: Using the **#** reset sequence on the phone brings it back into operation.
|
CSCdr55189
|
Cisco IP Phone 7960 takes 7min to work if pvid of phone is not equal to pvid of Cisco CallManager.
|
Workaround: No workaround exists.
|
CSCdt40012
|
DE 30+ loses D Channel under stress.
|
This occurs when SimClient is calling into back-to-back DE-30s towards an IVR.
SimClient makes 29 calls. The 30th call is made manually.
Workaround: None exists.
|
CSCdu44028
|
Cisco IP Phone 7960 causes slow response when connected to a 10MB NIC card. This problem only occurs when the PC port is running at a different speed from the SW port.
|
Workaround: No workaround exists.
|
CSCtr84167
|
When you enable the service parameter "Block Offnet to Offnet Transfer" and make a blind transfer with Cisco Unity Connection, the Q.931 SETUP message which CUCM sends to the PSTN gateway for an outbound PRI call still reaches the gateway. This transfer results in a dropped call.
|
Workaround: No workaround exists.
|
Feedback
