Nortel Networks Cartridge Wrong filename shown in FTP Send, Starting syslog with the web server

Page 32

32

Wrong filename shown in FTP Send

When performing a File > Send to FTP operation, you can change the filename by double-clicking it. However, the progress label does not register the change and instead reports “sending <old filename>.” (CR Q00732289)

Starting syslog with the web server

When you start the server, if the web server cannot start on its port, the web server fails and does not set a “docroot” value for the path to the install directory. The syslog server needs this value to locate the appropriate syslog.txt file. Once the webserver starts successfully at least once, the docroot is defined, and the syslog server can start with or without the web server.

Increasing the limit of concurrent user sessions

To avoid overloading, NCM has a default limit of ten concurrent server operations at any time, with a maximum of five operations per client request. If you wish to change the number, you can do so in the datastore.ini file in the installation directory. The semaphores can be modified by changing the “maxConnections=” line in the datastore.ini file on the server. Semaphore count can be up to 40 for a high-powered server machine.

Truncated menus

If you rely on the right-click method for running operations, you cannot view all menu options. The calculation for screen placement of the dialog box uses only the size of the main menu, without incorporating the size of any cascading submenus. It is possible, in some cases, to have a submenu truncated. In these cases, use the menu bar to perform the operations, or move the NCM client window to enable the submenus to display fully.

N0033985 1.0

Image 32
Contents NCM Trademarks Contents Web server migration Audit log inconsistencies N0033985 Symbols used in this guide PrefaceText conventions Acronyms How to get help In-country toll-free numbers Preface N0033985 New features Supported platformsCall Detail Recording settings Password change wizardKnown anomalies in NCM for BCM3.7 cartridge NCM3.6 CRs corrected on NCM for BCM3.7 cartridgeKnown anomalies in NCM3.6 Executing Trim Archive wizard on File Management folderChapter N0033985 Chapter Installing NCM for BCM3.7 Installing NCM for BCM3.7 in a Windows environmentInstalling NCM for BCM3.7 in a Solaris environment Uninstalling NCM for BCM3.7 in a Windows environmentUninstalling NCM for BCM3.7 in a Solaris environment Installing NCM for BCM3.7 N0033985 Introduction Executing NCM wizardsInstallation notes Install as a ServiceClient Install Policy Device WizardArchiving files larger than 32 MBytes in size Running NCM as a Windows serviceNCM Keycode not found issue Connectivity broken issue Inventory ReportingPptp tunnel wizard support IPSec Branch Office Tunnel supportIPSec Remote User Account support Intermittent call routing error messages Export when voicemail is not initialized NCM does not support SRGNCM NetIQ IP address value Extra holiday foldersConfig archive file naming Reboot after applying keycodesNCM reports do not check user permissions Exporting policy to BCM fails Incorrect Call Pilot version in IVR report Known problems in previous versions of NCM Timeout errors when importing device configurations IVR service start Progress barNCM potentially unreachable with dual NIC Archive label not migrated from Oracle databaseWrong filename shown after using Browse function Drop-down list not availableNaming conventions do not match Unified Manager Log rotators after migrationWrong filename shown in FTP Send Starting syslog with the web serverIncreasing the limit of concurrent user sessions Truncated menusSend to Tftp using a remote server Using the Netscape browser on SolarisAudit log inconsistencies Telnet session history listLog rotators Operation progress barImport data Viewing syslog messagesGeneral issues and recommendations Operational notesN0033985