## Avaya asa date separator error

which it was purchased within one (1) year from the date purchased, then Avaya Inc. will either replace the Client Software or offer to refund the License. Fixed a bug where tracing identifier was not available in Log clauses that were configured inside other clauses. AuthBy RADSEC and ServerRADSEC can now write. rfc868-time gets the date and time from an RFC 868 Time server. [Daniel Miller]; ssl-heartbleed detects the Heartbleed bug in OpenSSL CVE-2014-0160 [Patrik.

### Related Videos

IAUG Webinar: SIP Troubleshooting for Avaya Session Manager and the Avaya SBCE 2 3typemodemethodEach Push Message must contain one validroot tag.Optional notification alerts – number of ringpings.Push Content = Top Line.normal or barge priority.A fully qualified URL - to a valid XML PushContent file for Top Line pushes. Cannotexceed 1024 characters.HTTP get or post methods (i.e. GET URI;POST URI).Issue 5 November 2009 43

Top Line Push Example 2:Using our previous stock alert example, the price of the AV is reaching the $15price target. Now, the stock broker’s telephone display shows:Figure 10: Telephone Display Prior to Receiving Stock Alert MessageThe code excerpt associated with the Stock Alert example to be sent as part ofthe Push Message is as follows:XMLData = Push AgentOnce a Push Message is received from the Push Initiator, the Push Agent firstparses the XML file for validation and tag mismatch errors. Then the Push Agentverifies that the URL in the tag is part of the Trusted Push Servers.Note:For more information on Trusted Push Servers, see Chapter 4: PushAdministration.Then the Push Agent requests the Push Content from the Trusted Push Serverusing the URL.44 9600Series IP Telephones Application Programmer Interface (API) Guide Top Line Push Content (PC)The Top Line push type’s Push Content has to be an XML file that contains avalid tag that contains a valid tag. For 9600Series SIP IPTelephones running SIP software Release 2.2 or greater, Avaya recommendsthat Top Line push message strings contain 28 or fewer characters; stringslonger than 56 characters will be truncated.The following is the code excerpt associated with the Stock Alert Top Line PushExample 2: to be sent as part of the Push Content: -->Stock Alert: AV @$15Using the tagThe tag for the Top Line push type must be the root element in the(PC) XML file.Using the tagThe tag consists of the actual text message to display on thetelephone’s Top Line.If the length of the message exceeds the given pixels, the entire message isdivided. The message then fits on a single line, with the initial text and theremaining text alternating on the top display line.A Top Line message can be approximately 320 pixels of usable space,depending on the width of each character (average 4-6 pixels wide per character)for all 9600 IP Telephones except the 9610. A single 9610 Top Line messagecan be approximately 160 pixels in length. When the text is longer than theallowable space, the message displays in two parts that alternate every fewseconds, based on the display interval setting. This means that for all telephonesexcept the 9610, there are up to 640 pixels (320x2) and for the 9610 there are upto 320 pixels (160x2).The text within the tag can consist of different character encodingssuch as UTF-8, ISO-888991, and Latin1. See the IETF Documents listed underRelated Documentation for information on character encoding.The telephone’s XML parser parses the XML file. Depending on the priorities andstate of the telephone, the Push Content displays as shown in Figure 11 with analert ring ping of 3.Issue 5 November 2009 45

The telephone is already broadcasting any Transmit Audio pushedcontent.If a phone is not in one of the above states, it is considered to be in a pushablestate, meaning the telephone will accept a Pushed Message.Successful Push ResponseIf the phone is in a pushable state, the Push Agent sends the Push Initiator thefollowing response for all Push request modes and all Push request types:Parameter Avaya asa date separator error Code Reason PhraseHTTP Status Code 200 “OK”x-Push-Status 200 “Push Message Accepted”Normal PriorityWhen the mode attribute in the tag is set to normal, the telephone statefor the Receive Audio push type must be pushable. If the telephone is in thepushable state, then the telephone accepts the Receive Audio push. Thetelephone broadcasts the pushed audio stream through the currently active audiodevice - the Speaker, Handset, Headset, or Bluetooth headset. Once the pushedaudio stream is transmitted to the user, the user can redirect it, terminate it, etc.A Receive Audio push with a normal priority will not stream if the phone is in anon-pushable state. When the telephone is in a non-pushable state, anycurrent audio activity continues without interruption or user notification avaya asa date separator error theAudio push stream is rejected. Error message 208 is sent and the Avaya asa date separator error Requestdoes not proceed.Parameter Status Code Reason PhraseHTTP Status Code 200 “OK”x-Push-Status 208 “Not in Audio Push State: PushAborted”Issue 5 November 2009 49

With support for multicast pushes in software Release 3.0 (for H.323 9600SeriesIP Telephones only), additional Status Codes may apply to multicast pushes andcause a non-pushable state. They are as follows:Parameter Status Code Reason PhraseHTTP Status Code 200 “OK”x-Push-Status 310 “310 Multicast XML Failure: NoRTP listening port specified”x-Push-Status 311 “311 Multicast XML Failure: NoMulticast IP address specified”x-Push-Status 312 “312 XML Failure: RTP listeningport specified is less then 10001”x-Push-Status 313 “313 XML Failure: RTP listeningport specified is greater then65535”x-Push-Status 314 “314 Multicast XML Failure:Multicast IP address is not in theexpected range of 239.0.0.0 to239.255.255”Additionally, the phone reserves the rtpLPort specified in the Push Message. Ifthe port is not available, then the following x-Push-Status error is returned:Parameter Status Code Reason PhraseHTTP Status Code 200 “OK”x-Push-Status 209 “209 Not in Audio Push State:RTP listening port not available”Barge PriorityWhen the mode attribute in the tag is set to barge, the Receive AudioPush Content is accepted as a priority message. However, a barge Audio pushis rejected when the telephone is in one of these non-pushable states:When the telephone is in the process of restoring a retrieved backup file.When a Local (Craft) Procedure has been initiated (For more information,see the applicable SIP or H.323 Avayaone-X DeskphoneEditionfor9600Series IP Telephones Installation and Maintenance Guide onhttp://www.avaya.com/support).50 9600Series IP Telephones Application Programmer Interface (API) Guide

*set the listening port on thephone*/ /*set the multicast ip*/Using the TagThe Web browser interface supports the tag. The tagallows an application to set a name/value pair that can be sent to the source ofthe request. The name is set by the name attribute and must be a valid WMLvariable name. The value is set by the value attribute. A element cancontain one or more tags. Postfield tags must be sent if the HTTPPOST method is used.Note:For more information on the tag, see Chapter 7: DevelopingWeb Image i/o error for the Browser.Table 4: Description of Elements and Attributes used in the Receive Audio PushXML MessageElement orTag Attribute DescriptionEach Push Message must contain one validroot tag.alert=0 A-lawDefault is PCMU.packetsize 10

1 Avaya one- Attendant connected to Avaya Communication Manager Service and Installation Manual EN Release 3.02 Issue 1 August 2010 Avaya One- Attendant V3.02 CM Service and Installation Manual Page 1 of 123

2

3 All Rights Reserved Copyright 2010 Avaya GmbH & Co. KG Frankfurt/Main Service and Installation Manual one- Attendant connected to Avaya Communication Manager Version: 08/2010 Reproduction and disclosure of information contained in this document, in whole or in part require the prior written consent of Avaya GmbH & Co. KG. All technical data, information and properties of the product described in this document have been compiled to the best of our knowledge at the time of printing. Subject to modification and improvements to the product in the course of technical developments. Avaya GmbH & Co. KG A/SP-BS Documentation Avaya One- Attendant V3.02 CM Service and Installation Manual Page 3 of 123

5 ABSENCE INFO SERVER (AIS).30 Requirements.30 Preparations on Exchange.30 Entries in the Windows Registry.33 Note on absence display.33 CALENDARINFORMATION.33 Requirements.33 Installation.33 WEBACCESS.33 Web interface.33 Programmable functions.33 Command-overview.34 WEBACCESS ADMIN TOOL.35 Installing.35 CONNECTING TO ETERNAL DATABASES.35 Tool.35 Rules.35 Import ACM subscriber data into the one- Attendant database.35 CONFIGURING THE SOFTWARE.37 ONE- ATTENDANT CONFIGURATION TOOLS OVERVIEW.37 one- Attendant configuration tools collection.37 Starting and logging in.37 User interface.37 PROPERTIES.38 TOOLS: ABSENCEINFOPUSHER.40 Settings.40 Buttons.40 Testing.40 TOOLS: ADDRESS PARSER.41 Application.41 Overview.41 PBs in a networked system.41 Settings: Code numbers.41 Settings: Call Number Replacement.42 Settings: Area codes.42 Fixed Numbers.42 Example for call number replacement with a closed numbering scheme.42 Example of call number replacement with an open numbering scheme.43 Country settings.43 Definitions.44 TOOLS: ONE- ATTENDANT.45 Buttons / Check.45 TOOLS: JONAS (PHONE BOOK SERVER).48 Buttons.48 Settings for large databases.48 TOOLS: PHONE BOOK.49 Connection tab.49 Assignment tab.50 TOOLS: UPDATE SERVICE.51 Buttons.51 TOOLS: WEBACCESS.52 Buttons / connection testing.52 TOOLS: ETERNAL CALL DETECTION.53 Motivation:.53 Operator Window.53 Extended Redial List.54 Call List.54 Criteria for external call detection in One-Attendant v Processing of incoming calls by one- Attendant connected to CM.55 Processing of outgoing calls by one- Attendant connected to CM.57 Example.58 Known Problems.61 Incoming and Outgoing calls on one- Attendant I55 3 rd party.61 MAINTENANCE, PROBLEM SOLVING.63 Avaya One- Attendant V3.02 CM Service and Installation Manual Page 5 of 123

6 TROUBLESHOOTING.63 AVAYA ONE- ATTENDANT MIGRATION FROM OSPC V Performing migration.65 ONE- ATTENDANT UPDATE.67 TIPS AND TRICKS.68 Starting one- Attendant without ACM.68 Checking the connection to Web server when Outlook out of office is switched on.68 Sybase database in the network with the same name.69 Distinction between external and internal numbers is not working.69 one- Attendant does not start at all.69 one- Attendant does not start after a restart.69 one- Attendant does not dial.69 Recommendations on configuring feature buttons.69 Name reconciliation on the one- Attendant / ACM database.70 APPENDI.71 LDAP CONNECTION (LDAP BROWSER) EAMPLES.72 LDAP connection.72 (LDAP browser).72 Example 1 for data source using a JDBC-ODBC bridge.72 Example 2 for data source directly via JDBC.73 Example 3 for MEDCOM data source using a JDBC-ODBC bridge.73 Example 4 for an LDAP data source using a JDBC-LDAP bridge with general settings.73 Example 5 for Exchange 5.5 data source using a JDBC-LDAP bridge.74 Example 6 for Exchange 2007/2003/2000 data source using a JDBC LDAP bridge.75 Example 7 for Domino 6 data source using a JDBC-LDAP bridge.75 Example 8 for Domino 5 data source using a JDBC-LDAP bridge.75 Example 9 for connection of the MasterDirectory.76 AVAYA COMMUNICATION MANAGER CONFIGURATION EAMPLES.77 Configuration examples.77 Settings under ATTENDANT CONSOLE.77 Settings under CONSOLE PARAMETERS.80 Settings under OPTIONAL FEATURES.81 Settings under FEATURE RELATED SYSTEM PARAMETERS.82 Settings under CLASS OF SERVICE (not shown).83 Settings under HUNT GROUP.83 Setting of FEATURE ACCESS CODES (ACD Features).84 Allocating an ABBREVIATED DIALING LIST.84 Settings under AGENT LOGINID.85 Settings under IP NETWORK REGION.87 Using Media Encryption.88 Additional configuration instructions.88 REGISTERED SERVICES.89 PORT OVERVIEW OF ONE- ATTENDANT AND ACCESSORIES.89 IMPORTING CM STATION AND AGENT DATA TO ONE- ATTENDANT PHONE BOOK CYCLICALLY.90 Create task for Exporting Station Data.90 Import Station Data into Phone book Import Agent Data into Phone book AVAYA ONE- ATTENDANT FEATURES AT A GLANCE ABBREVIATIONS REFERENCES GLOSSARY Terms Avaya One- Attendant V3.02 CM Service and Installation Manual Page 6 of 123

7 About this document Who is this manual for? This manual is for technical staff who install and configure Avaya one- Attendant applications. Use this manual as you wish for reference purposes regarding individual topics or to learn how to install and configure the applications. What information is available in the manual? This manual contains information on how to install and configure the one- Attendant and how to upgrade from a former version. What information is not in the manual? This manual does not contain any information on how to use the one- Attendant. How is this manual structured? The structure of this manual provides a step by step introduction. Usually, an introduction to the topic is provided first. Prerequisites or necessary skills are often described next. Instructions follow the prerequisites or necessary skills. An illustration or example further clarifies the topic. Where can you find additional information? Avaya asa date separator error information on one- Attendant and the installation of various components can be found in the documents specified in the references. Avaya one- Attendant Overview Please familiarize yourself with these components List of components Whether you serve as a switchboard for many users or connect calls on a smaller scale, the one- Attendant operator position provides just the tools and functions you need to expertly forward calls to the correct party. Before you can use a one- Attendant operator position, various components must be installed and operational. Below is a list of all components. The following descriptions explain the functions of each of the components. one- Attendant application One Attendant server (Database/JOnAS) QTAPI Framework SCAPI, iclarity SVA-Manager (network wide busy display) Tomcat Web Server WebLM WebAccess Absence Info Server TTrace Avaya One- Attendant V3.02 CM Service and Installation Manual Page 7 of 123

8 Component: one- Attendant application The one- Attendant application is a client application you can use to access different servers and databases. Component: Database/JOnAS In order to run the one- Attendant application you need a database. The database contains the configuration and phone book data. A database management system, Sybase SQL Anywhere(ASA) and an application server, JOnAS, are used for the database. JOnAS and ASA cannot be separated. Both servers must be installed on the same computer. Component: SCAPI, iclarity After you start one- Attendant, it loads Softconsole API ( SCAPI ) and starts iclarity. These processes are used for communication between OS-TAPI and Avaya Communication Manager (ACM). In Road Warrior-mode iclarity is used for VoIP-voice communications between one- Attendant (e.g. using a headset) and ACM. iclarity is a component of Avaya Softconsole. It is installed automatically and does not have a separate setup. Components: QTAPI Framework, TSAPI Client QTAPI Framework and TSAPI Client together form the interface between AES-Server and the SVA-Manager, avaya asa date separator error. Both components are installed together with SVA Manager. A new program group Avaya AE Services > TSAPI Client will be created for TSAPI. Component: MasterDirectory MasterDirectory is an application for the management of databases. Master directory consolidates and synchronizes the managed databases. CM-data can be easily imported using MasterDirectory. The MasterDirectory is integrated into one- Attendant just like every other database. The integration is preconfigured in the next SP in the configuration tools with Default-Settings. Component: SVA Manager SVA Manager is an independent server. Its purpose is to provide the network wide busy display. It uses the QTAPI framework and is connected with the one- Attendant using a TCP/IP-interface. SVA-Manager runs as a service on the PC and has no windows. It is started every time the PC is booted up, avaya asa date separator error, independently of one- Attendant. SVA Manager only needs to be installed once in the network. At least it can be installed on the client, on the server, or on another PC in the Network. Program outputs can be viewed using the TTrace Monitor, avaya asa date separator error. Component: Web server A web server is needed for the out of office notice. The web server must be installed on the same PC as the databases. one- Attendant uses the Tomcat web server. You cannot use another web server (such as Apache Web Server) for one- Attendant. Component: WebAccess WebAccess contains the HTML and Java Server pages for the Web server to configure the out of office notice using AIS (see below) or a browser. Installing WebAccess installs the following components. HTML pages Java Server Pages Web server activation Avaya One- Attendant V3.02 CM Service and Installation Manual Page 8 of 123

9 Component: WebAccess admin tool This tool is used for resetting the user password for WebAccess. Component: Absence Info Server (AIS) AIS lets the one- Attendant application detect and use an out of office notice set in Microsoft Exchange Server. AIS is installed on a central PC in the network and uses MAPI to access the Exchange Server. Component: WebLM License Manager WebLM License Manager must hl2 gameinfo.txt error available on the network. It manages licenses for one- Attendant and its components, avaya asa date separator error. Component: Calendar information You can use Outlook or Lotus Notes to query calendar information. However, you can only use one of these at a time. You need an appropriate active client on the one- Attendant client PC (and the AVAYA one Attendant Presence License). Valid component versions For one- Attendant to work with all the other components, you must have the correct version of the components. Installing the components from the installation CD will of course install the correct versions. Always consult your system specialist before installing any other versions, avaya asa date separator error, even newer versions! You will find some information in the chapters Systemrequirements for Avaya one Attendant or System Requirements for ACM or Absence Infor Server (AIS). Avaya One- Attendant V3.02 CM Service and Installation Manual Page 9 of 123

10 Block diagram of one- Attendant in conjunction with all additional components The following block diagrams of one- Attendant Client and one- Attendant Avaya asa date separator error show how all the application components work together. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 10 of 123

11 Avaya One- Attendant V3.02 CM Service and Installation Manual Page 11 of 123

12 Avaya One- Attendant V3.02 CM Service and Installation Manual Page 12 of 123

13 Connecting to Avaya Communication Manager Avaya one- Attendant can be connected with the ACM in two ways in Road Warrior mode or in Telecommuter mode. Road Warrior mode: In the Road Warrior configuration there is only one IP connection between PC and ACM. Control software and audio software must be installed on the PC. In this case, the control software is the one Attendant application, which performs all call signaling and control tasks. VoIP communication is processed using iclarity IP Audio avaya asa date separator error H.323-V2- compatible audio application). Avaya iclarity IP Audio runs in the background. This program is launched automatically as soon as you launch up Avaya one Attendant. You need one of the following for communication: a headset connected to the PC, a combination of PC speakers and a microphone, or a USB phone. A USB phone converts the analog audio data into digital signals itself, thus relieving the PC of the task. We recommend a USB phone for this reason. Telecommuter mode.: In Telecommuter (dual connection) mode, the PC on which one- Attendant is running and a telephone are connected separately to ACM. The PC is connected to ACM over an IP network (LAN). All calls are signaled and controlled via this connection. Voice communication takes place using any telephone connected anywhere p-cad 2006 error 5566 your PB (ISDN, analog, VoIP). The actual conversations can therefore be made with the usual quality and convenience to which you are accustomed. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 13 of 123

14 Installing the software Avaya one- Attendant system requirements System requirements: Server The PC running the server components must meet the following minimum requirements: Only one- Attendant server: PC with 2 GHz 2 GBytes RAM (4 GBytes recommended) 500 MBytes available disk space (depending on data) 100 Mbit/s Ethernet IP connection Operating systems 32 Bit: Windows P, Windows 2003 Server, Windows 2003 Server R2, Windows Vista, Windows 2008 Server, Windows 7 (Professional / Ultimate) Operating systems 64 Bit: Windows Server 2003 (Enterprise/Standard), Windows Server 2008 (Enterprise/Standard), Windows Server 2008 R2 (Enterprise/Standard), Windows 7 (Professional/Ultimate). The latest service pack has to be installed in all cases. one- Attendant Server with other server components (i.e. Exchange, Lotus Domino etc.) : PC with 2 GHz 4 GBytes RAM (recommended 6 GBytes) 700 MBytes available disk space (depending on data) 100 Mbit/s Ethernet IP connection If ComMan for connection of SVA MAnager(Extended Busy Lamp) to the Integral 55 with E07 is used and installed on the server, a ISDN S0 adapter is necessary. System requirements: Client The PC running the one- Attendant application must meet the following minimum requirements: PC with 2 GHz 1 GBytes RAM, Depending on the configuration and installation of other components (for example MS-Outlook, MS-Word) 350 MBytes available disk space (depending on data) 19 -monitor with 1280x1024 pixels. (or a 21 monitor for visually impaired users) 1 free COM interface if a Braille module is connected. Printer with graphics capability for printing charges and statistical data. In Road Warrior mode: Only USB Headsets with DSP or USB phone. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 14 of 123

15 In Telecommuter mode: Any telephone that can be reached from theacm. Operating system 32 Bit: Windows P, Windows 2003 Server, Windows 2003 Server R2, Windows Vista, Windows 2008 Server, Windows 7 (Professional/Ultimate). Operating system 64 Bit: Windows Server 2003 (Enterprise/Standard), Windows Server 2008 (Enterprise/Standard), Windows Server 2008 R2 (Enterprise/Standard), Windows 7 (Professional/Ultimate). The latest service pack has to be installed in every case. Running Softconsole and one- Attendant in parallel Softconsole and one- Attendant cannot be run in parallel on the same PC. However, parallel running on the same ACM on different PCs is possible. System requirements: Single user A PC with a single user solution must meet the following hardware and software requirements. PC with 2 GHz 2 GBytes RAM (recommended 4 GBytes),depending on the configuration and installation of other components (for example MS-Outlook, MS-Word) Operating system 32 Bit: Windows P, Windows 2003 Server, Windows 2003 Server R2, Windows Vista, Windows 2008 Server, Windows 7 (Professional/Ultimate).Operating systems 64 Bit: Windows Server 2003 (Enterprise/Standard), Windows Server 2008 (Enter prise/standard), Windows Server 2008 R2 (Enterprise/Standard), Windows 7 (Professional/Ultimate). The latest service pack has to be installed in every case! 800 MBytes available disk space (depending on data) 19 -TFT-monitor with 1280x1024 pixels (for visually impaired users a 21 -TFT-monitor) 1 free COM interface if a Braille module is connected. In Road Warrior mode: USB Headsets with DSP or USB phone. In Telecommuter mode: any telephone connected to your PB. You will need a printer with graphics capability to output charges data and statistical data. Running Softconsole and one- Attendant in parallel Softconsole and one- Attendant cannot be run in parallel on the same PC. However, parallel running on the same ACM on different PCs is possible. Client server LAN connection Client and server must be connected via a LAN offering sufficient bandwidth. Avaya Communication Manager system requirements Version The ACM with which the one- Attendant is connected must be version 3.1 or higher. If you want to use the network wide busy display, you must also connect an AES version or higher. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 15 of 123

18 Licenses overview The table below shows which one- Attendant licenses you need for using the different features. Material Code Name of license Name of license in *.lic Effects on one- Attendant ONE ATTENDANT CLIENT NEW USER LIC VALUE_1ATTD_CLIENT Basic license for new customers, this is pre requisite for the one- Attendant client to start Value range: integer ONE ATTENDANT CLIENT UPG USER LIC ONE ATTENDANT ETL DATABASE LIC ONE ATTENDANT PRESENCE LIC ONE ATTENDANT ETENDED BUSY LAMP LIC VALUE_1ATTD_CLIENT FEAT_1ATTD_ETERNAL_ DB FEAT_1ATTD_PRESENCE FEAT_1ATTD_ETENDED_ BUSY_LAMP Basic license for a Softconsole upgrade, this is pre requisite for the one- Attendant client to start Value range: integer 1 Required for connecting external data sources. Only one license is required per system. Required for the functions: - Absence from calendar, - Absence from Outlook or Notes - Web Server (basis for AIS and For all ways of signaling the network wide busy states. One license per system will be needed, which monitors up to 20,000 extensions. Installing one- Attendant Setup types The following setup types are available for installation of one- Attendant. You must use the correct setup type based on the application. Client Installs one- Attendant without database. Use this setup type for a client server solution. Before you can install the one- Attendant client, you must install the one- Attendant server (database) on a suitable PC. For the one- Attendant client you need the host name or TCP/IP address of the one- Attendant server as well as the name of the one- Attendant database. The following avaya asa date separator error are installed: All Client components JRE (Java Runtime Engine) iclarity IP Audio Server Avaya One- Attendant V3.02 CM Service and Installation Manual Page 18 of 123

22 5. Click Next. The Password dialog opens. Enter the password for accessing the one- Attendant database which you set when you installed the server. 6. Click Next. The Setup type dialog opens. If you want to use the network wide busy display, you must establish a connection to an SVA-Manager. To do this, select the Yes option. 7. Click Next. The Edit data dialog for SVA Manager opens if you selected Yes in the previous dialog. You must make the following settings: Host Enter the host name of the computer on which the SVA Manager is running. Port Enter the port for accessing SVA Manager. 8. Click Next. The Select additional languages dialog opens, avaya asa date separator error. The default setting is to install all languages currently offered by one- Attendant. Here you can select the languages which you do not wish to install. You do this by unchecking the relevant checkboxes. 9. Click Next. The Ready to 49 error 4c02 the program dialog opens. 10. Click Install. The installation starts. This process takes several minutes. The Setup status dialog indicates the progress of the installation. 11. The last installation dialog, InstallShield Wizard Complete, opens. To end the installation, click Finish. Note If the client installation finds Lotus Notes (various versions) on the PC, the database name is checked on the server where the calendar function is set up. The Lotus Notes COM interface is avaya asa date separator error as well. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 22 of 123

27 Program window The program window is split in a tree view on the left and a work area on the right. The tree view allows you to select settings for various tasks. The possible settings for the topic marked in blue are sown in the work area. The settings for SVA Manager have to be made under the various topic areas. Avaya asa date separator error following table lists all the settings necessary for configuration of a SVA Manager to an Avaya Communication Manager. Further information on all the settings which can be made using QConfig is provided in reference /3/. Note: For security reasons, please change the login password immediately after the first start of QConfig. The change is made in the topic General > Config Protection > Password > Set. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 27 of 123

30 Absence Info Server (AIS) The one- Attendant Absence Info Server is a separate program for monitoring the out of office (OOF) status of all mailboxes of an exchange server (out of office reply in Microsoft Outlook enabled). It works with the Exchange Versions 5.5, 2000.,2003, The absence display for one- Attendant is updated regularly (using the web server). Requirements This requires that the WebAccess component is installed. You must have FEAT_1ATTD_PRESENCE licenses to use the absence notice. Preparations on Exchange A user is identified between one- Attendant and Exchange by the address. This address can be made available to one- Attendant in its own database or in a connected customer database. Each record used must contain both the address and the number. 1. General preparations on Exchange: Absence Info-Server (AIS) generates its own Mapi-profile and establishes a Mapi-connection if one has not been established (for example, avaya asa date separator error, on PCs that are not part of a domain). The rights of the local user running the service apply to the Mapi-connection. This user must be set up on the Exchange Server. Notes on setting up Exchange can be found in this manual. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 30 of 123

32 Example: host: localhost; port The AIS Config UI is started automatically at the end of the installation. AIS Config UI You can use the AIS Config UI to set all connection parameters, set additional options, select mailboxes, and start and stop the service. Start the AIS Config UI using a shortcut in the Start menu or on the desktop. Main avaya asa date separator error Button Connection Opens the Connection dialog Option Opens the Options dialog Selection Opens the Selections dialog Stop Stops the service Start Starts the service Refresh (icon) Quit Determines the current status of the service Quit Ends the AIS Config UI Connection: Group Function Exchange Server Here you can adjust the connection parameters forexchange Server.The Check button tests the connection to the server. The result is displayed in a dialog box and output via TTrace. You must restart the service and Config UI for changes to avaya asa date separator error settings to take effect, avaya asa date separator error. Web server Here you can adjust the connection parameters to error during capture error code 00000000 web server. The Check button tests the connection to the web server. The result is displayed in a dialog box and output via TTrace. You must restart the service and Config UI for changes to the settings to take effect. TTrace The level defines the outputs that are generated in addition to the general I nformation. The options are: Error: Information messages and errors are output. Warning: Information messages, errors and warnings are output. Debug: Information messages, errors, warnings and detailed troubleshooting messages are output. The default setting is Warning. These settings take effect as soon as you click OK. Options: Option Effect Poll interval Specifies the minimum time there must be between the starts of two polling cycles. Default: seconds (240 minutes). If a cycle lasts longer than the set polling time, the next cycle starts 30 seconds after the previous cycle, avaya asa date separator error. Delay Waiting time in milliseconds after an individual mailbox has been processed. Default: 0, avaya asa date separator error. Effect Selection: Button Function Select Selects the checked mailboxes for processing using AIS. The selection is saved in the AbsenceInfoServer.sel file, avaya asa date separator error. The file is located in the same directory as AbsenceInfoServer.exe. Deselect Clears a selection Select all Selects all listed mailboxes for processing using AIS Deselect all Clears the selection for all mailboxes Select all The complete list of mailboxes are prompted from the server in each update (dynamic) cycle and compared with the list of actual selected. If the option is set, all mailboxes are set processed automatically. If the option isn t set, avaya asa date separator error, only the selected and newly found mailboxes are processed. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 32 of 123

33. Entries in the Windows Registry Various entries are written to the Registry during installation. TTrace entries are located under the key HKEY_LOCAL_MACHINE\Software\avaya\AIS The remaining entries are located under the key HKEY_LOCAL_MACHINE\System\CurrentContolSet\Services\AbsenceIN foserver\parameters Note on absence display In the one- Attendant, an absence notice is only displayed for a subscriber. The subscriber is also listed as absent in Outlook. Calendar information You can use Outlook or Lotus Notes to query calendar information (although you can only use avaya asa date separator error or the other at a time). one- Attendant s busy display or network wide busy display then shows the relevant information for all subscribers. Requirements The user of the client computer must have access rights to the calendar data of all subscribers. You must have FEAT_1ATTD_PRESENCE licenses to use the calendar information. Installation No installation is required. The calendar information is automatically available with the client installation. WebAccess Web interface One Attendant provides a web interface for subscribers (called WebAccess). This interface allows a subscriber http error 500 internal to servor is indicate absence nformation (e.g., out of office) from any PC with a browser., avaya asa date separator error. Standard access is via the web address Attendantwebaccess/Login.jsp, which you can enter directly into your browser. host and port must be replaced with the machine name and port of the Tomcat web server, e.g. This interface can also be accessed using program commands. This requires that the programming language used must offer web programming capability. Current programming languages such as Visual Basic, Visual C++, Java, etc. meet this requirement. Programmable functions You can use the following five functions: Login, Logout, Set password, Set presence/absence, Query presence/absence. The way you access these functions depends on the programming language. In general, however, you use commands which will be sent via the HTTP protocol. The parameters and associated URLs are listed in the following paragraph. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 33 of 123

36 3. Select the control box Default CM Format. 4. Click on the. -button and select the exported file. 5. Click on Start. Please note that depending on the volume of your data the import may take a few minutes. There is a bar showing the progress of the import. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 36 of 123

38 Tree view Avaya asa date separator error tree view contains all the tools. The tool currently shown in the work area is highlighted in blue. A green check mark indicates that the tool test was successful. A red exclamation mark indicates a problem with this tool. A black question mark indicates that the tool cannot be tested. Click on a tool to load it to the work area. Properties Properties opens a dialog which you can use to edit the program settings (one- Attendant Config tool, properties). The drivers listed in the table below are available for selection when you define a data source. When you make a selection, the corresponding default URL is entered. Key Value Note DBPwd sql Password for the one- Attendant database DNS one Attendant ODBC link to the one- Attendant database Language DE Language of the one- Attendant configuration borland bde error 2108 collection jdbc.driver.class.1 sun.jdbc.odbc.jdbcodbcdriver Driver 1 for accessing ODBC data sources jdbc.driver.class.2 com.sybase.jdbc3.jdbc.sybdriver Driver 2 for direct access to Sybase databases (ASA and ASE) without ODBC jdbc.driver.class.3 com.octetstring.jdbcldap.sql.jdbcld Driver 3 for accessing LDAP data sources ap jdbc.driver.class.4 ianywhere.ml.jdbcodbc.jdbc3.idriver Driver for direct acces to Sybase Database (ASA and ASE) from Version 9 and higher. jdbc.driver.class5 jstels.jdbc.csv.csvdriver Driver 5 for accessing Text respectively CSV- Files jdbc.driver.default_url.1 jdbc \:odbc \:<Enter DSN here> Default provider URL for driver 1 jdbc.driver.default_url.2 jdbc \:sybase \:Tds \:<server>\:<port> Default provider URL for driver 2 jdbc.driver.default_url.3 jdbc \:ldap \://<server>\:389/ Default provider URL for driver 3 [BASE_DN ]?SEARCH_SCOPE \:\=subtreescope[&pagesize \:\=n ] jdbc.driver.default_url.4 jdbc.ianywhere:<enter DSN here> Default Provider URL for Driver 4 jdbc.driver.default_url.5 jdbc:jstels:csv:<enter directory here>?separator=;&charset=utf-8 Default provider URL for driver 5 Avaya One- Attendant V3.02 CM Service and Installation Manual Page 38 of 123

39 phonebookhost localhost Host on which the phone book server (JOnAS) runs phonebookport Port on which the phone book server listens Avaya One- Attendant V3.02 CM Service and Installation Manual Page 39 of 123

40 Tools: AbsenceInfoPusher Settings cycle (sec) - AIP query interval Host - AIP host name Test Port - AIP port Buttons The Save button saves the changes to the database. The Check connection button checks whether AIP can connect to the JOnAS server using the URL. The result is displayed in the gray text box. The Start button launches the AbsenceInfoPusher. The Stop button stops the AbsenceInfoPusher. Testing To check the connection, proceed as follows: 1. Enter a new free Test Port. 2. Save the new setting with the Save button. 3. Stop the AIP with the Stop button, avaya asa date separator error. 4. Start the AIP again with the Start button. 5. Test the connection using the Check connection button. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 40 of 123

42 Name Comment Example Country code Indicates the international country code. 49 for Germany. International Indicates the international prefix, avaya asa date separator error. 00 National Indicates the national prefix. 0 Area code Indicates the area code. 711 for Stuttgart Local PB Indicates the PB number Example If you enter an internal subscriber with the number 1234, the converted shadow number looks like this: Countrycode Area code Local PB Extensioncode Settings: Call Number Replacement one- Attendant uses the settings on the Call Number Replacement tab to identify a subscriber of a networked system even if the subscriber places an external call. The PB handles subscribers in a networked system like internal subscribers. The address parser always creates a shadow number with its own code numbers for this purpose. Therefore, when there is a call, the PB-numbers of external locations must be re avaya asa date separator error using the own code numbers avaya asa date separator error if necessary the node numbers. Note the following regarding call number replacement You must always enter numbers with the country code and area code, for example Settings: Area codes In a PB or PB network, there may be differences in how external connections are dialed and how they are stored in ACM. For example, in the Paris subsidiary, all the internal numbers could be saved with a preceding 123 in ACM: Number saved in ACMexternal number In the Area codes tab under Prefix enter the access number for the PB (7505) including all prefixes, e.g and under subst. head the associated digits of the internal number, as they are stored in CM, e.g Fixed Numbers In some cases with outgoing dialing (e.g. out of phonebook), the numbers must not be parsed. In Germany for example, there are some special numbers like 112 and 110 where it isn t allowed to put the area code in front ( isn t possible). Enter such numbers in the tab Fixed numbers, they would be dialed without putting trunk code or area code in front. This means here and in the phonebook the number has to be inserted with trunk code (e.g if 0 is trunk code). Example for call number replacement with a closed numbering scheme PB 1 in Stuttgart Number: PB 2 in Frankfurt Number: We are at PB 1 in Stuttgart. If you want to enter a subscriber from Frankfurt with internal number 1234 in the phone book, the address parser generates the following shadow number: Avaya One- Attendant V3.02 CM Service and Installation Manual Page 42 of 123

43 Country code Area code Local PB Extension Settings in call number replacement You must enter the following information for the example. From To PB number of the external location PB number of own location Example of call number replacement with an open numbering scheme PB cups ubuntu 11.04 client-error-forbidden in Stuttgart Number: Node number: 88 PB 2 in Frankfurt Number: Node number: 99 We are at PB 1 in Stuttgart. If you want to enter a subscriber from Frankfurt with internal number in the phone book (99 is the node number for Frankfurt), the address parser generates the following shadow number: Country code Area code Local PB Extension Settings in call number replacement You must enter the following information for the example. From To Country settings If you select France, Spain, Russia or USA from the mode-option fields, other country-specific configuration field will be offered to you. In case of a phonebook application entries have to be found by the phone number. Therefore each entry bears a phone number in a visible user format and in a invisible normalized format (ShadowNumber). When an entry is written into the database the normalized phone number is generated by the AddressParser. The user format is (nearly) arbitrary. It depends on how the user enters the phone number or how the phone number comes out of an import or connected data source. Phone numbers send by the PB are also treated as numbers in user format. This chapter describes how the AddressParser works and how it has to be configured. The address parser is only used to uniquely identify a record from the phone book entries. The address parser must be configured error 11 unrecognized drive string that a record can be uniquely identified and the corresponding features in the one- Attendant application (for example, subscriber properties) work correctly. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 43 of 123

44 Definitions Numbering Plan A numbering plan is a type of numbering scheme used in telecommunications. This is a set of rules used for making numbers. A telephone numbering plan is a plan for allocating telephone number ranges to countries, regions, areas and exchanges and to non-fixed telephone networks such python keyerror none mobile phone networks. Open Numbering Plan Open numbering plans have phone numbers that vary in length like in Germany. Closed Numbering plan Phone numbers in a closed numbering plan have a avaya asa date separator error length like in the USA. Dial Plan A dial avaya asa date separator error specifies the actual digits dialed within the constraints of a defined numbering plan. A typical dialed telephone number comprises sql logic error that need not always be dialed (codes) and digits that must always be dialed (local number). If a dial plan consists of slices (blocks) of DIDs where station numbers are ambiguous it is called heterogeneous. Example: Dial plan consists of two blocks of numbers. Slice 1 from to Slice 2 from to 5500 Stations 5000 to 5500 are in both slices. If a dial plan consists of slices (blocks) of DIDs where station numbers are unique it is called homogeneous. Example: Dial plan consists of two blocks of numbers. Slice 1 from to Slice 2 from to 1500 No station is in both slices. ShadowNumber The ShadowNumber is the invisible unique version of an arbitrary phone number. It is used as a key to searches in the phone book database. Dialable number The dialable number is that number that can be dialed after AddressParser processed a ShadowNumber. PBs in a networked system If multiple PBs are connected in a network, you also need the Call Number Replacement tab. one- Attendant uses this information to identify a subscriber of a networked system even if the subscriber places an external call. Call number replacement converts a call s number. You must specify the digits used in the search and what replaces them. Open the number scheme and on the Call Number Replacement tab assign the PB numbers to the node numbers. This replaces the PB number of the external location with the PB number of its own location and the node number of the external location. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 44 of 123

45 If the numbering scheme is closed, you only need to specify the PB numbers of the locations. This replaces the PB number of the external location with the PB number of its own location. Settings: Code numbers When you enter an internal subscriber in the phone book, the address parser adds the number and corresponding code number. The user cannot see the converted number. The number is saved in a shadow database. The user always sees the number in avaya asa date separator error phone book in the form he or she entered it. Standard, France, Spain, Russia and USA modes are possible. Tools: one- Attendant A separate sheet is displayed in the tree view for avaya asa date separator error one- Attendant client that has connected to the database at least once. The selected sheet consists of two table avaya asa date separator error. The Property Name and Property Value columns let you edit the properties. Buttons / Check The Save button saves the changes to the database. The Check button checks only the EJBSrvHostName and EJBSrvPortNo parameters. If a check fails, the entry responsible is highlighted in red. Once this entry is corrected, it is displayed in black again. Note on SVAMUsage parameter If no SVA Manager was installed during the client installation, then this shows 0 (otherwise 1 ). If an SVA Manager is installed later, the value 1 has to be entered manually on all clients. 02 CM Service and Installation Manual Page 45 of 123

46 EJBSrvHostName EJB server PC name (phone book server) (Default = localhost ) EJBSrvPortNo EJB server port number (phone book server) (Default = 21099) ForceBlockdialCM GlbSearchFilterField ImExportTransferMode NbaPumDefault NoCallIdentification OffsetSACSignalling OSType OSSoftwareVersion PUMLOgginTimeout SearchDelayTimeCC SearchDelayTimeST SearchNumberHead ShowSubstituteRemar k SVAHostNameIPL When using block dialing, e.g. using a destination key, the CM sends the number immediately without waiting for further inputs (0 = OFF (default), 1 = ON) Prefilter for topic calls (all phone book fields listed; default = company) Codepage format of the ex/imported phone book data (0=Default Codepage, 1=ISO 8859_1, 2=UTF 8, 3=UTF 16 BE, 4=UTF 16 LE, 5=UTF 16) Default size configuration for Personal User Mobility (PUM) and network wide busy display (Default = 200) Switches off number identification (0 = OFF (default), 1 = ON) Offset for send all calls signalisation (Default:0) OS hardware ( ACM ) OS software version (Default), 02.00, 01.51, avaya asa date separator error, ) Wait time for the PB answer for PUM user logon (sec, default: 5) Search delay time for the calling card (msec, default = 400) Search delay time for the lookup table in the phone book (msec, default = 400) Head number search (0 = OFF, 1 = ON (default)) Display substitute text as the topic (0 = OFF (default), 1 = ON) SVA Manager PC name for QTAPI (Default = "localhost SVAMHostName SVAMPortNo SVAMPortNoIPL SVAMUsage SystemLanguage Top100Support TransferOnBusy TTracePortNo TTraceHostName SVA Manager PC name (Default = localhost ) SVA Manager port number (Default = 6006) Port number for the QTAPI SVA Manager port (Default = 10405) Operate with or without SVA Manager (0 = OFF, 1 = ON) System language (Default = system language, e.g. en) Collect call-information for the Top100-display (1 = ON (default), 0 = OFF) Can be assigned to busy subscriber; no effect if one- Attendant is connected to ACM (1 = ON (default), 0 = OFF) TTrace server port number (Default = 10300) TTrace server PC name (Default = localhost ) Avaya One- Attendant V3.02 CM Service and Installation Manual Page 46 of 123

47 Avaya One- Attendant V3.02 CM Service and Installation Manual Page 47 of 123

48 Tools: JOnAS (phone book server) Buttons The Save button saves all changes and configures all available clients accordingly. The Restart JOnAS button stops the service and restarts it with the changed settings. The following table explains the text boxes and check boxes. Note When you have restarted JOnAS, you also need to restart all related services, such as AbsenceInfoPusher, WebAccess and Update Service. Server Registry Port Port on which the phone book server listens. Default = Remote Object Port Transaction timeout Cache active limit max. size (number of Records) Search result size Search result Port which should be used to transfer the search results to the one- Attendant. Define a port here if a firewall is installed between one- Attendant and the phone book server. (Default=0, i.e. dynamic) Timeout in seconds, the maximum time that the processing of a search query may last. Default = 120 Cache Select if you want to cache the search results. This can speed up a new search. Select if you want to restrict the memory for the cache. The search result size entered here will not be exceeded. The oldest entries in the cache will be deleted when more recent entries are to be written to the cache. The recommended max. size is 10,000 records. Search result Number of records transferred from the server to one- Attendant when a search returns more results. Default = 50 The timeout time in seconds for which a search result remains valid on the server. Records that are not queried are discarded after the timeout. Default = 120 Settings for large databases If you run one- Avaya asa date separator error with a large database (> 5000 records) or if it is linked to large databases, you must assign JOnAS more memory. You can do this when you configure the JOnAS service (Avaya Phonebook Server) in the Jonas.conf file. 1. Open the Jonas.conf file in a text editor. It is located in: c:\avaya\servers\serviceconf\ 2. Find the line wrapper.java.maxmemory in the wrapper properties. 3. Change the default-value from 64 (which means 64 MB) as required. 136 MB is enough for 15,000 records. 4. It may also be necessary to change the default time for transaction timeout. You can do so using the one- Attendant config tool on the JOnAS tab. We recommend increasing the time to 300 seconds. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 48 of 123

49 Tools: Phone book A separate sheet is created for each data source. You can define data sources and configure c00002la fatal system error field assignment using an index definition on the sheet. For examples of connecting to different data sources, see LDAP connection. Connection tab The Reload button discards the last changes, reloads the settings from the one- Attendant database and runs the SQL statement. However, no data is loaded into the one- Attendant database! Upcase table incorrect error#1627 New button creates a new data source and populates the fields with default values. The Save button checks the settings and saves the configuration data in the one- Attendant database. The Delete button deletes the active data source. If avaya asa date separator error data source is deleted, all records of that data source are automatically deleted at the same time. The Remove records button deletes all records of the data source just selected from the database. Name and Description The Name and Description fields describe the data source. The name is needed to uniquely identify a data stream. The name appears in the combo box of the one- Attendant phone book. Drivers The field Drivers contains a list of the available JDBC drivers. The driver displayed is loaded, avaya asa date separator error. The list can be added to in the one- Attendant- ConfigTool.properties file. If you select a driver from the list, the Provider URL box is populated with the corresponding URL schema by default. The name of the JDBC database driver can be found in the database documentation or the driver documentation (e.g. for a JDBC-ODBC bridge it is sun.jdbc.odbc.jdbcodbcdriver). Provider URL The Provider URL field contains the connection parameters. The URL points to the database to be connected, and has the following format: jdbc:<subprotocol>:<subname> subprotocol 1603. getlasterror = 127 to the JDBC class with which you are working (e.g. for a JDBC-ODBC bridge, this is odbc). subname provides information that is needed to locate the database (e.g. for a JDBC-ODBC bridge, this is a DSN from the ODBC data sources). The syntax of subname is dependent on the driver and can be found in the documentation for the database or the driver. For SYBASE, this information is in the SYBASE manual. User Shows the user for the database. Password Shows the password for the database as * SQL statement The SQL statement field contains the SQL query used to retrieve the data from the data source. Avaya Avaya asa date separator error Attendant V3.02 CM Service and Installation Manual Page 49 of 123

50 Transaction timeout The Transaction timeout contains the time in seconds after which a hanging transaction is ended if necessary. This information is also important for updates. The maximum value is 3600 seconds. Commit Transaction If a transaction takes longer than 1 hour it will automatically be canceled. With the option Commit Transaction you can configure the number of records, according to which the transaction is automatically confirmed (committed). Then begins a new transaction and the timer can not strike if the number is selected small enough. This configured automatic commit has the disadvantage that the final data will be stored into the database and if an error does occur the original state can be restored. A value of 0 disables the automatic Commit Transaction. Result (gray display window) The Result field contains messages which give an indication of any possible errors. Assignment tab Index The Index column selects the fields of the data source which make a record unique (the primary key). one- Attendant needs a primary key to be able to work with the customer data. This primary key can be the primary key of the customer database. You can also use several fields as the primary key. This is referred to as a composite primary key. one- Attendant uses this primary key for the shadow database. Caution: None of the elements of the primary key can be blank for any of the records! Source field The Source field column contains all the fields read out of the database. Target field The Target field column contains the assigned destination fields of the one- Attendant phone book. All the fields which are defined in the one- Attendant phone book are possible! The fields are displayed in the language of the one- Attendant configuration tool collection. For the Gender field the source value must be m or M for male, and f or F for female, avaya asa date separator error. All other values will be interpreted as undefined, avaya asa date separator error. CM Name (last name, first name) isn t a real phone book field. If you choose this as target field and the content of the source field has the format (last name, first name), then it will be split into the phonebook fields (last name) and (first name). This will be usually used for importing data from text files which are created via Avaya Site Administration (ASA) export. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 50 of 123

51 Tools: Update service The update service connects the external data sources (Exchange, Domino) with the phone book server (JOnAS). A separate sheet is created for each data source that was created in the phone book. One click on a sheet opens the vba application-defined or object-defined error 1004 settings in the work area. Data sources that do not have an enabled update service are not listed in one- Attendant as data sources. Caution: Records from these data sources are nevertheless found when you search for all data sources! Buttons The Save button saves configuration data in the one- Attendant database. This data only becomes active after the update service has been stopped and then restarted. The Check connection button tests whether the data sources can be reached by the update service. The Start button launches the update service. The Stop button stops the update service. Check connection To check the connection, proceed as follows: 1. Enter a new free Test Port. 2. Save the new setting with the Save button. 3. Stop the update service with the Stop button. 4. Start the update service again with the Start button. 5, avaya asa date separator error. Test the connection using the Check connection button. If necessary, you can read the results of the test in the updateservice.log logfile in the server directory Avaya\Servers. Tester/Services Host Test Port Name of the host on which the update service is installed. TCP error siocgifflags no such device port of the update service. Information for each database Earliest run (date, time) The Earliest run (date, time) fields define the earliest time that the update service should start. Interval The Interval fields define the how often the update service should run (value and unit). Activated In the Avaya asa date separator error check box, each database must be selected which should participate in the update service, avaya asa date separator error. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 51 of 123

52 Tools: WebAccess Buttons / connection testing Lets you test whether the Web server (Tomcat) connects correctly to the phone book server (JOnAS). The Check connection button checks whether the Web server connects correctly to the phone book server (JOnAS). Save avaya asa date separator error configuration data in the one- Attendant database. This data is only active when the WebAccess is stopped and then restarted. The Start button launches the WebAccess service. The Stop button stops the WebAccess service. Host Web server port Name of the host on which WebAccess is installed. Note Port on which the WebAccess is listening You need to specify the Web Server Port if you are using AIS or applying the absence display via a browser. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 52 of 123

53 Tools: External Call Detection Motivation: Avaya one- Attendant Service and Installation Manual shows in chapter 1 the block diagram of one- Attendant at CM. Scapi is the signalling interface between one- Attendant client and CM. Scapi is an Api designed for Avaya SoftConsoleanother Avaya attendant. It doesn t provide direct Information whether a call is external or internal. For this reason one- Attendant uses different indications in the from Scapi received events. The following chapters describe these indication and possible problems One- Attendant uses external number detection basically for redial and call list. Because Scapi doesn t provide the ARS Code for public network with external numbers, one- Attendant has to add socket error 10053 in outlook code for outgoing calls. Operator Window Figure 1: one- Attendant Operator Window showing an external call The operator window of one- Attendant GUI displays, whether an outgoing call is internal or external. In Figure 1 shown above, the call number is marked external (by displaying the text label Outg. Trunk ) because the following optional criteria has been configured with one- Attendant GUI: Figure 2: one- Attendant menu item for external call numbers Avaya One- Attendant V3.02 CM Service and Installation Manual Page 53 of 123

54 Figure 3: one- Attendant configuration dialog for external call numbers Extended Redial List Figure 4: one- Attendant Extended Redial List A call number is marked external or internal in the extended redial list. A double click on the call number optican flasher error the ARS Code for public network in front of the call number in case of an external call. Call List Avaya One- Attendant V3.02 CM Service and Installation Manual Page 54 of 123

55 Figure 5: one- Attendant Call List A call number is marked internal or external in the call list (One-Attendant GUI doesn t show it). A double click on the call number dials the ARS Code for public network in front of the call number in case of an external call and operator window shows Outg. trunk. Hint: All other dialing possibilities (net wide busy view, phone book, etc.) are handled with the Address Parser, that is handled in an extra chapter. Criteria for external call detection in One-Attendant v3 Processing of incoming calls by one- Attendant connected to CM Avaya One- Attendant V3.02 CM Service and Installation Manual Page 55 of 123

56 Figure 6: one- Attendant state machine for processing of incoming calls The critera a) to d) shown in figure 4 work as follows: serial call criteria: calls with sc as call type in display string received from Scapi (attendant serial calls) are marked as external (not configurable). Avaya One- Attendant V3.02 CM Service and Installation Manual Page 56 of 123

57 Incoming calls with call number length of the remote calling party greater than or equal to the in One- Attendant menu for external call numbers configured number. are marked as external. 0 digits means switch-off this criteria: Figure 7: one- Attendant configuration dialog for external call numbers Checkbox Call from/answered By criteria: incoming calls with call from or answered by identification in display string are marked as external. This criteria is configurable simply by checking or unchecking it. (see Figure 7) Incoming calls with ldn identification in display string (ldn = long distance calls on DID trunks) are marked as external. This criteria is not configurable. Processing of outgoing calls by one- Attendant connected to CM In addition to criteria for incoming call listed above, outgoing calls are marked external, if the ARS code for public network is dialled in front of the number call (i.e. in operator window). This criteria is configurable for a choosen one- Attendant work profile. Figure 8: one- Attendant Switching Options dialog The ARS code 0 configured in Figure 8 is automatically dialed in front of the call number in case dialing an external number out of call list (see Figure 5) dialing an external call number out of redial list (see Figure 4) of an assigned dialed number or a block dialed number begins with + (i.e. out of phone book or NBA) Avaya One- Attendant V3.02 CM Service and Installation Manual Page 57 of 123

58 Example The following example shows how criteria b) for avaya asa date separator error calls can influence the external call detection. Assume that 6 is the length configured as minimum length of external numbers and 0 is the configured ARS code: Figure 9: Example showing wrong external call number configuration Figure 10: Example showing Switching Options configuration Now we call an internal station via QSIG connection: Figure 11: Example showing Operator Window In the operator window, we see text label Outg. Trunk which classifies this call as external. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 58 of 123

59 In the redial list we see that the called number has been added: Figure 12: Example showing Extended Redial List Now we double click on that number to dial it out of redial list, avaya asa date separator error. In the operator window we obtain the following: Figure 13: Example latency test returned an error while trying rejected call in Operator Window The one-attendant has added the above configured ARS code, because the call was marked external in redial list. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 59 of 123

60 Now we change the configuration as follows: Figure 14: Example showing correct external call number confiduration Now we call the same internal station via QSIG again: Figure 15: Example showing internal call in Operator Window We see that now the call is marked internal. The redial list now also shows the call marked as internal : Avaya One- Attendant V3.02 CM Service and Installation Manual Page 60 of 123

61 Figure 16: Example showing internal call in Extended Redial List We now double click on the selected call number and establish the call: Figure 17: Example showing internal call established via QSIG. The call was marked internal so the ARS has not been added. Avaya asa date separator error When you change the above configuration you have to restart one-attendant to activate the changes. Known Problems The optional criteria do not work for every scenario. For example: Dial plans may exist that allows internal numbers to be longer than external numbers, so criteria b) does not work. Sometime calls coming via QSIG or SIP trunks have a CALL FROM identification and it is not allowed to add the ARS for outgoing calls, so criteria c) does not work. By deactivation of these criteria it can happen that an external call, is not marked external, so when dialling the number out of call list or avaya asa date separator error of redial list, the ARS is not added automatically or in display outg. Trunk is missing. Incoming and Outgoing calls on one- Attendant I55 3 rd party External Call Number detection is also a point for one- Attendant at I55 via 3 rd party. In this scenario we have Qtapi-Framework(SVA Manager) instead of Scapi The only criteria for incoming and outgoing calls is the avaya asa date separator error of the call number of the remote calling party. The difference to the CM version is, that call list and extended redial list are filled by the SVA Manager. That means a call number in call list or extended redial list is marked external, if the call number is longer than avaya asa date separator error with the SVA Manager Config-Tool configured value for Max. length internal numbers : Avaya One- Attendant V3.02 CM Service and Installation Manual Page 61 of 123

62 Figure 18: SVA Manager Configuration Tool In one- Attendant operator window, a call is marked external, if the call number of the remote calling party is longer than the configured value in the one- Attendant external call number dialog (see Figure 19) Figure 19: Enternal call number dialog Problems could be the same as described in a) but normally I55 dial plan does not provide internal numbers longer than external numbers. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 62 of 123

63 Maintenance, problem solving Troubleshooting TTrace TTrace allows you to generate and administer log files. Specifically, it can be used to record the traffic between the one- Attendant client and OS_TAPI. More detailed information on installation and operation can be found in references /7/ and /8/. The password for TTrace is Recall message TTrace installation To install TTrace, follow these steps: 1. Insert the one- Attendant installation CD in your CD drive. The Overview start page opens in your standard browser. 2, avaya asa date separator error. Click on TTrace (logging tool). The TTrace window opens. 3. Click on TTrace (logging tool). There is a program to guide you through the installation process. 4. Click on TTrace Update. This runs a batch file avaya asa date separator error replaces some program files.one- Attendant/SVA Manager zero display service error To record one- Attendant, SVA Manager, AIS and other messages, you need to set the correct TTrace server s host name and port number in the configuration tools, avaya asa date separator error. SVA Manager Configuration, avaya asa date separator error, one- Attendant ConfigTools and AISConfig. one- Attendant Info In case of problems with one- Attendant you can use Start > Programs > Avaya > one- Attendant >Avaya one- Attendant Info where you can record all your computer statuses and pass them over to the service department, who can then use this information to check your settings and applications, avaya asa date separator error. The program creates a directory C:\One AttendantInfo containing the informations in separate files. The directory should be zipped and provided to support. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 63 of 123

64 Application Once you have created all users and work profiles, you can back up the database and all entries. You can revert to this data at any time and restore the data. These functions help you to quickly and easily set up an operator position with the usual work profiles and users, if for example you reinstall the operating system. The file OSPCdb.db contains the entire one- Attendant database. You can use tools to back up the database while it is running and restore it when it is switched off. The appropriate tools are set up during the installation process. Backup You can back up the database during operation. Proceed as follows: 1. Click Start. 2. Click Programs. 3. Click Avaya. 4. Click on Backup one- Attendant. 5. If no backup folder exists, the following prompt appears: Directory does avaya asa date separator error exist. Create it. Acknowledge this prompt with Y (yes). The backup folder is created, and the OSPCdb.db database and the JOnAS and Serviceconf directories are copied to the folder. If the OSPCdb.db file already exists, a prompt is displayed asking whether you want to replace the file. 6. You can back up the OSPCdb.db file and both directories on a single drive (for example, a tape drive), avaya asa date separator error. It is recommended to change the file names afterwards and adding the one- Attendant version and date, for example OSPCdb_3v00_ db or moving all files to a suitably named folder. Restore Before you restore the database, you must make sure that the backed up database file OSPCdb.db is located in the backup folder, as subdirectory to the server installation directory (Default: C:\Avaya\Servers). You cannot restore a database when it is running. Proceed as follows: 1. Shut down all one- Attendant clients. 2. Click on Start. 3. Click on Programs. 4. Click on Avaya. 5. Click on Restore one- Attendant. This copies the database and the JOnAS and Serviceconf folders. 6. Press any key, avaya asa date separator error. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 64 of 123

65 Avaya one- Attendant migration from OSPC v2.5x Performing migration If you wish to migrate from an OSPC version 2.5x to one- Attendant v3.00, proceed as follows: First of all: <Serverdirectory new> is by default: C:\Avaya\Servers <Serverdirectory old> is by default: C:\Avaya\Servers The following steps are only for a database update necessary, this will occur if for the according version a update_xxx_xxx.sql file is available. For example at the update from to the file update_v300_v sql. Configuration(Database/SVAManager/JONAS) backup Start > Programs > Avaya > Avaya OSPC > Backup Avaya OSPC respectively Start > Programs > Avaya > Avaya one Attendant > Backup Avaya one Attendant 1. Recommendation: For safety reasons export the Profiles, Users, Phone Book and make screenshots of the Connection\Mapping data for the external Phone Directory in the one Attendant Configuration Tool. If something goes wrong, you can reimport/enter them after a normal installation of the next version. 2. Deinstall old version. Important: Please note database user and database password, because during the installation of the new version these should be used again, otherwise after the update the database libeay32.dll error #0 works no more. 3. Install the new one- Attendant version. 4. Copy files: Copy the files updatedb.bat and all update_vxxx vxxx.sql, avaya asa date separator error, which are necessary for this step of the update, from the Update Directory of the CD \software\one Attendant\DBUpdate into <Serverdirectory new>. For an update from 2.50 towards these files are update_v250_v251.sql, update_v251_v300.sql and update_v300_v sql. If now the Master Directory Application is installed and in the old version not, the entries for an automatic update of the phone book will be deleted during the restore of the configuration(database). If they should be restored, then also the file One AttendantAutoImport.sql out of the directory <Serverdirectory new>\masterdirectory\data> have to be copied in the <Serverdirectory new>., avaya asa date separator error. 5. Customize updatedb.bat Open the file update.bat with a text editor (e.g. Notepad) and change the following texts: SERVERNAME_1A in the name of the database server as stated during the installation respectively located in the registry under the Key [HKEY_LOCAL_MACHINE\SOFTWARE\Avaya\Avaya\OSPC\Setup] in the value DBServer SERVERNAME in the name of the PC as stated under Control Panel > System > Computer name Avaya One- Attendant V3.02 CM Service and Installation Manual Page 65 of 123

66 If during the installation the default values haven t been used, then possibly the following texts has to be changed: The value for ServerDrive (default is C: ) The value for ServerDir ( default is C:\Avaya\Servers ) The value for BACKUPPATH ( default is C:\Avaya\Servers\Backup ) The value for DBUser in the user name for the database server as stated during the installation The value for DBPwd in the password for the database server as stated during the installation The value for DBPort in the port for the database server as stated during the installation respectively located in the registry under the Key [HKEY_LOCAL_MACHINE\SOFTWARE\Avaya\Avaya OSPC\Setup] in the value DBPort 6. Update database Call updatedb.bat (with Windows VISTA and Windows 7 as administrator). 7. If you have chosen the usage of the SVAManager during the installation and you didn t have use before, the entry SVAMUsage in the one Attendant Config Tools after the restore of the configuration(database) is possibly set to 0. This means that usage of the SVAManager is deactivated and the extended busy lamp doesn t work. If you want to use this feature, you have to set entry SVAMUsage to 1 again. Note An upgrade should named tsig indicates error be installed over an existing version. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 66 of 123

67 one- Attendant update Carry out update The installation supports updates avaya asa date separator error Version and higher, no further actions are necessary. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 67 of 123

69 HKEY_LOCAL_MACHINE\SOFTWARE\Avaya Unknown host name You must use the host name when you enter the name of a server. This is how you find out the host name: 1. In order to find out the hostname, open a command prompt (DOS window) on the relevant PC. 2. Enter error 1920. service event log watch /all. 3. Press ENTER. This displays the host name and other IP settings. Sybase database in the network with the same name If there is a Sybase database with the same name (one- Attendant) in the network (LAN), a message to this effect is displayed. Note: The name for the one- Attendant database can only be entered during installation. The name of the one- Attendant database cannot be changed later on. Distinction between external and internal numbers is not working Sometimes, the distinction between external and internal phone numbers in the one- Attendant phone book does not work. Make sure that all external numbers are entered with a prefix, even if they are in the same area code as you. This is the only way to save numbers avaya asa date separator error that they are unique. one- Attendant does not start at all Problem: When starting one- Attendant, the splash screen (welcome screen) only appears briefly. There is a problem with the Java installation! In the Control Panel, the Java plugin must be set to Default, and under the PATH system variable, no path to a JRE should be entered. one- Attendant does not start after a restart Please note that one- Attendant will not start while the iclarity process is still running. This can happen if the one- Attendant did not close properly. End the OSPC.exe process and restart one- Attendant. one- Attendant does not dial If the one- Attendant seems to be working correctly but still will not dial, avaya asa date separator error, this can be due to an incorrect configuration of the bandwidth settings. Access the system configuration and correct any incorrect settings in the TEL tab. Recommendations on configuring feature buttons For the feature buttons you should only use the pre set functions (see appendix) or such functions that can be catalyst mobility download error using an avaya asa date separator error code. The special characteristic of these functions is that they can also be run using individual dialing in one- Attendant (e.g. access code for trunk line, ACW/Wrap up time, speed dialing keys, etc.). Other functions may cause the ACM to send responses to the one- Attendant, which are then displayed there in a misleading way and may cause a malfunction. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 69 of 123

70 Name reconciliation on show php errors on page one- Attendant / ACM database When a number is redialed, deflected to one- Attendant or diverted, avaya asa date separator error, ACM transfers only the name of the person being called as entered in the ACM database to the one- Attendant, not the internal number. For normal calls, the number is transferred from the ACM to the one- Attendant. The number is identified and the name displayed using the one- Attendant database. In order for a subscriber to always be displayed with the same name within the one- Attendant, the records within the ACM and the one- Attendant databases must be identical. You can achieve this by importing the records from the ACM into the one- Attendant database. Additional tips For more tips and tricks, visit the Avaya Enterprise Portal Once there, go to the Technical Center and, under Applications, look for one- Attendant. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 70 of 123

71 Appendix Avaya One- Attendant V3.02 CM Service and Installation Manual Page 71 of 123

72 LDAP connection (LDAP browser) examples LDAP connection (LDAP browser) Before configuring an LDAP connection you should first check the connection using the LDAP browser\editor tool. For this, copy the LDAPBrowser directory from the CD in directory software\service Tools to a local drive (with write access rights). To start the tool double click lbe.jar or if the system does not detect Java Runtime (basic one- Attendant installation), double click OSPC-lbe.bat. The Connect window opens. The Session list tab contains a few sample connections. Use the Edit button to view and modify the settings. If the name is changed (tab: Name), then a new connection configuration (session) will be created. The Connection tab displays the connection parameters. In Exchange, be sure to enter the PC which is running Active Directory. This is not necessarily the Exchange Server. Next click Fetch DNs to obtain a list of Base DNs (Domino (the IBM MAil Server, Lotus Domino) shows an empty list). Select the shortest entry. First, select an anonymous connection (Anonymous bind), click Save and in the Connect window click Connect. You should be able to see at least the BaseDN entry. Now enter an appropriate user and the user s password. You may be required to enter the user with the complete path (see Exchange2k_Lab login and Exchange2003_Lab login examples). To do so, you will need the support of your system administrator who will advise you in which substructure the user that you are utilizing is located. Once you have successfully set up the connection, you can transfer the parameters to the phone book tool. The Select-statement in the phone book tool must contain any field you may want to retrieve. After you have selected a user the avaya asa date separator error names will display in the LDAP browser\editor under attributes. Accept the names. Note that names are case-sensitive. Example 1 for data source using a JDBC-ODBC bridge The table below shows an example of the parameters on the Connection tab if you connect to a database using a JDBC-ODBC bridge. Parameter Name Driver Provider URL Password SQL statement Setting JDBC-ODBC bridge Description sun.jdbc.odbc.jdbcodbcdriver jdbc:odbc:sampledsn User admin SELECT * FROM SampleTable Avaya One- Attendant V3.02 CM Service and Installation Manual Page 72 of 123

73 Example 2 for data source directly via JDBC The table below shows an example of the parameters on the Connection tab if you connect to a database directly using a JDBC driver. The database with the name DBN is a Sybase ASA type and is located on the PC with the host name dbserver with port Parameter Name Driver Provider URL User Password SQL statement Setting AdaptiveServerAnywhere com.sybase.jdbc3.jdbc.sybdriver jdbc:sybase:tds:dbserver:4321 error detected lme279 dba sql SELECT * FROM SampleTable Example 3 for MEDCOM data source using a JDBC-ODBC bridge The table below shows an example of the parameters on the Connections tab if you connect to a MEDCOM database. You have to configure a system DSN for the MEDCOM database. The data source name for this example is Medcom_W2k. In the one- Attendant tool collection, you normally generate two data streams in the phone book tool which both point to the data source Medcom_W2k (in this example). The data streams could be called Staff and Patients, for example. You must use the appropriate SQL query for each data stream, avaya asa date separator error. Parameter Name Driver Provider URL Setting JDBC ODBC bridge sun.jdbc.odbc.jdbcodbcdriver jdbc:odbc:medcom_w2k or jdbc:odbc:; Driver={Adaptive Server Anywhere 6.0}; SRVR=Medcom_W2k User dba password sql SQL statement SELECT * FROM mcuser Example 4 for an LDAP data source using a JDBC-LDAP bridge with general settings The table below shows an example of the parameters on the Connections tab if you connect to an LDAP database. Parameter Setting Name Exchange 5.5 Driver com.octetstring.jdbcldap.sql.jdbcldapdriver Provider URL jdbc:ldap://<server>:389/[base_dn]?search_ SCOPE:=subTreeScope[&pageSize:=n] Note: The URL must not contain spaces (except for immediately in front of the? ). Avaya One- Attendant V3.02 CM Service and Installation Manual Page 73 of 123

74 LDAP connection (LDAP browser) examples Parameter Setting User <Domain>\<User ID> or<distinguished Name of the user (DN)> Examples: Domain\User ID:tnbk1\bek2fr distinguishedname: CN=BEK2FR,OU=Users,OU=Fr, OU=Germany, DC=Avaya,DC=corp,DC=lan Password Avaya asa date separator error SQL statement select DN,givenName,sn,cn,title,mail,telephoneNumber,mobile,homePhone,otherHomePhone,ipPhone,pager,facsimileTel ephonenumber,description,info,physicaldeliveryofficename,streetaddress,postofficebox,postalcode,l,st,co,compa ny,department, extensionattribute5,wwwhomepage,url from ou=orgunit select from ou=orgunit also works, but is not recommended. Example 5 for Exchange 5.5 data source using a JDBC-LDAP bridge The table below shows an example of the parameters on the Connections tab if you connect to an Exchange 5.5 database. Parameter Name Driver Provider URL Setting Your avaya asa date separator error com.octetstring.jdbcldap.sql.jdbcldapdriver jdbc:ldap://fr108033:389/o=ap4?search_scope:=subtreescope&pagesize:=90 Note: subtreescope is important for searching in substructures of DN (distinguished name). This entry is important because a 3ware bios drive error structure occurs only very rarely. User cn=abwospc The name is the key to avoid access problems and to deliver the correct login information. Most domains do not permit anonymous LDAP queries. Password SamplePassword SQL statement select DN,sn,cn,mail,telephoneNumber from ou=defr1009 where sn=* The number of subfolders depends on what you have learned from the special AD schema. In this way, for example, under a main account OU (organizational unit) there could be various other OUs for each region and each country. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 74 of 123

75 Example 6 for Exchange 2007/2003/2000 data source using a JDBC LDAP bridge The table below shows an example of the parameters on the Connections tab if you connect to an Exchange 2007/2003/2000 database. Parameter Setting Name ADS 2000/2003 Driver com.octetstring.jdbcldap.sql.jdbcldapdriver Provider URL jdbc:ldap://fr135120:389/dc=iccdomain,dc=com?search_scope:=subtreesco pe&pagesize:=90 User cn=administrator,cn=users,dc=iccdomain,dc=com Password SamplePassword SQL statement select DN,sn,givenName,cn,mail,telephoneNumber,department from ou=cdm test where sn=* Example 7 for Domino 6 data source using a JDBC-LDAP bridge The table below shows an example of the parameters on the Connections tab if you connect to a Domino 6 database. Parameter Setting Name Domino 6 Driver com.octetstring.jdbcldap.sql.jdbcldapdriver Provider URL jdbc:ldap://fr146025:389?search_scope:=subtreescope User Avaya Password Avaya asa date separator error SQL statement select givenname,sn,cn,mail,telephonenumber from o=ospc_org Example 8 for Domino 5 data source using a JDBC-LDAP bridge The table below shows an example of the parameters on the Connections tab if you connect to a Domino 5 database. The pagesize attribute in the url is not mandatory. Parameter Setting Name Domino 5 Avaya asa date separator error com.octetstring.jdbcldap.sql.jdbcldapdriver Provider URL jdbc:ldap://fr146025:389?search_scope: =subtreescope&pagesize:=90 User Avaya Parameter Setting Password SamplePassword SQL statement select givenname,sn,cn,mail,telephonenumber from o=ospc_org Avaya One- Attendant V3.02 CM Service and Installation Manual Page 75 of 123

76 Example 9 for connection of the MasterDirectory The following table shows an example with the default settings for connection of the MasterDirectory. Parameter Setting Name MasterDirectory Driver sun.jdbc.odbc.jdbcodbcdriver Provider URL jdbc:odbc:masterdirectory Note: see SQL Avaya asa date separator error for the name User Password SQL statement SELECT * FROM directory Note: directory stands for the name of the ODBC database without file extension. It can be found under System control > Administration > Data sources (ODBC) > Register System DNS > MasterDirectory (must correspond to the name quoted in the Provider URL) > Path. There will be found for instance directory.md. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 76 of 123

77 Avaya Communication Manager configuration examples Configuration examples General settings The following screen shots are from avaya asa date separator error ASA configuration tool and depict example settings. They must of course be customized to your system configuration. Note: In the text for the screen shots, only the settings which differ from the default settings or are absolutely necessary for one Attendant are referred to.settings under DIAL PLAN ANALYSIS TABLE For the Call Type attd, a digit (Dialed String) must be predefined in dialplan, with which one- Attendant can be called internally. You can use any digit that does not conflict with other settings ( 9 in this example). Settings under ATTENDANT CONSOLE Here you set up one- Attendant as attendant console, avaya asa date separator error. Type: 302 Name: Arbitrary name. Extension: Operator s number of the one Attendant. You can accept operator calls in night service or with a locked operator set. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 77 of 123

78 ConsoleType: principal, for a single one- Attendant. Only one principal and one night (day/night) is possible per system. Security code: code which also must be entered during login of one- Attendant at the CM. Display language: english. This is the only setting that ensures that one- Attendant is signaled correctly. Hundreds select button assignment: Define the number range you want to be displayed in the internal busy display. Entries made using HUNDREDS SELECT BUTTON ASSIGNMENTS must always be in the format YYYxx. Ones and tens places are not entered since the ranges always begin with 00 and end with 99. The entries must always be started at the 1: and none of the digits may be skipped. It would therefore be incorrect for instance to enter three number ranges under 1:, 2: and 4: ( 3: being omitted), avaya asa date separator error. Example: For the range to enter For the range to enter n The Auto Start should be set to n, because one- Attendant initiates a start itself. Feature buttons on the keypad FEATURE BUTTON ASSIGNMENTS lists up to 24 functions, which you can assign to the keypad and hotkeys in one- Attendant. You can call each of these functions using the corresponding button (1 24). You can create user defined labels for the feature buttons assigned functions Avaya One- Attendant V3.02 CM Service and Installation Manual Page 78 of 123

79 The following buttons are pre defined for one- Attendant v3.00: Name atd qcalls **crss alert night-serv *override **priority *pos busy *serial cal *split hold Function Shows the status of the queue. The queue contains all calls in the exchange group that have not yet been assigned to an operator. Indicates whether the pending call is an emergency call. Indicates the night service status of the entire exchange Requires that a call must have been made from your operator set but not yet answered, avaya asa date separator error. When you initiate a new call with this key, the previous call is deleted and replaced by the new Initiates a prioritized call or prioritizes the current call. Places your operator set in Off mode. Changes the status of the current incoming call to a serial call. Initiates a conference between the current party and a waiting party. Used to place the current connection on hold. The waiting call is shown as a call on hold in the preview. Notes: You will have to set up a feature button with the split-swap function. Otherwise, one- Attendant won t work. For convenience in operation we strongly recommend that you set up the following functions: split, avaya asa date separator error, atd-qcalls, night-serv, pos-busy. If you wish to use ACD call center functions, additional q-calls, so that you are shown the current waiting queue of the hunt group(s) (one- Attendant displays only one unidentified current waiting queue, even with membership in several hunt groups). Avaya One- Attendant V3.02 CM Service and Installation Manual Page 79 of 123

80 Settings under CONSOLE PARAMETERS Enter the following values. COS, COR: For one Attendant enter the desired classes Calls in Queue Warning: Specifies from what number of waiting callers backup telephones become signaled. Attendant Vectoring VDN: If you wish to use Attendant Vectoring, enter here the VDN of the desired vector. group 5 Select the following pages according to your requirements: Time Reminder on Hold: Time after which the one Attendant will be reminded of a held call Return Call Timeout: Time after which a waiting call will be included again in the call queue Time in Queue Warning: Time after which the one Attendant will be reminded of a call waiting in a queue. ABBREVIATED DIALING: If you use abbreviated dialing, you must specify here the names of the lists used. In the example, group 5 will be used as list 2. COMMON SHARED ETENSIONS: If you use common shared extensions for parking calls, enter the first extension number in the field Starting Extension and under COUNT the number of subsequent numbers. Tab 3 (not shown) lets you change the priorities with which different call types are evaluated. Tab 4, (not shown), displays all the attendants which are set up. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 80 of 123

81 Settings under OPTIONAL FEATURES The bold entries on the avaya asa date separator error screenshots show values for minimum system requirements. For more information, please contact your system specialist. Maximum Concurrently Registered IP Stations: The parameter must be sufficiently large to meet the requirements of the IP Stations. Maximum Concurrently Registered IP econs: The parameter must be at least as large as the number of one Attendants which can be connected. IP Stations, IP Attendant Console: Must be batman error 9000 fix to y. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 81 of 123

82 IP_eCons: Avaya asa date separator error parameter must be chosen to be at least as large as the maximum number of one Attendants which will be running at the same time. Settings under FEATURE RELATED SYSTEM PARAMETERS The screenshot shows typical settings for these parameters. Settings in bold are the values for minimum system requirements. Auto Hold must be set to y so that auto hold can be used by one- Attendant. Auto Start must be set to n. Transfer Upon Hang-up must be set to y, so that the Transfer key does not need to be pressed twice to transfer a call. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 82 of 123

83 Settings under CLASS OF SERVICE (not shown) In the settings for Console Parameters or Attendant Console, select only one COS-class which has the value y in the fields Console Permissions, Call Forwarding and Priority Calling (optional). Using call center functions in a hunt group (optional) All operator positions of the CM can be interconnected as agents into a hunt group. In a hunt group with call center functionality, call distribution can be even more finely configured than in the normal Attendant group, which usually controls the call distribution to the operator positions. How call distribution within a hunt group takes place is configured in CM (see /2/, /3/) The screen shots in this section correspond to the following scenario: Hunt group 1 Attendant is set up. It can be reached using the number An agent (= one- Attendant) Attendant2 belongs to the hunt group, and has the agent number There are various necessary function keys available for the agents, e.g. for logout. Settings under HUNT GROUP The screen shot shows the hunt group Attendant, which has also been prepared for Attendant Vectoring. Group Name: Name of the Attendant hunt group Group Extension: number of the hunt group Group Type: ead-mia recommended for one- Attendants ACD, Queue, Vector: y Avaya One- Attendant V3.02 CM Service and Installation Manual Page 83 of 123

84 Answer Skill? with y and, if you wish to use attendant vectoring, under Redirect to VDN enter the VDN to which a call to the hunt group number should be forwarded. Setting of FEATURE ACCESS CODES (ACD Features) Codes must be set for the following ACD features: Login, Logout, Aux work, After Call Work and Auto-In. The other settings are optional. Allocating an ABBREVIATED DIALING LIST The DIAL CODES of the feature access codes (fac) set above are allocated in this list. Here the dial code 12 is allocated to Logout (fac = 115) and the dial code 11 to Login (fac = 114) of the agent with the number 3109 and whose password is The dial codes are configured via FEATURE BUTTON ASSIGNMENTS as abbreviated dialing codes. In the example, key 7 is allocated the Abbreviated Dialing function abrv-dial. List 2 is consulted for the abbreviated code, avaya asa date separator error. In our example, this is list group 5, which was predefined in the CONSOLE Avaya asa date separator error. The digits which are provided under the abbreviated code (DC) 12 will be dialed. This is the fac 115, i.e. Logout. So if key 7 in one- Attendant is now applied to a feature key, the agent can log out with it. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 84 of 123

85 Settings under AGENT LOGINID Each one Attendant operator position corresponds to one agent. Important here are avaya asa date separator error name and the password, which are used to login to call distribution. On this panel you must still enter the agent s skill numbers and the associated skill levels because skill was established as a distribution criteria in call distribution. Using Attendant Vectoring (optional) A vector is a sequence of commands. These tell the system how it should deal with incoming calls. They are used to control call forwarding and call socket error #11004. Vectors can be placed in a normal attendant group as well as in an automatic call distribution (ACD) hunt group. Prerequisites: Attendant Group: Under OPTIONAL FEATURES (3#x), Basic Call Vectoring must be set to y. Hunt group: Under HUNT GROUP (1#3), the field Vector? must be set to y and under HUNT GROUP (2#3), the appropriate VDN must be given at Redirect to VDN. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 85 of 123

86 The example shows a CALL VECTOR with the name Attendant Vect. For an interpretation of the command steps 01 to 05 see /4/. A vector directory number (VDN) is a virtual number which redirects calls to a specified vector. The VDN is not assigned to a real extension. A VDN must conform to the number scheme. In the example, avaya asa date separator error, calls to 4150 will be routed to vector 3. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 86 of 123

87 Settings under IP NETWORK REGION For SECURITY PROCEDURES is only the value challenge allowed. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 87 of 123

88 Using Media Encryption Settings under OPTIONAL FEATURES Media Encryption Over IP must be set y Settings under IP CODEC SET If Media Encryption Over IP is activated under Media Encryption it is possible to choose the algorithm (aea or aes), one Attendant supports both but possibly not other connected IP Phones. Additional configuration instructions In ACM you must assign all connecting devices a name, or combination of letters, in the Name field. If the field contains a combination of numbers, such as the extension number, the device cannot be identified in one- Attendant. The Name in ACM can contain up to 23 letters. However, only 16 letters are signaled to one- Attendant. For signals coming from one- Attendant, 15 letters are evaluated. Pay attention that the same COS and COR classes are selected for all settings. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 88 of 123

89 Registered services Some one- Attendant components are installed on the PC as services. These services are also available when no users are signed on. During installation the following services are registered: Service Name displayed Description one- Attendant Avaya one- Attendant database Setup during the installation process database one- Attendant_JOnAS Avaya phonebook server Setup during the installation process AbsenceInfoPusher Avaya phonebook server AbsenceInfoPusher Set up during the installation process if WebAccess was selected UPDService Avaya phonebook server Setup during the installation process UpdateService one- AttendantWebAccess Avaya phonebook server WebAccess Set up during the installation process if WebAccess was selected SVAManager Avaya one- Attendant SVAManager Set up during the installation process if SVA Manager was selected Port avaya asa date separator error of one- Attendant and accessories The following table gives an all errors php of all the port default settings used by one- Attendant and accessory components. Application/Server Port Use one- Attendant Tomcat, WebAccess Internal Web server / http requests Phone book server (JOnAS) 21099, 16010, avaya asa date separator error, 1077 Database server SVA Manager 6006 IP Link (SVA Manager) TTrace Licensing WebLM 8443 License requests (for external access, depends on whether the license server is running locally or externally.) Avaya One- Attendant V3.02 CM Service and Installation Manual Page 89 of 123

90 Importing CM Station and Agent Data to one- Attendant Phone book cyclically Avaya asa date separator error document illustrates an easy way, with step-by-step instructions, of importing the Station and/or Agent Data of Avaya Aura TM Communication Manager into the Avaya one- Attendant Phone book cyclically. This roland internal error 0000015 a two step procedure which first requires you to export the Station and/or Agent Data using the Avaya Site Administration (ASA) tool and then import the data into the Avaya one- Attendant Phone book. Create task for Exporting Station Data 1. Start the Avaya Site Administration (ASA) application and select the PB of interest. 2. Click the Advanced bar from the ASA browser. 3. Click the Export Data wizard from the Advanced bar. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 90 of 123

91 4. The Export Data dialog starts with object selection and record filtering. By default, the station object is selected. If it is not, select station object from the drop-down box (shown below). Select Export to file option, if it is not already selected. Click the Next button. 5. In this step, the desired fields are selected and moved from the available fields column to the selected fields column, one field at a time. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 91 of 123

92 6. Select the fields from the available fields and move them to the selected fields column. When the fields have been moved to the selected column, click the Next button. For example, the following fields were selected for this document. Extension Type Name Room Building Avaya One- Rx crc align error packet count V3.02 CM Service and Installation Manual Page 92 of 123

93 7. In this step, the file format details are selected. Select semi-colon (;) as the Field delimiter, select the quotation mark as the Text qualifier, select the Export column titles on first row? check-box, click the browse button (the 3- dotted button to the right of Export file field) and select the file name and location. When complete, click the Next button. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 93 of 123

94 8. In this step, the exporting of station data can be scheduled to automatically run at a specified date and time. Enter a meaningful name for this task in the Name field, unselect the Run Now check-box, and then click the Schedule button. 9. In the Scheduler step, select the date for the task to start, the time for task to run, the interval for when to run the task the avaya asa date separator error time, and make sure select the Disconnect check-box, avaya asa date separator error. When scheduling of the task is completed, click the OK button. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 94 of 123

95 10, avaya asa date separator error. Verify the task is now scheduled to be run at a specified date and time. Click the Next button. 11. In this last step, details are summarized. Verify details and click the Finish button. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 95 of 123

96 Create task for Exporting Agent Data Similar to Exporting Station Data, the task is created for Exporting Agent Data in this section. 1. Start the Avaya Site Administration avaya asa date separator error application and select the PB of interest. 2. Click the Advanced bar from the ASA browser. 3. Click the Export Data wizard from the Advanced bar. 4. The Export Data dialog starts with object selection and record filtering. By default, the station object is selected. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 96 of 123

97 Instead, select agent-loginid object from the drop-down box (shown below). Select Export to file option, if it is not already selected. Click the Next button. 5. In this step, the desired fields are selected and moved from the available fields column to the selected fields column, one field at a time. 6. Select the fields from the available fields and move them to the selected fields column. When all the fields have been moved to the selected column, click the Next button. For example, the following fields were selected for this document. Login ID, Native Name, Script Tag, Name Avaya One- Attendant V3.02 CM Service and Installation Manual Page 97 of 123

98 7. In this step, the file format details are selected. Select semi-colon (;) as the Field delimiter, select the quotation mark as the Text qualifier, select the Export column titles on first row? check-box, click the browse button (the 3- dotted button to the right of Export file field) and select the file name and location. When complete, click the Next button. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 98 of 123

99 8. In this step, the exporting of agent data can be scheduled to automatically run at a specified date and time. Enter a meaningful name for these task in the Name field, un-select the Run Now check-box, and then click the Schedule button. 9. In the Scheduler step, avaya asa date separator error, select the date for the task to start, the time for task to run, the interval for when to run the task the next time, and make sure to select the Disconnect check-box. When scheduling of the task is completed, click the OK button. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 99 of 123

100 10. Verify the task is now scheduled to be run at a specified date and time. Click the Next button. 11. In this last step, details are summarized. Verify details and click the Finish button. When the scheduled tasks are triggered and running, they are individually displayed in Schedule tab of Status window with all the gory details. For bios id check error, the screenshot bind9 error network unreachable resolving ipv6 shows the status of two tasks; one Complete Avaya One- Attendant V3.02 CM Service and Installation Manual Page 100 of 123

101 and the other Running. Import Station Data into Phone book 1. Start the Avaya one- Attendant configuration tools application, select an entry under the phonebook item and press the New button in this dialog. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 101 of 123

102 2. Choose the Connection tab In the field Driver select the entry jstels.jdbc.csv.csvdriver Enter a meaningful Name and Description in the belonging fields, In the field Provider URL replace the text <Enter directory here> with the directory path where the station data file saved in Step 7 of Create task for Exporting station data Fortran error for3351 the field SQL statement replace the text <enter tablename here> with the name of the station data file saved in Step 7 of Create task for Exporting station data (without file extension) Click on the save button 3. Choose the Mapping tab and select for the exported CM fields the belonging one- Attendant phone book fields. Here we do the following mapping: ETENSION -> Business 1 (main phone number) TYPE -> Phone NAME -> CM name (last name, first name) CM Name (last name, first name) isn t a real phone book field. If you choose this as target field and the content of the source field has the format (last name, first name), then it will be split into the phonebook fields (last name) and (first name). ROOM -> Room BUILDING -> Building As primary key the ETENSION field should be checked. Don t forget to click on the save button again Avaya One- Attendant V3.02 CM Service and Installation Manual Page 102 of 123

103 4. In the Scheduler step, select the date for the task to start, the time for task to run, the interval for when avaya asa date separator error run the task the next time. When scheduling of the task is completed, click the Save button. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 103 of 123

104 Please also note, If the name has only one tilde character (~) before the name, the name is converted to Eurofont characters. If the name has two tilde character (~~) before the name, this record is excluded from importing. The number ( Primary call number field) of the first record may require editing. Import Agent Data into Phone book 1. Start the Avaya one- Attendant configuration tools application, select an entry under the phonebook item and press the New button in this dialog. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 104 of 123

105 2. Choose the Connection tab In the field Driver select the entry jstels.jdbc.csv.csvdriver Enter a meaningful Name and Description in the belonging fields, In the field Provider URL replace the text <Enter directory here> with the directory path where the agent data file saved in Step 7 of Create task for Exporting Agent data In the field SQL statement replace the text <enter tablename here> with the name of the agent data file saved in Step 7 of Create task for Exporting Agent data (without file extension) Click on the save button Avaya One- Attendant V3.02 CM Service and Installation Manual Page 105 of 123

106 3. Choose the Mapping tab and select for the exported CM fields the belonging one- Attendant phone book fields. Here we do the following mapping: LOGIN ID -> Business 1 (main phone number) NAME -> CM name (last name, first name) CM Name (last name, first name) isn t a real phone book field. If you choose this as target field and the content of the source field has the format (last name, first name), then it will avaya asa date separator error split into the phonebook fields (last name) and (first name). As primary key the LOGIN ID field should be checked. Don t forget to click on the save button again Avaya One- Attendant V3.02 CM Service and Installation Manual Page 106 of 123

107 4. In the Scheduler step, select the date for the task to start, the time for task to run, the interval for when to run the task the next time. When scheduling of the task is completed, click the Save button. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 107 of 123

108 Please also note, If the name has only one tilde character (~) before the name, the name is converted to Eurofont characters. If the name has two tilde character (~~) before the name, this record is excluded from importing. Verification of the Station and/or Agent Data can be done in two ways: Select the corresponding Data sources (as defined in chapter 2 of Import Station Data into Phone book) in the Avaya one- Attendant Phone Book and type the _ character in the search area above the column headings and the records of imported station data are displayed with the total number of records. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 108 of 123

109 Select the corresponding Data sources (as defined in chapter 2 of Import Station Data into Phone book) in the Avaya one- Attendant Phone Book and type the _ character in the search area above the column headings and the records of imported agent data are displayed with the total number of records, avaya asa date separator error. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 109 of 123

110 Type the _ character in the Call number or name area of the Operator window and the records of imported station and/or agent data are displayed with the total number of records in the Avaya one- Attendant Integrated telephone book (ITB). Avaya One- Attendant V3.02 CM Service and Installation Manual Page 110 of 123

111 In summary, the above step-by-step instructions in this document provides an easy way to cyclic import Station or/and Agent Data into the Avaya one- Attendant Phone book. Avaya One- Attendant V3.02 CM Service and Installation Manual Page 111 of 123

View more

40

## SAWMILL VERSION HISTORY

ALL PLUG-INS

Sawmill has plug-ins to support the following log formats:

This is the version history for Sawmill 8. The Sawmill 7 version history is here and the Sawmill 6 version history is here.

Version 8.8b2, shipped January 7, 2019

Bugs fixed in version 8.8b2:

• Fixed bug where SFTP log sources using passwords would hang on Windows

• Fixed bug where calendar report generated an error

• Fixed progress reporting on gzip log processing, which was inaccurate

• Fixed error when generating table-with-subtable reports

• Fixed code signing on Mac, which caused warnings on installation and failure to run Sawmill UI.

New features in 8.8b2:

• Added basic pdf-wkhtmltopdf option for command-line PDF generation using wkhtmlttopdf

Version 8.8.0, shipped February 13, 2019

Bugs fixed in version 8.8.0:

• Fixed bug in sorting of date/time reports with sharded databases.

• Fixed bug where SSMTP would fail with an error that SSL was not enabled.

• Fixed date range caching on database update in shard databases.

New features in 8.8.0:

Version 8.7.7, shipped October 5, 2015

Bugs fixed in version 8.7.7:

• [1326127] Fixed an issue with info.cfg where table_num_rows would show an incorrect number for main table after a database update was performed.

• [1326764] Fixed an issue that would cause an error to occur when a Snapon that was attached during profile creation was detached.

• [1328253] Reports of profiles without date/time support and applied filters show two "Clear Filters" buttons.

• [1328463] Report elements with "Use overview for totals" and "Table filter expression" may cause an error.

• [1328683] Email addresses containing an apostrophe or other non-alpha numeric printable ASCII characters did not pass email validation, respectively were indicated as invalid email address.

• [1329342] The Manage Fields dialog window in the Report Element Editor does not open under certain circumstances such as when creating a new report element which erroneously has a duplicate aggregating field.

New features in 8.7.7:

• [1329553] Resolved the issue where the Apple OS X Gatekeeper mistakenly reports the Sawmill MacOS DMG as "damaged".

• [1329592] Pre-built binaries are now available for the RedHat ES/AS 7, Debian 7 and Debian 8 operating systems.

Version 8.7.6, shipped May 18, 2015

Bugs fixed in version 8.7.6:

• [1321194] A schedule with a report filter that runs at a configured time sometimes does not apply the filter to the report.

• [1321466] Setting the CSV export value to empty string "" still shows the "(empty)" value when the report field has a custom display format type for export defined.

• [1322092] The info.cfg file which keeps track of previously processed log data was not properly deleted during a database rebuild, so subsequent updates can mistakenly skip files that were processed during the original build.

• [1324830] Inactive report filter items in admin scheduler are displayed as active/checked although the filter has no effect.

New features in 8.7.6:

• [1319403] Allows date_time database field to have the number of bits to be configureable via the browser. It had been fixed at 16 bits, which caused this problem due to an overflow.

• [1320092] Added support for TLS/SSL email connections via SMTP.

• [1323486] Added support for the new OCLC EZproxy standard log format.

Version 8.7.5, shipped January 29, 2015

Bugs fixed windows update error code 646 version 8.7.5:

• [1314766] Generating a report on Windows with multiple report filters sometimes results in an error like: Can't delete file LogAnalysisInfo\\TemporaryFiles\\illocal_xxx (Permission denied)

• [1316024] This illocal file deletion bug in Windows has been fixed for release 8.7.5.

• [1316990] Database Tools > Process Logs, added page description so that it doesn't become confused with Build Database.

• [1317984] HTTPS web server now uses TLS protocol, replacing SSLv3 protocol. This allows it to work in latest version of Firefox.

• [1320412] Choosing the "Professional" or "Lite" trial tier during setup has no effect.

• [1320413] Cannot save reports in reports editor after changing the order of reports. The reports editor states "No changes to save".

New features in 8.7.5:

• [1309202] Added support for Zentyal log format.

• [1312748] Added support for Bluecoat SGOS6.2/6.4 format.

• [1313210] Added support for Checkpoint log file format.

• [1313664] Added support for Optenet log format.

• [1313713] Added support for Trend Micro Control Manager.

• [1313714] Support for Trend Micro Deep Security has been added.

• [1313715] Support for Microsoft Exchange Server 2013 has been added.

• module online v.4 fatal error Support for Kiwi ISO Event Sentry Added

• [1313900] Added support for i-Filter log file format.

• [1315968] Added support for IWSVA log file format.

• [1319225] Avaya asa date separator error support for Gene6 SARL FTP log format.

Version 8.7.4, shipped October 26, 2014

Bugs fixed in version 8.7.4:

• [1305065] Profiles created with Tomcat Valve patterns give an error on report generation, 'The database field node "page_views" refers to the log field node "page_views" but this log field does not exist.'

• [1305547] Clicking on Customize Report Element or Export in Reports throw an error in Chrome and Safari web browser.

• [1305820] There is no option to choose the source field when adding a Aggregating Field snapon with "max" as the operator.

• [1305821] Manually attaching the Aggregating Field snapon results in an error: Unknown variable 'volatile.new_profile_name' in expression.

• [1306012] When using Italian language, the Snapons page gives an error, "Unknown variable 'param1' in expression"

• [1306186] If a report contains a graph of the Date/time Timestamp field, it generates an error like, "Unknown variable 'lang_stats.months_short.880' in expression".

• [1306255] Reports with a date_time_timestamp as the main field in non-log-detail reports throw an error when displaying a graph.

• [1306760] If log data contains commas in its "key" field used for collect/accept parsing, an error can occur on database update, "Error occurred while reading config 'LogAnalysisInfo/Databases/{profile}/main/saved_collected_entries.cfg'"

• [1308041] Restructured reports editor code base to prevent the loss of all reports when saving report changes. A side effect of this changes are improved loading and saving times of reports in reports editor.

• [1308531] After a database has been built and then updated, if a subsequent rebuild is performed, although a new report table will show the correct new date range, the date range in the graphs and calendar of reports will use a cached date range from the last update, and may not match the table. This cached date range is now deleted during the rebuild.

• [1308963] Relative date filter, i.e. "last6M-show1M" shows two months instead of one.

• [1311887] On on a 32-bit machine, report rows are sorted incorrectly for any number over 4.2 billion.

• [1311887] This bug has been fixed for release 8.7.4.

• [1314847] Export Report Element in Reports throws an error in Chrome and Safari web browser.

• [1314848] Changing the graph type from a chronological type to a non-chronological type has no effect on the graph itself.

• [1314849] Internal Sawmill database directory is not deleted when deleting a profile with a MySQL or MS SQL database.

• [1314850] New Profile Wizard - Log source page. An invalid regular expression in the file mask shows a a language variable reference instead of the error message.

• [1314878] Reports Editor - Manage Fields did not show report fields with type unnormalized_string.

New features in 8.7.4:

• [1304915] Added database type info in bug reports.

• [1305496] Ml 2015 internal error - false placement of snapon-generated report groups in the Reports menu, so they always go above Single-page Summary and Log Detail.

• [1305577] Enhanced Kerio Mailserver support to auto-detect a slight variant, and to report Subjects when present.

• [1305705] Added support for AWS ELB Avaya asa date separator error Format.

• [1306628] Improved the performance of large table reports sorted on a string field which uses itemnums (which is most string fields). Performance is at least 20x faster (20+ minutes to 1 minute) for a 800,000 row example table.

• [1307095] Added support for a variant of Watchguard Firebox XTM log format.

• [1307396] Added support for ICAP log format.

Version 8.7.3, avaya asa date separator error, shipped April 21, 2014

Bugs fixed in version 8.7.3:

• [1296642] When "Use overview for totals" is checked, the Other Items row can show a negative number. (This is fixed by showing a dash in this case).

• [1299899] If a report is generating, and a database-writing task like a rebuild or update runs, the database will be altered underneath the running report, possibly causing an error in report generation. This is now fixed by delaying the rebuild or update until no reports are running.

• [1301487] Apache Custom profiles are created with a duplicate file_type field, resulting in a build error, "Trying to compute 'file_type' field, but there is no 'page' field to compute it from."

• [1301592] Added info text to Profiles View feature permission in Roles, visible when Edit is checked.

• [1301594] Internet Explorer 8, IE9 and IE10 hangs when loading the profiles page and when Internet Explorer's "View all websites in Compatibility View" option is checked.

• [1301665] Remainder row shows negative values avaya asa date separator error fields with aggregation method unique when "Use overview for totals" is checked.

• [1301907] In the analysis of Juniper SSL VPN log data, "VPN Tunneling: Session ended for user with IP" lines are ignored, possible resulting in very long reported session durations for those sessions.

• [1301918] When using the internal database, indices do not improve the performance of single-value report filters on single fields.

• [1302023] Multiprocessor SSQL queries (e.g., from main table reports generated with "query splitting" turned on) crash or generate an internal error.

• [1302306] Attempting to create a profile from log data in Windows 2000/2003/2008 DNS Log Format, given an error "no date_time in snapons" during the Create Profile Wizard.

• [1302380] Reports generated from MDaemon 13 logs show no events.

• [1302651] Sending a report by email with multiple recipient email addresses causes a SMTP server error in some mail servers.

• [1302908] When analyzing servuftp logs, the Log Detail report fails with an error, "Unexpected text at end of SSQL field description: '_file'"

• [1303189] The profiles list is not properly sorted after a profile has been renamed.

• [1303428] Editing the last action in scheduler overrides the first action with the last action.

• [1303868] Report filter items of type within/matches are not added and not editable in Reports/Filters.

• [1303979] Manage fields in an overview report element allows to add non-aggregating fields which cause an error in reports. Fixed so that only aggregating fields can be added in overview report elements.

• [1304170] A report element which displays one or more chronological graphs without a table and with no filters applied causes an "Unable to read file" error. The error only occurs if the profile uses the internal database, profiles with an external database are not affected.

• [1304248] Sawmill Lite displays a "No Permission" page when navigating to the Config/Log Source page or to a Tools page.

• [1304349] When creating a MySQL profile with a non-default port, an error occurs at the end of profile creation like, "Failed to connect to MySQL database at 127.0.0.1:3302 with username 'user'"

• [1304406] When a regular expression table filter, or "omit parenthesized items," is used on a report column of type non-aggregating integer, avaya asa date separator error, an error occurs like, "Internal: attempt to get string value from non-varchar column 0 of table 'xref2' with GetStringCell()".

• [1305369] Clicking on Customize Report Element or Export in Reports throw an error in Internet Explorer 6, 7 and 8.

• [1305752] If Professional license holders upgraded to version 8.7.3.2 before April 26, 2014, they could get this error in the UI: "An error occurred while processing templates.alert (which was being used in an attempt to report an earlier error):" The task log would show this error: "Checksum does not match for file 'templates/util/html.cfv'."

New features in 8.7.3:

• [1285416] Display a "Before you start" section in Admin/Profiles to new users, it is only shown after a new setup. The section reminds new users to disable Antivirus software for the Sawmill directory and shows some links to best practice guides when processing large datasets.

• [1301348] Added support for WebLogic 10 log format (by extending the existing WebLogic 8 plug-in so it can handle both).

• [1301358] Added support to show a warning message for missing log fields in the New Profile Wizard. The warning message will be shown if required log fields are defined in a warn_on_missing_log_fields node in the log format plug-in and if these log fields are not detected in the log files.

• [1301531] Added support for Kerio Control security log format.

• [1301630] Added rendering of very large byte counts as Terabytes, Petabytes, and Exabytes.

• [1301689] Substantially rewrote support for the OpenVPN plug-in so it supports the latest format of log data, parses faster, supports any syslog header, and more.

• [1301696] Enhanced IPCop Syslog support to handle date header lines.

• [1301859] Added support for NPR Reporting log format.

• [1301902] When reporting on Cisco PIX/IOS log data, dynamic Teardown lines are ignored, resulting in lower than expected reported duration.

• [1301976] Added support for Cisco IronPort S-Series (WSA) CSV export format.

• [1302060] Added option to Report Options/CSV Export to convert the "(empty)" value to any custom defined value.

• [1302205] Display operating system and architecture in About window.

• [1302286] Display a warning message in File Manager/Network Shares when the "Map drive letter" is selected.

• [1302301] Added support for F-Secure HTTP Access log format

• [1302454] Added support for Zimbra mail server log format

• [1302671] Added support for IPCop Snort multiline log format.

• [1303041] Added support for Sophos UTM Web Application Firewall log format.

• [1303190] Display best practice tips in New Profile Wizard on log source and database page and in Scheduler.

• [1303191] Improved styling of the Help Manual and added a Best Practice Guides section.

• [1303424] Added support for Websense Server log format.

• [1303461] Added "Show/Hide Created By Avaya asa date separator error in Profiles/View menu. The column can now be set per user. User access can be set in Admin/Roles.

• [1303462] Moved "Show/Hide Database Info Column" from Profiles View Editor to Profiles/View menu. The column can now be set per user. User access can be set in Admin/Roles.

• [1303794] Added support for FortiGate 300 Series log format.

• [1304249] The "database info column" is now visible by default in the Profiles list.

• [1304335] Added support for InterMapper Chart log format.

Version 8.7.2, shipped February 02,2014

Bugs fixed in version 8.7.2:

• [1296399] Error messages from errors during parsing in multiprocessor mode, sometimes have embedded HTML code in them.

• [1296656] If a profile and its database is deleted, avaya asa date separator error, and the database is internal and uses a custom database directory, the directory is not fully deleted, but still exists and contains one file, info.cfg.lock.

• [1299432] If there is avaya asa date separator error new data in the log source, single-processor database updates will give an error like, "## Attempt to read beyond end of LogAnalysisInfo/Databases/(PROFILE)/main/Tables/f_main_table_p0/data.tbl (fileSize=0); attempted to read from 0 to 214."

• [1300566] If Flash Media Server log data contains fields with embedded spaces, some field values will be put into the wrong fields during parsing.

• [1301306] On small mobile devices, In the Scheduler, when adding a New Item to the Report Filters, the window opens partly off-screen, and runs away when chased by scrolling.

• [1301307] The profiles menu displays profiles for which a user has no access permission, though only when logging in with different usernames and access permissions on the same computer.

• [1301309] Clicking on a sorted report column does not change the sort direction under certain circumstances.

• [1301622] Import report filters in scheduler actions does not show existing report filters.

• [1301623] Report filter windows in scheduler actions are not correctly positioned and move away upon scrolling in mobile devices.

New features in 8.7.2:

• [1299895] Added support for MOVEit DMZ SSH log format.

• [1300599] Changed the "strftime:" option for custom "display format type" to use local time instead of UTC.

• [1300848] Added support for Internet Explorer 11 detection (user agents with "Trident").

• [1301207] Added support for Bitvice WinSSHD XML log format.

• [1301590] Added Avaya asa date separator error View in Admin/Profiles. Refresh view clears cached profiles and reloads all profile data.

• [1301591] Added Admin Tools page to clear the cached profiles list and server side report caches and to update web files.

Version 8.7.1, shipped January 23, 2014

Bugs fixed in version 8.7.1:

• [1292350] On SPARC Solaris, database builds usually crash.

• [1293936] Running the delete_database_field command-line action, on a profile with report fields which have no database field (e.g., expression fields), gives an error, "Internal Error: Empty node name"

• [1294383] When using an "unnormalized string" field with a dataset of more than about 5 million lines, a database build will crash.

• [1296757] When updating a database, if skip-by-pathname is on and file-by-file is on, the update re-adds previously seen files.

• [1299145] When importing a database into a fresh profile, the hierarchy avaya asa date separator error are only automatically rebuilt for those fields which have hierarchical xref tables. So most hierarchy tables are not built, and hierarchical reports fail with an error like, "Unable to read file LogAnalysisInfo/Databases/{profile}/main/Tables/geo_countrysubitem/header.cfg (Operation timed out)". (As a workaround, rebuild the hierarchies manually with "sawmill -p {profile} -a rdh").

• [1299296] There are duplicate File Type, Screen Depth, and Screen Dimensions log fields in a profile created with the Web Server Package snapon.

• [1299697] Clicking next rows on a table which already displayed the last row returned previous rows.

• [1299698] Missing row numbers and Rows button in Path Through a Page report element.

• [1299723] After manually adding the Device Type snapon to a profile, a database build fails with the error, avaya asa date separator error, "Syntax error: Expected variable, subexpression, or identifier -- found =".

• [1299892] In sendmail analysis, in status=Sent lines with multiple recipients, the last email address is not reported, and the second-to-last email address is reported twice.

• [1299960] Profile conversion of older version 8.0 and version 8.1 profiles does not start when clicking "Click here to convert the profiles".

• [1299961] Delete profiles is not functional when the Admin/Profiles page displays older version 7.x, 8.0 or 8.1 profiles.

• [1299962] Update Database and Build database hangs at "loading" in the Reports GUI when logged in as non-root-admin user.

• [1299963] Config Options and Tools menu is not visible in Reports and Config when logged in as non-root-admin with Config and Tools permissions.

• [1299965] Profiles View permissions are not available in Admin/Roles. Edit Profiles View is only available to root-admin.

• [1300154] Admin/Profiles page has no margin when no profile exists or when it contains invalid profiles from older versions.

• [1300156] New profile is not immediately displayed in profiles list.

• [1300158] Admin/Profiles misses language variables for translation.

• [1300592] Reports with complex filters run on Windows can give an error like, "Can't delete file LogAnalysisInfo\Databases\PROFILE\main\Tables\filtertmp_7804_2\indices\itemnum\header.dat (Permission denied)"

• [1300735] Admin/Profiles page does not show any profile when additional report columns are defined and when logged in as non-root-admin user.

New features in 8.7.1:

• [1292766] Added support for Watchguard Firebox logging via Syslog Watcher (new plug-in for Syslog Watcher, and enhanced Watchguard Firebox XTM plug-in to handle slight variant format.

• [1294243] Added support for IBM HTTP Server Common Log Format.

• [1299192] The remove_database_data action now allows the date_filter (-df) command line option, and discards whatever is *not* in the filter set, so "-df 30day" will expire everything older than 30 days.

• [1300869] Changed the way report filters are done internally in some cases (filtering on main table with "within" or date range filters), to reduce temporary disk usage and increase performance.

• [1301621] Added a GUI widget for report filters in scheduler actions. The widget is similar to the one in Reports. With the added import option it is possible asus p9x79 cpu fan error import report filters from the selected profile and from other scheduler actions.

Version 8.7.0, shipped December 8, 2013

Bugs fixed in version 8.7.0:

• [1285838] Profiles using Kiwi (mm/dd/yyyy) syslog format, do not report values for any fields other than the syslog header.

• [1288265] Deleting a MySQL profile with database results in an error, 'Unknown configuration group "admin_pages" in node ""'

• [1288440] If a database contains no data, the Sessions Overview gives a cryptic error, "Internal error: mapping 'LogAnalysisInfo\Databases\{profile}\main\Tables\session_users_stage1\sets\sessions' read-only, but its lists.dat"

• [1288998] PDF rendering cuts off the date range display at the far right of the page.

• [1289649] Fixed ShoutCAST 1.8 log format support; it was incorrect categorized as a Gateway device instead of a Media Server, so some of the reports were odd.

• [1290915] After performing a "remove database data" operation on an internal database, filtered reports which use indices may give incorrect (too large) numbers. (workaround: rebuild the indices with "sawmill -p {profile} -a rdi" after rdd).

• [1291100] When a snapon is detached, if it added a database field during profile creation, some traces of it remain in the profile (and can cause errors), including references in auto-generated cross-reference groups, and auto-generated reports.

• [1292125] References to row_number in report field expressions give an error, "Unknown variable 'row_number' in expression"

• [1292191] The Play Duration reported by Wowza and Flash can be slightly too high; it double-counts some duration when a session ends with a pause, followed by a stop.

• [1292206] When displaying a Log Detail report, with a filter, and paging forward, the second page will sometimes show no results.

• [1292709] When zooming in the reports UI, the "zoom" window appears too low, to wide, and transparent.

• [1293226] On multiprocessor systems with Enterprise licensing and "split queries" enabled, even when queries are large enough to be split among processors, they are not.

• [1293275] When a new field is created in the New Field Wizard, the resulting report element has no label.

• [1293441] When using a within/matches filter with a report field which has no corresponding database field, an error can occur like "Unknown variable 'page_directory' in expression".

• [1293446] On non-Windows servers, if a scheduled task to email a report uses a subject containing parentheses but no spaces, an error will occur when the schedule is run, "-bash: syntax error near unexpected token `('" (workaround: put the subject in double-quotes).

• [1293517] A CSV export of the Cities report contains HTML tags in the city names. And, the Display Format Type of the Cities field appears as "Bandwidth" in the UI.

• [1293861] Wowza sessions ending with "destroy" instead avaya asa date separator error "stop" are not counted in play duration.

• [1293885] IIS web log profiles avaya asa date separator error not include referrer analysis (search engines and search phrases), and do not simplify the c-referer field.

• [1294553] When deleting a profile with an external database, and checking the "Drop database" checkbox, the UI hangs after deletion.

• [1295435] Save As New Report does not save the defined date filter.

• [1295437] Filtering on report fields without underlying database fields (e.g., expression fields like Bounce Rate), gives a syntax error like, "Syntax error: Expected variable, subexpression, or identifier -- found".

• [1295520] If a log format contains an "average" field (aggregation method "average"), and the denominator field doesn't exist, and the field is checked in Create Profile Wizard, it will appear in reports as a simple summing field with the same values as the underlying numerator field (rather than not being included in reports).

• [1295828] Profiles created from Apache custom log data containing user-agent or referrer, have duplicate versions of the reports derived from those fields.

• [1296318] "Actions emails" do not have a subject or a return address.

• [1297066] The "time elapsed" part of the progress display is sometimes wrong (suddenly drops down to a lower time).

• [1297590] A cross-scripting vulnerability exists which allows a carefully crafted URL to run arbitrary JavaScript code in the client browser.

• [1298158] Changing the date time format in lang_stats.cfg had no effect in reports.

• [1298879] If an SMTP password contains a plus (+), it is passed incorrectly to the server, avaya asa date separator error, resulting in failed authentication.

• [1298923] Profiles created from Flash Media Server logs have multiple "byte" database fields which are normalized as type string, and non-aggregating, and have xref groups as though they were normal non-aggregating fields; these fields are not used directly in reporting and should not have xrefs; and they are integers and should not be normalized as itemnums. In short, complexity of Flash profiles has been reduced, and performance has been improved.

• [1299365] Canceling profile deletion by clicking No in the confirm delete window interpreted the click as Yes and deleted the profile in Internet Explorer 9.

• [1299696] Clicking previous table rows caused an error when the starting row had index 1.

New features in 8.7.0:

• [1288348] Added a new database field type, "unnormalized string," which does not use itemnums to normalize string fields. This is useful for fields which have a large number of unique values, and can greatly improve scalability while retaining full detail of a field.

• [1291946] Added support for Savvion BPM log format.

• [1292044] Added a new option attrs parameter to the built-in Salang function ldap_search(); this allows non-user attributes to be queried, which is necessary to use certain LDAP configurations for login.

• [1293647] Added support for Lotus Notes log format.

• [1294046] Added support for Windows Event log format (XML).

• [1295126] Added support for SiteMinder Apache WebAgent Log Format

• [1295174] Added support for a variant of McAfee Web Gateway log format (version 7.2).

• [1295942] Added support for Limelight SHOUTcast Service log format.

• [1296470] Added support for WebLogics Diagnostic log format.

• [1296714] Extended the Filemaker Access log format plug-in to support version 11.

• [1297159] Changed the "remove database data" query in MSSQL to remove data in batches of 1 million rows, to keep it from overloading the transaction log for very large datasets.

• [1297215] Added support to define a custom filename in Reports Export Table.

• [1297216] Improved reports and config navigation menus and fixed miscellaneous styling issues.

• [1297217] Added a profiles drop down menu in Reports and Config navigation bar. This allows to switch between profiles without navigating to Admin/Profiles.

• [1297218] Added a filter field in Admin Profiles. This allows to filter/search the profiles list by profile names.

• [1297219] Improved admin profiles list loading performance by caching the profiles list in the web browser.

• [1297221] Improved report element controls, layout and style.

• [1297222] Added support to run Process Logs from the web user interface. Process Logs is located in the new Tools menu in Config and Reports.

• [1297405] Enhanced Hurricane MTA support to report the EHLO responses, so it is possible to filter on them, for instance to show only connections supporting TLS.

• [1298119] Added support for MOVEit DMZ log format

• [1298815] Added support for Retrospect log format.

• [1299364] Added Admin/Profiles dashboard to display basic report values, display the profiles database state and to update/build profiles databases.

Version 8.6.3, shipped July 09, 2013

Bugs fixed in version 8.6.3:

• [1288964] In Wowza analysis, for profiles created with Sawmill 8.6.2, play duration is overreported in cases where there are "unpause" events in the logs.

• [1289068] When attempting to delete an MS SQL profile through the web interface, along with its database, an error occurs, 'Unknown configuration group "admin_pages" in node ""'.

• [1289278] The new profile wizard does not show the database page in the Pro version.

• [1289335] Config Reports Editor - "Link to report" list is not properly updated when renaming, adding or deleting new reports in reports editor.

• [1289722] In some circumstances, a Flash Media Server profile (or possibly other profiles which redefine their log fields during database building) will fail to build with an "Empty node name" error.

• [1289735] "Link to report" did not open the report in static (generated) report files.

• [1289736] The reports menu was not shown in static (generated) report files.

• [1289900] When creating a profile using MSSQL as the database, an error can occur when entering the database name, 'The MS SQL database name must start with a Unicode letter or the characters "_", avaya asa date separator error, "@", "#"; followed by one or more letters, numbers or the characters "_", "@", "#", "$". Please define a different database name.' • [1289956] When reporting on Chinese Windows syslog files, some characters are garbled in reports. • [1290318] A Flash Media Server profile created with the duration field unchecked, has no reports. • [1290495] If a SQL prefix is used, an error can occur on database update, "Unable to Execute ODBC Query='select count(*) from main_table_update'; diagnostics=ODBC error: rec1: SQLstate: S0002; msg=[Oracle][ODBC][Ora]ORA-00942: table or view does not exist" • [1290731] Fixed a security issue in the update and build database page. • [1291076] Profiles created from Akamai Streaming W3C logs, do not track the final field in log. • [1291263] Enhanced display format type settings in report fields. Display format types can now be specified for all aggregating fields in exported reports, they can also be different from the HTML settings. • [1294036] The password reset link doesn't work in CGI mode. New features in 8.6.3: • [1288297] Added support for Cisco eCDS log format. • [1288692] Added support for SocketLabs Hurricane MTA log format. • [1289692] Added "Bounces" and "Bounce Rate" as a standard part of the Web Server Package (affecting all plug-ins which use that package, including Apache Extended, IIS, and many others. • [1290423] Added support for DataEnter Xwall log format. • [1290844] Added avaya asa date separator error for {==} (Salang) sections in the database directory parameter, enabling, for instance, automatic creation of a new database every day. Version 8.6.2, shipped May 22, 2013 Bugs fixed in version 8.6.2: • [1279136] A Pages report, with a Page field as a pivot, gives an error like, "Can't find tableAlias=rep_*, fieldName= in table rep_*" • [1283035] Clicking "Save as New Report" has no effect on the first click, when using Internet Explorer 8 (it works on the second click). • [1283229] If a profile uses an MSSQL database, the Create Profile Wizard will not allow a space in the profile name. • [1283766] Import through the web UI of a Sawmill 7 database with sessions may fail with an error like, "Attempt to read beyond end of {dbdirectory}\main\item s\day_of_week\offsets_by_num (fileSize=8000); attempted to read from 484293090593472512 to 484293090593472520" • [1283834] Attempting to generate a pie chart, avaya asa date separator error, with sort set to chronological, causes a crash. • [1284137] Adding a date/time timestamp field to a report other than Log Detail gives incorrect timestamps in 1970. • [1284176] Profiles created in 8.6.0 may give an error, "Unknown variable 'lang_admin.snapons.geoip.comment' in expression" when displaying the Config -> Snapons page. • [1284320] If a format has a numerical field named "requests," and if the field is unchecked during profile creation, a crash or an error like "Couldn't find node parameters in" will occur. • [1284815] After adding a Field Ratio snapon, all table reports fail with an error, "Internal Error: Empty node name" • [1284921] Sawmill's built-in HTTPS server supports SSLv2, an old and less secure version of the protocol. Switched to allowing only SSLv3. • [1284973] Changed the "Turn on cross reference groups" option in the Create Profile Wizard so, if unchecked, it turns off all xrefs except the first one (date/time). Previously, it turned them all off, but that could lead to reporting timeouts when displaying the first report, on very large datasets. • [1285043] Attaching the "Bounce Rate" snapon has no effect on reports. • [1285059] If a profile is created from a plug-in which uses snapons, any require_field conditions in its log filters are ignored--log filters are not deleted properly if the fields they require are not present. This can cause errors during log parsing. For instance, Flash Media Server profiles created from a log file lacking c-client-id will give an error on build, "Unknown variable 'c_client_id' in expression". • [1285137] In profiles which use distribute_format_line() to handle multiprocessor parsing of data with embedded format lines (e.g., Wowza), a small amount of log data *before* a format line may be parsed using the parsing rules specified in that format line, resulting in values being put into the wrong fields. • [1285138] Opening a report in Gmail or Outlook does not show the legend colors from a pie or bar chart. • [1285268] Fixed an issue where Wowza (and potentially Flash) log data would be reported with 0 duration when filtered. Also, improved memory usage of database filtering in Wowza and Flash import, and lifted restriction that Wowza and Flash data be processed chronologically and with a single processor. • [1285273] Checking "Prevent Use Of Previous Passwords" in Admin/Preferences/Password is not saved and may cause a javascript error. • [1285292] When the maximum number of licensed profiles is exceeded, and Reports is clicked for a profile, an ugly unformatted HTML error message is displayed. • [1285370] Fallout 3 binkw32.dll error a database update is attempted against a database which has never been built, it fails with the error, "Cannot build database for {profile}-- someone is already writing to it" (it should instead build the database). • [1286378] A "Send Report Avaya asa date separator error Email" task, on a profile whose database is being updated, sends a report (or sometimes fails), rather than giving an error that the database is being written (as it should). • [1286440] The custom action dump_main_table gives critical error 80 40 motorola v3r error like, "Attempt to read beyond end of LogAnalysisInfo/Databases/{profilename}/main/items/date_time/offsets_by_num (fileSize=8000); attempted to read from 9916758672 to 9916758680 • [1287062] The filter "session start" still appears in the Report Filters menu, though this type of filter no longer applies to session analysis (and gives an error if you try to use it). • [1287173] The login page does not save the new entered password upon an expired password notification. Clicking the Login button has no effect. • [1287450] The date filter "last1week" selects 8 days (Sunday through Sunday) instead of 7 days (Sunday through Saturday). • [1287520] Sending email in reports does not show the error message if an error occurs. • [1287664] If a date range filter is used in a SQL database with a table prefix, it results in an error like, "Unable to Execute ODBC Query='select * from bottomleveldateitemnum'; diagnostics=ODBC error: rec1: SQLstate: S0002; msg=[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'bottomleveldateitemnum'.;" • [1287864] Display format type "megabytes" and "gigabytes" were implemented in Salang but not available in the GUI. • [1287865] Reports show table bar graphs for very small numbers when they are expected to have zero length. • [1287867] Report and report element descriptions have wrong margins. • [1288001] In formats that have both Visitors and Hostname in the Log Detail Avaya asa date separator error, a SQL error can occur such as: Unable to Execute ODBC Query='select * from ( select x.date_time, x.s_sitename, x.s_ip, x.cs_method, x.cs_uri_stem, x.cs_uri_stem, x.s_port, x.cs_username, x.c_ip, x.cs_referer, x.sc_status, x.sc_substatus, x.sc_win32_status, x.hits, x.page_views, x.sc_bytes, x.cs_bytes, x.time_taken, row_number() over (order by loadorder) as row from error invalidfont offendingcommand findfont x ) a where row >= 1 and row <= 50'; diagnostics=ODBC error: rec1: SQLstate: 37000; msg=[Microsoft][ODBC SQL Server Driver][SQL Server]The avaya asa date separator error 'cs_uri_stem' was specified multiple times • [1289203] Removed invalid reports editor "Show header bar" option in Reports Editor. New features in 8.6.2: • [1275810] Enhanced the "pattern" option for selecting profiles in the Scheduler (and the command line) so a profile matches if either avaya asa date separator error internal name (filename.cfg) matches, or its label (the way it appears in the Profiles list of the web UI) matches. Previously, only the internal name was checked. • [1276977] The language (e.g., Chinese) can now be selected during the Startup Wizard. • [1277418] Login plug-ins can now be enabled or disabled from the Preferences. • [1277966] All passwords in profiles and Preferences are now encrypted when saved to disk. • [1280145] Add a new command-line action, copy_node_from_another_profile, which copies a node from one profile to another. This can be used, for instance, to copy a custom report from one profile to another. • [1282080] Restored the "show all rows" option in table reports (this was removed in version 8.6.0 as part of a UI redesign). • [1282781] Restored the check_main_table_integrity and check_itemnum_integrity command line actions, which can be used to do database integrity checking, and some repair. • [1282917] Added a new "skip file expression" option which provides a way to create a rule for skipping files in the log source based on a Salang expression. This allows for advanced skipping algorithms, for instance, skipping files where the date in the filename is older than 7 days. • [1282927] Added Media Reports snapon to SHOUTcast format. • [1283423] Added support for LUNA Insight Media Manager Service log format. • [1283596] Enhanced Wowza log format plug-in, so it shows stream names both hierarchically and non-hierarchically, in separate reports. • [1283619] Changed Wowza log format plug-in to use the new "play duration" snapon to compute its play duration field. This allows play duration to be computed more precisely in cases where log data is processed with multiple processors, or multiple log files processed out of chronological order, which previously would have resulted in small discrepancies in the reported duration. • [1283946] Improved the robustness of database updates, by performing some parts of the update off to the side of the main table, and moving them into place only if the update completes without an error. This eliminates MUINT_MAX errors which can occur from database corruption resulting from an earlier failed update. • [1284000] Renamed the "allow empty log source" option to "Warn on log source errors", since it has gradually acquired many other conditions other than just an empty log source. Also, added logging of these warnings to TaskLog, and to console output. They are also displayed in the Progress display. • [1284018] Added a new option, "Skip File Expression," which allows files in the log source to be skipped based on a custom Salang expression. This allows for advanced skipping, for instance, skipping any files older than 30 days, according to the timestamp embedded in their filename. • [1284105] Added support for WebLogic W3C format logs. • [1284136] Added support for avaya asa date separator error of a date/time timestamp report field as "date" or "time", showing only the date or time of the timestamp. • [1284208] Added Media Reports snapon to Microsoft Media Server format. • [1284236] Added integration support for Vision Reporter, a mobile reporting app ( http://www.visionreporter.com/ ). • [1284358] Added support for Nginx log data with a customer log_format string. • [1284837] Added new "Date" and "Time" display formats for timestsamp report fields, to display just the date or time portion, for instance to have separate Date and Time columns in Log Detail. • [1284963] Added Media Reports to the Akamai Streaming format. • [1285140] Added support for Courier POP3/IMAP log format. • [1285207] Improved detection of BlackBerry devices, for the Operating Systems and Web Browsers reports. • [1285429] Added support for columns of type "text" in ODBC log sources in MSSQL databases. • [1285687] Added a new Miscellaneous -> Active Filters Info page to Reports, where the command-line and "expression" versions of the current report filters can be seen. • [1286514] Added support for VARCHAR() fields in the result of database_sql_query(). • [1287194] Added support for MDaeomon Routing log format. Version 8.6.1, shipped February 14, 2013 Bugs fixed in version 8.6.1: • [1278183] If an LDAP password contains a apostrophe, it causes an error on login like, ""Sawmill Alert Syntax error: Unknown operator in expression." • [1278669] When the option Report Options -> Numbers & Text -> "Use base 10 for byte displays" is changed, the changes does affect for previously-generated (cached) reports. • [1280548] When building with multiple processors on 64-bit Windows, if an integer field value has a value more than about 2 billion, and it will be truncated to about 2 billion, avaya asa date separator error, even if the database field is specified as 64-bit. • [1280717] Reports filtered on a date range query the main table (resulting in slow report generation), even if a cross-reference table exists able to optimize the query. • [1281429] IIS profiles do not detect web browsers properly; in particular, they identify Internet Explorer as "Unknown Mozilla". • [1281632] The values are invisible in table cells in standard PDF reports. • [1281718] If, avaya asa date separator error, after making graph changes in the Reports Editor, you avaya asa date separator error "Save Changes", and then go to Manage fields and click OK, the avaya asa date separator error changes are eliminated. • [1281797] The Scheduler gives an error, "Unknown variable 'lang_admin.snapons.device_type.report_label'", when there are profiles created in 8.5.9, which use the Web Server Package. • [1281861] Large table reports (e.g., a Hostnames report with a million rows) use a very large amount of memory, and if large enough, eventually fail with an error like, 'Unable to avaya asa date separator error 469762048 bytes of memory; maximum memory is 2242822425, but 2098194845 is already used, and no further memory can be freed. Allocation attempted at fstring.cpp:225, description: "fstring buffer"' • [1281968] Temporary tables with names starting with blitmp and join_maptable, are never removed from the database; large numbers of these can collect over time, until the database is rebuilt. • [1282110] When running a "remove database data" operation against a profile which uses a MySQL 4 database as a bank end, an error can occur like, "SQL query failed: 'delete from main_table using main_table x where (main_table.date_time < '2012-01-06 21:59:37')' error=Unknown table 'main_table' in MULTI DELETE at ./src/expire_database.cpp:212" • [1282133] View an Overview report for a profile with no data in its database, gives an error: "Attempt to read beyond end of LogAnalysisInfo/Databases/ • [1282143] Enhanced support for NetScreen, to extract virus information from a slight variant of the format, and to simplify the "message" field to improve performance and reduce database size. • [1283027] The "gear" and "save report" icons in report elements, do not render in the correct places when viewing reports in Internet Explorer 7. • [1283039] When clicking "Save as new report" l2walker 10.6.3. packet error Reports, a JavaScript error can occur, causing the window not to load. (Clicking again will avaya asa date separator error the window). • [1283040] There was a "pie chart" option for chronological graphs, in the "customize report" window in Reports, even though chronological data cannot be graphed as a pie. This caused an error when it was selected. This option has been removed. New features in 8.6.1: • [1277718] Modified the "Device Type" reports a bit, to show a Mobile Devices report listing only mobile devices, instead of a general Device Types report (the Device Categories report remains unchanged). • [1280054] Improved progress reporting while scanning a recursive log source, to show the directory being scanned. • [1280267] Added support for UTM 80-E Firewall. • [1280489] Improved database build performance slightly by removing the unnecessary xref on the session_sequence_number field. • [1280716] Added support for IIS Advanced Logging Module Log Format. • [1281737] Switched Apache Custom plug-in to use the Web Server Package, giving it the advanced functionality of the Web Server Package snapon, including a dashboard and advanced reporting of agent and referrer information. • [1281888] Added a Dashboard to the Media Reports snapon; added the Media Reports snapon to Flash Media Server. • [1282340] Added automatic conversion of incorrect but commonly attempted report syntax "fieldname = 'abc'" to the correct "fieldname within 'abc'" • [1282389] Added a Dashboard to all formats which use the Gateway Reports snapon (which is most major gateway log formats). • [1283929] Slightly enhanced the previously-seen-data skipping algorithm, so if a log file is zero length or inaccessible, and "skip files ide error status xs pathname" is enabled, the file will be ignored, and not saved as "seen," so if it gets data later or becomes accessible, it will be processed at that point. This is specifically important for IIS logs, where the latest log (the log being written) is not accessible for avaya asa date separator error, and should be retried until it becomes available. • [1297859] Added the ability to change the date/time format that appears in reports by editing the "date_time_format =" node of lang_stats.cfg. Version 8.6.0, shipped December 12, 2012 Bugs fixed in version 8.6.0: • [1263664] The built-in web server fails to load pages or files, sporadically, on non-Windows systems. • [1272644] When importing a v7 profile without a database to 8.5, session information (reports and fields) is not carried over to the new profile. • [1272731] "Remove Database Avaya asa date separator error operations did not correctly check for existing database-writing processes, potentially causing corruption of a database if they begin during a database update or rebuild. • [1274531] When building a database from Juniper MFC 12 (W3C) avaya asa date separator error without suppress_cs_range or suppress_etag fields, an error occurs, reporting the absence of these fields. • [1274718] Network actions like create_user, which shouldn't require -p, generate an error if p is not specified, "Unknown variable 'internal.profile_name' in expression" • [1274963] After attaching a "Report Field Ratio" snapon, reports give an error, "Unknown database field '{fieldname}' in v.query_result.header" • [1275020] Report filters on numerical fields using >= give incorrect results (often, filtering out nothing). • [1275153] If a version 8.1 profile has a "unique" database field of Type "string", conversion to 8.5 will result in a version 8.5 profile which fails on database build with an error like, "Internal: Attempt to find main table column number from database field 29 [visitors], but there is no such column in main_table" • [1275902] Avaya asa date separator error a database field is non-hierarchical, and there is a cross-reference group of it which is hierarchical, the corresponding report will show an extra blank line counting all events. • [1276172] If the web server is running more than 30 days straight, tasks may begin to fail immediately after starting (this clr20r3 windows 7 error due to MasterProcessLock files being prematurely deleted). • [1276578] Attaching the Geographic Location Information from Config -> Snapons gives an error, "Snapon attempted to add database field 'location', which already exists" • [1276952] Improved detection of libcrypto during "configure" on Linux, to handle systems with limited versions of the library. • [1276987] The "Other Rows" line in tables is incorrect, containing one of the rows which is visible. • [1277076] The "omit parenthesized items" item is not saved when using the Customize link in Reports for pivot tables. • avaya asa date separator error Session information is lost when importing a Sawmill 7 profile through the web interface. • [1277448] When using an SFTP log source, entering "/" for the pathname does not show the files in /. (workaround: use "/*"). • [1277702] Generating a report where one of the report elements has a label containing a double-quote, avaya asa date separator error, gives an error like, "Unexpected = in group node (v.progress.step.0.abc def ))". • [1278066] The delete_user action (or network action) gives an error, "Syntax error: Unknown variable 'profile_name' in expression." • [1278917] The command-line progress display often displays less than 100% at the end of a successfully completed action. • [1279444] A database build can crash if there are no xref and no indices and no database filters. New features in 8.6.0: • [1272161] itemnum tables are no longer indexed, when the corresponding database field is set to not be indexed. • [1273614] Separately implemented country/region/city support as a snapon, for better modularity; this also avaya asa date separator error it possible to have more than one Geo analysis in a single profile (based on different IP fields). • [1274335] Greatly improved the performance of filtered Log Php fatal error require reports, by eliminating the calculation and display of the total available rows. This decreases the time from 169 seconds to 7 seconds avaya asa date separator error one 180-million-line dataset. • [1274617] Created a new snapon, avaya asa date separator error, Create Default Xref Groups, which at the time it is attached, creates default xref groups for all database fields (each xref group having that get last error 1813 findresource delphi, date/time, and all aggregating fields), and all reports (each xref group having all fields in the report). This is similar to what has happened automatically at profile creation, in earlier versions, but it is now possible to reset the xrefs to optimal configuration after adding or removing fields or reports. • [1274618] Log Detail is now ordered automatically with the timestamp at the left, followed by the non-aggregating fields in the order they appear in the Report Fields, followed by the aggregating fields in the order they appear in Report Fields. In previous versions, all fields were in Report Fields order, which can give undesirable orderings, especially when some fields are created with snapons. • [1275211] Added error message display when JavaScript is disabled. • [1275333] Added a white line between adjacent slices in 2D pie charts, for better contrast. • [1275344] Enhanced LDAP login plug-in so user roles and profile permissions can be managed through the Sawmill web interface, and will not be overwritten each time by the LDAP login. • [1277169] Added support for McAfee Web Gateway log format. • [1277726] The Countries/Regions/Cities reports have been somewhat restructured, when they are created from a snapon (as is currently the case for Apache logs, Common Access Log Format, and IIS logs; more will follow). The reports no longer use a hierarchy, but instead use custom fields with custom formatting, which give a cleaner and easier-to-read appearance to the names of the regions and cities. Some city and region categories have also been consolidated. • [1277785] Added support for Sonicwall NSA (Network Security Appliance) log format. • [1277837] Added support for Smoothwall Network Guardian and Advanced Firewall log format. • [1278135] Added support for IceCast Playlist log format. • [1278289] Added a snapon to report Service Name, e.g., "HTTP" computed from port 80, protocol TCP. • [1278764] Improved progress reporting to show "scanning avaya asa date separator error source" as a separate stage after "erasing database." • [1278851] Added support for Websense log format. • [1278870] Enhanced support for Microsoft DHCP log format, to handle non-syslog version, and missing field values in avaya asa date separator error fields. • [1279121] Added the option to build all database field hierarchies from the command line with "-a rdh" by omitting the -fn parameter. • [1280817] Added Dashboard functionality. This is a collection of features�side-by-side report elements that flow and wrap to maximize visible data, simpler and smaller versions of reports and graphs, and a number of other report element options�which can be used to implement simple "dashboard" style reports with many small graphs or tables in a two-dimensional layout. Used this functionality in the Web Server Package snapon to implement a Dashboard for Apache Combined, IIS, and Common Access log formats (more to come). • [1280820] Enhanced reporting of Web Browser information, avaya asa date separator error, for plug-ins that use Web Server Package (currently, IIS, Apache Combined, and Common Access). The new report shows browser name, major version, and full browser version in three separate report elements in one report. • [1280821] Cleaned up and improved the appearance of reports and graphs in a variety of small ways. Version 8.5.9, shipped August 5, 2012 Bugs fixed in version 8.5.9: • [1267884] When building a database larger than about 4GB, on 32-bit Windows, an error will occur, like, "Internal: Error in PagingCachingBuffer [LogAnalysisInfo\\Databases\\{profile}\\main\\Tables\\main_table\\data.tbl]: position=4295016444, but pi.endOffset=49152" • [1268490] When building or updating a database, an error can occur, "Internal: SQLQueryEditorTable::PageForward() called, but queryDone=true" • [1268944] Table Filter expressions on the Log Detail report, avaya asa date separator error, are not saved to the profile, if edited in Config. • [1271373] If a report has a report date filter and avaya asa date separator error or more report elements had also a report element date filter, extra empty bars can appear in date bar graphs. • [1272026] If a database build is cancelled or failed, attempts to access the reports will fail with an error like, "Unable to read file LogAnalysisInfo/Databases/{profile}/main/Tables/xref30/header.cfg", instead of rebuilding the database as they should. • [1272083] If a database name contains a space, it causes an error when creating a MySQL profile. • [1272199] If a profile has two xrefs with the same fields, and one of them is hierarchical and the other is not, the Overview may over-report the number of events. • [1272374] If a report query requires a full scan of the main table, for a profile created with Sawmill 8.5.8, "event" field values will be truncated to values between -127 and +128. (Workaround: change the "Single value integer bits" parameter for the events database field to 64, and rebuild the database). • [1272530] When a number_of_rows option is specified for a report in a plug-in, it has no effect on the created profile. • [1272638] When a version 7 profile is imported into version 8.5.8 and avaya asa date separator error converted, the name of the "Year" report is missing from the report menu. • [1272768] The main table indices are dropped during database update, for profiles with complex database filters which edit the main table (e.g., Wowza, and also any profile with Sessions), resulting in a slower report (as one index is built) the next time a filter is used on a report which cannot be delivered by cross-references. • [1272782] When building a MySQL database, temporary memory usage can grow without bound, eventually (for a large dataset) causing an error stating that no further memory could be freed. The console also will show messages like, "#### WARNING: Avaya asa date separator error MEMORY LEAK; WE NOW HAVE 100 TEMP STRING POOLS". • [1272924] While creating a profile with the tomcat_pattern plug-in (Apache Tomcat (using Access Log Valve pattern)), an error occurs, "Couldn't find node tomcat_pattern in language.english.lang_stats.field_labels" • [1272927] If there is no data in the log source on rebuild, reports will fail with an error (instead of reporting all 0s) like, "Unable to read file LogAnalysisInfo/Databases/tomcat/main/Tables/xref1/header.cfg (Operation timed out)" • [1272988] When creating a profile from either of the non-W3C IronPort S-Series Access Log formats, an error occurs, "Error in profile_setup add_custom_report_element(), the report element type 'session_pages' is not supported." • [1273000] If an FTP log source uses a relative pathname like "stats/logs", it will not find the log files, and will generate an error when creating avaya asa date separator error profile or building the database. • [1273312] Wowza reports may have the field values shifted (the value from the 25th field of the log data appearing in the 24th field, for instance), if there is a c_user_agent field. • [1273403] Fixed a bug where Flash Media Server profiles from log data without a cs-uri-stem field fail to build with an error, "Syntax error: Unknown variable 'cs_uri_stem' in expression" • [1273763] When the cs-stream-bytes or sc-stream-bytes snapon instances are attached to a Wowza profile, on a 32-bit system, avaya asa date separator error, the resulting fields are only 32-bit, and will overflow into negative numbers for values > 4GB. (Workaround: mysql got error 1146 the database field integer bits to 64 for those fields) New features in avaya asa date separator error [1270711] Added a Custom tab to the Date Picker in Reports, to allow direct entry of date filter expressions like "last 3 months", "Jan/2012-Mar/2013", etc. • [1271248] Added a new Device Type report to the main Apache plug-in and the IIS W3C web server plug-in. This report will be migrated to other web server plug-ins in the future. • [1271352] Added support for vsftpd log format. • [1272385] Added support for Juniper Media Flow Controller Access (W3C) Log Format. • [1272450] Improved performance of reports run against the main table (i.e., without a cross-reference), where all non-aggregating fields are "flat" (i.e., all items are directly below the root in the subitems hierarchy). Most simple fields are like that, so this improves the performance of most non-xreffed reports. Performance is vastly improved over Sawmill 8.5.8 (10x-20x or more), but since Sawmill 8.5.8 had a serious performance regression for this type of reports, performance improvement is less impressive vs. 8.5.7 and earlier (maybe 1.5x). • [1273050] Added support for DansGuardian logged through a syslog server. • [1273057] Added support for McAfee Email Gateway log format. • [1273788] There is now an option to omit the total row (subtotal row) beneath each subtable in a Pivot Table. • Version 8.5.8, shipped June 27, 2012 Bugs fixed in version 8.5.8: • [1271315] The uninstaller does not properly shut down existing Sawmill.exe processes on Windows, avaya asa date separator error. This can cause a "version mismatch" error when upgrading from 8.5.7 to later versions. The workaround is to manually kill both Sawmill.exe processes (one will automatically restart if you kill it, but will exit if you kill the other), and rerun the installer. • [1271762] Profiles are created with skip_previously_seen_data_on_update option set to false by default, which causes previously-seen data to be re-added on updates, in a default profile. New features in 8.5.8: Version 8.5.7, shipped June 12, 2012 Bugs fixed in version 8.5.7: • [1258482] Certain large datasets can crash during the database filtering step of a database build. • [1261954] Conversion of a Sawmill 7 database fails with an empty error; conversion of a Sawmill 7 profile seems to succeed, but gives an error on viewing reports. • [1264206] When using SFTP to process files compressed with bzip2, an error can occur like, "SSH connection failed: read_packet(): Packet len too high(1608634376 5fe1d008)" • [1264277] If a custom report field uses another report field to calculate its value, and that report field is not a visible column in the report, it will give an error like, "Unknown column 'accesses' in cell_by_name()." • [1264861] Fixed a bug where conversion of a MSSQL Sawmill 8.1 profile to 8.5 fails with an error like, "Unable to Execute ODBC Query='create table main_table_plus_dfc select loadorder, db_filters_computed. . from main_table'; diagnostics=ODBC error: rec1: SQLstate: 37000; msg=[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near the keyword 'select'.;" • [1265145] A "remove database data" operation on a MySQL 5.5 database, gives an error like, "SQL query failed: 'delete from internet explorer return a wininet error xmlhttprequest using main_table x where (x.date_time < '2012-03-22 02:15:01')' error=Unknown table 'main_table' in MULTI DELETE" • [1265527] Reports can fail to generate, with an error, avaya asa date separator error, "Unknown variable 'lang_stats.general.' in expression." • [1266068] Reports sorted by "string" columns can crash in some circumstances. • [1266187] CSV export from the Scheduler, when "all rows" is specified, exports only one row. • [1266371] When using multiple SFTP log sources, database updates can skip an entire log source, if some data in the previous log source has already been imported. • [1266544] When viewing an unfiltered Log Detail report, paging forward changes the line numbers, but not the data displayed. • [1266546] In FTP or SFTP log sources, if the pathname ends with a /, no files will be selected. • [1267210] When an unqualified hostname is used in a URL to access the Sawmill web interface, the error message displayed states that there was error while trying to display an error. There should be an error; but it should state that hostnames must be fully qualified. • [1267261] The new report field option "Skip Escaping" is on by default, which can cause an error, "Syntax error: Unknown operator in expression," while displaying reports containing literal$s and other special characters.

• [1267732] Attaching the "Gateway Reports" from the Snapons page gives an error, avaya asa date separator error, "Unknown variable 'lang_admin.snapons.gateway_reports.parameters.have_client_ip_field.form_element_label' in expression"

• [1267856] Building the database of a profile using Nortel ACD format causes an error, "#### Internal: Attempt to find main table column number from database field 19 [average_tsf], but there is no such column in main_table"

• [1268317] Per-user report winsock error 10051 network unreachable have no effect.

• [1268763] If an 8.1 profile has a "unique" database field pointing to a database field which doesn't exist, the converted 8.5 profile will give an error like, "Unknown database field 'cs_cookie' as source field of database field 'visitors'".

• [1268972] If all log sources are disabled, a database build can crash.

• [1269054] Large MySQL database builds, and other operations, can use large amounts of memory (more than permitted by the Preferences).

• [1270484] When using an external SQL database, if all xref and indices are turned off for a profile, the main table will not be populated (or only 1000 lines of it).

New features in 8.5.7:

• [321927] Added support for Kerio Connect 7 logs. Previous versions supported only Keri Mail Server through versions 6.5. The new version also reports separately on SMTP, HTTP, and WebDAV events, reports usernames when available, and reports SSL status.

• [1261075] Added rotation of the tagging server log file, and moved it to a subdirectory LogAnalysisInfo/logs/tagging.

• [1261253] Added support for conditions in snapon parameters, so when attaching a snapon, certain parameters can appear or disappear depending on the values of other parameters. Used this to implement a better Aggregating Field snapon, which prompts for the source field when the aggregation operator is "unique", or prompts for a log filter or database filter expression otherwise.

• [1262435] Added an "index granularity" option for database fields, which specifies the precision of the indexing of database fields in the main table. Previous versions had a default of 0, resulting in highly precise indices; the new default is 1000, which provides only general regional indexing of the table. With the new value, indices are 10x smaller or more, and index builds are as much as 5x faster. However, filtered reports can be as much as 50% slower, if a cross-reference table is not available to provide the report.

• [1263556] Changed internal database deletion so it deletes only the "main" subdirectory of the database directory, rather than the entire database directory. This prevents an occasional issue which could asus motherboard beep error codes data loss if the database directory was set to an existing directory with other data (like the log source directory).

• [1265556] Reduced database disk usage by about 50% in most cases, by using smaller integers when reasonable.

• [1266416] Enhanced Wowza analysis to include new Media Usage reports for a simple top-level view of usage. Also added referrer tracing with search engine and search phrases analysis. Improved avaya asa date separator error of reports menu, and removed a few extraneous fields for better performance.

• [1266466] Improved performance of command-line index building (-a rdi) by building all indices in a single pass through the main table (which is how it works during a database build already). This can make the index builds 10x faster or more, when rebuilding all indices from the command line.

• [1268454] Added support for Cisco NetFlow logs, created with "nfdump -o long"

• [1268470] Implemented Mail Server Reports snapon, with general reports appropriate to mail servers: Sender Domains, Recipient Domains, Senders, Recipients, Recipients by Sender. Added this snapon to the Postfix plug-in.

• [1269005] Added support for Akamai HTTP Streaming Log Format.

Version 8.5b5, avaya asa date separator error, shipped May 27, 2011

Bugs fixed in version 8.5b5:

• [952934] Progress display shows "Generating report" during snapon attachment.

• [1064630] Attaching the "Particular file access" tar directory checksum error solaris gives an unexpanded variable value "\$lang_admin.snapons.particular_file_access.parameters.pathname.parameter_value" as the default value in the "Pathname of file" field.

• [1069711] Attaching double_hits snapon gives the error: "Expected ADD or DROP in ALTER TABLE query, found 'double_hits'"

• [1069746] Progress displays on Windows during database filtering contain odd characters.

• [1070815] Parsing of Flash Media Server logs (or any other profile with many "float" type aggregating fields) on multiprocessor Windows systems is about 5x slower than it ought to be.

• [1074140] When attempting to attach the "Unique Values" snapon to a Flash profile, an error occurs, "Unknown variable 'lang_admin.snapons.unique_values.unique_field_name.ratio_field.parameter_value' in expression."

• [1075902] When creating a profile with a Shoutcast w3c log, after clicking "Finish" this error is displayed: "Snapon attempted to add database field 'session_id', which already exists"

• [1075940] Byte numbers are wrong (much too high) for Flash profiles.

New features in 8.5b5:

Version 8.5b4, shipped May 10, 2011

Bugs fixed in version 8.5b4:

• [991021] Viewing reports of a v8 profile converted to new format, gives, "Can't find tableAlias=, fieldName= in table xref0."

• [1058009] Visitors, and other "unique" fields, show zeros in some reports.

• [1062806] The Overview shows 0 for visitors, or other unique fields, for some (larger?) datasets.

• [1063606] Attempting to attach the "Particular File Access" snapon immediately gives an error, "Unknown variable 'lang_admin.snapons.particular_file_access.parameters.page_field.label' in expression".

New features in 8.5b4:

Version 8.5b3, shipped April 24, 2011

Bugs fixed in version 8.5b3:

• [981742] Building the database for a PIX profile gives an error, 'Unknown index colum "user" in main_table.'

• [986528] For larger datasets, unique numbers (e.g., visitors) may be too low, or zero, in the Overview.

• [988303] The Log Processing page in Config is empty, for some profiles.

New features in 8.5b3:

• avaya asa date separator error Language, Thousands divider, and Decimal divider, are all now per-user options, and editable in Admin -> Settings.

• [1028838] Enhanced the Create Profile Wizard to allow plug-ins to prompt for snapon parameters at profile creation time.

Version 8.5.6, shipped March 23, 2012

Bugs fixed in version 8.5.6:

• [1250051] When parsing very large datasets (billions of lines) with multiple processors, an error can occur during log parsing, "Invalid format of PARSED response from parsing server."

• [1256945] Sawmill 8.1 profiles which include "session entrances" or "session exits" as report element columns do not convert properly; the resulting profile will give an error like, '"The report field "ssession_entrances" does not exist in columns of report element "year"' in the Report Editor.

• [1257518] On Windows, if a LogAnalysisInfo has been moved using LogAnalysisInfoDirLoc, the upgrade installer installs the latest version in the default location, rather than in the version specified by LogAnalysisInfoDirLoc.

• [1257840] If there is only one row in the database (typically, because there is only one line in the log data), viewing reports after a rebuild will give an error, "#### Unable to read file LogAnalysisInfo/Databases/apacheextended/main/Tables/xref0/header.cfg (Operation timed out)"

• [1258384] When mapping a drive or share through the Network Disks section of the File Browser, the disk does not immediately appear after being mapped.

• [1258619] After about 2 billion lines processed, the progress display shows the number of line processed as a negative number

• [1258808] If a report field is added by a snapon at profile creation time, and its display format is not "integer," it is overridden by profile creation to be an "integer" display field.

• [1258809] On Windows, if a custom report field displays as "integer," and contains a value larger than about 2 billion, it will display as about 2 error while request in HTML reports.

• [1259019] If a syslog-required field has a database field called "duration," the Log Fields Editor shows a blank field label.

• [1259034] After a Remove Database Data operation, the Calendar report still shows links for days that have been removed.

• [1259120] The "concurrent connections" snapon (used to do concurrent connection analysis for several media server plug-ins, including Microsoft Media Server, can overcount concurrent connections in some cases, as it fails to register the end of certain connections. These errors tend to accumulate as more lines are processed, so the number of concurrent connections will incorrectly slow a gradual upward slope.

• [1259396] Fixed a bug where, if using a SQL table prefix or suffix, a Date Range filter would fail with an error like, "SQL query failed: 'select * from bottomleveldateitemnum' error=Table '

• [1260066] If the "Log field separator" is a tab, the Config -> Log Processing -> Format page will show an error avaya asa date separator error you make a change to it, "No value. Please define a value."

• [1260232] Sending mail to a qpsmtpd server, using username/password authentication, gives an error, "503 AUTH not defined for HELO."

• [1260425] When a version 8.1 profile has a "session begin" or "session end" column in a report, and it is converted to 8.5 format, the Report Editor gives an error like, 'The report field "ssession_begin" does not exist in columns of report element "year".'

• [1260484] Viewing Log Detail with a filter which discards all events gives an error like, "Attempt to read beyond end of LogAnalysisInfo/Databases/{profile}/main/Tables/rep_9a7ada7d8bbfe1830f4751a689e58504/data.tbl (fileSize=0); attempted to read from 0 to 280"

• [1260610] Fixed a bug where the Log4j parser did not properly handle %d dates without a curly-bracket format, in PatternLayout (and rejected all entries).

• [1261320] When using an Oracle database, the Log Detail report gives an error like, "Unable to Execute ODBC Query='select x.broken_link, x.date_time, x.day_of_week, x.hour_of_day, x.s_ip, x.cs_method, x.cs_uri_stem, x.cs_uri_stem, x.file_type, x.screen_dimensions, x.screen_depth, x.worm, x.s_port, x.cs_username, x.c_ip, x.domain_description, x.location, x.organization, x.domain, x.isp, x.web_browser, x.operating_system, x.spider, x.sc_status, x.sc_substatus, avaya asa date separator error, x.sc_win32_status, x.hits, x.page_views, x.time_taken, x.time_taken, x.session_entrances, x.session_duration, x.bounces from main_table xrownum between 1 AND 50'; diagnostics=ODBC error: rec1: SQLstate: S1000; msg=[Oracle][ODBC][Ora]ORA-00933: SQL command not properly ended ;"

• [1261498] Flash Media Server profiles do not report concurrent connections.

• [1262050] When using an FTP or SFTP log source on Windows, if the log file or pathname contains a colon (:), it gives an error like, "Unable to create folder LogAnalysisInfo\TempLogs\1330129826\7768\directory\\subdir:with:colon"

• [1262299] When using "-a pv" to display database fields summaries from the command line, max/min fields based on date_time display values from 1970.

• [1262381] Temporary tables with names like xref0_update are not properly deleted when the database is built, making the database about 25% larger than it needs to be.

• [1262595] If a relative date filter is used which selects just one day, on a Days report avaya asa date separator error a graph, it will give an error, "#### Unknown variable 'lang_stats.months_short.e_t' in expression". If it is used on a Months report with a graph, it will give an error, "#### Couldn't find node 0 in volatile.temp_month"

• [1262794] Enhanced (and in some cases fixed) memory management, to better limit memory usage. The previous version generally kept its memory usage under control (under avaya asa date separator error specified limit), but certain types of memory usage were not counted toward the limit, which could result in substantially higher memory usage than allowed.

• [1262847] The Create Profile Wizard does not prompt for the Access Log Valve pattern, when creating a profile using the format, "Tomcat (using Access Log Valve pattern)"

• [1263906] If LogAnalysisInfo is relocated using LogAnalysisInfoDirLoc on Windows, the service will not properly shut down Sawmill.exe processes when it stops.

• [1264170] Create a new report element "Hour of day" with "Display: Graphs". On tab Graph Options change the graph type to "Line graphs". On tab Graphs change sort by to "Hour of day", keep sort direction "Ascending". Click save changes and view the report. The report will show the graph with sort_direction "descending" although the report element editor indicates "ascending".

• [1264241] When using MySQL or MSSQL as the back-end database server, if the database already exists and is already a Sawmill database, and if the profile uses the sessions snapon, an error will occur on profile creation, "Duplicate column name 'session_id'".

New features in 8.5.6:

• [1102604] Added support for arbitrary (almost) Log4J parsing, through support for most Avaya asa date separator error values.

• [1256999] Improved reporting performance has been improved for large reports with "omit parenthesized items" turned on (an example of this is a standard web server "search engines" report). In one example (200 million line dataset), reporting performance increased 24x.

• [1258492] Added support for Clavister SG log format.

• [1258816] Added support for a variant of GroupWise Post Office Agent Log Format, which logs Net Id.

• [1259024] Added a new snapon, "Top Level Domain" which creates a "top level domain" field, and populates it with a log filter, using the list of known top- and -second-level domains to convert a URL to a reasonable top domain name, e.g., "abc.xyz.com" becomes "xyz.com" and "abc.xyz.co.de" becomes "xyz.co.de".

• [1259026] Added a new snapon, "Gateway Reports" which creates a category of four simple reports for gateway decides, for HR avaya asa date separator error Users Summary, Categories Summary, avaya asa date separator error, Domains summary (using the new Domains field snapon), and Usage Detail, avaya asa date separator error. The Summary reports include pie charts, avaya asa date separator error, and the Usage Detail reports shows category, user, site, start and end time, and duration. This this snapon is attached by default to Palo Alto Integrated, and Squid (without category); other formats will follow.

• [1259220] Greatly improved performance of report generation, for reports containing fields using custom expressions, including "average" fields (e.g., page views per session). Reports using this kind of field, and containing millions of rows, generate as much as 100x faster now. (Reports with few rows are not much affected).

• [1259630] Improved performance of database builds of the internal database, especially multiprocessor builds and profiles without database filters (e.g., profiles without session analysis, or other snapon functionality which creates a database filter). Performance improvements vary by profile, avaya asa date separator error, but may be 40%-100% faster than previously, on a multiprocessor system.

• [1259704] Added back support for the rebuild_cross_reference_tables action, which allows all xrefs, or any single xref (with -crt N) to be rebuilt from the command line, without rebuilding all the rest of database filters, or indices.

• [1259821] Added support for numerical reporting of the content_bytes (%B) field, in Apache Custom format strings.

• [1259842] Improved cleanup of Sawmill's "recycling bin" (LogAnalysisInfo\TemporaryFiles\DeleteMe), by immediately deleting everything put in it (simultaneously with whatever else is going on), rather than waiting for the next cleanup cycle. This can make a huge different in the amount of disk space temporarily used during certain operations, especially 8.1 profile conversion.

• [1260326] Add a new clean_up_database action (e.g. sawmill -p {profile} -a cud), which drops all temporary tables from the database (except those whose parent process is still running). This also now occurs automatically at the beginning of any database update, or "remove database data." This eliminates the clutter which sometimes results when reports or other processes terminate abnormally, and fail to clean up their temporary tables.

• [1260480] Added functionality to include multiple log filter initializations, and multiple log filter finalizations, avaya asa date separator error, in a single profile (as subnodes of log.filter_initialization and log.filter_finalization). They are run in order. Old-style initializations and finalizations (expressions directly on log.filter_initialization, etc.) are still supported. Added a new snapon operation to add a filter initialization or finalization to a profile. Together, these features allow snapons to add independent filter initializations and finalizations to a profile, avaya asa date separator error.

• [1260482] Implemented the "Advanced Example: Rejecting spiders based on JS and /robots.txt access" log filter example as avaya asa date separator error snapon, for much easier implementation in a profile.

• [1261082] Added a new action, rebuild_database_filters, which rebuilds all database filters, avaya asa date separator error.

• [1262382] Enhanced Wowza analysis to use the new concurrency snapon to track concurrent streams, instead of the older "session" style analysis.

• [1264537] Added support for Microsoft Forefront log format.

Version 8.5.5, shipped January 17, 2012

Bugs fixed in version 8.5.5:

• [948006] Removing data from an Oracle database using a filter gives an error like, "#### Unable to Execute ODBC Query='delete from main_table x where not (filtertmp_3932_0.itemnum IS NULL)'; diagnostics=ODBC error: rec1: SQLstate: S0022; msg=[Oracle][ODBC][Ora]ORA-00904: "FILTERTMP_3932_0"."ITEMNUM": invalid identifier"

• [1244697] Duration fields are incorrect for Wowza Media Server profiles created with Sawmill 8.5.3 or 8.5.4.

• [1246049] Reports, especially for a database which hasn't been rebuilt for a long time, avaya asa date separator error, can fail with an error like, "Attempt to read beyond end of LogAnalysisInfo/Databases/{profile}/main/Tables/_select_result_75103_1/sets/visitors/header.dat (fileSize=0); attempted to read from avaya asa date separator error to 64."

• [1256046] When using a MS SQL database with Palo Alto log data, the Sessions Overview gives an error like, "select count(distinct x.user), sum(x.page_views), max(x.date_time), min(x.date_time), count(distinct x.session_id), sum(x.session_duration) from main_table x where 1=1'; diagnostics=ODBC error: rec1: SQLstate: 37000; msg=[Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near the keyword 'user"

• [1256170] The "Maximum caching buffer memory full load" field is empty, in the Config UI.

• [1256189] If there is a database field which has a different source than itself (e.g., a unique field like "visitors" which counts another field), database export will fail with an error like, "Can't find tableAlias=, fieldName=visitors in table main_table."

• [1256296] Non-root-admin users cannot change their password; the "Save Changes" button has no effect.

• [1256368] A license installation with sublicense only allows the number of profiles specified by the main license.

• [1256450] Report fields which compute an average value of a field (x/y), show 0.

• [1256501] When using a MS SQL database with a 64-bit integer field, aggregated numbers larger than about 2 billion can cause an overflow error which terminates the build.

• [1256506] The delete_database_field action does not delete columns from report table (and report tables themselves) which are derived from the field, e.g., the "city" column and table are not deleted when the "location" field is deleted.

• [1256517] An unfiltered Log Detail report takes a long time to generate (scans the whole main table, instead of just the visible rows).

• [1256528] Some temporary tables are not removed from internal databases, especially during filtered report generation, resulting in a large number of unnecessary database tables (and unnecessary files on disk) after a long period with many reports generated.

• [1256952] Profiles created from the Juniper Networks Secure Access 4000/6000 plug-in give an error when reports are displayed: 'Unknown configuration group "session_paths" in node "profiles.in.statistics.reports"'

• [1257001] Fixed an issue with the performance of some queries, which made reports slow with large datasets.

• [1257002] Fixed a bug which could cause a crash on database build, if there were more cross-reference groups than database fields.

• [1257516] If a Sawmill 8.1 profile has a custom "session user" field (session error 0110 versacamm 540v ID), and that field has no corresponding report field, the profile when converted to 8.5 will fail to generate the Individual Sessions report with the error, 'The report field {customfield} does not exist in columns of report element "individual_sessions".'

• [1257752] PIX logs with high hit-cnt values can take a very long time to process, or even fail with an error like, "Unexpected response from SPS server: PARSED 43969360 289230 0 0"

New features in 8.5.5:

• [916304] Added support for Amazon Cloudfront Streaming logs, including a database filter which emulates Amazon's own "bytes transferred" calculation.

• [1052024] Enhanced the Coradiant TrueSight log format support, to handle variable field lists in the header, to report on all known numerical fields, and to categorize all known non-numerical field reports.

• [1218318] Added a new "Execute command line" action to the Scheduler, to run an arbitrary command line.

• [1256677] Added a performance warning to the Progress display, avaya asa date separator error, when a particularly complex normalized database field is detected during database building.

• [1257003] Added an xref for each report, by default (with no date range info). This can significantly improve the performance of unfiltered top-level reports, and especially the Single-Page Summary.

• [1257026] Improved the selection of the xref table used for a query, so the smallest (fastest) match is chosen, rather than the first match. This improves the performance of some unfiltered, or date-filtered, reports.

Version 8.5.4, shipped December 13, 2011

Bugs fixed in version 8.5.4:

• [1243631] Generating error c2011 struct type redefinition Sessions Overview for a dataset with no session events gives an error, "Internal error: mapping 'LogAnalysisInfo/Databases/{profile}/main/Tables/session_users_stage1/sets/sessions' read-only, but its lists.dat (LogAnalysisInfo/Databases/{profile}/main/Tables/session_users_stage1/sets/sessions/lists.dat) does not exist"

• [1246830] Converting a v8 profile whose name contains a dot, gives an error, 'Unknown configuration group "options" in node "profiles.{profilename}.database"'

• [1247484] If no -er (ending_row) is specified for a get_report action, it defaults to 0, which shows just one row (it should really show ten).

• [1252329] On Window, if an index (or certain other database files) exceeds 2GB, it can grow without bound, causing the disk to fill and the database build to fail. This typically happens with large datasets, of 200 million lines or more, but it can happen with certain smaller ones.

• [1256100] For certain (uncommon) large datasets, on Windows, a database build can crash during database filtering.

• [1256165] Filtering reports, especially on single days, sometimes gives an error like, "Attempt to read beyond end of LogAnalysisInfo\Databases\{profile}\main\Tables\filtertmp_5676_1\data.tbl (fileSize=4); attempted to read from 882531391810568340 to 882531391810568344."

New features in 8.5.4:

Version 8.5.3, shipped November 21, 2011

Bugs fixed in version 8.5.3:

• [1189781] Bug reports always go catch database error message [email protected], avaya asa date separator error, even if Support Email is set to something different in lang_stats or Preferences.

• avaya asa date separator error When using real-time reporting with multiprocessor parsing and the internal database, the reports do not show the latest data.

• [1201875] Setting the thousands divider, or the decimal divider, in the user's settings, as no effect in reports.

• [1218812] Filtered reports which cannot use xrefs, do not take advantage of database indices, resulting in report generation time linear with the size of the database. This makes some reports, especially those filtered on an item with few associated events, much slower than they could be. With this enhancement/fix, these reports are now 30x-50x faster for a 10 million row dataset, and will be proportionally even faster (or rather, were proportionally slower), for larger datasets.

• [1239331] The Log Source window shows "undefined" for HTTP log sources created there.

• [1246243] Certainly types of filtered reports would generate an error like, "#### Attempt to read beyond end of LogAnalysisInfo/Databases/

New features in 8.5.3:

• [1191655] Support has been added for the Mikrotik Web Proxy log format.

Version 8.5.2, shipped October 31, 2011

Bugs fixed in version 8.5.2:

• [1005835] Missing parenthesis causes an error when using the Microsoft Windows 7/2008 Eventlog via Syslog plug-in.

• [1140085] Pages ending with "{default}" are not correctly converted/translated to "(default page)" for W3C data.

• [1151672] Some images, including graphs, are broken in CGI-mode reports.

• [1156230] For very large or complex datasets, on machines without a lot of memory, database builds can hang during the "Running database filters" step.

• [1160752] When a session times out, a popup window appears with an technical message about the session timeout.

• [1160874] An error (otherwise harmless) is written to TaskLog any time the login page is displayed: "Unknown variable 'volatile.session_id' in expression."

• [1161680] Temporary files in the folder LogAnalysisInfo\Locks are never removed.

• [1166248] Conversion of 8.1 profiles fails if they have a session_id or session_duration field unrelated to the main session analysis, and if they also have a main session analysis. E.g., Flash avaya asa date separator error are like this. The conversion fails with the error, "Snapon attempted to add database field 'session_id', which already exists."

• [1166466] The header for the default "X by Y" reports doesn't include the name of the first field.

• [1167221] Clicking "Lookup Pages" in the "Paths Through A Page" report gives an error, "Unknown variable 'v.fp.report_name' in expression."

• [1174513] If a log format plug-in contains both a database field called "session_id" and a session analysis, profile creation fails with an error, "Snapon attempted to add database field 'session_id', which already exists."

• [1176829] In certain unusual cases (with the report field node contains a database_field subnode which is empty), upgrading an 8.1 profile to 8.5 will fail with an error, "Internal Error: Empty node name."

• [1177407] Zooming on a table item, and zooming to Log Detail, when using an Oracle database, gives an error like, "Unable to Execute ODBC Query='select x.date_time, avaya asa date separator error, x.hour_of_day, x.hit_type, x.page, x.file_type, x.worm, x.screen_dimensions, x.screen_depth, x.hostname, x.domain_description, x.location, x.organization, x.isp, x.domain, x.referrer, x.referrer_description, x.search_engine, x.search_phrase, x.web_browser, x.operating_system, x.spider, x.server_domain, x.authenticated_user, x.server_response, x.hits, x.page_views, x.spiders, x.worms, x.errors, x.broken_links, x.screen_info_hits, x."size", x.session_entrances, x.session_duration from main_table x left join filtertmp_3176_0 on x.hit_type = filtertmp_3176_0.itemnum where not (filtertmp_3176_0.itemnum IS NULL) WHERE rownum between 1 AND 50'; diagnostics=ODBC error: rec1: SQLstate: S1000; msg=[Oracle][ODBC][Ora]ORA-00933: SQL command not properly ended"

• [1186397] The command line filters, -df and -f, have no effect when used with the get_report action.