Cisco CallManager Release 3.0(10 Specification
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Software
  5. CallManager Release 3.0(10
  6. Specification
Cisco CallManager Release 3.0(10 Specification

Cisco CallManager Release 3.0(10 Specification

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Release Notes for Cisco CallManager
Release 3.0(10)
Original CCO appearance: June 20, 2001
Revised: July 2, 2001
These release notes describe the new features and caveats for Cisco CallManager
Release 3.0(10).
For a list of the open and resolved caveats for Cisco CallManager Release 3.0(10),
see
"Resolved Caveats" section on page 20
and
"Open Caveats" section on
page
64. These release notes are updated every maintenance and major release.
Use these release notes in conjunction with the Installing Cisco CallManager
Release 3.0(10) document, located on Cisco Connection Online (CCO), and the
Cisco Documentation CD-ROM. The Installing Cisco CallManager Release
3.0(10) document is also packaged with your CDs or convergence server.
Access the latest software upgrades and release notes for Cisco CallManager
3.0(10) on Cisco Connection Online (CCO) at
http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr.
Corporate Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Copyright © 2001. Cisco Systems, Inc. All rights reserved.

Advertisement

Table of Contents
loading

Related Manuals for Cisco CallManager Release 3.0(10

Summary of Contents for Cisco CallManager Release 3.0(10

  • Page 1 Revised: July 2, 2001 These release notes describe the new features and caveats for Cisco CallManager Release 3.0(10). For a list of the open and resolved caveats for Cisco CallManager Release 3.0(10), “Resolved Caveats” section on page 20 “Open Caveats” section on page 64.

  • Page 2: Table Of Contents

    Obtaining Technical Assistance, page 102 • Introduction Cisco CallManager, a network business communication system, provides high-quality telephony over IP networks. Cisco CallManager enables the conversion of conventional, proprietary, circuit-switched PBXs to multiservice, open LAN systems. Release Notes for Cisco CallManager Release 3.0(10)

  • Page 3: System Requirements

    System Requirements System Requirements Make sure Cisco CallManager Release 3.0 is installed and configured on a Cisco Media Convergence Server. You may also install Cisco CallManager on a Cisco-approved Compaq server configuration or a Cisco-approved IBM server configuration. The installation will not complete if you do not follow the exact configuration.

  • Page 4: New And Changed Information

    Software License Agreement • New and Changed Information New Software Features for Release 3.0(10) Cisco CallManager Release 3.0(10) adds features and provides additional workarounds to open caveats and resolves caveats. Refer to “Resolved Caveats - Release 3.0(10)” section on page “Open...

  • Page 5: Backup Utility

    Utility restores those files as well, but all current back ups are saved as a .sti extension. Important Notes for Release 3.0(10) Compatibility Matrix Table 1 lists versions with which Cisco CallManager 3.0(10) has been tested. Table 1 Compatibility Matrix Component/Application Version Tested Cisco Unity 2.4.6.102...
  • Page 6 Cisco CallManager Release 3.0(9). User Interface Enhancement A new configuration parameter check box exists on the Cisco CallManager Administration H.323 Gateway Configuration Web page. This allows a H.225D to "run on every node.” If you select this option (by default it is on), theH.225D runs on every node.
  • Page 7 The following sections contain new and changed software features in Cisco CallManager Release 3.0(8). Strong Encryption Cisco CallManager Release 3.0(8) contains low encryption (56-bit or less) in all of its components. Access the Download Cryptographic Software link from the main CCO download location at http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr for...
  • Page 8 New and Changed Information New Software Features in Release 3.0(7) Cisco CallManager Release 3.0(7), a maintenance release, adds no new features. Refer to the “Resolved Caveats - Release 3.0(7)” section on page 47 for more information. Important Notes for Release 3.0(7)
  • Page 9 New and Changed Information Cisco IP Phone 7910 and Cisco IP Phone 7940 Compatibility Issue Cisco IP Phone 7910 and Cisco IP Phone 7940 are only supported by Cisco CallManager Release 3.0(5a) and higher. If you are running an earlier version, you must upgrade to a later version at http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr.
  • Page 10 New and Changed Information Tech Prefixes Cisco CallManager Release 3.0(6) supports tech prefixes in the Gatekeeper. To properly configure the Cisco CallManager to register with a tech prefix you must go to service parameters and perform the following steps: Choose Cisco CallManager.
  • Page 11 Release 3.0(5a) of Cisco CallManager. Support for New Cisco IP Phones These new phone models, Cisco IP Phone 7910, Cisco IP Phone 7910-SW+, and Cisco IP Phone 7940, broaden the product line of Cisco IP phones. Cisco IP Phone 7910—This is a single-line Cisco IP Phone with the •...
  • Page 12 New and Changed Information Cisco IP Phone 7940—This is a two-line Cisco IP Phone with the following • features: Line buttons assignable as either lines or speed dials – Pixel-based display – Four soft keys with context-sensitive features – Five fixed function buttons (Messages, Services, Information, Directory, –...
  • Page 13 Cisco IP Phone Services on Cisco Pixel-Based Display Phones Cisco IP Phone 7940 and Cisco IP Phone 7960 have an HTTP client with an XML parser. When a user presses the Services fixed-function button, the HTTP client will attach to a preconfigured (by the administrator) URL. This URL will display a menu of available HTML/XML services for the user.
  • Page 14 XML API. Corporate Directory Dialing from Cisco IP Phones The Cisco IP Phone 7940 and Cisco IP Phone 7960 display a menu of directories when a user presses directories. When the user selects Corporate Directory from the menu, the phone presents the option of specifying characters to find the destination user’s first name, last name, or directory number.
  • Page 15 Cisco VG200 FXO ports attached to PBXs. The NetVision Phones issue H.245 messages through the Cisco CallManager to Cisco VG200 FXO gateways on initiation by the user of PBX functions. The Cisco VG200 gateway interprets the signals and translates them to an FXO hookflash followed by a PBX-specific feature code.
  • Page 16 Cisco IP Phone Services Configuration—This new page enables • administrators to add, modify, or delete Cisco IP Phone services to which users can subscribe to at their site. To access this page from the main Cisco CallManager Administration page, select Feature > Cisco IP Phone Services.
  • Page 17 Computer Telephony Integration Computer Telephony Integration serves as the base interface to Cisco CallManager for TAPI and JTAPI applications as well as direct CTI applications such as Cisco WebAttendant. Cisco CallManager 3.0(5a) allows you to control CTI application usage on a per-user basis. You can enable CTI application use for a particular user by browsing to entry in the User->Global...
  • Page 18 The Cisco IP Interactive Voice Response System typically opens several CTI route points and CTI ports; it will always open a single CTI connection to a Cisco CallManager in the cluster. The 400 connection limit applies to the CTI connection and not the CTI ports or route points.
  • Page 19 Cisco CallManagers in the new cluster. You must also configure the new cluster with intercluster trunks to all of the Cisco CallManagers in the existing clusters.

  • Page 20: Resolved Caveats

    Caveats that were resolved in Cisco CallManager Release 3.0(10). Note If you have an account with Cisco.com (Cisco Connection Online), you can use the Bug Toolkit to find caveats of any severity for any release. To access the Bug Toolkit, log on to http://www.cisco.com/support/bugtools.
  • Page 21 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCds43704 Call looping uses CPU and other A Cisco CallManager code change fixes resources in Cisco CallManager. this problem. CSCds74822 Service Configuration application does A Cisco CallManager code change fixes not function properly.
  • Page 22 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt42403 User loses a call after transferring A Cisco CallManager code change corrects toward a busy line. this behavior. This item duplicates CSCdt45632, CSCdt82239, and CSCdr58998.
  • Page 23 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt71276 Backing up Media Convergence Server The priority of the backup engine was takes about 50 minutes; in previous reduced, so it does not interfere with the versions, this took much less time.
  • Page 24 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt75620 A need exists for TAPI dwCalledID to A code change ensures that TAPI reflect original called party. dwCalledID reflects the original called party. CSCdt75990 Calls with compatible regions and A code change resolves this behavior.
  • Page 25 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt83902 User cannot answer a consult transfer. The fix releases the answer thread when applications invoke an answer request on a consult call that is cleared due to transfer.
  • Page 26 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt94077 Device tables do not update correctly Calls going out through a digital gateway after failover occurs. were being dropped after one Cisco CallManager in a cluster fails in a...
  • Page 27 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdt96338 The simultaneous call limit for H.323 Intercluster calls stop at 248 active calls per device equals 248 when it should be H.323 device. A code change allows 360 360.
  • Page 28 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdu04286 After conferencing, if only two parties A Cisco CallManager code change corrects are left in the conference, TAPI redirect this behavior. causes both parties to be dropped instead of just the one doing the redirect.
  • Page 29 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdu10146 Locations bandwidth calculation is A caller initiates a call to a low bandwidth wrong with software conference and (30 KB) location with codec G.729. The codec change.
  • Page 30 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdu68211 The default SdlTraceTypeFlags value is The default value SdlTraceTypeFlags inadequate for debugging needs. changed to 0x00004B15. This change only occurs on new installs. On upgrade installations, the previous setting for the "SDLTraceTypeFlags"...
  • Page 31 Resolved Caveats Table 2 Cisco CallManager Release 3.0(10) Resolved Caveats (continued) DDTS Number Summary Explanation CSCdu18646 An unstable modem connection exists This version includes new loads that have through WS-X6608 and WS-X6624 been designed to provide V.34 connection gateways. speeds with a connection rate of 85 percent or higher.
  • Page 32 Table 3 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(9) If you have an account with Cisco.com (Cisco Connection Online), you can Note use the Bug Toolkit to find caveats of any severity for any release.
  • Page 33 CTI Framework shows up in phone Corporate Directory automatically filters Corporate Directory out special user "ctifw" when searched by name. CSCds63897 PerfMon CallsInProgress is inaccurate. A Cisco CallManager code change corrects this behavior. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 34 A Cisco CallManager code change corrects this behavior. CSCdt06744 Call forwarded via IVR does not show A Cisco CallManager code change added a forward information. service parameter to correct this behavior. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 35 When a new user is added on With the latest plug in schema files on Cisco CallManager 3.0(7) with Cisco CallManager 3.0(9), the plug in AD/NDS plugin, the user gets an error. works. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 36 MGCP request per endpoint. CSCdt43154 Migration from Cisco CallManager The Installing Cisco CallManager Release 3.0(4) to Cisco CallManager 3.0(7.2f) 3.0(8) and later documents now include the fails with large CDRs. information about removing large CDRs. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 37 Change of zone name in Gatekeeper The code now changes the gatekeeper zone, device requires the administrator to stop and the administrator uses the Reset and start the Cisco CallManager. Gatekeeper button to reset gatekeeper. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 38 Cisco CallManager. delayed and broken apart. The fragmented messages were coming from only one building. CSCdt82472 Hitting line button on a multiline phone A code change corrects this behavior. fails in some scenarios. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 39 Table 4 lists and describes caveats that were resolved in Cisco CallManager Release 3.0(8). If you have an account with Cisco.com (Cisco Connection Online), you can Note use the Bug Toolkit to find caveats of any severity for any release.
  • Page 40 CSCds69496 External Call Forward All loop causes Setting the CallManager Service Parameter high Cisco CallManager CPU usage. MaxForwardsToDn to 0 disables the cause of this problem. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 41 Caller ID mask on the gateway configuration web page, so the last redirecting or first redirecting numbers display in the “Calling Party” field of the ISDN primary setup message in the full E.164 format. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 42 InvalidStateException. corrected this problem. A Cisco CallManager code change cor- CSCdt13681 A directory number started returning rected this problem. busy to callers because too many calls had been forwarded to that number. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 43 By doing so, the Cisco CallManager continues to forward the call after the CTI application redirects the call to a new destination. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 44 This udp read thread was then trying to access Cisco Access Digital Trunk Gateway DT - 24+ data members that no longer existed in memory, thus causing a crash of Cisco CallManager. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 45 CO in the PSTN received it as available for new calls. CSCdt27581 User cannot delete partitions. This is an A Cisco CallManager code change fixed error but m_com_error was not valid. this caveat. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 46 ARP cache timeout. CSCdt62890 A deleted phone extension still exists in After you delete the phone, the extension no SQL database. longer appears in SQL database. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 47 Table 5 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(7) If you have an account with Cisco.com (Cisco Connection Online), you can Note use the Bug Toolkit to find caveats of any severity for any release.
  • Page 48 This value is now reported via the appropriate TLV in the CDP response in loads P004P301 (Cisco IP Phone 7910) and P003P301 (Cisco IP Phone 7960 and Cisco IP Phone 7940). Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 49 16. CSCds91718 Need exists to include CTI Messages in The default database was changed to default SDL trace setting. facilitate this problem. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 50 CcNotifyReq message, one more check needs to be added to make sure there is valid CI to route pattern association; otherwise it will crash the Cisco CallManager. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 51 Table 6 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(6) If you have an account with Cisco.com (Cisco Connection Online), you can Note use the Bug Toolkit to find caveats of any severity for any release.
  • Page 52 Slow SDL timer Service using call load Internal data structures that kept track of of 2.25 cps and IVR call information were not being cleaned up correctly which lead to some inefficiencies over time. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 53 CSCds61871 No error message occurs on The problem was corrected by using a timer unauthorized CTI user via TSP. to introduce a delay between sending the response and closing the pipe. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 54 CSCds66353 Cisco CallManager tells MGCP The Cisco CallManager software’s code gateway to use VAD when was modified to support SilenceSuppression is set to False. SilenceSuppression accordingly. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 55 CTI Application Use Enabled global flag. Thus, if a user has set the value of the global flag to true, the value would still be set to true after an upgrade. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 56 CSCds76640 State of Logout and Go Offline buttons This problem was solved by syncing up the does not change. TCD server and the Cisco WebAttendant. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 57 (such as voice mail configuration error or hop count exceeded). CSCds82156 Confusing screen occurs on auto The screen was changed to be read more upgrade when selecting clearly. publisher/subscriber is selected Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 58 Table 7 lists and describes Caveats that were resolved in Cisco CallManager Release 3.0(5a). If you have an account with Cisco.com (Cisco Connection Online), you can Note use the Bug Toolkit to find caveats of any severity for any release.
  • Page 59 The reason they do not connect is that the server name to an IP address will cause configuration file still contains the server phones not to boot. Auto-registering name. phones will not connect to Cisco CallManager. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 60 The target server’s name in DNS does not match the server’s machine name. CSCdr57242 OutofBandwidthText is not on by A call from a Cisco IP Phone to another default. Cisco IP Phone gets a reorder tone intermittently. Nothing on the phone display indicates the reason.
  • Page 61 Cisco IP Phone 7960 to NetMeeting Calls from a Microsoft NetMeeting client to G.711 calls without MTP have poor a Cisco 7960 IP phone result in poor audio audio quality. quality heard on the Cisco IP Phone 7960 side of the conversation. If the 'i' button is...
  • Page 62 ID was no longer unique. This would cause various timers to fail. The problem was identified and fixed. CSCds53566 Unable to unpause backup service in Automated Install fixed this problem for MCS backup utility Cisco CallManager 3.0(5a). Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 63 DBL trace files grow without bound if This problem occurred when the time limit number of minutes is not set. for trace is set to 0. Under these conditions, the trace file for the database layer is ignored. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...

  • Page 64: Open Caveats

    Workaround: Call the phone to update the phone status or go off-hook on the phone to update the status. CSCdr28947c 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.
  • Page 65 (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.
  • Page 66 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.
  • Page 67 DDTS number Description 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.
  • Page 68 Workaround: Use the preceding definitions instead of the definitions in the Cisco CallManager Administration Guide and online help. 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.
  • Page 69 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. CSCds14138 AVVID: A need exists for the automated install to allow reinstall option.
  • Page 70 CSCds42397 Terminal Services are nonfunctional. Workaround: This is a Microsoft limitation. CSCds46274 Cisco IP Phone 7960 user on G.729 call hears hiss after digit during IVR prompt. Workaround: No workaround exists. CSCds48200 Missing Disconnected, Established & TransferEnd in conference-transfer scenario.
  • Page 71 Workaround: Do not redirect the call back to the caller, which should not happen under normal circumstances 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.
  • Page 72 Call pickup does not pick up a call even when line is Call Forward All. Workaround: No workaround exists. 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.
  • Page 73 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>.
  • Page 74 Open Caveats for Cisco CallManager Release 3.0(10) (continued) DDTS number Description 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.
  • Page 75 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.
  • Page 76 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. CSCdt57230 Cisco CallManager upgrade adds extra ProcessNode for the same Cisco CallManager.
  • Page 77 Pilot number does not support redundancy. Workaround: No workaround exists. 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.
  • Page 78 CDR records are incorrect when recording conference calls. Workaround: No workaround 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.
  • Page 79 Call from callpark cannot be retrieved. Workaround: No workaround exists. CSCdu18827 A need exists for Cisco CallManager to support leading display character for Digital Multiplex System (DMS) protocol. Workaround: For the direction of IP phones to Nortel phones only, the display field on the line configuration for phones can be set up with a leading space that will fix the problem in one direction.
  • Page 80 Workaround: Stop and start the Cisco CallManager service on the recovered Cisco CallManager. CSCdu22012 Call forward from Cisco CallManager Admin allows user to enter an invalid number. Workaround: No workaround exists. CSCdu23382 Route filters do not display in exported route plan reports.
  • Page 81 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. CSCdu57794 If you have region names containing more than 32 characters, upgrading to Cisco CallManager 3.0(10) fails.

  • Page 82: Documentation Updates

    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 tele not equal to pvid of CM. Workaround: No workaround exists. CSCdt40012 DE 30+ loses D Channel under stress Workaround: No workaround exists.
  • Page 83 New Service Parameters Table 9 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0(5) Cisco CallManager Administration Guide or the online help for the Cisco CallManager application. Table 9 Cisco CallManager Service Parameter Updates...
  • Page 84 Alert message. This may enable a full duplex path before the Connect message is received on ISDN calls. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 85 0 and 7 and is represented as follows: 0 = routine 1 = priority 2 = immediate 3 = flash 4 = flashOver 5 = critical 6 = internet 7 = network Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 86 0 and 7 and is represented as follows: 0 = routine 1 = priority 2 = immediate 3 = flash 4 = flashOver 5 = critical 6 = internet 7 = network Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 87 If the performance value is set Note too high, phone registrations could slow the Cisco CallManager real-time response. If set too low, the total time for a large group of phones to register will be slow. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 88 “cause” during the release of the call, no re-routing to the next device in the route list is attempted and the call is released with the associated cause. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 89 AdvancedCallForwardHopFlag, allows the Cisco CallManager to select the next available voicemail port by skipping the busy or unregistered voicemail ports. Note VoiceMailMaximu mHopCount to the number of voice-mail ports in the system. Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02...
  • Page 90 Table 10 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0 Cisco CallManager Administration Guide or the online help for the Cisco CallManager application. Do not modify any defaults or settings of the following parameters...
  • Page 91 CMI Service Parameters Not Included in Release 3.0 Documentation ParamName Description BackupCallManagerName This parameter defines the names of the Cisco CallManagers that are going to be used for the CMI backup. You can use either the name of a Cisco CallManager or its IP address. BaudRate Cisco CMI connects to the voice mail system via an ETA/TIA-232 connection.
  • Page 92 However, some Octel systems periodically send an invalid DN specifically for the purpose of verifying that the attached Cisco CallManager is functioning properly. In this case, you can turn off ValidateDns if you know the DN that the Octel system will use as a keepalive.
  • Page 93 CMI Service Parameters Not Included in Release 3.0 Documentation (continued) ParamName Description Parity Cisco CMI connects to the voice mail system via an EIA/TIA-232 connection. This parameter defines that connection. Recommended default value: Even The parity settings can be None, Note Even, Odd, Mark, or Space.
  • Page 94 ParamName Description SsapiKeepAliveInterval During normal operations, CMI will be attached to a Cisco CallManager. When this is the case, CMI sends a keepalive message to the Cisco CallManager at the rate specified by this numeric parameter. Default value: 30 seconds...
  • Page 95 DN against the NumPlan table. This is an attempt to verify that the DN matches an existing DN known to Cisco CallManager. If the DN is not found in NumPlan, an invalid DN message is sent to the voice mailbox.
  • Page 96 Omissions This section contains lists of service parameters for the Cisco CallManager that were not included in the initial production of the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application. A later release of the document will define these parameters.
  • Page 97 Cisco CallManager Service Parameters The following list contains the service parameters, which can be configured for the Cisco CallManager service type, that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application: AlwaysUsePrimeLine •...
  • Page 98 Cisco TFTP Service Parameters The following list contains the service parameters, which can be configured for the Cisco TFTP service type, that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the Cisco CallManager application: AlternateFileLocation1 •...
  • Page 99 Cisco IP Voice Media Streaming Service Parameters The following list contains the service parameters, which can be configured for the Cisco IP Voice Media Streaming service type, that were omitted from the Release 3.0 Cisco CallManager Administration Guide and online help for the...

  • Page 100: Obtaining Documentation

    Incorrect Definition for HoldType and ToneOnHoldTime The definitions for the Cisco CallManager HoldType and ToneOnHoldTime service parameters are incorrect in the Cisco CallManager Administration Guide and online help for Cisco CallManager Release 3.0. The correct definitions are as follows: •...

  • Page 101: Ordering Documentation

    Obtaining Documentation World Wide Web You can access the most current Cisco documentation on the World Wide Web at the following sites: http://www.cisco.com • http://www-china.cisco.com • • http://www-europe.cisco.com Documentation CD-ROM Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product.

  • Page 102: Obtaining Technical Assistance

    Obtaining Technical Assistance Documentation Feedback If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
  • Page 103 P4—You need information or assistance on Cisco product capabilities, • product installation, or basic product configuration. In each of the above cases, use the Cisco TAC website to quickly find answers to your questions. To register for Cisco.com, go to the following website: http://www.cisco.com/register/...
  • Page 104 ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That’s Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST,...

This manual is also suitable for:

Callmanager release 3.0

Table of Contents