1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Server
  5. CS7000
  6. Administrator's manual

Avaya CS7000 Administrator's Manual

9.4 suite release
Hide thumbs Also See for CS7000:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Operating Manual
Avaya Meeting Exchange
CS7000 9.4 Suite Release
System Administrator Guide
04-600799
Issue 1
CS7000 9.4 Suite Release
January 2006

Advertisement

Table of Contents
loading

Related Manuals for Avaya CS7000

Summary of Contents for Avaya CS7000

  • Page 1 Avaya Meeting Exchange CS7000 9.4 Suite Release System Administrator Guide 04-600799 Issue 1 CS7000 9.4 Suite Release January 2006...
  • Page 2 Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://www.avaya.com/support...

  • Page 3: Table Of Contents

    Avaya Notifications Subsystem ......Avaya Template Editor ......
  • Page 4 Viewing the Audio Conferencing Status ..... . . Shutting down Avaya CS7000 Conferencing Server ....
  • Page 5 Contents Chapter 5: Introducing the Avaya Client Registration Server (CRS) ..Chapter 6: Administering the Avaya Client Registration Server (CRS) ..Starting the CRS Front End ......
  • Page 6 Setting the Maximum Number of Extension Periods ....Reusing the Same DDI for Scheduled Conferences....CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 7 Chapter 8: Configuring the Bands Initialization File ....Chapter 9: Introducing the Avaya Notification Subsystem ....
  • Page 8 Notification Templates....... . . Installing Avaya Template Editor ......
  • Page 9 Contents Chapter 13: Administering the Avaya SMS Controller ....The Short Message Service Controller ......
  • Page 10 LogSettings ........Chapter 17: Administering the Avaya Demand PIN Master ....

  • Page 11: Chapter 1: Introducing This Guide

    Contents of this guide The Avaya CS7000 Conferencing Server Administrator Guide is aimed at Avaya System Administrators. Users or Operators of the Avaya CS7000 Conferencing Server can consult the Avaya CS7000 Operator Guide for information on how to use the system.

  • Page 12: Avaya Client Registration Server (Crs)

    Avaya Operator Console and the CMS. Operators use the Avaya CRS Front End to create scheduled and demand conferences. Operators also use the Avaya CRS Front End to create and maintain company and client accounts. For more information, see: Introducing the Avaya Client Registration Server (CRS) ●...

  • Page 13: Avaya Notifications Subsystem

    ● Troubleshooting the Avaya Notifications Subsystem ● Avaya Template Editor Use the Avaya Template Editor to create and edit a set of fax and e-mail templates. The Avaya Notifications Subsystem uses these templates. The Avaya Template Editor automates an otherwise manual task. Before the release of the Avaya Template Editor, users had to create and edit individual templates.

  • Page 14: Avaya Data Services Client Application (Dsca)

    Chapter 1: Introducing this Guide Avaya Data Services Client Application (DSCA) Use the Avaya DSCA to ensure that registration details stored on the CRS are synchronized with registration details stored on the directory server. For more information, see: Administering the Avaya Data Services Client Application (DSCA) ●...

  • Page 15: New Features In The Avaya Cs7000 Conferencing Server

    New features in the Avaya CS7000 Conferencing Server New features in the Avaya CS7000 Conferencing Server Avaya has added a new feature to the Avaya Demand Pin Master to ensure that users do ● not needlessly waste resources. In this release, you can configure demand conferences to close if only a single conferee remains for a specified period of time.

  • Page 16: Additional Reading

    Chapter 1: Introducing this Guide Additional reading There are several guides that cover topics that are referenced, but not fully described in the current manual. These guides are available from the Avaya web site. Avaya CS7000 9.4 Conferencing Server Operator Guide ●...

  • Page 17: Chapter 2: Introducing The Avaya Conference Management Server (Cms)

    Starting CMS ● Introducing the CMS The CMS is the nerve center of the Avaya CS7000 Conferencing Server. It performs all the basic housekeeping tasks required by the system. These tasks are performed automatically without manual intervention. Using the CMS manager, you can: View the entire system configuration from system wide view to card level.

  • Page 18: Finding Cms Files

    Chapter 2: Introducing the Avaya Conference Management Server (CMS) Change the status of individual... ● - shelves - cards - lines - The entire system ...from in-service to out-of-service, and back again. Usually, you monitor the system through the various CMS applications and intervene only if a problem occurs.
  • Page 19 Table 1: CMS Files (continued) c:\C2001\bin c:\C2001\data SIF.EXE Cons.fil STATS.EXE Emi.Fil hh.fil hhconferee.fil icddi.fil isf.fil Isl.fil L13.fil Mf.fil Ogrouting.fil Pri.fil Routing.fil Serial.fil Sync.fil Sysparm.fil Timer.fil Aemess.log Armess.log Numbers.fil 2 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 20: Starting Cms

    Chapter 2: Introducing the Avaya Conference Management Server (CMS) Starting CMS This section describes how to start the CMS. It also describes the linked applications that make up the CMS. It contains the following sections: Starting CMS ● CMS applications ●...

  • Page 21: Cms Applications

    STATS accepts statistic records from the AC and puts them into *.cdr files. SCOMMS Serial SCOMMS implements serial Communications communications between the shelves and the CMS. It also displays serial communications statistics. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 22 Chapter 2: Introducing the Avaya Conference Management Server (CMS) CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 23: Chapter 3: Administering The Avaya Conference Management Server (Cms)

    Updating details of a shelf, slot, trunk, or line ● Viewing the database ● Updating recording settings ● Managing outgoing routing ● Managing DDI Tables ● Viewing ISF Settings ● Managing IPDDI Tables ● CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 24: Viewing Cms Version Details

    Chapter 3: Administering the Avaya Conference Management Server (CMS) To view the Acpc Management - man application: Select the Acpc Management - man application shortcut from the taskbar. ● The system displays the Acpc Management - man application. Figure 2: Acpc Management - man The Acpc Management - man application displays the status of shelves, cards, and lines.

  • Page 25: Viewing System Status

    Click OK to return to the Acpc Management - man application main screen. Viewing system status To view the system status: From the System menu, select Display. ● The system displays the system status screen. Figure 4: System Status CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 26: System Status Fields

    Chapter 3: Administering the Avaya Conference Management Server (CMS) System status fields Table 3: System Status Fields Item Description System status Displays the system status, in the following format: INS (INS). The status in brackers refers to the expected status. The status outside the brackets refers to the actual status.
  • Page 27 The system displays the shelf details. Figure 6: Shelf Details To view a slot: 1. Enter the slot number in the Slot field. 2. Click Slot. The system displays the slot details. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 28 Chapter 3: Administering the Avaya Conference Management Server (CMS) Figure 7: Slot Details To view a line: 1. Enter the shelf number in the Line field. 2. Click Line. The system displays the line details. Figure 8: Line Details CS7000 System Administrator Guide for Release 9.4...

  • Page 29: Updating Details Of A Shelf, Slot, Trunk, Or Line

    1. Enter the trunk number in the Trunk field. 2. Ensure that Trunk is selected in the Scope panel. 3. Click OOS Hard to put the trunk out of service. Click INS to put the trunk in service. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 30: Viewing The Database

    Chapter 3: Administering the Avaya Conference Management Server (CMS) To edit a line: 1. Enter the line number in the Line field. 2. Ensure that Line is selected in the Scope panel. 3. Click OOS Hard to put the line out of service.

  • Page 31: Viewing Audio Conferencing Configurations

    The system displays the audio conferencing system (ACS) data. Figure 11: Audio Conferencing Configuration Data Viewing Operator Console applications To view Operator Console configurations: 1. From the Database menu, select Consoles. The system displays the Console Display screen. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 32: Vewing Telephone Configurations

    Chapter 3: Administering the Avaya Conference Management Server (CMS) Figure 12: Console Display 2. Click Console Config. The Console Display screen displays the console configuration. Vewing telephone configurations To view telephone configurations: From the Database menu, select Telephones. ● The Acpc Management – man screen displays the telephone configuration.

  • Page 33: Viewing Map Configurations

    To update recording settings: 1. From the AppRec menu, select Logging. The system displays the Application Recording Settings dialog. 2. Update the recording settings. 3. Click OK. The updates are saved. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 34: Managing Outgoing Routing

    PRI.fil files. When a dial out is required in the Avaya CS7000 Conferencing Server, the system looks at the ogrouting.fil file. The system checks this file to see if the number or prefix has an associated hunt group.
  • Page 35 3, slot 4. This calls goes out on a trunk in shelf 3, slot 4 in accordance with the settings in the pri.fil file. The pri.fil file is set to use 003 by default. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 36: Viewing Outgoing Routing Settings

    Chapter 3: Administering the Avaya Conference Management Server (CMS) Customers can also specify a descending list of preferred trunks to be used when their first preference reaches capacity. This functionality diverts calls through alternative trunks during times of heavy load. In the ogrouting.fil file, trunks are separated by commas. The sample ogrouting.fil file below shows a descending list of preferred trunks:...

  • Page 37: Editing Outgoing Routing Settings

    The settings for outgoing routing are uploaded from the ogrouting.fil file in C:\C2001\data. To edit outgoing routing settings, you must update this fil file. Avaya recommends that you save a copy of the original file before you make any changes.

  • Page 38: Editing Ddi Tables

    Chapter 3: Administering the Avaya Conference Management Server (CMS) Figure 16: DDI Table 2. Click Read Ic Ddi. The Ic Ddi dialog displays the Ic Ddi configuration. The PRI address column displays the line on which the associated digit string is routed.

  • Page 39: Viewing Isf Settings

    The system displays 64 consecutive channels starting with the channel number entered in the ISF channel field. The Acpc Management - man screen displays the ISF status. Figure 18: ISF Information in the Acpc Management - man Screen CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 40: Managing Ipddi Tables

    Chapter 3: Administering the Avaya Conference Management Server (CMS) Managing IPDDI Tables In the IPDDI.fil, you can map SIP addresses and IP addresses to DDIs. This mapping ensures that whether users use VoIP or more traditional telephony technology, the experience is the same.

  • Page 41: Viewing Application Recordings

    Select the Acpc Recording - AR application from the startup menu. ● Figure 19: AR Application You can use this screen to review the operations of the Avaya CS7000 Conferencing Server and help the troubleshooting of problems. Application Recording produces messages in the following format: {Date &...

  • Page 42: Viewing Application Errors

    Chapter 3: Administering the Avaya Conference Management Server (CMS) Viewing Application Errors To review alarms and errors: Select the Acpc Errors – ae application. ● Figure 20: AE Application The system displays the errors in real time, so it only displays recent events.

  • Page 43: Viewing Statistics

    To view messages and links sent and received: Click Monitor. ● To view link statistics and messages for different shelves: 1. Enter the required shelf number, in the case of multishelf systems. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 44 Chapter 3: Administering the Avaya Conference Management Server (CMS) 2. Click Set Com Port. Table 4 describes the fields on the Scomms dialog. Table 4: Field Descriptions Item Description Start Polls Indicates receipt of a connect message from a shelf to the CMS.

  • Page 45: Viewing The Number Of Connected Consoles

    The system diaplays the Status field if a system is in service (INS) or out of service (OOS). The Total Seconds field displays how long the system is running, in seconds. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 46: Shutting Down Avaya Cs7000 Conferencing Server

    Chapter 3: Administering the Avaya Conference Management Server (CMS) Shutting down Avaya CS7000 Conferencing Server Double-click the Do Stop icon on the desktop. ● Figure 24: Do Stop The CMS must be started using BSMon tool. CS7000 System Administrator Guide for Release 9.4...

  • Page 47: Chapter 4: Configuring The Avaya Conference Management Server (Cms)

    ● Numbers configuration file (Numbers.fil) ● Serial configuration file (Serial.fil) ● Synchronization configuration file (Sync.fil) ● Internet protocol direct dial inward configuration file (IPDDI.fil) and Voice Over Internet ● Protocol (VoIP) CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 48: Introducing Cms System Configuration Files

    ● A string, which cannot contain blanks ● For more information about each of the CMS configuration files, see the Avaya 9.4 Conference Management Server Configuration File Guide. Shelf configuration file (Acs.fil) The file c:\C2001\data\acs.fil defines shelf configuration. This file tells the CMS the position of all cards used in its shelf or shelves.

  • Page 49: Primary Rate Interface Configuration File (Pri.fil)

    The file c:\C2001\data\LI3.fil defines the configuration details of the LI3 cards used in the system. It specifies the location and status of each card and the LI3 channel configuration. The LI3 card and the OI16 card are set up similarly. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 50: Intershelf Links Configuration File (Isl.fil)

    Chapter 4: Configuring the Avaya Conference Management Server (CMS) Intershelf links configuration file (Isl.fil) This file sets the parameters for intershelf linking. The ISL personality module links the switching matrix of one shelf to another. The system provides for the linking of 32 digital channels between the central processing units (CPUs) on two different shelves.

  • Page 51: Conference Configuration File (Conf.fil)

    AESIZE = 10000 MAX size of AEMESS.LOG in units of Kilobytes before automatic reset. ARTOTAL = 100000 MAX size of all ARnnnn.BAK files in units of Kilobytes before oldest deleted. 1 of 5 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 52 Chapter 4: Configuring the Avaya Conference Management Server (CMS) Table 5: Sysparm.fil (continued) Parameter Description AETOTAL = 100000 MAX size of all AEnnnn.BAK files in units of Kilobytes before oldest deleted. AUTO_CONFIG_OFF = N Y means that if an exception occurs, it is not automatically handled.
  • Page 53 If ROUTE* != 0, * routing is enabled. When a conferee hits the '*', followed by up to three digits, the system attempts to route him to the corresponding conference as per the AUTOROUTE option. 3 of 5 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 54 Chapter 4: Configuring the Avaya Conference Management Server (CMS) Table 5: Sysparm.fil (continued) Parameter Description DCHAIR = Y If DCHAIR = Y, resource control does not guarantee a CHAIRMAN position and reserves conference CNF lines as per the OPEN size. Dynamic CHAIRMEN use the CNF group 3.

  • Page 55: Console Configuration File (Cons.fil)

    PLAY_MESS_TO_CONF=N, messages are played to all callers. 5 of 5 Console configuration file (Cons.fil) Console configuration is specified in the file c:\C2001\data\cons.fil. This file tells the CMS which consoles are in service. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 56: Ems Configuration File (Emi.fil)

    Chapter 4: Configuring the Avaya Conference Management Server (CMS) EMS configuration file (Emi.fil) This file sets the parameters for communications between the CMS and the EMI card. Application recording configuration file (Aprec.fil) This file is read by the CMS at start up and sets the defaults for the application recording functionality.

  • Page 57: Mf.fil

    Sync.fil determines the order of PRIs used in failover situations. For example, in a failover situation, slot one might be the initial point, followed by slot two as a backup, and so on. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 58: Internet Protocol Direct Dial Inward Configuration File (Ipddi.fil) And Voice Over Internet Protocol (Voip)

    The CS7000 ensures that the user experience is transparent, irrespective of the transport method. The principle is that all traffic occurs within the same CS7000 conferencing infrastructure as the PSTN traffic. The user experience, the Operator experience, and elements such as billing and reporting remain essentially unchanged.

  • Page 59: Chapter 5: Introducing The Avaya Client Registration Server (Crs)

    Chapter 5: Introducing the Avaya Client Registration Server (CRS) As a System Administrator, you use the Avaya Client Registration Server (CRS) to manage several different aspects of the conferencing experience. You can manage users, conferencing components, wholesalers, telephones, timezones, and system parameters through the CRS Front End.

  • Page 60: Cs7000 System Administrator Guide For Release 9.4 January

    Chapter 5: Introducing the Avaya Client Registration Server (CRS) CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 61: Chapter 6: Administering The Avaya Client Registration Server (Crs)

    Chapter 6: Administering the Avaya Client Registration Server (CRS) As an Administrator of the Avaya CS7000 Conferencing Server, you have responsibility for managing several booking and scheduling resources. Operators require these booking and scheduling resources to arrange and supervise the Avaya conferencing system on behalf of their clients.

  • Page 62: Starting The Crs Front End

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Starting the CRS Front End If your environment has several operating CRS servers, Operators can choose which server they want to use. Each CRS server has an associated initialization file. Initialization files have an .ini file extension.
  • Page 63 Avaya support. Figure 27: CRS Front End 6. From the CRS Front End, click System Administration. The system displays the System Administration section of the CRS Front End. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 64: Optional Extras

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Figure 28: System Administration Section Optional Extras The Avaya CS7000 Conferencing Server contains several optional features. The optional features include Managing Wholesalers functionality and Managing Resellers functionality. Your configuration might not contain this functionality.

  • Page 65: Reference Numbers

    Creating a New User Login ● Editing an Existing User Login ● Deleting an Existing User Login ● Login Levels There are three login levels. They are as follows: Operator ● Supervisor ● Administrator ● CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 66: Operator

    Manage existing conference reservations ● An Operator also manages and monitors conference activity with the Avaya Operator Console. For more information on the Avaya Operator Console, see the Avaya CS7000 Operator Guide for Version 9.4. Supervisor Supervisor privileges include all Operator and certain Administrator privileges.

  • Page 67: Creating A New User Login

    Searching for an Owner Name/Wholesaler ● 1. From the Login tab, select User from the View panel. The system displays all user logins. 2. Click New. The system displays New User Login dialog. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 68: Searching For An Owner Name/Wholesaler

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Figure 29: New User Login Dialog Browse Symbol 3. Enter the appropriate details in the editable text fields. 4. From the Level drop down list, select the user type. 5. From the Owner Type drop down list, select the owner type.
  • Page 69 Alternatively, select a Wholesaler and click SELECT. The system displays a CRS Information dialog. Figure 31: CRS Information Dialog 5. Click Yes. The system closes the Wholesaler Search dialog and displays the New Login dialog. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 70: Editing An Existing User Login

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Editing an Existing User Login 1. From the Login tab, select a user and click Edit. The system displays the Edit Login dialog. Figure 32: Edit Login Dialog 2. Edit the appropriate details and click Update.

  • Page 71: Managing System Component Logins

    CRS to validate the participant details. The CRS checks the system database to ensure that log in details are correct and that the data feature is selected for this conference. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 72: System Fields

    Chapter 6: Administering the Avaya Client Registration Server (CRS) System Fields The fields available to system component logins are the same as those attributed to user logins with one exception: Table 7: System Login Field Field Explanation Example Level On the User Login dialog, there are three levels of users. The System three levels are Operator, Supervisor, and Administrator.

  • Page 73: Editing An Existing System Login

    1. From the Login tab, select a system component and click Edit. The system displays the Edit Login dialog. Figure 36: Edit System Login Dialog 2. Edit the appropriate details and click Update. The system updates the details. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 74: Deleting An Existing System Login

    2. Click Delete. The system deletes the system login. Managing Wholesalers Note: This feature is an optional feature in the Avaya CS7000 Conferencing Server. Note: A Wholesaler is the owner of a company or companies. Wholesalers can create... Companies ●...

  • Page 75: Wholesaler Fields

    You can enter a code in this field to associate the 12ab Wholesaler with an external database. String You can enter free text in this field to reconcile the TeleCon Wholesaler with an external database. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 76: Creating New Wholesalers

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Table 8: Wholesaler Fields (continued) Field Description Sample Contact Details Enter the contact details of the Wholesaler in this Teleconference field. Contact details include: Company, 123456, Name ● 789123, tele@company. Telephone ●...
  • Page 77 6. Click OK. The system displays New Wholesaler dialog. 7. Click Save. The system stores the new details in the CRS database. You can view the details from the Wholesaler tab. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 78: Editing Wholesalers

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Editing Wholesalers To edit a wholesaler: 1. From the Wholesaler tab, select a Wholesaler and click Edit. The system displays the Edit Wholesaler dialog. Figure 41: Edit Wholesaler Dialog 2. Edit the appropriate details and click Update.

  • Page 79: Managing Resellers

    The system deletes the Wholesaler. Managing Resellers Note: This feature is an optional feature in the Avaya CS7000 Conferencing Server. Note: The system owner or a Wholesaler can have a network of Resellers. The Resellers are responsible for finding conferencing customers for the Wholesaler. Accordingly, the Wholesaler can create, edit, and delete Resellers.

  • Page 80: Reseller Fields

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Reseller Fields Table 9 describes the Reseller fields. Table 9: Reseller Fields Field Description Sample Reference The system automatically generates a unique 123456789 number when you create a Reseller. Name The name of the Reseller.

  • Page 81: Creating New Resellers

    To create a new Reseller: 1. Select the Resellers tab. The system displays the Resellers tab. Figure 43: Resellers Tab 2. Click New. The system displays the New Reseller dialog. Figure 44: New Reseller Dialog CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 82: Editing Resellers

    Chapter 6: Administering the Avaya Client Registration Server (CRS) 3. Enter the appropriate details in the editable text fields. For more information on selecting a Wholesaler owner, see Searching for an Owner Name/Wholesaler on page 68. 4. Click Contact to enter the contact details.

  • Page 83: Deleting Resellers

    1. From the Reseller tab, select a Reseller and click Delete. The system displays the Delete Reseller dialog Figure 47: Delete Reseller Dialog 2. Click Delete. The system deletes the Reseller. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 84: Managing Sales People

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Managing Sales People Service providers who sell conferencing services can track sales personnel involved in the sale. Tracking sales personnel is especially useful for sales managers. Sales managers can use the data to assess job performance to determine a pay rise or exercise bonus schemes.
  • Page 85 The system displays the New Sales Person dialog. Figure 49: New Sales Person Dialog 3. Enter the appropriate details in the editable text fields and click Save. The system saves the details. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 86: Editing An Existing Sales Contact

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Editing an Existing Sales Contact To edit a sales contact: 1. From the Sales Person tab, select a sales person and click Edit. The system displays the Edit Sales Person dialog.

  • Page 87: Managing Cabinets

    Operators might want to book conferences on several different cabinets. In addition, Operators might want to book conferences on an Avaya CS7000 or an Avaya CS700 or an Avaya CS780 Conferencing Server. Currently, Operators can book conferences on several difference cabinets, as long as they are of the same server type.

  • Page 88: Adding A Cabinet

    Chapter 6: Administering the Avaya Client Registration Server (CRS) The bands.ini file contains a new parameter called AnyCabinetFlag. AnyCabinetFlag is located in the [Make Reservation] section. The possible values for this parameter are as follows: AnyCabinetFlag=0 ● If AnyCabinetFlag=0, the Any Cabinet feature is disabled. The feature is unavailable to the user on the Make Reservation dialog.

  • Page 89: Editing A Cabinet

    The system displays the Edit Cabinet dialog. Figure 54: Edit Cabinet Dialog These fields apply to the Avaya CS700/780 3. Edit the appropriate details and click Update. The system updates the cabinet. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 90: Deleting A Cabinet

    A typical cabinet shelf includes the following hardware cards: ● ● O.I.16 ● DACC ● ● ● ● For more information on system cards, see the Avaya CS7000 Hardware Guide for Version 9.4. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 91: Resource Fields

    For example, if you enter 240, the system makes 240 ports available for a single conference reservation. Extension You can use system ports to increase conferences in size after booking. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 92: Creating A New Resource

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Table 10: Resource Profile (continued) Example Field Description Operator You can reserve a certain number of ports for Operator use only. Toll Free When you select Toll Free, conferences completed using this resource are charged to the conferencing service provider and not the participant.

  • Page 93: Editing An Existing Resource

    1. From the Resource Profile tab, select a resource and click Edit. The system displays the Edit Resource dialog. Figure 58: Edit Resource Dialog 2. Edit the appropriate details and click Update. The system updates the details. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 94: Deleting An Existing Resource

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Deleting an Existing Resource To delete a resource: 1. From the Resource Profile tab, select a resource and click Delete. The system displays the Delete Resource dialog. Figure 59: Delete Resource Dialog 2.

  • Page 95: Managing Ddis

    When you create a new DDI, you enter a description for the DDI. Operators can view this textual description on the Avaya Operator Console, using the View Format menu. When the system sends conference details to conferees, the system displays the telephone number, rather than the DDI.

  • Page 96: Ddi Fields

    Chapter 6: Administering the Avaya Client Registration Server (CRS) DDI Fields Table 11: Resource DDI Field Description Example Reference The system automatically generates this number once the DDI is configured for use with the system. For more information, see Reference Numbers on page 65.
  • Page 97 This field provides a description for the DDI. It is an Crisis Alert optional field. Operators can view the text that you enter in this field. They can chose to display the text on the Avaya Operator Console, using the View Format feature. Owner Type DDIs are System DDIs or Wholesaler DDIs.

  • Page 98: Creating A New Ddi

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Creating a new DDI Note: Each conference type must have an associated dedicated DDI. Note: DDIs must be associated with conference types. This section describes the basic steps to create a new DDI. It also contains two examples: Creating a DDI for a Crisis Alert Conference ●...

  • Page 99: Creating A Ddi For A Crisis Alert Conference

    If you have associated the DDI with a Wholesaler, select the Wholesaler owner type and enter the Wholesaler name in the Owner field. For more information on selecting a Wholesaler, see Searching for an Owner Name/Wholesaler on page 68. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 100: Creating A Ddi For A Meet Me Secure (Cli Validation) Conference

    You can also enter additional details for the DDI such as an alias or a group name. Note: Avaya recommends that you restart the CRS Front End when you add a new Note: resource, such as a DDI. Restarting the system ensures that the displayed details are up-to-date.

  • Page 101: Editing An Existing Ddi

    The system updates the details. Deleting an existing DDI To delete a DDI: 1. From the Resource DDIs tab, select a resource and click Delete. The system displays the Delete DDI dialog. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 102: Managing Telephones

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Figure 64: Delete DDI Dialog 2. Click Delete. The system deletes the DDI. Managing Telephones The Phones tab enables you to associate DDIs and telephone numbers. Telephone numbers are presented to the user on: E-mail notification ●...

  • Page 103: Creating A New Telephone Number

    ● Deleting a Telephone Number ● Creating a New Telephone Number To create a new telephone number: 1. From the System Administration screen, click Phones. The system displays the Phones tab. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 104 Chapter 6: Administering the Avaya Client Registration Server (CRS) Figure 65: Phones Tab 2. Click New. The system displays the New DDIPhone dialog. Figure 66: New DDIPhone Dialog 3. Select a DDI from the DDI drop down list. 4. Enter the telephone number in the Phone Number field.

  • Page 105: Editing A Telephone Number

    The system displays the Delete DDIPhone dialog. Figure 68: Delete DDIPhone Dialog 2. Click Delete to delete the telephone number. The system deletes the telephone number and displays the System Administration screen. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 106: Managing Time Zones

    As a System Administrator, you control the number of time zones in the conferencing system. Avaya recommends that you focus on the time zones that the users are likely to require. For more information about time zones, see the Avaya CS7000 Operator Guide for Version 9.4.

  • Page 107: Creating A New Time Zone

    1. From the System Administration screen, click Time Zones. The system displays the Time Zone tab. Figure 69: Time Zones Tab 2. Click New. The system displays the New Time Zone dialog. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 108: Editing An Existing Time Zone

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Figure 70: New Time Zone Dialog 3. From the Resource drop down list, select the appropriate resource number. 4. Enter the following details: An appropriate time zone name. For example, EST + Daylight Savings Time (DST) ●...

  • Page 109: Deleting An Existing Time Zone

    This section describes how to add and delete multisite servers. It also describes the multisite fields. It contains the following sections: Multisite Server Fields ● Configuring a new multisite server ● Deleting an existing multisite server ● CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 110: Multisite Server Fields

    Chapter 6: Administering the Avaya Client Registration Server (CRS) Multisite Server Fields Table 13: Servers Field Description Example Client Ref The system automatically generates a reference number when you create a new server entry. Server The recognized computer name that the system uses...

  • Page 111: Deleting An Existing Multisite Server

    1. From the Servers property sheet, select an existing server and click Delete. The system displays the Delete Server dialog. Figure 75: Delete Server Dialog 2. Click Delete. The system deletes the server. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 112 Chapter 6: Administering the Avaya Client Registration Server (CRS) CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 113: Chapter 7: Configuring System Parameters

    Extending Conference Duration ● Setting the First ‘Conference Ending’ Time Warning ● Setting the Maximum Number of Conferences ● Booking Perpetual Conferences ● Setting Conference Reception Size ● Setting Account Number Length ● CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 114: Redistributing System Resources Across Multiple Shelves

    The system bills for cancelled conferences if conference organizers cancel too late. If conference organizers cancel before the time frame stated in the FreeIfCancelledXminutesBefore parameter, the system does not bill them. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 115: Previewing Conference Details Before It Starts

    The ListConferenceActivityXMinutesBefore parameter controls the preview time. The Avaya Operator Console uses this parameter to operate the Schedule Open functionality. Retaining a Conference After Completion After conference completion, the system retain the conference details for a configurable period of time.

  • Page 116: Setting The Maximum Participant/Port Availability

    You can restrict the number of participants in conferences to ensure that the conference load does not overstretch system resources. If a system has 240 ports, Avaya recommends that you set the MaxConferenceSize parameter to a percentage of the overall ports available.

  • Page 117: Setting The Minimum Duration

    116 For information about the first system message, see Setting the First ‘Conference Ending’ Time Warning on page 119. The OneMinuteWarningXMinutesBefore parameter controls the timing of the second warning message. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 118: Opening A Conference Before It Is Due To Begin

    Setting the Maximum Number of Extension Periods on page 116. The warning message plays before the end of the conference. For more information, see Setting the First ‘Conference Ending’ Time Warning on page 119. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 119: Setting The First 'Conference Ending' Time Warning

    The system sends the e-mail using SMTP protocols. A possible cause for a rebooking failure is if the PIN is allocated to another conference. The system also displays rebooking failures on the CRS Front End. See the Avaya CS7000 Operator Guide for Version 9.4 for an example e-mail.
  • Page 120 0 on a customer site. PerpCSendEmails Specifies whether the system should send e-mails for perpetual conference extensions. The system does not use the remaining parameters if you set this parameter to 0. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 121: Setting Conference Reception Size

    You can set the maximum size of conference reception. The parameter MaxReceptionConferenceId controls the maximum size of conference reception. If MaxReceptionConferenceId=120, the system does not accept more than 120 people in conference reception at any one time. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 122: Setting Account Number Length

    Setting Account Number Length Each client has an account number in the BSRes 2 database. The system generates the account number when Operators add a new client. For more information, see the Avaya CS7000 Operator Guide for Version 9.4. The AccountNumberLength parameter controls the length of the account number.

  • Page 123: Enabling Pin Entry

    Each field listed in Ctrlpos.ini has the following attributes: Table 16: Field Syntax Field Description Attribute A unique field identification number. nChecked A reference to the field identification number. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 124 2. Open Ctrlpos.ini. Ctrlpos.ini is located in C:\WINNT. The configurable field names are listed. Note: The system sets fields that are specific to Avaya CS700/CS780 to invisible, using Note: the bVisible attribute. 3. Update field names as required. For example, change the caption Auto Code to Auto PIN.

  • Page 125: Chapter 8: Configuring The Bands Initialization File

    System Parameters dialog and several Bands.ini files. Figure 76: System Parameters Dialog and a Number of Bands.ini Files Settings apply to all clients Settings apply to individual Operator Bands.ini Bands.ini Bands.ini CRS Front End Parameters CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 126 Operator. For example, if an Operator views a barchart, the system displays this graph type the next time the Operator accesses graph functionality. The default value is 7*. 1 of 10 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 127 The week starts on a Monday. MinimumFilter The minimum number of characters that the Operator 7000/7X0 must type into the Company Filter prior to requesting a Company List. 2 of 10 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 128 You can display CRS Front End icons in two different 7000/7X0 sizes. The possible values are as follows: LargeIcons=0* ● The system displays small icons. ● LargeIcons=1 The system displays large icons. 3 of 10 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 129 The possible values are as follows: ● CheckPINSize=0 CheckPINSize is disabled. ● CheckPINSize=1* CheckPINSize is enabled. You can configure PIN length on the System Parameters section in the CRS Front End. 4 of 10 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 130 If you disable ReadOnlyCompanies, Operators can add new companies, update existing companies, and delete companies. The possible values are as follows: ● ReadOnlyCompanies=0* ReadOnlyCompanies is disabled. ReadOnlyCompanies=1 ● ReadOnlyCompanies is enabled. 5 of 10 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 131 You can view the functioning of ExpandRepeats in the trace log. Avaya added the ExpandRepeats parameter to enable the CRS Front End to successfully work in multiple time zones. 6 of 10 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 132 The X and Y coordinates of the Conferee Selection 7000/7X0 dialog. For example: 0,0,480,640* CallerRect The X and Y coordinates of the Caller dialog. For 7000/7X0 example: 0,0,480,640* 7 of 10 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 133 The system automatically refreshes global conference 7000/7X0 data (GCD) if you enable the GCDUTimer parameter. You can disable GCDUTimer to reduce network traffic. GCDUTimer=0 GCDUTimer is disabled. GCDUTimer=1 GCDUTimer is enabled. 8 of 10 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 134 The system displays an error message if it encounters such a field. The possible values are: ● StrictValidation=0 StrictValidation is disabled. StrictValidation=1 ● StrictValidation is enabled. 9 of 10 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 135 0,100:1,100:2,100:3,100:4,100:8,100:9,10 0:10,100:11,100:28,100:21,100:36,100:37, 100:38,100:34,100:35,100:16,100:17,100:2 9,100: This parameter has no value in a Avaya CS7000 environment. You can configure column display on the CRS Front End. The system saves column display settings in the Bands.ini file when users exit the CRS Front End.
  • Page 136 2=Meet Me Operator Assisted 3=Management Alert And so on. Not all customers have the full range of conference types. Certain conference types are specific to the Avaya CS7X0 or the CS7000. Example values for Type are as follows: Type=1* Type=2 Type=3 And so on.
  • Page 137 Reservation dialog, by default. If you disable the Recording parameter, the system does not select the Recording check box, by default. The possible values are: ● Recording=0* Recording is disabled. Recording=1 ● Recording is enabled. 3 of 5 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 138 If you disable the TollFree parameter, the system does not select the TollFree check box, by default. The possible values are: TollFree=0* TollFree is disabled. TollFree=1 TollFree is enabled. 4 of 5 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 139 Cabinet list on the Make Reservation dialog. AnyCabinetFlag=2 ● If AnyCabinetFlag=2, the system displays the Any Cabinet option at the bottom of the Cabinet list on the Make Reservation dialog. 5 of 5 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 140 PlacedInConference specifies a default 7000 message that the system plays while the system places each participant into their conference. Each message has a numeric identifier. For example: PlacedInConference=293* 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 141 WaitForModerator specifies a default Wait For Moderator message. Each message has a numeric identifier. For example: WaitForModerator=298* MultiLanguage By default, the Avaya CS7000 contains many 7000 messages. You can record alternative custom messages. You can associate alternative messages with the new DDI. If you select MultiLanguage=1, the system makes additional messages available for selection.
  • Page 142 If you disable the LeavingTone parameter, the system does not select the LeavingTone check boxcheck box, by default. The possible values are: LeavingTone=0* ● LeavingTone is disabled. ● LeavingTone=1 LeavingTone is enabled. 1 of 6 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 143 Options dialog, by default. If you disable the WaitForModerator parameter, the system does not select the WaitForModerator check box, by default. The possible values are: WaitForModerator=0 ● WaitForModerator is disabled. WaitForModerator=1* ● WaitForModerator is enabled. 2 of 6 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 144 StreamPlayback check box, by default. The possible values are: ● StreamPlayback=0* StreamPlayback is disabled. StreamPlayback=1 ● StreamPlayback is enabled. StreamPlayback is an optional setting. Locked This parameter is for future use. 3 of 6 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 145 Name On Entry parameter, the system does not select the NameOnEntry check box, by default. The possible values are: ● NameOnEntry=0* NameOnEntry is disabled. NameOnEntry=1 ● NameOnEntry is enabled. 4 of 6 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 146 NameOnExit=1 ● NameOnExit is enabled. MusicSrc MusicSrc specifies the hold music that the system plays prior to the arrival of the Moderator. For example: MusicSrc=1 By default, MusicSrc=0*. 5 of 6 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 147 The possible values are: NRP=0 ● NRP is disabled. NRP=1* ● NRP is enabled. PinMode PinMode adds extra security to the conference. By default, PinMode=1*. 6 of 6 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 148 ODBC Text Setup dialog. ConfFullRptFile=ConfDataFullReport.r These files are report templates. Avaya recommends that you do no edit these ConfShortRptFile=ConfDataShortRepo parameters. rt.rpt ConfDataFile=ConfData.csv These files operate on both the Avaya CS7000 and CS7X0. ReservFullRptFile=ReservDataFullRep ort.rpt ReservShortRptFile=ReservDataShort Report.rpt ReservDataFile=ReservData.csv CompanyRptFile=CompanyReport.rpt ClientShortRptFile=ClientShortReport.r ClientFullRptFile=ClientFullReport.rpt...

  • Page 149: Chapter 9: Introducing The Avaya Notification Subsystem

    Chapter 9: Introducing the Avaya Notification Subsystem The Avaya Notifications Subsystem program is a fax, e-mail, and SMS broadcast provider for the Avaya CS7000 conferencing system. This chapter describes the Notifications Subsystem. It contains the following sections: Introduction ● Operating the Notifications Subsystem ●...

  • Page 150: Starting The Application

    In the case of e-mail requests, the system does not produce this report. The Avaya Billing System can then process this information. Invitation notifications are optionally sent to participants when a conference is booked.

  • Page 151: Operating The Notifications Subsystem

    However, the Notifications Subsystem is highly efficient at preparing e-mails for the e-mail transport provider. Note: The Avaya Web Portal application supports attachment functionality. Similar Note: applications might not have an attachment feature. CS7000 System Administrator Guide for Release 9.4...

  • Page 152: E-Mail Attachments

    ● E-mail Attachments The Notifications Subsystem attaches files to reminder type notifications when conference users make bookings on the Web. For more information, see the Avaya Web Portal documentation. Attachment settings The system has two specific settings for attachments. These settings are in the Configuration menu.
  • Page 153 The system has tagged a fax request for deletion. SUSPEND The system could not send a fax and is waiting to send the fax again. This state relates to Windows NT internal Fax resources only. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 154: Setting The Application Font

    Check Regular or combinations of other styles. Size Choose a size form the drop-down list or enter a value in the field. Sample This field displays a sample of the selected font style. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 155: Setting The Application Font

    Select to delete fax and e-mail in Send fail mode. REPORTOK Select to delete fax and e-mail in Report OK mode. REPORTFAIL Select to delete fax and e-mail in Report Fail mode. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 156: Deleting Items By State

    1. At the Edit menu, select Delete items by State. The system displays the Delete Items dialog. Figure 78: Delete Items Dialog 2. Select or deselect the items as necessary. 3. Click OK. The system deletes the selected items. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 157: Adding Faxes And E-Mails

    The participant details of the receiver of the notification ● The conference details ● Table 27: The Add New Item Dialog Item Description E-mail Select to send an e-mail. Select to send a fax. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 158 The caller is played a message in bell mode. (Operator Assisted). 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 159 Enter the destination name. Table 32: Conference Details Group Item Description Name Enter the Conference name. Reference Enter the Conference reference number. Enter the DDI number of the conference. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 160: Setting The Information Logs

    Setting the Information Logs Information logs record and display events associated with the various servers. 1. At the Logging menu, select Filter. The system displays the Filter Logging dialog. Figure 80: Filter Logging Dialog CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 161 Select to receive warning messages for the fax and e-mail transmissions. Error Select to receive error messages for the fax and e-mail transmissions. Serious (MsgBox) Select to log and display critical errors only. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 162: Testing The Notifications Subsystem

    1. At the Settings menu, select Process Flags. The system displays the Process dialog. Figure 81: Process Selected Item States Dialog 2. Select or deselect the items as necessary. 3. Click OK. The system sets the process flags. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 163: Logging Details

    SERIOUS Log critical errors only. Date Displays the Log date. Time Displays the Log time. Source Reservation Server. DOS Fax Server. Windows NT Fax Resource. Other. FREE TEXT Displays Log details. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 164: Viewing Logging Details

    You do not have to wait for the entire recording to be downloaded. The Notifications Subsystem polls the CRS for recordings. When it locates recordings, it converts them from wave format to the RealNetworks format. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 165: Streaming Requirements

    CWList must be set up and configured. ● Note: CWList is a Avaya application. It is a Java servlet that runs on a Web server. It Note: enables Internet users to listen to conference recordings over the Web. Web users must have a version of Real Player installed.
  • Page 166 This section shows the alert message template. It also contains a description of the Alerts section in Broadcast.ini. This section contains the following sections: Notification Alert Message ● Excerpt from Broadcast.ini Alerts Settings ● Alerts Section ● CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 167: Notification Alert Message

    Broadcast Alert conferences flagged for broadcast Console Send alerts to Operator Consoles FrontEnd Send alerts to Front Ends, such as the CRS Front End WorkingDir Path where alerts.txt template is stored CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 168: Alerts Section

    Chapter 9: Introducing the Avaya Notification Subsystem Alerts Section Active=N TimeWindow=10 ConfTypes=2,4 QandA=N Broadcast=N Console=Y FrontEnd=N WorkingDir=\Avaya\broadcast\Booking CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 169: Chapter 10: Configuring The Avaya Notifications Subsystem

    TCP IP address of MS DOS fax server PC i.e. 192.168.1.17. If this entry is blank the thread that talks to the fax server will not be started. FaxServerPortID Port ID of fax server i.e. 9090 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 170 If ‘Active’ is not set to ‘Y’ no e-mails will be sent. Profile Name of e-mail transport provider i.e. MS Outlook. Password Password to get access to e-mail transport provider. WorkingDir Internal working directory and position of e-mail template files. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 171 2-character year i.e. 04. YYYY 4-character year i.e. 2004. Numeric month with no leading zeros i.e. 11 or 4. Numeric month with leading zeros i.e. 11 or 04. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 172 AM/PM clock i.e. 10:30pm 1:00am. AM/PM clock i.e. 10:30p 1:00a. TTTT Standard 24-hour clock with colon separators and no seconds. TTTTTT Standard 24-hour clock with colon separators and seconds. 2 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 173 Directory to build raw reports (for testing only) (C:\Avaya\Broadcast\PCReport\Output) Table 47: Templates Format Description SysOwner1 Generic Alias used on all templates (SAMPLE NOTIFICATION) SysOwner2 Generic Alias used on all templates (Sample Company) CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 174: Example Sms Settings

    XMSDir This is the folder used by the XMS application to store conference recordings. The computer containing the scheduler must have visibility of the XMS computer. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 175 When set to Y, the Notifications Subsystem copies the wave file into the web directory without conversion to the RealNetworks format. Microsoft Media-Player may be used as an alternative to stream the audio files. 2 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 176: File Templates

    Template Name Examples ● Alias Controls ● Alias Control Character * and + ● Attendance Reports ● Fax Command Controls ● Character Attribute Commands ● Character Code Commands ● E-mail Command Controls ● CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 177: File Template Naming Conventions

    Start of Template Name Meet Me Direct Dial in conference. Meet Me Operator Dial in handled by the Operator. Assisted Meet Me Toll Free Dial in for free. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 178: Template Name Examples

    Recording Repeat Booking Template Name Examples Table 53: Template Example Action Conference Repeat Recordin Template Used Type Bookin Confirmation Meet Me Direct CONFIRM1AA.TXT Remind Meet Me Direct REMIND1BA.TXT 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 179: Alias Controls

    18 July 2004. CEDATE Conference end date. CMTIME Conference booking modified 23:50. time. CMDATE Conference booking modified 21 August 2004. time. FTEXT Comment box/Free text. Visit us at inventus www.inventus.com. 1 of 3 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 180 Conference local date. 18 July 2004. PPIN Participant PIN. 654654. CLNUM Client reference. 665544. CMNUM Company reference. 998877. CLACC Client a/c. 9955112233. DDIS Number of DDIs associated with conference 2 of 3 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 181 1. DDIs and DPIN are optional if Multiple DDIs=Y in Broadcast.ini. 2. DDILOCAL and DDIPHONE are optional if multiple DDIPhones=Y in Broadcast.ini. 3. The following fields are declared in the Broadcast.ini. They are system-wide and do not varying per booking. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 182: File Template Example

    Example PSDATE Participant entry date. 18 November 2004. PSTIME Participant entry time. 9:10pm. PEDATE Participant exit date. 18 November 2004. PETIME Participant exit time. 9:10pm. Participant CLI/ANI 1234564. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 183 Booking operator name. Mary White. CMNAME Company name. Company.com. CLINAME Client name. Sales Dept. CFREES Number of participants. DATE Current date. 21 November 2004. TIME Current time. 10.58. 2 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 184: Fax Command Controls

    This commands specifies that the text following will start on a new page. Table 58: Box Fax Command Description Usage {BOX/Box type/ID1 [, ID2][, ID3].} Meaning Draw box on fax document. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 185 This command specifies the end of a text box. The bottom right corner is at the character ‘}‘ at the end of the BEND command. Example See the above BOX example. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 186: Character Attribute Commands

    A numeric value representing the Modified ASCII 437 character set may be placed between square brackets i.e. [204] etc the numbers are taken to be values over 200 and values below 200 will have 200 added to them. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 187: E-Mail Command Controls

    CONFS or DDIS. ALIAS values may also be included in the content arguement. Use the asterisk character to take the ALIAS values from the related list rather than taking one static value. Example {REPEAT/DDIS/*Dial-in Number:[DDI*][DDILOCAL*][DDIPHONE*]} CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 188 The forward slash character should not be included in any of the above content Note: arguments. If URLs are required, they should be configured in Broadcast.ini and the ALIAS items SysURL1 or SysURL2 should be used to reference them. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 189: Example Confirm1Aa.txt Template

    [CNUM] * Participants: [CFREES] * Dial in code: [DDI] * Pin access code: [PIN] * Web console: www.avaya.com ------------------------------------------ Thank you for choosing Avaya WorldConference. [UNAME] Asst Telecom Service Executive [FTEXT] CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 190: Customizing Fax Logos

    Monochrome graphics may also embedded using the IMPORT keyword in a fax template. For example: Template: CONFIRM1AA.TXT {IMPORT/HeadingLogo.tif} {BOX/1/1,2} To:[NAME] Scheduled by Inventus [CMNAME] On: [DATE] At: [TIME] CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 191 Per-minute rates are based upon the use of either toll-free 800 or tolled telephone numbers. {BEND/4} {IMPORT/Advertisment.tif} The above fax template contains two tiff graphics HeadingLogo.tif & advertisment.tif. Figure 85: Sample Logo CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 192: Tiff Files

    A conversion tool needs to be used to create the TIFF file. The Tiffkit package from Informatik supplies a conversion application (reformat) to do this. There may be other applications that do similar but this was recommended by Dialogic. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 193: Converting Bmp To Tiff/F Using Tiffkit

    4. Select Source directory of bitmap file. 5. Select Destination directory of TIFF file. 6. Set Graphics format to TIF. 7. Set Tiff compression to TIFF/F (Dialogic). 8. Select bitmap file from Files. 9. Click OK. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 194: Applying Tiff/F To Fax Template

    2. Add or amend IMPORT command in each template to use your file name i.e. {IMPORT/ MYLOGO.TIF} Note: Test Faxes by using the Insert option in the Notifications Subsystem application. Note: Note: Tifkit and other tools can be downloaded from http://www.informatik.com Note: CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 195: Chapter 11: Troubleshooting The Avaya Notifications Subsystem

    ● Use the Import command to retrieve the name of the tiff file. Check the fax folder, for ● example, C:\Avaya\broadcast\booking\fax, to determine if the tiff file is present. Ensure that the telephone system is operating normally. ● Connect the analog handset to the line and check for a dial tone. If no dial can be heard, ●...

  • Page 196: Import Utility Problems

    Increase the Broadcast.ini setting “ResServerRequestInterval” and restart the Notifications ● Subsystem before doing a client import. Import a maximum of 1000 records on any single occasion. ● CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 197: Chapter 12: Administering The Avaya Template Editor

    This chapter describes how to operate the Avaya Template Editor application. You can use the Avaya Template Editor to create and edit a set of fax and e-mail templates. The Avaya Notifications Subsystem uses these templates for conference notifications. The Avaya Template Editor automates an otherwise manual task.

  • Page 198: Installing Avaya Template Editor

    The system displays the User Information dialog. Figure 89: User Information Dialog 3. Enter user information. This step is an optional step. 4. Click Next. The system displays the Choose Destination Loction dialog. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 199 The system displays the Select Program Folder dialog. Figure 91: Select Program Folder Dialog 6. Click Next. The system displays the Setup Complete dialog. Figure 92: Setup Complete Dialog 7. Click Finish to complete the installation. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 200: Editing An Existing Set Of Templates

    Figure 93: New Templates Project Dialog 2. Click Next. The system displays the Open dialog. Figure 94: Open Dialog 3. Browse for an existing template file. 4. Click Open. The system displays the Project Settings dialog. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 201 Editing an Existing Set of Templates Figure 95: Project Settings Dialog 5. Click Next. The system displays the Units Editor dialog. Figure 96: Units Editor Dialog CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 202 The nine digits on your keypad helps you to control the playback: 1. Slow Rewind 2. Increase volume 3. Slow Forward 4. Medium Rewind 5. Pause On/Off 6. Medium Forward 7. Fast Rewind 8. Increase Volume 9. Fast Forward CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 203 7. Once editing is complete, click Next. The system displays the Files Selector dialog. Figure 98: Files Selector Dialog 8. Click Finish. The system displays the Confirmation dialog. The Confirmation dialog confirms the number of generated templates. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 204: Editing A Single Template

    9. Click OK to close Avaya Template Editor. Editing a Single Template In addition to editing a set of templates, single templates can also be modified using Avaya Template Editor. 1. Display the File Selector dialog. For more information, see...
  • Page 205 5. Click OK. 6. Click Finish. The system displays the Confirmation dialog. The Confirmation dialog confirms the number of generated templates. Figure 102: Confirmation Dialog 7. Click OK to close Avaya Template Editor. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 206: Cs7000 System Administrator Guide For Release 9.4 January

    Chapter 12: Administering the Avaya Template Editor CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 207: Chapter 13: Administering The Avaya Sms Controller

    Notifications Subsystem installation. For more information on the Notifications Subsystem, see Configuring the Avaya Notifications Subsystem on page 169. Figure 103 displays the relationship between client applications and the SMSC/modem. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 208 The Message column displays the text message contents. In addition, the system uses icons to represent the progress of the SMS. Figure 104 displays the SMS Controller GUI. Table 65 displays the SMS progress icons. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 209 The SMS is being processed and the SMSC is notified. The SMS is successfully sent. The SMS has failed to reach its destination. Completed SMS requests are cleared from the SMS Controller GUI every 30 seconds. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 210: Installing The Sms Controller

    To test: 1. Run the SMS Controller. 2. Run the SMS Test Client. 3. On the SMS Test Client GUI, enter the SMS Controller details. The system displays the SMSTestClient dialog. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 211 5. On the SMS Test Client, enter some text in the SMS field. 6. Enter a destination mobile telephone number. Usually, the SMSC requires an international code prefix. 7. Click Send SMS. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 212: Configuring The Sms Controller

    This code is from a sample SMSController.ini file: [Server] Port=4500 Client=8 ;Protocol=SMPP Protocol=HTTP [SMPP] Logon=user1 Password=password Sender=35312073616 IP=10.121.10.125 Port=8901 ton=1 npi=1 [HTTP] URLA=http://213.190.141.35/bulksms/SendSMSClient.asp?UID=avaya& URLB=Pswd=spect2003&Phone=[DEST]&OperatorID=2&SMS=[MESG] [Logging] Path=Logs Level=2 Alert=4 Size=10 Days=3 Flush=1 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 213 SMPP settings. Logon SMSC account name Password SMSC security password IP server address of SMSC Port Listening port of SMSC Set to 0 Set to 0 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 214 The number of days for which logs are stored. When this number is reached, the log files are automatically deleted. Flush If Flush is set to 1, the logging data is not buffered. 2 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 215: An Example Of A Logging File

    14/07/04 15:39:54 N/ADebugSMPP_SUBMIT_SM_RESP Message ID - 84 14/07/04 15:39:54 1NoticeClient [0] disconneted Note: If a previous application crash is detected on start up, the last logging file is stored Note: in a subfolder called fatal. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 216 Chapter 13: Administering the Avaya SMS Controller CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 217: Chapter 14: Administering The Avaya Data Services Client Application (Dsca)

    Chapter 14: Administering the Avaya Data Services Client Application (DSCA) This chapter describes how the Avaya Client Registration Server (CRS) is integrated with an enterprise directory server. It contains the following sections: Directory Services Client Application ● How it Works ●...

  • Page 218: How It Works

    Chapter 14: Administering the Avaya Data Services Client Application (DSCA) Figure 106: DSCA Main Interface The Configuration dialog can be accessed via the Edit menu. Next Process Time Last Process Time Some Historical Status Details How it Works The Lightweight Directory Access Protocol (LDAP) is the standard for accessing directory servers.

  • Page 219: Installing Dsca

    Installing DSCA 1. Run setup.exe. 2. Locate and run the SQL script, DSCA.sql. The DSCA.sql script is stored in the SQL folder in, C:\avaya\dsca. Ensure that you choose the correct databse (BSRes2). Note: The Auto-Demand profile is now part of the standard BSRes2 database setup.
  • Page 220 Chapter 14: Administering the Avaya Data Services Client Application (DSCA) Figure 108: Configuration Dialog The following parameters need to be configured: Table 68: Configuration Parameters Parameter Description Host Value The IP address of the directory server Port The port number. The default value is 389.
  • Page 221 DisabledMask When masked with the UserAccountControl attribute, DisabledMask results in the disabled status of the account. LDapCompanyRef Specifies the company reference number. 2 of 4 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 222 Chapter 14: Administering the Avaya Data Services Client Application (DSCA) Table 68: Configuration Parameters (continued) Parameter Description Setting for Demand Conference Size: Specifies the conference size Profile Recording On: Indicates whether recording is on or off. The possible values are 1/0.

  • Page 223: Modes Of Operation

    DSCA. Ensure that the language and Moderator settings are consistent. Modes of Operation There are two modes of operation: Non-Cached ● Cached ● Cached mode is described here for illustrative purposes. Cached mode is supported in future releases only. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 224: Non-Cached Mode

    Chapter 14: Administering the Avaya Data Services Client Application (DSCA) Non-Cached Mode The steps involved in this mode of operation are: Retrieval of registration details from the directory server ● Synchronization of CRS registration details ● Using the search criteria configured in the current profile, the DSCA queries the directory server for entries that meet the specified criteria.

  • Page 225: User Data

    An example of a telephone number with brackets: (353) 895623 An example of a telephone number without brackets: 353 8598623 The DSCA has configurable mappings for CRS fields to LDAP attributes, as attributes are not standard across LDAP schemas. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 226: Demand Profile Creation

    Chapter 14: Administering the Avaya Data Services Client Application (DSCA) LDAP attributes to query for name, telephone number, and e-mail searches are set in the DSCP properties file. This file is in the same format as the Web Portal LDAP. It might possibly be shared out to the Web Portal LDAP, to minimize configuration.

  • Page 227: Chapter 15: Administering The Avaya Operator Console

    ● Configuring Log on Types In the Avaya CS7000 Operator Console, there are two log on types. Operators can log on as System Owners or as Wholesalers. A Wholesaler is the owner of a company or companies. Wholesalers can create...

  • Page 228: Disconnecting A Remote Operator Line

    Operator Console. Regular Operators and Supervisors cannot disconnect remote Operators. To disconnect a remote Operator: 1. Select a remote Operator. Figure 109: Selection of Operator 2. Select the Delete icon. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 229: Enabling The Display Of A Substitute Cli For Operator Originated Calls

    Enabling the Display of a Substitute CLI for Operator Originated Calls Figure 110: Delete Icon The Operator Console displays an Avaya Console information dialog. Figure 111: Avaya Console Information Dialog 3. Click Yes. The Operator Console disconnects the Operator. Enabling the Display of a Substitute CLI for Operator Originated Calls When Operators make outgoing calls, they can enable a substitute calling line identifier (CLI).

  • Page 230: Configuring Multiple Operator Consoles On One Workstation

    The desktop shortcuts must contain the full path of the Operator exe and the appropriate Operator ini file. The paths must be separated by a single space. For example: C:\C2000con\Operator.exe C:\C2000con\bridge 1\Operator.ini Figure 113 shows an example shortcut properties dialog. CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 231 Figure 114: Directory Structure for Multiple Operator Consoles with Different Bridge Versions C2000con Version 1 Operator.exe Operator.ini Version 2 Operator.exe Operator.ini Operator.exe Version 3 Operator.ini Directory Structure for Multiple Operator Consoles CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 232: Customizing The Operator Console Title Bar

    Holler groups to a conference, rather than manually connecting individual circuits. There are two main steps involved in the configuration of Hoot and Holler groups: Defining Hoot and Holler Groups ● Configuring the Operator ini File ● CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 233: Defining Hoot And Holler Groups

    Administrators must ensure that the exact same file is on all Operator workstations. For this reason, Avaya recommend the centralized option. Figure 115 displays a sample Hoot and Holler definition file. Figure 115: Hoot and Holler Groups CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 234: Configuring The Operator Ini File

    Usually, the holding conference has a conference ID of 1. A conference ID of 1 ensures consistency with an existing configuration of a customer. It might be necessary to reconfigure other elements in the Avaya CS7000 system. Figure 116 displays a section from a sample Operator ini file.

  • Page 235: Operator Options

    The group of circuits is moved to the conference that is holding unconnected Hoot and Holler groups. This conference is the conference defined in HHParkID. Figure 118 displays the Disconnect Preset menu option. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 236: New Fields

    Operator Console to the Conference Management Server (CMS). This message is sent using the Avaya protocol, CCL. When an Operator disconnects a group of circuits, a CCL message is also sent from the Operator Console to the CMS. When a group of circuits is connected to a conference, the Operator Console displays the letter P in the Conference title bar.
  • Page 237 Figure 120: Conference List Fields To view the Hoot and Holler Group information fields in the conference list and in the conference title bar, the view formats must be configured. For more information, see the Avaya CS7000 Operator Guide for Version 9.4.

  • Page 238: Customizing Operator Icons

    A parameter in C2000con.ini, called OpUserPath, specifies a network folder, such as Icons in Figure 121 . Within the specified folder, the Avaya CS7000 System Administrator must create several folders. The name of each of these folders must correspond with an Operator name.
  • Page 239 OpUserPath must specify the base folder. For more information, see Figure 121. 6. Save and close the C2000con.ini file. Figure 122 displays customized icons. Figure 122: Conference Dialog with Customized Icon CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 240 Chapter 15: Administering the Avaya Operator Console CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 241: Chapter 16: Administering The Avaya Client Registration Server (Crs) Server Interface

    Server on the Windows desktop. Alternatively, select Registration Server from the Program Start Up menu. Note: The Client Registration Server application is auto-started and can only be Note: stopped after the BSMon Program has stopped. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 242: Server Menu

    Chapter 16: Administering the Avaya Client Registration Server (CRS) server interface Figure 123: Client Registration Server This section introduces the CRS, server side. It contains the following sections: Server Menu ● Trace menu ● Help Menu ● Editing Trace Settings ●...

  • Page 243: Trace Menu

    Editing Trace Settings This feature helps the user to specify what events to log to the log file. 1. At the Trace menu, select Settings to display the Trace Settings dialog. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 244: General Group

    Chapter 16: Administering the Avaya Client Registration Server (CRS) server interface Figure 124: Trace Setting Dialog General Group Table 73: General Group Item Description Timing Shows the time of incoming and outgoing messages. Channel Header Information about the sender of the message.

  • Page 245: Applications Group

    Monitors communication between the Client Registration Server and EMS/XMS. Front End Monitors communication between the Client Registration Server and the CRS Front End. Registration Server CRS generated messages are monitored. 1 of 2 CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 246: Viewing Logging Details

    FREE TEXT Displays Log details Viewing Registration Server Details 1. At the Help menu, select About CRS server. Avaya CS7000 displays the About CRS server screen. 2. Click OK to return to the Client Registration Server screen. CS7000 System Administrator Guide for Release 9.4...

  • Page 247: Shutting Down The Application

    Configuration Shutting Down the Application At the Server menu, select Exit. Avaya CS7000 displays the CRS server screen Figure 125: CRS server Dialog Table 76: ReServer Dialog Do this Exit the application Click Yes. Return to the Client Registration Server Screen Click No.

  • Page 248: General

    Chapter 16: Administering the Avaya Client Registration Server (CRS) server interface General Table 77: General Configuration Item Description ContinueOnRepeatFailure=1 Specifies if repeat bookings are to stop on first conference failure SaveSettings=1 Specifies if changes are to be saved on exiting...

  • Page 249: Comms

    Table 80: Protocol Configuration Item Description ConsoleMajor=-1 Specifies the major version number of the console with which the server communicates. ConsoleMinor=-1 Specifies the minor version number of the console with which the server communicates. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 250: Logsettings

    Chapter 16: Administering the Avaya Client Registration Server (CRS) server interface LogSettings Table 81: LogSettings Configuration Item Description Archives=5 The number of log files that are written before a process of overwriting occurs. GenFlags=127 Retains the general trace settings. AppFlags=1023 Retains the application trace settings.

  • Page 251: Chapter 17: Administering The Avaya Demand Pin Master

    The Demand PIN Master manages resources efficiently by ensuring that conferences are not opened unneccessarily. Conferences do not open automatically at the scheduled start time. They open only if the first participant enters a valid PIN. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 252: Client Pin Validation

    External client PIN validation involves sending a query to an external database located outside the Avaya CS7000 system, for example, a credit card number database. There are several plug-in products, which can extend the Demand PIN Master to incorporate client data in the client PIN validation process.

  • Page 253: Cli Identification

    CLI Identification CLI Identification Prior to this release, Avaya distributed two versions of the Demand PIN Master. One version contained the standard DPM settings. The second version controlled the functionality of alert conferences. In this release, Avaya has merged the standard DPM with the Alerts DPM.

  • Page 254: Locked And Full Conferences

    Chapter 17: Administering the Avaya Demand PIN Master Branding means that the number you use to dial the conferencing system determines the greeting message that is played. Greeting messages can be customized to specific customer requirements. The system also uses DDIs to determine how your call is processed. DDI is known as Dialed Number Identification Service (DNIS) in the United States of America.

  • Page 255: Extending Conferences

    The Demand PIN Master ensures that its system clock is synchronized with the CRS system clock by regularly polling the CRS computer. Time synchronization between the Demand PIN Master and the CMS ensures that conference start and end times are the same in both systems. CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 256: Demand.ini

    PMPromptMsg The PIN Master prompt message is the message that is played to a caller to elicit their conference PIN. Avaya CS7000 contains several prerecorded messages. New messages can also be recorded. All messages are associated with a numeric identifier.
  • Page 257 If PMDO_F=2, all calls to full conferences are routed to reception. Disable PMDisconnect for this condition. It defaults to 2 of 5 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 258 Chapter 17: Administering the Avaya Demand PIN Master Table 83: Settings (continued) Parameter Example Value PMDO_P PMDO_P is ignored if PIN Master Disconnect (PMDisconnect) is set to zero. If PIN Master Disconnect is set to non zero, PMDO_P is used.
  • Page 259 For example, if you set EmptyAtOneSecs to 180, the demand conference closes if only a single conferee remains for a period of three minutes. By default, the EmptyAtOneSecs parameter is disabled: EmptyAtOneSecs=0 4 of 5 CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 260 Example Value DialTimeoutSecs The parameter, DialTimeoutSecs, was active in previous releases but in recent times, Avaya made it obsolete. Avaya has now reinstated DialTimeoutSecs. It now ensures that if users do not answer calls that the system starts, the system disconnects these calls.

  • Page 261: Index

    ..........Ctrlpos.ini CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 262 ..... sync.fil ....sysparm.fil CS7000 System Administrator Guide for Release 9.4 January 2006...
  • Page 263 ....ZeroStartPIN ....system status fields CS7000 System Administrator Guide for Release 9.4 January 2006...

  • Page 264: Cs7000 System Administrator Guide For Release 9.4 January

    Index CS7000 System Administrator Guide for Release 9.4 January 2006...

Table of Contents