Table Of Contents
Release Notes for Cisco CallManager Release 2.4(4)
June 23, 2000
These release notes describe the new features and caveats for Cisco CallManager Release 2.4(4). Use these release notes in conjunction with Installing Cisco CallManager Release 2.4 on the Cisco Media Convergence Server, the Cisco Voice Products documentation located on Cisco Connection Online (CCO), and the Cisco Documentation CD-ROM.
These release notes discuss the following topics:
Cisco CallManager is a network business communication system providing high-quality telephony over IP networks. Cisco CallManager enables the conversion of conventional, proprietary circuit-switched PBXs to multi-service, open LAN systems.
This section lists the system requirements for installing Cisco CallManager.
Minimum Hardware Requirements
Note The following system hardware requirements are for systems with 50 phones or less. Systems with more phones require a faster processor.
•Pentium 166 MHz processor
•128 MB RAM
•TCP/IP protocol installed and configured
•Monitor and display adapter capable of 256 colors at 800x600 resolution
Recommended Hardware Requirements
•Pentium 300 MHz processor
•256 MB RAM
•2 GB hard drive
•Windows NT 4.0 Server
•Windows NT Service Pack 5
•Internet Explorer 4.01 Service Pack 1 or higher (This is required even if you plan to use Netscape as your Web browser for Cisco CallManager.)
•Microsoft Data Access Components 2.0 Service Pack 1
•Microsoft Option Pack 4.0, IIS 4.0
•(Optional) If Microsoft Office 97 is installed, the SR2 patch to Microsoft Office 97 Professional must also be installed.
Minimum Requirements for the Cisco Access Digital Gateway DT-24+/DE-30+
A Channel Service Unit (CSU) is required if the Cisco Access Digital Gateway is connected to a telecommunications company or ISDN PRI demarcation point. If the gateway is connected to a PBX, a CSU may be required depending on the cable length. Consult the PBX documentation for maximum length requirements for connections without CSU support.
Determining Your Software Release
To determine the software release and version number of Cisco CallManager currently running on your system, perform these steps:
Step 1 Select Start >Programs>Cisco CallManager >CallManager Administration.
Result: The Welcome screen is displayed.
Step 2 Select About.
Result: The software release version is displayed. You can click the Details button to learn more information about the software release numbers.
This section contains information about installing Cisco CallManager Release 2.4(4) from the Cisco Connection Online (CCO) software download site and upgrading it to a more recent release. For a complete description of Cisco CallManager, see the appropriate online documentation for your release of the software.
Note These instructions only apply to installations and upgrades from the Cisco Connection Online (CCO) software download site. Refer to Installing Cisco CallManager Release 2.4 on the Cisco Media Convergence Server for instructions on how to install and configure Cisco CallManager Release 2.4(4) on a Cisco Media Convergence Server.
Perform the following steps to download and install the Cisco CallManager software:
Step 1 Download the Cisco CallManager executable file to your hard drive. Make note of the location where you save the downloaded file.
Step 2 If you are upgrading a previous release of Cisco CallManager, make a backup copy of the database file SelsiusData.mdb. Then stop all Cisco CallManager processes. For instructions on starting and stopping Cisco CallManager, refer to the appropriate online documentation for your current release of the software.
Step 3 Before starting the installation, review the latest release notes for information about system requirements, caveats, new features, and enhancements.
Step 4 Double-click on the downloaded Cisco CallManager executable file to begin the installation. Follow the online prompts.
Note If you want to use any optional components such as a Conference Bridge, you must install the appropriate Plug-In software during installation of Cisco CallManager. Even if you are performing an upgrade of a system that already has the optional Plug-Ins installed, you must install them again to pick up the latest changes in the new release of the software.
New and Changed Information
This section lists the features that are new or have changed for Cisco CallManager, up to and including Release 2.4(4).
DtSilenceFlag Default Setting Changed to 0 (Disabled)
The DtSilenceFlag setting in the Cisco CallManager scm.ini file controls whether or not silence is sent while a caller waits for the phone to be answered at the other end. When it is set to False (disabled), the audio stream is sent on call proceeding instead of waiting for a connect from the other end. When it is set to True, silence is sent until a connect is received from the phone at the other end. For Cisco CallManager Release 2.4(4), the default setting for DtSilenceFlag has been changed to 0 (disabled).
There is, however, one side effect that occurs when DtSilenceFlag is set to 0 (disabled). When DtSilenceFlag is disabled and you are calling an analog phone, you may hear loopback (echo) of your audio until the phone on the other end is answered.
To eliminate this echo, you can change the default setting of DtSilenceFlag to 1 (enabled).
Caution Setting DtSilenceFlag to 1 (enabled) can result in one-way audio on 911 calls, depending on the local carrier's configuration of the Central Office switch. The problem will only occur if the 911 switch fails to send a connect. If the 911 switch fails to send a connect, the calling phone continues to send silence, and the audio stream from the calling phone is never sent.
Therefore, it is strongly recommended that you schedule a test 911 call with your 911 service provider to verify that this problem does not occur. The test scenario should include the following steps:
1. Schedule a test call with your 911 service provider during off-peak hours.
2. Make sure that the test call will be routed over a Cisco Access Digital Trunk Gateway.
3. Enable the DtSilenceFlag parameter.
4. Make the 911call.
5. If the 911 operator can hear you, the test is passed, and you can leave the DtSilenceFlag setting enabled. If not, disable it immediately.
Perform the following steps only if you wish change the default setting of DtSilenceFlag to enable sending of silence:
Step 1 Open Notepad or WordPad (or any other text editing application).
Step 2 Browse to the scm.ini file on the CallManager server and open it. If you accepted the default location during installation of Cisco CallManager, this file will be located in C:\Program Files\Cisco\Bin.
Step 3 Locate the following line:
DtSilenceFlag=0 ; 0 = disable silence
Step 4 Change the setting from 0 to 1. The line should now read:
DtSilenceFlag=1 ; 0 = disable silence
Step 5 Save your changes and close the text editor.
DtSilenceFlag is set to 1, and silence is enabled.
Admission control helps maintain a desired level of voice quality over a network link by limiting the number of calls that can be active on that link at any one time. Using Cisco CallManager Administration, you can specify the total amount of bandwidth allocated for voice communications over each link in your network, thus limiting the number of calls allowed on each link. Admission control applies only to networks with a hub-and-spoke (or star) topology. Admission control does not guarantee a particular level of voice quality.
Audio Levels and Echo on Cisco Access Digital Gateway DT-24+/DE-30+
When using a Cisco Access Digital Gateway DT-24+/DE-30+, callers on the PSTN side of the connection might sometimes hear echo. You can reduce or eliminate this echo by adjusting the audio levels (pad settings) for the gateway.
Note If the echo problem is not on the PSTN side of the connection, do not change the default pad settings on the Cisco Access Digital Gateway DT-24+/DE-30+.
Possible causes of the echo are:
•The transmit level (outbound) audio from the gateway is too high (hot).
•The receive level (inbound) audio from the PSTN is too high (hot).
You should adjust the audio levels on the Cisco Access Digital Gateway DT-24+/DE-30+ only if callers on the PSTN side of a connection are experiencing an echo problem. Cisco recommends that you use a telecom test set on the PRI to verify that the audio levels are indeed out of telco specification, and then add gain or loss accordingly. If you do not have the appropriate test equipment, or if you do not have expertise with such equipment, you can try different pad settings and make test calls until the echo is reduced to an acceptable level on the PSTN caller side.
Note Do not adjust the audio levels of the Cisco Access Digital Gateway DT-24+/DE-30+ if your test equipment indicates that the trunk line from the central office is out of specification or if callers are experiencing echo only when connected to a particular central office or PBX. In both these cases, have your central office make the appropriate adjustments to the audio levels on the ISDN PRI.
Adjusting the audio levels on the Cisco Access Digital Gateway DT-24+/DE-30+ requires the following software:
•Cisco CallManager release 2.3 or 2.4
•Cisco Digital Access load file D003G024.bin
•Cisco DickTracy utility
Default pad settings for the D003G024 load are:
To adjust the audio levels on the Cisco Access Digital Gateway DT-24+/DE-30+ using the DickTracy utility, perform the following steps:
Step 1 If you are working with a Cisco CallManager release prior to 2.4(2b), copy the gateway load file D003G024.bin to the Cisco\TFTPPath folder.
Step 2 Using Cisco CallManager Administration, set the Load ID to D003G024 for the Cisco Access Digital Gateway DT-24+/DE-30+ in question. Then click Reset for that gateway.
Step 3 Allow the gateway time to re-register with Cisco CallManager, then use the Microsoft Performance Monitor to verify that the gateway has registered.
Step 4 If the DickTracy utility is not already installed on the server where Cisco CallManager is running, copy the file DickTracy.exe from Cisco CallManager release 2.4(3) to any location on the hard disk of the server.
Step 5 Run the DickTracy utility.
Step 6 In the DickTracy window, select File>Connect.
Step 7 Enter the IP address of the Cisco Access Digital Gateway DT-24+/DE-30+, and always use TCP port 2005. Then click OK.
Step 8 Select Options>Send Cmd to open the DickTracy command window. It may take 15 to 30 seconds for the gateway to respond and for the command window to open.
Step 9 In the DickTracy command window, enter 3 for the Task ID. Then enter other commands as needed. The command line syntax is as follows:
Display current settings.
set txpad NN
Set transmit pad value. (Brackets are required.)
set rxpad NN
Set receive pad value. (Brackets are required.)
Burn values to NVRAM. (Required to save the new settings.)
– specifies all B-channels. You can also specify individual channel numbers, such as  for channel 1,  for channel 2, and so forth.
–NN is a positive number between 00 and 63 that specifies the audio level, with 32 equal to zero dB, as indicated in the following table:
NN Pad value
New pad settings take effect on the next call made on each B-channel. Calls in progress are not affected by setting changes.
B-Channels and G.723 Calls on Cisco Access Digital Gateway DT-24+/DE-30+
To use all B-channels of the Cisco Access Digital Gateway DT-24+/DE-30+ for G.723 traffic, you must set the MaxNumberOf723Calls parameter in the scm.ini file. The MaxNumberOf723Calls parameter specifies the maximum number of G.723 calls that the gateway can send or receive. Set MaxNumberOf723Calls to 23 for the Cisco Access Digital Gateway DT-24+, or set it to 29 for the Cisco Access Digital Gateway DE-30+.
Cisco Messaging Interface
There are three new Windows Registry entries that you can use to configure the Cisco Messaging Interface. If you want to use them, you must create the Registry entries prior to installing the Cisco Messaging Interface. Upon installation, the Cisco Messaging Interface reads these Registry entries and uses them to configure the way it processes incoming and outgoing messages. If it cannot find these Registry entries, the Cisco Messaging Interface operates in default mode.
The Registry entries for configuring the Cisco Messaging Interface are located in:
HKEY_LOCAL_MACHINE/Software/Selsius Systems Inc./Selsius Unified Messaging Interface/
The available Registry entries for the Cisco Messaging Interface are:
•Trace - If this entry is present, the Cisco Messaging Interface creates a trace file and logs its actions. The trace file takes the name specified in the entry, and it normally is created in the Cisco/Bin directory. This trace file can be helpful when debugging Cisco Messaging Interface operations, and it should be enabled whenever Cisco Messaging Interface operations are in question.
•OutputDnFormat - The value found in this entry is used by an sprintf() function call in the Cisco Messaging Interface to format the outbound directory number. This Registry entry follows the syntax used in the C programming language to format character strings. The default setting of OutputDnFormat (used when this Registry entry is not present) is %010s. In the C programming language, this means that the directory number is formatted in a 10-character field padded with leading 0 characters. If you change the OutputDnFormat setting to 92%05s, for example, this causes the Cisco Messaging Interface to format the field as a five-character string padded with leading 0s. The two digits 92 are unconditionally prepended to the five-character field, making the outbound directory number a total of seven digits.
•InputDnSignificantDigits - This entry is a DWORD numeric value that determines how many digits are processed from the incoming directory number in the MWI message. The default value used when this Registry entry is not present is 10. If the incoming directory number contains more than the specified number of digits, the upper digits (most significant digits) are stripped from the directory number.
Note If you change any of these Windows Registry entries after installing the Cisco Messaging Interface, you must use Cisco Process Control to restart the Cisco Messaging Interface.
Debug Trace Flags
Cisco CallManager provides debug trace functionality for advanced error handling. The debug trace flags are most commonly used by the Cisco Technical Assistance Center (TAC) to resolve problems with Cisco CallManager. You can access the trace flags through Cisco CallManager Administration by selecting Control Center and then clicking the Show button for Cisco CallManager Debug Trace Flags.
Cisco CallManager now treats all DTMF signals as out-of-band, and it is now possible to pass digits in both directions on H.323 type devices.
Enhanced 911 Service
Enhanced 911 (E911) service is available for your Cisco IP Telephony system. Cisco CallManager provides the appropriate calling line ID information and signaling required for E911. Connection to E911 service providers is available through third-party sources. For more information on connecting your Cisco IP Telephony system to E911 services, visit the Cisco web site at http://www.cisco.com.
License Management has been disabled in Cisco CallManager for release 2.4(3) and 2.4(4). Please ignore any prompts from Cisco CallManager Administration that ask you to enter License Management information.
When you answer a multi-line phone (take the phone off-hook), the default behavior is for the phone to select the ringing line automatically. You can modify this behavior so that the phone always selects the prime line (line 1) when you go off-hook. To enable prime line selection for all phones, set the AlwayUsePrimeLineFlag to 1 in the SCM.INI file. If prime line selection is enabled, users must always press a line button to select a line other than the prime line, even if there is an incoming call on that other line.
Media Termination Point
You now have the option to control Media Termination Point (MTP) parameters by changing the settings in the Windows Registry. For details, see "Configuring the Media Termination Point" in the online System Guide.
Remote serviceability enables Cisco CallManager to be serviced from a remote location while maintaining the security of your site. This release of Cisco CallManager implements two features for remote serviceability:
•Cisco Bridged Telnet — provides Cisco Service Engineers (CSEs) transparent firewall access to a Cisco CallManager server on a customer site for diagnostic and troubleshooting purposes.
•show command — displays the contents of the Cisco CallManager configuration database, the configuration file, memory statistics, and Windows diagnostic information.
Reset Option for Configuring Cisco IP Phones
The Device Wizard in Cisco CallManager Administration contains a new option for resetting a Cisco IP Phone while you are configuring the phone in the database. After you enter the configuration data for the phone and click Finish, two new buttons appear:
•OK, reset now—Clicking this button saves the changes in the database, resets the phone (call processing on that phone is interrupted), and registers the changes with Cisco CallManager so that they take effect immediately.
•OK, reset later—Clicking this button saves the changes in the database, but it does not reset the phone or register the changes with Cisco CallManager.
If the phone is not yet physically installed on the network, you can click OK, reset now without interrupting call processing. If the phone is already installed on the network, then you might want to click OK, reset later to avoid interrupting call processing for that phone. Later, when the phone is not busy, you can reset it by clicking the Reset button for that phone in Cisco CallManager Administration, by pressing **#** on the phone, or by reconnecting the phone to the network.
Note Changes or additions to call forwarding information for a phone do not take effect in Cisco CallManager until you reset the phone. In some cases, Cisco CallManager might loop an incoming call back to its source if the destination phone has not been configured and reset properly and if the incoming call matches a routing pattern that routes calls back out. To avoid this problem, choose route patterns carefully so that they are unique, and reset each phone as soon as possible after configuring it in the Cisco CallManager database so that the call forwarding information can take effect.
Tone on Hold, Transfer, and Call Park
The party placed on hold, transfer, or call park hears an intermittent tone once every 10 seconds. Currently there is no tone on hold, transfer, or call park for calls going through a Media Termination Point. Also, if the party on hold, transfer, or call park activates a feature such as hold, the tone is not retained for either party on the call.
Cisco uOne is a voice messaging system that combines with Cisco CallManager to provide voice messaging services over an IP network. Cisco uOne is sold separately from Cisco CallManager. Cisco uOne is currently available only for the Cisco Media Convergence Server 7830 and only in the North American market.
Wherever possible, Cisco uOne supports industry standard internet messaging protocols such as LDAP, IMAP, MIME, SMTP and HTTP. For this release, Cisco uOne provides the following features:
•Call Answer Service — callers can leave messages for users.
•User Messaging Services — users can log in, retrieve their messages, and administer their voice mailboxes.
•Calling Services — callers can transfer to an attendant or another number. Users can return calls or make calls while listening to messages. After completing a call, the user returns to the same message in Cisco uOne.
You can install only one voice messaging system (either Cisco uOne or third-party voice mail) per installation of Cisco CallManager.
Note If you are using Cisco uOne, please ignore the voice mail information in the Cisco CallManager online System Guide and refer instead to the latest Cisco uOne documentation.
The latest software upgrades and release notes are available on Cisco Connection Online (CCO) at:
Cisco Year 2000 product compliance information can be found at:
A local copy of the online Help is installed with Cisco CallManager, and you can access it by clicking Start>Programs>Cisco CallManager>Cisco Help>System Guide. The System Guide is also available on the Web at:
You should perform regular system backups as described in the topic Backing Up the System in the online System Guide at:
For instructions on backing up the system, select the following book and topic in the menu:
Cisco CallManager>Backing up the system.
This section contains unresolved caveats for this release of Cisco CallManager. Caveats describe unexpected behavior or defects in Cisco CallManager software and related hardware.
Open Caveats for Cisco CallManager Release 2.4(4)
This section describes possibly unexpected behavior by Cisco CallManager Release 2.4(4).
Description: Sound problem for holding line. This problem can be seen after connecting a call. After connecting a call, if it does a holding action on both sides, then the holding sound can't be heard if only one side releases the holding action.
Description: Voice greeting fades when recording from Cisco IP Phone to Cisco uOne. When recording a voice greeting to Cisco uOne, the first couple of seconds are normal volume, then the voice will fade to lower volume. If the user speaks softly, the greeting will degrade into nothing. This condition is caused by the Echo Cancellation in any phone load that ends with 'J4'.
Workaround: If you are using Cisco uOne with your Cisco CallManager, use a phone load other then one ending in 'J4'.
Description: The status of the phone is not being updated in Cisco WebAttendant.
Workaround: To work around the problem:
–Call the phone to update the phone status.
–Going off hook on the phone should also update the status.
Description: If a random sequence of button pushes causes the Transfer button to quit working, the Cisco IP Phone cannot complete the transfer, and the buttons on the phone no longer work.
Workaround: Unplug the phone for 2 minutes or more, then plug the phone back in.
Description: Even at low call rates through the DT-24+, the collision light will show activity and will increase proportionate to the call volume.
Workaround: There is no workaround needed; there will be some activity on the collision light without impacting service, even at very high volumes.
Description: BootP fails on Cisco MCS7830 and MCS7820 platforms. BootP gets error 10048, "Unable to create socket" when you save and load the configuration. This problem only occurs at sites where DHCP is not running and the customer is using the BootP utility for some gateway devices (Cisco AS, AT, and DT24+ gateways).
Workaround: Install the BootP utility on another PC (other than the PC that is running Cisco CallManager).
Description: A call coming from the PSTN to a Cisco IP Phone does not complete because the H.225 setup message is too large to be understood by the Cisco CallManager.
This problem can occur under the following conditions:
–The setup includes a Cisco AS5300 with QSIG from the PSTN and Cisco CallManager, or
–A Cisco CallManager has a Cisco IP Phone registered and a Microsoft NetMeeting device connected in through a Cisco 800 router via an ISDN connection.
Workaround: To work around the problem if you have a Cisco AS5300 with QSIG from the PSTN, send smaller H.225 setup messages by turning off QSIG and other extra information.
To work around the problem under the second condition listed above, perform the following steps in the Microsoft NetMeeting device:
1. Select Tools > Options from the Microsoft NetMeeting menu bar.
2. Deselect (uncheck) everything under Directory Settings. This will reduce the amount of information sent in the H.225 setup message.
If those boxes are checked, then the H.225 message setup will be too long (because it contains too much information) and consequently will not be understood by the Cisco CallManager.
Note The same problem will occur if the Microsoft NetMeeting device is in the local LAN. It can be resolved by using the workaround above.
Description: No call progress when calling a busy user over a Cisco Access Digital Trunk Gateway DE-30+.
When placing a call out a DE-30+ and the called user is busy, the Cisco IP Phone displays the date and time instead of the user busy tone.
Description: 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.
Open Caveats for Cisco CallManager Release 2.4(3)
This section describes possibly unexpected behavior by Cisco CallManager Release 2.4(3). Unless otherwise noted, these caveats apply to all Cisco CallManager 2.4 releases up to and including Cisco CallManager Release 2.4(3).
Description: The exclamation point character (!) in a route pattern does not work as expected if it is followed by the pound sign character (#). The exclamation point character normally represents one or more digits 0 through 9, but it allows only a single digit when followed by the pound sign character. For example, the route pattern 011!# allows a caller to dial 0112 or 0112#, but it does not allow 01123.
Workaround: Create two route patterns, one with the pound sign character and one without. Define the route pattern with the pound sign character first. For the example above, the two route patterns would be 011!# and 011!.
Description: When it is first installed and configured, Media Termination Point (MTP) shows no resources available.
Workaround: Using Cisco CallManager Process Control, stop and restart the MTP process only.
Open Caveats for Cisco CallManager Release 2.4(2b)
This section describes possibly unexpected behavior by Cisco CallManager Release 2.4(2b). Unless otherwise noted, these caveats apply to all Cisco CallManager 2.4 releases up to and including Cisco CallManager Release 2.4(4).
Description: Cisco IP Phones generate an echo (feedback) when used at maximum volume.
Workaround: To reduce or eliminate the echo, set the volume to no more than 75% of maximum volume.
Description: If the greeting message for Cisco uOne voice mail is recorded using the speakerphone, the volume drops substantially. This problem has not been observed on any supported voice mail systems other than Cisco uOne.
Workaround: Always use the handset to record the greeting message for Cisco uOne voice mail.
Description: After upgrading to the latest release of Cisco CallManager and installing the Plug-Ins, the icons for the Plug-Ins do not appear in the System Tray and the configuration screens for the Plug-Ins are not accessible.
Workaround: Using Cisco Process Control, stop all processes and then restart them.
Description: If a user has a call on transfer hold and receives an incoming call, any attempt to transfer the incoming call results in that call being connected to the call on transfer hold.
Workaround: The call transfer feature in Cisco CallManager is commonly referred to as a consultation transfer, and it first places the transferred call on hold. If you have one call on transfer hold when a second call comes in, any attempt to transfer the second call results in a conference connection between the two calls on transfer hold. To avoid this situation, you can disable the call waiting feature if it is not needed for the phone in question.
Description: The description in the online documentation for configuring a Media Termination Point (MTP) is incomplete.
Workaround: First install the MTP plug-in as described in the online documentation under "Installing a Media Termination Point." Next, configure the MTP plug-in as described in the online documentation under "Configuring the Media Termination Point." Then use the Device Wizard to add an MTP device to the Cisco CallManager database, as described in the online documentation under "Adding a Media Termination Point."
Open Caveats for Cisco CallManager Release 2.4(1)
This section describes possibly unexpected behavior by Cisco CallManager Release 2.4(1). Unless otherwise noted, these caveats apply to all Cisco CallManager 2.4 releases up to and including Cisco CallManager Release 2.4(4).
Description: A hairpinned call from a Cisco AS5300 with different codecs (G.711 and G.723) to Cisco CallManager fails with a "Resources unavailable" error. Incoming voice dial peers (IP) are not compared strictly with dial peers in the configuration. In the configuration, there are two dial peers with different codecs (G711ulaw and G723r63) for connection with Cisco CallManager. The first dial peer was attached to a G711ulaw codec and the second was attached to a G723r63. When testing calls from Cisco IP phones in this configuration, calls could be made with the G711ulaw but not with the G723r63. (Error code was 2F - No resource.)
Workaround: Change codecs so that the first dial peer has G723R63 and the second one has G711ulaw. Both codecs should work under this new configuration.
Open Caveats for Cisco CallManager Release 2.3(1b) and 2.3(2)
This section describes possibly unexpected behavior by Cisco CallManager Release 2.3(1b) and 2.3(2). Unless otherwise noted, these caveats apply to all Cisco CallManager releases up to and including Cisco CallManager Release 2.4(4).
Description: The Call Direction parameter field for the T1 port of the Cisco Access Digital Gateway DT-24 does not appear to work. Call Direction specifies the direction of calls passing through this port. Allowed settings are:
–Inbound for inbound calls only
–Outbound for outbound calls only
–Both Ways for inbound and outbound calls
Workaround: Use a 24-port Cisco Access Digital Gateway PRI or an 8-port Cisco Access Analog Trunk Gateway.
Description: When a call is placed to a voice gateway, the caller first hears internal dial tone. The caller then dials the access code for an off-net call. External dial tone is heard, and the call is made and then cleared normally.
When the caller uses the redial feature, he first hears internal dial tone. When the caller presses the redial key, he hears external dial tone for five seconds or so before the connection is made. This dial tone is played out for too long and should be replaced with silence.
Workaround: There is no current workaround. The issue appears to be due to the long time required to connect through the H.323 Gateway. The issue is still under investigation.
Open Caveats for Cisco CallManager Release 2.2
This section describes possibly unexpected behavior by Cisco CallManager Release 2.2. Unless otherwise noted, these caveats apply to all Cisco CallManager releases up to and including Cisco CallManager Release 2.4(4).
Description: Existing route filter values cannot be seen in the form view of the Route Filter Configure dialog box.
Workaround: Entering multiple route filters causes the behavior described above. Cisco CallManager accepts only single route filter entries. This issue will be addressed in a future release.
Description: After a client places a Directory Services Call via the web browser, use of the browser Back button can cause the call to be placed again.
Workaround: After placing a Directory Services Call, refresh the Active Server Page (ASP) so that the browser Back button will not redial the previously placed call.
Troubleshooting is provided in the locally installed Help or the online System Guide at:
Click the Troubleshooting book in the menu to see the troubleshooting topics.
You can access information about Cisco CallManager Release 2.4(4) by using the System Guide on the Web instead of the locally installed version available from the Start menu. To access the Web version of the System Guide, open a web browser and type the URL:
The latest software upgrades and release notes are available on Cisco Connection Online (CCO) at:
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/pcgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Obtaining Technical Assistance
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco Connection Online
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
•Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.
–From North America, call 408 526-8070
–From Europe, call 33 1 64 46 40 82
You can e-mail questions about using CCO to email@example.com.
Technical Assistance Center
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language E-mail Address
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.
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.
You can e-mail your comments to firstname.lastname@example.org.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0005R)