Français dropdown-ico

Cisco Systems 3.0(10) manuel d'utilisation

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104

Aller à la page of

Les manuels d’utilisation similaires

Un bon manuel d’utilisation

Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Cisco Systems 3.0(10). Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Cisco Systems 3.0(10) ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.

Qu'est ce que le manuel d’utilisation?

Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Cisco Systems 3.0(10) décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.

Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.

Donc, ce qui devrait contenir le manuel parfait?

Tout d'abord, le manuel d’utilisation Cisco Systems 3.0(10) devrait contenir:
- informations sur les caractéristiques techniques du dispositif Cisco Systems 3.0(10)
- nom du fabricant et année de fabrication Cisco Systems 3.0(10)
- instructions d'utilisation, de réglage et d’entretien de l'équipement Cisco Systems 3.0(10)
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes

Pourquoi nous ne lisons pas les manuels d’utilisation?

Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Cisco Systems 3.0(10) ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Cisco Systems 3.0(10) et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Cisco Systems en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Cisco Systems 3.0(10), comme c’est le cas pour la version papier.

Pourquoi lire le manuel d’utilisation?

Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Cisco Systems 3.0(10), l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.

Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Cisco Systems 3.0(10). À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.

Table des matières du manuel d’utilisation

  • Page 1

    Corporate Headquarters: Copyright © 2001 . Cisco Systems, Inc. All rights reserved. Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA Release Notes for Cisco CallManager Release 3.0(10) Original CCO appearance: June 20, 2001 Revised: July 2, 2001 These release notes describe the ne w features and cav eats for Cisco CallManage[...]

  • Page 2

    Contents 2 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Contents These release notes discuss the following topics: • Introduction, page 2 • System Requirements, page 3 • Related Documentation, page 3 • Ne w and Changed Information, page 4 • Resolved Ca veats, page 20 • Open Cav eats, page 64 • Documentation Updates,[...]

  • Page 3

    3 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 System Requirements System Requirements Make sure Cisco CallManager Release 3.0 is installed and conf igured on a Cisco Media Con v ergence Serv er . Y ou may also install Cisco CallManager on a Cisco-approv ed Compaq server conf iguration or a Cisco-approv ed IBM server conf igurati[...]

  • Page 4

    New and Changed Information 4 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 • Cisco IP Phone 7900 F amily Administration Guide • Conf iguring Remote Serviceability for Cisco CallManager Release 3.0 • Using Cisco CallManager T race Gathering T ool for Diagnostic T races • Cisco W ebAttendant Quick Start Guide • Cisco W eb[...]

  • Page 5

    5 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 New and Changed Information Backup Utility The Backup Utility now creates backup f iles with the .sti extension instead of using the .tar extension. If you hav e .tar f iles already on your system, such as from an upgrade, the Backup Utility restores those f iles as well, but all cur[...]

  • Page 6

    New and Changed Information 6 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Service Parameters During an upgrade, Cisco CallManager does not ov erwrite service parameter values that the system administrator manually conf igures in Cisco CallManager Administration. New Software Features in Release 3.0(9) The following section conta[...]

  • Page 7

    7 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 New and Changed Information Service Parameters Cisco CallManager Release 3.0(9) supports new service parameters. Refer to T able 9 on page 83 for a complete listing of all service parameters, which includes descriptions and default v alues, that were not included in Release 3.0(5) of[...]

  • Page 8

    New and Changed Information 8 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 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 Ca veats - Release 3.0(7)” section on page 47 for more information. Important Notes for Release 3.0(7) Service[...]

  • Page 9

    9 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 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 v ersion at [...]

  • Page 10

    New and Changed Information 10 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Tech Prefixes Cisco CallManager Release 3.0(6) supports tech pref ixes in the Gatekeeper . T o properly conf igure the Cisco CallManager to register with a tech pref ix you must go to service parameters and perform the following steps: Step 1 Choose Cisco[...]

  • Page 11

    11 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 New and Changed Information New Hardware and Software Features in Release 3.0(5a) The following sections contain ne w and changed hardware and software features in Release 3.0(5a) of Cisco CallManager . Support for New Cisco IP Phones These ne w phone models, Cisco IP Phone 7910, Ci[...]

  • Page 12

    New and Changed Information 12 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 • 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 ke ys with conte xt-sensiti ve features – Fiv e f ixed function b u[...]

  • Page 13

    13 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 New and Changed Information • Simpler conf iguration—Previous v ersions of Cisco CallManager required all Cisco CallManagers in separate clusters to be conf igured in the Cisco MCM as a source address/destination address (SA/D A) pair . Registration by cluster pairs meant that f[...]

  • Page 14

    New and Changed Information 14 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 applications server . When the user selects one of the services, the service emits XML tags to the same phone according to the design behavior of the service. XML tags for menu display , item selection, graphics display , and character display are av aila[...]

  • Page 15

    15 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 New and Changed Information Additional MGCP Support for Cisco VoIP Gateways Media Gate way Conf iguration Protocol (MGCP) support provides two primary benef its over H.323 support. First, MGCP pro vides a centralized dial plan. An H.323 network requires that the dial plan for each g[...]

  • Page 16

    New and Changed Information 16 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 through the Cisco A VVID network, out of TDM networks to another AMIS-equi valent v oice messaging system. The capabilities allo wed include the ability to reply to and forward messages from one messaging system to another . User Interface Enhancements Ci[...]

  • Page 17

    17 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 New and Changed Information • Cisco W ebAttendant Conf iguration—A ne w set of added pages enables administrators to conf igure Cisco W ebAttendant pilot points, hunt groups, and users. T o access this page from the main Cisco CallManager Administration page, select Service >[...]

  • Page 18

    New and Changed Information 18 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 The following e xample highlights the dif ference: The Cisco IP Interactiv e V oice Response System typically opens sev eral CTI route points and CTI ports; it will always open a single CTI connection to a Cisco CallManager in the cluster . The 400 connec[...]

  • Page 19

    19 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 New and Changed Information • Cluster-2 conf igures 5 intercluster trunks (to CCM-A, CCM-B, and CCM-C in Cluster1 and to CCM-F and CCM-G in Cluster-3). • Cluster-3 conf igures 5 intercluster trunks (to CCM-A, CCM-B, and CCM-C in Cluster-1 and to CCM-D and CCM-E in Cluster -2). N[...]

  • Page 20

    Resolved Caveats 20 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats Resolved Caveats - Release 3.0(10) T able 2 lists and describes Caveats that were resolv ed in Cisco CallManager Release 3.0(10). Note If you hav e an account with Cisco.com (Cisco Connection Online), you can use the Bug T oolkit to f ind ca veats o[...]

  • Page 21

    21 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCds43704 Call looping uses CPU and other resources in Cisco CallManager . A Cisco CallManager code change f ixes this problem. CSCds74822 Service Conf iguration application does not function properly . A Cisco CallManager code change f ixes this behavior . CSCds82[...]

  • Page 22

    Resolved Caveats 22 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt42403 User loses a call after transferring to ward a b usy line. A Cisco CallManager code change corrects this behavior . This item duplicates CSCdt45632, CSCdt82239, and CSCdr58998. CSCdt47805 High CPU usage during directory searches from Cisco IP Phone 7960 o[...]

  • Page 23

    23 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdt71276 Backing up Media Con ver gence Server takes about 50 minutes; in pre vious versions, this took much less time. The priority of the backup engine was reduced, so it does not interfere with the operation of the Cisco CallManager . A code change corrects thi[...]

  • Page 24

    Resolved Caveats 24 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt75620 A need exists for T API dwCalledID to ref lect original called party . A code change ensures that T API dwCalledID ref lects the original called party . CSCdt75990 Calls with compatible regions and capabilities fail. A code change resolves this behavior .[...]

  • Page 25

    25 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdt83902 User cannot answer a consult transfer . The f ix releases the answer thread when applications in v oke an answer request on a consult call that is cleared due to transfer . CSCdt84284 A VVID: Cisco W ebAttendent client does not hav e access to wausers sha[...]

  • Page 26

    Resolved Caveats 26 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt94077 Device tables do not update correctly after failo ver occurs. Calls going out through a digital gatew ay were being dropped after one Cisco CallManager in a cluster fails in a certain way (links to other Cisco CallManagers in the cluster stay up, ev en th[...]

  • Page 27

    27 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdt96338 The simultaneous call limit for H.323 device equals 248 when it should be 360. Intercluster calls stop at 248 acti ve calls per H.323 de vice. A code change allows 360 calls to be in place simultaneously . Users experience this problem only with Cisco Cal[...]

  • Page 28

    Resolved Caveats 28 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdu04286 After conferencing, if only two parties are left in the conference, T API redirect causes both parties to be dropped instead of just the one doing the redirect. A Cisco CallManager code change corrects this behavior . CSCdu05420 Locations bandwidth takes [...]

  • Page 29

    29 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdu10146 Locations bandwidth calculation is wrong with software conference and codec change. A caller initiates a call to a low bandwidth (30 KB) location with codec G.729. The caller initiates a conference using a software conference bridge, and the codec changes[...]

  • Page 30

    Resolved Caveats 30 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdu68211 The default SdlT raceT ypeFlags value is inadequate for debugging needs. The def ault v alue SdlT raceT ypeFlags changed to 0x00004B15. This change only occurs on new installs. On upgrade installations, the previous setting for the "SDL TraceT ypeFla[...]

  • Page 31

    31 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdu18646 An unstable modem connection exists through WS-X6608 and WS-X6624 gatew ays. This version includes ne w loads that ha ve been designed to provide V .34 connection speeds with a connection rate of 85 percent or higher . Speeds in the V .90 range are possib[...]

  • Page 32

    Resolved Caveats 32 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats - Release 3.0(9) T able 3 lists and describes Caveats that were resolv ed in Cisco CallManager Release 3.0(9) Note If you hav e an account with Cisco.com (Cisco Connection Online), you can use the Bug T oolkit to f ind ca veats of an y se verity for[...]

  • Page 33

    33 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCds03249 Label line setting for phone is inoperable. Customer has a requirement to change the display of the line buttons to sho w information other than the directory number . If the "Line settings for device" under the phone conf iguration is set with [...]

  • Page 34

    Resolved Caveats 34 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds74363 User can delete route list ev en if it is in use. The code now checks De viceNumPlanMap table to see whether the route list is associ- ated with any route pattern. CSCds74374 An error occurs while deleting an activ e route f ilter . A code change interpre[...]

  • Page 35

    35 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdt11252 Call transfer fails and throws a platform exception. A Cisco CallManager software modif ication implements the NEVER_CONNECT option for the CTI enable consultation transfer call. W ith the NEVER_CONNECT option, the application (ICD) can choose not to esta[...]

  • Page 36

    Resolved Caveats 36 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt27696 The message content returned incorrectly when you delete a server . The return error message no w states “some devices are using the serv er . ” CSCdt29654 A call to an activ e phone may result in negati v e bandwidth. A Cisco CallManager code change [...]

  • Page 37

    37 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdt44128 6608 sends disconnect when it does not recei ve an alerting fast enough. A Cisco CallManager service parameter was extended to correct this beha vior . CSCdt48748 When W indows 2000 Administrator account name is changed, i.e., to "callmngradmin, ” [...]

  • Page 38

    Resolved Caveats 38 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt57397 The f ile, ringlist.xml, is o verwritten during upgrades, which causes the Cisco IP Phone 7960 to reset. A code change causes the ringlist to remain after upgrade. CSCdt58120 Cisco CallManager update should not ask if machine is publisher/subscriber A Cis[...]

  • Page 39

    39 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats Resolved Caveats - Release 3.0(8) T able 4 lists and describes caveats that were resolv ed in Cisco CallManager Release 3.0(8). Note If you hav e an account with Cisco.com (Cisco Connection Online), you can use the Bug T oolkit to f ind ca veats of an y se verity fo[...]

  • Page 40

    Resolved Caveats 40 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds13646 A VVID: SNMP agent is missing on Cisco CallManager . MIBII Host Branch The vendor’ s SNMP Extension Agent provides the functionalities for bro wsing the MIB II tree through the SNMP Agent; therefore, it is not in the domain of the Cisco CallManager SNMP[...]

  • Page 41

    41 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCds72125 DisconnectedEvent is recei v ed with Cause=CtiResourcesN A vail. When an external call called a CTI route point, the call was redirected back and forth between a CTI port and an IP phone sev eral times. A code change f ixed this problem. CSCds74298 A call[...]

  • Page 42

    Resolved Caveats 42 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds91320 A VVID: PerfMon ccmActiv ePhones counter is incorrect. A Cisco CallManager code change allows the PerfMon counter to display correctly . CSCdt02726 Consult call fails throwing e xception. A Cisco CallManager code change corrects this problem. CSCdt04309 D[...]

  • Page 43

    43 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdt15151 A calling party transform mask returns an in v alid digit. A Cisco CallManager code change checks and drops calling party Microsoft Internet Explorer if calling party transform mask returns in v alid digit. CSCdt15834 Deleted shared lines do not auto regi[...]

  • Page 44

    Resolved Caveats 44 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt19887 MTP resources reporting status=1, but Cisco CallManager will not jump to better resources. The Cisco CallManager software has been modif ied to handle error code 255 from the Cisco Catalyst 6000 - DSP Resource device when there is error in opening the rec[...]

  • Page 45

    45 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdt21490 MTP resets on 23rd 729-711 transcoding(V AD enabled) When the CPU time is lower than a lo w watermark, the transcoder takes no ne w calls (and the calls will not be complete). All new calls will be rejected. The transcoder will not accept new calls until [...]

  • Page 46

    Resolved Caveats 46 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt28640 Cisco IP Phone 7960 intermittently delays dialtone when going off-hook. The off-hook message w as getting delayed only in certain scenarios. A Cisco CallManager code change resolved this cav eat. CSCdt29217 Call Park code correction to av oid blocking of [...]

  • Page 47

    47 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats Resolved Caveats - Release 3.0(7) T able 5 lists and describes Caveats that were resolv ed in Cisco CallManager Release 3.0(7) Note If you hav e an account with Cisco.com (Cisco Connection Online), you can use the Bug T oolkit to f ind ca veats of an y se verity for[...]

  • Page 48

    Resolved Caveats 48 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds55086 Access violation occurs in svchost during W in2K startup on client running Cisco SoftPhone. Microsoft has a f ix, contact Microsoft support for details at the following URL: http://support.microsoft.com/support/kb/ar ticles/q278/7/18.asp. CSCds58392 Putti[...]

  • Page 49

    49 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCds81134 Release messages are missing from Cisco CallManager . Changes made to the translation pattern to amends this problem. CSCds82314 Cisco CallManager will not initialize if many translation patterns e xist. The ability to initialize quickly even if hundreds [...]

  • Page 50

    Resolved Caveats 50 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds92026 No disconnect e vent occurs when disconnecting consult conference. CallManager .jav a was modif ied not to set setConferenceFeature during the initialization of the consult Conference call. CSCds92393 SDL router services are declared dead. When stationD p[...]

  • Page 51

    51 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats Resolved Caveats - Release 3.0(6) T able 6 lists and describes Caveats that were resolv ed in Cisco CallManager Release 3.0(6) Note If you hav e an account with Cisco.com (Cisco Connection Online), you can use the Bug T oolkit to f ind ca veats of an y se verity for[...]

  • Page 52

    Resolved Caveats 52 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdr74342 DC Directory gets suspended due to f ile system error . The problem was due to the f ile system backup utility locking the f ile using the win32 LockFile(). LockFile either allows a shared Read lock or an exclusi v e Read or Write lock. If a shared Read l[...]

  • Page 53

    53 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCds53378 Cisco CallManager upgrade with locations pre vents SW -based conference from working. The code for unlimited bandwidth in location for Cisco CallManager 3.0 does not currently work. Migration has been changed to remove the 0 bandwidth location records and[...]

  • Page 54

    Resolved Caveats 54 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds63460 BLIND TRANSFER: caller/calledid information becomes messed up on blind transfer . Cisco CallManager software has been modif ied to correctly display the calling, called party number , and name for the scenario of a call that was blind transferred to a lin[...]

  • Page 55

    55 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCds66507 Cisco W ebAttendant client will not install on W indo ws NT operating system. W indo ws operating systems version of regsvr32.e xe could not load the .dll extensions containing the Cisco W ebAttendant controls. Each Cisco W ebAttendant DLL tries to start [...]

  • Page 56

    Resolved Caveats 56 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds69538 Conference is in bad state when Cisco AutoAttendant redirects call back to its own ports When Cisco AutoAttendant is redirected to a second CTI port, a redirect signal is sent to the Conference process inside of Cisco CallManager . The logic in this proce[...]

  • Page 57

    57 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCds77578 Cisco CallManager does not cut through after progress with DE30+ (ov erlap sending). At the ov erlap sending situation, the channel ID can be receiv ed in setup pack. CSCds79716 UserPrefs do not work after an upgrade from versions prior to Cisco CallManag[...]

  • Page 58

    Resolved Caveats 58 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats - Release 3.0(5a) T able 7 lists and describes Caveats that were resolv ed in Cisco CallManager Release 3.0(5a). Note If you hav e an account with Cisco.com (Cisco Connection Online), you can use the Bug T oolkit to f ind ca veats of an y se verity [...]

  • Page 59

    59 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdr41614 DTMF digits are not propagated to members of a conference. When a DTMF digit is pressed when a phone is connected to a conference, the digit is dropped. For e xample, if a ringing phone is added to a conference, and the phone is subsequently not answered [...]

  • Page 60

    Resolved Caveats 60 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdr51675 When using the Cisco CallManager Control Center web page, the services for a server do not appear when it is selected. The screen displays "A connection to the server could not be established." This problem occurs under any of the following cond[...]

  • Page 61

    61 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCdr78651 Ability to park call by directory number is missing. Modif ied park code allocation to use the same park code number when call park rev ersion occurred. This allo ws the parking party to repark the same call to the same park code in effect when call park [...]

  • Page 62

    Resolved Caveats 62 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds19447 No information about Cisco AutoAttendant install exists in Cisco CallManager install documents. The AutoAttendant Administrativ e Guide documents the information. CSCds21377 The Cisco CallManager service was up but w as not running. Looking at PerfMon sta[...]

  • Page 63

    63 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Resolved Caveats CSCds67376 Auto install on 7820/22 locks up on f inal reboot after upgrade. When performing upgrades on the MCS7820 or 7822, the server would lock up on the f inal reboot. This issue is resolved if W indo ws 2000 service pack 1 is installed prior to upgrading Cisco [...]

  • Page 64

    Open Caveats 64 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats Open Caveats for Cisco CallManager Release 3.0(10) T able 8 describes possible unexpected behaviors by Cisco CallManager Release 3.0(10). Unless otherwise noted, these cav eats apply to all Cisco CallManager 3.0 releases up to and including Cisco CallManage[...]

  • Page 65

    65 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats CSCdr36331 Going from low bit rate to lo w bit rate, the wrong counter is sent from a transcoder . The problem occurs when the system is conf igured, so a transcoder is inv oked to transcode between two lo w-bit-rate codecs (for example, from a G.723 to a G.729). Note C[...]

  • Page 66

    Open Caveats 66 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdr39403 Database notif ication does not work in certain situations. Updates made from the Cisco CallManager administration page are registered b ut not ref lected in the MIB tables until the SNMP data collector or Cisco CallManager (depending on the type of update) i[...]

  • Page 67

    67 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats CSCdr39493 Y ou cannot assign the same extension to a Cisco Catalyst 6000 24 Port FXS Analog Interface Module and a Cisco IP phone. W orkaround : No w orkaround exists. F or Cisco CallManager Release 3.0, only MGCP gate ways (VG200s) allo w FXS ports to share the same p[...]

  • Page 68

    Open Caveats 68 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdr77184 Call park numbers do not recycle through conf igured range. W orkaround : Go to Feature > Call Park , select a range, and click Update ; or create a ne w range. CSCdr80075 A need exists for the Cisco CallManager to check the assignment of lines and speed-d[...]

  • Page 69

    69 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats CSCds09623 The scroll bar does not appear on De vice/Phone list page. W orkaround: 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-ans[...]

  • Page 70

    Open Caveats 70 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds42397 T erminal services do not function. W orkaround : This is a Microsoft limitation. CSCds42397 T erminal Services are nonfunctional. W orkaround: This is a Microsoft limitation. CSCds46274 Cisco IP Phone 7960 user on G.729 call hears hiss after digit during IVR[...]

  • Page 71

    71 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats CSCds55942 A VVID: Call produces cumulati ve feedback when conferencing back to itself. W orkaround: A void conferencing a call back on itself. CSCds59268 When Call Forw ard No Answer is conf igured on a line with partition, the calls forward to Call F orward No Answer [...]

  • Page 72

    Open Caveats 72 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCds80198 Call pickup does not pick up a call e ven when line is Call F orward All. W orkaround : No w orkaround exists. CSCds84446 A VVID: V olume from Cisco Access Digital T runk Gatew ay DT -24+ to Cisco uOne is too lo w to hear voice mail. W orkaround : No w orkaro[...]

  • Page 73

    73 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats CSCdt17567 Conference master drops from conference while adding 24th party into the conference. W orkaround: No w orkaround exists. CSCdt20517 Calls placed on IP phones sho w translated No. W orkaround : The problem does not occur when no translation is done, b ut if di[...]

  • Page 74

    Open Caveats 74 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt29275 Cisco CallManager 3.0(5a) upgrades reset enterprise parameter URLs to default. W orkaround : After the upgrade, change the URLs to the v alues that existed prior to the upgrade. CSCdt30332 Cisco Messaging Interf ace stops after Cisco CallManager 3.0(7) upgrad[...]

  • Page 75

    75 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats CSCdt40012 DE 30+ loses D Channel under stress. W orkaround : No w orkaround exists. CSCdt40683 Cisco Messaging Interface partition must match route partition when conf iguring Cisco Messaging Interface. W orkaround: If you are using partitions and calling search spaces[...]

  • Page 76

    Open Caveats 76 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt50317 Cisco CallManager 3.0(7) Call Detail Records do not nov e from subscriber to sublisher . W orkaround : No w orkaround exists. CSCdt52841 Cisco W ebAttendant documentation calls for read access to the w ausers share, b ut change access is required to open the [...]

  • Page 77

    77 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats CSCdt62208 Cisco IP Phone 7960 reports two missed calls if unanswered. W orkaround : 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 undef ined directory number rec[...]

  • Page 78

    Open Caveats 78 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdt73926 CDR CallID is reset with Cisco CallManager restart. W orkaround : 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[...]

  • Page 79

    79 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats CSCdu06412 Cisco CallManager incorrectly interprets the disconnect cause. W orkaround : Use the route group that chooses local gate way . CSCdu08950 Unchecking the run H.225 on ev ery node still has location leaks. W orkaround : No w orkaround exists. CSCdu10456 T ransf[...]

  • Page 80

    Open Caveats 80 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CSCdu21141 A lineAnswer returns SUCCESS, but state does not change. W orkaround :Use blind transfer or consult transfer instead of arbitrary transfer . CSCdu21447 Cisco CallManager subscriber does not refresh database upon network recovery . W orkaround : Stop and start[...]

  • Page 81

    81 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Open Caveats CSCdu52827 Network time protocol service hangs. W orkaround : Perform the follo wing steps if you experience an issue with the Network time protocol service: Step 1 Right click My Network Places . Step 2 Click Properties . Step 3 Right click Local Area Connection . Step[...]

  • Page 82

    Documentation Updates 82 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates This section contains the latest documentation updates for Release 3.0 of the Cisco CallManager , and the latest service parameters that were not included in Release 3.0(5) of the Cisco CallManager documentation. Included in these updates [...]

  • Page 83

    83 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates New Service Parameters T able 9 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0(5) Cisco CallManager Administr ation Guide or the online help for the Cisco CallManager application. T able 9 Cisco C[...]

  • Page 84

    Documentation Updates 84 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 CTIRequestT imeo ut Default: 5 (seconds) Specif ies timeout interval. Timer ensures responses to CTI requests are generated for situations where network or remote Cisco CallManager node problems prev ent the normal processing of the CTI requests. This timer ser[...]

  • Page 85

    85 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates IpT osCm2Cm Default: 3 Controls class of service of IP traff ic and signals between Cisco CallManager to Cisco CallManager . Note The follo wing list shows that the v alid v alue for IpT osCm2Cm is between 0 and 7 and is represented as follows: 0 = routine 1 = [...]

  • Page 86

    Documentation Updates 86 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 IpT osCm2Dvce Default: 3 Controls class of service of IP traff ic and signals between Cisco CallManager to device. Controls class of service of IP traf f ic and signals between Cisco CallManager to Cisco CallManager . Note The follo wing list shows the v alid v[...]

  • Page 87

    87 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates MaxCTI Connections Default: 400 Designates the maximum number of CTI connections. Cisco CallManager allows a maximum number of CTI connections. T ypically , each CTI application (or instance of the application) has a single CTI connection to the Cisco CallManag[...]

  • Page 88

    Documentation Updates 88 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 NumberingPlanInf o Default: 1 Gi ves some control o ver the ISDN Numbering Plan Information f ield on the Called Party Number . This control that is av ailable for H.323 calls and ISDN calls has the following characteristics: • If set to 0: disabled • If se[...]

  • Page 89

    89 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates StopRoutingOnUn allocatedNumberF lag Default: F Specif ies when set to true, that if a call being routed through a route list detects the associated “cause” during the release of the call, no re-routing to the next device in the route list is attempted and [...]

  • Page 90

    Documentation Updates 90 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Service Parameters T able 10 contains new Cisco CallManager service parameters, with descriptions, that were not included in the Release 3.0 Cisco CallManager Administr ation Guide or the online help for the Cisco CallManager application. Caution Do not modify [...]

  • Page 91

    91 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates T able 1 1 CMI Service P aramet ers Not Included in Release 3.0 Documentation ParamName Description BackupCallManagerName This parameter def ines the names of the Cisco CallManagers that are going to be used for the CMI backup. Y ou can use either the name of a[...]

  • Page 92

    Documentation Updates 92 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 InputDnSignif icantDigits This parameter is designed to accommodate the differences between voice mail mailbox numbers and DNs. If a Le gac y v oice mail system has mailbox numbers that are longer than the DNs on the system, this parameter can be used to strip [...]

  • Page 93

    93 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates Parity Cisco CMI connects to the voice mail system via an EIA/TIA-232 connection. This parameter def ines that connection. Recommended default v alue: Even Note The parity settings can be None, Even, Odd, Mark, or Space. Settings are usually Even and None, with[...]

  • Page 94

    Documentation Updates 94 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 SsapiK eepAliv eInterv al During normal operations, CMI will be attached to a Cisco CallManager . When this is the case, CMI sends a keepaliv e message to the Cisco CallManager at the rate specif ied by this numeric parameter . Default v alue: 30 seconds Cautio[...]

  • Page 95

    95 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates Server Name Change Change the CiscoW orks2000 server name by editing the SAen vproperties.ini f ile manually , then restarting the Cisco Syslog Collector service. In future releases, an administrati ve interface will be a v ailable for this purpose. V alidateDn[...]

  • Page 96

    Documentation Updates 96 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Running Show Tech T o run show tech correctly , use this example to construct your command: show -f output.txt -v -w480 db The example gi v en in the Sho w Command chapter of Conf iguring Remote Serviceability for Cisco CallManager 3.0 (page 3-2) lacks a space [...]

  • Page 97

    97 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates Cisco CallManager Service Parameters The following list contains the service parameters, which can be conf igured for the Cisco CallManager service type, that were omitted from the Release 3.0 Cisco CallManager Administr ation Guide and online help for the Cisc[...]

  • Page 98

    Documentation Updates 98 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 • SdlT raceT ypeFlags • SendingCompleteIndicator • T oneOnCallForward • T ypeOfCalledNumberForH225Devices • V oiceMail Cisco TFTP Service Parameters The following list contains the service parameters, which can be conf igured for the Cisco TFTP servic[...]

  • Page 99

    99 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Updates • DataBits • DialingPlan • InputDnSignif icantDigits • K eepAliv eDn • OutputDnFormat • OutputExternalFormat • Parity • RouteFilter • SsapK eepAliv eInterv al • StopBits • V alidateDns • V oiceMailParition Cisco IP Voice Media Streaming [...]

  • Page 100

    Obtaining Documentation 100 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Errors This section contains any errors contained in the Cisco CallManag er Administration Guide for Release 3.0 and/or the online help for the Cisco CallManager application. The upcoming release of the document and online help application will correct these[...]

  • Page 101

    101 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Obtaining Documentation World Wide Web Y ou can access the most current Cisco documentation on the W orld W ide W eb at the following sites: • http://www .cisco.com • http://www-china.cisco.com • http://www-europe.cisco.com Documentation CD-ROM Cisco documentation and additio[...]

  • Page 102

    Obtaining Technical Assistance 102 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Documentation Feedback If you are reading Cisco product documentation on the W orld W ide W eb, you can submit technical comments electronically . Click Feedback in the toolbar and select Documentation . After you complete the form, click Submit to se[...]

  • Page 103

    103 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Obtaining Technical Assistance Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order , access technical support, and vie w benef its specif ic to their r[...]

  • Page 104

    Obtaining Technical Assistance 104 Release Notes for Cisco CallManager Release 3.0(10) 78-13493-02 Contacting TAC by Telephone If you hav e a priority le vel 1 (P1) or priority le vel 2 (P2) problem, contact T AC by telephone and immediately open a case. T o obtain a directory of toll-free numbers for your country , go to the following website: htt[...]