Administering Meeting Exchange Servers

Transcription

1 Administering Meeting Exchange Servers Reease February 18, Issue 1

2 2012 Avaya Inc. A Rights Reserved. Notice Whie reasonabe efforts have been made to ensure that the information in this document is compete and accurate at the time of printing, Avaya assumes no iabiity for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obigation to notify any person or organization of such changes. Documentation discaimer Documentation means information pubished by Avaya in varying mediums which may incude product information, operating instructions and performance specifications that Avaya generay makes avaiabe to users of its products. Documentation does not incude marketing materias. Avaya sha not be responsibe for any modifications, additions, or deetions to the origina pubished version of documentation uness such modifications, additions, or deetions were performed by Avaya. End User agrees to indemnify and hod harmess Avaya, Avaya's agents, servants and empoyees against a caims, awsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deetions to this documentation, to the extent made by End User. Link discaimer Avaya is not responsibe for the contents or reiabiity of any inked websites referenced within this site or documentation provided by Avaya. Avaya is not responsibe for the accuracy of any information, statement or content provided on these sites and does not necessariy endorse the products, services, or information described or offered within them. Avaya does not guarantee that these inks wi work a the time and has no contro over the avaiabiity of the inked pages. Warranty Avaya provides a imited warranty on its hardware and Software ( Product(s) ). Refer to your saes agreement to estabish the terms of the imited warranty. In addition, Avaya s standard warranty anguage, as we as information regarding support for this Product whie under warranty is avaiabe to Avaya customers and other parties through the Avaya Support website: Pease note that if you acquired the Product(s) from an authorized Avaya reseer outside of the United States and Canada, the warranty is provided to you by said Avaya reseer and not by Avaya. Software means computer programs in object code, provided by Avaya or an Avaya Channe Partner, whether as stand-aone products or pre-instaed on hardware products, and any upgrades, updates, bug fixes, or modified versions thereto. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER; AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS YOU AND END USER ), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ( AVAYA ). Avaya grants you a icense within the scope of the icense types described beow, with the exception of Heritage Norte Software, for which the scope of the icense is detaied beow. Where the order documentation does not expressy identify a icense type, the appicabe icense wi be a Designated System License. The appicabe number of icenses and units of capacity for which the icense is granted wi be one (1), uness a different number of icenses or units of capacity is specified in the documentation or other materias avaiabe to you. Designated Processor means a singe stand-aone computing device. Server means a Designated Processor that hosts a software appication to be accessed by mutipe users. License type(s) Heritage Norte Software Heritage Norte Software means the software that was acquired by Avaya as part of its purchase of the Norte Enterprise Soutions Business in December The Heritage Norte Software currenty avaiabe for icense from Avaya is the software contained within the ist of Heritage Norte Products ocated at under the ink Heritage Norte Products. For Heritage Norte Software, Avaya grants Customer a icense to use Heritage Norte Software provided hereunder soey to the extent of the authorized activation or authorized usage eve, soey for the purpose specified in the Documentation, and soey as embedded in, for execution on, or (in the event the appicabe Documentation permits instaation on non-avaya equipment) for communication with Avaya equipment. Charges for Heritage Norte Software may be based on extent of activation or use authorized as specified in an order or invoice. Copyright Except where expressy stated otherwise, no use shoud be made of materias on this site, the Documentation, Software, or hardware provided by Avaya. A content on this site, the documentation and the Product provided by Avaya incuding the seection, arrangement and design of the content is owned either by Avaya or its icensors and is protected by copyright and other inteectua property aws incuding the sui generis rights reating to the protection of databases. You may not modify, copy, reproduce, repubish, upoad, post, transmit or distribute in any way any content, in whoe or in part, incuding any code and software uness expressy authorized by Avaya. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a crimina, as we as a civi offense under the appicabe aw. Third-party components Certain software programs or portions thereof incuded in the Software may contain software (incuding open source software) distributed under third party agreements ( Third Party Components ), which may contain terms that expand or imit rights to use certain portions of the Software ( Third Party Terms ). Information regarding distributed Linux OS source code (for those product that have distributed Linux OS source code) and identifying the copyright hoders of the Third Party Components and the Third Party Terms that appy is avaiabe in the Documentation or on Avaya s website at: You agree to the Third Party Terms for any such Third Party Components. Note to Service Provider. The Product may use Third Party Components that have Third Party Terms that do not aow hosting and may need to be independenty icensed for such purpose. In Meeting Exchange Reease 5.2 the Cient Registration Server, OCS Integration Server, Conference Viewer, Web Porte and Web Conferencing servers use the Windows Server Embedded 2003, and the Cient Registration Server uses Microsoft SQL 2005 Embedded. Whie Microsoft informs us that most Service Providers aready have SPLAs in pace, Avaya recommends that you contact your Microsoft deaer to assure the proper icensing of these eements. Preventing To Fraud "To fraud" is the unauthorized use of your teecommunications system by an unauthorized party (for exampe, a person who is not a corporate empoyee, agent, subcontractor, or is not working on your company's behaf). Be aware that there can be a risk of To Fraud associated with your system and that, if To Fraud occurs, it can resut in substantia additiona charges for your teecommunications services. Avaya To Fraud intervention If you suspect that you are being victimized by To Fraud and you need technica assistance or support, ca Technica Service Center To Fraud Intervention Hotine at for the United States and Canada. For additiona support teephone numbers, see the Avaya Support website: Suspected security vunerabiities with Avaya products shoud be reported to Avaya by sending mai to: [email protected]. Trademarks The trademarks, ogos and service marks ( Marks ) dispayed in this site, the Documentation and Product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiiates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation and Product(s) shoud be construed as granting, by impication, estoppe, or otherwise, any icense or right in and to the Marks without the express written permission of Avaya or the appicabe third party. Avaya is a registered trademark of Avaya Inc. A non-avaya trademarks are the property of their respective owners, and Linux is a registered trademark of Linus Torvads. <XYZ> is a trademark of <XYZ Inc.> A other trademarks are the property of their respective owners. Downoading documents For the most current versions of documentation, see the Avaya Support website:

3 Contact Avaya Support See the Avaya Support website: for product notices and artices, or to report a probem with your Avaya product. For a ist of support teephone numbers and contact addresses, go to the Avaya Support website: scro to the bottom of the page, and seect Contact Avaya Support.

4

5

6

7 Contents Chapter 1: Introducing the New Features in Meeting Exchange New recording functionaity New audio prompts New CDR fieds New bast dia cafow New anguages New codecs New signa to noise cacuation New upgrade procedures New server support New dia ist functionaity Chapter 2: Meeting Exchange checkist Chapter 3: Working with an eectronic preinstaation worksheet Obtaining a copy of the EPW Configuring the EPW Loading the EPW Verifying SNMP trap information using the EPW Chapter 4: Instaing Meeting Exchange software Introducing this chapter Introducing the stages of the instaation Accessing the server Instaing Meeting Exchange Accessing the software Configuring and testing the instaation Customizing the server IP Checking if a process are up and running Configuring the system timezone Configuring the number of icensed ports Enabing features Configuring ca branding Introducing ca branding Defining the DNIS size Listing a the entries Listing a singe entry Adding a DNIS Deeting a DNIS Administering Meeting Exchange Servers Apri

8 Modifying a DNIS Dispaying hep Making a ca Instaing Bridge Tak Configuring server resources Configuring server ogins Configuring SNMP Configuring automatic backups Viewing a ist of the fies that backup.sh supports Configuring backup.sh Chapter 5: Configuring the Meeting Exchange appication server Tips for using this document Matching Meeting Exchange to the speed of the network Customizing Meeting Exchange properties Customizing the scheduer utiity Creating sign-ins to Meeting Exchange A short note about sign-ins Creating sign-ins Viewing and deeting sign-ins Chapter 6: Configuring the Meeting Exchange media server Avaya Common Media Server features Configuring codecs Configuring the system settings Configuring the media settings Configuring automatic gain contro Configuring comfort noise generation Configuring transport settings Configuring drive settings Configuring the active speaker notification interva Chapter 7: Configuring externa servers Fie ocation Mounting Mounting the recording directory on the appication server Chapter 8: Branding the customer experience A short note on the customer experience Obtaining conference teephone numbers Administering Meeting Exchange Servers Apri 2011

9 Configuring Meeting Exchange number coection Configuring Meeting Exchange to hande a number it does not recognize Configuring partia matching Configuring the widcard Configuring the teephone number branding Configuring reservation groups Adding reservation groups Configuring ca branding for reservation groups Configuring diaing patterns A short note about syntax Configuring patterns for diaing out Configuring patterns for diaing in Chapter 9: Configuring bast dia ists Introducing bast dia ists Configuring bast dia Creating bast dia ists System administrators Creating a new bast dia ist Generating a bast dia ist from the LDAP server Viewing and printing bast dia ists Operators Bridge Tak CRS Front End Using bast dia ists Operators Bridge Tak CRS Front End Moderators Diaing out to bast dia ists Operators Moderators Viewing and printing bast dia ists System administrators Operators Chapter 10: Viewing Meeting Exchange information Introducing reports Ca Detai Record (CDR) reports Conference Detai Records (CODR) reports Administering Meeting Exchange Servers Apri

10 CDR Loader appication Accessing records using the Meeting Exchange System Administrator main menu 109 Configuring the fieds for viewing and printing Viewing and printing detai records Accessing reports using the Meeting Exchange System Administrator main menu 111 Working with conference report information Viewing and printing conference reports Accessing records using a reationa database Accessing records using a remote host Introducing the transmission process Configuring the Meeting Exchange server Configuring the remote host Writing an appication Defining a port Testing the configuration Accessing reports using the Cient Registration Server Accessing reports using Bridge Tak Accessing reports using Web Porta Accessing reports using the Reports Appication Accessing LAN statistics reports Accessing ogs Accessing genera ogs Accessing modification ogs Accessing operator ogs Accessing participant ogs Accessing port capacity reports Accessing poing reports Chapter 11: Configuring PINs A short note on PIN functionaity Off System Conference Conference types Unattended conferences Attended conferences Fexfow conferences Sef Registration conferences PIN mode and the user experience Administering Meeting Exchange Servers Apri 2011

11 A short note on PIN ists Creating PIN ists PINs.txt PINist.txt Loading PIN ists Chapter 12: Configuring recording Enabing the recording feature Configuring recording properties Configuring the payback ca fow Managing fies Ensuring access for users Managing recordings Supporting an oder method of conference payback for Web Porta users Chapter 13: Configuring anguages Introduction to ocaization A point of carification regarding anguages System anguage Conference anguage Participant experience Chapter 14: Configuring audio messages A short note about audio messages Prompt sets Per-conference messages System wide messages Recording new audio messages A short note about recording audio messages Configuring prompt set names Recording new messages Maintaining a transcript of messages Enabing system wide messages Chapter 15: Connecting Meeting Exchange to your network Connecting directy to Communication Manager Adding Meeting Exchange to the node names ist Adding a signaing group Adding a trunk group Adding a diapan entry Administering Meeting Exchange Servers Apri

12 Adding a UDP entry Adding an AAR entry Adding a route pattern Configuring Meeting Exchange for Communication Manager Connecting to an SES proxy Configuring Meeting Exchange for an SES proxy Configuring Communication Manager for an SES proxy Adding Meeting Exchange to the node names ist Adding the SES proxy to the node names ist Adding a signaing group for Meeting Exchange Adding a signaing group for the SES proxy Adding a trunk group for Meeting Exchange Adding a trunk group for the SES proxy Adding a diapan entry for Meeting Exchange Adding a diapan entry for the SES proxy Adding an AAR entry for Meeting Exchange Adding an AAR entry for the SES proxy Adding a route pattern for Meeting Exchange Adding a route pattern for the SES proxy Configuring Communication Manager and the SES proxy for SIP cas Configuring the SES proxy for SIP Configuring Communication Manager for SIP Connecting to AudioCodes Configuring Meeting Exchange for AudioCodes Configuring AudioCodes for Meeting Exchange Configuring PSTN trunks Configuring TDM Configuring direct connectivity Configuring ca routing Configuring transport type Configuring codecs Configuring DTMF Chapter 16: Configuring secure rea-time transport protoco (SRTP) Configuring Meeting Exchange Configuring Communication Manager Verifying SRTP Chapter 17: Configuring security features Configuring secure recordings Administering Meeting Exchange Servers Apri 2011

13 Configuring additiona PINs Chapter 18: Configuring Externa Passcode Vaidation (EPV) Introducing EPV Introducing the process Configuring the XML code Configuring the chdbased.reg fie Understanding the format of requests Understanding the format of responses Configuring EPV for fexfow conferences Ensuring that the second eve passcodes feature operates successfuy Configuring eader PINs Configuring mandatory biing codes for fexfow Configuring biing Configuring settings reating to stranded participants Testing the configuration Testing your code Using the keep aive response Using the xcaci test program Using a Web browser to vaidate PIN codes Chapter 19: Configuring aarms Introducing SNMP Introducing the traps Adding and deeting traps Configuring threshod vaues of trap receivers Configuring CPU and disk space usage traps Configuring Port usage traps Verifying that SNMP is running Debugging SNMP Introducing core services Running and verifying core services Configuring core services Viewing the ogs Chapter 20: Introducing mutisite Introducing mutisite How mutisite can be used to create goba conferences About hubs and inking servers Maximum number of sites and conferences Administering Meeting Exchange Servers Apri

14 Singe dia-in number to access goba conferences Mutisite required components Mutisite optiona components Architecture Network architecture System faiover Link ine architecture Faiover configuration and faut identification Biing architecture Mutisite terminoogy Chapter 21: Upgrading from Meeting Exchange 5.2 Service Pack 1 to Meeting Exchange 5.2 Service Pack Instaing the RPM fie Roing back to a previous version Ensuring the vaues of softmediaserver.cfg Chapter 22: Configuring mutisite Mutisite environment requirements Opening ports between sites Instaing mutisite for Meeting Exchange Setting up a CRS for mutisite use SQL 2000 and SQL 2005 SP Linking CRS servers Registering the server Setting up the stored procedure Configuring SQL stored procedures Configuring the MSDTC og fie Creating a new server in the CRS Front End Viewing servers Configuring MutiSite.ini for mutisite use Configuring mutisite for BSMon Stopping mutisite Setting up the audio conference server Utiizing goba conference resources Overbooking settings Setting up goba conference biing Chapter 23: Running mutisite About goba conferences Administering Meeting Exchange Servers Apri 2011

15 Scheduing goba conferences Managing goba conferences Conference features Goba eve conference features Loca conference features Non-supported features Tracking biing information for goba conferences Goba conference resource monitoring Chapter 24: Navigating mutisite Introduction CRS pane Bridge pane Stats pane Log Messages area Appendix A: Configuration task ist Tips for using this document Configuration tasks Appendix B: Finding parameters by name Tips for using this document Bast dia configuration properties CDR configuration properties Formatting considerations CDR configuration properties CODR configuration properties Ca Routing configuration properties Operator configuration properties Supervision configuration properties System configuration properties Timed Assist configuration Voice Message configuration Warning Tone configuration Administering Meeting Exchange Servers Apri

16 Appendix C: Supported management information bases (MIBs) Appendix D: Audio messages Appendix E: Dua Tone Muti-Frequency (DTMF) commands Scan conferences Moderator commands Conferee commands Fexfow conferences Moderator commands Conferee commands Commands for paying back a recording Appendix F: Feature List Appendix G: Configuration changes that require a reboot or a restart Rebooting or powering down Meeting Exchange Appendix H: List of softmediaserver.cfg parameters Administering Meeting Exchange Servers Apri 2011

17 Chapter 1: Introducing the New Features in Meeting Exchange 5.2 This chapter describes the new features in Meeting Exchange 5.2. New recording functionaity New audio prompts New CDR fieds New bast dia cafow New anguages New codecs New signa to noise cacuation New upgrade procedures New server support New dia ist functionaity New recording functionaity Meeting Exchange 5.2 features new recording functionaity. Customers can now record and pay back conferences directy from the appication server. The new recording and payback feature is aso highy configurabe to enabe customers to exacty match their depoyment requirements. Avaya has introduced a series of new parameters and a new cbuti function for this purpose. For more information, see Configuring recording on page 141. New audio prompts Meeting Exchange 5.2 contains a number of new audio prompts. In addition, Avaya has made changes to existing audio prompt scenarios, such as entering and exiting Q&A. Avaya has aso configured different tones to be payed when caers perform different actions. Avaya has aso increased the number of avaiabe message sots to accomodate two new message features. These new features are per-conference messages and system-wide messages. For more information, see Configuring audio messages on page 151. Apri

18 Introducing the New Features in Meeting Exchange 5.2 New CDR fieds Meeting Exchange 5.2 outputs a number of new fieds in the Ca Detai Record (CDR) fies. These new fieds incude the number of requests for operator assistance, the time of the ast request for operator assistance, and the unique participant identifier. These fieds are caed Oper Hep Reqs, Last Hep Req, and Unique Participant Identifier, respectivey. For moreinformation on these fieds, see CDR configuration properties on page 273. For more information on the functionaity reating to the unique participant identifier, see Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. New bast dia cafow In Meeting Exchange 5.2, the participants cafow when they receive a bast dia ca is very simiar to a reguar conference entry participant cafow. For exampe, Meeting Exchange may request a roca name and announce their entry to the conference. For more information, see Diaing out to bast dia ists on page 105. New anguages For Meeting Exchange 5.2, Avaya have re-recorded a audio messages for the foowing anguages: Engish (United States) German French (France) French (Canada) Spanish (Spain) Spanish (Latin America) Russian For more information, see Configuring anguages on page Administering Meeting Exchange Servers

19 New codecs New codecs Meeting Exchange 5.2 now ships with the Avaya Common Media Server. As a resut, Meeting Exchange supports a number of new features, such as ow rate bit codecs and video voice activated switching. For more information on these features, see Configuring the Meeting Exchange media server on page 75. New signa to noise cacuation The Meeting Exchange appication server now provides the Avaya Conferencing Provider appication programming interface (ACP-API) with the signa to noise cacuation on any given teephone ine. The ACP API sends a request and the appication server responds with the cacuation. New upgrade procedures It is now easier to upgrade your edition of Meeting Exchange. For the 5.2 reease, Avaya has automated many upgrade steps. In previous reeases, these steps were manua and required speciaist technica knowedge. For exampe, in the current reease, the databases upgrade automaticay. For more information, see Upgrading from Meeting Exchange 5.0.x, 5.1.x, or 5.2 to 5.2 Service Pack 1 on page 193. New server support For previous versions of Meeting Exchange, Avaya supported the De 1950 server. For Meeting Exchange 5.2, Avaya support the IBM X3550 M2 server for a components, with the exception of Avaya Web Conferencing recording functionaity. For Avaya Web Conferencing recording functionaity, customers require the IBM X3650 M2 server. For customers who are running Meeting Exchange 5.1 on a De 1950 server and who wish to upgrade to Meeting Exchange 5.2, Avaya wi continue to support the De 1950 server. However, this support for the De 1950 server ony extends to customers using the G.711 codec. If customers wish to add another codec, they must change to the IBM X3550 M2 server. If your depoyment consists of a De 1950 running Meeting Exchange 5.0, Avaya recommend increasing the avaiabe memory to 4 GB as a minimum requirement. Apri

20 Introducing the New Features in Meeting Exchange 5.2 New dia ist functionaity Meeting Exchange automaticay saves the current conference participant ist as the dia ist using the conference reference number as the fiename. Meeting Exchange makes this fie avaiabe for transfer to a dia ist directory on the Meeting Exchange server. To enabe this feature, you must configure a directory on the CRS server and aso configure a schedued job to transfer the fie to the Meeting Exchange server. For more information, see Configuring bast dia on page Administering Meeting Exchange Servers

21 Chapter 2: Meeting Exchange checkist This chapter ists the tasks that you must perform in order to insta, configure, and administer Avaya Meeting Exchange 5.2. This ist is an overview of the processes invoved in depoying Meeting Exchange in your customer network. Use it as a guide whie you perform the tasks in the specified order. Tabe 1: Overview of Meeting Exchange Tasks Description More Information 3 Insert the Meeting Exchange CD and restart the appication server. Connect a aptop to a dedicated services port or connect a screen and keyboard directy to the server. Introducing the stages of the instaation on page 32 Accessing the server on page 32 Insta the Meeting Exchange 5.2 software. Instaing Meeting Exchange on page 33 Obtain passwords from your Avaya Support Representative. Configure the customer s network IP information. Check if a processes are up and running. Configure the system timezone. Configure the number of icensed ports. Accessing the software on page 36 Customizing the server IP on page 37 Checking if a process are up and running on page 41 Configuring the system timezone on page 42 Configuring the number of icensed ports on page 43 Enabe Meeting Exchange features. Enabing features on page 43 Configure ca branding for a test ca. Configuring ca branding on page 44 Make a test ca. Making a ca on page 52 Insta Avaya Bridge Tak 5.2. Instaing Bridge Tak on page 56 Configure server resources. Configuring server resources on page 56 Configure server ogins. Configuring server ogins on page 57 Creating sign-ins on page 73 1 of 3 Apri

22 Meeting Exchange checkist Tabe 1: Overview of Meeting Exchange Tasks (continued) Description More Information 3 Configure SNMP. Configuring SNMP on page 58 Configure automatic backups. Match Meeting Exchange to the speed of your network. Customize the Meeting Exchange properties to suit your requirements. Customize the Scheduer Utiity. Obtain the teephone numbers which the customer intends to use for conferencing. Configure how Meeting Exchange handes these teephone numbers. If you intend to use them in your depoyment, configure reservation groups at this point. Configure how Meeting Exchange converts teephone numbers to Uniform Resource Identifiers (URIs). Connect Meeting Exchange to the customer s network for in-service use. If you intend to use them in your depoyment, configure dia ists. If you intend to use them in your depoyment, configure PIN ists. Configuring automatic backups on page 58 Matching Meeting Exchange to the speed of the network on page 62 Customizing Meeting Exchange properties on page 63 Finding parameters by name on page 269 Customizing the scheduer utiity on page 66 Obtaining conference teephone numbers on page 90 Configuring Meeting Exchange number coection on page 90 Configuring Meeting Exchange to hande a number it does not recognize on page 90 Configuring the teephone number branding on page 91 Configuring reservation groups on page 92 Configuring diaing patterns on page 93 Connecting directy to Communication Manager on page 161 Connecting to an SES proxy on page 167 Connecting to AudioCodes on page 176 Configuring bast dia ists on page 99 Configuring PINs on page of 3 22 Administering Meeting Exchange Servers

23 Tabe 1: Overview of Meeting Exchange Tasks (continued) Description More Information 3 If you intend to use the conference recording feature in your depoyment, configure record and payback. If you require any changes to the defaut audio messages, make these changes. If you have specific requirements for ocaization, configure your required anguages. If your depoyment requires enhanced security, configure these settings. Configuring recording on page 141 Configuring audio messages on page 151 Configuring anguages on page 147 Configuring security features on page of 3 Apri

24 Meeting Exchange checkist 24 Administering Meeting Exchange Servers

25 Chapter 3: Working with an eectronic preinstaation worksheet To faciitate configuration of settings for the conferencing server, an eectronic preinstaation worksheet or EPW is incuded with the software instaation. After you insta the Linux and Meeting Exchange software on your server, use SCP to copy the EPW to your PC. Configure the settings for your conferencing server and downoad the competed EPW to the conferencing server. Tip: Tip: Use the EPW ony for a new insta, not for an upgrade. This section contains the foowing sections: Obtaining a copy of the EPW Configuring the EPW Loading the EPW Verifying SNMP trap information using the EPW Obtaining a copy of the EPW To obtain a copy of the EPW: 1. Open a PuTTY session and og in as a craft user. PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid craft password. 2. Go to /usr/dcb/bin/mx_epw 3. Open a WinSCP session on your PC. 4. Using SCP, copy the EPW_MX.xs fie to /home/craft Apri

26 Working with an eectronic preinstaation worksheet Configuring the EPW Open the worksheet on your PC and enter specifics about your conferencing server by paging through the tabs at the bottom of the page. You wi need information for the foowing pages shown in Tabe 2. Tabe 2: EPW Settings EPW Page Description Information Cross Reference Intro Provides description of EPW Read-ony Status Checkist Usage - Patform Information NFS Config Server Quick reference to determine competion status of each EPW page Overview of items needed for software insta Enter server names and IP Addresses Detais for setting up an NFS server for audio fies Server Configuration Parameters SNMP Parameters Read-ony Read-ony Customizing the server IP on page 37 If the conferencing server does not use NTP, provide an IP address of in this fied. Configuring the system settings on page 79 The SNMP parameters are: Product ID Threshods: - Reserved Port Poo Usage Lower Aarm - Reserved Port Poo Usage Upper Aarm - Unreserved Port Poo Usage Lower Aarm - Unreserved Port Poo Usage Upper Aarm A port poo usage threshods are optiona. For more information, see Introducing SNMP on page 205. Media Server Runtime Parameters Configuring the media settings on page 80 1 of 2 26 Administering Meeting Exchange Servers

27 Configuring the EPW Tabe 2: EPW Settings (continued) EPW Page Description Information Cross Reference Media Server Interface Configuration Video Conferencing - System Parameters Save your changes. on page 84 Process Configuration Parameters System System Configuration Customizing Meeting Exchange properties on page 63 Scheduer Scheduer Settings For more information, see Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. Sign-in mxmonitor/ chdbased SIP SNMP Maintenance, Operator and Scheduer sign-in configuration Appication server faiover utiity SIP Proxy Configuration URI to Teephone Number Configuration Teephone Number to URI Configuration Configure IP for SNMP trap receivers A short note about sign-ins on page 73 Connecting Meeting Exchange to your network on page 161 Proxy Address with which to register Configuring diaing patterns on page 93 Configuring diaing patterns on page 93 The configurabe settings are: IP Address Port Number (Optiona) Community String (Optiona) SNMP Device Type (Optiona) For more information, see Verifying SNMP trap information using the EPW on page 28 2 of 2 Apri

28 Working with an eectronic preinstaation worksheet Loading the EPW Once you have configured a the settings in the EPW, downoad the spreadsheet to your conferencing server. 1. Foow steps 1 through 6 in Obtaining a copy of the EPW on page Copy the competed EPW from your PC to /home/craft on the conferencing server. 3. Cose your WinSCP session. 4. Log in to the server as a superuser. 5. Copy the new fie from dcbguest to /usr/dcb/bin/mx_epw. 6. Stop the server. service mx-bridge stop 7. Run the utiity../run_mx_epw.sh <Exce_spreadsheet_name> 8. Verify the instaation in the generated og fie at: /var/disk/ogs/run_mx_epw.og. 9. If you are using SNMP, run the commands shown in Verifying SNMP trap information using the EPW on page Reboot the server to insta the new configurations. Verifying SNMP trap information using the EPW The EPW utiity modifies a SQL script, /usr/ipcb/config/mxaarms.postgres.sq, which is then used to popuate the trap destination information into the snmptrapreceiver tabe in the Core Services database. To verify that the SNMP trap information has been popuated to postgres, execute the foowing commands after running the EPW utiity: su postgres At the bash prompt, enter: psq coreservices -f /usr/ipcb/config/mxaarms.postgres.sq This command wi execute the /usr/ipcb/config/mxaarms.postgres.sq command which wi popuate the snmptrapreceivers tabe. To see the configured SNMP trap services, at the bash prompt, enter: psq coreservices 28 Administering Meeting Exchange Servers

29 Verifying SNMP trap information using the EPW At the coreservices # prompt, enter: Tip: seect * from snmptrapreceiver; Tip: Verify that you have incuded the semicoon at the end of the command. This wi return the information for the SNMP trap server that has been set up for your system. For more information on SNMP, see Introducing SNMP on page 205. Apri

30 Working with an eectronic preinstaation worksheet 30 Administering Meeting Exchange Servers

31 Chapter 4: Instaing Meeting Exchange software This chapter describes how to insta the Meeting Exchange software. This chapter aso describes how to insta the Linux operating system, which is required by Meeting Exchange. The operating system is on the same CD as the Meeting Exchange software. Typicay, Avaya instas the Meeting Exchange software on the IBM 3550 M2 before they ship it to the customer. However, Avaya recognizes that many customers re-insta the Meeting Exchange software in order to configure it to suit their network environment. Avaya recommends that customers engage with their Avaya Support Representative for assistance if they choose to re-insta. This chapter contains the foowing sections: Introducing this chapter Introducing the stages of the instaation Accessing the server Instaing Meeting Exchange Accessing the software Configuring and testing the instaation Note: Note: This chapter refers to the IBM X3550 M2 as "the server". Introducing this chapter There are two routes through this chapter. The first route is for customers who decide to re-insta the Meeting Exchange software when the server arrives on their site. During this re-instaation, these customers configure the IP address of the server as it wi be referenced on their LAN. If you choose this route, begin with the steps in Instaing Meeting Exchange on page 33 and continue through the chapter. The second route is for customers who decide not to re-insta the Meeting Exchange software when the server arrives on their site. These customers accept the Avaya defaut instaation. These customers must run some scripts to configure the IP address of the server as it wi be referenced on their LAN. If you choose this route, begin with the steps in Accessing the software on page 36 and continue through the chapter. Apri

32 Instaing Meeting Exchange software Note: Note: You can aso use this chapter as a guide in the unikey event that you have to re-insta the Meeting Exchange software at any time. Introducing the stages of the instaation There are a number of stages invoved in the instaation of Meeting Exchange. Once you insert the CD that contains the Meeting Exchange software and provide a number of configuration settings, the server automaticay performs the instaation and you can simpy monitor the progress of the instaation. The instaation can take up to 40 minutes to compete. Important:! Important: When you re-insta Meeting Exchange, you deete a previous configurations, conferences, IP information, parameters, and biing information. The stages beow simpy provide an overview of the instaation phases. Do not foow the stages as if they were the ony required steps. Here are the main stages: Insert the CD that contains the Meeting Exchange software Restart the server Connect a screen and keyboard directy to the server Configure IP connectivity between the screen/keyboard and the server Configure the date and time Configure the ethernet settings - The server copies the fies from the CD - The server ejects the CD - The server automaticay reboots - The server configures the Meeting Exchange software - The server outputs a verfication string to demonstrate that the instaation has been successfu Accessing the server During the instaation, the server shoud not be connected to the customer s corporate network. During this time, you can access the server by connecting a screen and keyboard directy to the server. 32 Administering Meeting Exchange Servers

33 Instaing Meeting Exchange Avaya shipped previous reeases of Meeting Exchange on a De 1950 server. On the De 1950 server, there was a services port. The services port is not avaiabe on the IBM 3550 M2. It is important to note that on the IBM 3550 M2, eth1 is not avaiabe. In previous reeases of Meeting Exchange on the De 1950 server, eth1 was the service port. On the IBM 3550 M2, eth3 defauts to the service port. As part of the instaation process, you configure the server IP settings. After the instaation, the server is connected to the corporate network. After the instaation, you can access the server using your network LAN. Instaing Meeting Exchange During this stage, you can access the server directy. Once you compete the instaation, you must access the server using the secure she (SSH) protoco. 1. Insert the CD that contains the Meeting Exchange software into the CD drive on the server. 2. Restart the server. This can take up to five minutes. When the server restarts, it dispays the foowing message: Defaut is auto. Boot: Press enter 3. Press the Enter key. The software oads. When the software finishes oading, it dispays the foowing message: Press enter to activate this consoe. 4. Press the Enter key. The server dispays the first instaation screen, caed Warning - Format Disk - Warning. For more information, see Figure 1. Figure 1: Warning - Format Disk - Warning Screen Apri

34 Instaing Meeting Exchange software 5. Seect Yes on this screen. The server dispays the Seect Server Type screen. On the Seect Server Type screen, the IBM 3550 M2 may not be isted. 6. If the IBM 3550 M2 is not isted, seect the Unknown option. Tip: Tip: Use the Tab keys to navigate through the fieds. Use the space bar to seect a fied. When you have made your seection, navigate to OK and press the Enter/ Return key. The server dispays the What Do You Want To Do screen. For more information, see Figure 2. Figure 2: What Do You Want To Do Screen 7. Seect Insta Meeting Exchange X.X.X.X and seect OK. The server dispays the Date/Time Initiaization screen. For more information, see Figure 3. Figure 3: Date/Time Initiaization Screen 8. Configure the date, year, time, and timezone. 34 Administering Meeting Exchange Servers

35 Instaing Meeting Exchange 9. Enter the IP address of the NTP server that manages the time sychronization for your corporate network. 10. Seect OK. The server dispays the Configure Network Information screen. 11. Enter the configuration information. Tabe 3 describes each of the fieds on the Configure Network Information screen. Tabe 3: Configure Network Information Screen Fied Hostname DNS Domain DNS Server eth0 eth1 eth2 eth3 Description Enter the hostname of the server as it wi be referenced on your LAN. Enter the fuy quaified domain name of the server as it wi be referenced on your LAN. Enter the IP address of the server as it wi be referenced on your LAN. Enter the IP address and Subnet Mask for your LAN. Ensure that the Enabe fied has an X. Avaya provides these ethernet ports for network configurations with enhanced redundancy. At this point, you do not need to enter any information in these fieds. This is the services port. It is pre-popuated with the services IP address. It is enabed. Do not make any changes to this fied. When you compete this screen, the server formats the server drives. The server copies the fies from the CD. These fies incude a the fies that are necessary for Meeting Exchange operation, such as RPM fies. This process can take up to 10 minutes. The server ejects the CD. The server reboots. The server runs a number of configuration scripts in order to unpackage the instaation fies that it copied from the CD. This process can take up to 30 minutes. Once this process is compete, you can no onger access the server using the Tenet protoco. You must access the server using the secure she (SSH) protoco. 12. Open a PuTTY session and og in as a craft user. Apri

36 Instaing Meeting Exchange software Note: Note: PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid craft password. 13. Navigate to /var/disk/ogs and vaidate that the insta is compete by monitoring the S94mx-runOnce* fie for the appearance of the string MeetingExchange Server configured successfuy. For more information, see Figure 4. Figure 4: S94mx-runOnce* Fie Accessing the software At this point, you can access the Meeting Exchange software. Avaya provides four eves of access to the software. For more information about the eves of access, see Creating sign-ins to Meeting Exchange on page 72. Aternativey, contact your Avaya Support Representative for more information about ogins and passwords. Configuring and testing the instaation Before you start using Meeting Exchange, you must perform a number of configuration and verification tasks, as foows: Customizing the server IP Checking if a process are up and running Configuring the system timezone 36 Administering Meeting Exchange Servers

37 Configuring and testing the instaation Configuring the number of icensed ports Enabing features Configuring ca branding Making a ca Instaing Bridge Tak Configuring server resources Configuring server ogins Configuring SNMP Configuring automatic backups As described in Introducing this chapter on page 31: If you have re-instaed the software after the server arrived on site, you can proceed to Checking if a process are up and running on page 41. If you have not re-instaed the software after the server arrived on site, you must run some scripts to configure the IP address of the server as it wi be referenced on your LAN. You shoud proceed to Customizing the server IP on page 37 before Checking if a process are up and running on page 41. Customizing the server IP When Avaya ships the server to the customer site, they configure it with a defaut IP address. This IP address is identica in a Meeting Exchange servers that they ship. You must configure a new server IP address so that you can reference the server on your LAN. You can aso add the detais of the NTP server that manages the time sychronization for your corporate network. If you have just re-instaed a the Meeting Exchange software, in accordance with Instaing Meeting Exchange on page 33, you wi not need to customize the IP because you have aready performed that step. However, you may want to use some of the scripts to customize other detais. Avaya provide the mx-ipchange.sh script to manage the process of customizing Meeting Exchange server network information. This script can modify the IP address, host name, domain name, netmask, gateway NTP, and the DNS of the server. To run this script: 1. Open a PuTTY session and og in as sroot user or, if you cannot access it, you can connect directy to the server. Apri

38 Instaing Meeting Exchange software Note: Note: PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid sroot password. The sroot ogin provides a higher eve of access to the server than the craft ogin. 2. Navigate to /usr/dcb/bin and run the mx-ipchange.sh script. For more information, see Figure Administering Meeting Exchange Servers

39 Configuring and testing the instaation Figure 5: Syntax of mx-ipchange.sh mx-ipchange.sh: mx-ipchange.sh: ========================================== mx-ipchange.sh: NOTICE: SYSTEM REBOOT REQUIRED mx-ipchange.sh: mx-ipchange.sh: A system reboot is required to update mx-ipchange.sh: the conferencing bridge IP configuration. mx-ipchange.sh: mx-ipchange.sh: Additiona warnings wi be issued prior mx-ipchange.sh: to appying changes and prior to rebooting. mx-ipchange.sh: mx-ipchange.sh: Type "Ctr-C" within 10 seconds to mx-ipchange.sh: terminate this procedure. mx-ipchange.sh: =========================================== mx-ipchange.sh: Current customer LAN configuration is: Host name = aveoeight Domain name = usae.avaya.com IP_address = Netmask = Gateway = Network Time Server(s) = ntp.usae.avaya.com Domain Name Server(s) = Domain Search List = usae.avaya.com NIC bonding state = enabed NIC device = bond0 Host name (defaut="aveoeight"). Enter h for hep, q to quit: Apri

40 Instaing Meeting Exchange software ----At this point, you can enter the new host name---- Host name (defaut="aveoeight"). Enter h for hep, q to quit: Domain name (defaut="usae.avaya.com"). Enter h for hep, q to quit: usae.avaya.com Enter IP address 1 of 1 for New IP address : Enter IP address 1 of 1 for New subnet mask : Enter IP address 1 of 1 for New gateway address : Mutipe query. Type return if you have fewer addresses to enter Enter IP address 1 of 3 for Network Time Servers: ntp.1.net Enter IP address 2 of 3 for Network Time Servers: ntp.2.net Enter IP address 3 of 3 for Network Time Servers: netntp.3.net Mutipe query. Type return if you have fewer addresses to enter Enter IP address 1 of 3 for DNS servers : Enter IP address 2 of 3 for DNS servers : DNS search domains (eg: yours.net mine.net) : usae.avaya.com /usr/dcb/bin/mx-ipchange.sh: 10 second deay before writing new configuration. /usr/dcb/bin/mx-ipchange.sh: quit: Return to continue or anything to 3. At the end, the script performs an automatic reboot to compete the changes. 4. Vaidate the changes by accessing the server using the LAN: a. Open a PuTTY session and og in as a craft user. b. Enter the command: su - sroot c. Run the foowing command to dispay the hostname: hostname 40 Administering Meeting Exchange Servers

41 Configuring and testing the instaation d. Run the foowing command to dispay the IP address: cat /etc/hosts grep <hostname> e. Run the foowing command to view the defaut gateway and and subnet mask: netstat rn Checking if a process are up and running At this point, Avaya recommends running a command to check if a processes are up and running. You can do this using a command caed Digita Conferencing Bridge Process Status. (DCBPS). 1. Open a PuTTY session and og in as a craft user. 2. Enter the command: su - sroot 3. Run this command: dcbps This server returns a ist of the processes that are up and running. See Figure 6 for more information. Figure 6: DCBPS Command Resuts Apri

42 Instaing Meeting Exchange software Configuring the system timezone Athough you have aready configured an NTP server, you must aso set the server timezone for the PostgreSQL database. PostgreSQL is the object-reationa database management system (ORDBMS) that Avaya uses in Meeting Exchange. It is a free and open-source program. 1. Open a PuTTY session and og in as a craft user. 2. Enter the command: su - sroot 3. Navigate to /usr/dcb/bin and run the foowing command: tzset 4. Enter 0 for a ist of a supported timezones. For more information, see Figure 7. Figure 7: Tzset Command 5. Enter the number of the timezone that you wish to configure. 6. Reboot the server using the foowing method, which Avaya recommends: a. Log in to Meeting Exchange as dcbmaint. b. From the System Administrator Main Menu, seect Re-initiaization. c. Seect Y at the confirmation. d. Press the Enter/Return key. The server reboots and impements the change. 7. Once the server has rebooted, open a PuTTY session and og in as a craft user. 42 Administering Meeting Exchange Servers

43 Configuring and testing the instaation 8. Enter the command: su - sroot 9. Navigate to /usr/dcb/bin. 10. Verify the timezone by using the echo command to dispay the current timezone: echo $TZ :US/Eastern As an aside, if you want to view the current system time that the server is using: a. Log in to Meeting Exchange as dcbadmin. b. From the System Administrator Main Menu, seect System Date/Time and verify the time and date information. Configuring the number of icensed ports The number of icensed ports is the number of teephone ines that the server can support at any time. If a customer buys more ports, they can support a arger number of simutaneous conferences and conference participants. Note: Note: Contact your Avaya Support Representative for more information on how to configure the number of icensed ports. Enabing features Meeting Exchange ships with a arge number of features. You can enabe certain features and disabe others, depending on your requirements. You must restart the server if you make any changes to the feature ist. For exampe, Avaya offers a feature caed overbooking. The overbooking feature increases the avaiabe ports by providing a poo of additiona virtua ports. These virtua ports are avaiabe for reserved conference bookings. This functionaity ensures that customers can maximize the use of their conferencing system by aowing for the fact that in many cases, fu conference attendance does not occur. You can enabe or disabe this feature and many other optiona features. For more information on overbooking, see Customizing the scheduer utiity on page 66. Tip: Tip: Feature List on page 355 describes the Meeting Exchange features. You aso have the option of enabing or disabing these features at a ater date. Apri

44 Instaing Meeting Exchange software To configure the feature ists: 1. Open a PuTTY session and og in as an sroot user. 2. Navigate to /usr/dcb/bin and run the foowing command: featcfg The server ists the features and dispayed their status as instaed or not instaed. To dispay the disabed features: featcfg grep "Not Instaed" To dispay the enabed features: featcfg grep -v "Not Instaed" To enabe a feature: featcfg +<feature name> To disabe a feature: featcfg -<feature name> 3. Reboot the server using the foowing method, which Avaya recommends: a. Log in to Meeting Exchange as dcbmaint. b. From the System Administrator Main Menu, seect Re-initiaization. c. Seect Yes at the confirmation. d. Press the Enter/Return key. The server reboots and impements the change. e. Once the server reboots, og in to Meeting Exchange again as dcbmaint. Configuring ca branding Ca branding is a feature that enabes you to configure the participants conference experience, based on the teephone number that they use to dia Meeting Exchange. This section describes how to configure this feature in order to enabe you to make a very basic test ca to the conferencing server. It contains the foowing sections: Introducing ca branding Defining the DNIS size Listing a the entries Listing a singe entry Adding a DNIS Deeting a DNIS 44 Administering Meeting Exchange Servers

45 Configuring and testing the instaation Modifying a DNIS Dispaying hep For more detaied information on ca branding, incuding instructions on how to configure this feature for your customer needs, see Branding the customer experience on page 89. Introducing ca branding When conference participants dia the server to enter their conference, the server pays them a series of audio prompts. Avaya provides customers with the fexibiity to configure up to different teephone numbers that wi a dia into the same server. Customers can ink customized audio prompts with each of these different teephone numbers. For the customized audio prompts, Meeting Exchange supports up to 21 anguages. Customers can aso ink different ca fows with each of these different teephone numbers. These teephone numbers are caed Direct Dia Inward (DDIs) or Diaed Number Identification Service (DNISs). A ca fow refers to the sequentia experience of the conference participant as they dia into a conference or isten back to a conference recording. Avaya aso aows customers to imit the ength of the DDI which Meeting Exchange processes. For exampe, if customers use the teephone numbers , , , , and so on, you can configure Meeting Exchange to read the ony the digits that vary. Meeting Exchange does not need to process a digits. The number of digits that you configure to be processed by Meeting Exchange is caed the DNIS size. The configuration of processing preferences such as imiting the DNIS size and inking various ca fows is caed ca branding. Ca branding occurs when Meeting Exchange coects the digits that the participant dias, matches them to an entry in a ca branding tabe, then processes the ca in accordance with with the instructions that you have configured in that ca branding tabe. To configure ca branding, Avaya provides a command ine utiity, caed cbuti. cbuti enabes you to assign a specific annunciator message, ine name, company name, system function, reservation group, and audio prompt sets to a maximum of 5000 DNIS patterns. You must ensure that the fina entry in the ca branding tabe is the wid card entry, which is????. If Meeting Exchange coects a DNIS that is not isted in the tabe, it processes the ca based on the instructions that you have configured in this entry. When the a caer first uses a DNIS, Meeting Exchange checks the cbuti fie. Meeting Exchange then routes the ca in accordance with the configuration settings for that DNIS. After this initia check, Meeting Exchange caches the cbuti routing instructions in the shared memory database. Caching the instructions means that Meeting Exchange avoids having to check cbuti each time. Apri

46 Instaing Meeting Exchange software Tabe 4 describes each of the variabes in the ca branding tabe. Tabe 4: Expanation of the DNIS variabes Variabe <dnis> Expanation Specifies the digit pattern of the DNIS. In certain regions, this is known as Direct Dia Inward (DDIs). You can specify the number of digits that Meeting Exchange coects using the Digit Parameters configuration option. For more information see Ca Routing configuration properties on page 292. <rg> Specifies the Reservation Group. Meeting Exchange supports up to 999 Reservation Groups. The Reservation Groups feature aows operators to schedue mutipe conferences with the same conference code at the same time. Each DDI is associated with a specific Reservation Group. For more information on Reservation Groups, see Configuring reservation groups on page 92. <msg> <ps> <ucps> The annunciator message, isted by number, that Meeting Exchange pays to the participant before it processes the ca in accordance with the instructions that you have configured for this entry. For more information on configuring messages, see Configuring audio messages on page 151. The number of the audio prompt set, from 0 to 20, that Meeting Exchange uses to pay the annunciator messages. Meeting Exchange supports up to 21 anguages. Specifies if Meeting Exchange pays the audio prompt set from the anguage that the moderator or operator has assigned to the conference or if it pays the audio prompt set from the anguage that you have configured, using cbuti, for this entry. The vaid vaues are Y and N. 1 of 4 46 Administering Meeting Exchange Servers

47 Configuring and testing the instaation Tabe 4: Expanation of the DNIS variabes (continued) Variabe <func> Expanation Specifies how Meeting Exchange processes a ca that matches the incoming digits. The vaid vaues are: ENTER Meeting Exchange paces the ca in the Enter Queue. The Enter Queue is where participants await the attention of an operator. This is the most common choice for a conference in Attended Mode. DIRECT Meeting Exchange paces the ca directy in a conference. This a common choice for unattended cas. This function does not support fexfow conferences. If you require the DNIS to dia a fexfow conference, configure this vaue to FLEX. SCAN Meeting Exchange pays an annunciator message to prompt the participant to enter the passcode for the conference. This a common choice for unattended cas. HANGUP Meeting Exchange ends the ca. AUTOVL This fied is reserved for a mutisite conference. MutiSite refers to a network of Conference Reservation Servers (CRSs) ocated in different geographica ocations. FLEX Meeting Exchange identifies the ca as a Fexfow ca. A fexfow conference is a specific type of demand conference. In fexfow conferences, a ca routing is based on the conferee passcode. In addition to the conferee passcode, moderators enter a moderator passcode, which grants access to a moderator-specific menu. PLAYBACK Meeting Exchange routes the ca to the repository of conference recordings. Meeting Exchange prompts the User for a conference reference number and a passcode and pays the appropriate conference recording, if it is avaiabe. For more information, see Configuring the payback ca fow on page of 4 Apri

48 Instaing Meeting Exchange software Tabe 4: Expanation of the DNIS variabes (continued) Variabe Expanation -o <of> Specifies how Meeting Exchange deas with faied actions that the participant makes, such as entering an incorrect passcode. Meeting Exchange paces the participant in the Enter Queue (ENTER) or ends the ca (HANGUP) or aternativey appies the Conference Scheduer ENTER or HANGUP vaues (DEFAULT). The defaut is HANGUP. This fied is not vaid if you set the function fied to ENTER, HANGUP, or DIRECT. If you do not configure a vaue for this setting or configure DEFAULT, Meeting Exchange uses the faiure instructions that you have configured using the Conference Scheduer appication. The Conference Scheduer appication is a command ine utiity that Avaya provides to enabe you to configure a arge number of settings for conferences, such as how ong to retain conference records and the number of avaiabe ines for on-demand conferences. You can access the Conference Scheduer appication by ogging into Meeting Exchange as a dcbadmin and navigating to System Administrator Main Menu > Configure Scheduer > Invaid Code. For more information on the Conference Scheduer appication, see Customizing the scheduer utiity on page 66. The vaues that you configure using the Conference Scheduer appication are goba vaues. Meeting Exchange appies Conference Scheduer vaues to a conferences uness you configure a vaue using cbuti. A cbuti vaue of ENTER or HANGUP wi override the Conference Scheduer vaues. On the other hand, a cbuti vaue of DEFAULT wi appy the Conference Scheduer vaues. Another vaue, outside of cbuti, aso exerts an infuence over the functionaity of this variabe. That vaue is caed Security Code Error3 and you can configure it by ogging into Meeting Exchange as a dcbadmin and navigating to System Administrator Main Menu > Configurations > Voice Message Configuration. For this cbuti vaue to operate successfuy, you must set Security Code Error3 to Tone. If you set it to any vaue other than Tone, Meeting Exchange uses the Invaid Code property that you have set in the Conference Scheduer command ine utiity. - <"n"> An optiona ine name that you can associate with the DNIS. The name can contain up to 20 characters. Meeting Exchange dispays this name to the operator and aso dispays it in ca and conference detai records (CDRs and CODRS). This optiona ine name is especiay usefu for cas destined for the Enter Queue because it heps operators to provide custom greetings. The defaut is bank. If you eave this fied as bank and you have configured SCAN or FLEX in the func fied, Meeting Exchange uses this fied to dispay the ast passcode that the participant enters. -c <"cn"> An optiona company name to associate with the DNIS. The name can contain up to 20 characters. Meeting Exchange dispays this name to the operator and aso dispays it in ca and conference detai records (CDRs and CODRS). The defaut is bank. 3 of 4 48 Administering Meeting Exchange Servers

49 Configuring and testing the instaation Tabe 4: Expanation of the DNIS variabes (continued) Variabe -crs <n> -cre <n> -cc <n> Expanation An optiona starting Bridge Tak conference room assigned to this DNIS. This setting aong with conference room end sets a range of rooms. When caers ca the DNIS, Meeting Exchange paces them into the conference room. Operators, using Bridge Tak, can see the caers in the conference room diaog. Customers can use this feature to assign responsibiity for specific conference rooms to specific operators. Customers can aso use this feature, aong with - <"n"> and -c <"cn"> to ensure that operators customize the conferencing experience for caers. An optiona ending Bridge Tak conference room assigned to this DNIS. This setting aong with conference room start sets a range of rooms. An optiona setting that is ony used with the DIRECT function. When you configure the DIRECT ca fow in the <func> coumn, Meeting Exchange paces the ca directy in a conference. Using the CC coumn, you can enter a conference code for use with a DIRECT ca fow. For exampe, consider a depoyment of cbuti with the foowing vaues: DNIS: 1234 Function: DIRECT Conference Code: 5678 When a caer dias in with DNIS 1234, Meeting Exchange paces them in a conference with the passcode Using this feature, it is possibe to have any number of DIRECT ca branding entries putting caers into the same conference. If you do not configure the CC fied, Meeting Exchange paces a caer who dias in with DNIS 1234 into a conference that has the passcode This passcode can be a moderator passcode, a conferee passcode, or a co-chair passcode, so at most, Meeting Exchange can route three DIRECT ca branding entries to a given conference. The CC coumn eiminates this restriction. This feature is sometimes caed Unimited DDIs. 4 of 4 Defining the DNIS size Avaya does not recommend defining the DNIS size on an operationa conferencing system because the update coud impact ive conferences. To define the DNIS size, you must configure two separate fies: You must define the DNIS size in the ca branding tabe using cbuti. You must aso define the DNIS size in a Ca Routing Configuration parameter, caed Digit Parameters. The foowing steps describe these two configuration tasks: Apri

50 Instaing Meeting Exchange software 1. Open a PuTTY session and og in as a craft user. 2. Define the DNIS size as foows To define the DNIS size as 4: cbuti dnissize 4 3. Log in as a dcbadmin User to access the System Administrator Main Menu. 4. Navigate to System Administrator Main > Configurations > Ca Routing Configuration > Digit Parameters. 5. Define the vaue of Digit Parameters to ensure that it matches the vaue of dnissize in cbuti. Listing a the entries To ist a the entries in the ca routing tabe: 1. Open a PuTTY session and og in as a craft user. 2. Count the entries, as foows: cbuti count Meeting Exchange dispays the number of entries in the ca routing tabe. If the count is ess than 2000, proceed to step If the count is greater than 2000, set the ROW_SET_MAX environmenta variabe to the count vaue pus 1: If you are using the sh/ksh/bash she, the command shoud be: export ROW_SET_MAX=<count vaue +1> Note: Note: By defaut, when Avaya ships Meeting Exchange, the she for the sroot, craft, and dcbguest og-ins is the bash she. 3. Run this command: cbuti ist <number of entries to ist per page> By defaut, Meeting Exchange dispays 25 entries per page. 4. Press ENTER to view the next page of entries. Listing a singe entry To ist a singe ca routing entry: 1. Open a PuTTY session and og in as a craft user. 2. Run this command: cbuti ookup <dnis> 50 Administering Meeting Exchange Servers

51 Configuring and testing the instaation Adding a DNIS To add a singe ca routing entry: 1. Open a PuTTY session and og in as a craft user. 2. Run the foowing command: cbuti add <dnis> <rg> <msg> <ps> <ucps> <func> [-o <of> - <n> -c <cn> -crs <n> -cre <n>] Deeting a DNIS See Tabe 4 for more information on the ca routing variabes. To deete a singe ca routing entry: 1. Open a PuTTY session and og in as a craft user. 2. Run the foowing command: cbuti remove <dnis> Modifying a DNIS To modify a singe ca routing entry: 1. Open a PuTTY session and og in as a craft user. 2. Run the foowing command: cbuti update <dnis> <rg> <msg> <ps> <ucps> <func> [-o <of> - <n> -c <cn> -crs <n> -cre <n>] Dispaying hep See Tabe 4 for more information on the ca routing variabes. To dispay hep: 1. Open a PuTTY session and og in as a craft user. 2. Run this command to dispay a ist of a supported commands, cbuti 3. Run the -hep parameter with the command name to dispay hep for a specific command. For exampe, to dispay hep for the Add command: cbuti add -hep Tip: Tip: For more information on configuring cbuti for an in-service depoyment, see Configuring the teephone number branding on page 91. Apri

52 Instaing Meeting Exchange software Making a ca To make a ca to the server, downoad a SIP softphone from the Avaya Website. If you aready have a SIP softphone instaed, it is important to uninsta it before you insta the Avaya SIP softphone. The Avaya SIP softphone is caed one-x Desktop Edition. For more information about Avaya one-x Desktop Edition, incuding software downoads and supporting documentation, see Avaya one-x Desktop Edition. At this stage of the instaation, you can connect the Avaya one-x Desktop Edition directy to the Meeting Exchange server. Later in the instaation, when you configure the Avaya Aura Teephony Server or other interoperabiity requirements, you wi oose this direct connectivity between the Avaya one-x Desktop Edition and the Meeting Exchange server. It is important to note that this first ca is simpy a check to carify that the server can receive cas. It is a basic test. The roe of this test is to enabe you to rue out basic connectivity as an issue if you run into probems ater in the instaation or configuration. The settings that you configure to enabe this test ca are not the settings that your depoyment wi use when the instaation is compete. It is aso important to note that if you are instaing a S6800 or a Distributed S6200, this test ca does not vaidate your instaation. For S6800 and Distributed S6200 depoyments, you must compete a configuration steps in order to pace an effective test ca. The reason that the test ca does not vaidate instaations of S6800 or Distributed S6200 is that when Avaya ships the Meeting Exchange soution, they configure it for an S6200 depoyment, by defaut. To make a ca: 1. Downoad and insta the Avaya one-x Desktop. On the Instaation Wizard, there is no need to seect Enabe Buetooth Integration. 2. Once the instaation competes, seect the Settings button on the Avaya one-x Desktop dashboard. 3. At this stage, there is no need to configure most of the settings. You can accept the defaut vaues. However, the foowing settings are important: On the Account pane, enter a name and an e-mai address. At this stage, the server does not authenticate these detais so you can enter any name and any e-mai address. 52 Administering Meeting Exchange Servers

53 Configuring and testing the instaation Figure 8: Avaya one-x Desktop Account Pane On the Servers pane, seect Use Peer-to-Peer Communication. Figure 9: Avaya one-x Desktop Servers Pane Apri

54 Instaing Meeting Exchange software On the Profie pane, create a new profie. Regardess of your connection, ensure that you seect Loca Area Network from the Connection drop-down ist. This seection ensures that the server uses the G.711 codec, which Meeting Exchange supports. Figure 10: Avaya one-x Desktop Profie Pane Advanced: On the Advanced pane, seect Use UDP. 54 Administering Meeting Exchange Servers

55 Configuring and testing the instaation Figure 11: Avaya one-x Desktop Advanced Pane 4. Save the profie settings. 5. Restart Avaya one-x Desktop. To propery exit Avaya one-x Desktop, you must right-cick and seect Exit on the Avaya one-x Desktop icon in the system tray at the bottom right of your screen. 6. Open a PuTTY session and og in as a craft user. 7. Run the foowing command: cbuti ist For more information see, Configuring ca branding on page Seect a DNIS and make a note of it. 9. On the Avaya one-x Desktop dashboard, enter the DDI and Meeting Exchange server IP address in the Enter Name or Number fied. Use the foowing syntax to make the ca: <DDI>@<Meeting Exchange server IP address> Avaya one-x Desktop sends a SIP Invite to the Meeting Exchange server. If the ca is successfu, you shoud hear the defaut Wecome message audio prompt. Apri

56 Instaing Meeting Exchange software Instaing Bridge Tak Avaya Bridge Tak is a software appication which presents a goba view of the Meeting Exchange system. Avaya Bridge Tak enabes operators to schedue conferences, record messages, and manage ive conferences. The Bridge Tak instaation wizard shoud be on the Meeting Exchange instaation CD or in the Meeting Exchange instaation foder. Contact your Avaya Support Representative for more information on how to downoad Avaya Bridge Tak. To compete the Bridge Tak instaation and configuration, you must aso perform two further tasks: Configuring server resources Configuring server ogins Once you compete these two tasks, you can use Avaya Bridge Tak. For more information on Bridge Tak, see Using Meeting Exchange, which is avaiabe on support.avaya.com. Configuring server resources On the Meeting Exchange server, you must configure Fexibe Digita Auxiiary Port Interface (FDAPI) resources. An FDAPI resource is a permanant ink between the Meeting Exchange server and an operator or an API connection. You must configure an FDAPI resource for each operator in your depoyment. You need an FDAPI resource for each concurrent operator. You must aso configure an FDAPI resource for each API connection in your depoyment. Many components of Meeting Exchange, such as the Avaya Cient Registration Server, the Avaya Web Porta, or Avaya Bridge Tak, connect to the Meeting Exchange server using an API connection. You need an FDAPI resource for every appication which uses an API connection to communicate with the Meeting Exchange server. FDAPI resources are simiar, in concept, to teephone ines. FDAPI resources enabe operators to manage the Meeting Exchange server, record conferences, pay music fies, and so on. Each FDAPI resource reduces the number of avaiabe conference teephone ines (ports). For exampe, if a customer purchases 500 ports and requires 10 FDAPI resources, the number of ports avaiabe for conferencing is 490. In a Time Division Mutipexing (TDM) depoyment, FDAPI resources are phyica ines. In a Voice over IP (VoIP) depoyment, FDAPI resources are virtua ines. To configure an FDAPI resource: 1. Combine the number of concurrent operators and the number of API connections in your depoyment to cacuate the number of FDAPI resources that you require. 2. Log in to Meeting Exchange as dcbmaint. 56 Administering Meeting Exchange Servers

57 Configuring and testing the instaation 3. From the System Maintenance Main Menu, seect FDAPI Configuration. 4. On the Fex-DAPI Configuration screen, enter the number of FDAPI resources that you require in the Operators fied. 5. Navigate to ESC. 6. Seect Y to save changes. 7. Restart the server. Configuring server ogins As described in Configuring server resources on page 56, FDAPI resources are operators and API connections. For each of these operators and API connections, you must configure a ogin account on the Meeting Exchange server. This ogin account enabes operators and Meeting Exchange components, using API connections, to communicate with the Meeting Exchange server. These ogin accounts are not Linux accounts. They simpy enabe Meeting Exchange access for operators and other Meeting Exchange components, such as the Avaya Cient Registration Server, the Avaya Web Porta, or Avaya Bridge Tak. There are four eves of accounts. For more information on these four eves, see Creating sign-ins to Meeting Exchange on page 72. For API connections and operator channes, you can choose between any of four eves of access. To configure a ogin account: 1. Log in to Meeting Exchange as dcbmaint. 2. From the System Maintenance Main Menu, seect Administrator Menu. 3. From the System Administrator Main Menu, seect Sign-in Management. 4. On the System Sign-in Management screen, configure the ogin accounts as required. For each account, you must enter: A sign-in name Password Teephone Number 5. Navigate to ESC. 6. Seect Y to save changes. 7. Restart the server. Apri

58 Instaing Meeting Exchange software Configuring SNMP Simpe Network Management Protoco (SNMP) is a system of aarms which monitors the performance of the server. These aarms are caed traps. For a number of Meeting Exchange processes, you can configure a performance threshod and when that process exceeds this performance threshod, the server emits an SNMP trap. To enabe SNMP functionaity, you must: Configure an SNMP trap destination IP address. This is the IP address to which the server sends the trap. You can aso configure SNMP to create an aert e-mai or to automaticay raise a support request. Provide the customer with the Meeting Exchange Management Information Base (MIB). This fie is contained in the /usr/ipcb/config foder. The MIB defines the database rues that Avaya has deveoped for Meeting Exchange. Tip: For Tip: more information about SNMP, see Configuring aarms on page 205. Configuring automatic backups Meeting Exchange is pre-configured with a number of back-up scripts which automaticay create back-up fies for the various databases. These scripts require no configuration. However, one back-up fie, caed backup.sh requires manua configuration. backup.sh creates a arge number of back-up fies, such as ca detai record fies, biing fies, and configuration fies. Avaya recommends running this fie at east once before you eave a customer site foowing the instaation of the audio conferencing server. backup.sh is ocated in the foowing foder. You must run the script from this ocation: /usr/dcb/bin backup.sh stores back-up fies for 30 days in the foowing foder: /usr3/backups/autobackups You can perform the foowing tasks: Viewing a ist of the fies that backup.sh supports Configuring backup.sh 58 Administering Meeting Exchange Servers

59 Configuring and testing the instaation Viewing a ist of the fies that backup.sh supports You can foow these steps to view a og of the fies that backup.sh supports. These steps do not refer to viewing the actua backed-up fies. 1. Open a PuTTY session and og in as an sroot user. 2. Navigate to /usr/dcb/backup.og. You can view some of the fies that are backed-up. Aternativey, you can use a command to view more detais: tar -z -tvf <fiename> Configuring backup.sh To configure backup.sh. more 1. Open a PuTTY session and og in as an sroot user. 2. Using the crontab -e command, run backup.sh using the foowing syntax. This command requires a vi Editor * * * /usr/dcb/bin/backup.sh > /usr/dcb/backup.og In this exampe, the server wi create a back-up at 02:00, every day (*), every week (*), every month (*). In other words, on a daiy basis, at 02:00, the server wi create a back-up. In this exampe, the command redirects the back-up fies to another foder. Figure 12 shows this exampe. If you run the script more than once in a 24 hour period, it overwrites the previous og. Figure 12: Backup.sh Apri

60 Instaing Meeting Exchange software 60 Administering Meeting Exchange Servers

61 Chapter 5: Configuring the Meeting Exchange appication server This chapter describes how to configure Meeting Exchange to fit the requirements of your network. It contains the foowing sections: Tips for using this document Matching Meeting Exchange to the speed of the network Customizing Meeting Exchange properties Customizing the scheduer utiity Creating sign-ins to Meeting Exchange Note: Note: To successfuy perform the steps described in this chapter, you must first insta Meeting Exchange. For more information on how to insta Meeting Exchange, see Instaing Meeting Exchange software on page 31. Tips for using this document If you are configuring Meeting Exchange and require information, there are a coupe of ways of ocating the information you require: Finding parameters by name on page 269 contains a detaied ist of a configuration settings which you can configure within each of these menus. If you know the name of the parameter that you want to configure, you can use the Adobe Reader search option to ocate a detaied description of each parameter. For exampe, search for the parameter name Annunciator Deay to find the information you require to specify the pause before Meeting Exchange pays a message to an incoming teephone ine. Configuration task ist on page 265 contains a ist of Meeting Exchange configuration tasks. If you do not know the name of the parameter that you want to configure, you can use the Adobe Reader search option to ocate the information you require. For exampe, search for a term such as pay a message to find the information you require to specify the pause before Meeting Exchange pays a message to an incoming teephone ine. Apri

62 Configuring the Meeting Exchange appication server Matching Meeting Exchange to the speed of the network A customer s network can be a megabit network or a gigabit network. It is important to know which type of network the customer is running because the network type impacts the data transmission speeds. When Avaya ships Meeting Exchange to a customer site, Avaya configure it to fit to a 100 megabit, fu dupex network. This is the defaut setting. If the customer s network is a gigabit network, you must change this configuration setting. Aso, if a customer has more than 700 teephone ines with a singe connection to the switch, you must change this configuration setting. It is ikey that the Meeting Exchange server wi drop cas if you do not change the defaut megabit setting in a customer site with over 700 ports connected with a singe connection to the switch. Note: Note: Avaya recommends a gigabit network for optimum performance. To change the defaut megabit interface to a gigabit interface: 1. Open a PuTTY session and og to the Meeting Exchange server as a craft user. PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid craft password. 2. Enter the command: su - sroot This command aocates more permissions. It requires a password. To obtain the sroot password, pease contact your Avaya Support Representative. 3. Navigate to the foowing directory: cd /etc/sysconfig/network-scripts s -s ifcfg* 4. Edit the ETHTOOL_OPTS fied in each of the foowing three fies, which correspond to three ethernet ports: ifcfg-eth0 idcfg-eth2 ifcfg-eth3 In each of these fies, for a gigabit network, the ETHTOOL_OPTS fied shoud have the foowing vaue: ETHTOOL_OPTS="speed 1000 dupex fu autoneg on" Note: Note: In your depoyment, you may not be using each of these ethernet ports, but Avaya recommends updating each of the fies for consistency. 62 Administering Meeting Exchange Servers

63 Customizing Meeting Exchange properties 5. In the customer network, ensure that the ports on the switch are aso configured to match the settings on the Meeting Exchange server. In other words, ensure that the ports on the customer switch are set to gigabit, fu dupex, with autonegotiation (autoneg) set to on. These settings ensure that the customer network can estabish a ink to the Meeting Exchange server. 6. Verify that there are no customizations in the rc.oca fie. The rc.oca fie is in the etc/rc.d foder on the Meeting Exchange server. Customers often use the rc.oca fie to impement some additiona network customizations. If customers have added configurations to the rc.oca fie, these settings may override the settings in the ifcfg-eth0, ifcfg-eth2, and ifcfg-eth3 fies. An exampe customization from an rc.oca fie: ethtoo -s eth0 autoneg on 7. Reboot the server. Customizing Meeting Exchange properties This section describes how to customize the Meeting Exchange properties to match the customer s requirements. Before you customize the conferencing properties, it is a good idea to enabe or disabe the conferencing features using the featcfg command. Avaya recommend configuring the featcfg features first because if you disabe certain feature using featcfg, their corresponding configuration properties do not dispay in the Meeting Exchange System Configuration screens. For more information on using the featcfg command, see Feature List on page 355 and Enabing features on page Log in to Meeting Exchange as dcbadmin to dispay the System Administration Main Menu. Figure 13 dispays the System Administration Main Menu. Apri

64 Configuring the Meeting Exchange appication server Figure 13: System Administration Main Menu Screen 2. From the System Administrator Main Menu, seect Configurations. Figure 14: Configurations Screen The Configurations screen provides you with an entry point for the customization of a of the conferencing properties. 64 Administering Meeting Exchange Servers

65 Customizing Meeting Exchange properties 3. Use the Configurations screen to customize the conferencing properties to match the customer s requirements. Tabe 5 describes how Avaya has divided the conferencing features into a number of sections. To access these sections, you must access a sub-menu item on the Configurations screen. Tabe 5: Configuration Sections Menu Item Bast Dia Configuration CDR Configuration CODR Configuration Ca Routing Configuration Operator Configuration Description Use the Bast Dia Configuration option to specify how Meeting Exchange processes bast dia cas. In a bast dia, the Meeting Exchange simutaneousy dias an entire ist of phone numbers to estabish a conference. When conferees answer the ca, the Meeting Exchange prompts them to press specific digits on their teephones to join the conference without operator assistance. Tabe 51 describes each of the Bast Dia Configuration options. Use the CDR Configuration option to specify the content and format for ca detais in the CDR reports that Meeting Exchange produces. Tabe 52 describes each of the CDR Configuration options. Use the CODR Configuration option to specify the content and format for ca detais in the CODR reports that Meeting Exchange produces. Tabe 53 describes each of the CODR Configuration options. Use the Ca Routing Configuration option to specify how Meeting Exchange processes incoming cas based on DNIS and DDI parameters. To successfuy customize the ca routing feature, you must aso configure the cbuti fie. For more information on the cbuti fie, see Configuring the teephone number branding on page 91. In addition, Tabe 54 describes each of the Ca Routing options. Use the Operator Configuration option to specify a number of detais for the operator ines. To successfuy customize the operator ines, you must configure the number of ines that you require, using the FDAPI Configuration Menu. For more information about the FDAPI Configuration Menu, see Configuring server resources on page 56. In addition, Tabe 56 describes each of the Operator Configuration options. 1 of 2 Apri

66 Configuring the Meeting Exchange appication server Tabe 5: Configuration Sections (continued) Menu Item Supervision Configuration System Configuration Timed Assist Configuration Voice Message Configuration Warning Tone Configuration Description Use the Supervision Configuration option to specify a number of detais in reation to how Meeting Exchange handes disconnected ines. Use this menu aso to specify a number of timing deays, such as the deay before Meeting Exchange pays an audio prompt to an incoming ine. Tabe 57 describes each of the Supervision Configuration options. Use the System Configuration option to specify a arge number of diverse Meeting Exchange settings. This is the argest menu within the Configurations screen. You can use it to configure properties, such as whether the system is abe to aocate additiona teephone ports or time conferences whie they are in progress or whether participants can enter conferences earier. Tabe 58 describes each of the System Configuration options. Use the Timed Assist Configuration option to estabish time-based rues for deivering operator hep to participants. Tabe 59 describes each of the Timed Assist Configuration options. Use the Voice Message Configuration option to specify whether Meeting Exchange pays a tone, a voice message, or both to: Notify participants of conference events Provide instructions for conference functions Announce how much time is eft in a conference For more information on audio messages, see Configuring audio messages on page 151. In addition, Tabe 60 describes each of the Voice Message Configuration options. Use the Warning Tone Configuration to specify how often warning tones sound during the ast 15 minutes of an unattended conference to notify participants that the conference is about to end. 2 of 2 Customizing the scheduer utiity The Conference Scheduer appication is a command ine utiity that Avaya provides to enabe you to configure a arge number of settings for conferences, such as how ong to retain conference records and the number of avaiabe ines for on-demand conferences. You can 66 Administering Meeting Exchange Servers

67 Customizing the scheduer utiity access the Conference Scheduer appication by ogging into Meeting Exchange as a dcbadmin and navigating to System Administrator Main Menu > Configure Scheduer. The vaues that you configure using the Conference Scheduer appication are goba vaues. An optiona Externa Passcode Vaidation (EPV) feature enabes Meeting Exchange to vaidate passcodes and Persona Identification codes (PIN codes) on an externa server. With EPV enabed, you can integrate Meeting Exchange into a distributed audio conference infrastructure where you can use externa servers to schedue conferences. In this configuration, you can store conference parameters on externa databases. If you decide to impement a Meeting Exchange soution that invoves EPV, you must disabe the Conference Scheduer appication. To disabe the Conference Scheduer appication, configure the Status parameter, as described in Tabe 6. To customize conference parameters: 1. Log in to Meeting Exchange as dcbadmin to dispay the System Administration Main Menu. 2. From the System Administrator Main Menu, seect Configure Scheduer. 3. Use the Configure Conference Scheduer screen to customize the conferencing properties to match the customer s requirements. Tabe 6 describes the configuration settings. Tabe 6: Conference Scheduer Configuration Parameters Menu Item Group Name Status Invaid Code Description This is a non-editabe fied with the vaue schedue. Specifies whether the Conference Scheduer is used. Enabed Meeting Exchange uses the conference scheduer vaues. Disabed (defaut) Meeting Exchange does not use the conference scheduer vaues. When using EPV, aways disabe the conference scheduer vaues to prevent oca schedues from being used. If you disabe the Scheduer and are not using EPV, Meeting Exchange routes a cas to the ENTER queue. The Meeting Exchange response to participants who enter an invaid passcode. The Scan Time parameter specifies the aowed time. There are two vaues: ENTER (defaut) The participant is paced in the Enter Conference to wait for operator assistance. Hang-up The system disconnects the caer. 1 of 6 Apri

68 Configuring the Meeting Exchange appication server Tabe 6: Conference Scheduer Configuration Parameters (continued) Menu Item Timeout Conference Secured Max. Lines Reached Invaid Time of Day Scan Time Scan Attempts Description The Meeting Exchange response to participants who do not enter the digits within the time aowed. The Scan Time parameter specifies the aowed time. ENTER (defaut) The participant is paced in the Enter Conference to wait for operator assistance. Hang-up The system disconnects the caer. Caers using rotary stye teephones cannot enter digits and consequenty aways time out. The Meeting Exchange response to participants who enter invaid passcodes for conferences that have been secured by a moderator. Enter (defaut) The participant is paced in the Enter Conference to wait for operator assistance. Hang-up The system disconnects the caer. Moderators press *7 on their teephone keypad to secure a conference. The Meeting Exchange response to participants who enter vaid passcodes for conferences that aready contain the specified maximum number of ines. Enter (defaut) The participant is paced in the Enter Conference to wait for operator assistance. Hang-up The system disconnects the caer. Operators specify the maximum number of ines when they schedue a conference. The Meeting Exchange response to participants who enter a vaid code at the wrong time, for exampe by attempting to enter a conference too eary or too ate. Enter (defaut) The participant is paced in the Enter Conference to wait for operator assistance. Hang-up The system disconnects the caer. The number of seconds that Meeting Exchange scans for code digits entered by caers. The defaut is 10 seconds. The vaid time range is between 5 to 20 seconds. Be sure to aow an adequate scan time for engthy codes. Caers can press the pound key (#) after entering their code to immediatey enter the conference without waiting for the fu scan time to eapse. Specifies the number of times that Meeting Exchange prompts for a passcode. The possibe vaues are 1, 2, or 3 (defaut) times. 2 of 6 68 Administering Meeting Exchange Servers

69 Customizing the scheduer utiity Tabe 6: Conference Scheduer Configuration Parameters (continued) Menu Item Auto Hang-up Warning Tones Originator Dia Out Description Specifies whether Meeting Exchange disconnects a ines when the conference duration expires. Enabed Meeting Exchange disconnects a ines when a conference duration expires. A ines become immediatey avaiabe. This feature is especiay important in a depoyment in which there are no operators. Another parameter, the Auto Extend Duration parameter enabes moderators to extend their conferences up to 100 minutes beyond the specified end time. Disabed (defaut) The system does not automaticay disconnect a ines. For more information on the Auto End Duration parameter, see System configuration properties on page 298. Specifies whether Meeting Exchange pays warning tones to remind participants that conference time is about to expire. Enabed Meeting Exchange pays warning tones before disconnecting conference ines. To pay warning tones, you must enabe the Auto Hang-up parameter. Disabed (defaut) Meeting Exchange does not pay warning tones before disconnecting conference ines. The frequency with which tones are sounded is specified by the Warning Tone Configuration menu. For more information, see Warning Tone configuration on page 317. Defines whether moderators can use their teephones to access an open ine for dia out and add participants to an active unattended conference. This is usefu for contacting participants who cannot dia into the conference. Disabed (defaut) Moderators cannot dia out of secured or unsecured conferences. Unsecured Unattended moderators of unsecured conferences can access free ines for dia out, if sufficient channes are avaiabe based on the conference reservation. A Moderators can dia out for both secured and unsecured conferences. Note: Note: This setting ony appies to fexfow conferences. A fexfow conference is a specific type of demand conference. In fexfow conferences, a ca routing is based on the conferee passcode. In addition to the conferee passcode, moderators enter a moderator passcode, which grants access to a moderator-specific menu. 3 of 6 Apri

70 Configuring the Meeting Exchange appication server Tabe 6: Conference Scheduer Configuration Parameters (continued) Menu Item Automatic Security Codes Conference Retention Overbooking (%) Description Specifies whether Meeting Exchange automaticay assigns security codes to conferences. The vaues for this parameter are: The number of digits for the code, between 7 and 16 Meeting Exchange automaticay assigns both conferee and moderator passcodes to a conference when it is created. For exampe, if you enter 7, Meeting Exchange assigns unique 7-digit passcodes to conferences. Operators and moderators can modify the passcodes that Meeting Exchange assigns. Disabed (defaut) conferee and moderator passcode fieds remain bank. Operators and moderators must specify codes for conferences. Sets the number of weeks that Meeting Exchange retains conference records. 1 to 52 (defaut) The number of the most recent weeks for which you want to retain conference records. For exampe, if you want to retain conference records from the ast ten weeks, enter 10 for this parameter. 0 Do not retain any records expired as of midnight of the previous day. For more information on conference reports, see Accessing reports using the Meeting Exchange System Administrator main menu on page 111. Specifies the percentage of Meeting Exchange ines that operators and moderators can overbook for schedued conferences. This parameter does not impact on-demand conferences. 1% to 100% With overbooking, operators and moderators can reserve a percentage from 1% to 100% more than the maximum number of ines avaiabe for a given time period. Lines configured for operators, music, record/payback, or ink ines are not incuded in the ine count. For exampe, if your depoyment of Meeting Exchange has 1000 ines avaiabe for schedued conferences and you set this parameter for 10%, you can schedue 1100 ines. 0 (defaut) Meeting Exchange aows infinite conference overbooking. To view this parameter on the Configure Conference Scheduer screen, you must enabe it using the featcfg function. For more information on featcfg, see Enabing features on page 43 and Feature List on page of 6 70 Administering Meeting Exchange Servers

71 Customizing the scheduer utiity Tabe 6: Conference Scheduer Configuration Parameters (continued) Menu Item On-Demand Pct (%) Conf. Name Required Fex Short Time Fex Short Attempts Fex Long Time Fex Long Attempts Fex Minimum Dia Out Digits Fex Maximum Dia Out Digits Description Specifies the percentage of Meeting Exchange ines avaiabe for on-demand conferences, which are unattended conferences that can be convened on an ad hoc, first-come, first-served basis. The remaining percentage of Meeting Exchange ines is designated for reguary schedued conferences. The defaut is 0, which means that no ines are avaiabe for on-demand conferences. Specifies whether Meeting Exchange requires a conference name for each conference. Operators and moderators provide conference names when they schedue conferences. Enabed Meeting Exchange requires a conference name. Disabed (defaut) Meeting Exchange does not require a conference name. Defines the number of seconds, 3 20, that Meeting Exchange gives participants for entering a singe DTMF digit. The defaut is 5. Note: Note: This setting and the foowing settings with Fex in their tite ony appy to fexfow conferences. A fexfow conference is a specific type of demand conference. In fexfow conferences, a ca routing is based on the conferee passcode. In addition to the conferee passcode, moderators enter a moderator passcode, which grants access to a moderator-specific menu. Specifies the number of attempts, 1 5, that Meeting Exchange gives participants for entering a singe DTMF digit. The defaut is 3. Specifies the number of seconds, 5 60, that Meeting Exchange gives participants for entering a sequence of DTMF digits. The defaut is 40. Specifies the number of attempts, 1 3, that Meeting Exchange gives participants for entering a sequence of DTMF digits. The defaut is 1. Specifies the minimum number of digits that Meeting Exchange aows for a dia out. The defaut is 4, the maximum is 99. Specifies the maximum number of digits that Meeting Exchange aows for a dia out. The defaut is 4, the maximum is of 6 Apri

72 Configuring the Meeting Exchange appication server Tabe 6: Conference Scheduer Configuration Parameters (continued) Menu Item Fex Leader Pin Modify NRP-Oper Timeout (Last Attempt) This setting does not appy to fexfow conferences. Description Defines whether Meeting Exchange aows moderators to modify their moderator passcode using the DTMF commands on their teephone keypad. Enabed (Defaut) The moderator can modify the moderator passcode by pressing 2 on a teephone keypad to access the Defaut Conference Options menu before the conference starts. Disabed The moderator cannot modify the moderator passcode in the Defaut Conference Options menu before the conference starts. The minimum moderator passcode ength is set to 4. The maximum ength is set to 16. The audio prompt message that Meeting Exchange pays to moderators when they are modifying their moderator passcode refers to the minimum and maximum ength vaues. When Name Record/Payback is set to OPER in the conference scheduer, this setting specifies where Meeting Exchange paces a participant who fais to press # after recording their name. Conf (Defaut) Meeting Exchange paces participants who record a name, but who do not press #, into the conference. Enter Meeting Exchange paces participants who record a name, but who do not press #, into the Enter queue. 6 of 6 Creating sign-ins to Meeting Exchange A sign-in consists of a ogin name and a password created for a Bridge Tak user. The priviege eve for a sign-in specifies which Bridge Tak resources that sign-in can use and what management interface menus the sign-in can access. Users with the higher-eve sign-ins can access more resources than users with ower-eve sign-ins. This section describes how to create, modify, and deete user sign-ins. You must create sign-ins for operators who supervise attended conferences using Bridge Tak. A short note about sign-ins Creating sign-ins Viewing and deeting sign-ins 72 Administering Meeting Exchange Servers

73 Creating sign-ins to Meeting Exchange A short note about sign-ins Tabe 7 ists and describes sign-ins eves. Tabe 7: Sign-In Leves and Privieges Sign-In Leve Maintenance Administrator Operator Scheduer Privieges Access to a Bridge Tak resources and management interface options, incuding maintenance, administrator, operator, scheduer tasks, and network configuration. Access to a Bridge Tak resources and administrator-eve management interface options. Access to Bridge Tak operator tasks ony. No access to the System Administrator menu. Access to the Bridge Tak Scheduer appication. Creating sign-ins You must have maintenance or administrator privieges to create sign-ins. A maintenance-eve user can create, deete, and view a sign-ins. An administrator-eve user can create and deete administrator sign-ins and a ower-eve sign-ins. To create sign-ins: 1. Log in to Meeting Exchange as dcbadmin or dcbmaint. 2. Navigate to the System Administration Main Menu. 3. From the System Administrator Main Menu, seect Sign-In Management. Meeting Exchange dispays the System Sign-In Management menu. The menu varies depending on your your sign-in eve. 4. Seect the sign-in eve option you want to create. 5. Enter vaues for: Sign-In Name. Sign-in names can be up to eight characters in ength and can incude ony etters and numbers. Password Teephone number. This is an optiona fied. Do not use underscores (_), hyphens (-), spaces, or other specia characters in the sign-in name or password fied. These two fieds are case-sensitive. For exampe, ee, Lee, and Apri

74 Configuring the Meeting Exchange appication server LEE represent three different sign-in names. You cannot use identica sign-in names, but different sign-in names can have identica passwords. 6. Save your input. Meeting Exchange creates the sign-in. 7. Restart the server. Viewing and deeting sign-ins Maintenance eve users can view and deete a sign-ins on the system. To dispay sign-ins: From the System Sign-In Management menu, seect View/Deete Current Sign-In. Meeting Exchange dispays the current sign-ins. To deete a sign-in 1. Dispay the current sign-ins. 2. Highight the sign-in that you want to deete. 3. Press ENTER. A confirmation message appears. 4. To deete the sign-in you seected, press Y. Press N or ESC to cance the deetion. If you press Y, Meeting Exchange dispays a confirmation message and deetes the sign-in. 74 Administering Meeting Exchange Servers

75 Chapter 6: Configuring the Meeting Exchange media server The media server component of Meeting Exchange provides a number of functions, such as, audio mixing, Dua Tone Muti Frequency (DTMF) detection, message paying, and conference recording. There are two types of media server: The S6200 and the S6800. Meeting Exchange 5.2 uses a number of features from the Avaya Common Media Server. These features reduce depoyment risks and increase the predicabiity of the server performance. There are no changes required in the instaation and configuration of the servers. This chapter describes the features from the Avaya Common Media Server. It aso describes how to configure the media server. To successfuy depoy the media server, you must configure three fies: audiopreferences.cfg, system.cfg, and softmediaserver.cfg. Avaya Common Media Server features Configuring codecs Configuring the system settings Configuring the media settings Apri

76 Configuring the Meeting Exchange media server Avaya Common Media Server features Meeting Exchange 5.2 contains a number of new features, which are reated to the Avaya Common Media Server. Tabe 8 describes these new features. Tabe 8: New Media Server Features Name Support for the foowing codecs: G.729 G.726 G.722 ilbc Rea Time Transport Contro Protoco (RTCP) and Rea Time Transport Contro Protoco extended Reports (RTCP-XR) Secure Media Rea-time Transport Protoco (SRTP) Media oop back Easier configuration of diaing patterns Description These codecs encrypt and decrypt the digita audio transmissions on Meeting Exchange channes. For more information on configuring codecs, see Configuring codecs on page 76. RTCP provides out-of-band statistics and contro information for an RTP fow. RTCP XR suppements the statistics that are contained in the standard RTCP report. SRTP defines a profie of RTP (Rea-time Transport Protoco), intended to provide encryption, message authentication, and integrity, and repay protection to data. Meeting Exchange now supports this protoco for a audio and data transfers. For more information, see Configuring secure rea-time transport protoco (SRTP) on page 183. Using the media oopback mechanism, Meeting Exchange activey monitors the media deivery performance by ooping media back to the transmitter. This active monitoring provides vauabe audio quaity statistics for use in diagnosing any audio issues. System administrators can now update the tabes which transate between teephone numbers and URIs without restarting the server. For more information, see Configuring diaing patterns on page 93. Configuring codecs In a singe server S6200 depoyment, your codec choices have impications for the capacity of Meeting Exchange because some codecs use a arge amount of system resources. For 76 Administering Meeting Exchange Servers

77 Configuring codecs exampe, a singe ca using the ILBC codec uses the equivaent of approximatey 15 G.711 cas. It is important to note that Meeting Exchange sti treats the ca as a singe ca in terms of port aocation. If you need to support mutipe codecs in a singe server S6200 depoyment, Avaya recommends making the foowing changes to the system.cfg fie. The system.cfg fie is ocated in /usr/ipcb/config/system.cfg. The changes invove adjustments to the CoreAffinity parameter. After an instaation or an upgrade, the CoreAffinity parameter is not incuded in the system.cfg fie, by defaut. You must add it. You must aso make some changes to the processtabe.cfg fie by adding or removing ines, depending on the number of softms required. The processtabe.cfg fie is ocated in / usr/ipcb/config. Note: On an S6200, using G.711: - Configure the processtabe.cfg to use 6 softms - Configure the system.cfg vaue CoreAffinity=FC (use cores 2 to 7) On an S6200, using ony one codec, other than G.711: - Configure the processtabe.cfg to use 8 softms - Configure the system.cfg vaue CoreAffinity=FF (a avaiabe cores) On an S6200, using mutipe codecs with ess than 800 cas: - Configure the processtabe.cfg to use 8 softms - Configure the system.cfg vaue CoreAffinity=FF (a avaiabe cores) On an S6200, using mutipe codecs with more than 800 cas: - Configure the processtabe.cfg to use 7 softms - Configure the system.cfg vaue CoreAffinity=FE (use cores 1 to 7) Note: If you need to support mutipe codecs in your depoyment, you must aso configure the MaxChanneCount parameter in system.cfg. Contact your Avaya Support Representative for assistance in seecting an appropriate vaue. To configure codecs: 1. Open a PuTTY session and og in as an craft user. Note: Note: PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid craft password. 2. Navigate to /usr/ipcb/config/audiopreferences.cfg. Apri

78 Configuring the Meeting Exchange media server 3. In the audiopreferences.cfg fie, configure the vaues as isted in Tabe 9. Avaya recommends these vaues for a successfu depoyment of Meeting Exchange. Tabe 9: audiopreferences.cfg Parameters mimesubtype payoadtype PCMU 0 PCMA 8 G722 9 G ilbc30 97 ilbc20 98 wbpcmu 102 wbpcma 103 teephone-event 127/120 isac 104 G726_ G726_ G726_ G726_ Note: Note: Note: If you are using this codec, ensure that you set the ptime attribute to 20 for a incoming cas to Meeting Exchange. The ptime attribute reates to the packet size in terms of miiseconds of voice. A ptime of 20 means that each packet contains 20 miiseconds of voice content. Note: The defaut vaue is 101. If your depoyment consists of H.323 endpoints, configure this vaue to 127. If your depoyment consists of H.323 and SIP endpoints, configure this vaue to 120. If you want to disabe a specific codec, remove it from the ist or comment it out using a # 78 Administering Meeting Exchange Servers

79 Configuring the system settings symbo. 4. Restart the server. Configuring the system settings The settings in the system.cfg fie reate to Differentiated Service TOS Vaue (IP TOS) and Ethernet VLAN Vaue (VLAN). In the system.cfg fie, you must aso enter an ethernet ink. Tabe 10 describes the IP TOS and VLAN settings. Tabe 10: IP TOS and VLAN Concept IP TOS VLAN Description TOS is type of service. The TOS vaue is a differentiated service setting for SIP IP packets. Differentiated services attempt to guarantee quaity of service on arge networks, such as the Internet. Using TOS, you can assign priority to certain traffic, such as network-critica traffic. The Ethernet VLAN Vaue structure paces restrictions on traffic fow, permitting traffic to pass among a seect group of network nodes, to the excusion of other network nodes, based on the assigned group membership of individua nodes or switch ports. The VLAN Vaue range is between 0 and 32. The defaut vaue is 0. However, the choice of an appropriate VLAN vaue depends on the network being used and the type of traffic; signaing or media. To configure the SIP signaing IP TOS and VLAN parameters and the ethernet ink: 1. Open a PuTTY session and og in as an craft user. 2. Navigate to /usr/ipcb/config/system.cfg. 3. Configure the parameters as required. For exampe: # diff serv vaues that wi appear on the TOS fied of the IP packet DiffServSignaingTOSVaue=46 DiffServMediaTOSVaue=24 # van vaues EthernetSignaingVanVaue=0 EthernetMediaVanVaue=0 Apri

80 Configuring the Meeting Exchange media server 4. In the same fie, you must aso enter an Ethernet Link ID. This is the interface from which the media server takes connections. You can ist the interfaces in order of priority. For exampe: LinkNetworkDevice=bond0,eth0 5. Save your changes. Configuring the media settings You must configure a number of settings in the softmediaserver.cfg fie. For a compete ist of a the parameters in the fie, see List of softmediaserver.cfg parameters on page 361. Configuring automatic gain contro Configuring comfort noise generation Configuring transport settings Configuring drive settings Configuring the active speaker notification interva Configuring automatic gain contro Automatic Gain Contro (AGC) acts on oud signas to condition them around the specified vaue. Currenty, ow signas or signas beow the target eve are not modified. If you disabe AGC, Meeting Exchange does not reguate voume. Tabe 11 describes the settings reating to AGC. To configure AGC: 1. Open a PuTTY session and og in as an craft user. 2. Navigate to /usr/ipcb/config/softmediaserver.cfg. 3. Configure the settings, as described in Tabe 11. Tabe 11: Parameters Reating to AGC Parameter AutomaticGain agctarget Description The vaid vaues are 0=Off and 1=On. The target power eve during mixing. The vaid vaues are 6dBFS to 20dBFS in 2dBFS steps. 80 Administering Meeting Exchange Servers

81 Configuring the media settings 4. Save your changes. Configuring comfort noise generation Comfort noise generation adds background white noise to a conference to avoid tota sience when none of the participants are taking. If you disabe comfort noise generation, Meeting Exchange does not pay white noise when none of the participants are taking. To configure comfort noise generation: 1. Open a PuTTY session and og in as an craft user. 2. Navigate to /usr/ipcb/config/softmediaserver.cfg. 3. Configure the settings, as described in Tabe 12. Tabe 12: Parameters Reating to Comfort Noise Parameter ComfortNoiseGeneration ComfortNoiseLeve SienceSuppression ConfPayThreshod Description The vaid vaues are 0=Off and 1=On. The eve at which Meeting Exchange pays the comfort noise. The vaid vaues are 0=Off and 1=On. The energy threshod for sience suppression. 4. Save your changes. Configuring transport settings Note: Note: Pease reference the reease notes before configuring these settings. Certain patches to Communication Manager and/or Meeting Exchange may be needed to enabe this functionaity. It is a good idea to configure the packet oss conceament and the channe statistics update. In the softmediaserver.cfg fie, you must aso set TOS and VLAN vaues, as you did in the system.cfg fie. For more information on the system.cfg fie, see Configuring the system settings on page Open a PuTTY session and og in as an craft user. 2. Navigate to /usr/ipcb/config/softmediaserver.cfg. Apri

82 Configuring the Meeting Exchange media server 3. Configure the settings, as described in Tabe 13. Tabe 13: Parameters Reating to Transport Parameter PacketLossConceament ChanneStatisticsUpdate securityenabed srtpcryptosuite srtcpcryptosuite rtcptxintrv EnabeTTY EnabeTTYRedundancy DTMFRegenerationFormat Description The vaid vaues are 0=Off and 1=On. Determines how often Meeting Exchange prints statistics to a fie. To disabe the statistics og, enter 0. Determines whether Meeting Exchange uses SRTP for audio transmission. The vaid vaues are 0=Off and 1=On. Note: Note: For more information, see Configuring secure rea-time transport protoco (SRTP) on page 183. Determines which encryption and authentication agorithms Meeting Exchange uses for SRTP with RTP. For exampe, srtpcryptosuite=aes_cm_128_hmac_sha1_80. Note: Note: For more information, see Configuring secure rea-time transport protoco (SRTP) on page 183. Determines which encryption and authentication agorithms Meeting Exchange uses for SRTP with TCP. For exampe, srtcpcryptosuite=aes_cm_128_hmac_sha1_80. Note: Note: For more information, see Configuring secure rea-time transport protoco (SRTP) on page 183. Determines the minimum RTCP transmission interva in miiseconds. Determines whether Meeting Exchange supports the text teephone feature for the hearing impaired. Determines whether Meeting Exchange supports redundancy for the text teephone feature. Determines whether Meeting Exchange can regenerate DTMF in a specific format. For inband processing, enter 1, for out of band processing, enter 2, and to ensure that the choice is determines by negotiation with Session Description Protoco (SDP), enter Administering Meeting Exchange Servers

83 Configuring the media settings Tabe 13: Parameters Reating to Transport Parameter DefautNetworkInterface DiffServMediaTOSVaue EthernetMediaVanVaue Description Determines which network interface that Meeting Exchange uses. For exampe, defautnetworkinterface=bond0,eth0. Determines the differenciated service on IP packets. The defaut can be 0 or 26. Determines the VLAN service on IP packets. The defaut is Save your changes. Configuring drive settings The drive settings are highy sensitive. Pease consut your Avaya Support Representative for more information about making changes to these fies. The drive settings incude the configuration of the read and write infrastructure, the size of the cache, and the frequency of hard drive access. To configure the drive settings: 1. Open a PuTTY session and og in as an craft user. 2. Navigate to /usr/ipcb/config/softmediaserver.cfg. 3. Configure the settings, as described in Tabe 14. Tabe 14: Parameters Reating to Drives Parameter gobareadcacheminnumbuffers gobareadcachemaxnumbuffers gobareadcachebuffersize Description Defines the minimum number of buffers in the goba cache. For exampe, gobareadcacheminnumbuffers=128. Defines the maximum number of buffers in the goba cache. For exampe, gobareadcachemaxnumbuffers=182. Defines the maximum size of fies in the goba cache. Meeting Exchange stores a fies with a size smaer than this vaue. For exampe, gobareadcachebuffersize= Apri

84 Configuring the Meeting Exchange media server Tabe 14: Parameters Reating to Drives Parameter ocareadcachebuffersize ocawritecachebuffersize Description Defines the size of the oca read cache. The oca read cache is twice this vaue. Meeting Exchange uses a second buffer as a ook ahead buffer. For exampe, ocareadcachebuffersize= Defines the maximum size of the oca cache. Meeting Exchange stores the fies on a disk when the cache reaches this size. For exampe, ocawritecachebuffersize= Save your changes. Configuring the active speaker notification interva By defaut, Meeting Exchange checks each channe every 2000 miiseconds to see if someone is speaking. The active speaker notification interva parameter contros this timer. The active speaker notification parameter is caed asninterva. For exampe, if asninterva is 500, Meeting Exchange checks each channe every 500 miiseconds. The asninterva vaue overrides the defaut vaue on the appication server. To configure the active speaker notification interva setting: 1. Open a PuTTY session and og in as an craft user. 2. Navigate to /usr/ipcb/config/softmediaserver.cfg. 3. Configure the settings, as described in Tabe 15. Tabe 15: Parameter Reating to Active Speaker Notification Interva Parameter asninterva=2000 Description Sets the Active Speaker Notification Interva in miiseconds. It is an int. 4. Save your changes. 84 Administering Meeting Exchange Servers

85 Chapter 7: Configuring externa servers For security and resiience purposes, it is a good idea to store certain essentia fies on externa servers, rather than on the Meeting Exchange appication server. If you use externa servers in the customer site, you can aso provide additiona storage space and free up space on the Meeting Exchange appication server. Externa servers in this type of depoyment are caed Network Fie System (NFS) servers. If you wish to use an NFS server, depending on the type of Meeting Exchange soution, the foowing options are avaiabe to you: If you have a standaone S6200 server, you can store your conference recordings on an externa NFS server. You store a other fies internay, on the Meeting Exchange system. To impement this configuration, foow these steps: Mounting the recording directory on the appication server on page 86. If you have a distributed S6200 server, you can store your conference recordings, conference roster, audio prompts, and wecome messages on an interna NFS server. To impement this configuration, foow the steps in Impementing Resiience for Meeting Exchange Guide, which is avaiabe on support.avaya.com. If you have a distributed S6200 server, you can store your conference recordings on an externa NFS server and you store a other fies on an interna NFS server. To impement this configuration, foow the steps in Impementing Resiience for Meeting Exchange Guide, which is avaiabe on support.avaya.com and then Mounting the recording directory on the appication server on page 86. Typicay, externa NFS servers provide more robustness than interna NFS servers which reside on the appication server. The Impementing Resiience for Meeting Exchange Guide, which is avaiabe on support.avaya.com contains more information about NFS functionaity. It aso contains sampe depoyments. It is a good idea to read that information as a background to the current chapter. Fie ocation Typicay, the recordings, prompts, roster, and messages are stored in the foowing directories on the Meeting Exchange appication server. Both the appication server and the media server must reference and access the same fie. For exampe, both servers must view a singe instance of a recording. This is caed a cross-soution consistent view of the directories: usr3/confrp usr2/prompts usr2/roster usr3/confw Apri

86 Configuring externa servers Mounting If there are externa NFS servers in your depoyment, you must make the appication server and the media server aware of the existence of the externa NFS servers. You do this by mounting the NFS servers on the appication server and the media server. The mount command is a simpe Linux command. In Meeting Exchange 5.2 Service Pack 2, the process of mounting the recordings directory is partiay automatic in the foowing way: The media server automaticay mounts the recording directory, usr3/confrp. The appication server does not mount the recording directory and so you must manuay mount it, as described in Mounting the recording directory on the appication server on page 86. This process appies to both standaone and distributed S6200 soutions with an externa NFS server for conference recordings. Mounting the recording directory on the appication server The process of mounting the recording directory on the appication server consists of two tasks: You must update a parameter in system.cfg on each appication server. You must use the Linux mount command to mount the NFS directory. When you compete these two tasks and restart Meeting Exchange, the appication server generates an Inter Process Communication (IPC) event and sends it to the media server, by way of a program caed Server Comms. The Server Comms program transates the IPC event into a format that the media server can interpret. IPC events are interna and Server Comms makes them externa. Essentiay, the Server Comms program transates the IPC event into a Transmission Contro Protoco (TCP) event. In this way, the appication server communicates the ocation of the recordings to the media server(s). The media server receives the TCP event and automaticay mounts the NFS server. The media server mounts the NFS server using the information provided by the system.cfg fie that you updated on the appication server. To mount the recording directory on the appication server and any standby appication servers: 1. Open a PuTTY session and og in as a craft user. 2. Enter the command: su sroot 86 Administering Meeting Exchange Servers

87 Mounting the recording directory on the appication server 3. Enter the foowing command to navigate to the system.cfg fie: cd /usr/ipcb/config cat system.cfg 4. Enter the IP address of the NFS server in the nfsconfrecordingip parameter in system.cfg. 5. Save the fie. 6. Enter the foowing command to navigate to the fstab fie: cd /etc 7. Set the mount options in /etc/fstab to those specified by the parameter nfsmountoptions in system.cfg. This parameter defauts to the foowing: -t_nfs_-o_rw,async,bg,soft,tcp,noac 8. Save the fie. 9. Enter the foowing command to mount the directory and restart Meeting Exchange: mount /usr3/confrp service mx-bridge restart Apri

88 Configuring externa servers 88 Administering Meeting Exchange Servers

89 Chapter 8: Branding the customer experience This chapter describes how to configure Meeting Exchange to provide conference participants with a different conferencing experience, based on the teephone number they used to access the conference. Conferencing experience consists of audio messages, anguages, and conference ca fow. This chapter aso describes how to configure Meeting Exchange to interpret the teephone numbers that participants use to dia a conference and the teephone numbers that participants use to dia out from a conference to another potentia participant. Avaya refers to these mechanisms as ca routing. To configure ca routing, you must customize a number of fies in your depoyment of Meeting Exchange. These fies incude cbuti, tenumtouri, and URItotenum. This chapter contains the foowing sections: A short note on the customer experience Obtaining conference teephone numbers Configuring Meeting Exchange number coection Configuring Meeting Exchange to hande a number it does not recognize Configuring the teephone number branding Configuring reservation groups Configuring diaing patterns A short note on the customer experience As mentioned in the introduction to this chapter, you can configure Meeting Exchange to provide conference participants with a different conferencing experience, based on the teephone number they used to access the conference. Conferencing experience consists of audio messages, anguages, and conference ca fow. For exampe, a company can provide each department in the company with a different teephone number for conference access. Meeting Exchange wi pay a different message to each of the departments, such as "Wecome to the Engineering Department Conference System", "Wecome to the Saes Department Conference System", "Wecome to the Finance Department Conference System", and so on. Service providers can use this feature to customize the conferencing experience for each of the companies which avai of their conferencing service. Simiary, service providers and companies can use this feature to pay audio messages in different anguages to their customers. For more information on recording Apri

90 Branding the customer experience audio messages, see Recording new audio messages on page 155. This feature is caed ca branding or ca routing. Meeting Exchange 5.2 supports 30,000 entries for ca branding. When you instaed Meeting Exchange, you configured a basic ca routing entry in order to execute your test ca. For more information, see Configuring ca branding on page 44. This chapter describes how to configure ca routing for the in-service operation of your Meeting Exchange depoyment. Obtaining conference teephone numbers Your customer shoud provide the teephone numbers which they wish to use for conferencing. These teephone numbers shoud be diaed number identification service (DNIS) numbers. In some regions, DNIS numbers are caed direct dia inward (DDI) numbers. Configuring Meeting Exchange number coection To configure the number of digits that Meeting Exchange seects from the fu DNIS: 1. Log in as a dcbadmin User to access the System Administrator Main Menu. 2. Navigate to System Administrator Main > Configurations > Ca Routing Configuration > Digit Parameters. 3. Configure the Number of Digits parameter. For more information on this parameter, see Ca Routing configuration properties on page Save your changes. Configuring Meeting Exchange to hande a number it does not recognize There are two aspects to this configuration. You can configure Meeting Exchange to attempt to make a partia match when it receives fewer digits that it expects. You can aso configure Meeting Exchange to hande DNIS numbers that it does not recognize. Configuring partia matching Configuring the widcard 90 Administering Meeting Exchange Servers

91 Configuring the teephone number branding Configuring partia matching To configure the number of digits that Meeting Exchange seects from the fu DNIS: 1. Log in as a dcbadmin User to access the System Administrator Main Menu. 2. Navigate to System Administrator Main > Configurations > Ca Routing Configuration > Digit Parameters. 3. Configure the Short Coection Search parameter. For more information on this parameter, see Ca Routing configuration properties on page Save your changes. Configuring the widcard To configure a widcard: 1. Foow the steps described in Adding a DNIS on page 51. The widcard entry shoud be???? 2. Ensure that the number of question marks refects the number of digits that Meeting Exchange is expecting to receive. 3. Save your changes. Configuring the teephone number branding This section contains an exampe scenario of a ca branding configuration for an in-service conferencing server. You must configure your depoyment to meet the specific requirements of your customer requirements. In this exampe, a service provider provides conferencing capabiities to three companies. Each of the three companies use the Avaya ca fow. The Meeting Exchange appication server coects four digits. If it receives a DNIS that it does not recognize, it sends the caer to the operator for assistance. To enabe this scenario: 1. Foow the steps described in Configuring Meeting Exchange number coection on page 90 to set the vaue of the Number of Digits parameter to 4. Apri

92 Branding the customer experience 2. Foow the steps described in Adding a DNIS on page 51 to add the foowing entries: cbuti add???? n ENTER - "DNIS UNKNOWN" -c "DNIS unknown cbuti add n SCAN - "Avaya Ca Fow" -c "Company A" cbuti add n SCAN - "Avaya Ca Fow" -c "Company B" cbuti add n SCAN - "Avaya Ca Fow" -c "Company C" Configuring reservation groups A feature caed reservation groups enabes participants to use a singe conference passcode to enter a number of different conferences. These conferences must use different DNIS numbers. For exampe, if a moderator chairs a number of conferences which each have different DNIS, the moderator can use the same moderator code to enter a of these conferences. This feature is especiay usefu if the conferences occur at the same time or overap. To enabe this feature, you must associate each DNIS with a reservation group. Meeting Exchange supports up to 1000 reservation groups, numbered from 1 to 999. The defaut vaue of reservation groups is 0. To configure reservation groups in your depoyment, you must add each reservation group. For more information on adding reservation groups, contact your Avaya Support Representative. Once you add a reservation group, you can set the vaue of rg in cbuti for each DNIS. Adding reservation groups Configuring ca branding for reservation groups Adding reservation groups To add a reservation group: 1. Open a PuTTY session and og in as a craft user. 2. Enter the command: su sroot 3. Enter the foowing commands to add the reservation groups: cd /usr/dcb/dbase/bridgedb_postgres/exe.other./bridgedb_maintain_pg.sh prompt do_resgroup bridgedb 4. Foow prompts on the dispay. 92 Administering Meeting Exchange Servers

93 Configuring diaing patterns Configuring ca branding for reservation groups To configure a DNIS to use the reservation groups feature: 1. Foow the steps described in Adding a DNIS on page 51 to add the foowing entries: cbuti add???? n ENTER - "DNIS UNKNOWN" -c "DNIS unknown" cbuti add n SCAN - "Saes department" -c "Company A" cbuti add n SCAN - "Finance department" -c "Company A" cbuti add n SCAN - "Research department" -c "Company A" cbuti add n SCAN - "Accounts department" -c "Company A" In this exampe, the Saes and Finance departments use reservation group 1. The Research and Accounts departments use reservation group 2. Operators using Bridge Tak can now schedue conferences using the reservation groups feature by entering the reservation group number in the Res Group fied on the Bridge Tak Conference Scheduer. For more information, see Using Meeting Exchange, which is avaiabe on support.avaya.com. 2. Use the Cient Registration Server (CRS) Front End to add new whoesaers to represent each department. For more information on administering the CRS Front End, see Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. Configuring diaing patterns Conference participants dia teephone numbers to access Meeting Exchange. Simiary, participants dia teephone numbers once they are in a conference to dia out to other potentia participants. These two types of cas are caed incoming cas and outgoing cas. Meeting Exchange changes each teephone number to a Uniform Resource Identifier (URI). A URI consists of a string of characters used to identify or name a resource on the Internet. Simpy speaking, participants dea with teephone numbers. Meeting Exchange deas with URIs. Meeting Exchange contains two fies, which transate teephone numbers to URIs. One fie converts incoming teephone numbers to URIs and the other fie converts outgoing teephone numbers to URIs. These fies are caed: tenumtouri.tab and the URIToTenum.tab. Essentiay, these fies act as a conversion between a traditiona form of teephony in the form of DNIS/DDI numbers and the more modern, SIP form of transmission. Before you depoy Meeting Exchange, you must configure these fies. A short note about syntax Configuring patterns for diaing out Apri

94 Branding the customer experience Configuring patterns for diaing in A short note about syntax The fies, tenumtouri.tab and URIToTenum.tab, use the same format. They contain three coumns of information. The ast coumn contains a comment or textua information about the first and midde coumns. The first coumn provides a pattern match for the input vaue. Meeting Exchange searches this coumn in order. This coumn supports wid cards. Tabe 16 describes the symbos that may be used in the fie. Tabe 16: Wid Cards Name Symbo Description Asterisk * Match zero or more characters. This symbo matches any character, not just digits. Question Mark? Match a singe character in an exact postion. In the fies, tenumtouri.tab and URIToTenum.tab, the midde coumn provides the transation for the entry in the first coumn. This coumn supports string substitutions using the syntax, $n, where n is an integer. Essentiay, this fie functions by ooking for a pattern in the eft coumn and produces an output based on the midde coumn. The midde coumn uses this syntax: $0 substitutes the fu input string. $1 substitutes the first wid card. $n substitutes the nth wid card. The system considers??? a singe wid card, but treats *?* as three distinct wid cards. It is aso worth noting that whie * matches any character, not just digits, it does not match empty strings at the beginning. For exampe: *sip:* matches <sip:xxxx@ but does not match sip:xxxx@ So to aeviate this issue, Avaya normay add one extra entry for the empty character. *sip:* sip:* 94 Administering Meeting Exchange Servers

95 Configuring diaing patterns Tabe 17 demonstrates some wid card substitutions. Tabe 17: Wid Card Substitutions Input Pattern Match Transation Output * ?*? * sip:$0@ sip:1234@ Configuring patterns for diaing out When they are in a conference, participants can dia out to other potentia participants. To initiate a dia out, participants typicay enter a DTMF pattern, such as *1. As an aside, customers can choose to disabe the diaout feature in their depoyment. The tenumtouri.tab fie is stored in the /usr/ipcb/config directory. Generay this fie starts with one or more comments. Like most text fies, comments begin with the hash (#) character. Foowing the comments, the fie has one or more ines containing data. Each data ine contains three pieces of information: TenumPattern, TenumConversion, and Comment. Tabe 18 describes these data. Tabe 18: TenumToUri.tab fie Entry TenumPattern TenumConversion Comment Description This entry is the teephone number that participants dia. This entry may contain widcards for pattern matching. For exampe, 93???? matches any teephone number that begins with the digits 9 and 3, such as , , or Meeting Exchange repaces the TenumPattern with this entry when it dias out to the new caer. This entry aways begins with the characters sip: foowed by the dia out number, character, and ends with the IP address of the media gateway or proxy. For exampe: sip:6352@ The characters $1 in this coumn repace the first widcard matched from the TenumPattern coumn. Any text that provides some information about the pattern. Some exampes are: bridge, media gateway, or proxy server. This fied must not have any spaces so many peope use underbars to separate the words. Apri

96 Branding the customer experience Avaya recommends adding an entry to hande situations where a participant does not enter a dia out teephone number. To configure this row, enter an asterisk * in the TenumPattern coumn. This configuration operates for a Meeting Exchange depoyments, with the exception of depoyments that incude Avaya Web Porta and Avaya Audio Consoe. If your depoyment incudes the Avaya Web Porta and Avaya Audio Consoe appications, you must incude an entry for these appications in the tenumtouri.tab fie. During the operation of Avaya Web Porta and Avaya Audio Consoe, the Meeting Exchange appication server makes an outgoing teephone ca to the Meeting Exchange Web server. From the participants perspective, this ca occurs behind the scenes. To ensure that Meeting Exchange can make this outgoing ca, you must incude a row that uses the asterisk * symbo, using the foowing syntax: * sip:1234@<web Server IP address> modapioperator Configuring patterns for diaing in The UriToTenum.tab fie works in tandem with the cbuti fie to brand the customer experience for caers who dia into a conference or who dia a conference recording. Simpy speaking, the UriToTenum.tab fie states that the Meeting Exchange appication server shoud recognize a given URI and identify this URI s corresponding DNIS. The cbuti fie states that Meeting Exchange appication server shoud recognize this DNIS and hande the ca in a certain way, for exampe, by routing the ca into a conference cafow or a conference payback cafow. Simiary, the tenumtouri.tab states that the Meeting Exchange appication server shoud recognize a DNIS entered by a Moderator during a conference and dia out using a corresponding URI. The UriToTenum.tab fie is stored in the /usr/ipcb/config directory. The UriToTenum.tab fie is simiar in structure to the TenumToUri.tab fie. Each data ine contains three pieces of information: TenumPattern, TenumConversion, and Comment. Tabe 19 describes these data. Tabe 19: UriToTenum.tab fie Entry TenumPattern (sometimes caed URI or SIP pattern) Description The IP address of the teephone ine that the participant diaed. This entry aways begins with the characters sip: foowed by the dia-in number, character, and ends with the IP address of the media gateway or proxy. Since Meeting Exchange may not recognize every dia-in teephone number, this entry usuay contains widcards for pattern matching. For exampe, *@ , matches any ca deivered via that IP address. 96 Administering Meeting Exchange Servers

97 Configuring diaing patterns Tabe 19: UriToTenum.tab fie Entry TenumConversion Comment Description Meeting Exchange repaces the TenumPattern with this entry and then routes it to the corresponding ca fow. Any text that provides some information about the pattern. Some exampes are: bridge, media gateway, or proxy server. This fied must not have any spaces so many peope use underbars to separate the words. As with the tenumtouri.tab fie, Avaya recommends adding an entry to hande situations where Meeting Exchange receives a ca from a URI that it is not defined in the fie. To configure this row, enter an asterisk *, foowed and then another asterisk * in the TenumPattern coumn. In addition, you can add rows for each operator. These rows are optiona and are for situations where you want to be abe to dia into a specific operator. If you add these rows, you can ensure that operators can dia into the Meeting Exchange appication server. Use the foowing syntax for these ines: op<dnis>x<operator index>@<ip address> The operator index is the identity number associated with an operator, such as operator 1, operator 2, and so on, rather than the Logica Channe Number (LCN) of the operator. The ca hander does not perform any processing on the DNIS number at this stage, but it is important to enter a numeric vaue at this point in the syntax. You can configure a dia in for other channes in the same way. The other channes are the ink, record/payback, and music channes. For exampe, for a music channe: mu<dnis>x<operator index>@<ip address> For the ink channe, use LK, for the record/payback channe, use RP. Apri

98 Branding the customer experience 98 Administering Meeting Exchange Servers

99 Chapter 9: Configuring bast dia ists Meeting Exchange enabes operators and moderators to dia a arge group of potentia participants using a singe command. This feature is caed a bast dia. For the successfu operation of the bast dia feature, you must create and save bast dia ists. This section introduces the bast dia feature. It contains the foowing sections: Introducing bast dia ists Configuring bast dia Creating bast dia ists Using bast dia ists Diaing out to bast dia ists Viewing and printing bast dia ists Introducing bast dia ists In a typica bast dia, Meeting Exchange dias an entire ist of phone numbers simutaneousy. When potentia participants answer the ca, an audio message prompts them to press specific digits on their teephones to join the conference. The bast dia feature uses dia ists to store the information that it requires. Each entry in the dia ist incudes a participant name and teephone number. Entries can aso incude a company name, a question and answer (Q&A) priority and a moderator status fag. Each ist has a unique 8-character name and an optiona access code. The number of dia ists is imited ony by the amount of hard drive space avaiabe on the appication server. Operators can create, modify, print, and deete dia ists using BridgeTak. Operators can aso import dia ists using CRS Front End. When they are booking conferences, operators, using Bridge Tak or CRS Front End, can set the bast dia feature to: Dia the dia ist automaticay as soon as a moderator enters the conference. Dia the dia ist when the moderator presses a DTMF keypad sequence on their teephone. This sequence is typicay *92. Using Bridge Tak, operators can aso dia a singe entry in a dia ist. This feature is caed fast dia. When a Bast Dia List contains a sixteen digit code containing a zeros ( ), participants are immediatey paced into a conference when the ine is answered without Apri

100 Configuring bast dia ists hearing an annunciator. If the bast dia ist does not contain the sixteen zero code then the bridge pays an annunciator message to participants when the ine is answered. Aside from the bast dia ist feature, Meeting Exchange enabes moderators to dia out to mutipe participants using another method. Using Web Porta, moderators can add participants to their persona address book. Using Avaya Audio Consoe, moderators can dia out to singe or mutipe participants from their address book. They can aso edit and save their address book as a.csv fie. There is no direct reationship between bast dia ists stored on the appication server and the address book feature. For more information on managing and using the address book, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. Configuring bast dia To configure a number of parameters in reation to how Meeting Exchange handes the bast dia feature, og in to Meeting Exchange as dcbadmin to dispay the System Administration Main Menu. Using the System Administration Main Menu, you can customize the operation of bast dia. For more information, see Customizing Meeting Exchange properties on page 63. In addition, see Bast dia configuration properties on page 270 for a ist of the bast dia configuration properties. In addition to manuay-created bast dia ists, Meeting Exchange 5.2 now generates bast dia ists automaticay. When operators, using CRS Front End, or moderators, using Web Porta, book a new conference, Meeting Exchange automaticay saves the current conference participant ist as the dia ist using the conference reference number as the fiename. Meeting Exchange makes this fie avaiabe for transfer to a dia ist directory on the Meeting Exchange server. This is a new feature in Meeting Exchange 5.2. To enabe this feature, you must: 1. Create a directory on the CRS server. 2. Update the system parameters tabe with the path of the directory on the CRS server. Meeting Exchange wi save the automaticay-generated participant ists to this directory. 3. Configure a schedued job to transfer the fies to the Meeting Exchange appication server, or bridge. You can use any method for transferring the fies, such as FTP or secure fie transfer (WinSCP). Creating bast dia ists System Administrators and operators can create bast dia ists. Moderators, using Web Porta, cannot create bast dia ists. They can ony associate existing bast dia ists with their conferences. 100 Administering Meeting Exchange Servers

101 Creating bast dia ists As an aside, when they are booking a conference, operators can prevent moderators from making use of the bast dia feature. This conference property does not impact the operator s abiity to bast dia. System administrators Operators System administrators As a System Administrator, you can create a new bast dia ist. You can aso use the directory server in your organization to generate the content of the ist. Creating a new bast dia ist Generating a bast dia ist from the LDAP server Viewing and printing bast dia ists Creating a new bast dia ist As a System Administrator, you can create bast dia ists using any text editor. To create a bast dia ist: 1. Open a new fie in any text editor. 2. Start the first ine with You can aso enter a security code in this ine. If you enter a security code in this ine, potentia participants must enter the code using their teephone keypad before they enter the conference. Security codes may contain up to 16 characters. A dia ist for a conference with a security code equa to woud start with this A dia ist for a conference with no security code begins with this 3. Enter the participant name, company name, and teephone number, using this format: <Participant name> <Teephone Number> / <Company Name> Apri

102 Configuring bast dia ists 4. For more information, see Tabe 20. Tabe 20: Dia List records Fied Participant Name Teephone Number Company Name Description Optiona participant name, up to 20 characters. May start with one of these specia to indicate moderator status + to indicate Q&A Top Priority = to indicate Excude from Q*A These symbos dispay in the CDR record, but do not dispay when the record is viewed in Bridge Tak. Required teephone number, up to 40 digits incuding 0-9, comma, space, #, *. Optiona Company Name, up to 20 characters. 5. Save the dia ist. The dia ist fie name cannot have a space in it; dia_ist is fine, dia ist is not. Save it to this ocation: /usr/dcb/dbase/diaists. Generating a bast dia ist from the LDAP server When the operator seects an LDAP group as their bast dia ist, Meeting Exchange ocates the the group members and writes them to a bast dia ist fie for the conference. This fie resides in the fie directory \temp\diaist. You must ensure that this fie directory is accessibe to the Meeting Exchange appication server. For more information on enabing CRS for LDAP bast dia ist support, see the Administering Meeting Exchange Appications Guide. This guide is avaiabe on support.avaya.com. Viewing and printing bast dia ists To access the dia ists: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. To view the dia ists: a. Seect View. b. Seect Dia Lists. c. Seect a dia ist. Meeting Exchange dispays the dia ist. To print the detai record: a. Seect Print. 102 Administering Meeting Exchange Servers

103 Using bast dia ists a. Seect Dia Lists. a. Seect a dia ist. b. Seect a printer. Meeting Exchange prints the dia ist. Operators Operators can create bast dia ists using the Meeting Exchange appication caed Bridge Tak. Operators can aso use another appiation caed Cient Registration Server (CRS) Front End to import bast dia ists. Bridge Tak Bridge Tak CRS Front End Operators can create dia ists using Bridge Tak. To create an entry in a dia ist, they must enter the participant name, company, Q&A priority, and teephone detais. They can aso optionay enabe moderator status for the participant. For more information on creating and modifying dia ists using Bridge Tak, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. CRS Front End Using CRS Front End, operators can import bast dia ists in.csv format. When operators are booking a conference, they can associate the bast dia ist with a conference. For more information on importing bast dia ists using CRS Front End, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. Using bast dia ists Operators and moderators can associate bast dia ists with conferences. Operators Moderators Apri

104 Configuring bast dia ists Operators When they are booking a conference, operators can add bast dia ists to the conference. They can use Bridge Tak or they can use the CRS Front End. Bridge Tak Bridge Tak CRS Front End Operators can add bast dia ists to attended and unattended conferences, using the Conference Scheduer diaog. If they are booking an attended conference, operators can seect a dia ist by cicking the Dia List button on the Schedue Conference diaog. The Dia List button aso provides operators with the abiity to create, edit, and deete dia ists. If they are booking an unattended conference, operators must seect Auto or Manua from the Auto Bast drop-down ist. Once they make a seection, Bridge Tak enabes the Dia List button. Operators can aso seect the audio prompt message. For more information on adding bast dia ists to conferences using Bridge Tak, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. CRS Front End Operators can add bast dia ists to attended conferences and unattended conferences. If they are booking an attended conference, operators can enter a dia ist name in the Attended Conference Options pane in the Options diaog. They aso have the option of inking an LDAP ist to the conference. If they are booking an unattended conference, operators must seect the Moderator checkbox on the Book Reservation diaog. On the Options diaog, they can set the Bast Mode and audio message prompt. In addition, For both conference types, Meeting Exchange automaticay saves the current conference participant ist as the dia ist using the conference reference number as the fiename. Meeting Exchange makes this fie avaiabe for transfer to a dia ist directory on the Meeting Exchange server. For more information on adding bast dia ists to conferences using CRS Front End, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. 104 Administering Meeting Exchange Servers

105 Diaing out to bast dia ists Moderators When they book conferences, moderators can add bast dia ists to their conferences using the Web Porta appication. In addition, as with booking a conference using CRS Front End, eeting Exchange automaticay saves the current conference participant ist as the dia ist using the conference reference number as the fiename. Meeting Exchange makes this fie avaiabe for transfer to a dia ist directory on the Meeting Exchange server. As an aside, System Administrators can choose to hide the bast dia option for moderators who have the Web Porta appication. Diaing out to bast dia ists Operators and moderators can dia out to a bast dia ist during a conference. It is worth noting that the participants cafow when they receive a bast dia ca is very simiar to a participant cafow for reguar conference entry. As bast dia participants enter the conference, Meeting Exchange announces their arriva based on the settings that the operator or moderator have configured for that conference, such as pay entry tones, pay an entry message, prompt for a ro ca name. However, Meeting Exchange does not require bast diaed participants to enter passcodes or a PIN code. Operators Moderators Operators If they are using Bridge Tak, operators can dia a bast dia ist during a ive conference using the Fast Dia menu option. For more information on diaing a bast dia ist during a ive conference using Bridge Tak, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. Moderators Moderators can dia a bast dia ist by pressing the DTMF keypad sequence *92. When they initate a bast dia, Meeting Exchange pays an audio message to indicate that it has commenced the bast dia. The cafow for participants who respond to a bast dia is the same as for participants who dia into the conference. Apri

106 Configuring bast dia ists Moderators can aso dia mutipe participants using another method. Using Avaya Audio Consoe, moderators can dia out to singe or mutipe participants from their address book. This feature does not make use of bast dia ists. For more information on using the Avaya Audio Consoe appication, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. Viewing and printing bast dia ists System Administrators and operators can print bast dia ists: System administrators Operators System administrators To view and print dia ists that are currenty configured: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. To view the dia ist: a. Seect View. b. Seect Dia Lists. c. Seect a dia ist. Meeting Exchange dispays the dia ist. To print the dia ist: a. Seect Print. b. Seect Dia Lists. c. Seect a dia ist. Meeting Exchange dispays the dia ist. Operators Operators, using Bridge Tak can print bast dia ists, using the Fast Dia menu option. For more information on printing a bast dia ist using Bridge Tak, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. 106 Administering Meeting Exchange Servers

107 Chapter 10: Viewing Meeting Exchange information Meeting Exchange produces a arge number of reports to enabe you to view conference activity. Many of these reports act as an audit trai which can hep you to diagnose and resove any issues which arise in Meeting Exchange. You can aso use these reports to anayze conference activity in your network. This chapter describes the most usefu reports that Meeting Exchange produces. It contains the foowing sections: Introducing reports Accessing records using the Meeting Exchange System Administrator main menu Accessing reports using the Meeting Exchange System Administrator main menu Accessing records using a reationa database Accessing records using a remote host Accessing reports using the Cient Registration Server Accessing reports using Bridge Tak Accessing reports using Web Porta Accessing reports using the Reports Appication Accessing LAN statistics reports Accessing ogs Accessing port capacity reports Accessing poing reports Introducing reports Meeting Exchange coects a ot of data about conference activity and provides a number of ways of accessing this information. Much of this information consists of Ca Detai Records (CDRs) and Conference Detai Records (CODRs). Meeting Exchange stores this data in a database caed the CDRs database. If your depoyment of Meeting Exchange consists of severa appication servers, you can coect a the CDR and CODR fies from each of the appication servers and store them in a singe CDRs database. For this purpose, Avaya has created an appication caed the CDR Loader appication. For more information, see: Ca Detai Record (CDR) reports Conference Detai Records (CODR) reports CDR Loader appication Apri

108 Viewing Meeting Exchange information Aside from CDR and CODR information, Meeting Exchange aso coects a ot of data in reation to conferencing traffic, operator activity, and participant activity. Meeting Exchange aso creates a arge number of aarm and og fies. You can access this information using the Meeting Exchange System Administrator Main Menu. Ca Detai Record (CDR) reports A CDR is the computer record produced by a teephone exchange. The record contains detais of a ca that passed through it. Meeting Exchange produces CDRs for each ca. Meeting Exchange generates a CDR whenever a participant ine disconnects from the audio conferencing server. You can configure the output format of CDR reports. For exampe, customers may not want to incude a CDR fieds when they view and print CDR reports. Conference Detai Records (CODR) reports A CODR is the computer record produced by a teephone exchange. Meeting Exchange produces conference detai records (CODR) for each conference. The CODR contains detais of the conference, such as the start and end time. Meeting Exchange generates a CODR whenever a conference ends and a conference ines are ceared. To enabe Meeting Exchange to generate a CODR, the conference must have a conference ID. A conference ID is a unique number that identifies a conference. You can configure Meeting Exchange to automaticay assign a conference ID. Aternativey, you can configure the system parameter Automatic Conf. ID to enabe operators to assign a conference ID. For more information on configuring the generation of conference IDs, System configuration properties on page 298. Occasionay, operators may want to reuse a conference ID for severa sessions. For exampe, operators may set aside a particuar conference for saes associates to use throughout the day. Saes associates ca into the conference at 9 AM, 11 AM, and 4 PM. The operator assigns the conference ID to this conference. If the operator does not run the Conference Cear_a command in Bridge Tak, Meeting Exchange retains the conference ID. Each time a session empties, Meeting Exchange generates a new CODR with each CODR having the conference ID To enabe operators to reuse a conference ID for severa sessions, you must ensure that the system parameter Automatic Conf. Cear is OFF. For more information on Automatic Conf. Cear, see System configuration properties on page 298. CDR Loader appication If your depoyment consists of a number of Meeting Exchange appication servers, you can configure Meeting Exchange to coect the CDR and CODR fies from a of the appication servers. This feature is particuary usefu in a mutisite or muticabinet environment. The appication which manages this process is caed the CDR Loader appication. The CDR Loader 108 Administering Meeting Exchange Servers

109 Accessing records using the Meeting Exchange System Administrator main menu appication resides on the CRS server and stores a of the coected data in the CDRs database. For more information on accessing this information, see Accessing reports using the Cient Registration Server on page 119. For the CDR Loader appication to operate successfuy, you must configure each appication server and aso configure the CDR Loader appication on the CRS server. For more information on configuring the CDR Loader and the CDRLoader.ini fie on the CRS server, see Administering Meeting Exchange Appications. This guide is avaiabe on support.avaya.com. The CDR Loader appication operates by importing CDRs and CODRs from each appication server using fie transfer protoco (FTP) or secure FTP (SFTP). It stores the data that it receives in two tabes caed Cdr700 and Codr700. A schedued SQL server task, which runs at configurabe intervas, reads the data from these specia tabes, converts it into the correct format, and inserts it into the standard CDRs tabes. To configure the CDR Loader appication on each Meeting Exchange appication server: 1. Launch SQL Server Management Studio. 2. Right-cick on the bridge tabe under the CDRs database and seect Open Tabe. 3. Enter the appication server name and IP address in the fieds provided and press Return on the keyboard. When you press Return, the database enters the defaut vaues in a the remaining fieds. 4. Edit the Login and Password fied to craft and craft01 respectivey. 5. Ensure that the vaue in the ast fied in the tabe, the Cabinet Reference fied, is consistent with the cabinet reference information that you have configured on the CRS Front End that is associated with this specific appication server. For more information on configuring cabinets in the CRS Front End, see Administering Meeting Exchange Appications. This guide is avaiabe on support.avaya.com. 6. Repeat these steps for each appication server in your depoyment. In each case, ensure that you update the cabinet reference. Accessing records using the Meeting Exchange System Administrator main menu You can view and print CDRs and CODRs using the Meeting Exchange System Administrator Main Menu. Meeting Exchange coects a arge amount of data about conference activity but using the Meeting Exchange System Administrator Main Menu, you can choose which fieds that you want to view and print. Configuring the fieds for viewing and printing Viewing and printing detai records Apri

110 Viewing Meeting Exchange information Configuring the fieds for viewing and printing Meeting Exchange produces the CDRs and CODRs in a raw tabuar format. To configure the output format of detai record reports, you must og in to Meeting Exchange as dcbadmin and navigate to the Configurations menu. For more information on navigating to the Configurations menu, see Customizing Meeting Exchange properties on page 63. To configure the output format of detai record reports, you must seect which fieds that you want to view and print. For more information, see CDR Configuration Properties on page 273 and CODR Configuration Properties on page 283. The records are stored in their respective fies in a raw tabuar format without coumn headings. You can copy the fies for further processing using a text editor or spreadsheet appication. Each day, Meeting Exchange saves the detai records to a daiy CDR fie and a daiy CODR fie. It stores the fies in these ocations with these formats: /usr/dcb/cdr for exampe, Nov09.cdr /usr/dcb/codr for exampe, Nov09.cod. Meeting Exchange saves 30 fies and automaticay deetes the odest fie. Meeting Exchange does not deete CDR and CODR fies that you have stored outside of their defaut directories. You can retain fies for safekeeping outside the defaut directories. Viewing and printing detai records To view or print detai records: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. To view the detai record: a. Seect View. b. Seect CDRs or CODRs. c. Seect the report stye. d. Seect the report. Meeting Exchange dispays the report. To print the detai record: a. Seect Print. b. Seect CDRs or CODRs. c. Seect the report stye. 110 Administering Meeting Exchange Servers

111 Accessing reports using the Meeting Exchange System Administrator main menu d. Seect the report. e. Seect a printer. Meeting Exchange prints the report. Accessing reports using the Meeting Exchange System Administrator main menu You can view and print conference reports using the Meeting Exchange System Administrator Main Menu. These conference reports use the CDR and CODR information that Meeting Exchange coects and present the information in a tabe. You can ony access a conference report for a conference that has ended. If a conference is in-progress, you cannot access a conference report for that conference. Working with conference report information Viewing and printing conference reports Working with conference report information Conference reports incude: Conference date, conference ID, and conference name Meeting Exchange system (bridge) name Contact name or contact teephone number, but not both: This fied is for schedued conferences ony. Conference start time: The time that the first participant entered the conference. Recorded fie number: The number of the fie that Meeting Exchange uses to store the conference recording. Schedued duration minutes: The number of minutes between the conference s specified start and end times. Schedued participants: The number of ines that the User has reserved for a schedued conference. Conference duration: The interva between the first person joining the conference and the ast person eaving the conference. Tota conference minutes: The approximate sum of the ine conference minutes. Notes: Information entered by the operator. Apri

112 Viewing Meeting Exchange information Features status: This is the ON/OFF setting for each of 11 conference features. ON indicates that a feature was used during the conference. Payback and Record fieds: These fieds have three ON options: ANL=anaog, DIG=digita, A/D= anaog/digita. Unattended status: This is an ON/OFF setting. Maximum participants: The greatest number of simutaneous participants. Line numbers Line moderator status: This is a Y/N setting. Line names Line phone numbers, if recorded, or company name, if recorded Line start times: The time each ine entered the Meeting Exchange system. Line conference minutes: The number of minutes each ine was in the conference, rounded down to the nearest minute with a one-minute minimum. Line connect time: The number of minutes the ine was connected to Meeting Exchange system, rounded down to the nearest minute with a one-minute minimum. Viewing and printing conference reports To view or print detai records: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. To view the detai record: a. Seect View. b. Seect Conference Reports. c. Seect a record. The records have the fie extension.cod, which refers to CODR. d. Seect either Teephone Number or Company Name. This fied wi dispay on the conference report. 112 Administering Meeting Exchange Servers

113 Accessing records using a reationa database e. Seect either Report On A Singe Conference or Report On A Conferences. You can dispay a singe conference or a conferences on the seected day. If you seect Report On A Singe Conference, you must seect a particuar conference in the next diaog. Meeting Exchange dispays the conference report. To print the detai record: a. Seect View. b. Seect Conference Reports. c. Seect a record. The records have the fie extension.cod, which refers to CODR. d. Seect either Teephone Number or Company Name. This fied wi dispay on the conference report. e. Seect either Report On A Singe Conference or Report On A Conferences. You can print a singe conference or a conferences on the seected day. If you seect Report On A Singe Conference, you must seect a particuar conference in the next diaog. f. Seect a printer. Meeting Exchange prints the conference report. Accessing records using a reationa database You can view CDRs and CODRs using a Meeting Exchange reationa database. This database is caed bridgedb and is a PostgreSQL database, which is an object-reationa database management system (ORDBMS). For more information on the impementation of reationa database fies, contact your Avaya Support Representative. Accessing records using a remote host If a Meeting Exchange depoyment is in a LAN environment, you can view CDRs and CODRs on a separate computer, or remote host, in your network. Meeting Exchange can send CDRs Apri

114 Viewing Meeting Exchange information and CODRs to the remote host in rea time. Meeting Exchange uses a socket mechanism to faciitate this transmission. To enabe this feature, you must configure Meeting Exchange and the remote host. This feature is commony caed the autocdr process. Introducing the transmission process Configuring the Meeting Exchange server Configuring the remote host Introducing the transmission process When you configure Meeting Exchange for the autocdr process, you store the IP address of the remote host in a particuar fie on the Meeting Exchange server. Once the Meeting Exchange server ocates the remote host IP address, it waits indefinitey for a request from the remote host. The remote host sends requests that incude the foowing information: Command number Starting date(s) Starting record number Autocdr mode When Meeting Exchange receives a request, it opens a fie, ooks for the starting record number and sends the information to the remote host. Meeting Exchange sends a fies after this date. If the remote host requests CDRs and CODRs, Meeting Exchange sends the CDRs for the starting date, then CODRs for that same day, then CDRs for the foowing day, and so on. The request from the remote host contains a Mode fag. The Mode fag determines how Meeting Exchange processes the request: If Mode fag = N, Meeting Exchange processes each request synchronousy; The Meeting Exchange server competes each request, then returns to istening for another command. If Mode fag = Y, Meeting Exchange processes the request as above, then stops istening for commands and sends a records to the remote cient asynchronousy. If the connection between the Meeting Exchange server and the remote host breaks, Meeting Exchange stops processing requests from the remote host. You must re-estabish the connection and issue a request, specifying the date, starting sequence number, and mode. It takes up to 45 seconds to re-estabish a ost or broken connection. Each request from the remote host and response from Meeting Exchange contains a header string. This header string contains the foowing information: Fied type (51 or 52). CDRs have a fied type of 51. CODRs a fied type of 52. Month (Jan Dec) Day (01 31) 114 Administering Meeting Exchange Servers

115 Accessing records using a remote host Sequence number ( ) Data Vaid fag (Y = store this data, N = end of fie reached) Mode fag (Y/N) When Meeting Exchange sends CDRs and CODRs after midnight, they refect the new date. In addition, Meeting Exchange resets the sequence number to The date and sequence number of a CDR refect the start time of the ca. Thus, CDRs generated after midnight may have a mix of sequence numbers and dates, because the system generates records as cas disconnect. For exampe, a thirty-minute ca started 07/26/09 at 23:45 ends the foowing day (07/27/09) at 00:15. The CDR date is 07/26/09 and the sequence number is pre Tabe 21 provides an overview of the information fow between the Meeting Exchange server and the remote host. Tabe 21: Meeting Exchange Server Action and Remote Host Response Meeting Exchange.. Remote Host... Initiaizes (warm/cod boot). Listens for connection requests. <===== Requests connection. Verifies host in /etc/hosts fie. Estabishes connection. =====> <===== Sends vaid request. Request Autocdr Mode Fag=N. Locates/transfers requested fie. Reaches end of fie. Sends bank record (seqnum=99999, Data Vaid fag = N) =====> Receives/stores data. =====> Sees bank record; throws away bank record; coses fie. Waits for next command. Request Autocdr Mode Fag=Y. Locates/transfers requested fie. Stops istening for commands. Continues sending records as events occur. Loses/coses connection. Stops sending records. Listens for connection requests. =====> Receives/stores data. =====> Continues storing data. ==/ /=> Loses/coses connection. Apri

116 Viewing Meeting Exchange information Configuring the Meeting Exchange server To configure the Meeting Exchange server for the autocdr process: 1. Enter the IP address of the remote host in the /etc/hosts fie on the Meeting Exchange server. 2. Enter the port number on which Meeting Exchange istens for requests from the remote host in the /etc/services fie. You must add this information to the /etc/services fie on the Meeting Exchange server and to the the /etc/services fie on the remote host. You can define this port as any number greater than or equa to 5000 that does not confict with other port numbers in the /etc/services fie. The service name of this port is autocdr. The foowing command string is an exampe: autocdr <service number>/tcp where the white space between autocdr and <service number> is a tab character. 3. Set the Automatic CDR Print system parameter to LAN. For more information on Automatic CDR Print, see System configuration properties on page 298. Once you configure the Automatic CDR Print parameter, the autocdr process ocates a port number in the /etc/services fie and istens on that port for requests from the remote host. 4. Configure the output format of CDRs and CODRs using the Meeting Exchange System Administrator Main Menu. For more information, see CDR Configuration Properties on page 273 and CODR Configuration Properties on page 283. Using this functionaity, you can incude a subset of the CDR and CODR fieds in each response, rather than transmitting a fieds. Configuring the remote host There are three main steps in the configuration of the remote host: Writing an appication Defining a port Testing the configuration Writing an appication To access the CDR and CODR information on the Meeting Exchange server, you must configure the remote host. You must write a sma cient program and insta it on the remote host. The program must contain socket commands consisting of pain ASCII text. Meeting Exchange responds to these four vaid commands: 116 Administering Meeting Exchange Servers

117 Accessing records using a remote host REQUEST_CDR_FILE (cmd=01) This command asks Meeting Exchange to send CDR records to the remote host. REQUEST_CODR_FILE (cmd=02) This command asks Meeting Exchange to send CODR records to the remote host. REQUEST_CDR_CODR_FILE (cmd=03) This command asks Meeting Exchange to send CDR and CODR records to the remote host. REQUEST_PING (cmd=04) This command asks Meeting Exchange to send a message back confirming a connection. Each request is 13-bytes of ASCII text. A fieds in the requests are fixed-ength. Request numbers shoud be right justified and zero fied. The format of REQUEST_CDR_FILE is: struct request_cdr_fie { }; char cmd[2];// "01" char month[3];// MMM (e.g. "Jan") char day[2];// DD (e.g. "01") char seqnum[5];// NNNNN (e.g. "00012") char mode[1];// Y or N The format of REQUEST_CODR_FILE is: struct request_codr_fie { }; char cmd[2];// "02" char month[3];// MMM (e.g. "Jan") char day[2];// DD (e.g. "01") char seqnum[5];// NNNNN (e.g. "00012") char mode[1];// Y or N Apri

118 Viewing Meeting Exchange information The format of REQUEST_CDR_CODR_FILE is: struct request_cdr_codr_fie { }; 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. "01") char codrseqnum[5];// NNNNN (e.g. "00012") The format of REQUEST_PING is: struct request_ping { }; char cmd[2];// "04" char rfu[11]; These commands, REQUEST_CDR_FILE, REQUEST_CODR_FILE REQUEST_CDR_CODR_FILE, cause the Meeting Exchange server to send records for the specified day s fie, beginning with sequence # NNNNN. If you set the Mode Fag in the request to N, the Meeting Exchange server sends a bank record upon reaching end-of-fie (EOF). This bank record incudes the requested fie s date and a sequence number of 99999, with N as the Data Vaid Fag in the header. However, if you set the Mode Fag in the request to Y, the Meeting Exchange server does not send an end of fie bank record. Instead, the server continues sending records as they become avaiabe unti the connection is ost or broken. The command REQUEST_PING aows the remote host to check if the connection to Meeting Exchange is open and the server is running. The REQUEST_PING command is padded to the same size as a REQUEST_CDR_FILE command. If the connection to Meeting Exchange is open and the server is running, Meeting Exchange sends the same message back to the remote host. Defining a port You must define a port in the the /etc/services fie. For more information, see 2 in Configuring the Meeting Exchange server on page Administering Meeting Exchange Servers

119 Accessing reports using the Cient Registration Server Testing the configuration Avaya recommends testing the autocdr process by making a socket connection and sending one of the socket commands. Accessing reports using the Cient Registration Server Using the Cient Registration Server (CRS) Front End, operators can access the data in the CDRs database. They can ony view the data when the conference is over. They can aso save it as a.txt or.csv fie. They can access the data using the Schedue on the CRS Front End. For more information on accessing CDRs and CODRs using the CRS Front End, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. Accessing reports using Bridge Tak Using the Bridge Tak, operators can access the data in the CDRs database.they can view and print a arge number of reports, such as conference status reports, conference activity reports, ine connect times, and so on. They can aso view information about past conferences and about operator activity. For more information on accessing CDRs and CODRs using Bridge Tak, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. Accessing reports using Web Porta Using the Web Porta appication, moderators can access the data in the CDRs database. It is important to note that each report ony shows their conferences and conference usage. They cannot see the usage patterns of other moderators. The Web Porta appication produces Microsoft Exce spreadsheets and charts. Avaiabe reports incude Audio Conference reports, Data Conference reports, and port usage reports. System Administrators can aso use the Web Porta appication to generate reports. These reports obtain data from the CDRs and BSRes2 databases, as we as data from the appication server. These reports provide ive System Administrators with information about resource and User usage. Avaiabe reports incude booking reports, moderator consoe reports, session oad reports, and user session reports. Apri

120 Viewing Meeting Exchange information For more information on how moderators can access CDRs and CODRs using Web Porta, see the Using Meeting Exchange Guide. For more information on how System Administrators can use the Web Porta to generate reports, see the Administering Meeting Exchange Appications Guide. Both of these guides are avaiabe on support.avaya.com. Accessing reports using the Reports Appication The Meeting Exchange soution incudes an appication caed the Avaya Reports appication. The Avaya Reports appication produces Microsoft Exce spreadsheets and charts using the data in the BSRes2 and CDRs databases. Operators can use the Reports appication to anayze report data to respond to specific customer queries about conference usage, duration, individua attendance, and activity during a conference. System Administrators can use the Reports appication to anayze report data to check that system resources are being used efficienty. Exampes of reports incude reports on cient activity, conference ists, system utiization, and participant ists. System Administrators can configure the Reports appication to ensure that it generates reports at times when Meeting Exchange is not under heavy oad, such as overnight. This fexibiity ensures that the process of reports generation does not impact the performance of the audio conferencing server. For more information on the configuration of the Reports appication, see the Administering Meeting Exchange Appications Guide. For more information on the use of the Reports appication, see the Using Meeting Exchange Guide. Both of these guides are avaiabe on support.avaya.com. Accessing LAN statistics reports You can view a report that contains some basic information about the IP, ICMP, IGMP, TCP, and UDP packet traffic that Meeting Exchange has received and sent. This LAN statistics report provides a very imited information but coud be a usefu starting point for troubeshooting. For the most part, service providers rather than enterprise customers wi view these statistics. To access the LAN statistics report: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. 3. Seect View. 4. Seect LAN Statistics. Meeting Exchange dispays the report. 120 Administering Meeting Exchange Servers

121 Accessing ogs Aternativey, you can og into Meeting Exchange as a craft user and navigate to /usr/dcb/ anstats. Accessing ogs Using the System Administrator Main Menu, you can access a number of og fies, as foows: Accessing genera ogs Accessing modification ogs Accessing operator ogs Accessing participant ogs Accessing genera ogs You can view a og that contains messages from a software processes that Meeting Exchange uses. This og incudes information about system information, software errors, and trunk aarms. The name of the og fie is the current date (for exampe, Dec09). Meeting Exchange stores a maximum of 30 og fies. This fie is a usefu starting point for troubeshooting. To access the ogs: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. To view the ogs: a. Seect View. b. Seect Logs. c. Seect a og. Meeting Exchange dispays the og. To print the og: a. Seect Print. a. Seect Logs. a. Seect a og. b. Seect a printer. Meeting Exchange prints the dia ist. Apri

122 Viewing Meeting Exchange information Aternativey, you can og into Meeting Exchange as a craft user and navigate to /usr/dcb/ ogs directory. Accessing modification ogs You can view a og that shows any changes that a Bridge Tak operator makes to ive conferences. This fie is a usefu audit trai of operator actions. To access the ogs: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. To view the conference modification ogs: a. Seect View. b. Seect Modify Logs. c. Seect a conference modification og. Meeting Exchange dispays the og. To print the conference modification og: a. Seect Print. a. Seect Modify Logs. a. Seect a conference modification og. b. Seect a printer. Meeting Exchange prints the og. Aternativey, you can og into Meeting Exchange as a craft user and navigate to /usr/dcb/ modiog directory. Accessing operator ogs If you enabe the Transaction Logs parameter in the System Configuration Menu, Meeting Exchange creates an audit trai of Bridge Tak operator actions. For more information on the Transaction Logs parameter, see System configuration properties on page 298. For more information on configuring the system configuration properties, see Customizing Meeting Exchange properties on page 63. Meeting Exchange creates a og each day. To customize your og, you can fiter the avaiabe data using a number of fiters. Tabe 22 ists the fitering criteria. 122 Administering Meeting Exchange Servers

123 Accessing ogs Tabe 22: Operator Transaction Fiters Fiter Setting Month A For a months. Seect a month. Day A For a days in the month. Seect a day of the month. Operator Sign-in Enter the operator Station Number for which you want to see transactions. Enter the sign-in name of the operator for which you want to see transactions. Command A (defaut) Dispay a ist of a the commands that are ogged in the transaction og on the ower part of the screen. Seect the command you are interested in: - ACCESS - CONFERENCE - DEBUG_MODE - FASTDIAL - HELP - LINE - LOGIN - LOGOUT - NEXT_ENTER - OPERATOR_TALK - OPTIONS - PURGE - SET The resuting og references operator actions. Tabe 23 can hep you to interpret the og detais in terms of the Bridge Tak operator actions. Tabe 23: Logged Operator Transactions Command Access/Dia Access/Hangup Access/Next_Avaiabe Parameters Linenum; name; company; digits Linenum Linenum 1 of 6 Apri

124 Viewing Meeting Exchange information Tabe 23: Logged Operator Transactions (continued) Command Access/Next_Enter Access/Pace Access/Reease Access/Transfer Access/User_Seected Conference/AUX1 Conference/AUX2 Conference/CearA Conference/EntryTone Conference/ExitTone Conference/Gain Conference/Hangup Conference/ID Conference/Lecture Conference/Lock Conference/Music Conference/Music/Stop Conference/Name Conference/Note Conference/Payback/Digita Conference/Payback/ Externa Conference/Po/Cear Conference/Po/Exit Conference/Po/Hep Conference/Po/Incude Parameters Linenum; seizetime Linenum; confnum Linenum Linenum; number/extension Linenum Confnum; aux1 Confnum; aux2 Conference Confnum; entry tone = On/Off Confnum; exit tone = On/Off Confnum; gain = On/Off Confnum Confnum; confid Confnum; ecture = TRUE/FALSE Confnum; ock = TRUE/FALSE Confnum; musicsource; mode=on Confnum; mode=off Confnum; name Confnum; note Confnum; channum; fiename; skiptime Confnum; channum Confnum; inenum Confnum Access/User_Seected Confnum; incudea = TRUE/FALSE 2 of Administering Meeting Exchange Servers

125 Accessing ogs Tabe 23: Logged Operator Transactions (continued) Command Conference/Po/Mute Conference/Po/Po Conference/Po/Reease Conference/Po/Start Conference/Promptset Conference/QA/Cear Conference/QA/ Cose_Mute_Line Conference/QA/Exit Conference/QA/Open_Line Conference/QA/Reca Conference/QA/Resume Conference/QA/Start Conference/QA/Stop Conference/QA/Access_Hep Conference/QA/ Reease_Hep Conference/Record/Digita Conference/Record/Externa Conference/SecureAowed Conference/Pay_Rec/Stop Conference/Transfer Debug_Mode Fastdia/Bast Fastdia/Create Parameters Confnum; inenum; mute = TRUE/FALSE Confnum; pomode = TRUE/FALSE Access/Reease Confnum confnum;promptset Confnum Confnum; inenum Confnum Confnum; inenum Confnum; inenum Confnum; inenum Confnum Confnum time operator_number operator_name CONFERENCE/QA/ACCESS_MOD confnum;inenum time operator_number operator_name CONFERENCE/QA/RELEASE_MOD; confnum;inenum Confnum; channum; fiename;autogenname Confnum; channum Confnum; secure aowed = TRUE/FALSE Confnum fromconf; toconf Mode Listname; confnum; startinenum; annunciator Listname; accesscode 3 of 6 Apri

126 Viewing Meeting Exchange information Tabe 23: Logged Operator Transactions (continued) Command Parameters Fastdia/Modify Fastdia/Remove Hep/Conf Hep/Individua Listname; accesscode Listname Confnum; hepreqtime Linenum; hepreqtime Line/Aux1 Linenum; aux 1 Line/Aux2 Linenum; aux 2 Line/Aux3 Linenum; aux 3 Line/CaType Line/CompanyName Line/Faut Line/Hangup Line/Moderator Line/Mute Line/Name Line/Number Line/Promptset Line/Reconnect Line/Transfer Line/VirtuaLink Login Logout Linenum; ca type Linenum; company Linenum; mode = TRUE/FALSE Linenum Linenum; moderator = TRUE/FALSE Line/Mute inenumb = ;sefmute = TRUE/ FALSE; opermute = TRUE/FALSE Note: When the operator has Tak ON then opermute=fase. If the operator has Tak OFF, then opermute=true. Linenum; name Linenum; number Linenum; Promptset Linenum; tenum Linenum;toConf or Linenum; phone; usercode; pincode Linenum; v = TRUE/FALSE Channum; apitabidx Session= 4 of Administering Meeting Exchange Servers

127 Accessing ogs Tabe 23: Logged Operator Transactions (continued) Command Options/Annunciator/ Payback Options/Annunciator/Record Options/Annunciator/ Set_Msg Options/Annunciator/Stop Options/Chat Options/Listen/Line/HangUp Options/Listen/Line/Mute Options/Listen/Line/Reease Options/Listen/Line/Start Purge/Ca_Counts Purge/Disconnects Purge/Disconnects/A Purge/Mins_Per_Conference Purge/Tota_Line_Times Scheduer/Login Scheduer/Logout Scheduer/Conference/ Create Scheduer/Conference/ Modify/Before Scheduer/Conference/ Modify/After Scheduer/Getsched Scheduer/Getver Parameters Msgnum Msgnum Msgnum; text Msgnum Destopernum; text Linenum Line/Mute inenumb = ;sefmute = TRUE/ FALSE; opermute = TRUE/FALSE Linenum Linenum Linenum = a Confnum Confnum = a Confnum Linenum = a RemoteIPAddr; signinleve; servertype RemoteIPAddr ConfirmNum; confseccode; modseccode; confid ConfirmNum; confseccode; modseccode; confid; maxchans; startdate/time; enddate/ Time; inprog ConfirmNum; confseccode; modseccode; confid; maxchans; startdate/time; enddate/ Time; inprog Month; day; numitemsfound VersionMajor; versionminor 5 of 6 Apri

128 Viewing Meeting Exchange information Tabe 23: Logged Operator Transactions (continued) Command Scheduer/Usage Scheduer/Lsconf Scheduer/Conference/Purge Scheduer/Conference/ Remove Scheduer/Conference/ Setspecia Scheduer/Debug Scheduer/Timer Set/ACS Parameters LinesAvai; inesent; opersavai; confsavai Month; day; confirmnum; confid; confcode; confname; signinname; attended; ondemandlines; inprog; numitemsfound SaveWeeks ConfirmNum ConfirmNumIn; confirmnumout Debug TimerA; timerb; timerc Confnum; inenum Set/Answer Set/Night_Time Set/Scan_Time Linenum; answer = ON/OFF NightTime = TRUE/FALSE Odscantime; newscantime 6 of 6 To access the operator transaction ogs: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. To view the operator transaction ogs: a. Seect View. b. Seect Operator Trans. Logs. c. Use the Log Seection screen to specify your fiter criteria. d. Save your fiter criteria. Meeting Exchange dispays the og. To print an operator transaction og: a. Seect Print. a. Seect Operator Trans. Logs. a. Seect a og. 128 Administering Meeting Exchange Servers

129 Accessing ogs b. Seect a printer. Meeting Exchange prints the og. Aternativey, you can og into Meeting Exchange as a craft user and navigate to /usr/dcb/ dbase/oogs directory. Accessing participant ogs If you enabe the Log User Transaction parameter in the System Configuration Menu, Meeting Exchange creates an audit trai of conference participant actions. For more information on the Log User Transaction parameter, see System configuration properties on page 298. For more information on configuring the system configuration properties, see Customizing Meeting Exchange properties on page 63. Meeting Exchange creates a og each day. You can configure Meeting Exchange to save these og fies on the oca appication server. Aternativey, you can configure Meeting Exchange to send these og fies to a remote computer. By defaut, Meeting Exchange stores the ogs fies in /usr/dcb/utogs. To configure Meeting Exchange to send these og fies to a remote computer, you must configure the oca2.notice fied in the /etc/sysog.conf fie by adding the foowing information to the defaut User transaction ogs record the foowing information: Cas ANI/DNIS A DTMF entered Channes moving to user conferences Announcement segments payed to a user Customer disconnects with the reason Togging mute Performing a dia out operation Commands The ogs contain information in the foowing format: <date> <time> <system id> <service name>: <appication specific data> The <appication specific data> format is: chan <nn> dtmf <xxx> chan <nn> move to conf <nn> chan <nn> pay segment <xxx> chan <nn> disconnect with reason <xxx> Apri

130 Viewing Meeting Exchange information An eipse (...) foowing the segment number indicates that there are mutipe segments for this og entry. Accessing port capacity reports You can view traffic statistic fies that contain information about port capacity. The traffic statistic fies enabe you to view the usage patterns and conference activity. You can compage the schedued activity with the actua conference activity. Meeting Exchange generates a daiy fie containing statistics that it updates every 15 minutes. Meeting Exchange ists the minimum, maximum, and average counts for the foowing categories: System Capacity The number of ines currenty avaiabe for conferences. This count excudes remote operator ines, fauted ines, and ines out-of-service. Channes Schedued Information about the number of channes that operators and moderators have currenty schedued for conferences. Channes In Schedued Conf The schedued channes that Meeting Exchange is currenty using. Compare this information to Channes Schedued to see if scheduing and usage patterns agree. Channes In Use - Tota The channes that Meeting Exchange is currenty using for both schedued and unschedued conferences. Tota Utiization The percentage of channes that Meeting Exchange is currenty using. Meeting Exchange maintains a maximum of 30 traffic statistics fies. It automaticay deetes the odest fie. To access the traffic statistics fies: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. To view the traffic statistics fies: a. Seect View. b. Seect Traffic Stats. c. Seect a fie. Meeting Exchange dispays the traffic statistics. To print a traffic statistics fie: a. Seect Print. a. Seect Traffic Stats. a. Seect a fie. 130 Administering Meeting Exchange Servers

131 Accessing poing reports b. Seect a printer. Meeting Exchange prints the traffic statistics. Aternativey, you can og into Meeting Exchange as a craft user and navigate to the /usr/ dcb/traffic directory. Accessing poing reports If operators, using Bridge Tak, and moderators, using Conference Viewer, conduct pos during their conferences, you can view the poing resuts and poing tags after the po takes pace. The poing tags are the tites of the voting categories in a po. To access the poing fies: 1. Log in to Meeting Exchange as a dcbadmin user. 2. Navigate to System Administrator Main Menu > Fie Management. To view the traffic statistics fies: a. Seect View. b. Seect Poing Resuts or Tag Fies. c. Seect a fie. Meeting Exchange dispays the poing fies. To print a traffic statistics fie: a. Seect Print. a. Seect Poing Resuts or Tag Fies. a. Seect a fie. b. Seect a printer. Meeting Exchange prints the poing fies. Aternativey, you can og into Meeting Exchange as a craft user and navigate to the /usr/ dcb/dbase/poprnts directory. Apri

132 Viewing Meeting Exchange information 132 Administering Meeting Exchange Servers

133 Chapter 11: Configuring PINs PIN code is an identification number that is unique to each participant (both moderators and conferees). The name of the participant and their unique identification number are stored in a PIN ist. When operators using the CRS Front End and moderators using the Web Porta, create a new participant, the CRS generates a PIN code for each new participant. If customers require additiona security for their conferences, they can book conferences that require a conference passcode and the participant s PIN code to access the conference. This chapter describes how to configure PINs for your customers. It contains the foowing sections: A short note on PIN functionaity Conference types PIN mode and the user experience A short note on PIN ists A short note on PIN functionaity At conference booking time, an operator using the CRS Front End or a moderator using the Web Porta can specify a PIN Mode. The PIN Mode options are: Off System Conference Off If an operator or moderator seects Off, Meeting Exchange does not use PIN codes for the conference reservation. System If an operator or moderator seects System, Meeting Exchange grants conference access to a participant if they enter the correct passcode and a PIN code which matches any entry in the system s PIN ist, which is stored in a database tabe on the Meeting Exchange appication Apri

134 Configuring PINs server. The CRS creates this PIN ist automaticay. When an operator adds new participants to a Cient s address book or a moderator adds new participants to their own address book, the CRS aocates a PIN to each new participant. Meeting Exchange stores the PIN in a system-generated PIN ist. System PIN Mode primariy identifies attendees. Conference If an operator, using CRS Front End, seects Conference, Meeting Exchange grants conference access to a participant ony if they have been invited to that particuar conference. In other words, it grants access if a participant enters the correct passcode and a PIN code which matches any entry in that particuar conference s PIN ist. The CRS automaticay creates a conference PIN ist for each conference. The conference PIN ist contains the PINs of participants who have been specificay invited to that particuar conference. Aternativey, if operators wish to use a specific PIN ist, the CRS aows them to enter a name in the PIN List fied. For more information on creating these PIN ists, see Creating PIN ists on page 136. Conference PIN Mode adds security to the conference. Conference types This section describes how PIN Mode operates for different conference types. There are a number of conference types: Unattended conferences Attended conferences Fexfow conferences Sef Registration conferences Unattended conferences For Unattended conferences, operators and moderators can choose Off, System, or Conference PIN Mode. Attended conferences For Attended conferences, Meeting Exchange disabes PIN Mode functionaity. 134 Administering Meeting Exchange Servers

135 PIN mode and the user experience Fexfow conferences For Fexfow conferences, operators and moderators can choose Off, System, or Conference PIN Mode. Sef Registration conferences If an operator using CRS Front End books a Sef Registration conference, Meeting Exchange disabes the PIN Mode options on the interface. The PIN Mode options are inaccessibe to operators because, for Sef Registration conferences, the Meeting Exchange automaticay uses the Conference PIN Mode. The CRS generates a subset of the PIN List database tabe for each Sef Registration conference. This subset contains ony the invited, or registered, participants. PIN mode and the user experience Meeting Exchange Users are participants, either moderators or conferees, who attend conference cas. The User experience varies depending on the PIN Mode. Tabe 24: User Experience PIN Mode Off System Conference Experience when Entering the Conference Participants enter their passcode on the teephone keypad. Participants enter their passcode and their PIN code on the teephone keypad. Participants enter their passcode and their PIN code on the teephone keypad. A short note on PIN ists You can create any number of PIN ists. You can then copy these fies to the appication server and oad them into the bridgedb database. This section describes how to create, copy, and oad PIN ists. It contains the foowing sections: Creating PIN ists Apri

136 Configuring PINs Loading PIN ists As an aternative to creating, copying, and oading PIN ists, the CRS automaticay generates a PIN ist for each conference. The automaticay-generated PIN ist contains the PINs of participants who have been invited to the particuar conference. The CRS names this automaticay-generated PIN ist using this naming convention: c_conference reference.txt. If operators wish to make use of this automaticay-generated PIN ist, they simpy eave the PIN List fied bank. If they eave the PIN List fied bank, the CRS automaticay assigns the automaticay-generated conference PIN ist to the conference. On the Web Porta, moderators cannot edit the PIN List fied. Meeting Exchange automaticay assigns the PIN ist, c_conference reference.txt to the conference. If operators and moderators add or deete participants after they book the conference, the CRS updates the PIN ist dynamicay. If operators import a ist of participants from an externa fie, using the Import button on the CRS Front End, the CRS adds their PINs to the system s PIN ist. Creating PIN ists To create a PIN ist, you require two fies: PINs.txt PINs.txt PINist.txt You must create these fies in a specia format. If they do not conform to the format, you may be unabe to oad them on to the appication server. Both fies require the use of the pipe ( ) to separate the fieds. If you do not enter any information in an optiona fied, ensure that you enter a space, foowed by pipe. For exampe: 8975 Tabe 25 describes the format of the pins.txt fie.. Tabe 25: PINs.txt Fie Format Fied Type Required CompanyRef Integer N CientImportID Char(50) N CientFirstName Char(30) You can enter either: CientLastName Char(30) CientFirstName and CientLastName or CientFuName 1 of Administering Meeting Exchange Servers

137 A short note on PIN ists Tabe 25: PINs.txt Fie Format (continued) Fied Type Required CientFuName Char(80) Y, or CientFirstName and CientLastName CientCompanyName Char(60) N CientAddrLine1 Char(40) N. Reserved for future use. CientAddrLine2 Char(40) N. Reserved for future use. CientAddrLine3 Char(40) N. Reserved for future use. CientAddrLine4 Char(40) N. Reserved for future use. CientMainPINCode Char(16) Y. Must be unique for non-null vaues. CientMainPhone Char(40) N CientMainFax Char(40) N. Reserved for future use. CientEmai Char(30) N. Reserved for future use. LineAux1 Char(80) N LineAux2 Char(80) N LineAux3 Char(80) N InsertTimet Integer in seconds since midnight, 1 Jan 1970 in GMT. N InsertLogin Char(30) N UpdateTimet Integer in seconds since midnight, 1 Jan 1970 in GMT. N UpdateLogin Char(30) N 2 of 2 Apri

138 Configuring PINs PINist.txt Tabe 26 describes the format of the pinist.txt fie. Tabe 26: PINList.txt Fie Format Fied Type Required PINListName Char(30) Y CientMainPINCode Char(16) Y PINCompanyName Char(60) Reserved for use by the CRS Sef Registration appication. PINCientName Char(40) Reserved for use by the CRS Sef Registration appication. Loading PIN ists To oad the PIN ists to the Meeting Exchange appication server, you must copy the fies to a batchdata directory. From this directory, you must oad the ists to the appication server database caed bridgedb. 1. Open a PuTTY session and og in as an sroot user. Note: Note: Note: PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid sroot password. The sroot ogin provides a higher eve of access to the server than the craft ogin. 2. Navigate to /usr/dcb/dbase/bridgedb/batchdata/. 3. Start a Session Contro Protoco (SCP) session using the Meeting Exchange appication server name for the PIN code fies. scp <system_name> 4. Log in to the bridgedb database. ogin: brdgdbo Password:******* Note: Contact your Avaya Support Representative for a vaid bridgedb password. 5. At the SCP prompt, enter binary to indicate that you want to copy the fies in binary format: scp> binary 138 Administering Meeting Exchange Servers

139 A short note on PIN ists 6. Run the foowing command command to move the pinist.txt fie from your workstation to the Meeting Exchange /usr/dcb/dbase/bridgedb/batchdata/ directory. put pinist.txt pinist.txt 7. Run the foowing command to move the pins.txt fie from your workstation to the Meeting Exchange /usr/dcb/dbase/bridgedb/batchdata/ directory. put pins.txt pins.txt 8. Exit the SCP session: scp> quit 9. Run a fu database backup before you oad the two fies into the bridgedb database. This step ensures that you can restore the database if there is an error. bridgedb_maintain_pg.sh no_prompt backup bridgedb 10. Run the foowing scripts to oad the two fies: batch_oad_pg.sh prompt pins /tmp/pins.txt batch_oad_pg.sh prompts pinist /tmp/pinist.txt Meeting Exchange dispays this prompt: Batch oading started. This may take a moment so pease be patient... Batch oad was successfu! 11. Run a fu database backup as described in step 9. Now the PIN ist is avaiabe for use. You must distribute the PIN ist name to operators if you want them to use it. Apri

140 Configuring PINs 140 Administering Meeting Exchange Servers

141 Chapter 12: Configuring recording Meeting Exchange incudes a feature which enabes customers to record their conferences. This feature is usefu for customers who wish to store any or a conferences for security reasons. It is aso usefu for customers who wish to make conferences avaiabe for payback, for exampe, to peope who were unabe to attend a conference. Meeting Exchange can store and manage recordings within the Meeting Exchange server environment. If customers use this option, it is often caed on-bridge recording. Aternativey, customers can send the conferences to an externa device for recording, management, and payback. If customers use this option, it is often caed off-bridge recording. If customers use the off-bridge recording option, they cannot make use of the payback faciities within Meeting Exchange. This chapter is mainy concerned with on-bridge recording. As an aside, some peope aso refer to the recording feature as Digita Record and Payback (DRP). Peope use this term because the featcfg fie ists the recording feature as DRP. Aso, it is caed digita because it is stored on the hard disk in a digita form. For more information on the featcfg fie, see Enabing features on page 43. To configure recording, you must perform a number of tasks, as foows: Enabing the recording feature Configuring recording properties Configuring the payback ca fow Managing fies Supporting an oder method of conference payback for Web Porta users Enabing the recording feature To enabe the recording feature, foow the same set of steps that you used for many other Meeting Exchange features: 1. Open a PuTTY session and og in as an sroot user. Note: Note: PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid sroot password. The sroot ogin provides a higher eve of access to the server than the craft ogin. Apri

142 Configuring recording 2. Navigate to /usr/dcb/bin and run the foowing command: featcfg The server ists the features and dispayed their status as instaed or not instaed. 3. Enabe recording using the foowing command: featcfg +DRP 4. Reboot the server using the foowing method, which Avaya recommends: a. Log in to Meeting Exchange as dcbmaint. b. From the System Administrator Main Menu, seect Re-initiaization. c. Seect Yes at the confirmation. d. Press the Enter/Return key. The server reboots and enabes the recording feature. Configuring recording properties To customize the recording feature, you must configure a number of parameters in the System Configuration menu. For a ist of a the parameters in the System Configuration menu, see System configuration properties on page 298. For more information on navigating to the System Configuration menu, see Customizing Meeting Exchange properties on page 63. For ega reasons, in many countries, participants must be informed that the conference is being recorded. As a resut, Meeting Exchange pays an audio message to inform them that the conference is being recorded. If an operator or a moderator pauses the recording and then subsequenty resumes it, Meeting Exchange repays the audio message. This is not configurabe. To configure recording properties: 1. Log in to Meeting Exchange as dcbmaint 2. Navigate to the System Administration Main Menu. 3. From the System Administrator Main Menu, seect Configurations. The Configurations screen provides you with an entry point for the customization of a of the conferencing properties. 4. Seect System Configuration. 142 Administering Meeting Exchange Servers

143 Configuring recording properties 5. Use the System Configuration screen to configure the recording properties. You must scro through a number of pages to ocate a the parameters that reate to the recording feature. System configuration properties on page 298 describes the parameters: Bridge Record Phone Number Dia String PreDia Deay Period Short Jump Medium Jump Long Jump Automatic Record A Secure Bocks Record Bridge Num DRP:Auto-gen fname 6. Navigate to the System Maintenance Main Menu. 7. Use the FDAPI Configuration screen to configure the number of annunciator channes. The Number of Ann Chans is the parameter. Meeting Exchange uses annunciator channes for paying greetings and in-conference announcements as we as for recording and paying back conferences. Essentiay, Meeting Exchange uses annunciator channes for any sound data going to or from the interna hard-disk. This setting sets the maximum number of those resources that Meeting Exchange uses at any one time. In an in-service depoyment, the record and payback featues hod the annunciator channe resource for ong periods of time. For this reason, the record and payback usage is capped at a sub-set (70%) of the vaue entered here. Meeting Exchange reserves 30% for the paying of reguar audio messages during conferences. This metric aims to baance the requirements of the reguar conference audio messages and the recording and payback feature. This parameter represents the number of overa annunciator channes. The patform imit is This is aso the defaut vaue. For more information on FDAPI resources, see Configuring server resources on page 56. Apri

144 Configuring recording Configuring the payback ca fow To enabe conference payback, you must add a cbuti entry for a payback cafow. For more information on configuring cbuti, see Configuring ca branding on page 44. Tabe 4 ists the cbuti coumns. Meeting Exchange ignores many of these coumns for the payback cafow. For exampe, in a payback cafow, Meeting Exchange ignores <rg>, <crs>, and <cre>. When users dia the DNIS that you configure for payback, Meeting Exchange pays the audio message that you enter in the <msg> coumn. In a typica in-service scenario, you coud enter a greeting message number here. If you enter a zero vaue in the <msg> coumn, Meeting Exchange does not pay a greeting message. Next, Meeting Exchange pays an audio message to prompt the user for a conference reference number. Once they enter the correct conference reference number, Meeting Exchange prompts them for their passcode. If they enter a vaid passcode, Meeting Exchange may additionay prompt them for their name before granting them access to the conference recording. If there are one or more recordings associated with the conference reference, Meeting Exchange ists the tota number of recordings and pays a series of messages that offer access to each recording. Managing fies As a system administrator, you must manage the recording fies and ensure that users can access them when required. Ensuring access for users Managing recordings Ensuring access for users Cas to the payback cafow occupy on-demand port resources. Your aocation of on-demand resources must take account of these ines. For more information on aocating port resources for on-demand and schedued cas, see Customizing the scheduer utiity on page 66. Managing recordings Meeting Exchange stores conference recordings in /usr3/confrp as Raw PCM audio, 8 KHz sampe rate, 16-bit resoution, mono, mu-law fies, wrapped up in a.wav header. 144 Administering Meeting Exchange Servers

145 Supporting an oder method of conference payback for Web Porta users As a genera rue: The S6200 can store approximatey 2400 hours of recordings. The S6800 can store approximatey 1200 hours of recordings. Individua recording fies contain up to four hours of digitay recorded conference diaog. In any individua conference, recording stops after four hours to ensure that the hard drive does not reach storage capacity prematurey. As a system administator, you must manuay manage the /usr3/confrp foder to ensure that it does not grow excessivey arge. Aso, if you upgrade to Meeting Exchange 5.2 from an oder version of Meeting Exchange, you must rename existing recording fienames. In previous versions of Meeting Exchange, recording fienames were a maximum of eight characters. The Meeting Exchange 5.2 payback feature cannot pay these recordings because it requires the fienames to have a different naming convention, as foows: <Reservation Comfirmation Number>+<Bridge Num>+XXXX If you enabe automatic naming of the recordings, using the DRP:Auto-gen fname parameter, the vaue of XXXX begins with 0001 and grows to If you enabe automatic naming, the vaue of XXXX grows sequentiay, as foows: If the operator or moderator stops and then restarts recording during the conference, Meeting Exchange increments the vaue of XXXX. Simiary, if a participants eave the conference and ater re-join, Meeting Exchange increments the vaue of XXXX. If you disabe automatic naming and opt for manua naming of the recordings, the vaue of XXXX begins with 1 and grows to Manua names can be any name that does not aready exist. If there is no reservation confirmation number, Meeting Exchange aocates zeros to the fiename in pace of a vaid confirmation number. This scenario coud occur if an operator, using Bridge Tak, seects participants and paces them into an empty conference room. To access oder recordings after you upgrade, you must rename them to accomodate this new naming convention. You must add the <Reservation Comfirmation Number>+<Bridge Num> prefix to the od fiename. For more information, see Upgrading from Meeting Exchange 5.0.x, 5.1.x, or 5.2 to 5.2 Service Pack 1 on page 193. Supporting an oder method of conference payback for Web Porta users For users of the Web Porta appication, or moderators, Meeting Exchange sti supports an oder method of conference payback. With the oder functionaity, moderators dia the conference teephone number and enter the recording fiename. Moderators can obtain the recording fiename from the My Recorded Conferences screen. The imitation with this method Apri

146 Configuring recording is that if the recording was made using a previous version of Meeting Exchange, such as Meeting Exchange 5.1, they cannot access the recording using this method. They must use the new method instead. If the recording was made using Meeting Exchange 5.2, they can access the recording using this oder method. If you deete a recording from the recordings foder at/usr3/confrp, these recordings may sti appear on the Web Porta My Recorded Conferences screen. However, moderators wi not be abe to access them. 146 Administering Meeting Exchange Servers

147 Chapter 13: Configuring anguages This chapter describes how Meeting Exchange handes anguages. It contains the foowing sections: Introduction to ocaization A point of carification regarding anguages Introduction to ocaization It is important to note that the Meeting Exchange 5.2 server processes and graphic user interfaces (GUIs) use Engish text. System administrators must understand Engish in order to successfuy insta, configure, and monitor Meeting Exchange. Simiary, operators and moderators must understand Engish in order to interact with GUIs, such as Bridge Tak, CRS Front End, and Web Porta. However, Avaya has transated the audio messages into a number of anguages. This transation feature extends to a moderator and conferee audio messages. Customers can use this feature to provide conference participants with a ocaized experience. This feature is especiay usefu in a depoyment in which a customer creates a arge number of on-demand conferences so that users do not need to interact with a booking interface. Simiary, it is usefu in a depoyment with in which a customer has Engish-speaking operators and foreign anguage participants. Meeting Exchange 5.2 supports a number of anguages, such as, Engish, Simpified Chinese, Japanese, Maaysian, Korean, French, German, Itaian, Russian, Spanish, Braziian Portuguese, and so on. In order to use a transated set of audio messages, see Configuring audio messages on page 151. In particuar, see the section Prompt sets on page 151 for a rea word exampe of how to configure Meeting Exchange for German audio messages. A point of carification regarding anguages At this point, it is worth carifying an important distinction between system anguage and conference anguage. System anguage is often caed DNIS-driven anguage. System anguage Conference anguage Apri

148 Configuring anguages Participant experience System anguage When you configure ca branding, using the cbuti too, you create an association between a diaed number identification service (DNIS) and an audio prompt set. This association creates the system anguage. In each row of a cbuti tabe, the <dnis> variabe represents the DNIS and the <ps> variabe represents the audio prompt set. So, for exampe, you coud create an association between the DNIS and the Engish audio prompt set. For more information, see Configuring ca branding on page 44 and in particuar, Tabe 4. Conference anguage When operators or moderators book a conference, using CRS Front End, Bridge Tak, or Web Porta, they can create an association between the conference and an audio prompt set. This association creates the conference anguage. Bridge Tak operators can access the Prompt Set drop-down ist in the Conference Scheduer utiity, CRS Front End operators can access the Prompt Set drop-down ist on the Options diaog, and Web Porta moderators can access the Prompt Set drop-down ist on the Advanced Booking Options screen. For more information, see Using Meeting Exchange, which is avaiabe on support.avaya.com. Users cannot specify an audio prompt set if they book their conference using Avaya Conference Scheduer for Microsoft Outook or the Avaya Scheduing Pug-in for IBM Lotus Notes. Participant experience When participants dia the DNIS, Meeting Exchange aways pays audio messages in the system anguage. For exampe, if you associate the DNIS with the Engish audio prompt set, participants aways hear Engish messages. Once participants enter their conference passcode, Meeting Exchange has visibiity of the conference settings. At this point, there are two possibe outcomes, as foows: Each row of the cbuti too aso has a parameter caed Use Conference Prompt Set <ucps>. The defaut vaue of <ucps> is Y. If you set <ucps> to N, Meeting Exchange pays the system audio prompt set when the ca routes to the bridge and unti the caer joins the conference. After the caer joins the conference, the Meeting Exchange server uses the system audio prompt set to pay prompts to the individua caer s ine and uses the conference audio prompt set to pay prompts to the whoe conference. Exampes of prompts payed to everyone in the conference incude: - Message Number 359 Your Conference is now being recorded 148 Administering Meeting Exchange Servers

149 A point of carification regarding anguages Note: - Message Number 361 Conference Recording has stopped - Message number 455 The Conference Recording is currenty paused - Message Number 343 The Conference is now in sient mode - Message Number 343 The Conference is now in tak mode Note: When Meeting Exchange routes caers to the Enter queue, it pays the audio prompts from Prompt Set 0 ony. For more information, see Tabe 4. Apri

150 Configuring anguages 150 Administering Meeting Exchange Servers

151 Chapter 14: Configuring audio messages During a conference, Meeting Exchange pays audio messages to participants to inform them of conference information and to prompt them for a response. These audio messages are sometimes caed audio prompts or annunicator messages. A group of audio messages is often caed a prompt set. This chapter describes how to insta and configure audio messages. It contains the foowing sections: A short note about audio messages Recording new audio messages Enabing system wide messages A short note about audio messages This section introduces some technica points in reation to audio messages. It contains the foowing sections: Prompt sets Per-conference messages System wide messages Prompt sets A group of audio messages is often caed a prompt set. Avaya ships Meeting Exchange with the capabiity of supporting 20 prompt sets. You can configure your depoyment to use one or severa of these prompt sets. Each prompt set contains 2000 message sots. By defaut, Meeting Exchange uses 299 of these message sots for the basic audio messages that guide participants through the process of using the conferencing server. For a fu ist of defaut messages, see Audio messages on page 327. In the remaining message sots, you can record new messages and configure Meeting Exchange to use these new messages. For more information, see Recording new audio messages on page 155. Avaya does not recommend recording new messages over the defaut messages. Avaya stores the Meeting Exchange prompt sets on the appication server in the /usr2/ Prompts/Set# directory, where Set# ranges from Set0 to Set20. Set0 contains the defaut Apri

152 Configuring audio messages Engish audio messages. Each of the directories contains a foder for messages and a foder for numbers. For exampe: /usr2/prompts/set0/messages/ /usr2/prompts/set0/numbers/ /usr2/prompts/set1/messages/ /usr2/prompts/set1/numbers/ By defaut, the Engish anguage messages are shipped in Prompt Set 0 and a other prompt sets are inked to Prompt Set 0. However, Avaya has recorded the 299 defaut messages in a number of anguages, in addition to Engish. Here is an exampe of a depoyment of prompt sets. Tabe 27: Prompt Sets Language Name/abe in the CRS and Web Porta Engish Prompt Set 1 Simpified Chinese/Mandarin Prompt Set 2 Japanese Prompt Set 3 Engish Prompt Set 4 Korean Prompt Set 5 French Prompt Set 6 German Prompt Set 7 Itaian Prompt Set 8 Russian Prompt Set 9 Latin Spanish Prompt Set 10 Braziian Portuguese Prompt Set 11 Engish for teetype devices Prompt Set 12 Engish Prompt Set 13 Canadian French Prompt Set 14 Note: Note: Prompt Set 3 is reserved for Japanese word ordering 1 of Administering Meeting Exchange Servers

153 A short note about audio messages Tabe 27: Prompt Sets (continued) Language Name/abe in the CRS and Web Porta Castiian Spanish Prompt Set 15 Engish (United Kingdom) Prompt Set 16 2 of 2 Avaya does not ship the transated messages by defaut. If you wish to obtain a copy of a these messages, contact your Avaya Support Representative. There are a number of steps invoved in the configuration of any additiona anguage. For exampe, if you want to configure your depoyment to pay German messages: 1. Contact your Avaya Support Representative and obtain a copy of the German prompt set. 2. Open a PuTTY session and og in as an sroot user. Note: Note: PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid sroot password. 3. Make Prompt Set 2 avaiabe for prompts, as foows: rm Set2 mkdir Set2 mkdir Set2/messages mkdir Set2/numbers 4. Save the German prompt set to: /usr2/prompts/set2/messages/ /usr2/prompts/set2/numbers/ 5. You must perform the next steps on each of the Bridge Tak cient machines: a. Cose a instances of Bridge Tak. b. Open the Tempate.xm fie in the Bridge Tak instaation directory and configure the foowing parameters to ensure that the German prompt set is dispayed as an option on Bridge Tak. For a fu description of Tempate.xm parameters, see Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. <Property vaue="2" type="integer" name="numpromptsetlangs"/> <Property vaue="engish" type="string" name="promptsetlang1"/> <Property vaue="german" type="string" name="promptsetlang2"/> c. Save the changes. Now, the prompt sets are enabed. Apri

154 Configuring audio messages The audio messages are Raw PCM audio, 8 KHz sampe rate, 16-bit resoution, mono, mu-law fies. These messages have a fiename but no fie extension. The fiename of the saved messages is one ess than the message number on Meeting Exchange. For exampe, message 2 has a fiename of 1. You can configure the instances in which Meeting Exchange pays messages by ogging on to Meeting Exchange as dcbadmin and navigating to System Administrator Main > Configurations > Voice Message Configuration. For more information on the audio message parameters, see Voice Message configuration on page 315. As there are 2000 message sots in each prompt set and ony 299 defaut messages, you can use the spare message sots to record customized messages, such as Per-conference messages on page 154 or System wide messages on page 155. Per-conference messages Operators can use Bridge Tak to record messages to any message sot. For exampe, they can record a new message for a specific conference. Using the Cient Registration Server (CRS) Front End, they can associate the message with the conference. If operators use Bridge Tak to schedue their conference, they cannot associate the message with the conference. The message sot that they use must be in the prompt set that is associated with the conference. So, if Prompt Set 1 is associated with the conference, operators must record the conference message in a message sot within Prompt Set 1. Here is an exampe of a rea word scenario: A Bridge Tak operator records a message using their teephone audio path and the Toos > Annunciator diaog. They record the message in Prompt Set 2, message sot They edit the corresponding text fied with the message text. Meeting Exchange stores the message in /usr2/prompts/set2/messages/1499 A CRS operator schedues a conference and seects Prompt Set 2 and message 1500 as the conference message. This feature is ony avaiabe for depoyments of Meeting Exchange on the S6200 server patform. It is not avaiabe if your depoyment consists of an S6800 conferencing server. The CRS Front End does not have visibiity of the message text so Avaya recommends maintaining a separate transcript of messages for operators who have CRS Front End access but not Bridge Tak access. Moderators can aso use a DTMF keypad sequence (#2, by defaut) to record their own message for their conference. These messages, created by moderators, are entirey independent of the messages that the operator creates. These messages can be up to 30 seconds in ength. To avoid confusion, it is a good idea to refer to the messages that the operator creates as conference wecome messages and to refer to the messages that the moderator creates as persona wecome messages. 154 Administering Meeting Exchange Servers

155 Recording new audio messages For more information on using Bridge Tak and the CRS Front End, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. System wide messages Operators can aso use Bridge Tak to record messages that Meeting Exchange pays to a conferences. Meeting Exchange pays this message before any conference-specific messages. System administrators enabe this system wide message using the Configurations menu. For more information, see Enabing system wide messages on page 159. A known issue exists in Meeting Exchange 5.2 in reation to these per-conference and system messages. Specificay, the Avaya Conferencing Provider Appication Programming Interface (ACP API) does not support these messages. So, if the ACP API is used to route participants to a conference, the participants do not hear these messages. It is important to note that the Avaya Pug-ins for Microsoft Outook and IBM Lotus Notes use the ACP API to support the Cick to Join button. So, if participants enter a conference by cicking Cick to Join, they do not hear the per-conference or system messages. Recording new audio messages This section describes how to record new audio messages. It contains the foowing sections: A short note about recording audio messages Configuring prompt set names Configuring prompt set names Maintaining a transcript of messages A short note about recording audio messages By defaut, Meeting Exchange foows certain rues in reation to paying audio messages. It is important to consider these rues when recording and configuring new audio messages. By defaut, Meeting Exchange pays message 1 on each teephone ine entering the conferencing system. Meeting Exchange pays message 242 to caers who respond to a bast dia, uness the operator specifies another message when they initiate the bast dia. Meeting Exchange pays message 247 as the PIN code prompt for unattended conferences with PIN codes security in effect. Apri

156 Configuring audio messages Meeting Exchange immediatey paces caers who are attending attended conferences, in the Enter Queue. If you configure ca branding for your customer, Meeting Exchange pays the message that you configure in for that ca branding entry. If you assign 0 to a DNIS, Meeting Exchange disabes messages for any conferences that use this DNIS.For more information on configuring ca branding, see Branding the customer experience on page 89. Meeting Exchange 5.2 supports 30,000 entries for ca branding. Meeting Exchange pays some messages to individua ines and pays other messages to the entire conference. When Meeting Exchange pays a message to the entire conference, it mutes a conference ines. Meeting Exchange may deay some actions unti the message finishes paying. Meeting Exchange pays tones during messages. If participants are istening to a ine-specific message, Meeting Exchange does not pay any conference tones to that participant. When Meeting Exchange pays a message to the conference, operators can perform actions, such as removing a ine from a conference. If an operator accesses a ine waiting for a ine message, Meeting Exchange does not pay any message to that ine that it was intending to pay. Meeting Exchange records a audio messages aong with the conference. Under conditions of extremey heavy oad, Meeting Exchange may deay paying a message. This behavior can resut in a pause between a conference event and the corresponding message. This behavior can occur if messages are ong or if many participants enter a conference within a short period of time. If this situation occurs, Avaya recommends adjusting the engths of messages or substituting a tone for a message. You can configure Meeting Exchange to pay a continuousy ooping on hod message in the Enter Queue. If you enabe the On-Hod Msg. Frequency parameter, this change does not take effect unti the Enter Queue cears. For more information on the On-Hod Msg. Frequency parameter, see System configuration properties on page 298. Configuring prompt set names In a defaut instaation of Meeting Exchange 5.2, the prompt sets are caed Prompt Set 1, Prompt Set 2, and so on. So, when Bridge Tak operators cick the Message Prompt Set drop-down ist, they see the prompt sets isted as Prompt Set 1, Prompt Set 2, and so on. Operators access this drop-down ist in step 3 of Recording new messages on page 157. Before you depoy Bridge Tak in a muti-anguage environment, Avaya recommends changing these abes so that they represent the appropriate anguage. To change the abe names, you must update the Tempate.xm fie ocated in the Bridge Tak instaation path. For more 156 Administering Meeting Exchange Servers

157 Recording new audio messages information on the parameters in this fie, see Administering Meeting Exchange Appications. This guide is avaiabe on support.avaya.com. Recording new messages There are two ways to record new messages. You can use an externa audio editing program or you can use the Avaya program, Bridge Tak. This section describes how to use Bridge Tak. For more information on using Bridge Tak, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. Before you use Bridge Tak to record messages, you must first perform two configuration tasks: On the Meeting Exchange appication server, you must make the prompt sets avaiabe. On Bridge Tak, you must configure tempate.xm to dispay the prompt sets in the Message Prompt Set drop-down ist. Both of these steps are described in Prompt sets on page 151. It is important to note that if your depoyment consists of an S6800 server, Meeting Exchange does not support recording from Bridge Tak to mutipe prompt sets. Some messages are initia segments, such as The fie number you entered is:. Some messages are midde segments, such as the digits 0-9. Some messages are tai segments, such as Participants currenty in your conference. Some messages are standaone segments, such as Conference security has been activated. When recording new messages, you must record sience before and after the spoken portion using the foowing guideines: Record approximatey 0.5 to 0.9 seconds of sience before and after messages that are standaone segments. Record approximatey 0.05 to 0.09 seconds of sience before midde and tai segments. Record approximatey 0.2 to 0.3 seconds of sience after initia and midde segments. If the message consists of severa segments, record approximatey 0.5 to 0.9 seconds of sience before the first segment and after the ast segment. To record a new message: 1. Dia in an Operator ine to Bridge Tak. For more information about using Bridge Tak, see Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. 2. Navigate to Toos > Annunciator to dispay the Annunciator Messages diaog. 3. Seect a prompt set from the Message Prompt Set drop-down ist. You can record a message in any message sot in any prompt set. 4. Seect a message sot from the ist of message sots. 5. Cick Record and say the message. Apri

158 Configuring audio messages 6. Cick Stop when you are finished. 7. Cick Payback to verify the message. It is good practice to enter the message text in the Message Summary coumn. 8. Cick Cose. Maintaining a transcript of messages Meeting Exchange ships with a written transcript of the defaut messages. This transcript is usefu for seeing the message text without having to isten to each message. If you record new messages, Avaya recommends keeping this ist up to date with the new message text. You can maintain a transcript of messages using two methods. As a system administrator, you can maintain the transcript fie on the appication server. Aternativey, operators can maintain the transcript using Bridge Tak. For more information on maintaining the transcript in Bridge Tak, see Using Meeting Exchange, which is avaiabe on support.avaya.com. It is important to note that there is ony one transcript fie, regardess of the number of transated prompt sets that you have instaed in your depoyment. This means that the text description of the messages in prompt set 1 is the same for a other prompt sets. To update the written transcript on the appication server: 1. Log in to Meeting Exchange as dcbadmin to dispay the System Administration Main Menu. 2. From the System Administrator Main Menu, seect Configurations. The Configurations screen provides you with an entry point for the customization of a of the conferencing properties. 3. Seect Ca Routing Configuration. 4. Seect Fexibe Annunciator Messages. The Fexibe Annunciator Messages screen ists a the message text. You have to scro down to see the first defaut pre-recorded message. 5. Make any changes you require and save your changes. You can save up to 70 characters. 158 Administering Meeting Exchange Servers

159 Enabing system wide messages Enabing system wide messages You can configure Meeting Exchange to pay a message to a conferences. Meeting Exchange pays this message before any per-conference messages. In-service exampes of the use of this feature incude messages such as: This is a oss of service announcement. Conferencing services wi not be avaiabe 2am to 7am January 20th due to essentia maintenance. Apoogies for any inconvenience. Haf price conferencing this weekend! To enabe a system wide message: 1. Record a message using Bridge Tak and make a note of the message sot. For more information, see Recording new audio messages on page Log in to Meeting Exchange as dcbadmin to dispay the System Administration Main Menu. 3. From the System Administrator Main Menu, seect Configurations. The Configurations screen provides you with an entry point for the customization of a of the conferencing properties. For more information on this screen, see Finding parameters by name on page Seect System Configuration. 5. Set the System aert parameter to ON. Enter the message number, from 1 to 2000 in Aert message. A important point to note in reation to system wide messages is that if a caer dias in using SCAN cafow, Meeting Exchange pays the message in the anguage configured to the DNIS. If a caer dias in using the DIRECT cafow, Meeting Exchange pays the message in the anguage associated with the conference. This behavior is due to the fact that the DIRECT cafow routes the ca directy to the conference. For more information on cafows and the DNIS, see Tabe 4. Apri

160 Configuring audio messages 160 Administering Meeting Exchange Servers

161 Chapter 15: Connecting Meeting Exchange to your network You can connect Meeting Exchange to your existing network in a number of ways. You can directy connect the Meeting Exchange infrastructure to a singe Avaya Aura Communication Manager. You can aso connect the Meeting Exchange infrastructure to Communication Manager by way of a SIP Enabement Server (SES) proxy. You can aso connect Meeting Exchange to Avaya Aura Session Manager. The Avaya Systems Integration Lab (SIL) has fuy tested Meeting Exchange 5.2 with Session Manager. The documentation which describes this integration is avaiabe on the Avaya DevConnect website. For more information, see Additionay, if your network is a circuit-switched teephone network, you can connect Meeting Exchange to an Audiocodes Mediant media gateway. The Audiocodes gateway is a Voice over Internet Protoco (VoIP) media gateway, which acts as a transation unit between a Pubic Switched Teephone Network (PSTN) teecommunications network and the Meeting Exchange VoIP teecommunications network. The media gateway performs the conversion from Time Division Mutipexing (TDM) to VoIP. This conversion enabes your depoyment to use the Session Initiation Protoco (SIP). SIP is a signaing protoco, widey used for controing mutimedia communication sessions such as voice and video cas over Internet Protoco (IP). This chapter describes some sampe depoyments. The requirements of your network infrastructure may differ from those described here. Use these instructions as a genera guide. The Meeting Exchange soution aso supports a number of other integrations and severa hardware options from other vendors. For more information on these depoyments, contact your Avaya Support Representative. Connecting directy to Communication Manager Connecting to an SES proxy Connecting to AudioCodes Connecting directy to Communication Manager You can connect Meeting Exchange to a singe Communication Manager. A Meeting Exchange and Communication Manager integration routes incoming cas using a series of hierarchica tabes. When a caer makes a teephone ca to Communication Manager, the Communication Manager server anayses a dia pan tabe to see if the teephone number pattern matches an entry. If it finds a match, it reads the corresponding routing instructions. As an exampe, these instructions coud direct the server to anayze a second tabe, caed the Uniform Dia Pan (UDP) tabe. Again, it anayses the UDP tabe to see if the pattern matches an Apri

162 Connecting Meeting Exchange to your network entry. If it finds a match, it reads the corresponding routing instructions. As an exampe, these instructions coud direct the server to anayze a third tabe, caed the Automatic Aternate Routing (AAR) tabe. If it finds a match, it reads the corresponding trunk information and wi route the ca through that trunk. As a ast step, the server anayses a route pattern tabe to see if there are any further instructions before it paces the ca into the Meeting Exchange server. Instructions coud incude adding or removing some digits from the teephone number string. These steps through each of the hierarchica tabes iustrates the possibiities and fexibiity of Communication Manager. You can configure the fieds to process the teephone number according to the specific requirements of your depoyment. To enabe this functionaity, you must perform a number of tasks, as foows: Adding Meeting Exchange to the node names ist Adding a signaing group Adding a trunk group Adding a diapan entry Adding a UDP entry Adding an AAR entry Adding a route pattern Configuring Meeting Exchange for Communication Manager The steps in the foowing sections describe how to connect Communication Manager to Meeting Exchange. Adding Meeting Exchange to the node names ist To add Meeting Exchange as a node: 1. Navigate to change node-names ip. 2. Enter the name of the Meeting Exchange server in the Name coumn. 3. Enter the IP address of the Meeting Exchange server in the IP Address coumn. 4. Save your changes. Adding a signaing group Typicay, the signaing board on Communication Manager is a Contro Loca Area Network (CLAN) board. If your depoyment uses a singe CLAN board to connect your SIP trunk from Communication Manager to Meeting Exchange, there is a singe point of faiure if this is the primary connection. A more resiient option woud be to configure mutipe CLAN boards to connect to Meeting Exchange. For exampe, in a configuration with two CLAN boards, Meeting 162 Administering Meeting Exchange Servers

163 Connecting directy to Communication Manager Exchange sends a SIP option message to both CLAN boards. If both CLAN boards are operationa, Meeting Exchange connects the ca to the first CLAN board. If the first CLAN board fais, it responds with a service unavaiabe message when Meeting Exchange sends a SIP option message. If Meeting Exchange receives a service unavaiabe message, it sends a SIP invite message to the second CLAN board and connects the ca. Simiary, there are mechanisms in pace in Communication Manager which enabe it to detect if the Meeting Exchange server has faied. For exampe, using Look Ahead Routing (LAR), you can configure a routing preference for additiona connection attempts if Communication Manager cannot connect to the Meeting Exchange server on the first attempt. For more information on configuring mutipe CLAN boards and the LAR tabe, see the Communication Manager documentation, which is avaiabe on support.avaya.com. As an aternative to using a CLAN board, you can use a processor ethernet to provide network connectivity. You must set up a processor ethernet on Communication Manager. Before you can configure the processor ethernet, you must ensure that the feature is enabed in your icense fie. The main configuration takes pace on the Configure server - Set Identities page, but you must aso add the processor ethernet if it has not aready been added. The command to add the processor ethernet is: add ip-interface procr. You can then set the trunk and signaing in the exact same way as for a CLAN board. You set Near-end Node Name to the hostname: procr. On the Meeting Exchange side, configure the TenumToUri.tab fie to connect to the network using the processor ethernet. For more information, see Administering Avaya Aura Communication Manager and Instaing and Upgrading the Avaya S8300 Server, which are avaiabe on support.avaya.com. To add a signaing group: 1. Navigate to add signaing-group. 2. Ensure that the Group Type is sip. 3. Ensure that the Transport Method is ts. When you seect ts, Communication Manager enters the vaue 5061 in the Near-end Listen Port and Far-end Listen Port fieds. 4. Enter the name of a signaing board on the Communication Manager gateway in the Near-end Node Name fied. This is the signaing board that you have seected for the connection from Communication Manager to Meeting Exchange. It is typicay a CLAN board. 5. Enter the name of the Meeting Exchange server in the Far-end Node Name fied. 6. Ensure that Direct IP-IP Audio Connections is n. 7. Ensure that DTMF over IP is rtp-payoad. 8. Save your changes. Apri

164 Connecting Meeting Exchange to your network Adding a trunk group To add a trunk group: 1. Navigate to add trunk-group. 2. Enter a abe to refer to the Meeting Exchange server in the Group Name fied. 3. Ensure that the Service Type is tie. 4. Ensure that the Group Type is sip. 5. Ensure that the TAC is Enter the signaing group that corresponds to the signaing group that you added in Adding a signaing group on page 162 in the Signaing Group fied. 7. Set the Number of Members fied to the number of teephone ines or ports that you require in this trunk. Each trunk supports 255 ports. 8. Navigate to the second screen in the add trunk-group series. 9. Set the Preferred Minimum Session Refresh Interva to Navigate to the second screen in the add trunk-group series. 11. Set the Numbering Format to private. 12. Navigate to the fourth screen, caed Protoco Variations, in the add trunk-group series. 13. Set the Teephone Event Payoad Type as foows: If your depoyment consists of ony H.323 endpoints, set the Teephone Event Payoad Type to 127. If your depoyment consists of H.323 and SIP endpoints, set the Teephone Event Payoad Type to Save your changes. Adding a diapan entry To add a diapan entry: 1. Navigate to change diapan anaysis. 2. For each of the conference teephone numbers, enter number in the Diaed String coumn. You enter a partia string, rather than entering each individua teephone number. For exampe, you can enter 45 in the Diaed String fied. In this way, Communication 164 Administering Meeting Exchange Servers

165 Connecting directy to Communication Manager Manager can process instructions for a teephone numbers that start with 45, such as 4511, 4512, 4513, 4514, and so on. 3. Enter the number of digits in the teephone number in the corresponding Tota Length coumn, 4. Enter the routing instruction in the Ca Type coumn. For exampe, if you woud ike Communication Manager to anayze the UDP tabe to see if the pattern matches an entry, set this coumn to udp. 5. Save your changes. Adding a UDP entry To add a uniform diapan entry: 1. Navigate to change uniform anaysis. 2. In the Matching Pattern and Len coumns, enter the numbers that you entered in the Diaed String coumn and Tota Length coumns in Adding a diapan entry on page 164. You can configure the fieds to process the teephone number according to the specific requirements of your depoyment. Here, we present an iustrative configuration. 3. Enter aar in the Net coumn to ensure that Communication Manager anayzes the AAR tabe to see if the pattern matches an entry. 4. Save your changes. Adding an AAR entry To add an automatic aternate routing digit anaysis entry: 1. Navigate to change aar anaysis. 2. In the Diaed String and Tota Min Max coumns, enter the numbers that you entered in the Matching Pattern and Len coumns in Adding a UDP entry on page 165. You can configure the fieds to process the teephone number according to the specific requirements of your depoyment. Here, we present an iustrative configuration. 3. Enter the number of the trunk on which you woud ike Communication Manager to send the ca to Meeting Exchange in the Route Pattern coumn. 4. Ensure that the Ca Type coumn is set to aar. 5. Save your changes. Apri

166 Connecting Meeting Exchange to your network Adding a route pattern To add a route pattern: 1. Navigate to change route pattern. 2. Enter the number of the trunk on which you woud ike Communication Manager to send the ca to Meeting Exchange in the Grp No coumn. 3. Configure the fieds to process the teephone number according to the specific requirements of your depoyment. For exampe, you coud instruct Communication Manager to drop two digits from the teephone number by entering 2 in the No. De Dgts fied. This instruction ensures that Communication Manager ony sends the remaining digits to Meeting Exchange. 4. Save your changes. Configuring Meeting Exchange for Communication Manager To compete an integration with Communication Manager, there are a number of configuration tasks to perform on the Meeting Exchange appication server. These steps are detaied in this section. To configure Meeting Exchange: 1. Open a PuTTY session and og to the Meeting Exchange server as a craft user. Note: Note: PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid craft password. 2. Navigate to the foowing directory and view the system.cfg fie: cd /usr/ipcb/config cat system.cfg 3. Ensure that the transport method for both the MyListener and respcontact settings is ts, using the foowing syntax: MyListener=sip:Digit String@Meeting Exchange appication server IP;transport=ts respcontact=<sip:digit String@Meeting Exchange appication server IP;transport=ts> This step is because Communication Manager expects the Transport Layer Security (TLS) method of transmission. 166 Administering Meeting Exchange Servers

167 Connecting to an SES proxy 4. Configure two further settings as foows: minsetimervaue=100 sessionrefreshtimer=1800 Avaya recommends these vaues because they optimize communications between Meeting Exchange and Communication Manager. Your depoyment may have specific requirements and you may want to set different vaues. The minsetimervaue corresponds to a fied in the Communication Manager trunk-group screen caed Preferred Minimum Session Refresh Interva (sec). The sessionrefreshtimer corresponds to a fied in the Communication Manager signaing group screen caed Session Estabishment Timer (min). 5. Save your changes. 6. In the same directory, view the tenumtouri.tab fie: cat tenumtouri.tab Meeting Exchange uses the tenumtouri.tab fie to enabe operators and moderators to dia out to an externa teephone number from the Meeting Exchange appication server. In a depoyment with Communication Manager, Meeting Exchange routes the dia out cas through Communication Manager. 7. Add an entry row to the tabe to represent Communication Manager using the foowing syntax: sip:digit String@Communication Manager IP:5061;transport=ts This step is because Communication Manager expects the Transport Layer Security (TLS) method of transmission. 8. Save your changes. Connecting to an SES proxy The steps in the foowing section describes how to configure an SES proxy in your depoyment. In a depoyment of Meeting Exchange with an SES proxy, the SES proxy acts as a gateway between Communication Manager and Meeting Exchange. In this scenario, any cas to Meeting Exchange route through the Communication Manager server, then the SES proxy server, before terminating on the Meeting Exchange appication server. Communication Manager handes a H.323 and PSTN cas. Typicay, Communication Manager does not hande SIP cas. The SES proxy handes SIP cas. If your depoyment uses some SIP endpoints, you must perform some additiona configuration steps. To enabe this depoyment, you must perform a number of tasks, as foows: Configuring Meeting Exchange for an SES proxy Configuring Communication Manager for an SES proxy Apri

168 Connecting Meeting Exchange to your network Configuring Communication Manager and the SES proxy for SIP cas Configuring Meeting Exchange for an SES proxy To configure Meeting Exchange: 1. Compete steps 1 to 5 from Configuring Meeting Exchange for Communication Manager on page In the same directory, view the proxyconfigtabe.cfg fie. cat proxyconfigtabe.cfg 3. Add an entry to represent the SES proxy server that you intend to use. Tabe 28 describes the fieds. Tabe 28: ProxyConfigTabe.cfg Fied Description Syntax ProxyUri Contact To From usrname password The IP address of the SES proxy server that you intend to use. The address of the Meeting Exchange DNIS that you wish to aocate to the SES proxy server. The address of the SES proxy DNIS that corresponds with the Meeting Exchange DNIS that you entered in the Contact fied. The address of the SES proxy DNIS that corresponds with the Meeting Exchange DNIS that you entered in the Contact fied. The account username which Meeting Exchange wi use to register with the SES proxy server. The account password which Meeting Exchange wi use to register with the SES proxy server. sip:<ses proxy IP address> sip:<dnis>@<meeting Exchange IP address> sip:<dnis>@<ses proxy IP address> sip:<dnis>@<ses proxy IP address> XXXX XXXX 168 Administering Meeting Exchange Servers

169 Connecting to an SES proxy Tabe 28: ProxyConfigTabe.cfg Fied Description Syntax refreshtime The refresh time shoud be 1800, as you configured in the system.cfg fie ID A unique numeric identifier for this entry. X 4. In the same directory, view the mxmonitor.cfg fie. cat mxmonitor.cfg 5. Ensure that sipsource is set to oca. The defaut vaue for sipsource is crs. 6. In the same directory, view the processtabe.cfg fie. cat processtabe.cfg 7. Ensure that sipagent has an autostart vaue of 0. Aso, ensure that mxmonitor has an autostart vaue of Lasty, add an entry to the cbuti fie for the Meeting Exchange DNIS that you wish to aocate to the SES proxy server. For more information, see Adding a DNIS on page 51. Configuring Communication Manager for an SES proxy As in the case of a direct connection to Communiation Manager, the same routing processes appy: A Meeting Exchange and Communication Manager integration routes incoming cas using a series of hierarchica tabes. When a caer makes a teephone ca to Communication Manager, the Communication Manager server anayses a dia pan tabe to see if the teephone number pattern matches an entry. If it finds a match, it reads the corresponding routing instructions. As an exampe, these instructions coud direct the server to anayze a second tabe, caed the Uniform Dia Pan (UDP) tabe. Again, it anayses the UDP tabe to see if the pattern matches an entry. If it finds a match, it reads the corresponding routing instructions. As an exampe, these instructions coud direct the server to anayze a third tabe, caed the Automatic Aternate Routing (AAR) tabe. If it finds a match, it reads the corresponding trunk information and wi route the ca through that trunk. As a ast step, the server anayses a route pattern tabe to see if there are any further instructions before it paces the ca into the Meeting Exchange server. Instructions coud incude adding or removing some digits from the teephone number string. To enabe a Meeting Exchange integration with an SES proxy, you must perform the foowing tasks on the Communication Manager server: Adding Meeting Exchange to the node names ist Apri

170 Connecting Meeting Exchange to your network Adding the SES proxy to the node names ist Adding a signaing group for Meeting Exchange Adding a signaing group for the SES proxy Adding a trunk group for Meeting Exchange Adding a trunk group for the SES proxy Adding a diapan entry for Meeting Exchange Adding a diapan entry for the SES proxy Adding an AAR entry for Meeting Exchange Adding an AAR entry for the SES proxy Adding a route pattern for Meeting Exchange Adding a route pattern for the SES proxy Adding Meeting Exchange to the node names ist To add Meeting Exchange as a node: 1. Navigate to change node-names ip. 2. Enter the name of the Meeting Exchange server in the Name coumn. 3. Enter the IP address of the Meeting Exchange server in the IP Address coumn. 4. Save your changes. Adding the SES proxy to the node names ist To add the SES proxy as a node: 1. Navigate to change node-names ip. 2. Enter the name of the SES proxy server in the Name coumn. 3. Enter the IP address of the SES proxy server in the IP Address coumn. 4. Save your changes. Adding a signaing group for Meeting Exchange To add a signaing group: 1. Navigate to add signaing-group. 2. Ensure that the Group Type is sip. 170 Administering Meeting Exchange Servers

171 Connecting to an SES proxy 3. Ensure that the Transport Method is ts. When you seect ts, Communication Manager enters the vaue 5061 in the Near-end Listen Port and Far-end Listen Port fieds. 4. Enter the name of a signaing board on the Communication Manager gateway in the Near-end Node Name fied. This is the signaing board that you have seected for the connection from Communication Manager to Meeting Exchange. It is typicay a CLAN board. 5. Enter the name of the Meeting Exchange server in the Far-end Node Name fied. 6. Ensure that Direct IP-IP Audio Connections is y. 7. Ensure that DTMF over IP is rtp-payoad. 8. Save your changes. Adding a signaing group for the SES proxy To add a signaing group: 1. Navigate to add signaing-group. 2. Ensure that the Group Type is sip. 3. Ensure that the Transport Method is ts. When you seect ts, Communication Manager enters the vaue 5061 in the Near-end Listen Port and Far-end Listen Port fieds. 4. Enter the name of a signaing board on the Communication Manager gateway in the Near-end Node Name fied. This is the signaing board that you have seected for the connection from Communication Manager to the SES proxy server. It is typicay a CLAN board. 5. Enter the name of the SES proxy server in the Far-end Node Name fied. 6. Ensure that Direct IP-IP Audio Connections is y. 7. Ensure that DTMF over IP is rtp-payoad. 8. Save your changes. Adding a trunk group for Meeting Exchange To add a trunk group: 1. Navigate to add trunk-group. 2. Enter a abe to refer to the Meeting Exchange server in the Group Name fied. 3. Ensure that the Service Type is tie. 4. Ensure that the Group Type is sip. Apri

172 Connecting Meeting Exchange to your network 5. Ensure that the TAC is Enter the signaing group that corresponds to the signaing group that you added in Adding a signaing group for Meeting Exchange on page 170 in the Signaing Group fied. 7. Set the Number of Members fied to the number of teephone ines or ports that you require in this trunk. Each trunk supports 255 ports. 8. Navigate to the second screen in the add trunk-group series. 9. Set the Preferred Minimum Session Refresh Interva to Navigate to the second screen in the add trunk-group series. 11. Set the Numbering Format to private. 12. Save your changes. Adding a trunk group for the SES proxy To add a trunk group: 1. Navigate to add trunk-group. 2. Enter a abe to refer to the SES proxy server in the Group Name fied. 3. Ensure that the Service Type is tie. 4. Ensure that the Group Type is sip. 5. Ensure that the TAC is Enter the signaing group that corresponds to the signaing group that you added in Adding a signaing group for the SES proxy on page 171 in the Signaing Group fied. 7. Set the Number of Members fied to the number of teephone ines or ports that you require in this trunk. Each trunk supports 255 ports. 8. Navigate to the second screen in the add trunk-group series. 9. Set the Preferred Minimum Session Refresh Interva to Navigate to the second screen in the add trunk-group series. 11. Set the Numbering Format to private. 12. Navigate to the fourth screen, caed Protoco Variations, in the add trunk-group series. 13. Set the Teephone Event Payoad Type to Save your changes. 172 Administering Meeting Exchange Servers

173 Connecting to an SES proxy Adding a diapan entry for Meeting Exchange To add a diapan entry: 1. Navigate to change diapan anaysis. 2. For each of the conference teephone numbers, enter number in the Diaed String coumn. You enter a partia string, rather than entering each individua teephone number. For exampe, you can enter 45 in the Diaed String fied. In this way, Communication Manager can process instructions for a teephone numbers that start with 45, such as 4511, 4512, 4513, 4514, and so on. 3. Enter the number of digits in the teephone number in the corresponding Tota Length coumn, 4. Enter the routing instruction in the Ca Type coumn. For a depoyment with an SES proxy, Avaya recommend setting this vaue to aar. 5. Save your changes. Adding a diapan entry for the SES proxy To add a diapan entry: 1. Navigate to change diapan anaysis. 2. For each of the conference teephone numbers, enter number in the Diaed String coumn. You enter a partia string, rather than entering each individua teephone number. For exampe, you can enter 45 in the Diaed String fied. In this way, Communication Manager can process instructions for a teephone numbers that start with 45, such as 4511, 4512, 4513, 4514, and so on. 3. Enter the number of digits in the teephone number in the corresponding Tota Length coumn, 4. Enter the routing instruction in the Ca Type coumn. For a depoyment with an SES proxy, Avaya recommend setting this vaue to aar. 5. Save your changes. Adding an AAR entry for Meeting Exchange To add an automatic aternate routing digit anaysis entry: 1. Navigate to change aar anaysis. Apri

174 Connecting Meeting Exchange to your network 2. In the Diaed String and Tota Min Max coumns, enter the numbers that you entered in the Matching Pattern and Len coumns in Adding a diapan entry for Meeting Exchange on page 173. You can configure the fieds to process the teephone number according to the specific requirements of your depoyment. Here, we present an iustrative configuration. 3. Enter the number of the trunk on which you woud ike Communication Manager to send the ca to Meeting Exchange in the Route Pattern coumn. 4. Ensure that the Ca Type coumn is set to aar. 5. Save your changes. Adding an AAR entry for the SES proxy To add an automatic aternate routing digit anaysis entry: 1. Navigate to change aar anaysis. 2. In the Diaed String and Tota Min Max coumns, enter the numbers that you entered in the Matching Pattern and Len coumns in Adding a diapan entry for the SES proxy on page 173. You can configure the fieds to process the teephone number according to the specific requirements of your depoyment. Here, we present an iustrative configuration. 3. Enter the number of the trunk on which you woud ike Communication Manager to send the ca to the SES proxy in the Route Pattern coumn. 4. Ensure that the Ca Type coumn is set to aar. 5. Save your changes. Adding a route pattern for Meeting Exchange To add a route pattern: 1. Navigate to change route pattern. 2. Enter the number of the trunk on which you woud ike Communication Manager to send the ca to Meeting Exchange in the Grp No coumn. 3. Configure the fieds to process the teephone number according to the specific requirements of your depoyment. For exampe, you coud instruct Communication Manager to drop two digits from the teephone number by entering 2 in the No. De Dgts fied. This instruction ensures that Communication Manager ony sends the remaining digits to Meeting Exchange. 4. Save your changes. 174 Administering Meeting Exchange Servers

175 Connecting to an SES proxy Adding a route pattern for the SES proxy To add a route pattern: 1. Navigate to change route pattern. 2. Enter the number of the trunk on which you woud ike Communication Manager to send the ca to the SES proxy in the Grp No coumn. 3. Configure the fieds to process the teephone number according to the specific requirements of your depoyment. For exampe, you coud instruct Communication Manager to drop two digits from the teephone number by entering 2 in the No. De Dgts fied. This instruction ensures that Communication Manager ony sends the remaining digits to the SES proxy. 4. Save your changes. Configuring Communication Manager and the SES proxy for SIP cas Communication Manager handes a H.323 and PSTN cas. Typicay, Communication Manager does not hande SIP cas. The SES proxy handes SIP cas. Within the environment of Communication Manager, Session Initiation Protoco (SIP) cas are often caed Off PBX stations. If your depoyment incudes SIP teephones, you must perform some additiona configuration tasks on the Communication Manager server and on the SES proxy server, as foows: Configuring the SES proxy for SIP Configuring Communication Manager for SIP Configuring the SES proxy for SIP To configure the SES: 1. Open the SES Administration interface. 2. Add an entry to the Communication Manager Servers ist, as foows: a. Enter information to refer to the Communication Manager server. b. In the SIP Trunk IP Address fied, enter the IP of the signaing board that you have seected for the connection from Communication Manager to the SES proxy. This is the CLAN IP address. c. Add extensions to the Communication Manager server. For exampe, you can add the Meeting Exchange appication server as an extension. 3. Save your changes. Apri

176 Connecting Meeting Exchange to your network Configuring Communication Manager for SIP To configure Communication Manager: 1. Add a new station, using the ogin detais that you used for the Communication Manager server in Configuring the SES proxy for SIP on page Create an off-pbx-teephone station-mapping using the same Communication Manager extension detais. Connecting to AudioCodes The AudioCodes gateway is a Voice over Internet Protoco (VoIP) media gateway, which acts as a transation unit between a Pubic Switched Teephone Network (PSTN) teecommunications network and the Meeting Exchange VoIP teecommunications network. The media gateway performs the conversion from Time Division Mutipexing (TDM) to VoIP. Configuring Meeting Exchange for AudioCodes To configure Meeting Exchange: 1. Open a PuTTY session and og to the Meeting Exchange server as a craft user. 2. Navigate to the foowing directory and view the system.cfg fie: cd /usr/ipcb/config cat system.cfg 3. Add the IP address of the Meeting Exchange appication server: IPAddress=(XX.XX.XXX.X) 176 Administering Meeting Exchange Servers

177 Connecting to AudioCodes 4. Configure the MyListener and respcontact settings as foows: If you are using the Transport Layer Security (TLS) method of transmission: MyListener=sips:Digit Exchange appication server IP:5061;transport=ts respcontact=<sips:digit Exchange appication server IP:5061;transport=ts> If you are using the Transmission Contro Protoco (TCP) method of transmission: MyListener=sip:Digit Exchange appication server IP:5060;transport=tcp respcontact=<sip:digit Exchange appication server IP:5060;transport=tcp> If you are using the User Datagram Protoco (UDP) method of transmission: MyListener=sip:Digit Exchange appication server IP:5060;transport=udp respcontact=<sip:digit Exchange appication server IP:5060;transport=udp> 5. Configure two further settings as foows: minsetimervaue=900 sessionrefreshtimer= Save your changes. 7. In the same directory, view the tenumtouri.tab fie: cat tenumtouri.tab Meeting Exchange uses the tenumtouri.tab fie to enabe operators and moderators to dia out to an externa teephone number from the Meeting Exchange appication server.. 8. Add an entry row to the tabe to represent the AudioCodes gateway using the foowing syntax: sip:digit gateway IP:5060;transport=tcp 9. Save your changes. 10. Lasty, you must add a DNIS entry to the cbuti tabe. Ensure that you seect SCAN as the function. For more information on cbuti, see Configuring ca branding on page 44. In particuar, for more information on the cbuti fieds, see Tabe 4. Configuring AudioCodes for Meeting Exchange To configure the AudioCodes gateway, you must perform a number of tasks. You can perform these tasks using the AudioCodes gateway embedded Web server. The embedded Web server Apri

178 Connecting Meeting Exchange to your network presents a set of Web-based configuration screens. You can access these screens using any standard Internet browser, using this syntax: address of AudioCodes gateway> On these configuration screens, you can cick Submit or Burn to save your configuration. These buttons are ocated at the top of the screen. You can aso cick Reset to discard your configuration updates. This option is ocated in the Device Actions menu. The steps for configuring AudioCodes are as foows: Configuring PSTN trunks Configuring TDM Configuring direct connectivity Configuring ca routing Configuring transport type Configuring TLS Configuring codecs Configuring DTMF Configuring PSTN trunks To configure the PSTN trunks: 1. Access the Web interface for the AudioCodes gateway. 2. Cick Configuration on the eft of the screen. 3. Navigate to PSTN Settings > Trunk Settings. 4. Cick Stop Trunk to modify the seected trunk. 5. Scro to Genera Settings. 6. Seect E1 Euro ISDN from the Protoco Type drop-down ist. 7. Scro to Trunk Configuration. 8. Seect Recovered from the Cock Master drop-down ist. 9. Seect HDB3 from the Line Code drop-down ist. 10. Seect E1 Framing MFF CRC4 EXT from the Framing Method drop-down ist. The E1 trunk aways uses the HDB3 ine code and the MFF CRC4 EXT framing method. 11. Scro to ISDN Configuration. 12. Seect User side from the ISDN Termination Side drop-down ist. 13. Leave the remaining fieds in this section as the defaut vaues and cick Submit or Burn. 178 Administering Meeting Exchange Servers

179 Connecting to AudioCodes Configuring TDM To configure TDM: 1. Access the Web interface for the AudioCodes gateway. 2. Cick Configuration on the eft of the screen. 3. Navigate to TDM Configuration > TDM Bus Settings. 4. Seect ALaw from the PCM Law Seect drop-down ist. 5. Seect Network from the TDM Bus Cock Source drop-down ist. 6. Seect Disabe from the TDM Bus PSTN Auto Cock and TDM Bus PSTN Auto Cock Reverting drop-down ists. 7. Seect 9 from the TDM Bus Loca Reference drop-down ist. 8. Cick Submit or Burn. Configuring direct connectivity To configure direct connectivity: 1. Access the Web interface for the AudioCodes gateway. 2. Cick Configuration on the eft of the screen. 3. Navigate to Protoco Configuration > Proxy & Registration. 4. Seect No from the Use Defaut Proxy drop-down ist. 5. Cick Submit or Burn. Configuring ca routing To configure ca routing: 1. Access the Web interface for the AudioCodes gateway. 2. Cick Configuration on the eft of the screen. 3. Navigate to Protoco Configuration > Routing Tabes > Te to IP Routing. 4. Add an entry to represent the ca route from Meeting Exchange to the AudioCodes gateway. For exampe, to ensure that a cas to Meeting Exchange route to the AudioCodes gateway, enter the widcard symbo, *, as foows: a. Enter * in the Src. Trunk Group ID, Dest Phone Prefix, and Source Phone Prefix fieds. b. Enter the IP address of the Meeting Exchange appication server in the Dest. IP Address fied. Apri

180 Connecting Meeting Exchange to your network 5. Seect UDP, TCP, or TLS from the Transport Type drop-down ist to match your depoyment requirements. 6. Cick Submit or Burn. Configuring transport type You can configure the AudioCodes gateway to communicate with Meeting Exchange using UDP, TCP, or TLS communication: Configuring TCP Configuring TLS Configuring TCP - To configure TCP: 1. Access the Web interface for the AudioCodes gateway. 2. Cick Configuration on the eft of the screen. 3. Navigate to Protoco Configuration > Protoco Definition > SIP Genera Parameters. 4. Seect TCP from the SIP Transport Type drop-down ist. 5. Enter 5060 in the SIP TCP Loca Port and SIP Destination Port fieds. 6. Cick Submit or Burn. Configuring TLS - The TLS method of communication requires the exchange of keys. When you buy Meeting Exchange, Avaya ships the TLS keys on the Meeting Exchange appication server in the /usr/oca/ss/certs foder. By defaut, Avaya encrypts these key fies. To enabe the TLS method of communication, you must decrypt a key fie and insta it on the AudioCodes gateway. This key fie is caed CiCert1.pem. The decryption and instaation steps are incuded here. For diaing out over TLS, use the foowing format: sips:digitstring@audiocodes gateway IP:5061;transport=ts To configure TLS: 1. Access the Web interface for the AudioCodes gateway. 2. Cick Configuration on the eft of the screen. 3. Navigate to Protoco Configuration > Protoco Definition > SIP Genera Parameters. 4. Seect TLS from the SIP Transport Type drop-down ist. 5. Enter 5061 in the SIP TLS Loca Port and SIP Destination Port fieds. 6. Navigate to Security Settings > Genera Security Settings. 7. Seect TLS 1.0 ony from the TLS Version drop-down ist. Meeting Exchange ony supports TLS Administering Meeting Exchange Servers

181 Connecting to AudioCodes 8. In the Internet browser address fied, enter: address of AudioCodes gateway>/adminpage 9. Enter HTTPSCIPHERSTRING in the Parameter Name fied. 10. Enter ALL in the Enter Vaue fied. 11. Cick Appy New Vaue. Meeting Exchange supports the foowing cipher strings: TLS_RSA_with_DES_CBC_SHA TLS_RSA_with_AES_128_CBC_SHA Advanced Encryption Standard (AES) is a symmetric 128-bit bock data encryption technique. It repaces the oder Data Encryption Standard (DES) which uses a 56-bit key. 12. Decrypt the TLS key on the Meeting Exchange appication server: a. Open a PuTTY session and og to the Meeting Exchange server as a craft user. b. Navigate to the foowing directory and enter this command: cd /usr/oca/ss/certs openss OpenSSL> rsa -in CiKey1.pem -out CiKey1Decrypt.pem c. When Meeting Exchange prompts you for a password, enter CiKey Insta the TLS key fies on the AudioCodes gateway: a. Access the Web interface for the AudioCodes gateway. b. Cick Configuration on the eft of the screen. c. Navigate to Security Settings > Certificates. d. Browse to CiCert1.pem in the Send Trusted Root Certificate Store fie from your computer to the device fied. Cick Send Fie. e. Browse to CiKey1Decrypt.pem in the Send Private Key fie from your computer to the device fied. Cick Send Fie. Configuring codecs To administer your codec requirements: 1. Access the Web interface for the AudioCodes gateway. 2. Cick Configuration on the eft of the screen. 3. Navigate to Protoco Configuration > Protoco Definition > Coders. 4. In the first row, enter the codec information for your preferred codec. For exampe: a. Seect G.711 A-aw from the Coder Name drop-down ist. Apri

182 Connecting Meeting Exchange to your network b. Seect 20 from the Packetization Time drop-down ist. c. Seect 64 from the Rate drop-down ist. d. Enter 8 in the Payoad Type fied. e. Seect Disabed from the Sience Suppression drop-down ist. 5. Cick Submit or Burn. AudioCodes aocates the highest priority to the codec in the first row and uses it whenever possibe. The remaining rows represent your descending order of preference and priority. Meeting Exchange supports G.711, G.722, G.726, G.729AB, and ilbc. Configuring DTMF Meeting Exchange supports two methods of transmission with regard to DTMF tones. Meeting Exchange can transmit DTMF information in the same channe as voice information. This is caed in-band DTMF. Aternativey, Meeting Exchange can transmit DTMF information in a separate channe. This is caed out-of-band DTMF or RFC Configuring in-band Configuring out-of-band Configuring in-band - To configure in-band DTMF transmission: 1. Access the Web interface for the AudioCodes gateway. 2. Cick Configuration on the eft of the screen. 3. Navigate to Protoco Configuration > Protoco Definition > DTMF & Diaing. 4. Seect No from the Decare RFC 2833 in SDP drop-down ist. 5. Cick Submit or Burn. Configuring out-of-band - To configure in-band DTMF transmission: 1. Access the Web interface for the AudioCodes gateway. 2. Cick Configuration on the eft of the screen. 3. Navigate to Protoco Configuration > Protoco Definition > DTMF & Diaing. 4. Seect Yes from the Decare RFC 2833 in SDP drop-down ist. 5. Seect RFC 2833 from the 1st Tx DTMF Option drop-down ist. 6. Cick Submit or Burn. 182 Administering Meeting Exchange Servers

183 Chapter 16: Configuring secure rea-time transport protoco (SRTP) The secure reatime transport protoco (SRTP) is a form of encrypted transport. Using this protoco, you can ensure that communications between Meeting Exchange and Avaya Aura Communication Manager are secure and protected. To configure this form of secure communications, you must perform some configuration tasks on the Communication Manager server and on the Meeting Exchange server. This chapter describes each of these tasks and is a subset of the tasks described in Connecting Meeting Exchange to your network on page 161. To compete these steps, you must be famiiar with many Communication Manager terms. For SRTP to operate successfuy in your depoyment, you must set the Communication Manager to be non-shuffing. In other words, in an SRTP-enabed depoyment, there can be no direct IP connectivity between endpoints. Communication Manager must hande the media for each endpoint. Configuring Meeting Exchange Configuring Communication Manager Verifying SRTP Configuring Meeting Exchange To configure Meeting Exchange for secure communications, you must update four fies on the Meeting Exchange appication server or bridge. The four fies are: /usr/ipcb/config/system.cfg /usr/ipcb/config/softmediaserver.cfg /usr/ipcb/config/tenumtouri.tab /usr/ipcb/config/uritotenum.tab To configure SRTP: 1. Open a termina window, such as PuTTY. PuTTY is a Linux SSH cient that aows you to connect to other machines, giving you a termina window. You can downoad PuTTY from 2. Log in to the appication server (bridge) virtua machine using PuTTY. 3. Enter the name craft and the password craft01. Apri

184 Configuring secure rea-time transport protoco (SRTP) 4. Use the sroot command to change from craft to sroot access. The sroot command is: su sroot The password is sroot Navigate to the foowing directory and view the system.cfg fie: cd /usr/ipcb/config cat system.cfg 6. Ensure that the transport method for both the MyListener and respcontact settings is ts, using the foowing syntax: MyListener=sip:Digit Exchange appication server IP;transport=ts respcontact=<sips:digit Exchange appication server IP;transport=ts> This step is because Communication Manager expects the Transport Layer Security (TLS) method of transmission. 7. Save your changes. 8. In the same directory, view the softmediaserver.cfg fie: cat softmediaserver.cfg 9. In this fie, enabe security by ensuring that it is set to 1, or true. securityenabed=1 10. Save your changes. 11. In the same directory, view the tenumtouri.tab fie: cat tenumtouri.tab Meeting Exchange uses the tenumtouri.tab fie to enabe operators and moderators to dia out to an externa teephone number from the Meeting Exchange appication server. In a depoyment with Communication Manager, Meeting Exchange routes the dia out cas through Communication Manager. For more information on the tenumtouri.tab fie, see Configuring patterns for diaing out on page Add an entry row to the tabe to represent Communication Manager using the foowing syntax: sips:digit String@Communication Manager IP:5061;transport=ts This step is because Communication Manager expects the Transport Layer Security (TLS) method of transmission. 13. Save your changes. 184 Administering Meeting Exchange Servers

185 Configuring Communication Manager 14. In the same directory, view the UriToTenum.tab fie: cat UriToTenum.tab The UriToTenum states that the Meeting Exchange appication server shoud recognize a DNIS entered by a Moderator during a conference and dia out using a corresponding URI. For more information on the UriToTenum fie, see Configuring patterns for diaing in on page 96. You must modify the <sip vaues to change them to <sips. For exampe, for the widcard entry: ""*"*<sips:*"$1@communication Manager 15. Restart the Meeting Exchange appication server. Configuring Communication Manager This section describes some sampe depoyments. The requirements of your network infrastructure may differ from those described here. Use these instructions as a genera guide. You must connect the Communication Manager server and the Meeting Exchange server in the usua way, by adding Meeting Exchange as a node on Communication Manager, as described in Connecting directy to Communication Manager on page 161. You can configure a depoyment in which some network regions support SRTP and some do not support SRTP. Aside from the settings and procedures described in Connecting directy to Communication Manager on page 161, there are a number of configuration settings of particuar importance to an SRTP configuration, as foows: On the ip-codec set screen, configure a new codec set. For the new codec set, set Media Encryption to 1-srtp-aescm128-hmac80. Ensure that this is the ony entry in the ist. Ensure that the none entry is not in the ist. On the ip-network region screen, assign a name and switch off Direct IP-IP Audio Connections. Associate the codec-set you just configured. On the add signaing-group and add trunk group screens, foow the exact steps here Adding a signaing group on page 162 and here Adding a trunk group on page 164. Associate these entities with the SRTP-enabed network region. Verifying SRTP It is a good idea to verify the secure communications before you pace Meeting Exchange in service. To verify this functionaity, you require severa downoadabe appications: Apri

186 Configuring secure rea-time transport protoco (SRTP) A sniffer trace appication, such as tcpdump for the Linux operating system. tcpdump is a command-ine packet anayzer. Cick here to downoad it: #atest-reease. Wireshark or Etherea. Wireshark and Etherea are network protoco anayzers. Cick here or to downoad. WinSCP. WinSCP is an appication which enabes you to securey copy fies over a network. The Linux operating system aready contains utiities that perform the actions of WinSCP and PuTTY, so you do not need to downoad them. Note: Note: To perform these verification steps, you must be famiiar with WinSCP, Wireshark or Etherea and a sniffer trace appication, such as tcpdump. 1. Log in to the appication server (bridge) virtua machine using PuTTY, as described in Configuring Meeting Exchange on page Enter this command to ensure that a processes are up and running: dcbps The number of processes various across depoyments. 3. Ensure that the sipagent process is running. 4. Log in to Communication manager and ensure that the signaing group and trunk are in service. You can check their status using the status signaing group and status trunk group screens. 5. Pace a teephone ca to Meeting Exchange and ensure that it uses SRTP. For more information, see Making a ca on page Pace a teephone ca from Meeting Exchange, using the Dia Out feature, To dia out, you can press *1 on your teephone, by defaut. 7. Using a sniffer trace appication, obtain a sniffer trace of the teephone ca which you made to the Meeting Exchange server. a. Once the ca is compete, press CTRL+C to terminate the trace. b. Transfer the trace fie to a computer running the Wireshark or Etherea appications. You can transfer the fie using the WinSCP appication. c. Confirm that no payoad data is saved and that you cannot access any payback of the ca. 186 Administering Meeting Exchange Servers

187 Chapter 17: Configuring security features Meeting Exchange 5.2 contains a number of enhanced security features. These features enabe customers to aocate varying eves of protection to their communications. The features are described in this manua and in the rest of the Meeting Exchange 5.2 documentation suite, which is avaiabe on support.avaya.com. This chapter references some of these features. Configuring secure recordings Configuring additiona PINs Configuring secure recordings Moderators can ock conferences. The act of ocking a conference prevents further participants from joining and aso excudes operators. You can configure Meeting Exchange to aow moderators to record ocked conferences or you can configure Meeting Exchange to prevent them from recording ocked conferences. For more information, see Configuring recording properties on page 142. Configuring additiona PINs Meeting Exchange 5.2 supports highy secure conferencing through the addition of new chaenges and barriers to conference entry. Now, Operators can book secure conferences that require participants to enter a passcode, an empoyee identification number, and a secret PIN. For more information on this feature, see Using Meeting Exchange and Administering Meeting Exchange Appications. Both of these guides are avaiabe on support.avaya.com. Apri

188 Configuring security features 188 Administering Meeting Exchange Servers

189 Chapter 18: Configuring Externa Passcode Vaidation (EPV) Externa passcode vaidation (EPV) is an optiona feature that enabes Meeting Exchange to vaidate moderator and conferee passcodes and Persona Identification Numbers (PIN codes) on an externa server. Introducing EPV Introducing the process Configuring the XML code Configuring EPV for fexfow conferences Configuring biing Configuring settings reating to stranded participants Testing the configuration Introducing EPV With EPV enabed, you can integrate Meeting Exchange into a distributed audio conference infrastructure where you can use externa servers to schedue conferences. In this configuration, you can store conference parameters on externa databases. If you decide to impement a Meeting Exchange soution that invoves EPV, you must disabe the Conference Scheduer appication. The Conference Scheduer appication is part of the Bridge Tak appication. Operators use it to schedue conferences. With EPV, an externa reservation server supports a conference reservations. To disabe the Conference Scheduer appication, configure the Status parameter, as described in Tabe 6. When EPV is enabed, Meeting Exchange uses HTTP to send requests to the externa passcode server, where passcodes and PIN codes are stored and vaidated The externa server communicates directy back to Meeting Exchange by sending an XML document that conforms to the Document Type Definition, (epv.dtd). Figure 15 shows the components and data fow in the distributed infrastructure. September

190 Configuring Externa Passcode Vaidation (EPV) Figure 15: EPV Enabed-System Externa Components Distributed Infrastructure Audio Conference Patform EPV Conference Interface HTTP Passcode Vaidation & Data Transfer Passcode Database Server Database Query Program Conference Reservation Server Reservation Interface Conference Information Conference 1 Conference 2 Conference 3 XML Data Transfer & Synchronization Reservation Records System Memory Conference Records Reservation database XML Document HTT epv.dtd Note: Note: Meeting Exchange creates daiy og fies of EPV events. The fies are ocated in the /usr/dcb/apiog directory. The fiename consists of a singe string that denotes the year, month, and day (yyyymmdd). For exampe, fie is generated for January 09, Introducing the process When the first caer attempts to enter a conference by providing a passcode in response to a system prompt, Meeting Exchange requests vaidation of the passcode from the passcode database server. If the database server determines the passcode is vaid, it confirms the request and upoads the conference information to Meeting Exchange, where it is stored in system memory. Meeting Exchange starts the conference and vaidates passcodes entered by a subsequent caers based on the conference information in memory received from the database server. If the first caer enters an invaid passcode, the passcode database server withhods vaidation and notifies Meeting Exchange. The number of times that Meeting Exchange repeats the passcode prompt to the caer depends on the vaue specified for the Scan Attempts parameter for the Schedue. For more information the Scan Attempts parameter, see Customizing the scheduer utiity on page 66 and Tabe 6 in particuar. 190 Administering Meeting Exchange Servers

191 Configuring the XML code If a reservation incudes a PIN code, the database server confirms the request in the same manner as it vaidates the conference passcode. If a caer enters an invaid PIN code, Meeting Exchange repeats the PIN code prompt based on the Scan Attempts parameter. Configuring the XML code This section describes the protoco for EPV servers capabe of parsing the arguments from the request URI, vaidating the passcode, and returning the resut in XML form. It contains the foowing sections: Configuring the chdbased.reg fie Understanding the format of requests Testing your code Understanding the format of responses Configuring the chdbased.reg fie An EPV impementation reies on configuration information stored in the chdbased.reg fie instaed in the /usr/dcb/dbase/admin directory. The fie contains a section, [xmdatasource] which defines the configuration settings for EPV. At instaation time, the chdbased.reg fie contains the foowing defaut settings: [xmdatasource] version=1.0 bridgeid=specte700 address=ocahost URI=/epvtest pinguri=/epvtest/ping.htm cmduri=/epvtest/epvcmd.htm port=80 timeout=10 connections=1 test=fase September

192 Configuring Externa Passcode Vaidation (EPV) Tabe 29 describes the attributes and settings in the chdbased.reg fie. Use the information in this tabe to edit the chdbased.reg settings for your configuration. Tabe 29: chdbased.reg Attribute Settings Attribute Version BridgeId Address URI PingURI cmduri Port Timeout Connections Test Description Current version of the protoco. One to 63 characters identifying the bridge name. The IP address or name of the EPV server. The Universay Recognized Identifier is used for passcode vaidation requests. Entries in this fied are imited 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. Points to page containing the keep aive response. Entries in this fied are imited to 127 characters. The URI that defines where the system sends the conference attribute updates. Currenty ony updates to the Leader PIN are supported. The Port the system connects to on the HTTP server. 80 is the defaut for HTTP. The amount of time in seconds to wait for a response from the EPV server. The number of connections to open to the EPV server. Each connection handes a singe EPV request. Requests are asynchronous, therefore severa requests may be made without bocking ca processing. The attribute setting depends on the EPV server s capacity. For instance, if the EPV server can ony process one request at a time, connections shoud be set to 1. However, if it can process mutipe requests simutaneousy, connections shoud be set to more the 1. Used for testing with a dumb HTTP server. When test is set to True, the passcode being verified is used as the name of an htm fie. For exampe, to vaidate a passcode of on a test HTTP server, pace a fie with the name htm in the /epvtest directory. 192 Administering Meeting Exchange Servers

193 Configuring the XML code Understanding the format of requests When the chdbased.reg configuration information is accurate and the specified EPV server is avaiabe, Meeting Exchange estabishes the specified number of connections to the EPV server. Each passcode and PIN code vaidation request is sent to the EPV server using the HTTP GET command. The passcode, the PIN code, and severa other parameters, are sent in the GET request as arguments in the URI. Tabe 30 describes information sent to the EPV server. Tabe 30: GET Request Arguments Argument Description Defaut Vaue pc The passcode to vaidate. none V Version of the protoco Setting for the version attribute in the epdv.reg fie. The defaut is 1.0. Bn Bridge name Setting for the bridgeid attribute in chdbased.reg. Defaut is specte700 Pt An Dn The port or channe on which the ca resides. Automatic Number Identification (ANI) digits, if avaiabe. Typicay the phone number of the caer. Diaed Number Identification Service (DNIS) digits, if avaiabe. Typicay the number the caer diaed to reach the bridge. rq Reservation Group number 0 ct The current time, in seconds, that have eapsed since midnight, 1 January 1970, Greenwich Mean Time none none none none September

194 Configuring Externa Passcode Vaidation (EPV) The HTTP GET request uses the foowing syntax: GET [URI, with arguments] HTTP/1.1 Host: [address from chdbased.reg] [empty ine] For exampe: GET / epvtest?pc=97979&v=1.0&bn=specte700&pt=1&an=6354&dn=6200&ct=9999 HTTP/1.0 Host: webmaster7 Where: Tabe 31: Expanation of argument This argument: Is set to this vaue: This argument: Is set to this vaue: Address webmaster7 Pt 1 URI /epvtest An 6354 pc Dn 6200 V 1.0 ct 9999 Bn specte700 Tip: Tip: Refer to rfc2616 for a compete description of the HTTP Request. A internet Request For Comments documents (i.e. RFCs) are avaiabe at Understanding the format of responses Once the Externa Passcode server vaidates the GET message from the bridge, the externa passcode server repies with a vaid XML response which conforms to the epv.dtd. Note: Note: The dtd is instaed in /usr/dcb/dbase/admin. Figure 16 shows a vaid XML response which uses epv.dtd: 194 Administering Meeting Exchange Servers

195 Configuring the XML code Figure 16: Exampe XML response using the epv.dtd <?xm version="1.0"?> <!DOCTYPE specte PUBLIC "-//Avaya Inc//DTD for Avaya Conferencing Systems//EN" "specte.dtd"> <!-- Sampe vfow conference passcode:701 Leader PIN:777 MUSIC=on MOD HUP=off NAME REC=off Entry/Exit=message EXTREC=t ADDSEC=t AUXCODE=t --> <specte> <spectesys700> <epvresponse> <passcodestatus>valid</passcodestatus> <passcode>701</passcode> <conferenceinfo> <starttime>0</starttime> <duration>1440</duration> <maxchans>60</maxchans> <codeduration>1440</codeduration> <conferenceid>9701</conferenceid> <DTMFCommandSet>2</DTMFCommandSet> <confseccode>701</confseccode> <eaderpin>777</eaderpin> <eaderpinstatus>0</eaderpinstatus> <pmin>3</pmin> <pmax>7</pmax> <confname>xml701</confname> <confsecurity>1</confsecurity> <confentrytone>3</confentrytone> <confexittone>3</confexittone> <modhangup>0</modhangup> <musicsource>1</musicsource> <ondemandlines>1</ondemandlines> <nrpsetting>0</nrpsetting> <pinmode>0</pinmode> <pinistname></pinistname> <biingcodes>d</biingcodes> <extrecord>1</extrecord> <addseccode>1</addseccode> <auxcode>1</auxcode> <resgroup>0</resgroup> </conferenceinfo> </epvresponse> </spectesys700> </specte> September

196 Configuring Externa Passcode Vaidation (EPV) Configuring EPV for fexfow conferences Typicay, fexfow conferences are conferences in which a participants enter a conferee passcode on their teephone keypad. After entering a conferee passcode, moderators can enter a moderator passcode to promote their status. In fexfow conferences, moderator passcodes are often caed eader PINs. It is important to understand that, in the context of fexfow conferences, the eader PIN is the moderator passcode. The PIN, in this situation, is a passcode. Within the wider Meeting Exchange environment, a PIN is defined as an identification number that is unique to each participant (both moderators and conferees). The name of the participant and their unique identification number are stored in a PIN ist. When operators using the CRS Front End and moderators using the Web Porta, create a new participant, the CRS generates a PIN code for each new participant. For more information on PIN code and PIN mode, see Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. Ensuring that the second eve passcodes feature operates successfuy Configuring eader PINs Configuring mandatory biing codes for fexfow Ensuring that the second eve passcodes feature operates successfuy If your depoyment uses fexfow functionaity and EPV, you must configure a particuar setting in order to successfuy use the second eve passcode feature. In an EPV depoyment, in which operators use fexfow conferencing, operators can seect the second eve passcode option at conference booking time. In the EPV, the second eve passcode feature is caed the Security Code fied. When operators enabe the Security Code fied at booking time, the <addsecconf> parameter is set to true or 1. In order for this feature to work, you must aso configure a setting in the System Configuration section of the Meeting Exchange server. For more information on this setting, see Conference Passcode on page 307 and see Second Leve Passcode on page 368. Configuring eader PINs If Meeting Exchange is configured for fexfow, when it queries the EPV server for the passcode, the EPV server can return a vaue identifying the status of the Leader PIN for the conference. The status can be: vaid, expired, or expiring. When Meeting Exchange returns the "expired" or 196 Administering Meeting Exchange Servers

197 Configuring EPV for fexfow conferences "expiring" status vaues, it pays an audio prompt requesting that the Leader PIN be updated. Tabe 32 describes the fieds and settings reated to Leader PIN expiration status vaues. Tabe 32: Fexfow Leader PIN Status Vaues Fied type Description eaderpinstatus Integer The expiration status of the Leader PIN for a vfow conference. Where, -1 (Vaid) The Leader PIN is vaid and is not set to expire within the next 15 days. The system does not pay a warning regarding pending expiration. (defaut) 0 (Expired) The Leader PIN has expired. The system prompts the user, "This Leader PIN has expired and must be changed." 1-15 (Expiring) The Leader PIN wi expire in this number of days. The system prompts the user, "This Leader PIN is set to expire in <number> of days. Press 1 to change or star (*) to defer." pmin Integer Minimum string ength for a new Leader PIN. 0-16, or the maximum vaue aowed by the system configuration. The defaut entry, 0,causes the system to use the system-wide setting. pmax Integer Maximum string ength for a new Leader PIN. 0-16, or the maximum vaue aowed by the system configuration. The defaut entry, 0,causes the system to use the system-wide setting Figure 17 is an excerpt from an XML response which shows the Leader PIN settings for an expired PIN code. In this exampe, the new Leader PIN is set to "777." This three-digit string meets the requirement estabished by the minimum ength (pmin) and maximum ength (pmax) settings. Figure 17: EPV HTML Command <eaderpin>777</eaderpin> <eaderpinstatus>0</eaderpinstatus> <pmin>3</pmin> <pmax>7</pmax> September

198 Configuring Externa Passcode Vaidation (EPV) Meeting Exchange can send commands to the EPV server to update conference schedue data. The cmduri parameter in the xmdatasource section of the /usr/dcb/dbase/admin/ chdbased.reg fie defines the URI where EPV commands are sent. 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 Meeting Exchange is requesting. The cmdtok parameter is foowed by a set of command-specific parameters. Currenty, the ony supported command updates the eader PIN in a fexfow conference. The cmdtok parameter for the Update Leader PIN command: cmdtok=1 Figure 18 shows the fu http request used when sending the Update Leader PIN command to the defaut cmduri. This exampe assumes that the EPV server returned a vaid Conference ID that is a unique identifier for any given schedue. Figure 18: Update Leader PIN Exampe cmdtok=1& confid=<conferenceid>& v=1.0& bn=<bridgename>& p<eaderpin>& ent<entrytones>& exit<exittones> & qs<quickstart> & mh<modhang> & nrp<nrp> Figure 19: Exampe cmduri within chdbased.reg [xmdatasource] version=1.0 bridgeid=edison instaed=true name=xmdatasource address=epv URI=/epvtest pinguri=/epvtest/epvping.htm cmduri=/epvtest/epvcmd.htm port=8080 test=fase 198 Administering Meeting Exchange Servers

199 Configuring biing Configuring mandatory biing codes for fexfow Meeting Exchange can prompt the eader to provide a biing code for their conference when they enter their fexfow conference. To make the biing code mandatory, set the foowing parameter: <forceauxcode>=1 Set this fied to 0 to not require the biing code. If this fied is set to 1, the eader wi be disconnected if he fais to enter the biing code after three attempts. Configuring biing The biingcodes parameter contros whether Meeting Exchange prompts moderators for a biing code upon conference entry. Figure 16 shows a sampe biingcodes vaue. The supported biing codes vaues are D/E/2: <biingcodes>d</biingcodes> Meeting Exchange does not prompt for a biing code. <biingcodes>e</biingcodes> Meeting Exchange prompts for a biing code. <biingcodes>2</biingcodes> Meeting Exchange prompts for two biing codes. Configuring settings reating to stranded participants On systems configured with EPV servers, the stranded participant feature can be enabed on a per conference basis for both fexfow and reguar, or scan, ca fow conferences. When a singe participant remains in a conference for a preconfigured number of minutes, Meeting Exchange September

200 Configuring Externa Passcode Vaidation (EPV) pays an audio prompt to enter any DTMF key to keep the conference active. Tabe 33 shows the stranded participant settings avaiabe through EPV. Tabe 33: EPV Stranded Participant Settings Fied Definition Range Defaut <spctconfthreshod> <spctconfbockinput> <spctconfnumprompts> <spctconfperiodx> <spctconfperiodz> Number of participants in conference to disconnect Whether to bock a DTMF key to keep the conference aive Number of times to repay the termination warning message Number of minutes to wait before paying initia message to stranded participant Interva between warning prompts = disabed 0= fase 1= true System setting System setting Testing the configuration When you have configured Meeting Exchange to operate with EPV, you can use the foowing toos and methods to test your configuration: Testing your code Using the keep aive response Using the xcaci test program Using a Web browser to vaidate PIN codes Testing your code For testing you may want to send a message to a dumb server one which is ony capabe of returning an HTML page as specified in the URI. EPV can operate in this mode when the test attribute in chdbased.reg is set to True. 200 Administering Meeting Exchange Servers

201 Testing the configuration When EPV operates in test mode, the passcode becomes the name of an ascii fie containing a vaid XML response. Using the vaues from the prior exampe, the GET request now ooks ike this: GET /epvdtest/97979.htm HTTP/1.1 Host: webmaster7 Using the keep aive response The foowing sampe Keep Aive response conforms to the epv.dtd. <specte> <spectesys700> <pingresponse> <ping>alive</ping> </pingresponse> </spectesys700> </specte> Using the xcaci test program The xca Cient sampe appication, xcaci resides in /usr/dcb/bin after a successfu instaation. xcaci uses the same ibraries that EPV uses to make requests and receive data from an externa passcode vaidation server. Use xcaci to: verify connectivity to the server verify your sampe/test XML fies Enter the xcaci command at any command ine. 1.Cmd> xcaci The xcaci diaog dispays. September

202 Configuring Externa Passcode Vaidation (EPV) 2. Cmd> <menu option> Menu options are described in Tabe 34: Tabe 34: xcaci Menu Options Menu Option Description v i p t s Vaidate passcode. When you seect 'v', the xcaci prompts you to enter a passcode, ANI, DNIS, and LCN (i.e. port). Enter a vaue and press return for each prompt. Vaidate PIN code If you enter "i", it wi prompt for the PIN code and try to vaidate that PIN with the configured EPV server. Depending on the repy that is returned, it wi report either Vaid or Invaid with the vaue of the ine s company, ine name, and tenum fieds. Ping the server. Use this option to send a ping or keep aive request. Start keep aive timer Stop keep aive timer? Print this message q Quit xcaci. Using a Web browser to vaidate PIN codes You can use a web browser such as Microsoft Internet Exporer or Firefox Mozia to send a get to the EPV server. The foowing is an exampe of a typica PIN code http get: pinquery.xm?pin=5555&ist= &v=1.0&bn=conf_br_ Administering Meeting Exchange Servers

203 Testing the configuration Many of the query eements come from the EPV configuration as shown in Tabe 35 Tabe 35: Web PIN Code query Eement Definition pinuri fied in <xmdatasource> section of /usr/dcb/dbase/ admin/chdbased.reg 8080 Port fied in chdbased.reg pinquery.xm pinuri fied in chdbased.reg 5555 The user entered PIN The conference reservation s <pinistname> fied. Retrieved when the conference is started in the EPV server s passcode repy conf_br_003 Configured in chdbased.reg as the bridgeid Figure 20 is an exampe of a repy for a vaid PIN: Figure 20: Repy for a Vaid PIN <?xm version="1.0?> <specte> <spectesys700> <epvpinresponse> <pinstatus>valid</pinstatus> <code>5555</code> <pininfo> <inename>test_inename</inename> <company>test_co</company> <teenum> <teenum> </pininfo> <epvpinresponse <spectesyst700> </specte> September

204 Configuring Externa Passcode Vaidation (EPV) For an invaid PIN, the response shows <pinstatus>invalid</pinstatus> and the <pininfo>... <pininfo> tag is empty. 204 Administering Meeting Exchange Servers

205 Chapter 19: Configuring aarms Meeting Exchange contains two features which notify you if there are any probems with the operationa performance of the conferencing servers. You can use this information to react to any issues and take actions to address the cause of the probem. These features reated to each other and are caed Simpe Network Management Protoco (SNMP) and core services. Introducing SNMP Introducing core services In addition to these aarm features, Meeting Exchange produces a arge number of reports which provide information about the conferencing servers. For more information, see Viewing Meeting Exchange information on page 107. Introducing SNMP This section describes Simpe Network Management Protoco (SNMP). Avaya uses SNMP to monitor the performance of Meeting Exchange. The SNMP system emits aarms, which are caed traps. The SNMP system is highy configurabe. You can configure the conditions that trigger traps. You can configure the threshods that trigger traps. You can aso configure where the SNMP system sends the traps. Introducing the traps Adding and deeting traps Configuring threshod vaues of trap receivers Verifying that SNMP is running Debugging SNMP Introducing the traps Tabe 36 shows the SNMP traps that Avaya ships with Meeting Exchange. These traps operate for both the Network Management System (NMS) and Initiaization & Administration System (INADS). NMS and INADs represent two ways to impement SNMP in your network. A Managed Information Base (MIB) defines which information is captured by the SNMP system. Meeting Exchange supports a number of MIBs. For more information, see Supported management information bases (MIBs) on page 319. Apri

206 Configuring aarms If you are using INADs, you must perform an extra configuration step. The NMS system does not require this extra configuration step. In an INADs depoyment, you must set the Product ID. The Product ID must be a unique number, of no more than 10 digits, which Meeting Exchange sends in a INADS traps to distinguish which server is generating the traps. Tabe 36: SNMP Traps Trap avmx6200processstartednotification avmx6200processstoppednotification avmx6200reservedportpoousagein crease avmx6200reservedportpoousaged ecrease avmx6200unreservedportpoousagei ncrease Trap Description This trap is generated when a critica Avaya Meeting Exchange process has been started. This trap is generated when an Avaya Meeting Exchange process has been stopped. When you ki a softms process on a Pyramid system, the foowing is the trap sequence: Ki softms A. Trap receiver shows: softms A stopped softms B started softms C started softms B stopped This trap is generated when the number of used ports in the reserved port poo equas or exceeds the upper watermark configured for that poo providing the corresponding ower watermark has been crossed since the ast time this trap was generated. The defaut vaue for a High Threshod is 85%. This trap is generated when the number of used ports in the reserved port poo fas beow the ower watermark configured for that poo providing the corresponding upper watermark has been crossed since the ast time this trap was generated. The defaut vaue for a Low Threshod is 75%. This trap is generated when the number of used ports in the unreserved port poo equas or exceeds the upper watermark configured for that poo providing the corresponding ower watermark has been crossed since the ast time this trap was generated. The defaut vaue for a High Threshod is 85%. 1 of Administering Meeting Exchange Servers

207 Introducing SNMP Tabe 36: SNMP Traps (continued) Trap avmx6200unreservedportpoousage Decrease avmx6200appicationserverfaiover avmx6200mediaserverfaied cscpuutiization csdiskusagethreshod Trap Description This trap is generated when the number of used ports in the unreserved port poo fas beow the ower watermark configured for that poo providing the corresponding upper watermark has been crossed since the ast time this trap was generated. The defaut vaue for a Low Threshod is 75%. This trap is generated when the appication server fais over. This trap is generated when the media server does not respond. Note: Note: This trap is ony generated on singe server configurations. It is not generated in a distributed server environment. If the CPU usage reaches or exceeds an upper threshod (defaut is 90%), an SNMP aarm wi be sent identifying the system impacted. This functionaity is provided by Avaya Core Services components. The system aows configuration of a system-wide disk space usage threshod (defaut is 80%). If the disk usage reaches or exceeds this threshod, an SNMP aarm is sent identifying the system impacted. This functionaity is provided by Avaya Core Services components. 2 of 2 Adding and deeting traps To match the requirements of your customer, you can specify one or more endpoints to receive SNMP traps from your depoyment. You can do this by inserting or deeting entries in the snmptrapreceiver tabe. The foowing script provides an exampe for manuay inserting and deeting an SNMP trap receiver entry. Each entry requires a unique ID. In this exampe, the ID is 1, the trap receiver IP is , and the port is 162. Apri

208 Configuring aarms To insert an SNMP trap receiver entry: 1. Obtain the IP address of the SNMP trap destination. 2. Open a PuTTY session and og in as a craft user. Note: Note: PuTTY is a termina emuator appication which can act as a cient for the SSH protoco. Contact your Avaya Support Representative for a vaid craft password. 3. Connect to coreservices database: su postgres bash-3.00$ psq coreservices Wecome to psq 8.1.4, the PostgreSQL interactive termina. Type: \copyright for distribution terms \h for hep with SQL commands \? for hep with psq commands \g or terminate with semicoon to execute query \q to quit 4. View the SNMP trap receiver tabe: coreservices=# seect * from snmptrapreceiver; id enabed snmpdevicetype ipaddress portnumber snmpnotifytype snmpversion name authprotoco authpassphrase privprotoco privpassphrase (0 rows) 5. Insert or deete the SNMP trap receiver entry: To insert: You must configure the SNMP in the database for NMS and INADS. Configuring the traps is sighty different in both cases: - For NMS, the SNMPdevicetype = 1 - For INADS, the SNMPdevicetype = 2 coreservices=# insert into snmptrapreceiver (id, enabed, snmpdevicetype, ipaddress, portnumber, snmpnotifytype, snmpversion, name, authprotoco,authpassphrase, privprotoco, 208 Administering Meeting Exchange Servers

209 Introducing SNMP privpassphrase) vaues ('1', 'true', 1, ' ', 162, 1, 2, 'avaya', 1, '', 1, ''); INSERT 0 1 To deete: Enter the foowing command: coreservices=# deete from snmptrapreceiver where id = '1'; DELETE 1 6. Verify the insertion or deetion. To verify an insertion: coreservices=# seect * from snmptrapreceiver; id enabed snmpdevicetype ipaddress portnumber snmpnotifytype snmpversion name authprotoco authpassphrase privprotoco privpassphrase t avaya 1 1 (1 row) To verify a deetion: coreservices=# seect * from snmptrapreceiver; id enabed snmpdevicetype ipaddress portnumber snmpnotifytype snmpversion name authprotoco authpassphrase privprotoco privpassphrase (0 rows) 7. Exit Coreservices. coreservices=# \q bash-3.00$ exit exit Apri

210 Configuring aarms Configuring threshod vaues of trap receivers A threshod-based traps have defaut vaues. These defaut vaues are isted in Tabe 36. This section describes how to change the defaut vaues. It contains the foowing sections: Configuring CPU and disk space usage traps Configuring Port usage traps Note: Note: If you make changes to system.cfg, you must restart the server. If you make changes to the database, you do not need to restart the server. Configuring CPU and disk space usage traps This section describes how to change the defaut vaues for the CPU and disk space usage traps. It contains the foowing sections: Configuring CPU utiization trap Configuring disk space usage trap Tip: Tip: CPU utiization and disk space usage traps are impemented using mon. You can earn more about mon here: Configuring CPU utiization trap - To configure CPU utiization trap: 1. Open a PuTTY session and og in as a craft user. 2. Navigate to /etc/mon/mon.cf Interva indicates how often the system checks the CPU eve. In Figure 21, the system checks the CPU utiization every 10 minutes. Monitor cpu.monitor indicates the threshod eve percentage when SNMP traps are generated. In Figure 21, the threshod is set to 90%. Figure 21: CPU Utiization Trap 210 Administering Meeting Exchange Servers

211 Introducing SNMP Configuring disk space usage trap - To configure disk space usage trap: 1. Open a PuTTY session and og in as a craft user. 2. Navigate to /etc/mon/mon.cf Interva indicates how often the system checks the hard disks capacity. In Figure 22, the system is checked every hour. Monitor disk.monitor indicates the threshod eve percentage when SNMP traps are generated. In Figure 22, traps are sent once the various drive partitions reach 80% usage. Figure 22: Disk Space Usage Trap Configuring Port usage traps You can configure the reserved and unreserved port poo usage using the system.cfg fie, as foows: 1. Open a PuTTY session and og in as a craft user. 2. Navigate to /usr/ipcb/config and access system.cfg. 3. Uncomment the appropriate parameter. The parameters are as foows: #ReservedPortPooUsageThreshodLow= #ReservedPortPooUsageThreshodHigh= #UnreservedPortPooUsageThreshodLow= #UnreservedPortPooUsageThreshodHigh= 4. Insert the threshod that you woud ike in your impementation. Apri

212 Configuring aarms Note: Note: When you manuay configure these settings in system.cfg, you must enter actua numbers of ports and not a percentage of a particuar port poo. For exampe: ReservedPortPooUsageThreshodLow=60 ReservedPortPooUsageThreshodHigh=100 Unreserved Port Poo Usage is ony triggered when usage exceeds threshod. Reserved Port Poo Usage is triggered when usage reaches threshod. The defaut settings on the conferencing server are: Threshod Low = 75% Threshod High = 85% Verifying that SNMP is running To verify that SNMP is operating correcty, run the foowing command to ensure that the SNMP trap receiver is receiving the traps: bridge restart You shoud receive mutipe traps. Debugging SNMP This section describes some of the common issues with SNMP. It contains steps and suggestions to overcome these issues. If traps are not generating, you shoud ensure the foowing core services are running: /opt/coreservices/ifecyce/bin/c ist There shoud be 12 services started. /opt/coreservices/dss/bin/dss ist -h ocahost -p There shoud be 2 services started. /opt/coreservices/dss/bin/dss ist -h ocahost -p There shoud be 21 services started. If you do not receive traps for CPU Utiization or Disk Space Usage, you shoud ensure that mon.cf is configured. Aso ensure that the foowing processes are running: mon (service mon status) sysogreader (/opt/coreservices/sysog/bin/sysogreader status) 212 Administering Meeting Exchange Servers

213 Introducing core services If there are no INADS traps being generated, you shoud ensure the foowing ine is in / usr/share/tomcat-5.5.9/shared/casses/aarm.properties. INADSMinorNotifyEnabed=true Introducing core services Core services is a process which monitors the performance of Meeting Exchange and produces a number of ogs. You can view these ogs in an Internet browser. Running and verifying core services Configuring core services Viewing the ogs Running and verifying core services The core services process shoud aways run in the background whie Meeting Exchange is in operation. You can use the foowing commands to start, stop, and verify core services. Start /sbin/service wdinit start It can take up to 15 minutes to correcty start Meeting Exchange when core services are running. Stop /sbin/service wdinit stop When you stop wdinit, the tomcat service may sti be running. You shoud stop the tomcat service to ensure the core services wi start up correcty the next time. Restart /sbin/service wdinit restart Verify that a processes are running as part of core services: /opt/coreservices/ifecyce/bin/c ist Meeting Exchange outputs a ist of the services that it has started. These services incude, PEAarmRetrieverServer_key, PENworkLogServer_key, PENetworkLogRetrieverServer_key, PEAarmServer_key, PESDAS_key, MessageBrokerService, AdminTomcat, and so on. There are ten services in tota. If the services do not start, Meeting Exchange generates an exception error. Apri

214 Configuring aarms Configuring core services The core services process produces a number of ogs. To configure these ogs, you must edit an XML fie on Meeting Exchange. The XML fie is in the foowing directory: /usr/ipcb/config/ipcbog4j.xm To enabe ogging to the HOST_LOG_SERVER, edit the foowing ines at the end of the fie: <root> <priority vaue= a /> <appender-ref ref= system /> <appender-ref ref= HOST_LOG_SERVER /> </root> To disabe ogging to the HOST_LOG_SERVER, edit the ines as foows: <root> <priority vaue= a /> <appender-ref ref= system /> <!--appender-ref ref= HOST_LOG_SERVER /--> </root> Viewing the ogs You can use an Internet browser to view the ogs which the core services process produces. 1. Open an Internet browser. 2. Navigate to: Exchange appication server IP address>:8080/cs-oam 3. Disabe any pop-up bocker software. 4. On the Log in screen, enter a ogin ID and a password. Note: Note: Contact your Avaya Support Representative for password information. 5. Navigate to System Maintenance > Log Viewer or Aarm Manager. 6. Seect the required settings. 214 Administering Meeting Exchange Servers

215 Introducing core services 7. Cick OK. Apri

216 Configuring aarms 216 Administering Meeting Exchange Servers

217 Chapter 20: Introducing mutisite This chapter incudes these topics: Introducing mutisite Architecture Mutisite terminoogy Introducing mutisite Mutisite refers to a network of Cient Registration Servers (CRS) ocated in different geographica ocations. It inks conferences distributed over audio conferencing servers (bridges) ocated anywhere in the word. A caer dias into a oca bridge and enters their goba password. The caer wi be connected to other bridges within the mutisite network if other goba participants are present. In this way, mutisite dramaticay increases the capacity of a singe conference where, in conjunction with arge conference support, a singe conference distributed across three gobay inked bridges can be as arge as 12,000 ports. The potentia voume of traffic increases, whie caers reduce their costs, as many ines can dia ocay into one bridge whie ony one ong distance ink is needed to gobay connect the conference. Mutisite optimizes system resources to ensure that conferencing is more economica. It aows the administrator to schedue one goba conference to span mutipe sites. This reduces administrative costs whie at the same time it increases port capacity by connecting mutipe conferencing servers within a singe network. Apri

218 Introducing mutisite How mutisite can be used to create goba conferences The foowing ist describes a typica sequence: An operator seects the Goba option from the CRS Front End scheduing appication or the Muti-Site Conference option via the Web Porta. The CRS assigns a Goba Conference ID to the reservation. The reservation, incuding the number of requested ines and goba conference features, is schedued on a bridges in the mutisite network. Participants join a goba conference by diaing the Diaed Number Identification Service (DNIS) or Direct Dia Inward (DDI) number and entering a PIN to any of the participating bridges. As participants join, a centra, virtua hub is created, which inks a bridges. See About hubs and inking servers on page 218. As more caers dia in, mutisite adds inks to additiona conferences automaticay. Each ocation incudes an ide backup bridge avaiabe for faiover, if needed. Mutisite connects a the participants in a singe conference ca. About hubs and inking servers Each conferencing server has the same ink priority. The first server diaed becomes the hub for the conference. Each additiona server diaed becomes a spoke for the conference. Servers designated as spokes dia out a virtua ink ine to connect to the hub. If a designated hub disconnects from an active conference and the conference does not end (moderator hangs up), then the remaining bridges can reestabish the conference inks. For an overview, see Figure 23. For more information on goba conference features, see About goba conferences on page Administering Meeting Exchange Servers

219 Introducing mutisite Figure 23: Three-node site with backup servers Site 1 1 MutiSite engine Site Site Figure notes: 1. Mutisite engine 2. CRS database 3. CRS 4. Appication server Apri

220 Introducing mutisite Maximum number of sites and conferences Tabe 37 shows the capacity and performance requirements that mutisite supports. Tabe 37: Capacity Number of Supported sites depoyed simutaneousy within a goba conference. The sites do not incude redundant sites configured for faiover purposes ony. Maximum number 3 Conferences that can be booked as goba conferences. 100,000 Simutaneous goba conferences 300 Concurrent conferences on a singe appication server. Note: Note: Reserve one common conference room for participants who are paced on hod (Hod is room 999) Ports per site 4000 Singe dia-in number to access goba conferences Caers ony have to dia one appication server number, which can be oca for their area. The dia-in numbers can then be configured on the system specificay for goba conferences. Mutisite required components Tabe 2 ists the required mutisite components. Tabe 38: Mutisite required components Component CRS 5.2 instaed on a Windows 2003 server Description Each CRS incudes severa parameters, such as: Link priority that determines each bridge s probabiity of becoming a hub. Link teephone number, which is the number other bridges must dia if that bridge becomes the hub. 1 of Administering Meeting Exchange Servers

221 Introducing mutisite Tabe 38: Mutisite required components (continued) Component Mutisite for Meeting Exchange 5.2 Web Porta 5.2 Meeting Exchange 5.2 Description Mutisite communicates with the CRS using a variety of different messages, such as Make Me Hub. As new bridges join the goba conference network, their ink priority rating determines whether or not they become the hub. If they are successfu, other bridges must dia their ink teephone number. If they are not successfu, they must dia the ink teephone number of the successfu bridge. Using Web Porta, users can schedue conferences, seect various conference options, and manage active conferences from their workstations. Meeting Exchange S6200/S6500/S6800 conference servers designed for use with a wide variety of conferencing appications. Note: Note: Mutisite is not backwards compatibe with previous conference server reeases. 2 of 2 Mutisite optiona components The CRS stores CDRs and booking information based on the Goba Conference ID. Companies can coect goba conference information using one or more optiona components isted in Tabe 39. Tabe 39: Mutisite optiona components Component Biing Notifications Subsystem Description The Avaya Biing (SBi) utiity generates a fie for a variety of fixed or customized output formats for use in externa, third-party invoicing appications. For more information on biing, see Biing architecture on page 226 and aso see Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. The Notifications Subsystem program sends Fax and E-mai conference notifications to conference participants. The Notifications Subsystem contains tempates that can be used for goba conference notifications. These tempates contain important internationa information, such as diaing codes and teephone numbers. 1 of 2 Apri

222 Introducing mutisite Tabe 39: Mutisite optiona components (continued) Component Reports CDR Loader Goba CSPI Description The CRS Reports appication generates reports through Microsoft Exce. Reports can incude data on individua conferences, cient usage, and system port utiization. The CDR Loader retrieves CDR and CODR fies from the bridge and updates the CDR database used by the Biing and Reports utiities. The CRS Stored Procedure Interface (CSPI) supports conference range attributes for read and write interfaces. 2 of 2 Note: Note: You must run the SBi utiity on a the CRS servers in the network to obtain compete goba conference information. For more information on biing or reports, see Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. Architecture Mutisite comprises four architectures: Network architecture Link ine architecture Faiover configuration and faut identification Biing architecture Network architecture Mutisite uses a hub network architecture. The mutisite hub network maximizes system resources by enabing customer configuration of the preferred hub through the ink priority mechanism. Link priority, which determines the probabiity of a bridge becoming a hub, is set as foows: Zero (0) is the highest priority Five (5) is the owest 222 Administering Meeting Exchange Servers

223 Architecture Note: Note: NAT shoud be disabed. If a inks have the same priority, the hub is the site where the conference first opens. Apri

224 Introducing mutisite System faiover In a mutisite network, a standby system monitors the active system and determines if the active system fais. If this occurs, the standby system promotes itsef to be the active system and takes over a processing. The newy promoted system aso re-routes trunks to the former active system, which is demoted to standby status. See Figure 24. Figure 24: Mutisite architecture Booking a goba conference 4 5 Figure notes: 1. Goba bridge site 1 2. Goba bridge site 2 and Hub 3. Goba bridge site 3 4. Conference scheduing 5. Goba conference Note: Note: The CRS system and the standby CRS system exist on the same IP subnet. 224 Administering Meeting Exchange Servers

225 Architecture Link ine architecture A virtua ink ine (VLL) is a network communications channe with a point-to-point connection. AUTOVLLs connect servers to the hub. The system creates AUTOVLLs between servers as caers dia into their oca conferences and disconnects the inks when caers eave their conferences. VLLs use IP ines for inking conferences, based on the hub and spoke mode. See Figure 25. Figure 25: Goba conference network Figure notes: 1. AUTOVLL (Virtua Link Line) 2. Centra hub is the bridge with the highest ink priority Mutisite uses specific DNIS digits to abe incoming ines as VLLs automaticay. When the receiving bridge answers the ine, the caing bridge dias the moderator passcode for the conference to identify the target conference for the ink. The bridge automaticay assigns moderator status to a VLL. Apri

226 Introducing mutisite Each bridge creates a VLL by diaing out to a neighboring bridge using a defined DNIS or DDI number and the system abes the ine, AUTOVLL. An exampe of a ca branding AutoVLL is: N AUTOVL AutoVLL Note: Note: The ine name must be named AutoVLL. AUTOVLLs ony ink two active conferences and do not transmit DTMF commands entered by moderators or participants from a teephone keypad. Faiover configuration and faut identification If the active or backup CRS or appication server fais, the system sends a notification to the system administrator. This notification may be in form of SNMP trap, E-mai, SMS, pager aert, or Bridge Tak system message. Biing architecture Mutisite ensures that goba conferences are bied accuratey by centraizing biing data in the CRS that originates the booking. At a schedued time, recommended to be at an off-peak time, the originating bridge runs a Goba CDRs script. This script coects data from each participant bridge and compies data on individua caers and their duration in the goba conference. The conference originator is then bied for the cost of the goba conference using the SBi utiity. 226 Administering Meeting Exchange Servers

227 Architecture Tabe 40: Overview of biing architecture Figure notes: 1. Goba bridge site 1, the conference organizer 2. Goba bridge site 2 3. Goba bridge site 3 4. Goba CDRs script 5. Participant data 6. Bi generated Apri

228 Introducing mutisite Mutisite terminoogy Tabe 41 provides a ist of terms used with regard to mutisite and Meeting Exchange. Tabe 41: Gossary Tabe Term Active CRS AUTOVLL Bandwidth Ca branding Ca routing CDR CODR conference server CRS DSA DDI DHCP DNIS Definition Processes a requests sent to the CRS. The active CRS repicates data changes to the standby CRS system, which can take over in case of system faiure. A ca-branding function performed by the bridge on a ca when the incoming digits match an entry in the Ca Branding tabe. The bridge abes the ine, AUTOVLL. A measure of the amount of data that a network can hod at one time. A way of assigning specific greeting messages, company names, ine names, and system functions (Direct, Enter, AutoVL, or Scan) to caer ines. A way of processing a ca. Ca Detai Record. Conference Detai Report. An audio conferencing system (bridge). Cient Registration Server. The CRS Front End is a reservation appication that books conferences on a CRS server. Each bridge has its own CRS, which shares booking information with other CRS servers in the network. Directory System Agent. A generic term for database-hoding directory information. Direct Dia Inward. Depending upon the configuration, a bridge pays a wecome message to caers diaing in, prompts caers to enter a participant code, and enters the participant into the appropriate conference. Dynamic Host Configuration Protoco. A TCP/IP protoco that enabes a network connected to the Internet to assign a temporary IP address to a host automaticay when the host connects to the network. Diaed Number Identification Service. Depending upon the configuration, a bridge pays a wecome message to caers diaing in, prompts caers to enter a participant code, and enters the participant into the appropriate conference. 1 of Administering Meeting Exchange Servers

229 Mutisite terminoogy Tabe 41: Gossary Tabe (continued) Term DNS DTMF E1 Goba booking Fai over Goba conference Goba Conference Master Hot standby Hub Hub and Spoke IP IVR LAN Link ine Location Definition Domain Name System. The system in which hosts on the Internet have both a domain name address, such as msite1.mycompany.org and an IP address, such as Domain name addresses are transated automaticay into numerica IP addresses, which are used by the packet-routing software. Dua Tone Muti-frequency diaing used by the Touch-Tone phone system. Euro ISDN. An E-carrier that can hande 30 voice channes. A conference reservation that the CRS sends to a servers on the MutiSite network. A backup operationa mode in which primary system components such as a CRS or appication server, can be taken over by secondary system components. A singe conference ca made up of reserved conferences that run on mutipe, remote bridges inked by audio channes. A master bridge maintains information on a bridge activity and broadcasts the information to a other active nodes. A bridge can act as master or backup master, as required. A disk drive reserved for use if an active drive fais. A pace of convergence where data arrives from one or more directions and is forwarded to one or more other ocations. A inking architecture where one or more nodes act as interconnection points for other nodes. Internet Protoco. Interactive Voice Response. A teephony technoogy that uses touch-tone teephones to interact with a database, such as entering or retrieving information. Loca Area Network. A ine used to ink one bridge to another in estabishing arge conferences. A ocation defined as a combination of two sites, one site is active and the other acts as redundant backup (Hot standby). 2 of 4 Apri

230 Introducing mutisite Tabe 41: Gossary Tabe (continued) Term NAT Node Overbooking PIN PSTN Ring network Roster SCC SIP Site Standby CRS T1 TCP/IP Definition Network Address Transation (NAT) mode. An IETF standard that enabes Loca Area Networks (LANs) to configure one set of IP addresses for interna use and another set of addresses for externa use. A junction or device of some type. In oca area networks, a device that is connected to the network and is capabe of communicating with other network devices. The process of reserving more than the maximum number of ines avaiabe for a given time period. Lines configured for operators, music, record/pay, or ink ines are not incuded in the system s count of avaiabe ines. Persona Identification Number. Pubic Switched Teephone Network. A oca area network in which devices (nodes) are connected in a cosed oop, or ring. Messages in a ring network pass around the ring from node to node in one direction. When a node receives a message, it examines the destination address attached to the message. If the address is the same as the node's, the node accepts the message; otherwise, it regenerates the signa and passes the message aong to the next node in the ring. A ro ca of participant names or preset dia ist. Signaing Contro Card. A hardware component within the S6x00 Convedia server. Session Initiated Protoco, or Session Initiation Protoco. An appication-ayer contro protoco; a signaing protoco for Internet Teephony. A depoyment unit for goba conferences that comprises bridge hardware and a co-ocated appication server ike a bridge contro software and CRS. Receives a data changes from the active CRS system and monitors the active system to determine if it is functiona. If the active system is no onger functiona, the standby CRS promotes itsef to be the new active system and takes over a processing. A T-carrier that can hande 24 voice channes. Transmission Contro Protoco/Internet Protoco. 3 of Administering Meeting Exchange Servers

231 Mutisite terminoogy Tabe 41: Gossary Tabe (continued) Term TDM Ten Base T (10BaseT) UDP Virtua Link Line (VLL) WAN Definition Time Division Mutipexing. A digita transmission capabiity that aows users to access a singe radio-frequency channe without interference. TDM aocates separate time sots to each user within a channe. The Ethernet standard for baseband oca area networks using twisted-pair cabe carrying 10 megabits per second (Mbps) in a star topoogy. User Datagram Protoco. A standard user channe used to provide audio between conferences on two or more Avaya bridges. VLLs can be diaed in or out, but do not respond to DTMF digits during conferences. See AUTOVLL. A Wide Area Network. 4 of 4 Apri

232 Introducing mutisite 232 Administering Meeting Exchange Servers

233 Chapter 21: Upgrading from Meeting Exchange 5.2 Service Pack 1 to Meeting Exchange 5.2 Service Pack 2 Note: Note: Before you upgrade from Meeting Exchange 5.2 Service Pack 1 to Meeting Exchange 5.2 Service Pack 2, you must insta the atest patch on your 5.2 Service Pack 1 system. To upgrade to version 5.2 Service Pack 2, you must insta the RPM fie. You must foow this RPM fie with the atest recommended patch, which is aso an RPM fie. An RPM fie is a Red Hat Package Manager fie. A patches are cumuative and so you ony need to insta the atest reeased patch. When instaing the RPM, changed fies are backed up to /usr3/backups/ before tar.gz. If customizations have been made to any of these fies, they wi not exist after the upgrade. Possibe fies that may have been customized are: Exampe 1: grimreaper.sh - used to manage the ceanup of od og fies Exampe 2: backup.sh - used to backup configuration In the Meeting Exchange 5.2 Service Pack 2 reease, there are new defaut Wecome messages that contain Avaya branding. By defaut, the RPM does not insta these new messages. If you wish to use these these new messages, contact your Avaya Support Representative. Instaing the RPM fie To insta the RPM fie: 1. Copy the RPM fie to the Meeting Exchange bridge. Suggested ocation: /home/craft 2. Using the PuTTY appication, og on to the bridge as an sroot user. You can downoad PuTTY from downoad.htm. a. Enter the name craft and the password craft01. Apri

234 Upgrading from Meeting Exchange 5.2 Service Pack 1 to Meeting Exchange 5.2 Service Pack 2 b. Use the sroot command to change from craft to sroot access. The sroot command is: su sroot The defaut password is sroot Stop the bridge: #bridge stop 4. Insta the RPM: #rpm --force --nodeps -ihv mx-bridge-sp i386.rpm Force is necessary because some of the upgrade fies naturay confict with the existing bridge fies. Nodeps is necessary because there are some unnecessary dependencies. 5. Verify the RPM instaation: #rpm -qa grep bridge-sp The bridge shoud dispay the foowing: mx-bridge-sp Verify the version: #version The bridge shoud dispay the foowing: Start the bridge: #bridge start 8. Now you must oad the recommended patch. The instructions for oading the patch are described in the corresponding patch instructions. Roing back to a previous version If you wish to revert to the state of the system prior to the upgrade, you must undo the upgrade steps in reverse order: You must uninsta the recommended patch. You must then uninsta the RPM ( ). When you insta the RPM fie, it backs up any changed fies to the foowing directory: /usr3/backups/before tar.gz. When you uninsta the upgrade, or roback, the script restores any fies that it finds in /usr3/backups/ 234 Administering Meeting Exchange Servers

235 Ensuring the vaues of softmediaserver.cfg before tar.gz. It is important to note that if you have made any changes to these fies between the upgrade and the roback, you wi oose these changes. To roback: 1. Using the PuTTY appication, og on to the bridge as an sroot user. You can downoad PuTTY from downoad.htm. a. Enter the name craft and the password craft01. b. Use the sroot command to change from craft to sroot access. The sroot command is: su sroot The defaut password is sroot Stop the bridge: #bridge stop 3. Uninsta the recommended patch. The instructions for uninstaing the patch are described in the corresponding patch instructions. 4. Uninsta the RPM fie: #sudo rpm -e mx-bridge-sp Start the bridge: #bridge start Ensuring the vaues of softmediaserver.cfg Note: Note: This section appies to upgrades from Meeting Exchange 5.1. The buffer cache parameter settings settings have increased in vaue since the Meeting Exchange 5.1 reease. You must ensure that the vaues of these settings on your system are never ess than the defaut vaues. For more information on the defaut vaues, see Buffer cache parameter settings on page 362. When you upgrade from Meeting Exchange 5.1 to Meeting Exchange 5.2.x, you need to update these vaues in the softmediaserver.cfg fie on each media server in your depoyment. A bridge restart is required on the server so that the softms processes pick up the settings. Apri

236 Upgrading from Meeting Exchange 5.2 Service Pack 1 to Meeting Exchange 5.2 Service Pack Administering Meeting Exchange Servers

237 Chapter 22: Configuring mutisite This chapter describes the foowing: Mutisite environment requirements Instaing mutisite for Meeting Exchange Setting up a CRS for mutisite use Configuring MutiSite.ini for mutisite use Mutisite environment requirements Tabe 42 ists the recommended environment requirements. Tabe 42: Mutisite environment requirements Requirement Maximum atency between sites Avaiabe bandwidth Recommended 60ms each way 512 kbps If the network characteristics are inferior to the recommended requirements described in Tabe 42, the end user experience wi be impacted in the foowing areas: Time taken to pace inks between conferences Time taken for DTMF commands to propagate between systems Time taken to schedue a goba conference (ony noticeabe for repeat bookings) Apri

238 Configuring mutisite Opening ports between sites Tabe 43 ist the ports that need to be opened for use by Meeting Exchange. Tabe 43: Ports Port Description 1100 NSI DoubeTake port 1105 Service port Tabe 44 ist the ports that need to be opened to aow the CRS servers to communicate with each other. Tabe 44: CRS ports Port Type Source Destination Description 20 and 21 TCP CRS S6200 bridge CDR Loader. Fetches CDRs and CODRs by way of FTP. 53 TCP A devices DNS DNS name server requests. (Optiona) 123 UDP Web Porta S6200 bridge Time synchronization. Request and return (bidirectiona). 123 UDP CRS S6200 bridge Time synchronization. Request and return (bidirectiona) TCP Web Porta CRS ODBC for web reports - TomCat TCP CRS S6200 bridge Informix for Sef Registration pin codes to bridge TCP S6200 bridge CRS Modapi contro. 1 of Administering Meeting Exchange Servers

239 Instaing mutisite for Meeting Exchange Tabe 44: CRS ports (continued) Port Type Source Destination Description 5050 TCP Web Porta CRS Web Porta scheduing to Reserver TCP Web Porta CRS Additiona TCP session to the Reserver for the Audio Consoe TCP S6200 bridge 6601 UDP S6200 bridge Web Porta Web Porta API for Web-based appications to contro bridge (Audio Consoe CMAPI). API for Web-based appications to contro bridge (Audio Consoe CMAPI) TCP Web Porta S6200 bridge Moderator command/ contro for Bridge Tak TCP CRS S6200 bridge SSL-encrypted moderator command/ contro for Bridge. 2 of 2 Instaing mutisite for Meeting Exchange To insta mutisite: 1. Copy entire MSE foder to desired ocation. 2. Start MSE. 3. Consut insta.txt if you want to modify MSE operation. Apri

240 Configuring mutisite Setting up a CRS for mutisite use Each CRS server connects to a oca bridge but maintains TCP/IP connectivity to a other CRS servers in the mutisite network. Figure 26: CRS connectivity within the mutisite network Mutisite Figure notes: 1. CRS 2. S6200/S TCP/IP To configure a CRS for mutisite use, use the System Administrator tab in the CRS Front End appication to: Identify a other CRS servers in the network. Verify that the ist of time zones is identica on a CRS servers in the network. Note: Note: Synchronize a CRSs and bridges to one source, otherwise the GCD process wi not accuratey determine which bridge to make the hub. Configure the Notifications Subsystem s goba tempate to incude conference access numbers for a the bridges in the network. 240 Administering Meeting Exchange Servers

241 Setting up a CRS for mutisite use There shoud be severa teephone access numbers but ony one number per bridge. Participants can use the teephone number of the nearest bridge. For exampe, caers in Canada woud dia a Toronto access number. Caers in Boston woud ca a New York number. Note: Note: Avaya recommends that you create a unique ogin for each CRS and bridge to ensure that each node connects ony to its own resources. For more information on configuring ogin information, see Configuring MutiSite.ini for mutisite use on page 248. For information on configuring a CRS, see the Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. For an introduction to creating goba conferences, see About goba conferences on page 253. SQL 2000 and SQL 2005 SP2 Due to encryption enhancements in SQL 2005 Service Pack 2, Avaya has updated the process of CRS faiover in Meeting Exchange 5.2. Contact Avaya Support Engineers for more information about these configuration steps. Linking CRS servers In order to configure CRS servers for mutisite use, it is necessary to ink the servers. This is done through the SQL Enterprise Manager. Note: Note: An expert knowedge of the workings of the SQL Enterprise Manager is necessary to compete this task. Registering the server To register the server: 1. Cick Start > Programs > SQL Enterprise Manager. The SQL diaog dispays. 2. Right-cick SQL Server Group. 3. From the submenu ist, seect New SQL Server Registration option. Tip: Tip: If the Wizard diaog dispays, seect Disabe Wizard to cance. 4. In the Registered SQL Server Properties diaog, cick the Server ist box. Apri

242 Configuring mutisite Figure 27: Registered SQL Servers Properties Diaog 5. In the Seect Server diaog, seect a server name from the Active servers ist and cick OK. Figure 28: Seect Server Diaog 6. Seect the Use SQL Server authentication option as shown in step Enter a ogin name. The ogin name is. 8. Enter a password. The password is. 9. Cick OK to register the server. 242 Administering Meeting Exchange Servers

243 Setting up a CRS for mutisite use Setting up the stored procedure To configure the stored procedure: 1. From the New Server option ists seect database. 2. From the Database ist, seect BSRes2. 3. Cick Stored Procedure. 4. Doube-cick to open the p_getsystemparameter from the Stored Procedures ist. The Stored Procedures window dispays. 5. Under Seect Statement, enter the site ink number for the oca server in section. For more information, see Link ine architecture on page Enter the site ink priority in section: where 0 has the highest priority and 5 the east priority 7. Enter the time zone of this side in This shoud match the TimeZoneType tabe under the System Administrator tab in the CRS Front End appication. 8. Cose the Stored Procedures window. Configuring SQL stored procedures You must create the BSRes2 database first by using the foowing two stored procedures: DoProcessGCDChanges RunMutiSiteCDRs Note: Note: These stored procedures (aso caed jobs) are isted in the stored procedures foder in the BSRes2 database. DoProcessGCDChanges You can configure the DoProcessGCDChanges SQL job on any one of the nodes within the mutisite network. It shoud ony be configured on one node. To configure DoProcessGCDChanges: 1. From the SQL Enterprise Manager box, expand the Loca Server foder. 2. Expand the Management foder. 3. Expand the SQL Server Agent foder. 4. Right-cick on Jobs and seect New Jobs from the submenu. 5. In the New Jobs Properties box under the Genera tab: Apri

244 Configuring mutisite a. Enter DoProcessGCDChanges in the Name fied. Figure 29: New Jobs Properties Diaog b. In the Owner fied, seect a name, for exampe,. c. Enter DoProcessGCDChanges in the Description fied. 6. In the Steps tab: a. Cick the New button. b. In the Genera tab, enter Step1 in the Step name fied. Figure 30: New Job Step c. Choose BSRes2 in the Database fied. d. Under Command, enter DoProcessGCDChanges for the command name. e. In the Advanced tab under On success action, choose the Quit the job reporting success for the success action option. f. Cick OK. 244 Administering Meeting Exchange Servers

245 Setting up a CRS for mutisite use 7. In the Schedues tab: a. Cick the New Scheduer button. b. In the New Jobs Scheduer diaog, enter Schedue1 in the Name fied. c. Choose Recurring. d. Cick the Change button. e. In the Edit Recurring Schedue diaog, seect Daiy. Figure 31: Edit Recurring Schedue Diaog f. Under Daiy Frequency, seect Occurs every 1 minute, and cick OK. 8. In the New Jobs Properties diaog, cick Appy and then OK. The configuration is compete. Note: Note: The Notification tab does not require configuration. RunMutiSiteCDRs Use SQL Script to insta the RunMutiSiteCDRs SQL job on a nodes in the mutisite network. To insta the RunMutiSiteCDRs SQL job: 1. Choose Start > Programs > Microsoft SQL Server > Query Anayzer. 2. In the Connect to SQL Server diaog, seect the server to which you want to connect, for exampe, Loca. 3. Choose the Windows authentication option and cick OK. 4. In the Query Anayzer diaog, choose Fie > Open, and navigate to the /ReadCDR700 foder on the root directory. Apri

246 Configuring mutisite Note: 5. Seect MutiSiteCDRs.sq and cick Open. 6. From the Database ist on the too bar, choose CDRs. 7. Execute the query by pressing f5 (or cick the arrow button on the toobar). 8. Wait for the script compete message. 9. Verify that you successfuy instaed the RunMutiSiteCDRs job by opening the SQL Enterprise Manager and navigating to the Loca/Management/SQL Server Agent/Jobs foder. 10. Doube-cick to open RunMutiSiteCDRs. 11. Seect the Schedues tab and cick the Edit button. 12. In the Edit Job Schedue diaog, cick the Change button. 13. Under the Daiy Frequency in the Edit Recurring Job Schedues diaog, reset the defaut time (12:00 AM) to a time recommended by your system administrator, and cick OK. Note: Each server requires a designated time to process goba conference information from the other nodes in the mutisite system. To avoid conficts, the system administrator may choose to stagger the start times for running RunMutiSiteCDRs on each server one haf hour apart during off-peak hours. 14. In the Edit Job Schedue diaog, cick OK. 15. In the RunMutiSiteCDRs Properties diaog, cick Appy and OK. The configuration is compete. Configuring the MSDTC og fie The foowing sections describe how to modify the defaut MSDTC setting to the recommended setting for Windows 2003 operating systems. To modify the MSDTC og fie on a Windows 2003 system: 1. Choose Start > Settings > Contro Pane. 2. In the Contro Pane window, doube-cick on Administrative Toos. 3. In the Administrative Toos window, doube-cick on Component Services. 4. Expand the Microsoft Transaction Server and the Computer foders. 5. Right-cick on My Computer and seect Stop MSDTC. 6. Right-cick on My Computer and seect Properties. 7. Cick on the MSDTC tab. 246 Administering Meeting Exchange Servers

247 Setting up a CRS for mutisite use Figure 32: My Computer Properties Diaog 8. In the MSDTC diaog, enter 32 in the Capacity fied, and cick the Reset Log button. 9. Cick Yes in the DTC Consoe Message diaog. 10. Under Status in the MSDTC diaog, cick Start, and cick OK. Creating a new server in the CRS Front End To create a new server in the CRS Front End: 1. Open the CRS Front End by doube-cicking the CRS Front End icon on your desktop. 2. Cick System Administration. The System Administration fieds appear. 3. Seect Server and cick New. 4. Enter the server name and cick Save. For information on creating new servers in CRS Front End, see the Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. Apri

248 Configuring mutisite Viewing servers To view the servers: 1. Open the CRS Front End by doube-cicking the CRS Front End icon on your desktop. 2. Cick Customer Bookings. 3. Seect the *Muti-Site* company from the company ist on the eft-hand side. The new server dispays in the company detais section. 4. To view bridge information, cick on the Bridge tab. If configured for an Active/Standby environment, mutisite receives bridge information stored on the CRS. The CRS dispays bridge information on the Bridge tab, which incudes the bridge name, IP addresses, and status (Active or Standby). Mutisite parses this information and tries to connect to the active bridge and bypassing the entries isted in the defaut MutiSite.ini fie (bridgenames). If an appication server fai over occurs, mutisite shuts down. BSMon then restarts mutisite, which sends a request to the CRS for an updated active/standby bridge ist and connects to the newy active bridge. Configuring MutiSite.ini for mutisite use Before running mutisite, you must first configure the mutisite.ini fie. The mutisite appication (MSE.exe) can be tod the ocation of the mutisite.ini fie. For exampe: MSE.exe c:\avaya\mutisite\mutisite.ini The defaut ocation for the MutiSite.ini fie is %windir%\mutisite.ini. To set up the mutisite.ini fie: 1. Using Windows Exporer, ocate the <instaation path> mutisite foder. 2. Open the MutiSite.ini fie using any text editor, such as Notepad. 248 Administering Meeting Exchange Servers

249 Configuring MutiSite.ini for mutisite use 3. Add the foowing vaues isted in Tabe 45, where indicated. Tabe 45: ini fie description Parameter with defaut Range Description Mutisite Genera MSE settings SaveSettings= Whether settings shoud be written back to MutiSite.ini on success LogLeve= Log Leve (0=Error; 1=Information, 2=Verbose, 3,4,5=Debug) LogSize= Log Size in Kb LogArchives= Number of og fies kept LogBuffered= Whether buffering is on (buffered ogs have itte effect on performance) BridgePoingInterva= Number of seconds between pinging CRS and bridge (heartbeat) RefreshSecs= Number of seconds between refreshing bridge and crs conference ists CRSBridgeList= Whether we shoud get our bridge IP from the CRS bridge tabe CRSHost= <ipaddress> The IP address of the CRS ResSrvr Port=5050 <port> The port of the CRS ResSrvr CRSEncryption= Whether CRS ipaddress:port is encrypted TeCRSAboutLocas= Whether to inform the CRS ResSrvr about opening/cosing of oca conferences NumVLLRetries= Number of VLL retry attempts LinkTime= The maximum number of seconds to wait for a VLL to ink AutoBridgeReconnect= Whether MSE shoud cose down or retry to connect to bridge on bridge connection faiure ReconnectTime= The maximum number of minutes to wait for a bridge connection PortGroupsOB=MutiSite <portgroupob> If desired, a portgroup name from /usr/dcb/ dbase/admin/portgroupsob.txt (wi imit VLLs to this range.) 1 of 2 Apri

250 Configuring mutisite Tabe 45: ini fie description (continued) Parameter with defaut Range Description EventPort=13912 <our-port> Incoming port that bridge wi send events to our machine on. Verify firewa has this open. EventIPAddress=oca-ip <our-ip> This is the address sent to the bridge. It wi try to send events to our-ip:our_port BridgeNames MyBridge= ,2000 4,1212,5 MyBridge <bridge_info> 4. Save and cose the mutisite.ini fie. A section for a bridges known. One ine per bridge. If CRSBridgeList is set, this ip-address wi be repaced by the one got from the CRS This entire section appies to this bridge name. OperatorName=msite <op_name> The operator name that MSE wi use to ogon to the bridge OperatorPassword=x <op_pass> The operator password that MSE wi use to ogon to the bridge IsEncrypted= Whether the bridge modapi communication is encrypted Layout For Query window detais (support view) Tite= <tite> Caption written to MSE appication tite bar MainTopLeftPos=183,108 <x,y> Top, eft co-ordinates for main window (Aows pacement) QueryTopLeftPos=0,0 <x,y> Top, eft co-ordinates for query window (Aows pacement) QueryRef=0 <ConfRef> Query window, initia ConferenceRef dispaye 2 of 2 Configuring mutisite for BSMon You can configure mutisite to start by BSMon. For information, see the Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. 250 Administering Meeting Exchange Servers

251 Configuring MutiSite.ini for mutisite use Stopping mutisite To stop mutisite, just cick the Cose button. Setting up the audio conference server The system administrator shoud configure each bridge/server in the network to ensure that mutisite operates seamessy. Add specific mutisite sign-in accounts on the bridge using the Administrator Menu > Configurations > Sign In menu of the system administration software. These sign-in accounts shoud match the sign-in accounts defined in the MutiSite.ini fie. See Tabe 45. To set up ca branding, use the command ine cbuti utiity ocated in the /usr/dcb/ bin directory to specify phone numbers to route cas. If Communications Manager is not part of the impementation, set up outgoing ca branding using the /usr/ipcb/config/tenumtouri.tab fie. If you want to incude options ike Attended Originator Dia Out (ODO), or Lecture, enabe the options uniformy on a bridges in the mutisite network. The CDR End Date (cdr_end) feature enabes a system to generate CDRs or a CODR for a conference on the end date rather than the start date when a conference extends past midnight. Utiizing goba conference resources When a goba conference is booked, you do not need to aow for additiona resources for each conference. At the utmost, the number of ink ines in a conference is a function of the number of caers who have diaed into other bridges. However, you do need to monitor the avaiabiity of bridge resources for inking. For exampe, when a participants are diaed into the same bridge no resources are used for inking. A ink ine uses a resource. However, a ink ine does not occur uness it is initiated by a participant diaing into a bridge other than the oca one. A possibe aternative approach for managing inking resources is to use the standard resource poo for inking and activate overbooking. Overbooking settings Set up the overbooking eve for each site as a function of the number of ports on the site reative to the number of ports (at the site with the most ports) and site-cost weighting. Apri

252 Configuring mutisite For exampe, overbooking needs to be enabed to aow for the fact that a ten-participant conference booked over four bridges wi ony use, at most, ten ports for caers and two for inks (each ink requires a port at each end). Therefore, the conference may use ony 14 ports out of 40 booked. Tip: Note: Tip: Determine which site may require the most inks. If bridges are significanty different in size, the overbooking parameter may need to be increased on the smaer site to accommodate goba conferences. Note: The key to resource management is essentiay the same as for an on-demand environment, for exampe, the Reports utiity. Monitoring ink ine usage is a key part of this process. Setting up goba conference biing Since a goba conference resuts in biing data distributed over mutipe sites, you must configure a stored procedure (Goba Biing) to run on a daiy basis, as we as separatey on each site. A ocay based Ca Detai Records (CDRs) generated by the goba conference must be reocated to a singe, targeted site for reports and biing purposes. Transferred CDRs acquire the goba conference reference number (Goba Ref) of the CRS on which the conference was originay booked. Athough each CDR incudes a fied that references the site on which the CDR originated, the goba conference reference number takes precedence. Each CRS in the network forwards the CDRs to the site identified by the reference number. Web, post-conference, and CRS reports incude the tota participant counts based upon the goba conference reference number. Therefore, goba CDR biing information is captured one time ony at the referenced site and not the originating site. Tip: Tip: Run the biing appication after CDRs are transferred to ensure compete goba biing information. 252 Administering Meeting Exchange Servers

253 Chapter 23: Running mutisite This chapter describes the foowing: About goba conferences Scheduing goba conferences Conference features Tracking biing information for goba conferences About goba conferences Goba conferences are schedued, unattended conferences that start and end at a predefined time and run on severa bridges simutaneousy. End users book goba conferences on a CRS, which automaticay propagates the reservation across a other CRS servers in the mutisite network. If severa active conferences share the same Goba Conference ID, mutisite inks them together using specific moderator VLL ines caed AutoVLLs. The spokes dia to the hub using the number specified in the CRS system parameters. Using one of the foowing formats, the spokes pass the conferee passcode for access the conference: Or <DNIS>...<CONFEREE PASS CODE># A goba conference begins: # When the first participant dias a specified teephone number into the nearest bridge in the mutisite network and enters a conference passcode. As additiona participants dia into the goba conference from remote bridges, mutisite creates audio inks between neighboring, active bridges within the network. Operators can use the operator consoe, Bridge Tak, to connect to a bridge in the network and view a oca conference segment of the goba conference. Note: Note: If the hub is no onger in the goba conference, for exampe, if the number of participants on the hub bridge goes to zero, the actve spokes wi re-estabish the handshake with one another to keep the goba conference running. Apri

254 Running mutisite Scheduing goba conferences An operator can create goba conferences using the CRS Front End appication. Note that you must incude a moderator for the conference to contro conference features, such as ecture or security. Note: Note: You can ony schedue goba conferences using a CRS, which propagates a goba conference across a other CRSs in the mutisite network. To schedue a goba conference: 1. Doube-cick the CRS icon dispayed on your desktop. 2. Cick Customer Bookings. 3. Seect the company and the cient for whom you wish to create a schedued conference. 4. Cick Create Reservation. 5. Enter your reservation detais. When you seect Goba, the CRS automaticay seects a moderator for the conference. Note: Note: To insta passcodes across a mutisite system, it is important to have a passcode management strategy so that a sites can be instaed efficienty. For exampe, you shoud pan the instaation sequence and manage the passcode range on each site. For information, see the Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. 6. Confirm the reservation. 7. Enter a tite for the reservation. The appication dispays the Booking Summary diaog. 254 Administering Meeting Exchange Servers

255 About goba conferences Figure 33: Booking Summary Diaog The CRS books the conference ocay and propagates the reservation across a CRSs in the network. The CRS assigns a goba reference number (Goba Ref) to each oca segment of the goba conference. Tip: Tip: A symbo in the Booking Summary diaog signifies a goba conference. Here are some important reminders when scheduing a goba conference: Conference features and passcodes are identica for a bridges; however, area-specific Diaed Number Identification Service (DNIS) or Direct Dia Inward (DDI) numbers remain oca. Mutisite keeps track of CDR information for goba conferences through the goba conference ID stored in each CRS database. The teephone number can be a goba conference (800) number or a oca number. Each conference, incuding the number of requested ines and goba conference features, is schedued on a bridges in the mutisite network. Note: Note: To avoid scheduing conficts, you shoud run ony one instance of mutisite for each conference server and CRS unit at a time. Apri

256 Running mutisite For more information about scheduing, see Using Meeting Exchange, which is avaiabe on support.avaya.com. Managing goba conferences Simiar to a reguar conference, operators can modify the oca segments of the goba conference features, mute ines, respond to hep requests, and so on. Mutisite is positioned as an unattended soution since operators cannot see more than one segment of the goba conference on their workstation. Using the CRS Front End, an operator or administrator can view various detais of goba conferences by cicking the GCD button on the Conference Schedue diaog. Tabe 46 describes the Conference Schedue options. Tabe 46: GCD options in the CRS Conference Schedue diaog Feature Server Ref LinkServer LinkPhone LinkPty LmodP GmodP GmodA Gock Gbcas GmuA GmuLk Gkeep Description The site name. The oca conference reference number. The current hub s server name. The current hub s phone number. The current hub ink priority. (0 is the highest, 5 is the owest priority). Dispays the presence of the oca moderator. Denotes the presence of the goba moderator. Indicates the arriva of the goba moderator. Dispays that the goba ock function is active. Indicates that the goba broadcast function is active. Dispays that the goba mute a function is active Denotes that the goba mute ock function is active. Indicates that the goba keep function is active. 1 of Administering Meeting Exchange Servers

257 Conference features Conference features Mutisite supports most oca and goba conference features described in the foowing sections. Goba eve conference features At the goba conference eve, moderators can use the features isted in Tabe 47. Tabe 47: Moderator-controed features specific to goba conferences Feature Lecture Secure/ock Moderator Hang up Music Entry tones/exit tones Description The moderator can ecture a goba conference. If schedued, the moderator can secure a goba conference. Note: Note: If a moderator secures the conference, a new participant or AUTOVLL cannot join the conference. If schedued, the system hangs up a caers when the ast moderator eaves the conference. The moderator can use DTMF commands to togge this feature on or off during the conference. If schedued, the system pays music to a caers unti the first moderator joins the conference. If schedued, conference participants can hear Entry tones/messages and Exit tones/messages. There are severa Entry and Exit tone options depending upon the bridge configuration. Note: Note: Set this feature to OFF or TONES ony. Participants hear the tones as soon as a ink ine (AUTOVLL) joins the conference. Apri

258 Running mutisite Loca conference features Tabe 48 detais the features that are excusive ony to the oca segment of goba conferences. Tabe 48: Moderator-controed features specific to oca conferences Feature Conference Record/Payback Originator Dia Out (ODO) Participant count Roster Description Moderators can start recording the conference on the bridge where they dia in. The goba conference is recorded as ong as the ink ines are in pace. The fie recording is stored on the oca bridge where the conference was recorded. Moderators must start the recording manuay by entering DTMF commands. Note: Tip: Note: A moderator must be present to record the conference. Tip: The moderator shoud manuay start the recording to avoid creating mutipe copies that may not be compete. If enabed on the system, the moderator can dia out to pace additiona oca participants into a oca segment of a goba conference; however, they cannot dia out from a different bridge to which they dia in. The moderator can hear a count of participants for the oca segment of the conference ony. Moderators or participants can hear a ro ca of participant names or preset dia ist for the oca segment of the conference ony. 258 Administering Meeting Exchange Servers

259 Conference features Non-supported features Tabe 49 describes the goba conference features not avaiabe for this reease. Tabe 49: Goba conference features not currenty supported Feature Subconference Ro ca Subconference/ Intercept DNIS/DDI Direct Q&A Poing Description The moderator can create a subconference for the oca segment of the goba conference. The system can ony pay a oca participant ro ca (roster). Any participant or moderator can initiate an unattended subconference at any time during a conference by entering *93. The moderator ony intercepts the ast caer in the oca conference segment. The system aows direct entry into a conference. Q&A is excusivey an attended conference feature. Poing is excusivey an attended conference feature. 1 of 2 Apri

260 Running mutisite Tracking biing information for goba conferences Each CRS server tracks Ca Detai Records (CDRs) and biing information for its oca bridge and transmits the CDR data back to the bridge where the conference was originay booked. If no participants diaed into a specific bridge, no CDR data is avaiabe. Biing is run independenty at each site, but reports can be run from a centra site. For more information about reports and biing, see Administering Meeting Exchange Appications, which is avaiabe on support.avaya.com. Goba conference resource monitoring The CRS reports appication provides this capabiity. This provides port utiization of ink ines and conference resources. 260 Administering Meeting Exchange Servers

261 Chapter 24: Navigating mutisite Meeting Exchange 5.2 contains a Windows interface for the mutsite appication. Using this Windows interface, you can easiy monitor the status of the mutisite engine. This chapter describes the new interface. It contains the foowing sections: Introduction CRS pane Bridge pane Stats pane Log Messages area Introduction The mutisite interface consists of four separate areas. The mutisite interface has been designed primariy as a too for Support Engineers. CRS pane Bridge pane Stats pane Log Messages area Figure 34 shows the interface. Apri

262 Navigating mutisite Figure 34: Mutisite Interface CRS pane The CRS pane shows: The IP address of the CRS in the foowing format: <ipaddress>:<port>:<enc ss >. The status of the connection. The status vaues are Disconnected, Connected - Logged Out, Connected - Logged In, Connected - Syncing). The deay, which is represented by the sowest response received from this server. The version of this server. Bridge pane The Bridge pane shows the same information as the CRS pane, but refers to the bridge server. For more information, see CRS pane on page Administering Meeting Exchange Servers

263 Stats pane Stats pane The Stats pane shows: The number of gobas that are currenty active. For exampe: G0050; H0040; O0010 = 50 gobas, 40 Hubs, 10 Outgoing inks. The number of waiting messages in the CRS and bridge queues. - CRS exampe: T0005; R0002 = 5 messages to be transmitted to CRS, 2 messages to be received from CRS. - Bridge exampe: T0005; R0002; E0007 = 5 messages to be transmitted to Bridge, 2 messages to be received from Bridge, and 7 messages in the event queue from the Bridge. The current server uptime for both the CRS and bridge servers. For exampe: B0072h; C0072h = Bridge up 72 hours, CRS up 72 hours. s=seconds, m=minutes, h=hours Log Messages area The Log Messages area shows the og message. Each og consists of: Time (hh:mm:ss) Source (which thread in the mutisite engine is ogging it) Type (Error / Info / Verbose / Debug) Text (The actua og information) At the base of the Log Messages area, there are two checkboxes. Seect Track Latest to enabe the Log Messages area to scro as new ogs arrive so that the atest og is awyas on top. Seect Log To Screen to dispay the ogs in the Log Messages area. There are aso three buttons: Cick Log Reset to deete a og fies. The mutisite appication stores a configurabe number of og fies regardess of whether you cick this button. The Log Reset button is usefu to reset the dispay. Apri

264 Navigating mutisite Cick Query to view the currenty in-progress conference in more detai. For more information, see Figure 35. Cick Cose to cose the appication. Figure 35: Exampe Query Diaog 264 Administering Meeting Exchange Servers

265 Appendix A: Configuration task ist This appendix ists the common Meeting Exchange configuration tasks that you can perform using the System Administrator Main Menu > Configurations menu. It contains the foowing sections: Tips for using this document Configuration tasks Tips for using this document If you do not know the name of the parameter you want to configure but you do know the end resut of the configuration task, that you want to perform, you can use this chapter to find the information you require. It provides an aternative method for finding information on the Meeting Exchange parameters. For exampe, using the Adobe Reader search option, search for a term such as pause to find the information you require to specify the pause before Meeting Exchange pays a message to an incoming teephone ine. These chapters contain reated information: Configuring the Meeting Exchange appication server on page 61 describes how to navigate to the Configurations menu. It aso provides an overview of each configuration sub-menu. Finding parameters by name on page 269 ists the configuration parameters. It provides an aternative method of finding the information that you require. Apri

266 Configuration task ist Configuration tasks Tabe 50 ists the common configuration tasks. Tabe 50: Common Configuration Tasks I want to... Where to find this information Configure conference payback. Tabe 58 Configuring recording on page 141 Configure conference recording. Tabe 58 Configuring recording on page 141 Configure DTMF. Tabe 58 Configure ecture settings. Tabe 58 Configure mute settings. Tabe 58 Configure operator hep, assistance. Tabe 59 Configure PINs. Tabe 58 Configuring PINs on page 133 Configure roster, ro ca. Tabe 58 Configure sub conferencing. Tabe 58 Configure the output of reports. Tabe 52 Tabe 53 Enabe or disabe dia out for Moderators. Tabe 58 Enter the name of the conferencing server. Tabe 58 Specify audio messages, prompts. Tabe 60 Configuring audio messages on page 151 Specify automatic conference IDs. Tabe 58 Specify date and time formats. Tabe Administering Meeting Exchange Servers

267 Configuration tasks Tabe 50: Common Configuration Tasks I want to... Specify how ong Meeting Exchange waits for passcodes. Where to find this information Tabe 51 Specify messages. Tabe 58 Configuring audio messages on page 151 Specify the Meeting Exchange response to invaid passcodes. Specify the number of digits that Meeting Exchange captures when caers dia the conference server. Specify the number of ines that Meeting Exchange dias in a bast dia. Specify the number of teephone digits which Meeting Exchange expects. Specify the pause before Meeting Exchange pays a message to an incoming teephone ine. Tabe 51 Tabe 58 Tabe 60 Tabe 54 Tabe 51 Tabe 54 Configuring ca branding on page 44. Configuring Meeting Exchange number coection on page 90. Tabe 57 Specify tones, beeps, sounds. Tabe 54 Tabe 58 Tabe 60 Warning Tone configuration on page 317. Customizing the scheduer utiity on page 66. Specify what happens when participants hang-up their teephone ine. Specify what to do with fauty teephone ines. Specify whether Meeting Exchange aows eary entry into conferences. Specify whether Meeting Exchange extends conferences. Tabe 57 Tabe 57 Tabe 58 Tabe 58 Apri

268 Configuration task ist Tabe 50: Common Configuration Tasks I want to... Where to find this information Turn ogging on or off. Tabe 58 Viewing Meeting Exchange information on page 107 Write a transcript of audio messages. Tabe 54 Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. 268 Administering Meeting Exchange Servers

269 Appendix B: Finding parameters by name This appendix ists the Meeting Exchange parameters that you can configure using the System Administrator Main Menu > Configurations menu. It contains the foowing sections: Tips for using this document Bast dia configuration properties CDR configuration properties CODR configuration properties Ca Routing configuration properties Operator configuration properties Supervision configuration properties System configuration properties Timed Assist configuration Voice Message configuration Warning Tone configuration Tips for using this document If you know the name of the parameter you want to configure, you can use the Adobe Reader search option to ocate a detaied description of each parameter. For exampe, search for the parameter name Annunciator Deay to find the information you require to specify the pause before Meeting Exchange pays a message to an incoming teephone ine. These chapters contain reated information: Configuring the Meeting Exchange appication server on page 61 describes how to navigate to the Configurations menu. It aso provides an overview of each configuration sub-menu. Configuration task ist on page 265 ists the configuration tasks. It provides an aternative method of finding the information that you require. Apri

270 Finding parameters by name Bast dia configuration properties Tabe 51 describes the bast dia configuration properties. Tabe 51: Bast Dia Configuration Properties Parameter Max. Channe Bast Bast Deay Invaid Code Description The number of channes (1 to 16) that Meeting Exchange simutaneousy dias during a bast dia. The defaut is eight channes. Diaing channes in groups with a short pause between each group prevents fooding the network with cas. The Bast Deay parameter specifies the pause between bast dias. The number of seconds (0 to 60) that Meeting Exchange waits before diaing the next group of channes in a bast dia. The defaut is two seconds. The Meeting Exchange response to participants who enter an invaid passcode or participants who do not enter the digits within the time aowed. The Scan Time parameter specifies the aowed time. There are two vaues: ENTER (defaut) The participant is paced in the Enter Conference to wait for operator assistance. Hang-up The system disconnects the caer. The Invaid Code setting aso specifies the Meeting Exchange response to participants entering codes for secured bast conferences. This parameter appies to coded bast dias ony. In coded basts, the caed party must acknowedge the ca using a DTMF command within a configurabe time. This step ensures that Meeting Exchange quicky disconnects cas that are answered by voicemai. 1 of Administering Meeting Exchange Servers

271 CDR configuration properties Tabe 51: Bast Dia Configuration Properties (continued) Parameter Scan Time (5 to 20) CLPG Timeout (0, 30 to 600 s) Description The number of seconds (5 to 20) that Meeting Exchange scans for additiona passcode digits after a participant enters the first digit. The defaut is 20 seconds. Avaya recommends adjusting this parameter to accommodate the ongest passcode on your system. This parameter appies to coded basts ony. In coded basts, the caed party must acknowedge the ca using a DTMF command within a configurabe time. This step ensures that Meeting Exchange quicky disconnects cas that are answered by voicemai. Specifies what happens to ines that remain in the Ca Progress (CLPG) state after a bast dia. (Some ines may remain in the CLPG state because no one answers the bast dia, or the participant fais to enter digits.) 30 to 600 (seconds) The system automaticay hangs up ines remaining in the CLPG state beyond the specified time. This incudes participants using rotary phones, who cannot enter DTMF commands. 0 (defaut) There is no timeout. Lines remain in the CLPG state unti an operator accesses the ine or cears or exits Bast Dia, which hangs up a ines in the CLPG state. Avaya recommends specifying a timeout vaue when operators are not avaiabe to cear the ines. 2 of 2 CDR configuration properties Meeting Exchange records a CDRs in fu. This CDR Configuration option ony specifies the formatting options for viewing and printing. This section contains the foowing sections: Formatting considerations CDR configuration properties Apri

272 Finding parameters by name Formatting considerations Using the CDR Configuration and CODR Configuration options, you can configure the properties of four different types of CDR and CODR reports.they are: Stye 1 (Short Format) Stye 2 (Long Format) Stye 3 (Custom Format) Auto CDR or Auto CODR For each type of report, you can incude or excude report fieds to suit customer requirements. Each time you print a CDR or CODR report, you can choose which of the types of report you require. You can modify a stye names except for the Auto (CDR or CODR) stye name. This fexibiity enabes you to assign stye names that indicate the types of data fieds that you have incuded or excuded from a stye. The defaut names, Short Format, Long Format, and Custom Format do not indicate the scope of data that you can incude in an output stye you can configure the Short Format to incude a data, and conversey you can configure the Long Format to incude a singe data item. You cannot modify the Auto (CDR or CODR) stye name. Additionay, you cannot view or print these reports. The Auto stye is the defaut stye for CDRs and CODRs exported by Meeting Exchange to a remote host by the autocdr process. Coumn width for an output stye is directy proportiona to the number of fieds that you incude in a stye. The more fieds you specify, the more coumns appear in the report output. You may want to imit the number of fieds for records so that they print on a singe ine for easier reading. If you exceed the number of fieds that fit into a singe ine, the report prints the additiona fieds on a second ine beow the first. Most printers accommodate CDRs and CODRs up to 80 coumns ong, printing each record on a separate ine. To print CDRs and CODRs with more than 80 coumns, Avaya recommends the use of andscape mode to accommodate a data. Meeting Exchange determines the tota coumns a CDR format requires and dispays this information next to the stye name you choose in the seection box when you print or view CDRs and CODRs. Knowing the number of coumns is usefu when setting up printers. This vaue is defined as foows: number of coumns = (tota fied sizes + number of fieds) -1 A fieds except Stye Name and Headers in CDRs and CODRs and Phone in CDRs are simpe ON/OFF togges, where ON incudes the fied in the stye. For more information about viewing and printing CDR reports, see Ca Detai Record (CDR) reports on page Administering Meeting Exchange Servers

273 CDR configuration properties CDR configuration properties Tabe 52 describes the fieds avaiabe for a CDR report. For more information about viewing and printing CDR reports, see Ca Detai Record (CDR) reports on page 108. Tabe 52: CDR Configuration Properties Parameter Size Options Description Exampe Stye Name n/a Up to 15 characters Name of a CDR output stye. The system stores four different CDR styes. You can rename a styes except the Auto CDR stye. Stye Name text is not incuded in the source of CDR fies. Headers n/a 0 to 60 Up to three ines of headings can be incuded in the report output. The Headers fied accepts entries from 0 to 60. Enter a 0 to disabe headers. Any other vaue (x) prints headers every xth CDR. For exampe, the defaut vaue for the Custom Format stye is 57. When you seect this stye for printing or viewing, the output incudes a Header every 57th CDR incuded in the output fie. Headers text is not incuded in the source of CDR fies. Line Number 4 OFF, ON Number of the teephone ine used for this ca (1-1200). n/a n/a of 10 Apri

274 Finding parameters by name Tabe 52: CDR Configuration Properties (continued) Parameter Size Options Description Exampe Conf Num Sm 3 OFF, ON Number of the ast conference room in which the teephone ine was incuded up to room 999. This number wi be 999 if the conference room is number 999 or above because Conf Num Sm is accurate up to room 998 ony. Use the Conf Num Wh fied to determine the conference room number as it accomodates a 2000 possibe conferences. If the conference takes pace in room 1001, Conf Num Sm = 999 and Conf Num Wh = If the conference takes pace in room 5, Conf Num Sm =5 and Conf Num Wh = 5. Seize Time 8 OFF, ON Time of day the ine connected to the system, recorded to the nearest second and based on a 24-hour cock. Disc. Time 8 OFF, ON Time of day the ine disconnected from the system, recorded to the nearest second. Ca Duration 4 OFF, ON Tota time the ine was connected to the system, rounded down to the nearest minute with a 1-minute minimum. Because ca duration represents a ine s entire activity on the system incuding minutes spent with an operator or in the Enter Queue it typicay exceeds the time indicated by the Conf Minutes fied. 01 to 999 ** indicates that the ine was not paced in a conference hh:mm:ss 12:30:49 hh:mm:ss 15:43: of Administering Meeting Exchange Servers

275 CDR configuration properties Tabe 52: CDR Configuration Properties (continued) Parameter Size Options Description Exampe Line Name 20 OFF, ON For an attended conference, the Line Name is the name entered by the operator in the Bridge Tak Line Detai diaog. For an unattended conference, the information depends on whether PIN codes were used for the conference. If PIN codes were not used, the Line Name is the passcode of participant. If PIN codes were used, the Line Name is the PIN code of the caer. For DNIS/DDI cas processed by the Ca Routing feature, the CDR Report takes the ine name from the corresponding Ca Branding tabe entry. Mod. Status Phone 1 OFF, ON Indicates whether a participant had moderator status at any time during the conference. It has three possibe vaues: N, Y, and A indicating participant, moderator, and aternate moderator respectivey. Aternate moderator represents the co-chair feature. 11, 20, or 40 OFF, short (11), medium (20), ong (40) The participant phone number stored on Meeting Exchange in dia ists and in the PIN code database. Options for the this fied et you choose the ength that best meets your requirements SHORT (11 digits), MEDIUM (20 digits), LONG (40 digits), or OFF (0). The phone number from which a caer actuay dias is represented by the Caing Phone parameter. Conf Name 12 OFF, ON Name of the conference in which the ine is incuded. The system name appears in the Conf Name fied for the first entry in a CDR. Saes Rep 1 or 4321 N Saes mtg 3 of 10 Apri

276 Finding parameters by name Tabe 52: CDR Configuration Properties (continued) Parameter Size Options Description Exampe Conf ID 12 OFF, ON Conference ID number or confirmation number. For attended conferences, you can configure Meeting Exchange to automaticay assign conference IDs, or an operator can assign them manuay. The conference ID for schedued attended conferences may be entered by the operator or by an externa reservation system. Unattended conferences are aways assigned a conference ID. For schedued conferences, this is either the operator or moderator-assigned ID (up to 12 aphanumeric characters) or the Meeting Exchange-generated confirmation number (up to 12 digits). When an operator or moderator assigns an ID to a conference, this ID repaces the Meeting Exchange-generated ID and confirmation number when the conference starts, so this ID appears in the CDR for that conference , or dept 23 Conf Minutes 4 OFF, ON Tota minutes a ine spends in the conference, rounded down to the nearest minute with a 1-minute minimum. Because participants move about on the system, such as when they wait in the Enter conference, this vaue is typicay ess than the tota time the ine is connected to the system, as specified by the Ca Duration parameter of Administering Meeting Exchange Servers

277 CDR configuration properties Tabe 52: CDR Configuration Properties (continued) Parameter Size Options Description Exampe Conf Entry Time 8 OFF, ON Time of day the teephone ine entered the conference based on Greenwich Mean Time (GMT). The system records the time the ine entered the conference to the nearest second. Cas that never join a conference (for exampe, a disconnect from INP) show a conference entry time that corresponds to 00:00 GMT. Ca Type 10 OFF, ON Type of ca based upon the setup of the ca, typicay one of the foowing vaues: Dia-in Participant caed in to the attended or unattended conference. ODO An operator or moderator made the ca or initiated the ca, such as in a bast dia. Other possibe vaues incude: VLL, u_bast, or any string. hh:mm:ss e.g. 08:59:30 ODO 5 of 10 Apri

278 Finding parameters by name Tabe 52: CDR Configuration Properties (continued) Parameter Size Options Description Exampe Disc. Reason 2 OFF, ON Code indicating the reason that Meeting Exchange disconnected a ca. Vaid codes incude: 0 = Unknown 1 = Network 2 = Operator hangup 3 = Invaid code 4 = Code timeout 5 = Conference secured 6 = Invaid code time of day 7 = Maximum ines reached 8 = Conference time expired 9 = Transferred to a PBX ext. 10 = Line timeout 11 = CLPG timeout (Bast conferees ony) 12 = Other system 13 = Faut 14 = Aarm 15 = DSP faied 16 = Error 17 = DNIS/DDI hang up (Systems with DNIS/DDI ony) 18 = ODO hang up 19 = Moderator hang up (unattended) 20 = Transferred to another conference 21 = SP Disconnect 22 = Channe hot swapped 23 = Biing code error 24 = Session has timed out 25 = No system resources avaiabe 26 = Invaid security credentias 27 = Gare on the channe Codes 3-8 appy to unattended conferences. Code 18 occurs when ODO moderators hang up a ine that they have diaed or their own ine of Administering Meeting Exchange Servers

279 CDR configuration properties Tabe 52: CDR Configuration Properties (continued) Parameter Size Options Description Exampe Company Name 20 OFF, ON Company name associated with a ine. Meeting Exchange takes it from dia ists (fastdias and basts) or an operator enters it. For DNIS/ DDI cas processed by the Ca Routing feature, Meeting Exchange takes the company name from the corresponding entry in the ca branding configuration tabe. DNIS Digits 16 OFF, ON DNIS/DDI digits that match an entry in the Ca Branding tabe for dia-in cas processed by the Ca Routing feature. Transfer 1 OFF, ON Indicates whether a ine was transferred by the operator to the specified conference from another conference. Y The ine was transferred. N The ine was not transferred. Transferred ines have at east two CDRs because Meeting Exchange issues a separate CDR each time a participant transfers to a conference. A but the first CDR show a Y in the transfer fied. A but the ast CDR show disconnect reason 20 in the Disc Reason fied. Reconnect 1 OFF, ON Indicates whether a ine disconnected and then reconnected to the system. Y The ine disconnected then reconnected. Operators must use the Reconnect command to fag reconnected ines. A reconnected ine has two CDRs, with the CDR from the second connection showing Y in the reconnect fied. The fied is bank if a ine was not reconnected. PIN Code 16 OFF, ON PIN code required for a ine. This fied appies ony to unattended conferences with PIN codes enabed. xyz corp Y or N Y of 10 Apri

280 Finding parameters by name Tabe 52: CDR Configuration Properties (continued) Parameter Size Options Description Exampe Access Time Caing Phone 8 OFF, ON The time that an operator first accessed a dia-in ine after it entered the system. This fied aows System Administrators to distinguish between the time a ca entered the system, was first accessed by an operator, and was paced in a conference. The fied is bank if the ine was never accessed or was a dia-out ca. 40 OFF, ON Phone number from which a caer diaed in to the conference. Appies ony to systems configured to coect ANI digits. Cross Ref 12 OFF, ON Unique number Meeting Exchange assigns to a main conference and a sub-conferences created from it. This number associates main conferences with sub-conferences. User Conf Type 4 OFF, ON Indicates the type of conference in which the teephone ine is incuded: 0 This conference is not a sub-conference or a conference that has been intercepted by an operator. 1 This conference is a sub-conference. 2 This conference has been intercepted by an operator. Seize Date 8 OFF, ON The date the teephone ine connected to Meeting Exchange. Network Type 2 OFF, ON Dispays the Network Type, which can be PSTN or VoIP that was used for the conference: 0 The participant caed via a PSTN ine. 1 The participant caed via a VoIP ine. Line Aux1 60 OFF, ON Any caer record information, such as an emai address. hh:mm:ss 08:55: , 1, or 2 mm/dd/yy e.g. 12/01/ 02 0 or 1 name@co mpany.com 8 of Administering Meeting Exchange Servers

281 CDR configuration properties Tabe 52: CDR Configuration Properties (continued) Parameter Size Options Description Exampe Line Aux2 60 OFF, ON Any caer record information. n/a Line Aux3 60 OFF, ON Any caer record information n/a Passcode 16 OFF, ON In a Fexfow conference, this fied is the ast passcode that the participant entered via DTMF. Aux Code 40 OFF, ON In a Fexfow ca, this is a biing reference number that a moderator assigns to a conference. In Bridge Tak, this fied is caed the Accounting Code. Prompt Set 2 OFF, ON The audio prompt set used in the conference , 2, Video Info 5 OFF, ON Not appicabe for this patform. Conf Num Wh 5 OFF, ON Number of the ast conference in which the ine was incuded. Aux Code2 40 OFF, ON When ON, the conferencing server prompts moderators for a second biing code for their conference. You cannot set a second biing code using the Avaya Bridge Tak appication. Oper Hep Reqs 2 OFF, ON This vaue records the number of requests for operator assistance during the ca. Participants request hep by entering *0 on their teephone keypad. The defaut vaue is OFF. 01 to 2000 ** indicates that the ine was not paced in a conference of 10 Apri

282 Finding parameters by name Tabe 52: CDR Configuration Properties (continued) Parameter Size Options Description Exampe Last Hep Req Unique Participant Identifier 8 OFF, ON This vaue records the time of the ast request for operator assistance. The defaut vaue is OFF OFF, ON This vaue records the unique participant identifier of the caer. Participants must enter this DTMF numeric code to access their conference when Operators seect Identify or Identify and Vaidate from the Participant ID drop-down ist at conference booking time. 22:30: of 10 For more information about viewing and printing CDR reports, see Ca Detai Record (CDR) reports on page 108. CODR configuration properties Meeting Exchange records a CODRs in fu. This CODR Configuration option ony specifies the formatting options for viewing and printing. Meeting Exchange produces CODR reports in a simiar way to CDR reports. For more information about viewing and printing CODR reports, see Ca Detai Record (CDR) reports on page 108. For more information on formatting reports, see Formatting considerations on page Administering Meeting Exchange Servers

283 CODR configuration properties Tabe 53 describes the fieds avaiabe for a CODR report. Tabe 53: CODR Configuration Properties Parameter Size Options Description Exampe Stye Name n/a Up to 15 characters Name of a CODR output stye. The system stores four different CODR styes. You can rename a styes except the Auto CODR stye. Stye Name text is not incuded in the source of CODR fies. Headers n/a 0 to 60 Up to three ines of headings can be incuded in the report output. The Headers fied accepts entries from 0 to 60. Enter a 0 to disabe headers. Any other vaue (x) prints headers every xth CODR. For exampe, the defaut vaue for the Custom Format stye is 57. When you seect this stye for printing or viewing, the output incudes a Header every 57th CODR incuded in the output fie. Headers text is not incuded in the source of CODR fies. Conf Num Sm 3 OFF, ON Number of the ast conference room in which the teephone ine was incuded up to room 999. This number wi be 999 if the conference room is number 999 or above because Conf Num Sm is accurate up to room 998 ony. Use the Conf Num Wh fied to determine the conference room number as it accomodates a 2000 possibe conferences. If the conference takes pace in room 1001, Conf Num Sm = 999 and Conf Num Wh = If the conference takes pace in room 5, Conf Num Sm =5 and Conf Num Wh = 5. Conf Name 12 OFF, ON Name of the conference in which the ine is incuded. The system name appears in the Conf Name fied for the first entry in a CODR. n/a n/a 01 to 999 ** indicates that the ine was not paced in a conference Saes mtg 1 of 9 Apri

284 Finding parameters by name Tabe 53: CODR Configuration Properties (continued) Parameter Size Options Description Exampe Conf ID 12 OFF, ON Conference ID number or confirmation number. For attended conferences, you can configure Meeting Exchange to automaticay assign conference IDs, or an operator can assign them manuay. The conference ID for schedued attended conferences may be entered by the operator or by an externa reservation system. Unattended conferences are aways assigned a conference ID. For schedued conferences, this is either the operator or moderator-assigned ID (up to 12 aphanumeric characters) or the Meeting Exchange-generated confirmation number (up to 12 digits). When an operator or moderator assigns an ID to a conference, this ID repaces the Meeting Exchange-generated ID and confirmation number when the conference starts, so this ID appears in the CODR for that conference. See Automatic Conf. ID in System configuration properties on page 298 for detais on configuring the system to automaticay generate conference IDs. Max User Count 4 OFF, ON Maximum number of simutaneous conference participants, excuding operators (1 1200). Start Time 17 OFF, ON Date and time the conference begins. Start Time is rounded up to the nearest second, based on a 24-hour cock , or dept mm/dd/yyhh:mm:ss e.g. 07/27/ 02-08:59:30 2 of Administering Meeting Exchange Servers

285 CODR configuration properties Tabe 53: CODR Configuration Properties (continued) Parameter Size Options Description Exampe Conf Duration Conf Minutes Attended (U/A) 8 OFF, ON Period in minutes, rounded up to the nearest minute, between the first participant joining the conference and the ast participant eaving the conference. The interva extends from the Start Time to the Conf End Time. This is the ength of the conference itsef, in contrast to the Conf Minutes, which is the tota individua ine minutes. 8 OFF, ON Approximate sum of the individua ine times for a conference. Whie a conference itsef may ast for ony 30 minutes, the Conf Minutes typicay exceeds this vaue. The ratio of Conf Minutes to Conf Duration varies with the number of participants and how ong each of them remains in the conference. Sometimes conferees wait in the conference room severa minutes before the conference begins. Because the system begins tracking conference minutes as soon as the first person joins the conference, the tracked minutes may not match the actua conference time and thus ead to over-biing. 1 OFF, ON Type of conference: A Attended (Operator assistance schedued for this conference.) U Unattended (Operator assistance not schedued for this conference. The system cassifies the conference as unattended even if operator assistance is provided on an ad hoc basis.) O On-Demand (Operator assistance not schedued for this conference. This is a re-occurring type of conference.) A or U or O 3 of 9 Apri

286 Finding parameters by name Tabe 53: CODR Configuration Properties (continued) Parameter Size Options Description Exampe Status Info. 43 OFF, ON Indicates which of 11 different conference features were used in a conference. An ON appears in the CODR if the feature was used at any time during the conference; otherwise, OFF appears. The header abe for each of the tracked features appear in the foowing order: ENT Entry Tone EXIT Exit Tone LEC Lecture LNK Linking MUS Music PBK Payback REC Record Q&A Question & Answer POL Poing SEC Security Vaid output for the ENT and EXIT fieds incude: OFF, SYS, MSG, TON, or BTH (both). The PBK and REC fied output indicates the recording and payback mode: ANL Anaog DIG Digita A/D Anaog and digita OFF Off Notes 60 OFF, ON Conference information text entered either by an operator using Bridge Tak. Conf End Time 17 OFF, ON Date and time the ast participant eaves the conference. It is recorded to the nearest second, based on a 24-hour cock. ENT EXIT REC - DIG PBK - DIG... and a conferees were successfu y entered to the conference... mm/dd/yyhh:mm:ss e.g. 07/27/ 02-10:00:00 4 of Administering Meeting Exchange Servers

287 CODR configuration properties Tabe 53: CODR Configuration Properties (continued) Parameter Size Options Description Exampe Contact Name Contact Phone RP Fie Number Sched Duration 20 OFF, ON Contact name entered for a conference. 20 OFF, ON Contact phone number for a schedued conference. 8 OFF, ON Fie name specified for participant-requested record or payback. When set to ON, Meeting Exchange extracts the fie name specified for record or payback from the information generated during the conference. This fied contains information ony when a participant initiated recording or payback. Operator-initiated recording names are not saved. 4 OFF, ON Number of minutes schedued for this conference. For schedued attended conferences, this fied appies ony if the Startup Notify Time parameter is set to ON and the conference is automaticay setup by the system. Meeting Exchange cacuates the schedued conference duration from the Start and End Times specified in the conference reservation form. Ann Smith confrcrd of 9 Apri

288 Finding parameters by name Tabe 53: CODR Configuration Properties (continued) Parameter Size Options Description Exampe Sched Partips 4 OFF, ON Number of ports reserved for participants in a schedued conference. This fied aways appies to schedued unattended conferences; however, it aso appies to attended conferences if the system s Startup Notify Time parameter is set to ON and the conference is automaticay setup by the system. Meeting Exchange extracts the number of ports schedued for the conference from the conference reservation form. The Auto Conf ID parameter must aso be set to OFF for schedue duration and participants to be tracked. Auxiiary 1 20 OFF, ON Additiona fied for up to 20 characters of conference information aong with the conference name. Auxiiary 2 20 OFF, ON Additiona fied for up to 20 characters of conference information aong with the conference name. Biing Code Confirm Num 20 ON, OFF The biing reference number that a moderator assigns to a conference. 12 ON, OFF The conference confirmation number. Goba ID 12 ON, OFF The vaue for this fied associates this CODR with other CODRs (with the same vaue) created for a singe conference distributed across mutipe bridges. This parameter is ony reevant in a MutiSite configuration confinfo1 confinfo of Administering Meeting Exchange Servers

289 CODR configuration properties Tabe 53: CODR Configuration Properties (continued) Parameter Size Options Description Exampe Cross Ref 12 ON, OFF A unique number that Meeting Exchange assigns to a main conference CODR and a sub-conference CODRs created from it to associate main conferences with the sub-conferences User Conf Type Sub Conf Count Intercpt Count 4 ON, OFF Indicates the type of conference: 0 This conference is not a sub-conference or an intercept conference. 1 This conference is a sub-conference. 2 This conference is an intercept conference. 4 ON, OFF The tota number of sub-conferences created from this conference. The defaut is zero. 4 ON, OFF The tota number of intercept conferences created from this conference. Data Conf 1 ON, OFF Indicates whether the conference has an associated data conference. N indicates no associated data conference. Y indicates an associated data conference. Conf Viewer 1 ON, OFF Indicates whether the Conference Viewer appication is associated with the conference. N indicates the Conference Viewer appication is not associated. Y indicates Conference Viewer appication is associated. Prompt Set 2 Indicates the Prompt Set used for the conference. Must be a vaue between 1 and 20. Conf Sec Code ON, OFF Conference security code Y Y 19 7 of 9 Apri

290 Finding parameters by name Tabe 53: CODR Configuration Properties (continued) Parameter Size Options Description Exampe Mod Sec Code 16 ON, OFF Moderator security code Sef Reg 1 ON, OFF Indicates whether the Sef Registration appication is associated with the conference. N indicates the Sef Registration appication is not associated. Y indicates Sef Registration appication is associated. Y Account Number Adhoc Creater Conf Number Wh Biing Code 2 50 ON, OFF The Account Number inks the schedue to the owner's profie on an externa database. For configurations using a CRS, this fied inks to the Account Number on the CRS. 128 ON, OFF Not appicabe for this patform. 5 OFF, ON Number of the ast conference in which the teephone ine was incuded. 20 OFF, ON When ON, Meeting Exchange prompts moderators for a second biing code for their conference to 2000 (** indicates that the ine was not paced in a conference.) of Administering Meeting Exchange Servers

291 CODR configuration properties Tabe 53: CODR Configuration Properties (continued) Parameter Size Options Description Exampe User Conf Type RP FNAME Wh CoCh Sec Code 3 OFF, ON When ON, the foowing vaues are vaid: 6: This is a payback conference 101: This CODR was generated as a resut of a recording being stopped. 102: This CODR was generated as a resut of a recording being paused. 103: This CODR was generated as a resut of a payback being stopped. 104: This CODR was generated as a resut of a payback being paused. 23 OFF, ON This fied contains the whoe payback fie name. The defaut vaue is OFF. 16 OFF, ON This fied records the co-moderator pass code of 9 For more information about viewing and printing CODR reports, see Conference Detai Records (CODR) reports on page 108. Apri

292 Finding parameters by name Ca Routing configuration properties Tabe 54 describes the ca routing configuration properties. Tabe 54: Ca Routing Configuration Properties Parameter Digit Parameters Fexibe Annunciator Messages Description The Digit Parameter option enabes you to specify the number of digits used for Ca Routing entries in the Ca Branding tabe. For more information on ca routing, see Configuring ca branding on page 44. When you access the Digit Parameters option, Meeting Exchange dispays the Digit Parameters screen. For more information on the Digit Parameters screen, see Tabe 55. The Fexibe Annunciator Messages option enabes you to compose, edit, and save text versions of annunciator messages. You can compose a message script for a narrator to read for a message recording, or you can determine what messages are avaiabe on the system without having to isten to the messages. Avaya deivers verbatim text for defaut prerecorded messages. However, the text for a message does not have to match its recorded version. You may want to abbreviate the text or insert keywords in the text that indicates when and why the message is payed. The Fexibe Annunciator Messages option is especiay usefu when you are setting up the Ca Branding tabe and you want to view messages to determine which one to specify for an entry in the tabe. For more information on configuring ca branding, see Branding the customer experience on page 89. For more information on customizing audio messages, see A short note about audio messages on page Administering Meeting Exchange Servers

293 Operator configuration properties Tabe 55: Digit Parameters Properties Parameter Size Options Description Exampe Number of Digits Short Coection Search The right-most number (from 1 to 16) of DNIS/DDI digits the system wi use to route a ca. This number must not exceed the actua number of DNIS/DDI digits received from the network. The system assumes receipt of a compete DNIS/DDI number when this imit is reached, ignoring any extra digits sent. (You can incude DNIS/DDI digits in a CDR. See Configuring CDRs on page 214.) The defaut is 4. OFF, ON Contros the search performed in the Ca Branding tabe when the system coects too few DNIS/DDI digits. ON The system attempts a partia match in right to eft order. For exampe, if Meeting Exchange ony coects the digits 127 when four digits are required, it matches these digits to the first entry in the tabe having 127 as its right most three digits. The system searches the Ca Branding tabe in ascending order unti it finds the first match. OFF (defaut) Any DNIS/DDI coection faiing to contain the prescribed number of digits is processed according to the widcard entry (????) in the Ca Branding tabe. Empty coections aways match the widcard entry (????). 4 OFF Operator configuration properties Tabe 56 describes the operator configuration properties. Apri

294 Finding parameters by name When you navigate to the Operator Configuration menu, Meeting Exchange dispays the Edit Operator Channe screen. The Operator Channe screen dispays the range of operator channes that you have configured on the Fex-DAPI Configuration screen. For more information on Fexibe Digita Auxiiary Port Interface (FDAPI) resources, see Configuring server resources on page 56. On the Edit Operator Channe screen, you must specify an operator channe. When you specify an operator channe, Meeting Exchange dispays the Operator Configuration screen for that operator. For more information on the Operator Configuration screen, see Tabe 56. Tabe 56: Operator Configuration Properties Parameter Printing Beep Mode Beep Time Remote (audio) Description This feature is not impemented in the current reease. Meeting Exchange pays a tone when it paces a participant in the Enter Queue, Hep Queue, or Disconnect Mode. Entry tones appy on a per conference basis. No Beep Do not beep. Singe Beep (defaut) Pay a 1-beep tone. Continuous Beep Pay a beep every one to five seconds (as specified by the Beep Time parameter). Specifies the duration in seconds, from 1 to 5, between beeps if you specify Continuous Beep as the Beep Mode parameter. The defaut is 5. Important:! Important: Do not use this feature in a SIP bridge depoyment. Specifies whether Meeting Exchange uses a revenue channe for the operator audio path instead of an FDAPI operator channe: Y Use a revenue channe for the operator audio path. You can specify the number of the revenue channe to which you want to assign the audio path with the Channe parameter. N (defaut) Use the FDAPI channe for the operator audio path. Switching the operator audio path from an FDAPI operator channe to a remote channe (Y) does not free an FDAPI operator channe configured for the system. 1 of Administering Meeting Exchange Servers

295 Supervision configuration properties Tabe 56: Operator Configuration Properties (continued) Parameter Channe Term Prompt Description Dispays the FDAPI operator channe or enabes you to specify a revenue channe number. If you set the Remote parameter to N, this parameter dispays the FDAPI operator channe number. If you set the Remote parameter to Y, this parameter enabes you to enter a channe number from the avaiabe revenue channes. If you specify a revenue channe for operator audio, do not incude this channe in a hunt group. This feature is not impemented in the current reease. 2 of 2 Supervision configuration properties Tabe 57 describes the supervision configuration properties.. Tabe 57: Supervision Configuration Parameters Parameter Annunciator Deay Dia Deay Description Specifies the pause before the system pays a message to an incoming teephone ine. To specify a deay, enter a vaue between 1 to 5 seconds. The defaut vaue is 0. Specifies the pause before Meeting Exchange begins to dia digits if a moderator initiates a dia out from the conference. This deay verifies dia tone. Vaid time intervas range from 1 to 5 seconds. The defaut vaue is 1. Consut your phone network provider to determine the most suitabe dia deay for your system. Note: Note: This feature is not impemented in the current reease. 1 of 3 Apri

296 Finding parameters by name Tabe 57: Supervision Configuration Parameters (continued) Parameter Disconnect Mode Disconnect Notification Description This setting determines what Meeting Exchange does when participants, who are attending attended conferences, hang up their teephone ine. This parameter does not determine what Meeting Exchange does when participants who are attending unattended conferences, hang up their teephone ine. There are two possibe vaues: OFF (defaut) Meeting Exchange puts disconnected ines back on hook, and the ines are immediatey avaiabe for a new ca. It is a good idea to set Disconnect Mode to OFF when you need to make disconnected ines immediatey avaiabe for new cas. ON Meeting Exchange puts disconnected ines into a pending state, awaiting an action from the operator. During this time, the Bridge Tak appication dispays a visua indicator to inform the operator that the participant has hung up their teephone ine. Specifies whether Meeting Exchange dispays additiona information about the teephone ine when a participant attending an attended conference, hangs up their teephone ine. There are two possibe vaues: ON The foowing message appears on the chat ine of each active workstation when a quaifying ine disconnects: O: DC: 0001 NAME C:0003 NAME where: 0 = Goba Message DC = Message Type (in this case, Disconnect) 0001 = Line Number NAME = Line Name C:0003 = Conference Number NAME = Conference Name This information is hepfu in determining whether to re-estabish the connection or aert the conference moderator of the disconnect. OFF (defaut) Meeting Exchange does not dispay disconnect information. 2 of Administering Meeting Exchange Servers

297 Supervision configuration properties Tabe 57: Supervision Configuration Parameters (continued) Parameter Wink Timeout Line Faut Description Specifies how ong Meeting Exchange waits for a wink-back from the far end before disconnecting the ine. Note: Note: This feature is not impemented in the current reease. Specifies whether Meeting Exchange disconnects fauted teephone ines. Operators commony pace teephone ines in a fauted state to take them temporariy out of service. There are two possibe vaues: OFF Meeting Exchange does not disconnect fauted ines. Meeting Exchange does not aow dia-outs from this ine. Meeting Exchange ignores any teephone cas to the fauted ine. Caers to the fauted ine hear their ca ringing the fauted ine. Caers do not hear a busy tone. ON (defaut) Meeting Exchange disconnects fauted ines. Caers to the fauted ine hear the busy tone. Caers do not hear their ca ringing the fauted ine. 3 of 3 Apri

298 Finding parameters by name System configuration properties Tabe 58 describes the system configuration properties. Tabe 58: System Configuration Parameters Parameter System Name Entry Tone Exit Tone DTMF Acknowedge Description Dispays the TCP/IP host name assigned to the system when system software is instaed. The name appears on screens and in various system fies and serves as the aias for the system IP address. Specifies the number of beeps in an entry tone when a participant enters a conference. Customers can enabe or disabe entry tones on a per-conference basis. Aso, Bridge Tak operators can enabe entry tones in an attended conference. Moderators can enabe entry tones for schedued conferences. Singe Beep (defaut) Doube Beep Specifies the number of beeps in an exit tone when a participant exits a conference. Customers can enabe or disabe exit tones on a per-conference basis. Aso, Bridge Tak operators can enabe exit tones in an attended conference. Moderators can enabe exit tones for schedued conferences. Singe Beep (defaut) Doube Beep Specifies whether Meeting Exchange sounds a tone when it receives DTMF (Dua-Tone Muti-Frequency) diaing input. ON Meeting Exchange emits an acknowedgment tone when participants press vaid DTMF digits on their teephones to enter a response to a po question or to pace themseves in either the Hep or Q&A queues. These acknowedgment tones assure participants that Meeting Exchange received their DTMF input. OFF (defaut) Meeting Exchange does not emit an acknowedgment tone. However, participants typicay hear norma DTMF tones as they press digits on their teephone keypad. 1 of Administering Meeting Exchange Servers

299 System configuration properties Tabe 58: System Configuration Parameters (continued) Parameter Transaction Logs Automatic CDR Print Automatic Conf. Cear Description Specifies whether Meeting Exchange generates operator Transaction ogs. ON (recommended) Meeting Exchange generates transaction ogs. OFF (defaut) Meeting Exchange does not generate transaction ogs. For more information on og fies, see Viewing Meeting Exchange information on page 107. Specifies whether Meeting Exchange automaticay exports the automatic ca detai record (CDR) and conference detai record (CODR)s. LAN Meeting Exchange exports CDRs across the network to a cient in rea-time. If you set this vaue, you must restart Meeting Exchange. OFF (defaut) Meeting Exchange does not automaticay generate rea-time CDRs and CODRs. You can configure this feature to process records in rea time. For more information, see Accessing records using a remote host on page 113 Specifies whether Meeting Exchange automaticay cears attended conference settings when a conference ends. Meeting Exchange generates a CODR and a Conference Report for a conference ony after that conference has been ceared. ON The system automaticay cears conference settings when the ast participant exits an attended conference. Settings ceared incude: Entry Tone, Exit Tone, ID, Lecture, Links, Lock, Music, Name, Note, Payback, Record, Security, and Time information. OFF (defaut) An operator must run the Conference Cear_a command in Bridge Tak to remove features from competed attended conferences. Note: Note: Meeting Exchange aways automaticay cears unattended conferences. 2 of 17 Apri

300 Finding parameters by name Tabe 58: System Configuration Parameters (continued) Parameter Attended ODO First Person Message Description Defines whether moderators can use their teephones to dia out to add participants to an active conference. This is usefu for contacting participants who cannot dia in. ON In an attended conference, a moderator can use Originator Dia Out (ODO), if there is a free channe configured for ODO Aow. OFF (defaut) In an attended conference, a moderator cannot use ODO. Meeting Exchange restricts ODO to one moderator at a time per conference. Specifies whether Meeting Exchange pays message 221; You are the first participant in this conference, when the first participant enters a conference. ON Meeting Exchange pays the message. OFF Meeting Exchange does not pay the message. 3 of Administering Meeting Exchange Servers

301 System configuration properties Tabe 58: System Configuration Parameters (continued) Parameter Auto Extend Duration Description Specifies whether Meeting Exchange attempts to automaticay extend the duration of in-progress unattended conferences for 25 additiona minutes. OnDefaut Meeting Exchange attempts to extend unattended conferences. Successfu extension depends on the avaiabiity of ines and security codes. Users can change this setting on a per-conference basis, using many of the Meeting Exchange booking appications. OffDefaut Meeting Exchange does not attempt to automaticay extend unattended conferences. Users can change this setting on a per-conference basis, using many of the Meeting Exchange booking appications. OFF (defaut) Meeting Exchange does not attempt to automaticay extend unattended conferences. Users cannot change this setting on a per-conference basis. Meeting Exchange attempts to extend a conference three additiona times after successfuy extending it the first time. This means that a conference can extend up to 100 minutes beyond its origina end time. If you enabe warning tones, each time Meeting Exchange pays a warning tone, it aso attempts to extend the conference, incuding one ast time just before the conference ends. If you do not enabe warning tones for unattended conferences, Meeting Exchange attempts to extend a conference one time just before a conference s end time. Meeting Exchange pays annunciator message 241 to inform participants that it has extended their conference; otherwise, the conference ends at the schedued end time. Note: Note: If your depoyment uses an Externa Passcode Vaidation (EPV) process, Auto Extend Duration is aways disabed. For more information on EPV, see Customizing the scheduer utiity on page of 17 Apri

302 Finding parameters by name Tabe 58: System Configuration Parameters (continued) Parameter Auto Extend Ports Eary Start Minutes Description Specifies whether Meeting Exchange can aocate additiona participant ports (ines) to unattended conferences whie they are in progress. OnDefaut Meeting Exchange attempts to aocate additiona ports to accommodate additiona conferees as required. Successfu aocation of ports depends on the avaiabiity of (non-reserved) ports. Users can change this setting on a per-conference basis, using many of the Meeting Exchange booking appications. OffDefaut Meeting Exchange does not attempt to aocate additiona ports. Users can change this setting on a per-conference basis, using many of the Meeting Exchange booking appications. OFF (defaut) Meeting Exchange does not attempt to aocate additiona ports. Users cannot change this setting on a per-conference basis. Note: Note: Fexfow conferences do not support Auto Extend Ports. Specifies whether participants can enter unattended conferences earier (1-30 minutes) than the schedued start time if ports are avaiabe. OFF (defaut) Participants cannot enter conferences earier than the schedued start time. 1-10, 15, 20, 25, 30 (minutes) Participants can enter conferences earier than the schedued start time. The setting specifies how eary participants can enter conferences. Note: Note: Two or more conferences may have conficting security codes if you enabe Eary Start Minutes and a User extends an earier conference. Meeting Exchange detects when a confict wi occur. As a resut, if Meeting Exchange detects a confict, Users cannot edit and save their reservation unti they change the conference start or end time. 5 of Administering Meeting Exchange Servers

303 System configuration properties Tabe 58: System Configuration Parameters (continued) Parameter Ignore DTMF Commands Operator Assistance Description Determines whether Meeting Exchange ignores DTMF commands entered by participants. ON Meeting Exchange ignores DTMF commands entered by participants. Meeting Exchange aso bocks hep requests when this feature is active. OFF (defaut) Meeting Exchange interprets a DTMF commands entered by participants. Note: Note: Fexfow conferences do not support Ignore DTMF Commands. Specifies whether operators provide hep to entire conferences or ony to the participant who requests hep. INDVL (defaut) The operator heps ony individua conferees who request hep. Meeting Exchange temporariy removes the participants from the conference to speak privatey with the operator. CONF The operator provides hep to the entire conference. Meeting Exchange does not remove anyone from the conference. A conferees hear whatever assistance is provided by the operator. Operators individuay hep participants requesting hep from muted ines, regardess of the setting. 6 of 17 Apri

304 Finding parameters by name Tabe 58: System Configuration Parameters (continued) Parameter Automatic Conf. ID Starting Conf. ID Description Specifies whether Meeting Exchange automaticay assigns IDs for unschedued attended conferences. CODRs and conference reports require Conference IDs. ON Meeting Exchange automaticay assigns a unique conference ID when the first participant enters a conference. Conference IDs faciitate conference tracking and et you generate CODRs and conference reports. OFF (defaut) Operators assign IDs using the Conference ID command. If an operator assigns an ID and Meeting Exchange aso assigns an ID, the operator s ID overrides the system-generated ID. Note: Note: In the case of schedued attended conferences, if you set Automatic Conf. ID parameter to OFF and the Startup Notify Time parameter to a non-zero vaue, Meeting Exchange ensures that the conference ID matches the confirmation number. This faciitates matching a conference reservation to the resuting CODR generated when the conference ends. Specifies the 12-digit starting number for system-assigned conference IDs. The defaut is The system increments IDs by 1 ( , , and so on). As with Automatic Conf. ID, if an operator assigns an ID and Meeting Exchange aso assigns an ID, the operator s ID overrides the system-generated ID. Unfortunatey, in the current reease, Meeting Exchange does not ink the Starting Conf. ID vaue to a bridgedb vaue caed NextConfirmNum. This absence of a ink can cause issues. When the Starting Conf. ID vaue differs from the vaue of NextConfirmNum in the database, you must update the Starting Conf ID vaue so that the database can see the changes. For exampe, if Starting Conf ID is set to on the System Configuration screen, but the NextConfirmNum is 8933 in bridgedb, you must: 1. Deete the reservations. 2. Edit the System Configuration s Starting Conf ID to (or any other vaue). 3. Save the changes 4. Edit the System Configuration s Starting Conf ID to Save the changes. 7 of Administering Meeting Exchange Servers

305 System configuration properties Tabe 58: System Configuration Parameters (continued) Parameter Moderator Lecture Payback Mute Sef Mute Sub Conferencing Mode Description Specifies whether moderators can mute a non-moderator ines. ON Moderators can mute a non-moderator ines and pace the conference in Lecture mode. Operator screens update to show that the conference is in Lecture mode, indicating that non-moderator ines within the conference are muted. This feature is not avaiabe during Q&A and Poing sessions. OFF (defaut) Moderators cannot mute ines for Lecture mode. Specifies whether Meeting Exchange mutes moderator ines during a recorded conference payback. ON Meeting Exchange mutes moderator ines during payback. OFF (defaut) Meeting Exchange does not mute moderator ines during payback. If you update this setting on a ive system, with a payback in progress, the update does not impact active conferences. Specifies whether participants can mute their own ines. If an operator mutes or unmutes a participant, this operator action aways overrides the participant mute status. If an operator mutes a ine, a participant cannot unmute it. OFF (defaut) No one can mute his own ine. Participant Conferees can mute their own ines. Anyone A participants, incuding moderators, can mute their own ines. Muted moderators retain a moderator privieges such as Lecture and moderator hang-up, but their audio input is not fed into a conference. Specifies whether a participant can create a sub-conference from a main conference by pressing *93 on their teephone keypad. If Meeting Exchange cannot fufi a sub-conference request, it pays message 24, This operation is currenty unavaiabe. ANYONE Any participant (conferees and moderators) can create a sub-conference. MODERATOR Ony a moderator can create a sub-conference. OFF (defaut) Sub-conferencing is disabed. 8 of 17 Apri

306 Finding parameters by name Tabe 58: System Configuration Parameters (continued) Parameter On-Hod Msg. Frequency Startup Notify Time Date Format Time Format Description Specifies whether Meeting Exchange pays the On Hod message (# 208) in the Enter queue and the frequency with which it pays the message. OFF (defaut) Meeting Exchange does not pay the On Hod message. 5, 10, 15,... 50, 55, 60 The interva, in seconds, after which Meeting Exchange pays the On Hod message. For exampe, if you specify 5, the message pays every 5 seconds. Specifies whether Meeting Exchange automaticay sets up schedued attended conferences and notifies operators for those conferences. OFF (defaut) Disabes startup. 0 Meeting Exchange starts the setup and sends notification messages at the conference s specified start time. 1, 2, 3, 4, 5, 10, 15, 20, 25, or 30 minutes The number of minutes before the conference s schedued start time that set up begins and messages are sent. Meeting Exchange checks for conferences that need setup at 1-minute intervas. Tip: Tip: If there are concurrent attended conferences with the same name, Bridge Tak ony dispays one of them. To ensure that Meeting Exchange dispays the fieds Contact Name, Contact Teephone, Schedued Participants, and Schedued Minutes in Conference Reports, you must enabe this fied. Specifies one of the foowing system date formats: US standard date format (defaut): mm/dd/yyyy An aternate format: yyyy/mm/dd Internationa format: dd/mm/yyyy Date Format has no effect on date formats in CDRs and CODRs. Specifies whether Meeting Exchange uses a 12-hour (defaut) or 24-hour cock format for a time references on the bridge, incuding system time, schedue times, and operator screens. Time Format has no effect on time formats in CDRs and CODRs. 9 of Administering Meeting Exchange Servers

307 System configuration properties Tabe 58: System Configuration Parameters (continued) Parameter PIN Mode Conference Passcode (Fexfow Ony) Save Roster Enabe Description Specifies PIN code requirements for unattended conferences schedued on the system. Optiona (defaut) Caers do not have to enter a PIN code, however they may enter one. They must press the pound key (#) in response to a PIN code prompt. Required Caers are required to enter a PIN code in response to a PIN code prompt. The PIN code does not have to be unique per participant, for exampe one PIN code per conference. Unique Required Caers are required to enter unique PIN codes (a unique PIN code for each caer). Important:! Important: This option is not avaiabe if PIN codes are not instaed. Aows for an additiona passcode that participants enter on their teephone keypad to join a Fexfow conference. A moderator creates the passcode using DTMF commands when starting the conference. Meeting Exchange does not save the passcode after the conference ends. This code is often caed a security code or a second eve passcode. You must configure this setting in order for the Fexfow conference attribute caed Security Code to operate successfuy. Specifies whether Meeting Exchange combines and saves the ro-ca audio fie. ON Meeting Exchange saves combined roster recordings for a conference to an audio fie in the system s /usr3/ savedroster directory. OFF (defaut) Meeting Exchange does not save an audio fie of roster recordings. 10 of 17 Apri

308 Finding parameters by name Tabe 58: System Configuration Parameters (continued) Parameter Bridge Record Phone Number Dia String Description Specifies whether Meeting Exchange records conference information on the bridge or to an externa device. On-bridge (defaut) The system records conference information to the bridge. Off-bridge The system records conference information to an externa device. In an Off-bridge depoyment, you must enter a vaue in the Phone Number and Dia String parameters. Note: Note: Typicay, conference recordings are stored on the usr3/confrp drive of the IBM 3650 M2. When you configure Meeting Exchange for Off-Bridge Recording and a User schedues a conference for a maximum of 10 participants, the conference can have either: 9 participants and an externa recording, or 10 participants and no externa recording. If you configure Bridge Record to Off-bridge and operators are using Bridge Tak Conference Scheduer, you must aso configure Bridge Tak Conference Scheduer to Off-bridge. If you do not configure Off-bridge recording in both ocations, Meeting Exchange defauts to On-bridge. Specifies the number to dia when Bridge Record is set to Off-bridge. This is the number of the externa recording device. The DTMF digits that Meeting Exchange sends to the externa recording device after the recorder answers the ca. Some of the information contained in the Dia String may be vendor specific. Some information may be derived at run time. Use these vaues in the string to specify run-time vaues: %P expanded at run time to contain the conference passcode. %T expanded at run time to contain conference start time in Linux time format (seconds since 1/1/1970). %C expanded at run time to contain conference confirmation number. For exampe, if you set the Dia String to *000#*%P#*%T#%C## and the foowing conference properties appy in your conference: The Passcode is 1234 The conference starts on Apri 3, 2010 at 9:58 AM The confirmation number is Under these conditions, Meeting Exchange sends the string *000#*1234#* #* ## to the externa recording device. 11 of Administering Meeting Exchange Servers

309 System configuration properties Tabe 58: System Configuration Parameters (continued) Parameter PreDia Deay Period Log User Transaction Short Jump Medium Jump Long Jump Description Designates number of seconds that Meeting Exchange waits before sending a Dia String to the externa recording device. The maximum setting is 50. Identifies whether Meeting Exchange ogs a of a caer s DTMF actions and the Meeting Exchange responses. OFF (defaut) Meeting Exchange does not create a User Transaction og. ON Meeting Exchange writes caer DTMF and the Meeting Exchange responses to a User Transaction og, which is a text fie. For more information on og fies, see Viewing Meeting Exchange information on page 107. During payback, users can move through the conference recording using rewind and forward options. By defaut, to rewind a payback by a short amount, users press 1 on their teephone keypad. By defaut, to forward a payback by a short amount, users press 3 on their teephone keypad. This parameter sets the number of seconds for that short amount. During payback, users can move through the conference recording using rewind and forward options. By defaut, to rewind a payback by a medium amount, users press 4 on their teephone keypad. By defaut, to forward a payback by a medium amount, users press 6 on their teephone keypad. This parameter sets the number of seconds for that medium amount. During payback, users can move through the conference recording using rewind and forward options. By defaut, to rewind a payback by a ong amount, users press 7 on their teephone keypad. By defaut, to forward a payback by a ong amount, users press 9 on their teephone keypad. This parameter sets the number of seconds for that ong amount. 12 of 17 Apri

310 Finding parameters by name Tabe 58: System Configuration Parameters (continued) Parameter Automatic Record A Secure Bocks Record Description Identifies whether Meeting Exchange records a conferences, regardess of the per-reservation setting. OFF (defaut) Meeting Exchange does not automaticay record a conferences. ON Meeting Exchange automaticay records a conferences. As an aside, at reservation time, operators and moderators can enabe two settings reating to recording: Operators, using the CRS Front End or Bridge Tak, and moderators, using the Web Porta, can enabe the automatic recording of a conference. If they enabe this feature, Meeting Exchange automaticay starts recording the conference as soon as participants begin to tak. Operators, using the CRS Front End or Bridge Tak, and moderators, using the Web Porta, can aso enabe moderator contro of the recording feature. If they enabe this feature, moderators can start and stop the conference recording. The defaut vaue is ON. For more information on creating reservations using CRS Front End, Bridge Tak, or the Web Porta, see the Using Meeting Exchange Guide. This guide is avaiabe on support.avaya.com. The vaue of Automatic Record A supersedes any reservation-specific settings. Identifies whether Meeting Exchange aows conference recording when a moderator secures, or ocks, the conference. ON (defaut) If a moderator ocks a conference, by pressing *7 on their teephone keypad, Meeting Exchange terminates any in-progress recording and does not aow the moderator to begin recording. OFF If a moderator ocks a conference, Meeting Exchange continues any in-progress recording and aows the moderator to begin recording. 13 of Administering Meeting Exchange Servers

311 System configuration properties Tabe 58: System Configuration Parameters (continued) Parameter Bridge Num Description This three digit number uniquey identifies the Meeting Exchange appication server, or bridge. The Meeting Exchange recording feature uses this number for a recording fienames. If Meeting Exchange automaticay names a recording, it uses the foowing conventions: <Conference Comfirmation Number>+<Bridge Num>+XXXX The vaue of XXXX grows sequentiay, as foows: If the operator or moderator stops and then restarts recording during the conference, Meeting Exchange increments the vaue of XXXX. Simiary, if a participants eave the conference and ater re-join, Meeting Exchange increments the vaue of XXXX. As an exampe, this scenario occurs when moderators use their on-demand conference for a weeky meeting. Meeting Exchange views this weeky recurring meeting as mutipe instances of a singe conference. If your depoyment consists of a number of appication servers, caed a muticabinet environment, there are impications for the automatic naming convention. Meeting Exchange encodes a recording fienames on a given bridge with the bridge number. This fact can be used to keep recordings from difference bridges from having name conficts if customers copy them to a common payback device. Conversey, if customers can guarantee that name conficts wi not occur due to other factors, such as configuring confirmation numbers to be unique across a recording source bridges, then customers can set the Bridge Num vaues to be the same on a bridges. In this scenario, users can pay muti-sourced fies from a singe-source payback. This scenario ony operates successfuy in a depoyment that incudes a CRS server. If there is no CRS server, you must set Bridge Num to a unique vaue on a servers. Avaya recommends consuting with your Avaya Support Representative for advice if your depoyment incudes a compex server environment. As an aside, operators and moderators can manuay specify the fiename of a conference recording. They can enter amost any digit string for this purpose but it must not start with zero. Automatic fienames aways start with zero. This fiename forms the XXXX portion of the compete recording fiename: <Conference Comfirmation Number>+<Bridge Num>+XXXX For more information, see Managing recordings on page of 17 Apri

312 Finding parameters by name Tabe 58: System Configuration Parameters (continued) Parameter DRP:Auto-gen fname Payback Ro Ca Singe Person (SP) 1st Period # of SP Subsequent Prompts SP Prompt Waiting Period Recite wrong passcode Description Identifies whether Meeting Exchange automaticay aocates a fiename to a conference recording when an operator or moderator manuay initiates a recording. ON (defaut) Meeting Exchange automaticay aocates a fiename to a conference recording. OFF Meeting Exchange does not automaticay aocate a fiename to a conference recording. Instead, operators manuay enter a fiename and moderators enter a DTMF string on their teephone keypad to represent the fiename. Identifies whether Meeting Exchange records users' names when they are in the payback cafow. For more information on the payback cafow, see Configuring the payback ca fow on page 144. OFF (defaut) Meeting Exchange does not prompt the user for their name during the payback cafow. ON Meeting Exchange prompts the user for their name during the payback cafow. Meeting Exchange adds the recording fiename to the ro ca fie and stores it in /usr2/pkbrosters. When Meeting Exchange detects that a singe participant is in the conference, this is the number of minutes that Meeting Exchange waits before paying a prompt requesting a DTMF digit to indicate that the conference shoud continue. The number of times that Meeting Exchange pays the prompt requesting a DTMF digit to indicate that the conference shoud continue. The number of minutes that Meeting Exchange waits after requesting a DTMF digit before paying subsequent prompts. Once it receives a DTMF digit, Meeting Exchange resets the timer to the Singe Person (SP) 1st period. If a caer enters an incorrect passcode, this setting determines if Meeting Exchange pays an error message that mentions the actua individua DTMF digits entered by the caer. OFF (defaut) Meeting Exchange pays an error message that states that the caer entered a wrong code. This message does not mention the actua digits. ON Meeting Exchange pays an error message that mentions the individua DTMF entries entered by the caer, so that the caer can recognize if they entered an incorrect code. 15 of Administering Meeting Exchange Servers

313 System configuration properties Tabe 58: System Configuration Parameters (continued) Parameter Country Code Interationa Prefix Loca Prefix Fex Leader Code NRP Seconds Web ID Length DTMF Conf Hangup Description These are three separate parameters. Meeting Exchange is configured to present its internationa prefix, country code, and oca prefix to support a "+" as part of Audio Consoe diaout with LDAP address book ook-up. You must enter the appropriate information for each parameter. Provides the option for a moderator to join a Fexfow conference when they enter a singe passcode instead of the defaut Fexfow requirement of two passcodes. ON - moderator joins conference upon entry of one code. This code must be unique. OFF - moderator must enter two codes to join a Fexfow conference. The # terminator after participants speak their name for the ro ca feature is optiona. The setting can be from 0 to Participants must press # after they state their name (defaut) Number of seconds that Meeting Exchange waits to automaticay pace ine into conference. Tip: Avaya Tip: recommends setting NRP Seconds to 3. Moderators can use DTMF commands to associate a Web conference with the audio conference. To associate a Web conference with an audio conference, moderators press *95 on their teephone keypad and enter the ID of the Web conference. This parameter represents the the number of digits that moderators can enter to associate a Web conference with the audio conference. The maximum vaue is 16. Determines if moderators can end their conference using the DTMF command ##. ENABLED - Moderators can press ## to end their conference. DISABLED - If moderators press ##, they cannot end the conference. 16 of 17 Apri

314 Finding parameters by name Tabe 58: System Configuration Parameters (continued) Parameter System aert Aert message Description Determines if Meeting Exchange shoud pay a message to a conferences. If enabed, Meeting Exchange pays the message before any per-conference messages. ON Meeting Exchange pays a message to a conferences. OFF (defaut) Meeting Exchange does not pay a message to a conferences. For more information, see Enabing system wide messages on page 159. If you set System aert to ON, you must specify which message that Meeting Exchange shoud pay to a conferences. There are 2000 message sots in each prompt set, so vaid vaues for this fied are of 17 Timed Assist configuration The time-sensitive operator hep feature aows you to estabish time-based rues for deivering operator hep to conference participants. In the event of a request for hep from a participant, you can configure Meeting Exchange to dia the operator, pace the participant on hod, or dia out to another teephone number. You can configure up to 49 rues. If a participant requests hep whie the conference is paying music and, after the hep intervention, the operator and participant both decide to return to the conference, the operator must turn off the music if they wish to speak to the conference participants. To configure time-sensitive operator hep settings: 1. As with navigating to the other parameters in this chapter, navigate to System Administrator Main > Configurations > Timed Assist Configuration. Meeting Exchange dispays the Timed Assistance screen. 2. On this screen, you can press the foowing keys: I or INSERT to insert a new rue. D to remove the seected rue. ENTER to edit the current rue The first rue on the Timed Assistance screen aways has the Data Type set to DEFAULT. Meeting Exchange uses this rue when none of the other rues appy. Athough you can configure the action of this rue, you cannot deete this rue. 314 Administering Meeting Exchange Servers

315 Voice Message configuration 3. Press I to add a configuration. Meeting Exchange dispays the Timed Assist Configuration screen. To enter a setting that passes midnight, for exampe 5:00 PM to 7:00 AM, you must create two rues, one as Start Time 5:00 PM and End Time 12:00 AM and the second as Start Time 12:00 AM and End Time 7:00 AM. 4. Enter data into the fieds. Tabe 59 describes the fieds. Tabe 59: Timed Assist Configuration diaog Fied Start Time End Time Date Type Action Code Action Setting Description The start for the time range in hour: minutes: [AM PM] The end for the time range in hour: minutes: [AM PM] DEFAULT, WEEKDAY, or WEEKEND Ony one action is aowed at one time. Therefore, time ranges for the same data type cannot overap. Seect WAIT_FOR_HELP, PLAY_MSG, or DIAL_OUT. Enter the action for the Code. For exampe, if the code is PLAY_MSG, enter the message record number. When the Code is DIAL_Out, enter the Phone number for the system to dia. The WAIT_FOR_HELP code does not require an action setting. 5. Press ESC and save your changes. Meeting Exchange saves configuration data to /dbase/admin/operatorhep.txt. Voice Message configuration You can configure Meeting Exchange to pay a tone, a voice message, or both to notify participants of conference events, provide instructions for conference functions, and announce how much time is eft in a conference. To configure tones and voice: 1. As with navigating to the other parameters in this chapter, navigate to System Administrator Main > Configurations > Voice Message Configuration. Meeting Exchange dispays the Voice Message Configuration screen. 2. Seect the appropriate option for each type of message isted on the screen. Tabe 60 ists each of the types of message. Tone Meeting Exchange sounds the currenty defined tone to indicate condition. Apri

316 Finding parameters by name Message Meeting Exchange pays a preassigned voice message (msg nnn) to indicate condition. For descriptions of voice messages, see Configuring audio messages on page 151. Both (defaut) Meeting Exchange sounds the tone and pays a preassigned voice message to indicate condition. Avaya recommends using Tone or Both when an immediate warning is required. The Message setting coud deay the warning message if a annunciators are busy when the condition requiring the warning occurs. The settings appy to every conference supported by Meeting Exchange. You do not have to reboot the system after changing settings. You can aso configure entry and exit tones on a per-conference basis using any of the Meeting Exchange booking appications. 3. Press ESC and save your changes. Tabe 60: Voice Message Configuration Parameters Fied ODO Messages Security On Security Off Conference Entry Conference Exit Security Code Error1&2 Security Code Error3 PIN Code Error1&2 PIN Code Error3 Warning Tone (15-1 mins) Warning Tone (0 mins) Description Payed when a moderator attempts to dia out to another teephone ine during a conference but Meeting Exchange is unabe to accomodate the request. Payed when an operator or moderator ocks a conference. Payed when an operator or moderator unocks a conference. Payed when a participant enters the conference. Payed when a participant eaves the conference. Payed when a participant enters an invaid conference passcode. Payed when a participant enters an invaid conference passcode and Meeting Exchange paces them in the queue for operator assistance. Payed when a participant enters an invaid PIN code. Payed when a participant enters an invaid PIN code and Meeting Exchange paces them in the queue for operator assistance. Payed at configurabe intervas to indicate that the conference is due to end soon. For more information, see Warning Tone configuration on page 317. Payed as the conference ends. 316 Administering Meeting Exchange Servers

317 Warning Tone configuration Warning Tone configuration You can specify how often warning tones sound during the ast 15 minutes of an unattended conference to notify participants that the conference is about to end. The warning tone is a 2-beep tone foowed by a 3-beep tone. It is important to note that you must enabe two additiona parameters in order to successfuy configure warning tones. These two additiona parameters are caed Auto Hang-up and Warning Tones. These parameters are ocated in the Conference Scheduer appication. The Conference Scheduer appication is a command ine utiity that Avaya provides to enabe you to configure a arge number of settings for conferences, such as how ong to retain conference records and the number of avaiabe ines for on-demand conferences. You can access the Conference Scheduer appication by ogging into Meeting Exchange as a dcbadmin and navigating to System Administrator Main Menu > Configure Scheduer. For more information on the Conference Scheduer appication, see Customizing the scheduer utiity on page 66. The vaues that you configure using the Conference Scheduer appication are goba vaues. By defaut, Meeting Exchange sounds warning tones at each of the foowing intervas before the conference is schedued to end: 15 minutes 10 minutes 5 minutes 4, 3, 2, 1 minutes unti the conference ends To configure the frequency with which warning tones are sounded: 1. As with navigating to the other parameters in this chapter, navigate to System Administrator Main > Configurations > Warning Tone Configuration. Meeting Exchange dispays the Warning Tone Configuration screen. 2. Seect Y or N under the minute number to specify when you want warning tones to pay. The changes do not impact in-progress conferences, which use the previous configuration. 3. Press ESC and save your changes. Apri

318 Finding parameters by name 318 Administering Meeting Exchange Servers

319 Appendix C: Supported management information bases (MIBs) Meeting Exchange 5.2 supports the foowing MIBs: Meeting Exchange MIB Core Services MIB Meeting Exchange Server Monitoring MIB Most of the traps generated by the system come from the Meeting Exchange MIB: AV-MX-S6200-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, enterprises FROM SNMPv2-SMI sysname FROM SNMPv2-MIB entphysicaassetid FROM ENTITY-MIB appsrvname FROM APPLICATION-MIB ipadentaddr FROM IP-MIB ItuPerceivedSeverity FROM ITU-ALARM-TC-MIB ituaarmadditionatext FROM ITU-ALARM-MIB csaarmseverity FROM AV-CORE-SERVICES-MIB; avmx6200mib MODULE-IDENTITY LAST-UPDATED " Z"-- 13 Oct 2008 ORGANIZATION "AVAYA" CONTACT-INFO "Avaya Customer Services Apri

320 Supported management information bases (MIBs) Posta: Avaya, Inc. 211 Mount Airy Rd Basking Ridge. NJ USA Te: WWW: DESCRIPTION "A MIB to support Meeting Exchange Groupware Edition S6200. Copyright (C) 2007 by Avaya Inc. A rights reserved." REVISION " Z" Oct 2008 DESCRIPTION "Revision X.X.X - For MX Bridge 5.2." ::= { avmx6200mibs 1 } The foowing are defined in AVAYA-GEN MIB -- avaya OBJECT IDENTIFIER ::= { enterprises 6889 } products OBJECT IDENTIFIER ::= { avaya 1 } mibs OBJECT IDENTIFIER ::= { avaya 2 } avmx6200prod OBJECT IDENTIFIER ::= { products 22 } avmx6200mibs OBJECT IDENTIFIER ::= { mibs 22 } Top eve components of this MIB -- avmx6200notifications OBJECT IDENTIFIER ::= { avmx6200mib 1 } -- Notification group 320 Administering Meeting Exchange Servers

321 avmx6200objects OBJECT IDENTIFIER ::= { avmx6200mib 2 } -- Objects Common Object groups for CoreServices MIB -- avmx6200notifyobj OBJECT IDENTIFIER ::= { avmx6200objects 1 } Core Services Notify group (csnotifyobj) -- avmx6200aarmseverity OBJECT-TYPE SYNTAX ItuPerceivedSeverity MAX-ACCESS read-ony STATUS current DESCRIPTION "Aarm severities are based on ITUPerceivedSeverity (RFC 3877)" ::= { avmx6200notifyobj 1 } MX Suite 5.0 Notifications -- avmx6200processstartednotification NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION Apri

322 Supported management information bases (MIBs) "This trap is generated when an Avaya Meeting Exchange process has been started." ::= { avmx6200notifications 101 } avmx6200processstoppednotification NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "This trap is generated when an Avaya Meeting Exchange process has been stopped." ::= { avmx6200notifications 102 } avmx6200reservedportpoousageincrease NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "This trap is generated when the number of used ports in the reserved port poo equas or exceeds the upper watermark configured for that poo providing the corresponding ower watermark has been crossed since the ast time this trap was generated." 322 Administering Meeting Exchange Servers

323 ::= { avmx6200notifications 103 } avmx6200reservedportpoousagedecrease NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "This trap is generated when the number of used ports in the reserved port poo fas beow the ower watermark configured for that poo providing the corresponding upper watermark has been crossed since the ast time this trap was generated." ::= { avmx6200notifications 104 } avmx6200unreservedportpoousageincrease NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "This trap is generated when the number of used ports in the unreserved port poo equas or exceeds the upper watermark configured for that poo providing the corresponding ower watermark has been crossed Apri

324 Supported management information bases (MIBs) since the ast time this trap was generated." ::= { avmx6200notifications 105 } avmx6200unreservedportpoousagedecrease NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "This trap is generated when the number of used ports in the unreserved port poo fas beow the ower watermark configured for that poo providing the corresponding upper watermark has been crossed since the ast time this trap was generated." ::= { avmx6200notifications 106 } avmx6200appicationserverfaiover NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "This trap is generated when the appication server fais over." 324 Administering Meeting Exchange Servers

325 ::= { avmx6200notifications 107 } avmx6200mediaserverfaied NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "This trap is generated when the media server does not respond." ::= { avmx6200notifications 108 } avmx6200serverrebooted NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "This trap is generated after the host server was rebooted." ::= { avmx6200notifications 109 } END The CPU Utiization and Disk Usage SNMP traps come from the Core Services MIB: cscpuutiization NOTIFICATION-TYPE Apri

326 Supported management information bases (MIBs) OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "CPU utiization is at east 80% (MINOR)." ::= { cscpunotifications 1 } csdiskusagethreshod NOTIFICATION-TYPE OBJECTS { sysname, ipadentaddr, entphysicaassetid, csaarmseverity, appsrvname, ituaarmadditionatext } STATUS current DESCRIPTION "Disk usage has exceeded 80% (MAJOR)" ::= { csdisknotifications 8 } 326 Administering Meeting Exchange Servers

327 Appendix D: Audio messages This appendix ists the Meeting Exchange messages that Avaya ship with Meeting Exchange 5.2. For more information on audio messages, see Configuring audio messages on page 151. Tabe 61: Meeting Exchange 5.2 Audio Messages Message Number Fiename Actua Words 0 0 Wecome. You have reached the audio conferencing system. After the tone, enter your conference passcode foowed by the pound key. Thank you After the tone pease state your name foowed by the pound key The foowing participants are in the conference I'm sorry. The "Dia Out" feature is currenty unavaiabe I'm sorry. Your conference is at capacity. Dia out cannot be performed I'm sorry. Dia out is not authorized at this time Conference security has been turned on Conference security has been turned off Someone has entered the conference Someone has eft the conference I'm sorry. You have entered an invaid passcode. Pease try again I'm sorry. You have entered an invaid passcode. Pease stay on the ine for the next avaiabe operator I'm sorry. You have entered an invaid PIN code. Pease try again I'm sorry. You have entered an invaid PIN code. Pease stay on the ine for the next avaiabe operator Your conference is schedued to end in 15 minutes Your conference is schedued to end in 14 minutes Your conference is schedued to end in 13 minutes. 1 of 16 Apri

328 Audio messages Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words Your conference is schedued to end in 12 minutes Your conference is schedued to end in 11 minutes Your conference is schedued to end in 10 minutes Your conference is schedued to end in 9 minutes Your conference is schedued to end in 8 minutes Your conference is schedued to end in 7 minutes Your conference is schedued to end in 6 minutes Your conference is schedued to end in 5 minutes Your conference is schedued to end in 4 minutes Your conference is schedued to end in 3 minutes Your conference is schedued to end in 2 minutes Your conference is schedued to end in 1 minute Your conference time has now expired. Thank you Thank you for your patience. Pease stay on the ine for the next avaiabe operator I'm sorry. Conference recording is not avaiabe I'm sorry. Conference payback is not avaiabe Pease enter your recording fie number foowed by the pound key or press star to cance Conference recording has stopped The recording fie number is Press 1 to begin the recording. Press 2 to re-enter the recording fie number or press star to cance Press 1 to begin the payback. Press 2 to re-enter the recording fie number or press star to cance Conference payback has stopped. 2 of Administering Meeting Exchange Servers

329 Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words I'm sorry. The recording fie number you have entered cannot be used. Pease enter a different recording fie number foowed by the pound key or press star to cance Conference recording has been turned on Conference payback has been turned on Enter the number of minutes to skip at the beginning of the payback foowed by the pound key or press star to cance payback You are currenty the ony participant in this conference There are currenty participants in your conference Roster payback is compete Pease enter the phone number that you wish to dia foowed by the pound key or press star to cance Dia out has been canceed The phone number you have entered is: Press 1 to make this ca. Press 2 to re-enter the phone number or press star to cance Your ca coud not be competed. The ine may be busy The seected conference is not currenty active. Pease check the schedued time and timezone This conference has been ocked by the moderator and entry is not aowed at this time. Pease contact the conference organizer for additiona information This conference has reached its maximum capacity. Pease contact the conference organizer for additiona information No digits have been detected Pease enter the biing code for this conference foowed by the pound or press star to cance The biing code entered for this conference is 3 of 16 Apri

330 Audio messages Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words Press 1 to accept, press 2 to change or press star to cance This conference wi end when the ast moderator hangs up This conference wi not terminate after the ast moderator hangs up This operation has been canceed This operation is currenty unavaiabe Your conference has been extended an additiona 25 minutes Heo. Your conference is about to begin. To join, press Heo. Your conference is about to begin. Pease enter your conference passcode foowed by the pound key Pease standby whie your participants are diaed Not enough ines are avaiabe to dia in a participants. Pease standby whie some participants are diaed. To determine the number of participants in the conference press star 8 when diaing has competed Your bast dia has competed Pease enter your pin code foowed by the pound key I'm sorry. You have entered an invaid passcode. Your ca wi be disconnected. Goodbye I'm sorry. You have entered an invaid PIN code. Your ca wi be disconnected. Goodbye The main conference is ocked. Entry is not aowed at this time. The moderator has been notified of your request. Pease standby A participant in sub-conference is requesting re-entry but this conference is currenty ocked. Pease unock conference to aow re-entry, Re-entry to the main conference is now aowed You are the ony moderator in this conference. Pease unock the conference before joining the sub-conference Your operator request has been canceed. 4 of Administering Meeting Exchange Servers

331 Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words I'm sorry. There are no operators currenty avaiabe Main Menu. To request operator hep press star 0. To dia out press star 1. To record the conference press star 2. To pay back a recording press star 3. To togge ecture mode press star 5. To mute or unmute your own ine press star 6. To togge security press star 7. To payback roster press star 8. To enter biing code press star 9 1. To bast dia a dia ist press star 9 2. To enter a sub-conference press star 9 3. To isten to the name of the recording press star 9 4. To enter your Web conference ID press star 9 5. To mute a ines, aowing them to unmute themseves, press star 9 6. To togge moderator hang-up press star 9 8. To end this ca now press pound pound. To pay this menu again press pound Main Menu. To request operator hep press star 0. To pay back a recording press star 3. To mute or unmute your own ine press star 6. To pay back roster press star 8. To enter a sub-conference press star 9 3. To enter your Web conference ID press star 9 5. To pay this menu again press pound zero You are entering a conference that is muted. To unmute just your ine press star I'm sorry the system did not detect any entry Pease enter the second biing code foowed by the pound key or press star to cance The second biing code for this conference is You have been added to the Q&A queue You have been removed from the Q&A queue Press 1 to accept or press 2 to change I m sorry. Recording fie numbers may not begin with zero Conference payback has been paused I'm sorry. The system is currenty busy. Pease try again ater Pease enter your conference reference number foowed by the pound key I'm sorry. You have entered an invaid conference reference number. Your ca wi be disconnected. Goodbye. 5 of 16 Apri

332 Audio messages Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words There are no recordings for this conference. Your ca wi be disconnected. Goodbye There are recordings avaiabe for this conference To access the conference recorded on day of month at January February March Apri May June Juy August September October November December The conference payback instructions are as foows Press any key to skip these instructions Press 1 to rewind 1 minute Press 4 to rewind 5 minutes Press 7 to rewind 20 minutes Press 3 to skip ahead 1 minute Press 6 to skip ahead 5 minutes. 6 of Administering Meeting Exchange Servers

333 Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words Press 9 to skip ahead 20 minutes Press 5 to pause or resume the payback Press star to stop payback and choose another recording You have reached the end of the payback. Press 1 to choose another recording any other key to disconnect Thank you for using the conference payback feature. Your ca wi be disconnnected. Goodbye Press Thank you Enter the area code and number foowed by the pound key. To cance this request and return to the conference press star You have entered To proceed with diaing press pound. To change this number press star is invaid. Pease enter the correct digits foowed by pound The foowing options are avaiabe once you press pound to begin diaing. To pace the participant in conference press star 1. To join the participant and continue diaing press star 2. To disconnect the ine press star 3. To disconnect the ine and continue diaing press star 4. To proceed with diaing press pound now I'm sorry your entry is invaid. Enter the vaid digits foowed by pound After joining the ca press star 2 to record your conference. For assistance press star 0. To start your conference press 1 now Defaut conference options. A changes made to the defaut options wi appy to active and future conferences with the exception of quick start. Changes to quick start wi appy to future conferences ony. 7 of 16 Apri

334 Audio messages Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words Main Menu. To change your 4 digit eader pin press 1. To configure participant name record and entry and exit announcement options press 2. To change quick start options press 3. To change auto-continuation option press 4. For an overview of different conference options press 9. To return to the previous menu press star I'm sorry. This feature is not enabed. Pease contact your system administator to change your eader PIN. Press star to return to the previous menu I'm sorry. This feature is not enabed Defaut options overview. Caers are prompted to record their name as they join a conference ca. At any time during the conference these names can be repayed privatey to any conference participant by pressing star 9. Quick start aows conferences to begin immediatey without waiting for the eader to arrive. Autocontinuation aows a conferences to automaticay continue after the eader disconnects. Entry and exit announcement options determine what wi be heard when participants join and eave the conference. Options incude, name announcements, entry and exit tones or sience Quick start is enabed. To disabe quick start press 1. To return to the previous menu press star Quick start is disabed. To turn on quick start press 1. To return to the previous menu press star Auto continuation is enabed. To turn off auto continuation press 1. To return to the previous menu press star Auto continuation is disabed. To turn on auto continuation press 1. To return to the previous menu press star Participant name record is enabed. To turn off participant name record press 1. To change conference entry and exit announcement options press 2. To return to the previous menu press star Participant name record is disabed. To turn on participant name record press 1. To change conference entry and exit announcement options press 2. To return to the previous menu press star. 8 of Administering Meeting Exchange Servers

335 Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words Participants wi be announced, when joining and eaving the conference, by tones. To seect name announce press 1. To seect tones press 2. To seect sience press 3. To return to the previous menu, press star Participants wi be announced, when joining and eaving the conference, by name. To seect name announce press 1. To seect tones press 2. To seect sience press 3. To return to the previous menu press star Participants wi not be announced when joining and eaving the conference. To seect name announce press 1. To seect tones press 2. To seect sience press 3. To return to the previous menu press star I'm sorry. Participant name record must be on to choose this option I'm sorry. Your entry is invaid You wi now be paced into conference. To mute your ine press star 6. To unmute press star You are the first participant. To mute your ine press star 6. To unmute press star To mute your ine press star 6. To unmute press star I'm sorry. Your entry is invaid. Enter the vaid digits foowed by pound Wecome to Avaya's "Instant Conference". Enter your conference passcode foowed by the pound key The conference has been ocked by the eader The conference has been unocked If you are the eader press star now Pease enter your eader PIN foowed by pound I'm sorry. This conference has been ocked by the eader. Pease hang up and contact your system administrator for assistance. Your ca wi be disconnected. Goodbye. 9 of 16 Apri

336 Audio messages Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words The foowing conference commands are avaiabe to the eader. To request an operator join your conference press star 0. To request an operator speak to you individuay press 0 0. To dia out press star 1. To record the conference press star 2. To change conference entry and exit announcement options press star 3. To ock the conference press star 4. To unock the conference press star 5. To mute your individua ine press star 6. To unmute your ine press star 7. To seect or deseect conference continuation after you disconnect press star 8. To hear a private ro ca of participants press star 9. To hear a private participant count press star pound. To mute a ines except the eader press pound pound. To unmute a ines press 9 9. To join a sub-conference press 9 3. To hear the recording fiename press 9 4. To end the conference press The foowing conference commands are avaiabe. To request an operator join your conference press star 0. To request an operator speak to you individuay, press 0 0. To mute your ine press star 6. To unmute your ine press star 7. To hear a private ro ca of participants press star 9. To hear a private participant count press star pound. To join a sub-conference press You are now muted You are no onger muted The conference is muted The conference is unmuted I'm sorry. That entry is invaid. Pease stay on the ine for the next avaiabe operator I'm sorry. This feature is disabed The foowing participants are in the conference has joined the conference has eft the conference Your request wi be answered by the next avaiabe operator. To cance your request press star Your operator request has been canceed To change conference entry and exit announcement options press 2. To return to conference press star. 10 of Administering Meeting Exchange Servers

337 Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words The conference wi be aowed to continue after you disconnect. To set the conference to end when you disconnect press star The conference wi end when you disconnect. To aow the conference to continue after you disconnect press star You wi now be paced into conference. To mute your ine press star 6. To unmute press star The eader has not arrived yet. Pease standby To start recording the conference press 1. To cance press star Pease standby whie your recording connection is estabished. To cance the recording press star The conference is now being recorded Press 1 to stop recording. Press 2 to pause or resume recording. Press 3 to hear the recording fie number or press star to cance The conference is no onger being recorded After the tone state your name foowed by the pound key I'm sorry. No ine is avaiabe for Dia Out TONE - Note: This fie contains 2 short beeps and doesn't require professiona recording I'm sorry. The passcode you have entered is invaid. Pease stay on the ine for the next avaiabe operator I'm sorry. The eader PIN is invaid. For assistance pease contact your service provider An operator is requesting to join your ocked conference. To aow operator entry press star 5 to unock your conference This is a quick start conference Pease enter your new eader PIN foowed by the pound key. The eader PIN must be to digits. To return to the previous menu press star Your new eader PIN is 11 of 16 Apri

338 Audio messages Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words I'm sorry. The eader PIN must be between and digits ong. Pease re-enter your eader PIN foowed by pound To skip entering a conference passcode press star now. If you have a conference passcode pease enter it now foowed by the pound key. The passcode may be 4 to 9 digits ong A conference passcode wi not be required for this conference Your conference passcode is To change this entry press star now Pease enter the conference passcode foowed by pound I'm sorry. The conference passcode must be between 4 and 9 digits ong. Pease re-enter your passcode foowed by the pound key Pease enter the conference passcode foowed by the pound key I'm sorry. The conference passcode you have entered is not correct. For assistance pease contact your conference organizer Pease enter the biing code for this conference foowed by pound You wi now be disconnected by the eader The phone number you entered is not aowed at this time This conference has been secured by the eader and entry is not aowed at this time. Your ca wi be disconnected. Goodbye I'm sorry. We did not get your name. After you state your name pease press the pound key Your ca wi now begin. For operator assistance any time during your ca press star 0. To mute your ine press star 6. To unmute press star 7. For more information press star star Recording You are being paced into a conference in muted mode. 12 of Administering Meeting Exchange Servers

339 Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words To stop the recording press star An operator is requesting to join your ocked conference. To aow operator entry press star 7 to unock your conference I'm sorry. We did not get your name. Pease standby for an operator Pease seect the sub-conference you wish to join by pressing a digit between 1 and 9. You may aso press zero to go back to the main conference or press star to cance The sub-conference number you have entered is invaid. You wi now to returned to your conference The sub-conference number you have entered is invaid A moderator has requested for everyone to re-join the main conference. You wi now be transferred back to the main conference Sub-conference is currenty ocked. A participant from another sub-conference is trying to enter this sub-conference. Press 1 to unock sub-conference or press star to cance The main conference is currenty ocked. A participant from a sub-conference is requesting re-entry. Press 1 to unock the main conference or press star to cance has been ocked by the moderator and entry is not aowed at this time. A moderator has been notified of your request. Pease standby Everyone has been moved back to the main conference. Pease re-join the main conference now by pressing star Entry to the sub-conference you were trying to join is now aowed I'm sorry. The conference you were trying to join cannot be unocked at this time Pease enter 1 through 9 to join a sub-conference. Press 0 to go back to the main conference. Press pound to return a participants to the main conference or press star to cance. 13 of 16 Apri

340 Audio messages Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words Your conference is currenty ocked. An operator is unabe to assist you. Press 1 if you want to unock your conference and request hep. Press star if you want to cance the hep request Your conference is in the hep queue. If you ock it an operator wi be unabe to assist you. Press 1 if you want to ock your conference and be removed from the hep queue. Press star if you want to cance this request and remain in the hep queue Your conference is currenty ocked. An operator is unabe to assist you The conference fie number is Pease hod whie an assistant is diaed. After the assistant joins press star 2 to add the assistant to your conference or press star 3 to hang-up the assistant and return to your conference I'm sorry. An assistant cannot be reached at this time. Pease try again ater. You wi now be returned to your conference This is a secure conference. The option to add an assistant to the conference is not avaiabe at this time Pease hod whie an assistant is diaed. Press star 2 to hang-up the operator at any time I'm sorry. An assistant cannot be reached at this time. Pease try again ater. Your ca wi be disconnected. Goodbye I'm sorry. Conference recording was unabe to start Pease press any key to remain in conference Virtua ink ine Someone has joined the conference via a Virtua ink ine Someone has eft the conference. Virtua ink ine Virtua ink ine has entered the conference Virtua ink ine has eft the conference Conference gain is on Conference gain is off Pease standby for operator hep. 14 of Administering Meeting Exchange Servers

341 Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words The conference is in ecture mode The conference is no onger in ecture mode Your eader PIN has expired and must be changed now Your eader PIN wi expire in days. To change your eader PIN press 1. To keep your current eader pin and continue press day. To change your eader PIN press 1. To keep your current eader pin and continue press Your new eader PIN must be different from the current eader PIN digits There was a system error when trying to update your eader PIN. Your eader PIN has reverted back to I'm sorry. The biing code entered is invaid. Your ca wi be disconnected. Goodbye The number of participants is beow the minimum required. The ca wi be disconnected if more participants do not join The conference wi now be disconnected Pease enter your second biing code foowed by pound Wecome to the conference wecome message recording faciity Press 1 to record or press any other key to exit Press 1 to record, press 2 to pay, press 3 to deete, or press any other key to exit Pease record the message after the tone foowed by the pound key The message has been successfuy deeted The biing code entered is invaid Pease enter your unique Participant Identifier foowed by the pound key. 15 of 16 Apri

342 Audio messages Tabe 61: Meeting Exchange 5.2 Audio Messages (continued) Message Number Fiename Actua Words Sorry. You have entered an invaid unique participant identifier. Pease try again Sorry. You have entered an invaid unique participant identifier. Pease disconnect now. Thank you Sorry. You have entered an invaid unique participant identifier. Pease stay on the ine for next avaiabe operator Pease enter your Secret PIN foowed by the pound key I'm sorry. You have entered an invaid secret PIN. Pease try again I'm sorry. You have entered an invaid Secret PIN. Your ca wi be disconnected. Goodbye I'm sorry. You have entered an invaid secret PIN. Pease stay on the ine for the next avaiabe operator Conference is in sient mode. To unmute yoursef Press * Conference recording is currenty paused 16 of Administering Meeting Exchange Servers

343 Appendix E: Dua Tone Muti-Frequency (DTMF) commands This chapter ists the defaut keypad codes which participants enter on their teephone keypad to attend and participate in reguar conferences. This chapter aso ists the defaut keypad codes which participants enter to isten to conference recordings. When attending and participating in conferences, moderators can access a arger number of options than conferees. When istening to conference recordings, moderators and conferees have access to the same options. For the purposes of DTMF mappings, Meeting Exchange 5.2 effectivey supports two different conference types. These conference types are commony caed scan conferences and fexfow conferences. The conference recording payback options are the same for both conference types. For fexfow conferences, moderators are often caed eaders. For more information about configuring teephone numbers, or DDIs, for scan and fexfow conferences and payback, see Configuring ca branding on page 44. Scan conferences Fexfow conferences Commands for paying back a recording Scan conferences The scan conference DTMF sequence uses the sfowdigits.reg configuration fie. It is important to note that some mappings are not configurabe. For more information, contact your Avaya Support Representative. If you make any changes to the defaut DTMF mappings, you must ensure that you aso configure the audio prompt messages to pay the correct message. For more information, see Audio messages on page 327. Typicay, scan conferences are reguar conferences in which the participants enter a moderator passcode or a conferee passcode on their teephone keypad to access the conference. Moderator commands Conferee commands Apri

344 Dua Tone Muti-Frequency (DTMF) commands Moderator commands Tabe 62 ists the moderator teephone keypad commands for scan conferences. Tabe 62: Moderator Commands Press... To... *0 Request hep by entering the Hep Requests queue. As a system administrator, you can configure this feature to pay a message, to connect to an operator with audiopath capabiities, or to connect to an assistant without audiopath capabiities. *8 Pay the number of conference participants, foowed by a ro ca of conference participants when used in conjunction with the name record/ payback feature. If there is no ro ca, this command simpy pays the number of conference participants. If there is no ro ca, Meeting Exchange aways pays this message as a private message. When you enabe ro ca: - If a conferee presses *8, Meeting Exchange pays this message as a private message. - If a moderator presses *8, Meeting Exchange can pay this message as a private message or as a conference message, depending on how you configure NRP. You can set NRP to CONF or INDIVIDUAL. *1 Initiate a dia out. Once a moderator enters *1 on their teephone keypad, the moderator wi be paced into a sef-expanatory Interactive Voice Response (IVR) sequence for requesting, coecting, and diaing a teephone number. Once the teephone ca has been made, Meeting Exchange makes the foowing options avaiabe: *2 Returns both moderator and caer to the conference. *3 Returns moderator to the conference and hangs up the caed party. *2 Enter the conference recording menu. If Meeting Exchange is not currenty recording the conference, it pays the options for starting a recording session. If Meeting Exchange is currenty recording the conference, it pays the foowing options: 1 Ends the recording. 2 Togges the pause/resume feature. 3 Repays a conference recording fie number. * Exits the menu. 1 of Administering Meeting Exchange Servers

345 Scan conferences Tabe 62: Moderator Commands (continued) Press... To... *3 Enter a payback menu, which enabes the moderator to pay a conference recording to the entire conference. Meeting Exchange 5.2 now contains a new method for paying a conference recording. This oder DTMF command is a egacy feature, which pays the conference recording to the entire conference. Additionay, this oder payback feature does not support pause and resume. For more information on the new functionaity, see Commands for paying back a recording on page 353. *5 Turn Lecture on or off. Meeting Exchange paces a participant ines in mute. Participants cannot unmute their individua ines whie in ecture mode. *6 Mute or unmute the teephone ine. *96 Turn Mute A on or off. When a conference is in mute-a mode, a current participants are paced into muted mode. In addition, any new participants join the conference in muted mode. When a moderator unmutes a conference, a current participants remain in muted mode unti they press *6 on their teephone keypad. However, any new participants join the conference in unmuted mode. *7 Turn conference security on or off. ## End the conference. *91 Enter a biing code. Meeting Exchange pays a message which prompts the moderator for a biing code for the conference. *92 Trigger an unattended, automatic Bast Dia or rebast. For the successfu operation of this command, the operator, using Bridge Tak or CRS Front End, or the moderator, using Web Porta, must enabe Bast Dia for the conference. 2 of 3 Apri

346 Dua Tone Muti-Frequency (DTMF) commands Tabe 62: Moderator Commands (continued) Press... To... *93 Start a subconference or join a subconference. Once a moderator enters *93 on their teephone keypad, Meeting Exchange makes the foowing options avaiabe: 1-9 Paces the moderator into a subconference room. For exampe, if a moderator presses 7, Meeting Exchange paces them into subconference number 7. Note: Note: If the moderator presses the current subconference number, Meeting Exchange ignores the command. 0 Returns the moderator to the main conference. # Pays a warning message into a subconferences to indicate that participants wi be rejoining the main conference shorty. After a few moments, Meeting Exchange transfers a ines back to the main conference. * Does nothing. It exits this menu. *94 Repay the ast or current conference recording fie number. *95 Associate a Web conference with the audio conference. *98 Togge moderator hang-up. This sequence turns on or turns off the moderator hang-up option. If a conference has moderator hang-up enabed, Meeting Exchange coses the conference when the ast moderator eaves the conference. If a conference does not have moderator hang-up enabed, Meeting Exchange does not cose the conference when the ast moderator eaves the conference. 1 Leave a Q&A queue. Meeting Exchange paces moderators in the Q&A queue, by defaut. #2 Record a persona greeting for the conference. Once a moderator enters #2 on their teephone keypad, Meeting Exchange makes the foowing options avaiabe: 1 Records a greeting. 2 Pays the current greeting. 3 Deetes the current greeting. 3 of Administering Meeting Exchange Servers

347 Scan conferences Conferee commands Tabe 63 ists the conferee teephone keypad commands for scan conferences. Tabe 63: Conferee Commands Press... To... *0 Request hep by entering the Hep Requests queue. As a system administrator, you can configure this feature to pay a message, to connect to an operator with audiopath capabiities, or to connect to an assistant without audiopath capabiities. *6 Mute or unmute the teephone ine. *8 Pay the number of conference participants, foowed by a ro ca of conference participants when used in conjunction with the name record/payback feature. If there is no ro ca, this command simpy pays the number of conference participants. If there is no ro ca, Meeting Exchange aways pays this message as a private message. When you enabe ro ca: - If a conferee presses *8, Meeting Exchange pays this message as a private message. - If a moderator presses *8, Meeting Exchange can pay this message as a private message or as a conference message, depending on how you configure NRP. You can set NRP to CONF or INDIVIDUAL. *93 Start a subconference or join a subconference. Once a conferee enters *93 on their teephone keypad, Meeting Exchange makes the foowing options avaiabe: 1-9 Paces the conferee into a subconference room. For exampe, if a conferee presses 7, Meeting Exchange paces them into subconference number 7. Note: Note: If the conferee presses the current subconference number, Meeting Exchange ignores the command. 0 Returns the conferee to the main conference. *1 Enter a Q&A queue. Once a conferee enters *1 on their teephone keypad, Meeting Exchange makes the foowing option avaiabe: 1 removes the conferee from the Q&A queue. Apri

348 Dua Tone Muti-Frequency (DTMF) commands Fexfow conferences The fexfow conference DTMF sequence uses the fexfow_cfg.reg configuration fie. For more information, contact your Avaya Support Representative. Typicay, fexfow conferences are conferences in which a participants enter a conferee passcode on their teephone keypad. After entering a conferee passcode, moderators can enter a moderator passcode to promote their status. There are other keypad commands in the fexfow_cfg.reg fie but they are within comment tags. When you upgrade Conferencing, the upgrade script does not make any changes to the existing fexfow_cfg.reg fie. When you insta a new instance of Conferencing, the instaation script paces the new fexfow_cfg.reg fie in usr/dcb/dbase/admin. The new fexfow_cfg.reg fie contains a the atest keypad commands, incuding some within comment tags, such as ToggeMuteIndividua. If you want to enabe any commands which are not the defaut commands, you must modify the fexfow_cfg.reg fie for new instaations and upgrades. For exampe, if you require *6 for ToggeMuteIndividua, you must add it to the togge ine and remove it from the expicit Mute ine. If you make any changes to the defaut mappings, a program caed /usr/dcb/bin/ fexdigits is a usefu utiity to test your customized fexfow_cfg.reg before you pace the new settings into a ive environment. To test your configuration changes, enter the fie name after the utiity. For exampe: usr/dcb/bin/fexdigits testfexfow_cfg.reg This program parses the input fie and reports any errors. If you make any changes to the defaut DTMF mappings, you must ensure that you aso configure the audio prompt messages to pay the correct message. For more information, see Audio messages on page 327. Moderator commands Conferee commands 348 Administering Meeting Exchange Servers

349 Fexfow conferences Moderator commands Tabe 64 ists the defaut moderator teephone keypad commands for fexfow conferences. t Tabe 64: Moderator Commands Press... To... *0 Dispay the conference in the hep request queue. Once the conference enters this queue, an operator, using Bridge Tak can see that the conference requires assistance. This feature requires operator support. 00 Dispay an individua teephone ine in the hep request queue. Once moderators enter this queue, an operator, using Bridge Tak can see that they require assistance. This feature requires operator support. *1 Initiate a dia out. Once a moderator enters *1 on their teephone keypad, the moderator is paced into a sef-expanatory Interactive Voice Response (IVR) sequence for requesting, coecting, and diaing a teephone number. Once the teephone ca has been made, Meeting Exchange makes the foowing options avaiabe: *1 Return to the conference with the caed party. *2 Return to the conference without the caed party. *3 Deposit the caed party into the conference and stay in the IVR sequence to make another ca. *4 Hang-up that ca and and stay in the IVR sequence to make another ca. *2 Enter the conference recording menu. If Meeting Exchange is not currenty recording the conference, it pays the options for starting a recording session. If Meeting Exchange is currenty recording the conference, it pays the foowing options: 1 Ends the recording. 2 Togges the pause/resume feature. 3 Repays a conference recording fie number. * Exits the menu. *3 Enter an IVR sequence to change entry and exit tones and announcements. *4 Turn conference security on. This sequence ocks the conference. *5 Turn conference security off. This sequence unocks the conference. 1 of 3 Apri

350 Dua Tone Muti-Frequency (DTMF) commands Tabe 64: Moderator Commands (continued) Press... To... *6 Mute the teephone ine. *7 Unmute the teephone ine. *8 Togge between two options, as foows: The conference wi continue after the moderator eaves. The conference wi end when the moderator eaves. This option is simiar to the moderator hang-up option in the scan conference ca fow. *9 Pay an avaiabe ist of participant names into the teephone ine. ## Turn Mute A on. Meeting Exchange mutes a conferee ines in the conference. Conferees can unmute their individua ines whie in mute a mode. 99 Turn Mute A off. Meeting Exchange unmutes a conferee ines in the conference. *# Pay the number of participants. ** Pay a menu which ists the avaiabe DTMF teephone keypad sequences and their associated functions. To read the message text, see 339 on page End the conference. This DTMF sequence ends the conference if a parameter caed DTMF Conf Hang Up is configured on the Meeting Exchange appication server. For more information, see DTMF Conf Hangup on page of Administering Meeting Exchange Servers

351 Fexfow conferences Tabe 64: Moderator Commands (continued) Press... To Start a subconference or join a subconference. Once a moderator enters *93 on their teephone keypad, Meeting Exchange makes the foowing options avaiabe: 1-9 Paces the moderator into a subconference room. For exampe, if a moderator presses 7, Meeting Exchange paces them into subconference number 7. Note: Note: If the moderator presses the current subconference number, Meeting Exchange ignores the command. 0 Returns the moderator to the main conference. # Pays a warning message into a subconferences to indicate that participants wi be rejoining the main conference shorty. After a few moments, Meeting Exchange transfers a ines back to the main conference. * Does nothing. It exits this menu. 94 Repay the ast or current conference recording fie number. 95 Associate a Web conference with the audio conference. #2 Record a persona greeting for the conference. Once a moderator enters #2 on their teephone keypad, Meeting Exchange makes the foowing options avaiabe: 1 Records a greeting. 2 Pays the current greeting. 3 Deetes the current greeting. 2 At the start of a conference, after the moderator enters their conferee passcode and then upgrades their status with a moderator passcode, they can press 2 to enter an IVR sequence that enabes them to make changes to their conference properties. A changes made to the defaut conference properties wi appy to active and future conferences with the exception of quick start. For more information, see 309 on page 333. Once in this menu: Press: 1 to enter an IVR sequence to change the moderator, or eader, passcode. 2 to change the conference entry and exit tones. 3 to change the settings in reation to quick start, which reates to whether the conference begins when the first conferee arrives or when the first moderator arrives. 4 to change the settings in reation to conference cosure. 9 to hear an expanation of each of these conference properties. For more information, see 313 on page of 3 Apri

352 Dua Tone Muti-Frequency (DTMF) commands Conferee commands Tabe 65 ists the defaut conferee teephone keypad commands for fexfow conferences. t Tabe 65: Conferee Commands Press... To... *0 Dispay the conference in the hep request queue. Once conferees enter this queue, an operator, using Bridge Tak can see that the conference requires assistance. This feature requires operator support. 00 Dispay an individua teephone ine in the hep request queue. Once conferees enter this queue, an operator, using Bridge Tak can see that they require assistance. This feature requires operator support. *6 Mute the teephone ine. *7 Unmute the teephone ine. *9 Pay an avaiabe ist of participant names into the teephone ine. *# Pay the number of participants. ** Pay a menu which ists the avaiabe DTMF teephone keypad sequences and their associated functions. To read the message text, see 339 on page Start a subconference or join a subconference. Once a conferee enters *93 on their teephone keypad, Meeting Exchange makes the foowing options avaiabe: 1-9 Paces the conferee into a subconference room. For exampe, if a conferee presses 7, Meeting Exchange paces them into subconference number 7. Note: Note: If the conferee presses the current subconference number, Meeting Exchange ignores the command. 0 Returns the conferee to the main conference. # Pays a warning message into a subconferences to indicate that participants wi be rejoining the main conference shorty. After a few moments, Meeting Exchange transfers a ines back to the main conference. * Does nothing. It exits this menu. 352 Administering Meeting Exchange Servers

353 Commands for paying back a recording Commands for paying back a recording Tabe 66: Moderator and Participant Commands To pay back a recording, dia the dedicated payback ine and enter the conference passcode Once a participant dias the specia payback ine and enters the conference passcode on their teephone keypad, they are paced into a sef-expanatory IVR sequence for vaidating conference security information, isting fies which are avaiabe for payback, and coecting information for identifiying the caer s fie choice. Once the payback of the chosen fie begins, Meeting Exchange makes the foowing options avaiabe: 1 Rewinds the payback by a sma amount. 4 Rewinds the payback by a medium amount. 7 Rewinds the payback by a arge amount. 3 Forwards the payback by a sma amount. 6 Forwards the payback by a medium amount. 9 Forwards the payback by a arge amount. 5 Togges the start/stop feature. * Returns to the start of the payback menu. For more information on configuring the rewind and forward jumps, see Configuring recording properties on page 142. Apri

354 Dua Tone Muti-Frequency (DTMF) commands 354 Administering Meeting Exchange Servers

355 Appendix F: Feature List Tabe 67 dispays the ist of features that are currenty avaiabe on Meeting Exchange. Avaya enabes a number of features, by defaut. You can enabe or disabe the features which you require for your depoyment, using the featcfg command. For exampe: To enabe the Digita Record and Payback (DRP) feature: /usr/dcb/bin/featcfg +drp service mx-bridge restart For more information on DRP, see Configuring recording on page 141. You must restart the server if you make any changes to the feature ist. See Enabing features on page 43 for more information. Tabe 67: Feature Configuration Feature Name Feature Aias Description Do Avaya charge for it? Instaed by Defaut? A-aw Audio Encoding A_aw UK ony Now obsoete. Conference Scheduer sched Enabes the conference scheduer. No Yes Loca Area Network an Enabes connection to a LAN if a LAN card and LAN drivers are instaed. No Yes DNIS/Fexibe Annunciators dnis Enabes the bridge to process DNIS digits and pay a avaiabe annunciators. No Yes Digita Conference Record Payback drp Enabes operators to record conference diaogue to and payback recordings. No No 1 of 4 Issue 1 Apri

356 Feature List Tabe 67: Feature Configuration (continued) Feature Name Feature Aias Description Do Avaya charge for it? Instaed by Defaut? State of Texas stye ODO sodo Enabes DTMF input. Now obsoete. Warning Messages msg Enabes voice messages. PIN codes pins Enabes PIN codes. No No Line Overbooking Scheduer API Aternate Termination Tone Gain Modification Number of Logins Moderator Contro API Bridge Name in CDR Q&A (instaed by defaut) Poing (instaed by defaut) overbook schapi att gain ogins x (where x is the number of ogins) modapi bridge qa po Enabes scheduer overbooking. Enabes Conference Scheduer interface. Enabes aternate touch tones. Note: Does not appy to Fex Fow. Setting for bridges instaed in the United Kingdom ony Setting for the maximum number of ogins and is set to 255. Enabes moderator interface. Enabes incusion of bridge name in CDR and CODR fies. Enabes question and answer conference feature. Enabes poing conference feature. No No No No Now obsoete. No No No No No Yes No Yes No Yes Yes Yes Yes Yes 2 of Administering Meeting Exchange Servers

357 Tabe 67: Feature Configuration (continued) Feature Name Feature Aias Description Do Avaya charge for it? Instaed by Defaut? Muti-Bridge Contro System mbcs Enabes muti-bridge contro feature. No Yes Line Fauting faut Enabes ine fauting. Now obsoete. Disconnect Mode disconnect Enabes disconnect mode. No No CDR End Date cdr_end Enabes the system to generate a CDR or a CODR for a conference on the end date rather than the start date when a conference extends past midnight (into the next day). No No Externa Passcode Vaidation (EPV) from an externa database epv Enabes EPV feature. Not appicabe in this reease. No Unattended Bast ubast Enabes moderators to initiate bast dias. No No SNMP snmp Enabes impementation of the SNMP agent. Yes No Hide Scheduer hidesched Sets a fag that requests that BridgeTak hide/ disabe the Conference Scheduer interface (front end). No No Pubic Switched Teephone Network pstn Enabe PSTN features No Yes 3 of 4 Issue 1 Apri

358 Feature List Tabe 67: Feature Configuration (continued) Feature Name Feature Aias Description Do Avaya charge for it? Instaed by Defaut? Fex ca fow fex Enabe the Fex ca fow. No No NRP Operator Ony Mode nrpoper Turns on the abiity to schedue a conference with Name Record/Pay Operator Mode. This Mode prompts participants to record information that ony the operator may pay back. Aso turns on the abiity to turn on the Saved Roster Enabe in the dcbadmin System Configuration Screen. T3 Transport t3 Now obsoete. No No 4 of Administering Meeting Exchange Servers

359 Appendix G: Configuration changes that require a reboot or a restart This appendix ists the Meeting Exchange configuration changes that require a reboot or a restart. A point of carification: A restart takes approximatey 60 seconds and invoves stopping and restarting the appication server, or bridge, processes. A reboot takes onger and invoves stopping and restarting a Meeting Exchange servers and appications. A reboot can take severa minutes. Many peope refer to a reboot as powering down the system. For more information, see Rebooting or powering down Meeting Exchange on page 360. The foowing configuration changes require either a reboot or a restart: 1. Any changes to featcfg require a restart. For more information, see Feature List on page Any changes to FDAPI require a restart. For more information, see Configuring server resources on page Any changes in the /usr/picb/config directory require a restart. The fies incude: - Aarm, ogging, and SNMP fies. For more information, see Configuring SNMP on page System.cfg. For more information, see Configuring the system settings on page softmediaserver.cfg. For more information, see Configuring the media settings on page proxyconfigtabe.cfg. For more information, see Connecting to an SES proxy on page Mxmonitor.reg. For more information, see Connecting to an SES proxy on page Changes to the foowing network configuration fies require a reboot: - Changes to IP addresses - Changes to subnet masks - Changes to the defaut gateway - Changes to NTP - Changes to hostnames - Changes to network interface settings For more information on these tasks, see Customizing the server IP on page 37. Issue 1 Apri

360 Configuration changes that require a reboot or a restart 5. Changes to sfowdigits.reg that modify the DTMF commands for the SCAN ca fow require a restart. For more information, see Dua Tone Muti-Frequency (DTMF) commands on page Changes to fexfow_cfg.reg that modify the DTMF commands for FLEX fow require a restart. 7. Any changes to chdbased.reg require a restart. This fie contains the settings for the Externa Passcode Vaidation (EPV) feature. 8. Changes to the timezone, using the tzset command require a reboot. For more information, see Configuring the system timezone on page Changes to NFS configuration require a restart. For more information, see Figure 17. Rebooting or powering down Meeting Exchange This task does not require root access to the system. Customers can carry out this task. This procedure takes approximatey 15 to 20 minutes. 1. Open a PuTTY session. 2. Log in to the Meeting Exchange appication server as a dcbmaint user. For more information about the dcbmaint user eve, see A short note about sign-ins on page Seect System Shutdown from the System Maintenance Main Menu. 4. Type YES. The system dispays a message that it is shutting down. 5. Leave the system aone for 5 minutes. 6. Power down. The Power On/Off switch turns the system on and shuts the system off. The Reset button initiates a power-off/power-on cyce. 7. Leave the system aone for 5 minutes. 8. Power Up. The system wi take 5-8 minutes to become ive again. 9. Check for aarms and check ogs for any probems. Some systems may not go ive on the first Power up attempt. If this happens, repeat the shutting down procedure. 360 Administering Meeting Exchange Servers

361 Appendix H: List of softmediaserver.cfg parameters For more information on configuring the softmediaserver.cfg fie for audio and data conferencing, see Configuring the media settings on page 80. For more information on configuring the softmediaserver.cfg fie, see Configuring softmediaserver.cfg on page 198. Tabe 68: Softmediaserver.cfg Parameters Name and Defaut Vaue AutomaticGain=0 agctarget=-12 ComfortNoiseGeneration=0 ComfortNoiseLeve=60 SienceSuppression=1 ConfPayThreshod=-45 AudioTakerThreshod=-18 Description Media server runtime parameter. Automatic gain can be on or off (1 or 0). It is an integer (int). The AGC target power eve. It is an int. Generate comfort noise when nobody is speaking in the conference. It can be on or off (1 or 0). It is an int. The eve at which comfort noise is to be set. The vaue can vary from 30 to 60. Comfort noise is ouder when the vaue is ower. Avaya recommends a vaue of 60. It is an int. Enabe this option to enabe sience suppression. Sience suppression is the process of not transmitting information over the Meeting Exchange network when the parties invoved in a conference ca are not speaking, thereby reducing bandwidth usage. Essentiay, sience suppression prevents the Meeting Exchange server from sending packets during sience periods. Avaya recommends that you disabe sience suppression because during a conference, the Meeting Exchange server shoud aways be sending packets. When sience suppression is enabed, this vaue represents the energy threshod at which the media server stops sending audio. The vaues can vary from -20 to -60. Avaya recommends a vaue of -45. This vaue means that if the signa out of the conference is ess than 45 (DB) decibes, the Meeting Exchange server does not send a packet. Energy threshod for Audio Takers. Recommended vaue is -18 db, but the vaue can vary between -50 db and -5 db as required. It is an int. 1 of 3 Issue 1 Apri

362 List of softmediaserver.cfg parameters Tabe 68: Softmediaserver.cfg Parameters (continued) Name and Defaut Vaue basertpport=42000 maxchannes=702 maxchannesperconferenc e=300 PacketLossConceament=0 Buffer cache parameter settings gobareadcacheminnumb uffers=128 gobareadcachemaxnum Buffers=182 gobareadcachebuffersiz e= ocareadcachebuffersize = ocawritecachebuffersize = SRTP config Description Initia port for the rtp data. It is an int. The range of UDP ports used for the RTP media is defined by the number of channes per software media server and the number of software media servers configured: ((maxchannes * 2) * numberofsoftms processes) + basertpport) For exampe, (((702 x 2)x 6) ) = shows the defaut vaue of 702 maxchannes per Softms x 2 which is the number of UDP ports used in an audio ca. This vaue (1404) is then mutipied by the number of Softms processes configured on the system, in this exampe 6 giving a vaue of When added to the base range of this gives a fina UDP port number of The UDP range in this case is As an aside, the cacuation if the conferencing bridge has video enabed is as foows: ((maxchannes * 4) * numberofsoftms processes) + basertpport) Note there are 4 UDP RTP streams for audio and video instead of 2. Maximum number of channes in media server. It is an int. Maximum conference size. It is an int. Enabe PLC, on = 1, off = 0. It is an int. These settings have increased in vaue since the Meeting Exchange 5.1 reease. You must ensure that the vaues of these settings on your system are never ess than the defaut vaues that are presented here. When you upgrade from Meeting Exchange 5.1 to Meeting Exchange 5.2.x, you need to update these vaues in the softmediaserver.cfg fie on each media server in your depoyment. A bridge restart is required on the server so that the softms processes pick up the settings. 2 of Administering Meeting Exchange Servers

363 Tabe 68: Softmediaserver.cfg Parameters (continued) Name and Defaut Vaue Description securityenabed=0 Whether or not SRTP shoud be used for audio streams. 0 = disabed 1 = enabed. It is an int. Note: Note: For more information, see Configuring secure rea-time transport protoco (SRTP) on page 183. Note: Note: There are additiona parameters in this section but they are not isted here because they shoud ony be changed by an Avaya Support Representative. 3 of 3 Issue 1 Apri

364 List of softmediaserver.cfg parameters 364 Administering Meeting Exchange Servers

365 Gossary Automatic Number Identification Appication Server Attended Conference Bast Dia Bridge Tak Ca Hander Conferee Ca Detai Record Conference Detai Record ANI enabes Meeting Exchange to capture the teephone number of a caer. An appication server is the ocation of many of the core Meeting Exchange processes. It is the "heart" of the Meeting Exchange soution. It handes a teephone cas to Meeting Exchange and seects a media server on which to terminate each ca. It interprets a DTMF inputs, SIP information, database requests, and it processes biing data. The appication server communicates with the media server to provide a compete conferencing soution. It is often caed a ca hander appication server. A conference that is supervised by an operator. Typicay, an operator greets participants when they dia the conference teephone number. Operators can aso hep moderators to conduct pos or question and answer sessions. Operators can use Meeting Exchange appications such as Bridge Tak to perform these tasks. Attended conferences are usuay more expensive than unattended conferences because of the cost of an operator. In a bast dia, the Meeting Exchange simutaneousy dias an entire ist of phone numbers to estabish a conference. When conferees answer the ca, the Meeting Exchange prompts them to press specific digits on their teephones to join the conference without operator assistance. Moderators can initiate a bast dia when they are in a conference. Bridge Tak is an Avaya appication that you can use to manage conferences. You can perform tasks such as scheduing and controing ive conferences. Ca Hander is a term that is commony used to refer to the appication server. A conferee is a conference participant who does not have access to any advanced conference management features during a ive conference. Conferees attend conferences that moderators contro. Conferees can mute their own teephone ine but they cannot mute the teephone ines of other conferees. A conferee is often caed a reguar participant or an attendee. A CDR is the computer record produced by a teephone exchange. The record contains detais of a ca that passed through it. Meeting Exchange produces CDRs for each ca. Meeting Exchange aso produces conference detai records (CODR) for each conference. The CODR contains detais of the conference, such as the start and end time. See Ca Detai Record. Administering Meeting Exchange Servers Apri

366 De 1950 Servers De 1950 Servers Direct Dia Inward Distributed S6200 Diaed Number Identification Service Fexfow Conference Fexibe Digita Auxiiary Port Interface IBM 3650 M2 Intiaization and Administration System For previous versions of Meeting Exchange, the De 1950 servers provided the media server component for a S6200 server soution. For Meeting Exchange 5.2, Avaya support the IBM X3550 M2 server for a components, with the exception of Avaya Web Conferencing recording functionaity. For Avaya Web Conferencing recording functionaity, customers require the IBM X3650 M2 server. For customers who are running Meeting Exchange 5.1 on a De 1950 server and who wish to upgrade to Meeting Exchange 5.2, Avaya wi continue to support the De 1950 server. However, this support for the De 1950 server ony extends to customers using the G.711 codec. A DDI is a teephone number on the customer s private teephone exchange. A typica depoyment has a range of numbers. When a caer dias into a conference, Meeting Exchange recognizes the DDI that they have diaed and routes the ca in accordance with a number of configuration settings. A DDI is aso known as a Diaed Number Identification Service (DNIS). A distributed S6200 configuration is a depoyment which contains mutipe S6200 servers. This configuration provides more capacity than a singe S6200 and emuates the scae of a S6800 depoyment. Avaya Business Partner and Avaya Support Representatives often refer to this configuration as a Pyramid configuration. See Direct Dia Inward. A fexfow conference is a specific type of demand conference. In fexfow conferences, a ca routing is based on the conferee passcode. In addition to the conferee passcode, moderators enter a moderator passcode, which grants access to a moderator-specific menu. Using this menu, moderators can edit conference attributes via DTMF from their teephone keypad. An FDAPI resource is a permanant ink between the Meeting Exchange server and an operator or an API connection. You must configure an FDAPI resource for each operator in your depoyment. You need an FDAPI resource for each concurrent operator. You must aso configure an FDAPI resource for each API connection in your depoyment. For Meeting Exchange 5.2, the IBM 3650 M2 server provides the media server component. INADS is an Intiaization and Administration System. INADS is a computer system that receives aarm notification cas and generates troube tickets to track the resoution of that aarm. If you seect INADS, the SNMP trap is sent to an Avaya Services Security Gateway (SSG). An SSG is used for outbound connections through a virtua private network (VPN) from the customer system to Avaya Services. 366 Administering Meeting Exchange Servers Apri 2011

367 Passcode Load Baancing Media Processing Cards (MPC) Media Server Component Moderator This is a method of resiience that is suitabe for the S6200 and the S6800 media servers. This method of resiience prevents one server from being heaviy oaded, whie another server remains ide or reativey ide. Meeting Exchange aso supports resiience in the appication server. For more information, see Impementing Resiience for Meeting Exchange, which is avaiabe on support.avaya.com. Media Processing Cards (MPCs) provide the media server component for a S6800 server soution. In this regard, it can be usefu to think of MPCs as media servers. The media server component of Meeting Exchange provides a number of functions, such as, audio mixing, Dua Tone Muti Frequency (DTMF) detection, message paying, and conference recording. There are two types of Media Server; The S6200 and the S6800. In a S6200 soution, the media server components are the IBM 3650 M2 servers. In a S6800 soution, the media server components are the Media Processing Cards (MPC). A moderator is a conference participant who has access to a number of specia features during a ive conference. These features enabe moderators to contro the conference. These features may incude the abiity to start and stop recording, extend the size and ength of a conference, start ecture mode, and dia out to new participants. A moderator is often caed a Host or a Chairperson. If the Avaya Web Porta appication is depoyed in their organization, moderators can access Web Porta. In the Microsoft environment, moderators are often caed Leaders or Presenters. N+1 This is a method of resiience that is ony supported on the S6800 media server. This method of resiience invoves N number of media servers and a singe standby MPC. With this method of resiience, the standby is ide unti the appication server detects an issue on the active media server(s). Network Management System Participant Passcode NMS is a Network Management System. NMS is a commerica software system used for managing data networks. NMS are often extended to the management of attached systems and their embedded software. Usuay, NMSs use SNMP as the management protoco. Exampes are HP OpenView and IBM Tivoi. Participants are peope who attend conference cas. There are two types of participants; moderators and conferees. A passcode enabes entry to a conference. There are two types of passcode: Conferee passcode and moderator passcode. A conferee passcode grants access to conferee-eve conference features. A moderator passcode grants access to moderator-eve conference features. In the Meeting Exchange 5.2 appications, Passcode is often shorted to Code. In the wider Meeting Exchange environment, many peope refer to passcodes as security codes, host codes, conference codes, access codes, entry codes, and even PIN codes. Administering Meeting Exchange Servers Apri

368 PIN Code PIN Code Radisys Media Server (convms) Second Leve Passcode Simpe Network Management Protoco (SNMP) SIP Re-invite Unattended Conference PIN code is an identification number that is unique to each participant (both moderators and conferees). The name of the participant and their unique identification number are stored in a PIN ist. When operators using the CRS Front End and moderators using the Web Porta, create a new participant, the CRS generates a PIN code for each new participant. The CRS Front End interface refers to this fied as User PIN. The PINs and the name of the participant are stored in a database tabe. If an operator, using the CRS Front End or a moderator using the Web Porta books an unattended conference, they can choose a PIN Mode in the Options diaog. The Radisys media server is a carrier-cass media server optimized for arge IP Mutimedia Subsystem (IMS) network depoyments. Radisys CMS6000 and CMS9000 MPCs are exampes. If an operator books a Fexfow conference using the CRS Front End, they can enabe Security Passcode at booking time. If the operator enabes this feature, the audio conferencing server pays a message such as "Woud you ike to associate a second eve passcode with this conference?" to moderators after they enter their moderator passcode. Moderators can then enter a code using DMTF. Moderators are responsibe for distributing this code to conferees. To successfuy access the conference once the moderator has registered the code, conferees require their conferee passcode and the Second Leve Passcode. This feature is not avaiabe to moderators who book conferences using Web Porta. SNMP is a system of aarms which monitor the condition of the network. If there are probems on the network, the network sends an aarm. You can configure the aarm threshods so that you can contro the conditions that eicit an aarm. This is the name of the message that an appication server sends to the teephone endpoints to inform them of a new media server. An unattended conference is a conference that is not supervised by an operator. Typicay, caers manage their own progression through Meeting Exchange using the audio prompts. A faciity to access an operator in the event of difficuties may or may not be present, depending on the configuration. Unattended conferences are cheaper than attended conferences. 368 Administering Meeting Exchange Servers Apri 2011

369 Index Index Symbos +DRP /usr/ipcb/config , 211 A access time, CDR fied accessing the software Administrator sign-in AGC aarms Annunciator Deay, supervision configuration parameter295 annunicator messages See audio messages architecture ink ine Attended conference, Poing, non-supported feature conference, Q&A, non-supported Attended (U/A), CODR fied Attended ODO, system parameter audio messages ACP API Bridge Tak enabing per-conference message recording , 157 system wide messages , 159 transcript of audiopreferences.cfg Auto Hang-Up, code group parameter Auto-Extend Ports, system parameter Auto-Extend-Duration, system parameter Automatic CDR Print, system parameter Automatic Conf. Cear, system parameter Automatic Conf. ID, system parameter Automatic Security Codes, code group parameter.. 70 AutoVLL definition VLL diaout, overview Aux Code, CDR fied Auxiiary 1, CODR fied Auxiiary 2 fied in CODRs Auxiiary 2, CODR fied B beep mode, operator channe parameter Biing compatibe software, description of Biing Code fied in CODRs Biing Code, CODR fied bast deay, bast dia parameter bast dia , 270 bast deay configuring , 100 creating ists introducing LDAP ists , 106 moderators operators printing system administrators Bast dia, configuring CLPG (Ca Progress) timeout period invaid code response max. channe bast scan time Bridge Record Broadcast Scheduer component, overview of BSRes configuring stored procedure C ca ca branding definition introducing Ca Duration, CDR fied ca routing DDI Direct definition DNIS Direct ca routing configuration properties Ca Type, CDR fied Caing Phone, CDR fied cbuti , 144 CDR definition CDR End Date Administering Meeting Exchange Servers Apri

370 Index cdr_end, instaing on bridge CDR End Date Fiename cdr_end, description of CDR fieds access time ca duration ca type caing phone company name conf entry time conf ID , 284 conf minutes conf name , 283 conf number , 281, 283, 290 Cross Ref , 289 disc. reason disc. time DNIS digits headers , 283 Line Aux Line Aux Line Aux ine name ine number mod. status Network Type Passcode phone PIN code Prompt Set reconnect stye name , 283 transfer User Conf Type CDR report cdr_end CDR End Date Fiename, description of instaing on bridge Channe, operator channe parameter chdbased.reg Cient Registration Server component, overview of CLPG Timeout, bast dia parameter Code group caer destination when maximum ines exceeded. 68 caers trying to enter conference at wrong time.. 68 destination of caer faiing to enter code on time. 68 destination of caers entering a vaid code destination of caers entering invaid codes enabing/disabing enabing/disabing automatic hang-up enabing/disabing ODO enabing/disabing warning tones naming , 71 number of enter code prompts time between entry prompts user or system security code assignment codecs configuring CODR definition CODR fieds attended (U/A) auxiiary auxiiary biing code conf duration conf end time conf minutes Conf Viewer confirm number contact name contact phone Data Conf Goba ID Intercept Count notes recorded fie number sched duration min sched partips start time status info Sub Conf Count User Conf Type CODR reports comfort noise generation common media server Company Name, CDR fied Components description of, reated software optiona, reporting, biing Conf Duration, CODR fied Conf End Time, CODR fied Conf Entry Time, CDR fied Conf ID, CDR fied , 284 Conf Minutes, CDR fied Conf Minutes, CODR fied Conf Name, CDR fied , 283 Conf Num Wh , 290 Conf Number, CDR fied , 281, 283, 290 Conf Viewer, CODR fied Conference passcode, setting for Conference ID description of conference anguage Conference Name Required, code group parameter. 71 Conference Retention Conference Secured, code group parameter Conference server Administering Meeting Exchange Servers Apri

371 Index definition Conferences adding intercept goba, description of Poing, attended feature Q&A, attended feature conferences recording Configuration featcfg configuring active speaker notification interva automatic gain contro bast dia ca branding codecs comfort noise generation drive settings featcfg , 63, 355 anguages media server NTP server server IP the EPW timezones transport settings Confirm Number, CODR fied Contact Name, CODR fied Contact Phone, CODR fied Creating user sign-ins Cross Ref, CDR fied , 289 CRS definition goba reference number opening ports between sites D Data Conf, CODR fied Date Format, system parameter DDI definition DDI Direct ca routing defaut messages DHCP definition Dia Deay, supervision configuration parameter Dia String Dia-out use of, when scheduing DIRECT Disc. Reason, CDR fied Disc. Time, CDR fied Disconnect Mode, supervision configuration parameter296 DNIS definition direct, ca routing DNIS Digits, CDR fied DNIS-driven anguage DNS definition DoProcessGCDChanges configuring DTMF creating subconferences, moderator commands. 346, 351, 352 definition DTMF Acknowedge, system parameter E E1 definition Eary Start Minutes, system parameter enabe Enabing/disabing features with featcfg enabing/disabing features with featcfg , 355 Entry Tone, system parameter EPV. See Externa Passcode Vaidation Ethernet standard, 10BaseT Exit Tone, system parameter Externa Passcode Vaidation chdbased.reg process F fast dia See bast dia FDAPI featcfg , 63, 142, 355 Features adding intercept recording, a conference Fie Format PIN Codes PIN Lists First Person Message, system parameter Fex additiona passcode, setting for G Goba conference ID, overview conference, definition conferences, supported, non-supported features 256 Goba Conference Master Administering Meeting Exchange Servers Apri

372 Index definition Goba ID, CODR fied Goba Ref assigned by CRS Gossary Group Name, code group parameter H Hang up operator, goba conference, description of Headers, CDR fied , 283 Hub definition Hub and Spoke definition I IBM 3550 M , 33 ID goba conference, overview of Ignore DTMF Commands,system parameter instaing introduction to Intercept ast caer, conference feature Intercept Count, CODR fied Invaid Code, bast dia parameter Invaid Code, code group parameter Invaid Time of Day, code group parameter IP definition IVR definition J Jobs DoProcessGCDChanges p_getsystemparameter RunMutiSiteCDRs running stored procedures stored procedures, setting site ink priority in stored procedures, setting time zones in L LAN definition restrictions anguages conference anguage configuring system anguage icensed ports icenses Line Aux1, CDR fied Line Aux2, CDR fied Line Aux3, CDR fied Line Faut, supervision configuration parameter Line Name, CDR fied Line Number, CDR fied Link setting site ink priorities Link ine definition Loading the EPW Loca conference, participant counts conference, ro ca option conference, subconference Loca server setting site ink number, for oca server ocaization See anguages Log User Transaction M Maintenance sign-in Max. Channe Bast, bast dia parameter Max. Lines Reached, code group parameter Mod. Status, CDR fied Moderator dia out Moderator Lecture, system parameter mu-law mx-ipchange.sh N NAT definition Netwok Type, CDR fied Node definition Notes, CODR fied O ODO, enabing dia out On-Demand Percentage, Schedue code group parameter 71 On-Demand services, specifying percentage of ines. 71 On-Hod Msg. Frequency, system parameter Operator Assistance, system parameter Operator channes, configuring channe number Administering Meeting Exchange Servers Apri

373 Index remote operator operator channes, configuring beep mode beep time operator configuration properties Operator sign-in operatorhep.txt Originator Dia Out (ODO), code group parameter.. 69 Overbooking definition setting up eve, per site Overbooking (%), Schedue code group parameter.. 70 Overbooking, percentage of system ines P p_getsystemparameter setting time zones, ink priorities Participants count, oca conference Passcode optiona, for Fex conference Passcode, CDR fied per-conference message Phone Number Phone, CDR fied PIN Codes CDR fied creating fies definition fie format instaing with featcfg PIN Lists fie format PIN Lists PIN Mode, system parameter payback Payback Mute, system parameter Poing attended feature Ports enabing overbooking opening, between sites Priority setting site ink priorities, from stored procedure. 243 Prompt Set, CDR fied prompt sets names of prompts See audio messages properties bast dia ca routing CDR , 273 CODR operator configuration supervision configuration system configuration time assist configuration voice message warning tones PSTN definition Q Q&A attended feature R Reconnect, CDR fied Recorded Fie Number, CODR fied recording a conference, moderator feature configuring enabing fies introduction to payback use of, when scheduing Web Porta Remote (operator), operator channe parameter Reports compatibe software, description of Resources reserving additiona ports by overbooking Retention period, for Schedue group conference records70 Ring network definition Ro ca use of, oca conference RTCP RunMutiSiteCDRs configuring Running and verifying Core Services S Save Roster Save Roster, system parameter SBi appication, optiona component SCAN Scan Attempts, code group parameter Scan Time, bast dia parameter Scan Time, code group parameter Sched Duration Min., CODR fied Sched Partips, CODR fied Administering Meeting Exchange Servers Apri

374 Index Schedue code group conference retention percentage of system ines for On-Demand services71 percentage of system ines for overbooking Scheduer sign-in Scheduing recording option secure she Seize Date, CDR fied Seize Time, CDR fied Seect Sef Mute, system parameter server IP Sign-ins creating dispaying SiteLinkNum setting site ink number, for oca server setting, in stored procedure SiteLinkPriority setting site ink priority, in stored procedure Sites opening ports SiteTimeZoneName setting time zone, in stored procedure SiteTimeZoneType setting time zone, from stored procedure SNMP softmediaserver.cfg Software compatibe, for biing and reports SQL jobs, configuring DoProcessGCDChanges jobs, configuring RunMutiSiteCDRs SSH Start Time, CODR fied Starting Conf. ID, system parameter Startup Notify Time, system parameter Status Info., CODR fied Status, code group parameter Stored procedure, BSRes database Stored procedures DoProcessGCDChanges p_getsystemparameter RunMutiSiteCDRs setting site ink priority in setting time zones in Stye Name, CDR fied , 283 Sub Conf Count, CODR fied Sub Conferencing Mode, system parameter Subconferences starting, using moderator commands..346, 351, 352 viewing Supervision configuration annunciator deay dia deay disconnect mode ine faut wink timeout supervision configuration properties System configuration attended ODO auto-extend ports auto-extend-duration automatic CDR Print automatic conference ID automaticay cearing conference settings Bridge Record date format Dia String DTMF acknowedge eary start minutes entry tone exit tone first person message Ignore DTMF Commands Log User Transaction moderator ecture on-hod msg. frequency operator assistance Phone Number PIN mode payback mute Save Roster Sef mute starting conference ID startup notify time sub conferencing mode system name time format transaction ogs system configuration properties system anguage System Name, system parameter system wide messages , 159 T T1 definition TCP/IP definition tenumtouri.tab BaseT definition Administering Meeting Exchange Servers Apri 2011

375 Index testing the instaation Time Format, system parameter Time zone setting, from stored procedure time-based rues Timeout, code group parameter time-sensitive operator timezone tips TOS Transaction Logs, system parameter transcript of messages Transfer, CDR fied traps U UDP definition UI (User Interface) Unattended conferences enabing originator dia out warning tones User Conf Type, CDR fied User Conf Type, CODR fied V Verifying SNMP Trap Information Viewing goba conferences subconference Virtua Link Line See aso VLL VLAN VLL AutoVLL, ine diaed out, description voice message configuration W WAN definition Warning tones enabing for unattended conferences warning tones Warning Tones, code group parameter Wink Timeout, supervision configuration parameter. 297 Administering Meeting Exchange Servers Apri

376 Index 376 Administering Meeting Exchange Servers Apri 2011