Page 1 Meeting Exchange ® 5.1 Administration and Maintenance Guide CS700/CS780 Conferencing Server 04-602673 Issue 1 November 2008...
Page 2 Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an e-mail or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative...
Page 3: Table Of Contents
Contents Preface ........Audience ........Conventions .
Page 4 Contents Peripherals ........Chapter 2: Configuring System-Wide Settings ....Introduction .
Page 5 Contents Annunciator Messages ....... . Recording Messages ....... About Annunciator Numbering .
Page 6 Contents T3 Status Utility, t3stat ......Configuring the FDAPI ....... . Specifying Flex-DAPI Channels.
Page 7 Contents View ........Hard Disk Status .
Page 8 Contents Installing OpenSSL ......Installing SSH ....... . . Environment Variables .
Page 9 Contents Real-time CDRs and CODRs ......The autocdr Process ....... Record Format .
Page 10 Contents Cleaning System Drives ......File Maintenance ........Check Files .
Page 11: Preface
TCP/IP protocols, and UNIX commands. Contact a technical support representative if you require assistance with configuring system and audio conference settings or require in-depth training on using the CS700/CS780 Conferencing Server or Avaya desktop products. Conventions...
Page 12: Related Documents
Provides information about actions that may disrupt or damage CAUTION: system resources. Related Documents The following documents may provide additional information: Meeting Exchange 5.1 CS700/CS780 Conferencing Server Release Notes ● Meeting Exchange 5.1 Installing the S700/780 Conferencing Server ● Meeting Exchange 5.1 Relational Database Guide ●...
Page 13: How To Get Help
How to Get Help Information Telephone +1-877-742-8351 +1-877-742-8352 Web site http://www.avaya.com/support US and Canada Technical Support *1-800-242-2121 E-mail: MXCustomerSupp@avaya.com Fax: +1-978-677-5134 International Technical Support +353-1-207-5667 (CS700/CS780) +353-1-207-5666 (CS7000) E-mail: MXdubsupp@avaya.com International Meeting Exchange E-mail: MXSupport@avaya.com Technical Support Issue 1 November 2008...
Page 14 Preface 14 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 15: Chapter 1: System Features
Introduction The CS700/CS780 Conferencing Server is a scalable, multi-featured audioconferencing system designed to support a variety of audioconferencing requirements including: Control of large conferences from a single user interface.
Page 16: System Configuration Overview
● components. System Configuration Overview The CS700/CS780 can be configured to conduct audio conferences using Public Switched Telephone (PSTN) lines. Operator audio paths and links can be set up as conventional lines. Figure 1 depicts various system components and features in a PSTN environment.
Page 17: Audioconferencing Features
The CS700/CS780 can be configured for support operators, who can manage and monitor conferences alone or as part of a team.
Page 18: On-Demand Conferences
System Features Other features that can be configured for unattended conferences on a system-wide basis include: Auto Extend Duration — The system attempts to extend a conference beyond its ● scheduled end time. Auto Extend Ports — The system attempts to allocate additional ports to conference to ●...
Page 19: Flex Conferences
Audioconferencing Features Flex Conferences Flex is a type of unattended, on-demand conference in which participants can join a conference directly. This “reservationless” conference uses a profile to keep track of all the selected conference features, such as Hang up or Name Record/Playback. Once the system administrator has defined the settings in a profile, participants can join Flex conferences on a first-come, first-served basis.
Page 20: External Passcode Validation
System Features conference lines than the system supports. In light of the fact that some conference participants do not attend conferences as scheduled, this feature ensures that those scheduled yet unused lines are immediately available for other conferences. Refer to Chapter 7: Configuring Conference Scheduler on page 173 for details on apportioning a percentage of system lines for Conference Overbooking that will meet your requirements.
Page 21: Sub-Conferences
The CS700/CS780 can be configured to allow a conferee, a moderator, or both to convene a sub-conference from a main conference. Both conferees and moderators, however, can join a sub-conference regardless of which type of conference participant started the conference.
Page 22: How Participants Access And Exit A Sub-Conference
System Features The values for the Cross Ref fields and the values for the Conference ID fields for main ● and sub-conference CODRs are identical. This enables billing or auditing personnel to correctly associate sub-conferences with main conferences. The User Conf Type field in a sub-conference CODR identifies the conference as a ●...
Page 23: Conference Scheduler
Audioconferencing Features Questions and answers about the role of a moderator in a main conference and a sub-conference: What happens when the only or last moderator in the main conference joins a ● sub-conference and the system is configured to automatically end a conference (Auto Hang-up feature enabled) when the last moderator in the conference disconnects? The system does not end the main conference.
Page 24: Auto Blast
System Features Scheduler also enables you to view and print scheduling reports and purge expired conference information. See the ACS Managing and Scheduling Conferences Guide for Conference Scheduler details. Auto Blast The optional Auto Blast feature provides blast-dial capability for moderators in unattended conferences.
Page 25: System Component Alerts
Conference Call Modes objects and platform-specific object, the MIB provides remote monitoring support for crucial system components. Unsolicited data from SNMP trap objects notify network management stations of actual and potential problems with system, processor, memory, and network components (see System Component Alerts on page 25.
Page 26: How A Conferee Is Placed In A Conference
System Features automatically disconnected. In addition, you can run a conference that is unattended except for an operator initiated blast dial. The system also permits combinations of certain modes. For example, the moderator of an attended dial-in conference can ask an operator to dial out to a conferee who has not dialed in. How a Conferee Is Placed in a Conference Conferees gain access to conferences in eight different ways.
Page 27: Hardware Features
Telecommunication Network Interface Cards (NICs), each with eight RJ-45 ports that ● support scalable T1, T1-ISDN, or E1 channel configurations. The CS700 supports up to six NICs (1152 T1, 1104 T1-ISDN PRI, and 1200 E1 ● channels). Issue 1 November 2008...
Page 28 Up to three (3) hot-swappable Digital Signal Processing (DSP) cards in the CS780, and six ● (6) in the CS700. DSP cards process audioconference operations. Use these equations to calculate the number of DSP resources: T1 systems require T1 = 1 DSP board.
Page 29 Hardware Features CPU host processor card with a minimum processing power and RAM to support the ● installed system features. Table 2 identifies the supported T1/E1 that are required for various system features and Table 3 the supported T3 system configurations. Table 2: Supported T1/E1 Configurations Max # Calls/...
Page 30: Standard System Components
2016 2016 CS780 5551 CS780 5551 Redundant, hot-swappable power supplies: up to four for the CS700; up to two for the ● CS780. RCA Jack (on a DSP card) for connection to analog music source (CD player for ● example).
Page 31 The serial and ethernet ports on the NIC card and the serial port on the DSP card are only used by the CS700/CS780 developers for application development.
Page 32 System Features Figure 2: CS700 Components ( RAID configuration differs.) Front Rear Figure notes: 1. ESD Jack 12. CD-ROM Drive 22. Hard Drive (removable) 2. DSP Card 13. DSP Monitor Port 23. RCA Jack 3. CPU Card (ZT5551) 14. Ethernet B Port 24.
Page 33 Hardware Features Figure 3: CS780 Components ( RAID configuration differs. Rear Front Figure notes: 1. Power Supply 2. DSP Card 3. DSP Monitor Port 4. USB Port 5. RCA Jack 6. 10 Base T LAN Port 7. NIC Monitor Port 8.
Page 34: Network/Dsp Card Configurations
DSP cards in the system chassis. NIC/DSP Card Combinations The CS780 chassis holds up to three NIC/DSP pairs, and the CS700 holds up to six NIC/DSP pairs. The DSP system dynamically allocates DSP processing bandwidth so that all channels in the same conference are processed on the same DSP node.
Page 35 Hardware Features Table 4: Possible NIC/DSP Configurations (continued) Number of Ports Number of NICs Number of DSPs T1: 192 T1 (ISDN PRI): 184 E1: 180 T1: 384 T1 (ISDN PRI): 368 E1: 390 T1: 576 T1 (ISDN PRI): 552 E1: 600 T1: 768 T1 (ISDN PRI): 736 E1: 780...
Page 36 Figure 4: Network and DSP Card Numbering DSPs NICs NICs DSPs CS780 CS700 1 2 3 4 5 6 6 5 4 3 2 1 1 2 3 1 2 3 CPU Front View Front View Input/Output Ports Table 5 lists and describes system ports.
Page 37 1 in Back LAN A CS780 Front 8-pin modular jack Primary 10baseT/ (Ethernet) 100baseT LAN port. CS700 Back On the CS700 only the rear Note: port is enabled during May be manufacturing. However, changed in this configuration can be BIOS reversed by an authorized service technician.
Page 38: Media Drives
39.) Power Supply The CS700 can be configured with up to four power supply modules, which can provide up to 600 watts of output. The CS780 can be configured with either one or two power supply modules, which can provide up to 600 watts of output. Power supplies for both system models are hot swappable.
Page 39: Raid System
Hardware Features RAID System The optional RAID System configuration replaces the system’s standard on-board hard drive and the optional removable hard drive. Figure 5 shows RAID components located on the front of the system. Figure 5: RAID Components on front of system Figure notes: 1.
Page 40 8 GB drive for the /usr3 directory, and one 35 GB drive, which is unused. The maximum physical array size is approximately 51 GB. A single RAID system can be configured to support one CS700/CS780 on one of the system’s backplane segments or two CS700/CS780s on each of the system’s two backplane segments.
Page 41 Hardware Features Figure 8: CS700/CS780 Single System RAID Configuration CS700 Configuration Backplane Segment A Backplane Segment B 10 11 CS780 Configuration Redundant Disk Array Hot Standby Unused Backplane Segment A Backplane Segment B Floppy Disk Drive 10 11 Redundant Disk Array Hot Standby...
Page 42: Status Leds
System Features Figure 9: CS700/CS780 Dual System RAID Configuration Backplane Segment A Backplane Segment B 10 11 Redundant Disk Array Hot Standby Redundant Disk Array Hot Standby Floppy Disk Floppy Disk Drive Drive RAID Controller RAID Controller Module Interface Module Interface Contact Customer Support for information on RAID system installation and configuration options.
Page 43 Power Supply LEDs Status Indications INPUT FAULT (CS700) STATUS (CS780) Green = OK INPUT (CS700) On = OK INPUT FAULT FAIL (CS700) On = Failure Figure notes: 1. The CPU’s yellow Major Alarm LED flashes once every 10 seconds to notify you that the alarm system is correctly functioning.
Page 44: Peripherals
Hot Swap LED Peripherals A CS700/CS780 installation typically includes the following peripheral devices: UPS — To protect against data loss and prevent spontaneous system shutdown, Avaya ● recommends the use of an Uninterruptible Power Supply (UPS) that provides 350 W or more.
Page 45: Chapter 2: Configuring System-Wide Settings
Chapter 2: Configuring System-Wide Settings Describes how to configure various system-wide conference settings, how to configure annunciator delay, dial delay, disconnect notification, wink timeout, and line fault settings, how to set the system date and time, how to configure blast dial settings, and how to assign voice messages and tones to conference events.
Page 46 Configuring System-Wide Settings Figure 12: System Configuration Note: If the PIN Code feature is installed on the system, then the System Configuration Note: screen will include a PIN Mode field in the below the Time Format field; when it is not installed, this space will be blank.
Page 47 System Configuration 3. Configure parameter values as desired. See Table 7 for parameter descriptions. 4. Save (or cancel) your changes. Table 7: System Configuration Parameters Parameter Description System Name Displays the TCP/IP host name assigned to the system when system software is installed. The name appears on screens and in various system files and serves as the alias for the system IP address.
Page 48 Configuring System-Wide Settings Table 7: System Configuration Parameters (continued) Parameter Description Digit Recognition Specifies the number of telephone keys conferees must press to use certain conference features. ONE (default) — The system requires conferees to press one ● digit for these features. TWO (recommended) —...
Page 49 System Configuration Table 7: System Configuration Parameters (continued) Parameter Description Automatic CDR Specifies whether the automatic call detail record (CDR) and Print conference detail record (CODR) exporting feature is enabled. This feature can be configured to process (for example, print) records in real-time: See Real-time CDRs and CODRs on page 296.
Page 50 Configuring System-Wide Settings Table 7: System Configuration Parameters (continued) Parameter Description First Person Specifies whether the system plays message 221; “You are the first Message participant in this conference”, when the first conferee enters a conference. ON — The message is played. ●...
Page 51 System Configuration Table 7: System Configuration Parameters (continued) Parameter Description Auto Extend Ports Specifies whether the system is able to allocate additional conferee ports (lines) to unattended conferences while they are in progress. OnDefault — The system attempts to allocate additional ports ●...
Page 52 Configuring System-Wide Settings Table 7: System Configuration Parameters (continued) Parameter Description Early Start Minutes Specifies whether conferees are allowed to enter unattended conferences earlier (1 - 30 minutes) than the scheduled start time if ports are available. OFF (default)— Conferees cannot enter conferences earlier ●...
Page 53 System Configuration Table 7: System Configuration Parameters (continued) Parameter Description Ignore DTMF Determines whether the system ignores DTMF commands entered Commands by conference participants. ON— The bridge ignores DTMF commands entered by ● conference participants, and will override any of the individual Conferee Mute and Conferee Gain settings.
Page 54 Configuring System-Wide Settings Table 7: System Configuration Parameters (continued) Parameter Description Automatic Conf. ID Specifies whether the system automatically assigns IDs for unscheduled attended conferences. (Conference IDs are required for CODRs or conference reports.) ON — The system automatically assigns a unique ●...
Page 55 System Configuration Table 7: System Configuration Parameters (continued) Parameter Description Starting Conf. ID Specifies the 12-digit starting number for system-assigned conference IDs. The default is 000000000001. The system increments IDs by 1 (000000000002, 000000000003, and so on). If you assign an ID using the scheduler or during a batch load process, that ID overrides the ID assigned by the system.
Page 56 Configuring System-Wide Settings Table 7: System Configuration Parameters (continued) Parameter Description Moderator Lecture Specifies whether moderators can mute all non-moderator lines. ON — Moderators can mute all non-moderator lines and ● place the conference in Lecture mode. Operator screens update to show that the conference is in Lecture mode, indicating that non-moderator lines within the conference are muted.
Page 57 System Configuration Table 7: System Configuration Parameters (continued) Parameter Description Sub Conferencing Specifies whether a conference participant can invoke a Mode sub-conference from a main conference by pressing *93 on their telephone keypad. If the system cannot fulfill a sub-conference request, it plays message 24, “This operation is currently unavailable.”...
Page 58 Configuring System-Wide Settings Table 7: System Configuration Parameters (continued) Parameter Description Date Format Specifies one of the following system date formats: US standard date format (default): mm/dd/yyyy ● An alternate format: yyyy/mm/dd ● International format: dd/mm/yyyy ● Note: Date Format has no effect on date formats in CDRs and CODRs.
Page 59 The Meeting Exchange applications which use the Note: Bridge Control Application Programming Interface (BCAPI), such as the Avaya Audio Console, support the pause feature during conference recording. Users cannot pause recordings via the DTMF commands or via the Avaya BridgeTalk application.
Page 60 Configuring System-Wide Settings Table 7: System Configuration Parameters (continued) Parameter Description Phone Number Specifies the number to dial when Bridge Record is set to Off-bridge. Dial String Details the DTMF digits that are sent to the external recording device after the recorder answers the call. Some of the information contained in the Dial String may be vendor specific.
Page 61 System Configuration Table 7: System Configuration Parameters (continued) Parameter Description DRP: Auto-gen Identifies whether the system automatically assigns names to filename recordings that are initiated by phone commands. OFF (default)—The system will not automatically assign a ● name to file recordings that were initiated by phone commands.
Page 62: System Supervision
Configuring System-Wide Settings Table 7: System Configuration Parameters (continued) Parameter Description Flex Leader Code Provides the option to have leader join a Flex flow conference upon entry of one passcode instead of the two required by default. ON - Leader joins conference upon entry of one code. ●...
Page 63 System Supervision Use this procedure to configure system supervision settings: 1. Select System Administrator Main > Configurations > Supervision Configuration. The system displays Supervision Configuration Screen. Figure 14: Supervision Configuration Screen Figure notes: The Dial Delay and Wink Timeout settings are not supported for this release ●...
Page 64 Configuring System-Wide Settings Table 8: Supervision Configuration Parameters (continued) Parameter Description Disconnect Mode This setting determines how the system handles lines in attended conferences that are disconnected from the far end (by the caller), and specifies whether an operator or the system puts disconnected lines back on hook.
Page 65 System Supervision Table 8: Supervision Configuration Parameters (continued) Parameter Description Disconnect Specifies whether or not disconnect messages appear on Notification operator workstation displays when lines disconnect from attended conferences. Disconnect Notification provides operators with additional information about a disconnecting line. ON —...
Page 66: Time-Sensitive Operator Assistance Configuration
Configuring System-Wide Settings Table 8: Supervision Configuration Parameters (continued) Parameter Description Wink Timeout Specifies how long the system waits for wink-back from the far end before disconnecting the line. Note: Not supported in this release. Note: Line Fault Specifies whether or not the system takes faulted lines off-hook. Operators fault lines to take them temporarily out of service.
Page 67 Time-sensitive Operator Assistance Configuration Important: The first rule on the Timed Assistance dialog always has the Data Type set to Important: DEFAULT. The system uses this rule when none of the other rules apply. Although you can configure the action of this rule, you can not delete this rule. 2.
Page 68: System Date And Time
Configuring System-Wide Settings Tip: Configuration data is saved to /dbase/admin/operatorhelp.txt. Tip: System Date and Time You should check the system’s date and time regularly. WARNING: Do not change the system date/time while conferences are active. This action WARNING: prevents the generation of valid CDRs and CODRs and can cause certain time-related conference features such as automatic hang-up and termination tones to work improperly.
Page 69: Blast Dial Parameters
Blast Dial Parameters To change the date or time or both: 1. Select System Administrator Main > System Date/Time. The system displays the System Date/Time. System Date/Time +-------System Date/Time--------+ ¦ ¦ ¦ Date (mm/dd/yyyy): 03/16/2006 ¦ ¦ Time (hh:mm) : 07:28 ¦...
Page 70 Configuring System-Wide Settings To configure blast dial parameters: 1. Select System Administrator Main > Configurations > Blast Dial Configuration. The system displays Blast Dial Configuration. Blast Dial Configuration +------Blast Dial Configuration-------+ ¦ ¦ ¦ Max. Channel Blast (1-16): 5 ¦ ¦...
Page 71: Voice Message Configuration
Voice Message Configuration Table 10: Blast Dial Parameters (continued) Parameter Description Scan Time The number of seconds (5 to 20) the system scans for (5 to 20) additional access code digits after a conferee enters the first digit. The default is 20 seconds. Be sure to adjust this parameter to accommodate the longest access code on your system.
Page 72 Configuring System-Wide Settings To configure system messages: 1. Select System Administrator Main > Configurations > Voice Message Configuration. The system displays the Voice Message Configuration screen. Voice Message Configuration +----------Voice Message Configuration----------+ ¦ ¦ ¦ ODO Messages (msg181-183) BOTH ¦ ¦...
Page 73: Operator Audio Paths
Operator Audio Paths Operator Audio Paths Operator audio communication with the system is typically supported on FDAPI Operator channels (see Configuring the FDAPI on page 163). Under some circumstances (FDAPI limitations for a system with a single network trunk or a faulty FDAPI channel for example) you may have to transfer an operator’s audio path from an FDAPI channel to a revenue channel to maintain operator audio support for attended conferences.
Page 74 Configuring System-Wide Settings 4. Enter the parameter values you want. Table 11 lists and describes parameters. 5. Save (or cancel) your changes. Table 11: Operator Configuration Parameters Parameter Description Printing Not implemented Beep Mode The system plays a tone when the system places a conferee in the Enter Queue, Help Queue, or Disconnect Mode.
Page 75 Operator Audio Paths Table 11: Operator Configuration Parameters (continued) Parameter Description Channel Displays the FDAPI Operator channel or lets you specify a revenue channel number. This parameter displays the FDAPI Operator channel ● number if the Remote parameter is set to N. This parameter lets you enter a channel number from the ●...
Page 76: Flex Configuration Settings
Configuring System-Wide Settings Flex Configuration Settings This section describes the required bridge settings for configuring Flex conference features. Table 12 to configure Flex system settings. Table 12: Flex Configuration Settings System Administrator Parameter / Setting Main Menu > Configurations > Moderator Lecture = Enable conference leaders to mute/ unmute non-leader line...
Page 77 Flex Configuration Settings Table 12: Flex Configuration Settings (continued) System Administrator Parameter / Setting Main Menu > Configure Scheduler Originator Dial Out The Unsecured setting enables leaders (ODO) = Unsecured to access available system channels for dial-outs. The All setting enables —or—...
Page 78 Configuring System-Wide Settings Table 12: Flex Configuration Settings (continued) System Administrator Parameter / Setting Main Menu > Configure Scheduler Flex Maximum Dial Specifies the maximum number of digits Out Digits allowed for dial out. Configure Scheduler Flex Leader Pin Modify Select one of the following conference-wide settings: ENABLED (Default).
Page 79: Chapter 3: Configuring Channels And Call Routing
Chapter 3: Configuring Channels and Call Routing This chapter discusses configuration options for ports or channels that are not configured for operator audio (see Operator Audio Paths on page 73) or for FDAPI functions (see Configuring the FDAPI on page 163). This chapter additionally describes how to configure call branding for DNIS and DDI calls processed by the system’s Call Routing feature.
Page 80: Understanding The Portgroupsib.txt File
Configuring Channels and Call Routing Consider the following when configuring the IPG: Specify Inbound Port Groups as a list of ranges. Do not overlap IPG ranges. ● Include all revenue lines in the list. ● Include a default IPG. The default does not require a range. ●...
Page 81 Establishing Port Groups Note: BridgeTalk refers to the autoconf setting as “ACS”. Note: When assigning conference numbers to unattended conferences, the system uses the first available (inactive) conference with the lowest conference number. To prevent conflicts on systems running both ACS and unattended lines, specify high-numbered conferences for ACS.
Page 82: Outbound Port Groups (Opg)
Configuring Channels and Call Routing Y (default) — Enable call routing. ● Incoming calls on channels with Call Routing enabled are processed according to the specifications in the system’s Call Branding table. For more information on Call Branding, Branding Calls using cbutil on page 86.
Page 83 Establishing Port Groups Tip: To ensure that dial-in participants are not inadvertently routed to FDAPI lines, do Tip: not include FDAPI lines in Outbound Port Groups. See Configuring the FDAPI page 163. Configuring the OPG is a two-part process: 1. Edit the Port Groups Configuration File (PortGroupsOB.txt). 2.
Page 84: Call Routing Configuration
Configuring Channels and Call Routing Outbound Port Group File version 1.1 group OPG_One default range 1 24 range 49 72 descend group OPG_Two range 49 72 ascend range 1 24 descend Call Routing Configuration The Call Routing feature provides automated processing of incoming calls based on DNIS and DDI parameters.
Page 85 Call Routing Configuration Call Routing Considerations for Operators Operators have additional considerations when a system uses DNIS/DDI. Be sure operators are aware of the following effects: When accessing a DNIS/DDI line from the Enter Queue, use the branded line name to ●...
Page 86: Branding Calls Using Cbutil
Configuring Channels and Call Routing Note: The System Configuration file (system.txt) includes Digit Parameters. See Print Note: on page 203 for instructions on printing this information. Table 14: Digit Parameters Parameter Description Number of Digits The right-most number (from 1 to 16) of DNIS/DDI digits the system will use to route a call.
Page 87: Accessing Cbutil
Branding Calls using cbutil The last entry in the table consists entirely of wildcard characters. The number of characters in this entry corresponds to the number of DNIS/DDI digits specified in the Digit Parameters configuration. Tip: The last entry in the call brand table always needs to be a wild card entry, ????, Tip: assigned to message number 208.
Page 88: Adding Call Branding Entries
Configuring Channels and Call Routing Adding Call Branding Entries Use the cbutil add command to add a new entry to the Call Branding table. Use this Syntax: add <dnis> [-m <msg> -g <rg> -p <ps> -u <ucps> -f <func> -o <of> -l <ln>...
Page 89 Branding Calls using cbutil Table 16: Call Branding Configuration Parameters (continued) Parameter Description function (-f) This required entry specifies the function the system performs for this call when the incoming digits match an entry in the table. Functions include: ENTER (default) — Place the line in the Enter Queue.This is the most ●...
Page 90 Configuring Channels and Call Routing Table 16: Call Branding Configuration Parameters (continued) Parameter Description l <"ln"> (-l) Optional line name to associate with the caller. The name may contain up to 20 characters. The name may appear in the line name field both on the operator display and in the CDR (see Working with CDRs and CODRs page 263).
Page 91: Modifying Call Branding Entries
Branding Calls using cbutil Modifying Call Branding Entries Use the cbutil update command to update an existing entry in the Call Branding table. update <dnis> [-m <msg> -g <rg> -p <ps> -u <ucps> -f <func> -o <of> -l <ln> -c <cn> -crs <n> -cre <n>] where: where: <dnis>...
Page 92: Displaying A Single Call Branding Entry
Configuring Channels and Call Routing Displaying a single call branding entry Use the cbutil lookup parameter to display a single call branding entry. cbutil lookup <“dnis”> where <dnis> is the DNIS for entry to display. Displaying all call entries in the call brand table To display all of the entries in the call brand table: 1.
Page 93: Setting The Maximum Dnis Length System Configuration
Branding Calls using cbutil Setting the Maximum DNIS Length System Configuration The maximum DNIS length is set during startup in the shared memory database managed by the system. However, you can use cbutil dnissize <number> to set this value. Typically, you will only use this command on a system that is not running the dcbadmin application and, therefore, has not set this value in the shared memory database.
Page 94: Adding Reservation Groups
Configuring Channels and Call Routing Adding Reservation Groups In order to identify a reservation group in the call branding table, you must first add the required Reservation Groups to the server using the following utility: su brdgdbo cd /usr/dcb/dbase/bridgedb ./resgroup_util.sh -a -r 1 Bridge returns the following message: Reservation Group with Ref=1 successfully added! Add each additional reservation group as shown above.
Page 95: Setting Up Flex Call Routing
Setting Up Flex Call Routing Setting Up Flex Call Routing The following section describes how to associate the Flex call routing with DNIS or DDI digits so the system can process Flex-specific dial-in calls. Note: Do not use the same numbers for DNIS Direct and Flex conferee passcodes. Note: DNIS Direct does not support Flex conferences.
Page 96 Configuring Channels and Call Routing 96 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 97: Chapter 4: Managing Annunciator Messages
Chapter 4: Managing Annunciator Messages Describes the annunciator message numbering system, considerations for using annunciators, how to configure tone and voice messages, how to manage annunciator text, and recommendations for optimizing annunciator performance. Introduction Annunciator messages are recorded voice messages installed on the system. Annunciator messages inform conferees about the status of conferences, greet conferees and announce their presence to other conferees, guide conferees through conference actions, and provide other types of circumstantial information.
Page 98: Prompt Sets
Managing Annunciator Messages System Configuration on page 45 includes a description of the On-Hold Frequency ● parameter. This parameter specifies whether or not the system plays a looping “on hold” message to callers on hold and the frequency with which it is played. Copying Voice Files on page 251 provides information about the MLCP utility.
Page 99: Installing Non-Default Prompt Sets
Annunciator Messages Installing non-default prompt sets There is a separate CD for non-default prompt sets. Copy all the prompt sets needed to the bridge. Choose any one of the 21 sets to copy a certain prompt set to. Tip: It is recommended that Set0 and Set1 be used for the default prompt set. Tip: Non-default prompt sets CanadianFrench...
Page 100: Recording Messages
Managing Annunciator Messages Messages are stored in /usr2/Prompts/Set#/messages. ● Numbers are stored in /usr2/Prompts/Set#/numbers. ● The annunciator file name is one less than the annunciator number. Table 17: Flexible Annunciator Messages documents the default message recorded for each annunciator file number and message number.
Page 101: About Annunciator Numbering
Annunciator Messages About Annunciator Numbering The system stores 438 annunciator messages. Each annunciator is associated with a unique file number (0—437). This file number is always one less than message number displayed on the Flexible Annunciator Messages screen. These files have no extension. For example annunciator 2 is stored in a file named, “1”.
Page 102 Managing Annunciator Messages File Message Message Number Number I’m sorry. You have entered an invalid security code. Please try again. I’m sorry. You have entered an invalid security code. Please stay on the line for the next available operator. I’m sorry. You have entered an invalid PIN code. Please try again. I’m sorry.
Page 103 Annunciator Messages File Message Message Number Number Please enter your conference file number followed by the pound key or press star to cancel. Conference recording has stopped. The recording file name is…(digits played here). Press 1 to begin recording, press 2 to re- enter the file number, or press * to cancel.
Page 104 Managing Annunciator Messages File Message Message Number Number This conference has been secured by the moderator and entry is not allowed at this time. Please contact the meeting organizer for additional information. This conference has reached its maximum capacity. Please contact the meeting organizer for additional information.
Page 105 Annunciator Messages File Message Message Number Number The system is unable to recognize the security code that was entered. Please disconnect now, thank you. The system is unable to recognize the PIN code that was entered. Please disconnect now. Thank you. The main conference has been secured and entry is not allowed at this time.
Page 106 Managing Annunciator Messages File Message Message Number Number The following options are available once you press pound to begin dialing. To join the participant to conference, press star 1; to join the participant and continue dialing, press star 2; to disconnect the line, press star 3;...
Page 107 Annunciator Messages File Message Message Number Number Quick Start is off. To turn Quick Start on, press 1. To return to the previous menu, press star. Auto continuation is on. To turn auto continuation off, press 1. To return to the previous menu, press star. Auto continuation is off.
Page 108 Number Number I’m sorry, your entry is invalid. Enter the valid digits followed by pound. Welcome to Avaya’s instant conferencing. Enter your conference code followed by pound. The conference has been locked by the leader. The conference has been unlocked.
Page 109 Annunciator Messages File Message Message Number Number I am sorry, that entry is not valid. Stand by for an operator. (sequence of 4 short beeps). I’m sorry. This feature is not enabled. The following participants are in the conference. <Name> has joined the conference. <Name>...
Page 110 Managing Annunciator Messages File Message Message Number Number I’m sorry, the Leader PIN is invalid. For assistance, please contact your service provider. An operator is requesting to join your locked conference. To allow operator entry, press star 5 to unlock your conference. This is a Quick Start conference.
Page 111 Annunciator Messages File Message Message Number Number This conference has been secured by the moderator and entry is not allowed at this time. Please disconnect now. Thank you. I'm sorry, we did not get your name. After you state your name, please press the pound key.
Page 112 Managing Annunciator Messages File Message Message Number Number …has been locked by the moderator and entry is not allowed at this time. A moderator has been notified of your request. Please stand Note: Message 399 and 402 are played as one sentence. Everyone has been moved back to the main conference.
Page 113 Annunciator Messages File Message Message Number Number Please press any key on your phone to remain in conference. Virtual Link Line. Someone has joined the conference ... Virtual Link Line. Someone has left the conference ... Virtual Link Line. Virtual Link Line has entered the conference. Virtual Link Line has left the conference.
Page 114: Message Assignment Considerations
Managing Annunciator Messages File Message Message Number Number The conference will now be disconnected. Please enter your 'second billing code' followed by the pound key. 14 of 14 Message Assignment Considerations Callers dialing in to an attended conference hear the greeting message once. Those answering a blast are either placed immediately into the conference or hear a repeating message depending on configuration.
Page 115: Managing Annunciator Text
Managing Annunciator Text Message 242 is the default message played to blast-dialed conferees. ● The system always uses message 247 as the PIN code prompt. ● When a conference or line is set to play messages and also sound tones, the following ●...
Page 116 Managing Annunciator Messages Note: Message narrators use Bridge Talk’s Record option to record messages. When a Note: narrator selects the option, it prompts them to enter message text before they record the message. If text already exists for the specified message number, it appears on the command line (and it is editable).
Page 117: About Annunciator Performance
About Annunciator Performance About Annunciator Performance At certain times, an annunciator resource may not be available to play a requested message. This can occur when system use is extremely heavy, when messages are long, or when many lines attempt to enter a conference within a short span of time. When this does occur, the system waits for an available annunciator and then plays the message.
Page 118 Managing Annunciator Messages 118 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 119: Chapter 5: Using The System Management Interface
Working with the Management Interface Chapter 5: Using the System Management Interface Lists how to log in to the system’s management interface, the content and organization of management interface menus and options, and how to work with menus and options. It also describes how to create and manage login accounts (sign-ins) for BridgeTalk users.
Page 120: Menus And Options
CAUTION: The dcbmaint and dcbadmin logins provide read/write access to critical system settings. Avaya recommends that you change the default passwords for the logins to prevent unauthorized users from accessing these settings. Changing default passwords requires root access to the system’s UNIX interface. Contact Avaya Customer Support for assistance.
Page 121 Working with the Management Interface Figure 15: Organization of Maintenance Menus and Screens Issue 1 November 2008...
Page 122: System Maintenance Options
Using the System Management Interface Figure 16: Organization of Administrator Menus and Screens System Maintenance Options System Maintenance Main Menu includes options that enable you to configure advanced system settings, reboot and shut down the system, and access the Administrator Menu. See System Administrator Options on page 123 for information on Administrator Menu settings.
Page 123: System Administrator Options
Working with the Management Interface Table 19: System Maintenance Options Options Tasks Network Configuration Configure, manage, and view various network layer and physical layer network interface settings: Configure network interface parameters — primary, ● secondary, and backup trunk; Layer 1 and signal class parameters;...
Page 124 Using the System Management Interface Table 20: System Administrator Options Option Task(s) Backup Back up various configuration files and reports: System Configuration ● Call Detail Records (CDRs) ● Dial Lists ● Logs ● Sign-ins ● Tag files ● Restore Restore various configuration files and reports: System Configuration ●...
Page 125 Working with the Management Interface Table 20: System Administrator Options (continued) Option Task(s) File Management View, delete, and print various system files: Alarm Report ● CDRs ● CODRs ● Conference Reports ● Dial Lists ● LAN Statistics ● Logs ● Modify Logs ●...
Page 126: Working With Menus And Screens
Using the System Management Interface Working with Menus and Screens Table 21 lists and describes keyboard procedures for navigating through menus and screens, selecting items from menus and screens, changing configuration settings in screens, and saving or canceling changes made to settings. Special keystroke operations not covered in this section are described where required throughout this guide.
Page 127: Managing User Sign-Ins
Managing User Sign-Ins Managing User Sign-Ins A sign-in consists of a login name and a password created for a BridgeTalk user. The privilege level for a sign-in specifies which BridgeTalk resources that sign-in can use and what management interface menus the sign-in can access through BridgeTalk. Users with the higher-level sign-ins can access more resources than sign-ins with lower-level sign-ins.
Page 128 Using the System Management Interface To create sign-ins: 1. Select System Administrator Main > Sign-In Management. The System displays the Sign-In Management menu. The menu varies depending on your login privileges. System Sign-In Management, Maintenance level sign in +---System Sign-In Management----+ ¦...
Page 129: Viewing And Deleting Sign-Ins
Reservation Features Tip: Do not use underscores (_), hyphens (-), spaces, or other special characters in Tip: the sign-in name or password field. Sign-in names and passwords are case-sensitive. For example, lee, Lee, and LEE represent three different sign-in names. You cannot use identical sign-in names, but different sign-in names can have identical passwords.
Page 130: Entry And Exit Announcements
Using the System Management Interface Entry and Exit Announcements The Entry and Exit Announcements may be set to Message, Tone, or Silence. Do not select Tone & Message; this feature does not apply. When you set the Entry/Exit Announcement to Message, enable Music (turn off Quick Start), the system mutes participants entering the conference and plays music to those participants on hold and waiting for a leader to enter the conference.
Page 131 Reservation Features Table 23: Default Settings for Subscription Features (continued) Subscriber-based Feature Default Flex Name Record / Playback (NRP) INDVL. Do not set NRP to CONF; this feature does not apply. PIN Mode Start Date <Blank> Leave blank. End Date <Blank>...
Page 132 Using the System Management Interface 132 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 133: Chapter 6: System Maintenance Options
Chapter 6: System Maintenance Options This chapter describes how to use the System Maintenance menu and several command line utilities to set up the advanced configurations settings for the audio conferencing system. Note: Generally, you will not change the settings discussed in this chapter unless Note: special circumstances require it.
Page 134: Configuring Network Settings
System Maintenance Options System Re-Initialization on page 169 describes how to clear network event and error ● statistics files generated by the system. System Re-Initialization on page 169 describes how to reboot and shut down the system ● from the management interface. Configuring Network Settings The system may be configured to support the following mixed-mode conferences: T1 and T3...
Page 135: Configuring Trunks On T1/E1
Configuring Network Settings When PSTN is not available on the system, for example only T3 networks are supported, the menu looks like this one: Network Configuration Menu, PSTN not installed +---- Network Configuration ----+ ¦ ¦ ¦ T3 Loopback Enable/Disable ¦...
Page 136: Synchronization And Monitoring
System Maintenance Options Tip: After editing any of the Trunk Configuration screens, select the Apply Changes Tip: option to save the changes. Changes will not take effect until you perform a system re-initialization. Synchronization and Monitoring The enables you to specify the primary and backup clocking source, the alarm thresholds for various synchronization failures, and the line-status polling interval.
Page 137 Configuring Network Settings Table 24 lists and describes Synchronization & Monitoring parameters. Table 24: Synchronization & Monitoring Parameters Parameter Description Primary Board Specifies the board through which the primary clocking source is obtained (via the network, internally, or externally). Valid entries include: Board 1 (2, 3, ...6) ●...
Page 138 System Maintenance Options Table 24: Synchronization & Monitoring Parameters (continued) Parameter Description Specifies the number of out-of-frame errors before the system generates an alarm. Errored Seconds Limit Specifies the number of seconds a cyclic redundancy check error exists before the system generates an alarm.
Page 139: Layer 1 Configuration
Configuring Network Settings Layer 1 Configuration The Layer 1 Configuration screen enables you to specify the carrier service (T1, T1CSU, or E1) and the signaling class for each trunk. The following example screens show settings for T1 and E1 configurations. Table 25 lists and describes Layer 1 Configuration parameters.
Page 140 System Maintenance Options Table 25: Layer 1 Configuration Parameters Parameter Description Standard Specifies the carrier rate for the trunk. Framing Specifies the framing type used for the trunk. For T1 and T1CSU: ● Extended Super Frame (ESF) ● Super Frame (SF) ●...
Page 141: Signaling Details And Configuration
Configuring Network Settings Signaling Details and Configuration The Configure Signaling Detail screen enables you to view and specify the attributes associated with the signaling class specified in the Layer 1 Configuration screen. Select System Maintenance Main Menu > Network Configuration > Trunk (T1/E1) Configuration >...
Page 142 System Maintenance Options Table 26: Signaling Details Parameter Parameter Description Wink Time (100-1000 ms) Specifies the length of a valid wink signal for an incoming call. When a trunk is configured for WINK START for incoming calls and it detects the far end has gone off hook, it winks back to the far end by going off hook.
Page 143 Configuring Network Settings Table 26: Signaling Details Parameter (continued) Parameter Description Trunk In-Signaling Specifies how a channel responds to an incoming call: Immediate (default) — The system seizes back ● immediately upon incoming line seizure. Wink — The system winks back to the far end ●...
Page 144 System Maintenance Options Table 26: Signaling Details Parameter (continued) Parameter Description Q.931 Variant Specifies the variations of the Q.931 connection control protocol used on this port. Possible values: (ISDN signal class only) AT&T Custom ● Nortel Custom ● Bellcore ISDN-1 ●...
Page 145: Set Board Count
Configuring Network Settings Considerations for Configuring Trunk-Out Signaling Trunk-out signaling (also referred to as dial out supervision specifies the type of supervisory signaling a channel uses when dialing out. Keep the following in mind when configuring dial out supervision: When dialing out, the system sends a signal to the recipient machine (CO, PBX) to ●...
Page 146: Trunk Status
System Maintenance Options Trunk Status There are three different screens used to view trunk parameters: Status View (default) ● Switches View ● Configuration View. ● Select System Maintenance Main Menu > Network Configuration >Trunk Status to display Trunk Status view. Use function keys to toggle between the three different views: F1 Status View (default) ●...
Page 147: Configuration And Switches Views
Configuring Network Settings Table 27 describes the line codes associated with trunk status. Table 27: Trunk Status Line Codes Code Description In Service Connected line Pre seize (when collecting digits) Seize in (dial in call) Seize out (dial out call) Releasing line Out of Service (Maintenance Alarm) Faulted...
Page 148: Trunk Enable And Disable
System Maintenance Options Trunk Enable and Disable The Trunk Enable/Disable option opens the Maintenance Mode screen, which enables you to take trunks out of service as required. Maintenance Mode +-Maintenance Mode-+ ¦ ¦ ¦ 1: Enable ¦ ¦ 2: Enable ¦...
Page 149: T3 Loopback Enable/Disable
Configuring Network Settings T3 Loopback Enable/Disable On T3 systems you can select Network Configuration > T3 Loopback Enable/Disable to display the T1 on T3 Loopback Mode screen. Use this dialog to place individual T1 into loopback mode. T1 on T3 Loopback Mode +-T1 on T3 Loopback Mode-+ ¦...
Page 150: T3 Trunk Enable
System Maintenance Options T3 Trunk Enable On T3 systems you can select the T3 Trunk Enable option from the Network Configuration menu to display the T3 Maintenance Mode settings Use this screen to enable or disable individual trunks on the t3transport. T3 Maintenance Mode +--T3 Maintenance Mode---+ ¦...
Page 151: Load The Inbound Port Group Configuration
Configuring Network Settings Follow these steps: 1. Select Network Configuration > Load Outbound Port Group Cfg. The system displays a prompt letting you know the status, such as Port Groups Loaded. Port Groups Loaded +------------------------+ ¦ ¦ ¦ Port Groups Loaded ¦...
Page 152: Configuring T3
System Maintenance Options Configuring T3 You can not configure T3 transports using the Maintenance and Administration screens; rather you use a manual process. During this process you create and edit a text file that contains the configurations for the T3 cards. You load this text file in the system with a command line utility that creates the necessary dat file.
Page 153: T3 Configuration Text File
Configuring T3 option generates two files in the current directory (/usr/dcb/bin): -default t3config.txt.default ● t3config.dat.default ● For example: t3config -default Tip: Use t3config -default as the starting point for a new configuration. The Tip: t3config.txt.default file generated contains a Profile section, which specifies None for the SIGTYPEIN and SIGTYPEOUT and the default values for robbed bit signaling.
Page 154 System Maintenance Options Table 28 describes the T3 configuration file’s sections and corresponding parameters. Systems configured for T3 do not currently support ISDN configurations. Table 28: T3config.txt file Settings <Section> Setting Parameter <Profile ID > Each profile section contains the signaling configuration for a trunk.
Page 155 Configuring T3 Table 28: T3config.txt file Settings (continued) <Section> Setting Parameter DIALDELAY Valid settings are 50 — 1000 milliseconds. The default value is 100 ms. DNISDIGITS Defines the number of DTMF digits the system expects to receive during call set-up. These digits include all ANI, DNIS, and delimiters specified by the DNISPATTERN.
Page 156 System Maintenance Options Table 28: T3config.txt file Settings (continued) <Section> Setting Parameter <Calling-Numbers> This section identifies the numbers used to provide the caller-id of the bridge to the far-end for ISDN. The format for the Calling-Numbers entries is: <entry number> <calling number> Where: <entry number>...
Page 157 Configuring T3 Table 28: T3config.txt file Settings (continued) <Section> Setting Parameter CLOCK_DRIVER_SOURCE Valid settings include: Internal ● ● TRUNKn, where n is 1 - 28. ● IP_Address The IP address of the T3 card. TRUNKS <trunk>:<id> TRUNKS=3:3 <starting trunk>-<ending trunk>:<id> TRUNKS=1-2:2 4-28:2 Tip: The <id>...
Page 158 System Maintenance Options t3config.txt, Profile and Call number example <Profile 1> # this is a robbed bit configuration profile. CODING=B8ZS FRAMING=ESF SIGTYPEIN=Wink SIGTYPEOUT=Wink # Robbed Bit Configuration WINKOUT=200 MINWINKIN=100 MAXWINKIN=200 GUARDTIME=200 HOOKFLASHTIME=100 DIALDELAY=100 DNISDIGITS=4 DNISTIMEOUT=4000 DNISPATTERN= ANSWER=YES OUTDIAL=NO CALLROUTING=YES <Profile 2> # this is an ISDN configuration example CODING=B8ZS FRAMING=ESF...
Page 159: T3 Status Utility, T3Stat
Configuring T3 T3config.txt, board configuration example <Board 1> RECEIVE_EQUALIZER=0 LINE_BUILDOUT=0 CHASIS_SLOT=14 CLOCK_SOURCE=Internal CLOCK_DRIVER=C8A CLOCK_DRIVER_SOURCE=Internal IP_ADDRESS=10.221.11.10 TRUNKS=1-2:2 4-28:2 TRUNKS=3:3 CALLING=1-9:1 10-19:2 20-28:3 <Board 2> RECEIVE_EQUALIZER=0 LINE_BUILDOUT=0 CHASIS_SLOT=13 CLOCK_SOURCE=C8A CLOCK_DRIVER=None CLOCK_DRIVER_SOURCE=None IP_ADDRESS=10.221.11.12 TRUNKS=1-28:2 CALLING=1-28:3 <Board 3> RECEIVE_EQUALIZER=0 LINE_BUILDOUT=0 CHASIS_SLOT=12 CLOCK_SOURCE=C8A CLOCK_DRIVER=None CLOCK_DRIVER_SOURCE=None IP_ADDRESS=10.221.11.13 TRUNKS=1-28:2 T3 Status Utility, t3stat...
Page 160 System Maintenance Options T3stat display Board 0 is active | Put ptrs: head 80, tail 80, 0 words queued Get ptrs: head 6327, tail 6327, 0 words queued State: Active T3 Rx Alarms: Green T3 Tx Alarms: Green T2 RX Alrm:1234567 T2 TX Alrm:1234567 R:------- ------- B:-------...
Page 161 Configuring T3 Table 29 describes the fields in the T3stat display. Table 29: t3stat fields Field Description Put ptrs These are the messages sent from the T3 board to the host. The head and tail values are not important. Get ptrs These are the messages sent from the host to the T3 board.
Page 162 System Maintenance Options T3stat - trunk alarm states T1 RX Alrm:1234567890123456789012345678 T1 TX Alrm:1234567890123456789012345678 R:---------------------------- ---------------------------- B:---------------------------- ---------------------------- Y:---------------------------- ---------------------------- OOF:---------------------------- ---------------------------- LOS:---------------------------- ---------------------------- States:AAAAAAAAAAAAAAAAAAAAAAAAAAAA N-NtCnfgrd A-Actv O-OOS U-Unknwn Chan Stats:1234567890123456789012345678 1234567890123456789012345678 ---------------------------- ---------------------------- 01|____________________________ 13|____________________________ 02|____________________________ 14|____________________________ 03|____________________________ 15|____________________________ 04|____________________________ 16|____________________________ 05|____________________________...
Page 163: Configuring The Fdapi
170 of the system’s digital phone channels as auxiliary channels to support music (digital or analog source), analog conference recording and playback, dedicated links to other CS700/CS780 Conferencing Servers, and dedicated operator audio paths. Channels configured for FDAPI functions channels are not available as revenue channels.
Page 164: Specifying Flex-Dapi Channels
System Maintenance Options Specifying Flex-DAPI Channels To specify the number of FDAPI channels to use for auxiliary functions: 1. Select System Maintenance Main > FDAPI Configuration. The system displays the Flex-DAPI configuration screen which corresponds to the transport protocols installed on the system. T1/E1 Flex-DAPI Configuration +-Flex-DAPI Configuration-+ ¦...
Page 165 Default Range Operators / Operator voice channels — For operator 0 — 70 audio paths, the number of operator audio paths lines. Avaya Operator Audio Paths on page 73 for information recommends on configuring operator audio paths over non-FDAPI not exceeding channels.
Page 166: About Configuring Link Channels
System Maintenance Options About Configuring Link Channels An FDAPI Link channel supports a dedicated telecommunication path to a Link channel on another system to integrate a conference hosted by one system with a conference on another. Unlike a Virtual Link Line (VLL) connection between two systems, which is established across revenue channels (conferee channels), Link channels are not available as revenue channels.
Page 167: Configuring The System Hosts File
Configuring the System Hosts File Configuring the System Hosts File The LAN Configuration option enables you to view, add, modify, and delete hostname entries in the system’s hosts file. To access the LAN Configuration menu: 1. Select System Maintenance Main > LAN Configuration. The system displays the LAN Configuration menu.
Page 168: Adjusting The Channel Transmission Level
1.1 91/02/28 16:30:32 ccs Exp $" # Internet host table 127.0.0.1 localhost 192.168.12.25 sqa25.avaya.com sqa25 192.168.12.14 releng-sco711.avaya.com releng-sco711 CAUTION: Do not delete or modify the localhost entry in the hosts file. CAUTION: 3. Follow system prompts to save (or cancel) any changes you have made to the hosts file.
Page 169: System Re-Initialization
System Re-Initialization To adjust the transmission volume level: 1. Select System Maintenance Main > Transmission Level. The system displays the Transmission Level Screen screen. Transmission Level Screen +- Transmission Level , Current Setting = unity -+ ¦ ¦ ¦ -8.0 dB -2.0 dB ¦...
Page 170 System Maintenance Options CAUTION: Re-initialize terminates all conferences. Do not re-initialize an active system CAUTION: unless absolutely necessary. CAUTION: Ensure that the 3.5 disk drive is empty before you re-initialize the system so the CAUTION: system does not attempt to boot from the floppy in the disk drive. To re-initialize the system: 1.
Page 171: System Shutdown
System Shutdown System Shutdown A system shutdown terminates system processes. To shut down the system: 1. Select System Maintenance Main > System Shutdown. The system displays the System Shut Down prompt. System Shut Down +-------System Shut Down--------+ ¦ ¦ ¦ ARE YOU SURE? (yes/NO): ¦...
Page 172 System Maintenance Options 172 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 173: Chapter 7: Configuring Conference Scheduler
Except for the External Passcode Validation features, all unattended services described in this chapter are standard features. Contact your Avaya representative for more information on optional features. This chapter is organized as follows: Working with the Conference Scheduler on page 173 describes how to configure the ●...
Page 174 Configuring Conference Scheduler To configure the Schedule: 1. Select System Administrator Main > Configure Scheduler. The system displays the Configure Conference Scheduler Screen. Configure Conference Scheduler Screen +-------Configure Conference Scheduler--------+ ¦ ¦ ¦ Group Name : schedule ¦ ¦ Status : ENABLED ¦...
Page 175 Working with the Conference Scheduler 2. Set the required parameter values. Table 32 lists and describes the scheduler configuration parameters. 3. Save (or cancel) your changes. Table 32: Conference Scheduler Configuration Parameters Parameter Description Group Name This is a non-editable field with the value Schedule. Status Specifies whether or not the Conference Scheduler is used.
Page 176 Configuring Conference Scheduler Table 32: Conference Scheduler Configuration Parameters (continued) Parameter Description Conference Specifies the system response to callers entering valid codes Secured for conferences that have been secured by a moderator (no one, including operators, can enter, monitor, or record a conference).
Page 177 Working with the Conference Scheduler Table 32: Conference Scheduler Configuration Parameters (continued) Parameter Description Specifies whether or not the system disconnects all lines Auto Hang-up when the conference duration Enabled — The system disconnects all lines when a ● conference duration expires. All lines become immediately available, a feature especially important on a fully unattended system.
Page 178 Configuring Conference Scheduler Table 32: Conference Scheduler Configuration Parameters (continued) Parameter Description Automatic Specifies whether or not the system automatically assigns Security security codes to conferences. Codes The number of digits for the code, between 7 and 16 — ● The system automatically assigns both conferee and moderator passcodes to a conference when it is created.
Page 179 Working with the Conference Scheduler Table 32: Conference Scheduler Configuration Parameters (continued) Parameter Description On-Demand Specifies the percentage of the system lines available for Pct (%) On-Demand conferences, which are unattended conferences that can be convened on an ad hoc, first-come, first-served (Scheduler basis.
Page 180: Configuring Warning Tones
Configuring Conference Scheduler Table 32: Conference Scheduler Configuration Parameters (continued) Parameter Description Flex Leader Select one of the following conference-wide settings: Pin Modify Enabled (Default)—The moderator (leader) can modify ● (Flex only) a Leader PIN by pressing 2 on a telephone keypad to access the Default Conference Options menu before the conference starts.
Page 181: Using External Passcode Validation
Using External Passcode Validation 10 minutes ● 5 minutes ● 4, 3, 2, 1 minutes until the conference ends ● To configure the frequency with which warning tones are sounded: 1. Select System Administrator Main > Configuration > Warning Tone Configuration. The system displays the Warning Tone Configuration.
Page 182: Validation Process
Configuring Conference Scheduler When EPV is enabled, the system uses HTTP to send requests the external passcode server, where passcodes are stored and validated The external server communicates directly back to the bridge by sending an XML document that conforms to the Document Type Definition, (epv.dtd).
Page 183: Xml Data Source Configuration
Using External Passcode Validation Note: Although the Schedule can remain activated and enabled on the system, the Note: Conference Scheduler, which is accessed from the Bridge Talk application, is disabled when EPV is enabled on the system. All conference scheduling for an EPV-enabled system is supported by the external reservation server.
Page 184: Validation Requests
Configuring Conference Scheduler Table 33: chdbased.reg Attribute Settings (continued) Attribute Description The Universally Recognized Identifier is used for passcode validation requests. Entries in this field are limited to 127 characters. The URI points to either an HTML page for a production system, or to a directory on the HTTP server for a test environment.
Page 185: Http Get Syntax
Using External Passcode Validation Each passcode and PIN code validation request is sent to the EPV server using the HTTP GET command. The passcode, and several other parameters, are sent in the GET request as arguments in the URI. Table 34 describes information sent to the EPV server.
Page 186: Test Syntax
Configuring Conference Scheduler For example: GET / epvtest?pc=97979&v=1.0&bn=spectel700&pt=1&an=6354&dn=6200&ct=9999 HTTP/1.0 Host: webmaster7 Where: This argument: Is set to this value: This argument: Is set to this value: Address webmaster7 /epvtest 6354 97979 6200 9999 spectel700 Tip: Refer to rfc2616 for a complete description of the HTTP Request. All internet Tip: Request For Comments documents (i.e.
Page 187 Using External Passcode Validation The following sample is a valid XML response which uses epv.dtd: Example XML response using the epv.dtd <?xml version="1.0"?> <!DOCTYPE spectel PUBLIC "-//Avaya Inc//DTD for Avaya Conferencing Systems//EN" "spectel.dtd"> <!-- Sample vFlow conference passcode:701 Leader PIN:777 MUSIC=on...
Page 188 <leaderPinStatus>0</leaderPinStatus> <lpMin>3</lpMin> <lpMax>7</lpMax> The CS700/CS780 Conferencing Server can send commands to the EPV server to update conference schedule data. The cmdURI parameter in the xmldatasource section of the /usr/dcb/ dbase/admin/chdbased.reg file defines the URI where EPV commands are sent. 188 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 189: Billing Code Values
Using External Passcode Validation To construct EPV commands, you append the cmdtok parameter to an http request sent to the URI defined by cmdURI. This parameter identifies which command the system is requesting. The cmdtok parameter is followed by a set of command-specific parameters. Currently, the only supported command updates the Leader PIN in a Flex conference.
Page 190: Mandatory Billing Codes For Systems Configured With Flex
Configuring Conference Scheduler Mandatory billing codes for systems configured with Flex The system can prompt the leader to provide a billing code for their conference when entering a Flex flow conference. To make the billing code mandatory, set the following parameter: <forceAuxCode>=1 (Set this field to 0 to not require the billing code) If this field is set to 1, the leader will be disconnected if he fails to enter the billing code after three attempts.
Page 191: Keep Alive Response
Using External Passcode Validation Keep Alive Response The following sample Keep Alive response conforms to the epvd.dtd. <spectel> <spectelSys700> <pingResponse> <ping>ALIVE</ping> </pingResponse> </spectelSys700> </spectel> The xCalcli Test Program The xCal Client sample application, xCalcli resides in /usr/dcb/bin after a successful installation. xCalcli uses the same libraries that EPV uses to make requests and receive data from an external passcode validation server.
Page 192: Validating Pin Codes Via A Web Browser
Configuring Conference Scheduler 2. Cmd> <menu option> Menu options are described in Table Table 36: xCalci Menu Options Menu Option Description Validate passcode. When you select 'v', the xcalcli prompts you to enter a passcode, ANI, DNIS, and LCN (i.e. port). Enter a value and press return for each prompt.
Page 193 Using External Passcode Validation Table 37: Web PIN Code query Element Definition 5555 The user entered PIN 123456789 The conference reservation’s <pinlistName> field. Retrieved when the conference is started in the EPV server’s passcode reply conf_br_003 Configured in chdbased.reg as the bridgeid The following is an example of a reply for a valid PIN: <?xml version="1.0?>...
Page 194 Configuring Conference Scheduler 194 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 195: Chapter 8: Managing Files
Introduction Chapter 8: Managing Files This chapter describes how to work with system files using the file-management tools available from the management interface. It also describes procedures for managing files from the UnixWare command line interface. Introduction The system generates files and reports that include conference, system event, system configuration, and statistical data.
Page 196: About System Files
Managing Files management, and examples that show how TCP/IP utilities are used to work with files. Also discussed in this section is configuration of the system for SSH. Additional Information About File Transfers on page 249 discusses filename issues related ●...
Page 197: System File Summary
About System Files System File Summary The system generates some files automatically; others are generated in response to user actions. Table 38 summarizes the file features. Table 38: System File Summary File type Generation Filename Extensio Example Retention Period Saved Roster Auto Cross ref.
Page 198: System File Locations
Managing Files System File Locations The following table describes the various files stored by the system and the directory where each is located. This table excludes PIN codes, PIN lists, and voice files (see Copying Voice Files on page 251). Table 39: System Data File Names and Locations Directory Description...
Page 199: Working With The File Management Menu
Working with the File Management Menu Table 39: System Data File Names and Locations (continued) Directory Description File Format: Name Permission CDR/CODR export Binary: cdrstyle.dat Read/Write configuration ASCII: cdrstyle.txt Read/Write Channel configuration Binary: channel.dat Read/Write ASCII: channel.txt Read/Write Operator configuration Binary: operator.dat Read/Write ASCII: operator.txt...
Page 200: File Management Capabilities
Managing Files To open the File Management Menu: 1. Select System Maintenance Main > Administrator Menu > File Management to display File Management Menu menu. File Management Menu +--File Management---+ ¦ ¦ ¦ Delete ¦ ¦ Print ¦ ¦ View ¦...
Page 201: Working With File Lists
Working with the File Management Menu Table 40: File Management Capabilities (continued) File Type Delete Print View Configurations Dial List LAN Statistics Logs Modify Log Operator Printouts Operator Transaction Logs Polling Results Record/Playback Tag File Traffic Statistics 2 of 2 Working with File Lists This section includes a few guidelines on working with the file lists displayed when you invoke any of the File Management menu options discussed in this chapter.
Page 202: Delete
Managing Files Delete Files are deleted from the system in one of three ways: 1. The system automatically deletes active files older than 30 days. 2. You can use the File Management Menu’s Delete option to manually delete files. 3. You can manually delete files by logging into the dcbguest account to directly access the files (see Using the Guest Account on page 232).
Page 203: Print
Working with the File Management Menu Figure 20: Recorded File List 3. Select and delete the required files. 4. Save (or cancel) your changes. Print Use the File Management Menu’s Print option to print dial lists, logs, reports, and the following configuration files: cdrstyle.txt (call detail record style) ●...
Page 204 Managing Files To print files: 1. Select Administrator Menu > File Management > Print. Print File menu lists the different file types. Print File menu +-------Print File-------+ ¦ ¦ ¦ Alarm Report ¦ ¦ CDRs ¦ ¦ CODRs ¦ ¦ Conference Reports ¦...
Page 205: View
Working with the File Management Menu View Use the View option to view dial lists, logs, reports, and configuration files. To view files: 1. Select Administrator Menu > File Management > View. The system displays View File. View File +---------------------View File----------------------+ ¦...
Page 206: Hard Disk Status
2. Press any key to return to the File Management menu. Working with the Printer Management Menu The default configuration for the CS700/780 sends output to the local printer (the default printer for the workstation from which you invoke a print job). See...
Page 207: Cancel Print Jobs
Working with the Printer Management Menu To access the Printer Management menu: 1. Select Administrator Menu > Printer Management. The system displays Printer Management. Printer Management +----Printer Management----+ ¦ ¦ ¦ Cancel Print Jobs ¦ ¦ Display Printer Status ¦ ¦...
Page 208: Disabling Print Jobs
Managing Files Figure 21: Printer Status Screen Disabling Print Jobs The Disable Printer option lets you disable the system from sending print jobs to the system printer. When the system printer is disabled and you choose the system printer option when you print system files, the print job fails.
Page 209: Back Up Files
Working with the Backup/Restore Menu Table 41: Backup/Restore Options File Type Backup Restore System Configuration Call Detail Record (CDR) Dial List Sign-in Note: If you prefer, you can use any of the TCP/IP utilities and UNIX commands Note: described in Managing System Files from a Remote Host on page 232 to directly access system directories and files in order to perform backup operations.
Page 210: Restore Files
Managing Files To backup files: 1. Select Administrator Menu > Backup/Restore > Backup. The system displays the Backup menu. Backup +---------Backup---------+ ¦ ¦ ¦ System Configuration ¦ ¦ CDRS ¦ ¦ Dial Lists ¦ ¦ Logs ¦ ¦ Sign-Ins ¦ ¦...
Page 211: Configuration Files
Configuration Files Saved Roster Audio Files are saved to the /usr3/savedroster directory. The system assigns the Cross Ref number for a conference as the filename for the each saved roster file. See Configuring CODRs on page 276 for information on the Cross Ref number. The raw audio file does not include an extension (for example, 000225456037), but is saved in pcm format.
Page 212: Dial Lists
Managing Files Table 42: System Configuration Files (continued) File Name Contents system.txt System, system supervision, blast dial, call routing, FDAPI, voice message, warning tone configuration settings, and which optional features are installed on the system. unattend.txt Active code group (typically Schedule) configuration settings. 2 of 2 Dial Lists Dial list files include system dial lists created and used by operators for blastdial and fastdial...
Page 213: Lan Statistics Report
LAN Statistics Report LAN Statistics Report The LAN Statistics report includes IP, ICMP, IGMP, TCP, and UDP data derived from the system’s LAN interfaces. For information on viewing LAN Statistics files and other files, see View on page 205. You can directly access LAN Statistics Report files from the /usr/dcb/lanstats directory.
Page 214: System Log
Managing Files System Log ● Modify Log ● External Passcode Validation Log ● Operator Transaction Logs ● For information on printing log and other files, see Print on page 203. For information on viewing log and other files, see View on page 205.
Page 215: User Transaction Log
Log Files You can directly access daily log files from the /usr/dcb/logs directory or you can view them by selecting: Administration > File Management > View File > Logs. Sample Log File Screen UnixWare_sqa25 2006-04-01 23:57:05 0000.0100 REPT AUTO /* 0n0100ain.c 1464 Information <==init main.c 1464 B SYSTEM RESTARTED ================>*/ <================ DCB SYSTEM RESTARTED ================>*/ UnixWare_sqa25 2006-04-01 23:58:25...
Page 216: Configuration
Managing Files Note: If local logging obstructs normal bridge operation, then remote logging is needed. Note: The following events are logged using the Unix syslog facility: Calls ANI/DNIS ● All DTMF entered ● Channels moving to user conferences ● Announcement segments played to a user ●...
Page 217 Log Files 3. Restart syslogd to activate the new settings. Use one of these methods: a. Type, to report syslog’s pid. "ps -e | grep syslog" b. Type, <pid of syslog>" "kill -l —or— Restart the server. ● User Transaction Log Format The message format used by the syslog to display information is: <date>...
Page 218: Modify Log
Managing Files System log containing User Transaction information for a system configured for Flex Mar 13 09:24:23 bell syslog: chan:360 Connect with ANI/DNIS:/6458 Mar 13 09:24:23 bell syslog: chan:360 play segment:331 Mar 13 09:24:33 bell syslog: chan:360 dtmf:6 Mar 13 09:24:33 bell syslog: chan:360 dtmf:3 Mar 13 09:24:34 bell syslog: chan:360 dtmf:2 Mar 13 09:24:34 bell syslog: chan:360 dtmf:2 Mar 13 09:24:34 bell syslog: chan:360 dtmf:6...
Page 219: External Passcode Validation Log
Log Files In the Example Modify Log File the first entry indicates a conference modification, while the second entry shows an additional modification. First, the code duration was increased to 75 minutes; later, the end time was extended to 5:00 PM. The “start time” shown for modified records represents the time the modification was made.
Page 220: Operator Transaction Logs
Managing Files Operator Transaction Logs When the Transaction Logs parameter is enabled (see System Configuration on page 45), the system keeps a log of the commands an operator executes while working with BridgeTalk. Each entry in the operator transaction log file includes the time the entry is logged, operator station number, operator sign-in name, command the operator performed that is being logged, and any additional information specific to the action being logged.
Page 221: Specifying Filtering For A Operator Transaction View
Operator Transaction Logs Figure 24: Operator Transactions List Screen Specifying Filtering for a Operator Transaction View The Log Selection screen (Figure 23) lets you to specify the information you want to view from a transaction log. You can specify whether you want to view operator transactions for a single day, all days in a month, or all days for all months.
Page 222: Operator Commands
Managing Files Table 43: Operator Transaction Filters (continued) Parameter Setting Sign-in Enter the sign-in name of the operator for which you want to see transactions. Command All (default) — Display a list of all the commands that ● are logged in the transaction log on the lower part of the screen.
Page 223 Operator Transaction Logs Table 44: Logged Operator Transactions (continued) Command Parameters Access/User_Selected Linenum Conference/AUX1 Confnum; aux1 Conference/AUX2 Confnum; aux2 Conference/ClearAll Conference Conference/EntryTone Confnum; entry tone = On/Off Conference/ExitTone Confnum; exit tone = On/Off Conference/Gain Confnum; gain = On/Off Conference/Hangup Confnum Conference/ID Confnum;...
Page 224 Managing Files Table 44: Logged Operator Transactions (continued) Command Parameters Conference/Promptset confnum;promptset Conference/QA/Clear Confnum Conference/QA/ Confnum; linenum Close_Mute_Line Conference/QA/Exit Confnum Conference/QA/Open_Line Confnum; linenum Conference/QA/Recall Confnum; linenum Conference/QA/Resume Confnum; linenum Conference/QA/Start Confnum Conference/QA/Stop Confnum Conference/QA/Access_Help time operator_number operator_name CONFERENCE/QA/ACCESS_MOD confnum;linenum Conference/QA/ time operator_number operator_name Release_Help CONFERENCE/QA/RELEASE_MOD;...
Page 225 Operator Transaction Logs Table 44: Logged Operator Transactions (continued) Command Parameters Line/Aux1 Linenum; aux 1 Line/Aux2 Linenum; aux 2 Line/Aux3 Linenum; aux 3 Line/CallType Linenum; call type Line/CompanyName Linenum; company Line/Fault Linenum; mode = TRUE/FALSE Line/Hangup Linenum Line/Moderator Linenum; moderator = TRUE/FALSE Line/Mute Line/Mute linenumb = ;selfMute = TRUE/ FALSE;...
Page 226 Managing Files Table 44: Logged Operator Transactions (continued) Command Parameters Options/Chat Destopernum; text Options/Listen/Line/HangUp Linenum Options/Listen/Line/Mute Line/Mute linenumb = ;selfMute = TRUE/ FALSE; operMute = TRUE/FALSE Options/Listen/Line/Release Linenum Options/Listen/Line/Start Linenum Purge/Call_Counts Linenum = all Purge/Disconnects Confnum Purge/Disconnects/All Confnum = all Purge/Mins_Per_Conference Confnum Purge/Total_Line_Times...
Page 227: Digital Record/Playback (Drp) Files
Digital Record/Playback (DRP) Files Table 44: Logged Operator Transactions (continued) Command Parameters Scheduler/Conference/ ConfirmNum Remove Scheduler/Conference/ ConfirmNumIn; confirmNumOut Setspecial Scheduler/Debug Debug Scheduler/Timer TimerA; timerB; timerC Set/ACS Confnum; linenum Set/Answer Linenum; answer = ON/OFF Set/Night_Time NightTime = TRUE/FALSE Set/Scan_Time Oldscantime; newscantime 6 of 6 Digital Record/Playback (DRP) Files The Digital Record/Playback feature enables conference operators and moderators to digitally...
Page 228: Drp Information In Codrs And Conference Reports
Managing Files Figure 25: Record/Playback Files Screen DRP Information in CODRs and Conference Reports The Record (REC) and Playback (PBK) fields in Conference Reports and CODRs differentiate between digital and analog record/playback features with the following codes: OFF — Feature not applied ●...
Page 229: Converting Drp Files To Wav Files
Digital Record/Playback (DRP) Files Digital Playback conference report shows a Conference Report for a digital playback conference. Digital Playback conference report Date: Aug 11, 2001 Bridge: Boston Conference ID: 000000001238 Conference Name: Subatom Contact Name: Contact Tel. : Start Time: 08:59:11 Duration: Total Conf.
Page 230 Managing Files 3. Run the soundcvt utility to convert the selected DRP file to a .wav file. You can rename the .wav file (the converted file) during the conversion. The conversion can take minutes to hours, depending on the size of the DRP file. $ /usr/dcb/bin/./soundcvt -U <DRP filename>...
Page 231: Traffic Statistics
Traffic Statistics Traffic Statistics Traffic Statistics files contain information about overall system usage, letting you view system activity and compare channels scheduled with the actual channels in use. The system generates statistics each day and updates the file every 15 minutes, listing minimum, maximum, and average counts for the following categories: System Capacity —...
Page 232: Managing System Files From A Remote Host
Managing Files Traffic Statistics Report shows an example report. Traffic Statistics Report Date: Feb 26 188 Channels Installed System Channels Channels In Channels In Total Time Capacity Scheduled Scheduled Conf Use - Total Utilization Min/Max/Avg Min/Max/Avg Min/Max/Avg Min/Max/Avg Min/Max/Avg% ------------------------------------------------------------------------------ 00:00 11/ 11/ 11 00:15...
Page 233: Unix Commands Summary
Managing System Files from a Remote Host The account login name and default password are: Login: dcbguest Password: abc123 You can change the default Guest account password using the passwd command described in Table 45. Passwords must be at least six characters long with a minimum of two alphabetic characters and one numeric or special character.
Page 234: Remote Login And File Transfer
Managing Files Table 45: UNIX Command Subset (continued) Command Syntax Description Change login password. passwd prompts for the old passwd password and then the new password. If accepted, you must re-enter the new password before system sets it. Must be run by root. View contents of text file(s).
Page 235: Using Rlogin
8-bit character set such as the Asian or European character sets. [- l login] login is the name of the CS700/CS780 Conferencing Server account to which you want to log in. (The current login name on your system is assumed if this option is waived.) Note: Your remote host’s software may vary.
Page 236: Using Telnet
Managing Files Logging in using rlogin: 1. Log into the 1100_a guest directory from your remote host. $ rlogin s1100_a -l dcbguest The system displays the password prompt. If your host is listed in the system’s .rhosts file, this step is unnecessary. 2.
Page 237: Using Rcp
Managing System Files from a Remote Host Note: Your remote host’s software may vary. Consult the TCP/IP documentation for Note: command support, setup, and usage. Example: Logging into an 1100_a using telnet. 1. Log into the s1100_a guest directory from your remote host. $ telnet s1100_a The system displays a login prompt.
Page 238: Using Ftp
Managing Files Copy to directory. directory Preserves the last access time, last modification time, and [-p] access mode of the file being transferred. Causes a recursive copy of any subdirectory whose root appears [-r] in the list of files. When you use this form of the rcp command, the source can be either a file or a directory, but the destination must be a directory.
Page 239 Managing System Files from a Remote Host To use ftp, add the system’s name and IP address to the hosts file of your remote host(s). Consult the documentation of your TCP/IP software for proper setup. The ftp command uses the following syntax (bracketed arguments are optional): ftp [-d] [-g] [-i] [-n] [-t] [-v] [host [port]] Where Enables debugging.
Page 240 Managing Files 4. Enter a password by typing abc123 The system displays the message: 230 User dcbguest logged in. Remote system type is UNIX. Using binary mode to transfer files. 5. At the ftp> prompt, change to the directory containing the files to be transferred by typing: cd /usr/dcb/dbase/admin The system displays the message: 230 User dcbguest logged in.
Page 241: Ssh
SSH provides secure connections to perform remote system administration on the system from BridgeTalk. Administrators install and configure SSH on both the conferencing server and on BridgeTalk. This section documents the procedures required on the CS700/780. Refer to Meeting Exchange 5.1 Bridge Talk User’s Guide to configure that application.
Page 242: Installing Zlib
Managing Files Note: Zlib, OpenSSL, and OpenSSh are third party products not licensed by, or Note: distributed through, Avaya, Inc. SSH installation is a sequential, three-part process: 1. Installing zlib version 1.2.1 2. Installing OpenSSL version 0.96 or later 3. Installing SSH version 3.7p1 The following sections, document this three-part process.
Page 243: Installing Openssl
Managing System Files from a Remote Host Installing OpenSSL OpenSSL is a cryptography toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) network protocols and related cryptography standards required by them. The openssl program is a command line tool for using the various cryptography functions of OpenSSL's crypto library from the shell.
Page 244 Managing Files Follow this procedure to install SSH on the BridgeTalk workstation. Table 48: Installing SSH on the BridgeTalk Workstation Step Description Log into the system as root. login: root Start the Account Manager to create an scoadmin Account Manager sshd account.
Page 245: Environment Variables
Managing System Files from a Remote Host Tip: You can set up SSH so that it starts automatically when the system starts. Create Tip: a file named S99ssh in /etc/rc2.d: The file must contain the following lines: #!/bin/sh # Start/Stop SSH SSHD=/usr/local/sbin/sshd SSHDPID=/usr/local/etc/sshd.pid #set -vx...
Page 246 Managing Files 1. Enter the command: ssh-keygen -t [rsa | dsa] This command generates a public/private rsa key pair. The system displays these prompts: Enter a file in which to save the key: (/home/username/.ssh/id_rsa) Enter passphrase: (leave blank for no passphrase) Enter the same passphrase again: Your identification has been saved in /home/username/.ssh/id_rsa.
Page 247: Configuration
Managing System Files from a Remote Host Configuration Dcbmaint and dcbadmin accounts each require an .ssh directory in their home directories. SSH will not function if the ownership and permissions of the .ssh directory are not correct. Administrators need to perform the following procedure to configure SSH on the system: Table 49: Commands to configure SSH on the system Step Description...
Page 248: Improving System Security
Managing Files Table 49: Commands to configure SSH on the system (continued) Step Description Verify that you are in the correct directory. Creates the new .ssh directory. mkdir .ssh Changes ownership of the directory to chown dcbdcbmaint .ssh dcbmaint. Changes group ownership to the dcb chgrp dcb .ssh group.
Page 249: Additional Information About File Transfers
Additional Information About File Transfers When you run dcbsyssecurity.sh, the system displays this menu: 1) High Security With SSH. Disable all the unsecured Unix services* but leave sshd running. 2) High Security Without SSH. Disable all the unsecured Unix services* and sshd 3) Enable/Disable Individual Services.
Page 250: Creating Files Off-Line For Downloading
Managing Files If your ftp package forces file names to upper-case, do not use ftp for transferring configuration files (files residing in /usr/dcb/dbase/admin) to the system. Creating Files Off-line for Downloading You can create selected files off-line and download them to the system using ftp or rcp. Applicable file types are tag files and dial lists.
Page 251: Copying Voice Files
Additional Information About File Transfers 2. All subsequent lines contain the participant name, company name, and telephone number. Table 50: Dial List records Field Description Participant Name Optional Participant Name, up to 20 characters. May start with one of these special characters: to indicate moderator to indicate Q&A Top Priority to indicate Exclude from Q*A...
Page 252: About Mlcp
Managing Files LAN users have read-only access to voice directories. However, the mlcp utility provides a mechanism for copying voice files from one system to another. After using rcp or ftp to copy files to designated download directories, you can run mlcp, which automatically performs data checks and moves the files to the appropriate voice directories.
Page 253: Starting Mlcp
Additional Information About File Transfers mclp performs these verifications when copying files: Disk space — The system displays an error message if insufficient space is available in ● the target directory. Verification before overwriting — When the system encounters an existing file (same ●...
Page 254: Managing The Pin Code Files
2. Copy the files onto the system 3. Load PIN codes into the bridgedb. 4. Unload PIN information from the bridgedb. Refer to the CS700/780 Relational Database Guide for detailed information on batch loading data into the bridge database. Creating PIN Code Files The batch load script used to load PIN data into bridgedb requires two files: 1.
Page 255: Pre-33 Pin Code File Format
Char(16), required, unique 970824356 line name Char (20), optional Eve Adams company name Char (20), optional Avaya telephone number Char (40), optional 18885550999 Note: Optional fields must contain a space to separate the field delimiters. For example: Note: 8975| | |654-555-9436| Files containing duplicate PIN codes cannot be loaded onto the system.
Page 256: Pre-33 Pin List File Format
Managing Files Pre-33 PIN List file format The first line of the pinlist.txt file contains two fields delimited by pipes (|). The first field contains the name of a PIN list and the second field contains an exclamation point (!) followed by a For example: ETURN listname|!|...
Page 257: Pin Code File Format
Managing the PIN Code Files PIN Code File Format The pins.txt file format is defined in Table 53. Unlike the pre-33 file, this format does not require a first row identifying the fields. All lines of the file contain data. For example ||||ACBRIDGE Test1|AnyCo, Inc.|||||99999999901|197865551212|||LineAux1Info|LineAux2Info|LineAux3Info|107712 3541|PINRaw Batch Load|||...
Page 258: Pin List File Format
Managing Files Table 53: PINs.txt File Format (continued) Field Type Required InsertTimet Integer in seconds since midnight, 1 Jan 1970 in InsertLogin Char(30) UpdateTimet Integer in seconds since midnight, 1 Jan 1970 in UpdateLogin Char(30) 2 of 2 PIN List File Format The fields required for the pinlist.txt file format are documented in Table Table 54: PINList.txt File Format...
Page 259: Copying The Files To The System
Loading PIN Codes and PIN Lists to into Bridgedb Copying the files to the system This section describes how to copy the files from your PC or workstation to the system. To copy PIN code files to the system: 1. Navigate to the directory on your system where the PIN code files are stored. cd /usr/dcb/dbase/bridgedb/batchdata/ 2.
Page 260 Managing Files Note: Chapter 2 Maintenance on the Relational Database Guide, includes Note: recommendations and options for batch loading data. Follow this procedure to load pin codes into the database: 1. Log on to the bridge with the brdgdbo account: login: brdgdbo Password:******* 2.
Page 261: Unloading Pin Codes
Loading PIN Codes and PIN Lists to into Bridgedb 5. Type “a” to append records to the existing pin list. The system displays this prompt: Enter full path and file name where the pin code file to be batch loaded can be found [/usr/dcb/dbase/bridgedb/batchdata/pins.txt]: 6.
Page 262 Managing Files 3. Press Enter to accept the default. If the file exists, then the system displays this prompt: The file '/usr/dcb/dbase/bridgedb/batchdata/pins.txt' already exists, overwrite?. Enter 'y' to continue [n]: 4. Type “y” and press NTER The system displays this prompt: Enter full path and file name where the pin list data will be unloaded to [/usr/ dcb/dbase/bridgedb/batchdata/pinlist.txt]: 5.
Page 263: Chapter 9: Managing Reports
Chapter 9: Managing Reports Describes how to configure, manage, view and print system reports. The system generates various reports that include conference, system event, system configuration, and LAN statistical data. You can view, print, and backup and restore system files using the system’s management interface tools.
Page 264: How The System Manages Detail Records
The system offers two methods for saving CDR and CODR files—text files or a relational database. For additional information on using the relational database method for detail records, refer to the CS700/CS780 Conferencing Server Relational Database Guide. The remainder of this chapter will discuss using text files to manage detail records.
Page 265 Working with CDRs and CODRs Figure 26: Order of CDR and CODR Data Fields When you configure CDRs and CODRs for printing or viewing from the system’s management interface, you can specify the data fields you want included in each of four output styles (or formats).
Page 266: Configuring Cdrs
Managing Reports You can modify all style names except for the Auto (CDR or CODR) style name. This enables you to assign style names that indicate the types of data fields included (or excluded) from a style (e.g., Company Names) or a style’s purpose (e.g., Billing Data). The default names, Short Format, Long Format, and Custom Format do not indicate the scope of data that can or should be included in an output style —...
Page 267 Working with CDRs and CODRs To configure CDRs: 1. Select Administrator Menu> Configurations > CDR Configuration. The system displays CODR Configuration, screen 1. There are four configuration screens, each with editable fields for each CDR style. See Table 55 for configuration/output field specifications.
Page 268 Managing Reports CDR Configuration, screen 3 +-----------------------------CDR Configuration------------------------------+ ¦ ¦ ¦ FIELD(size) STYLE 1 STYLE 2 STYLE 3 AUTO CDR ¦ ¦ ¦ ¦ Calling Phone(40) ¦ ¦ Cross Ref (12) ¦ ¦ User Conf Type (4) ¦ ¦ Seize Date (8) ¦...
Page 269 Working with CDRs and CODRs Table 55: CDR Field Specifications Field Size Options Description Output Example Style Name Up to 15 Name of a CDR output style. The characters system stores four different CDR styles. You can rename all styles (no more than 15 characters) except the Auto CDR style.
Page 270 Managing Reports Table 55: CDR Field Specifications (continued) Field Size Options Description Output Example Call OFF, ON Total time the line was connected to Duration the system, rounded down to the nearest minute with a 1-minute minimum. Because call duration represents a line’s entire activity on the system —...
Page 271 Working with CDRs and CODRs Table 55: CDR Field Specifications (continued) Field Size Options Description Output Example Conf Name OFF, ON Name of the conference in which Sales mtg the line was included. The system name appears in the Conf Name field for the first entry in a CDR.
Page 272 Managing Reports Table 55: CDR Field Specifications (continued) Field Size Options Description Output Example Conf Entry OFF, ON Time of day the line entered the hh:mm:ss Time conference based on Greenwich e.g. 08:59:30 Mean Time (GMT). The system records the time the line entered the user conference to the nearest second.
Page 273 Working with CDRs and CODRs Table 55: CDR Field Specifications (continued) Field Size Options Description Output Example Disc. OFF, ON Code indicating the reason the Reason system disconnected a call. Valid codes include: 0 = Unknown 1 = Network 2 = Operator hangup 3 = Invalid code 4 = Code timeout 5 = Conference secured...
Page 274 Managing Reports Table 55: CDR Field Specifications (continued) Field Size Options Description Output Example DNIS Digits OFF, ON DNIS/DDI digits that match an entry 9785556255 in the Call Branding table for dial-in calls processed by the system’s Call Routing feature. Transfer OFF, ON Indicates whether a line was...
Page 275 Working with CDRs and CODRs Table 55: CDR Field Specifications (continued) Field Size Options Description Output Example Calling OFF, ON Phone number from which a caller 978-552-6222 Phone dialed in to the conference. Applies only to systems configured to collect ANI digits.
Page 276: Configuring Codrs
Note: You cannot set a Note: second billing code using the Avaya Bridge Talk application. 8 of 8 1. Conf Num Sml is accurate up to room 998 only. Use the Conf Num Whl field to determine Conference Room Number as it accommodates all 2000 possible conferences.
Page 277 Working with CDRs and CODRs Use this procedure to configure CODRs: 1. Select Administrator Menu> Configurations > CODR Configuration. The system displays the CODR Configuration, screen 1. There are a total of four CODR Configuration screens on four pages. These screens include editable fields for each output style.
Page 278 Managing Reports CODR Configuration, screen 2 +-----------------------------CODR Configuration------------------------------+ ¦ ¦ ¦ FIELD(size) STYLE 1 STYLE 2 STYLE 3 AUTO CODR ¦ ¦ ¦ ¦ Notes(60) ¦ ¦ Conf End Time(17) ¦ ¦ Contact Name(20) ¦ ¦ Contact Phone(20) ¦ ¦ RP File Number(8) ¦...
Page 279 Working with CDRs and CODRs Table 56 describes CODR fields specifications: Field — Names of data fields. ● Size — Character lengths for data values output by the system. ● Output Example— Examples of data values showing the output format. ●...
Page 280 Managing Reports Table 56: CODR Field Specifications (continued) Field Size Options Description Output Example Conf ID OFF, ON Conference ID number or confirmation 000000000 number. For attended conferences, the system can be configured to automatically dept 23 assign conference IDs, or an operator can assign them manually.
Page 281 Working with CDRs and CODRs Table 56: CODR Field Specifications (continued) Field Size Options Description Output Example Conf Duration OFF, ON Period in minutes, (rounded up to the 1440 nearest minute), between the first participant joining the conference and the last participant leaving the conference.
Page 282 Managing Reports Table 56: CODR Field Specifications (continued) Field Size Options Description Output Example Attended (U/ OFF, ON Type of conference: A or U or O A — Attended (Operator assistance scheduled for this conference.) U — Unattended (Operator assistance not scheduled for this conference.
Page 283 Working with CDRs and CODRs Table 56: CODR Field Specifications (continued) Field Size Options Description Output Example Status Info. OFF, ON Indicates which of 11 different conference features were used in a EXIT conference. An ON appears in the REC - DIG CODR if the feature was used at any PBK - DIG time during the conference;...
Page 284 Managing Reports Table 56: CODR Field Specifications (continued) Field Size Options Description Output Example Conf End OFF, ON Date and time the last participant mm/dd/yy- Time leaves the conference. It is recorded to hh:mm:ss the nearest second, based on a e.g.
Page 285 Working with CDRs and CODRs Table 56: CODR Field Specifications (continued) Field Size Options Description Output Example Sched Partips OFF, ON Number of ports reserved for 1000 participants in a scheduled conference. This field always applies to scheduled unattended conferences; however, it also applies to attended conferences if the system’s Startup Notify Time parameter is set to ON and the...
Page 286 Managing Reports Table 56: CODR Field Specifications (continued) Field Size Options Description Output Example User Conf ON, OFF Indicates the type of conference: Type 0 — This conference is not a sub-conference or an intercept conference. 1 — This conference is a sub-conference convened from another conference.
Page 287: Multiple Codrs For One Conference Id
Note: You cannot set a Note: second billing code using the Avaya Bridge Talk application. 1Auto CODR has no Name field. 9 of 9 1. Conf Number Sml is accurate up to room 998 only. Use the Conf Number Whl field to determine Conference Room Number as it accommodates all 2000 possible conferences.
Page 288: Printing And Viewing Cdrs And Codrs
Managing Reports If you do not run Conference Clear_all for the attended conference, the system retains the ID for subsequent conferences and generates a CODR each time conference 25 empties. At day’s end, there are three CODRs with ID 000000001234, each with a different start time. If the system is configured for Automatic Conference Clear, IDs are not retained for subsequent conferences.
Page 289: Printing And Viewing Codrs
Working with CDRs and CODRs 3. Select the file you want to print or view: If you want to print the CDR, the system prompts you for a destination, the system or local ● printer. Upon making your selection the report prints to the selected destination. If you want to view the CDR, the system displays it.
Page 290: Printing Cdrs And Codrs With More Than 80 Columns
Managing Reports 2. Select an output style. The system displays a list of available CODR files. 3. Select the file you want to print or view: If you want to print the report, the system prompts you for a destination, the system or local ●...
Page 291: Conference Reports
Conference Reports Access Alarm Reports from the /usr/dcb/alarm directory. Sample Alarm Report $ more alarm.rpt ----------------------------------------------------------------------- Of 24 types, 18 are in use. ----------------------------------------------------------------------- Alarm Summary Report For - Critical Alarmed Events Power (Non Service Affecting) Occurrences: 1 Sat Jun 16 16:50:57 2001: Power degraded Temperature (Non Service Affecting) Occurrences: 1 Mon Jun 18 11:34:54 2001: Core temp low Sync./No Synchronization (Service Affecting) Occurrences: 0...
Page 292: Printing And Viewing Conference Reports
Managing Reports Scheduled participants (number of lines reserved for a scheduled conference) ● Conference duration (interval between the first person joining the conference and the last ● person leaving the conference) Total conference minutes (the approximate sum of the line conference minutes, with a ●...
Page 293 Conference Reports 2. Select the file from which you want to print or view a Conference Report. The system displays Include in Conference Report. Use this dialog to specify the company name or the company phone number in the report. Include in Conference Report +-----Include in Conference Report-----+ ¦...
Page 294: Lan Statistics Report
Managing Reports If you specify all conferences: ● Printing — Specify the destination printer, the system or local printer. Viewing — The report appears on the screen. The top portion of the Conference Report Screen lists CODR information, while the bottom portion lists individual line data from the CDRs associated with the conference.
Page 295: Drp Information In Codrs And Conference Reports
LAN Statistics Report Lan Statistics 73707 total packets received 0 bad header checksums 0 with bad IP version number 0 with size smaller than minimum 0 with data size < data length 0 with header length < data size 0 with data length < header length 0 with unknown protocol 0 with link layer broadcast addr but unicast IP addr 0 fragments received...
Page 296: Real-Time Cdrs And Codrs
0091 Real-time CDRs and CODRs The CS700/CS780 Conferencing Server’s Auto CDR server (cdrland) is a mechanism for real-time transmission of Call Detail Records (CDR) and Conference Detail Records (CODR) across the LAN. The system sends records to a host as they are generated (that is, each time a line disconnects from the system (CDRs) or each time a conference empties and clears (CODRs).
Page 297: The Autocdr Process
Real-time CDRs and CODRs The autocdr Process When the Automatic CDR Print parameter (see System Configuration on page 45) is set for LAN, the Auto CDR server begins the autocdr process after each reboot (re-initialization or shutdown). Once begun, this process finds the listen port number in the /etc/services file and listens for remote client (host) requests on that port.
Page 298: Record Format
Managing Reports Record Format Each Auto CDR record contains data specific to an individual call (CDR) and/or conference (CODR) on the audioconferencing system. When a record is sent across the LAN, this text string is prefixed by a code/date/sequence#/flags header. Clients can distinguish between the two types of records by examining the header: CDRs have a field type of "51", CODRs a field type of "52".
Page 299: Retrieving Records
Technically, the client can reside on any host, including the CS700/CS780 Conferencing Server (local host), but is more typically installed on a remote host. The program contains socket commands consisting of plain ASCII text and must be sent over a socket connection for processing.
Page 300: Checking A Connection
Managing Reports The format of REQUEST_CDR_CODR_FILE is: struct request_cdr_codr_file char cmd[2];// "03" char cdrMonth[3];// MMM (e.g. "Jan") char cdrDay[2];// DD (e.g. "01") char cdrSeqnum[5];// NNNNN (e.g. "00012") char mode[1];// Y or N char codrMonth[3];// MMM (e.g. "Jan") char codrDay[2];// DD (e.g.
Page 301: Auto Cdr Process Flow
Real-time CDRs and CODRs Auto CDR Process Flow This section summarizes the process of requesting and sending records between the Auto CDR server and the remote host. Table 57: Auto CDR Server Action and Remote Host Response Auto CDR Server... Remote Host...
Page 302: Preparing For Real-Time Export
Consult your TCP/IP documentation for the location of the /etc/services file on your host system. Note: Avaya service personnel configure the Auto CDR option during system Note: installation. Contact them, if you have any questions; for example, if you need to change the TCP/IP port assignment.
Page 303 Real-time CDRs and CODRs 3. Make sure the file /etc/hosts lists the IP address and system name of any computer on which your client program will run. Add the remote host by entering the appropriate parameters. For more information on adding hosts, see Configuring the System Hosts File on page 167.
Page 304 Managing Reports 304 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 305: Appendix A: Moderator And Participant Touchtone Commands
Appendix A: Moderator and Participant Touchtone Commands This appendix lists Dual Tone Multifrequency Dialing (DTMF) commands that moderators and participants can press on a telephone keypad to manage a conference. Participants can use a subset of these commands. This appendix includes instructions on: Managing conferences using touchtone commands ●...
Page 306: Managing Conferences Using Touchtone Commands
To browse a list of touchtone commands for participants, see Table Note: Contact Avaya Customer Support to enable features listed with an asterisk (*): Note: - Request help menu - Request roster...
Page 307: Participant Touchtone Commands
Managing conferences using touchtone commands Table 1: Default touchtone commands for moderators (continued) Press Feature Description Dial out by Moderator Dial While dialing out, the system accessing an temporarily removes the moderator open line from the conference. Available only after the moderator Return both presses *1 to access a line and dial moderator and...
Page 308 Moderator and Participant Touchtone Commands Table 1: Default touchtone commands for moderators (continued) Press Feature Description Start or stop a Digital Record/ The moderator can record a conference Playback conference digitally by pressing *2 (or recording from a Web-based application). If the system is configured to create filenames automatically, the system External Digital...
Page 309 Managing conferences using touchtone commands Table 1: Default touchtone commands for moderators (continued) Press Feature Description Toggle lecture Lecture The system plays a tone and then on or off places all participant lines in mute. Participants cannot unmute their individual lines while in lecture mode. Toggle self mute Mute Mutes or unmutes the line (if...
Page 310: Managing Conferences Using Flex Touchtone Commands
Moderator and Participant Touchtone Commands Table 1: Default touchtone commands for moderators (continued) Press Feature Description Track billing Billing code Prompts moderators to enter billing codes for prompt codes. Moderators can modify codes unattended or during the conference but only the last on-demand values entered will appear in the conferences...
Page 311 Managing conferences using touchtone commands Table 1: Default touchtone commands for moderators (continued) Press Feature Description Associate a web Web ID Requests the ID of the web conference with conference running in conjunction with the audio the audio conference. conference Allow or not Moderator The following settings determine the...
Page 312: Managing Flex Conferences Using Touchtone Commands
Moderator and Participant Touchtone Commands Table 2: Default touchtone commands for participants (continued) Press Feature Description Toggle self Mute Mutes or unmutes the line. mute on or off Note: Participants cannot Note: unmute their own lines if muted by an operator or by lecture mode.
Page 313 Managing flex conferences using touchtone commands If Change Conf Opt is scheduled for a conference, the system immediately prompts the ● leader to press 1 to start the conference. However, the leader can press 2 to change several conference options before the conference starts. After changing options, the leader can press 1 to start the conference.
Page 314 Moderator and Participant Touchtone Commands Table 3: Default flex touchtone commands to modify conference settings (continued) Press Feature Description Entry/Exit Prompt participants to state their names upon entering the conference. announcements Choose 1 to allow participants to hear a roll call. ●...
Page 315 Managing flex conferences using touchtone commands Tip: To browse a list of flex touchtone commands for participants, see Table Tip: Table 4: Default flex touchtone commands for leaders Press Feature Description Request Help An operator can speak to all participants conference-wide at the same time.
Page 316 Moderator and Participant Touchtone Commands Table 4: Default flex touchtone commands for leaders (continued) Press Feature Description Disconnect the Moderator Dial line and return to conference Disconnect the line continue dialing out Cancel request and return to conference Record the Unattended The leader can record an unattended conference...
Page 317 Managing flex conferences using touchtone commands Table 4: Default flex touchtone commands for leaders (continued) Press Feature Description Change Entry Tones/ The leader can change both tones to one Conference Exit Tones setting, such as Tones (or Message). Entry Tone & Note: Exit Do not select Tone &...
Page 318 Moderator and Participant Touchtone Commands Table 4: Default flex touchtone commands for leaders (continued) Press Feature Description Hear a private Roster The system temporarily removes the roll call during a requester from the conference and plays conference the names of the participants. Any single Stop playing the Ends the roster playback.
Page 319: Appendix B: Site Requirements
Managing flex conferences using touchtone commands Table 4: Default flex touchtone commands for leaders (continued) Press Feature Description Start or join a Unattended After pressing 93 from a telephone subconference Subconference keypad, a leader can: Press a subconference number from ●...
Page 320 Moderator and Participant Touchtone Commands Table 5 lists the default flex touchtone commands for participants. Table 5: Default flex touchtone commands for participants Press Feature Description Request Help An operator can speak to all conference-wide participants at the same time. This operator help command toggles on and off.
Page 321 Managing flex conferences using touchtone commands Table 5: Default flex touchtone commands for participants (continued) Press Feature Description Hear a list of DTMF Help Participants hear touchtone available commands that are available to touchtone participants only. commands Press any key to cancel. Start or join a Unattended After pressing 93 from a telephone...
Page 322 Moderator and Participant Touchtone Commands Administration and Maintenance of the S700/780 Audio Conferencing Server November 2008...
Page 323: Overview
Describes network, power, environmental, and cabling requirements for the system installation. Overview To maintain the low noise, low echo features of the system, Avaya recommends the following: Use T1 or E1 connections from the system to the public network. ●...
Page 324: Environmental
A UPS is highly recommended to prevent system shutdown and loss of data Note: during power interruptions. It must provide 350 W or greater. Environmental The CS700/CS780 Conferencing Server requires these environmental conditions: Ambient operating temperature: 5°C to + 40°C (32°F to 104°F) ● Ambient storage temperature: -40°C to +70°C ●...
Page 325: Lan Cabling
Network Connection Lines LAN Cabling The system connects to an Ethernet network through a 10/100BaseT network concentrator using unshielded twisted pair (UTP) cabling containing at least two pairs and meeting the specifications listed in the following section. The 10/100BaseT network concentrator must meet specifications defined in the ISO/IEC 8802.3 standard for repeaters and 10/100BaseT signaling.
Page 326: Maintenance Modem Line
Cabling Cabling is shielded twisted pair (1 pair transmit, 1 pair receive). Avaya recommends use of Category 5 cable. The shield is not terminated at the digital system. If the cable is continuous to the PBX or channel bank, the shield must be grounded to frame ground at that end. If there is a DSX or other break in the cable, the shield must be connected to the shield of the other cable.
Page 327: Introduction
Appendix C: System Maintenance Describes recommended system cleaning procedures, guidelines for using the Power On/Off switch and the Reset button, and the DSP card hot swap procedure. Introduction This chapter is organized as follows: Hot Swapping describes the recommended procedures for replacing DSP cards and T1 ●...
Page 328: Extracting A Dsp Card
System Maintenance CAUTION: To avoid losing system annunciator ports and causing other disruptive effects to CAUTION: the system, do not hot swap a DSP card if it is the only DSP card installed in the system chassis. Extracting a DSP Card Follow this procedure to extract a DSP card: 1.
Page 329: Hot Swapping A Pri
Hot Swapping Hot Swapping a PRI This section describes how to safely replace the PRI board while the system is active. Note: Hot swap is only supported for systems with Net Access Series NS301 PRI Note: cards. These hot swap procedures do not apply to other PRI cards. Contact Customer Support for help determining the model of PRI board installed in a system.
Page 330: Inserting The Pri
System Maintenance 7. Loosen the screws on the top and bottom latches of the back board. Note: The screws are fixed to the latch assemblies; do not attempt to remove them. Note: 8. Flip the card’s top latch half-way up and the bottom latch half-way down. 9.
Page 331: Backup
6. Verify the room temperature is lower than 40°C 7. Ensure that the hard wired music source is powered and running. 8. Ensure that the system is dust free. 9. Clean filters of fans for CS700/CS780 Conferencing Server. Issue 1 November 2008...
Page 332: Cleaning The Air Filter Assembly
1. Remove the assembly from the Front of the system chassis see Standard System Components on page 30. The CS700 has four spring-loaded screws. ● The CS780 has two spring-loaded screws. ● 2. Remove the vented panel from the chassis.
Page 333: Amend Date And Time To Reliable Source
Powering Down Amend Date and Time to Reliable Source Follow this procedure to amend the date and time: 1. Use the Maintenance and Admin Menu to select the System Date and Time. 2. Adjust the clock to reliable source date and time. 3.
Page 334 System Maintenance number of log files, log file size and volume. Preferably schedule maintenance to occur during low-usage or non-peak hours. 1. Follow this procedure to Shut Down the System. This procedure will take approximately 15 to 20 minutes. 2. Select System Shutdown from the System Maintenance Main Menu. 3.
Page 335: Using The Power On/Off Switch And Reset Button
Powering Down Using the Power On/Off Switch and Reset Button The Power On/Off switch (see Standard System Components on page 30) turns the system on and shuts the system off. The Reset button initiates a power-off/power-on cycle. Follow these guidelines: Avoid using the Power On/Off switch or the Reset button to reboot the bridge after setting ●...
Page 336 System Maintenance 332 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 337: Appendix D: Snmp Agent Configuration And Mib Object Definitions
Appendix D: SNMP Agent Configuration and MIB Object Definitions Describes SNMP agent configuration procedures and provides MIB object definitions. Configuring the Master Agent Configuration File The /etc/srconf/agt/snmpd.cnf includes the configuration settings for the system’s master SNMP agent, snmpdm. You can store a backup copy of the configuration file in any directory other than the /etc/srconf/agt directory.
Page 338 SNMP Agent Configuration and MIB Object Definitions sysNameEnter the fully qualified domain name for the system. snmpEnableAuthenTraps Enter 1 (default) to enable the agent to send authentication traps in response to receiving unauthorized management requests, or enter 0 to disable the agent from sending traps in response to receiving unauthorized management requests.
Page 339 Configuring the Master Agent Configuration File ################################################################### Define SNMP Community - Use this variable to change the default read-only and read-write SNMP Community Name for the t0000000 community from “public” to a customer-confidential name. Example: Change “public” to “myName.” snmpCommunityEntry t0000000 public public localSnmpID - - nonVolatile snmpCommunityEntry t0000000 myName myName localSnmpID - - nonVolatile...
Page 340 SNMP Agent Configuration and MIB Object Definitions vacmAccessStorageType (nonVolatile, permanent, readOnly) vacmAccessEntry Anyone - snmpv1 noAuthNoPriv exact CfgProt - CfgProt \ nonVolatile vacmAccessEntry Anyone - snmpv2c noAuthNoPriv exact CfgProt - CfgProt \ nonVolatile #Entry type: vacmSecurityToGroupEntry #Format: vacmSecurityModel (snmpv1, snmpv2c, snmpv2s, usm) vacmSecurityName (text) vacmGroupName...
Page 341 Configuring the Master Agent Configuration File recipient object is inform(2), then it will transmit Inform PDUs to the target recipient (Network Management Station). Each notification type defined has a label that is used in subsequent definitions (described below) - in this case, they are called "31" and "32", but can be any text string.
Page 342 SNMP Agent Configuration and MIB Object Definitions snmpTargetParamsSecurityLevel (noAuthNoPriv,authNoPriv,autPriv) snmpTargetParamsStorageType (nonVolatile, permanent, readOnly) snmpTargetParamsEntry v1ExampleParams 0 snmpv1 public noAuthNoPriv \ nonVolatile snmpTargetParamsEntry v2cExampleParams 1 snmpv2c public noAuthNoPriv \ nonVolatile MIB Object Definitions You can compile the MIB, Bridge700.my for your SNMP management application. A copy of the file is located in the /etc/srconf directory.
Page 343 Configuring the Master Agent Configuration File tSystemParams OBJECT-IDENTITY STATUS current DESCRIPTION"Subtree for system parameters." ::= { spectel-bridge700-mib 1 } tRunTimeRsc OBJECT-IDENTITY STATUS current DESCRIPTION "Subtree for the run-time resources. " ::= { spectel-bridge700-mib 2 } tTelecomTrunks OBJECT-IDENTITY STATUS current DESCRIPTION "Subtree for the telecom trunks. " ::= { spectel-bridge700-mib 3 } tLANMonitor OBJECT-IDENTITY STATUS current...
Page 344 SNMP Agent Configuration and MIB Object Definitions tSystemParamsPowerSupplyDegradedTrap NOTIFICATION-TYPE STATUScurrent DESCRIPTION"Fires when power supply is signaling an overload or over temp state" ::= { tSystemParams 5} tSystemParamsPowerSupplyFaultTrap NOTIFICATION-TYPE STATUScurrent DESCRIPTION"Fires when power supply is OOS due to no input, over-temp, over-current"...
Page 345 Configuring the Master Agent Configuration File MAX-ACCESSnot-accessible STATUScurrent DESCRIPTION"Information about a specific instance of a filesystem" INDEX{ tRunTimeRscFSIndex } ::= { tRunTimeRscFSTable 1 } tRunTimeRscFSIndexOBJECT-TYPE SYNTAXINTEGER (1..65535) MAX-ACCESSread-only STATUScurrent DESCRIPTION"Index used to select a filesystem in the table" ::= { tRunTimeRscFSTableElement 2 } tRunTimeRscFSName OBJECT-TYPE SYNTAXDisplayString MAX-ACCESSread-only...
Page 346 SNMP Agent Configuration and MIB Object Definitions STATUScurrent DESCRIPTION"Fires when the host has run out of memory" ::= { tRunTimeRsc 6} tRunTimeRscHostProcessFaultTrap NOTIFICATION-TYPE OBJECTS { tRunTimeRscHostProcessFaults } STATUScurrent DESCRIPTION"Fires when at least one host process fault has been detected in the last 15 minutes"...
Page 347 Configuring the Master Agent Configuration File INDEX{ tTelecomTrunksIndex } ::= { tTelecomTrunksTable 1 } TelecomTrunksTableEntry ::= SEQUENCE { tTelecomTrunksCountINTEGER, tTelecomTrunksIndex INTEGER, tTelecomTrunksIdentifier DisplayString, tTelecomTrunksLineType INTEGER, tTelecomTrunksLineStatus INTEGER, tTelecomTrunksLineCoding INTEGER, tTelecomTrunksLES Gauge32, tTelecomTrunksCSS Gauge32, tTelecomTrunksES Gauge32, tTelecomTrunksBES Gauge32, tTelecomTrunksSES Gauge32, tTelecomTrunksSEFS Gauge32, tTelecomTrunksDM Gauge32,...
Page 348 SNMP Agent Configuration and MIB Object Definitions tTelecomTrunksLineStatus OBJECT-TYPE SYNTAXINTEGER { dsx1NoAlarm(1), dsx1RcvFarEndLOF(2), dsx1XmtFarEndLOF(4), dsx1RcvAIS(8), dsx1XmtAIS(16), dsx1LossOfFrame(32), dsx1LossOfSignal(64), dsx1LoopbackState(128), dsx1T16AIS(256), dsx1RcvFarEndLOMF(512), dsx1XmtFarEndLOMF(1024), dsx1RcvTestCode(2048), dsx1OtherFailure(4096) MAX-ACCESSread-only STATUScurrent DESCRIPTION"Indicates the the type of line status of the interface." ::= { tTelecomTrunksTableElement 5 } tTelecomTrunksLineCoding OBJECT-TYPE SYNTAXINTEGER { dsx1JBZS(1),...
Page 349 Configuring the Master Agent Configuration File MAX-ACCESSread-only STATUScurrent DESCRIPTION"The number of Errored Seconds in the last 15 minutes." ::= { tTelecomTrunksTableElement 9 } tTelecomTrunksBES OBJECT-TYPE SYNTAXGauge32 MAX-ACCESSread-only STATUScurrent DESCRIPTION"The number of Bursty Errored Seconds in the last 15 minutes." ::= { tTelecomTrunksTableElement 10 } tTelecomTrunksSES OBJECT-TYPE SYNTAXGauge32 MAX-ACCESSread-only...
Page 350 SNMP Agent Configuration and MIB Object Definitions tTelecomTrunksLossOfFrameFailureTrap NOTIFICATION-TYPE OBJECTS { tTelecomTrunksIndex } STATUScurrent DESCRIPTION"T1 - persistent OOF or LOS defect. E1 - OOF defect. " ::= { tTelecomTrunks 4} tTelecomTrunksLossOfSignalFailureTrap NOTIFICATION-TYPE OBJECTS { tTelecomTrunksIndex } STATUScurrent DESCRIPTION"Red alarm" ::= { tTelecomTrunks 5} tTelecomTrunksLoopbackPseudoFailureTrap NOTIFICATION-TYPE OBJECTS { tTelecomTrunksIndex }...
Page 351: Appendix E: System And Log Messages
Configuring the Master Agent Configuration File tLANMonitorPacketsReceived OBJECT-TYPE SYNTAXCounter32 MAX-ACCESS read-only STATUScurrent DESCRIPTION"The number of packets received without errors in the last 15 minutes" ::= { tLANMonitor tLANMonitorBytesReceived OBJECT-TYPE SYNTAXCounter32 MAX-ACCESS read-only STATUScurrent DESCRIPTION"The number of bytes received without errors in the last 15 minutes" ::= { tLANMonitor tLANMonitorTransmitErrors OBJECT-TYPE SYNTAXCounter32...
Page 352 SNMP Agent Configuration and MIB Object Definitions --- ========================================= --- Event Logging portion of the MIB --- ========================================= tLogTableSize OBJECT-TYPE SYNTAXCounter32 MAX-ACCESSread-only STATUScurrent DESCRIPTION "The number of log messages that should be stored in the srLogTable. If the number of entries in the table exceeds srLogTableSize, the oldest log message is discarded."...
Page 353 Configuring the Master Agent Configuration File MAX-ACCESS read-only STATUS current DESCRIPTION "The time when this log message was generated, as measured (in hundredths of a second) since the network management portion of the system was last re-initialized." ::= { tLogTableElement 3 } tLogSubSystem OBJECT-TYPE SYNTAX...
Page 354 SNMP Agent Configuration and MIB Object Definitions 350 Administration and Maintenance of the S700/780 Audio Conferencing Server...
Page 355: System Messages
Appendix E: System and Log Messages Describes system messages, log message codes, UNIX error message codes, and hardware error message codes. System Messages The following messages may appear across the top of the operator screen. The appropriate action for each situation is described. Table 7: System Messages and Recommended Responses Message Meaning...
Page 356 System and Log Messages Table 7: System Messages and Recommended Responses (continued) Message Meaning Action Could Not Create Although a valid From the operator Unattended Conference: conference passcode console, run a All Confs. In Use was entered, all Conference Clear_all on conferences are in use all empty conferences to or have not been...
Page 357 System Messages Table 7: System Messages and Recommended Responses (continued) Message Meaning Action Empty Blast List Or No There are several View dial list to Items Selected possibilities: determine nature of error and try again. Operator blasted empty list or list without phone numbers.
Page 358: Log Message Codes
System and Log Messages Log Message Codes The following sections describe the error messages associated with specific codes in the system log files. If you need more information concerning a particular error, contact Customer Support. Each message is in a 6-line format. The first line of each message is blank and the sixth line contains a single semicolon: 2 - systemName_nodeName date&time 3 - AsequenceNumber.messageNumber REPT AUTO...
Page 359 Log Message Codes 0000–0999: Status Messages Table 8: Status Message Definitions Message Message Meaning Code 0100 DCB SYSTEM RESTARTED Someone ran a system shutdown and the system restarted at the specified time. Typically followed by diagnostics and cold restart messages. 0103 %s alarm clear on %s: %s Indicates a network (T1) alarm has...
Page 360 System and Log Messages Table 8: Status Message Definitions (continued) Message Message Meaning Code 0104 %s alarm set on %s: %s Indicates a network (T1) alarm has been set. Variables are alarm type, alarm location (Trunk), and alarm classification. Alarm Type Alarm Classification Red/Carrier Major/Service Affecting...
Page 361 Log Message Codes Table 8: Status Message Definitions (continued) Message Message Meaning Code 0110 Blast dial list %d (%s) - A blast/reblast has been requested insufficient channels available but insufficient user channels are available. The channels are either in use for other calls, still disconnecting from previous calls, or are out of service/faulted.
Page 362 System and Log Messages Table 8: Status Message Definitions (continued) Message Message Meaning Code 0118 Cannot find channel %d in Whenever a channel is placed into a conference %d conference, it is always moved from one conference to another. This error indicates that the channel could not be found in its previous conference.
Page 363: 1000-1999: User/Usage Messages
Log Message Codes Table 8: Status Message Definitions (continued) Message Message Meaning Code 0125 No transition found for channel Indicates a T1/Call Handler state %d, message 0x%X, state %s transition error. An event has occurred on a channel which is not defined for the state that the channel is in.
Page 364: 2000-2999: Process Interface Messages
System and Log Messages Table 8: Status Message Definitions (continued) Message Message Meaning Code 0134 System time has been reset Database updated. 0135 Timer lost, source process %d Memory allocation error in the Timer tag 0X018X, operation %s process. 0136 Warm restart requested but A system re-initialization was started, network device not configured...
Page 365 Log Message Codes Table 8: Status Message Definitions (continued) Message Message Meaning Code 0149 Duplicate DTMF Digits in Indicates that the ‘digits.txt’ file has digits.txt, %s and %s been modified and that an error has occurred in the definition of the indicated digits.
Page 366 System and Log Messages Table 8: Status Message Definitions (continued) Message Message Meaning Code 0157 Bad Parameters Passed For Incorrect information entered by DigConf. Rec/Play operator and not trapped in operator screen. 0158 Could Not Allocate Annunciator Operator requested DigRP channel For DigConf.
Page 367 Log Message Codes Table 8: Status Message Definitions (continued) Message Message Meaning Code 0168 LAN configuration updated. An administrator changed the LAN configuration. 0174 Rebuilt conference scheduler This message follows 0134 on a shared database. system running the Conference Scheduler (administrator resets system date/time) or 0146 (administrator activates Conference Scheduler).
Page 368 System and Log Messages 2000–2999: Process Interface Messages Table 10: Process Interface Messages Message Code Message Meaning 2000 MakeNull/Add/Peek/ The specified software Delete link list failure operation with respect to link lists failed. 2001 Cannot start/stop timer An attempt to start or stop a timer provided by the timer process or to create a queue for such timers...
Page 369 Log Message Codes Table 10: Process Interface Messages (continued) Message Code Message Meaning 2101 Received unknown A process received a command 0x%d message to perform an unknown or unsupported operation with the specified command number. 2102 Undefined message type Indicates a message has 0x%X received from been received by a process %d...
Page 370 System and Log Messages Table 10: Process Interface Messages (continued) Message Code Message Meaning 2202 Process terminating - A LAN process terminated 'service-name' service not trying to set up a listener found in ‘/etc/services’ file for a particular LAN service because it was unable to obtain port assignment information regarding service...
Page 371: 3000-3999: Unix System Error Messages
Log Message Codes 3000–3999: UNIX System Error Messages These are UNIX directory, file, fork/exec, alloc, shm, lock, prio, rtalarm, and ipc errors. Table 11: Unix System Error Messages Message Code Message Meaning 3000 Cannot change to name The process cannot change directory to the specified directory.
Page 372 System and Log Messages Table 11: Unix System Error Messages (continued) Message Code Message Meaning 3110 File not COFF format A file to be downloaded to a DSP has the wrong format for downloading. 3111 Cannot read name The specified file cannot be read.
Page 373 Log Message Codes Table 11: Unix System Error Messages (continued) Message Code Message Meaning 3305 Cannot map dual-port A failed attempt to write the memory reference memory using the dual-port memory defining DSo timeslots for use by the transmit PLD on the MVIP bus.
Page 374 System and Log Messages Table 11: Unix System Error Messages (continued) Message Code Message Meaning 3900 Process terminating - A LAN process terminated func-name function call trying to set up a listener for failed a particular LAN service due to either inadequate system resources or a system/software error when trying to execute...
Page 375 Log Message Codes 4000–4999: Hardware and Device Messages Table 12: Hardware and Device Messages Message Code Message Meaning 4000 Annunciator ready event An attempt to report to the annunciator %d failed for channel %d process that the specified buffer is ready for the logical channel failed.
Page 376: Api Messages
System and Log Messages Table 12: Hardware and Device Messages (continued) Message Code Message Meaning 4019 Put_(in) active error An attempt to set a DSP node active or inactive has failed. 4020 Read_intr error The event process failed to read a interrupt message from the DSP driver.
Page 377 Log Message Codes Table 12: Hardware and Device Messages (continued) Message Code Message Meaning 4107 Network %d failed- switch: The memory diagnostic for the specified %c, memory: %s, stream” network failed for the indicated switch, %d, channel %d memory, stream, and channel. 4108 Network in service - %s Indicates a network trunk has come into...
Page 378 System and Log Messages Table 12: Hardware and Device Messages (continued) Message Code Message Meaning 4117 DSP Board %d fails MVIP The specified MVIP control test failed for RX/TX ping pong test the specified DSP board. 4118 DSP node %d - minimum The specified DSP failed the MVIP frame MVIP RX/TX frame count count test.
Page 379 Log Message Codes Table 12: Hardware and Device Messages (continued) Message Code Message Meaning 4123 DSP node %d test During the specified DSP test, the parameter: Wrote 0x%d, specified parameter was written, but the got 0x%d DSP got a different one or did not recognize the parameter.
Page 380 System and Log Messages API Messages Table 13: API Messages Message Code Message Meaning api natevent.c 574 No such Error message written to / file or directory usr/dcb/logs when a NAT'd workstation unexpectedly Failed on poll. POLLER on terminates connection. NAT event Session API Num API num is equal to the number of the API session...
Page 381: Appendix F: Trunk Alarms
Appendix F: Trunk Alarms Describes trunk alarms and recommends how to respond to trunk alarms. Trunk Alarm Definitions The system tracks numerous trunk alarm conditions. Alarm conditions indicate trouble along the transmission path, either at the system end or the far network end. These problems occur on a per-trunk basis.
Page 382: Responding To Trunk Alarms
Trunk Alarms Table 14: Summary of Trunk Alarm Conditions (continued) Alarm Type Cause Severity Class Clears When Blue alarm Unframed all 1s pattern. Nonalarm Cessation of all 1s The system releases all pattern lines currently seized on the trunk, thus transmitting a yellow alarm to the network.
Page 383 Trunk Alarm Definitions Table 14: Summary of Trunk Alarm Conditions (continued) Alarm Type Cause Severity Class Clears When Determines how many frames have errors. (Available for ESF framing mode only.) ESecs The system tracks the number of seconds having at least one CRC error.
Page 384 Trunk Alarms Table 15: Trunk Alarm Descriptions (continued) Alarm Description Not Installed Declared for any trunk not installed on the system. This nonalarmed event is classified as nonservice affecting. Maintenance Occurs when an administrator disables a trunk or a trunk has not been configured. A trunk in this state transmits a blue alarm to the network.
Page 385: Index
Index Index Symbols ........cdr files Access privileges. See Sign-ins .
Page 386 Index ..... Automatic CDR Print, system parameter Call Duration, CDR field ......Automatic Conf.
Page 387 Index ......... printing headers .
Page 388 Index ......Conference reports /usr/dcb/dbase/unattend ..... . .
Page 389 Index ..........dnis process .
Page 390 Index ........CDRs Super Frame (SF) .
Page 391 Index ....commands Line coding for T1 ..... . .
Page 392 Index ......tLANMonitor tTelecomTrunksIdentifier ... .
Page 393 Index ......synchronization errors Operator printouts ....Network settings viewing .
Page 394 Index ......... . pins.txt prompt sets .
Page 395 Index ....system configuration Signal class ......... tag files E&M .
Page 396 Index ....Subscription Features transaction logs ......Entrance Announcements System Date and Time .
Page 397 Index ........viewing User Transaction Log .
Page 398 Index Administration and Maintenance of the S700/780 Audio Conferencing Server November 2008...

This manual is also suitable for:

Cs780

Avaya CS700 Administration And Maintenance

Preface

Audience

Conventions

Related Documents

How to Get Help

Chapter 1: System Features

Introduction

System Configuration Overview

Audioconferencing Features

Conference Call Modes

Hardware Features

Chapter 2: Configuring System-Wide Settings

Introduction

System Configuration

System Supervision

Time-Sensitive Operator Assistance Configuration

System Date and Time

Blast Dial Parameters

Voice Message Configuration

Operator Audio Paths

Flex Configuration Settings

Chapter 3: Configuring Channels and Call Routing

Establishing Port Groups

Call Routing Configuration

Branding Calls Using Cbutil

Setting up Flex Call Routing

Chapter 4: Managing Annunciator Messages

Introduction

Prompt Sets

Annunciator Messages

Managing Annunciator Text

About Annunciator Performance

Chapter 5: Using the System Management Interface

Working with the Management Interface

Managing User Sign-Ins

Reservation Features

Chapter 6: System Maintenance Options

Configuring Network Settings

Configuring T3

Configuring the FDAPI

Configuring the System Hosts File

Adjusting the Channel Transmission Level

System Re-Initialization

System Shutdown

Chapter 7: Configuring Conference Scheduler

Working with the Conference Scheduler

Configuring Warning Tones

Using External Passcode Validation

Chapter 8: Managing Files

Introduction

About System Files

Working with the File Management Menu

Working with the Printer Management Menu

Working with the Backup/Restore Menu

Saved Roster Audio Files

Configuration Files

Dial Lists

LAN Statistics Report

Log Files

Operator Transaction Logs

Digital Record/Playback (DRP) Files

Traffic Statistics

Managing System Files from a Remote Host

Additional Information about File Transfers

Managing the PIN Code Files

Loading PIN Codes and PIN Lists to into Bridgedb

Chapter 9: Managing Reports

Working with Cdrs and Codrs

Alarm Report

Conference Reports

LAN Statistics Report

Real-Time Cdrs and Codrs

Appendix A: Moderator and Participant Touchtone Commands

Managing Conferences Using Touchtone Commands

Managing Flex Conferences Using Touchtone Commands

Appendix B: Site Requirements

Overview

Power

Appendix C: System Maintenance