67
Release Notes for Cisco CallManager Release 3.0(10)
78-13493-02
Open Caveats
CSCdr39493
You cannot assign the same extension to a Cisco Catalyst 6000 24 Port FXS Analog
Interface Module and a Cisco IP phone.
Workaround: No workaround exists. For Cisco CallManager Release 3.0, only
MGCP gateways (VG200s) allow FXS ports to share the same phone number with a
Cisco IP phone. This release does not support shared-line capability for other analog
gateways in this release.
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.
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.
CSCdr53720
Transfer from Cisco uOne to busy phone without forwarding does not complete.
Workaround: Have phones forward on busy to voice mail.
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.
Table 8
Open Caveats for Cisco CallManager Release 3.0(10) (continued)
DDTS number
Description
