Avaya one-x Communicator Centralized Administration Tool

Avaya one-x Communicator Centralized Administration Tool August 2010

2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available to Avaya customers and other parties through the Avaya Support Web site: http://www.avaya.com/support. Please note that if you acquired the product from an authorized Avaya reseller outside of the United States and Canada, the warranty is provided to you by said Avaya reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ 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, AND 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 End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. Designated Processor means a single stand-alone computing device. Server means a Designated Processor that hosts a software application to be accessed by multiple users. Software means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone products or pre-installed on Hardware. Hardware means the standard hardware originally sold by Avaya and ultimately utilized by End User. License type(s) Named User License (NU). End User may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. Named User, means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a Named User may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an e-mail or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Software that permits one user to interface with the Software. Shrinkwrap License (SR). With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as shrinkwrap or clickwrap license accompanying or applicable to the Software ( Shrinkwrap License ). The text of the Shrinkwrap License will be available from Avaya upon End User s request (see Third-party Components for more information). Copyright Except where expressly stated otherwise, no use should be made of materials on this site, the Documentation(s) and Product(s) provided by Avaya. All content on this site, the documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ( Third Party Components ), which may contain terms that expand or limit rights to use certain portions of the Product ( Third Party Terms ). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://www.avaya.com/support/copyright/. Preventing toll fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: http://www.avaya.com/support/. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: securityalerts@avaya.com. 2 Administering Avaya one-x Communicator R6 August 2010

Trademarks Avaya, the Avaya logo, Avaya one-x Communicator, Avaya one-x Portal, Avaya Aura, Avaya Communication Manager, Application Enablement Services, Avaya Video Telephony Solution, Modular Messaging, and Conferencing are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All other trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: http://www.avaya.com/support Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://www.avaya.com/ support Administering Avaya one-x Communicator R6 August 2010 3

4 Administering Avaya one-x Communicator R6 August 2010

Contents Chapter 1: Introduction...7 About this guide...7 Centralized Administration Tool overview...7 Chapter 2: Configuring Login settings...9 Login settings...9 Allow auto-login...10 Allow saving login credentials...10 Allow saving login password...10 Allow My Computer login mode...10 Allow Desk Phone login mode...10 Allow Other Phone login mode...10 Save...10 Open...11 Specifying Login settings...11 Modifying Login settings...11 Chapter 3: Configuring Auto-configure settings...13 Auto-configure settings...13 Group...14 Auto-configure at startup...14 Specify a date and time after which the clients must auto-configure at startup...14 Server...14 Server Directory...14 Server File...14 Save...15 Open...15 Enhancing Auto-configure settings...15 Modifying Auto-configure settings...15 Chapter 4: Configuring Dialing Rules...17 Dialing Rules settings...17 Add...18 Add Rule dialog box field descriptions...18 Remove...20 Save...20 Open...20 Configuring Dialing Rules...20 Modifying Dialing Rules...20 Chapter 5: Customizing call log settings...23 Customize settings...23 Save...23 Open...24 Specifying call log settings...24 Modifying call log settings...24 Chapter 6: Configuring features...25 Features settings...25 Administering Avaya one-x Communicator R6 August 2010 5

Allow video...25 Portal...25 Allow Citrix mode...25 64-bit Windows...25 Changing features settings...26 Index...27 6 Administering Avaya one-x Communicator R6 August 2010

Chapter 1: Introduction About this guide This Centralized Administration Tool guide describes how to configure different Avaya one- X Communicator settings. Centralized Administration Tool overview Centralized Administration Tool is a graphical user interface (GUI) stand-alone tool that allows you to configure different Avaya one-x Communicator settings. This tool saves all the settings in XML files. These files can be imported to multiple computers thereby supporting largescale deployments. You can configure the following settings by clicking the corresponding tabs: Login Auto-configure Dialing Rules Customize Features Administering Avaya one-x Communicator R6 August 2010 7

Introduction 8 Administering Avaya one-x Communicator R6 August 2010

Chapter 2: Configuring Login settings Login settings Avaya one-x Communicator uses the settings defined in the login.xml file to control enduser Login settings. You can create this file manually in a text editor or by using the Centralized Administration tool. Sample login.xml file <?xml version="1.0" encoding="utf-8"?> <Login xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http:// www.w3.org/2001/xmlschema" xmlns="http://xml.avaya.com/endpointapi"> <AllowAutoLogin>true</AllowAutoLogin> <RememberLoginCredentials>true</RememberLoginCredentials> <RememberLoginPassword>true</RememberLoginPassword> <AllowMyComputerLogin>true</AllowMyComputerLogin> <AllowDeskPhoneLogin>true</AllowDeskPhoneLogin> <AllowOtherPhoneLogin>true</AllowOtherPhoneLogin> <NetworkRegion>-1</NetworkRegion> </Login> You can save this file either in the user path or in the installation path and also in both paths. The user path is C:\Documents and Settings\<user>\Application Data\Avaya \Avaya one-x Communicator directory in case of Microsoft Windows XP and C:\Users \<user>\appdata\roaming\avaya\avaya one-x Communicator directory in case of Microsoft Windows Vista and Microsoft Windows 7. The installation path is C:\Program Files\Avaya\Avaya one-x Communicator directory in case of Microsoft Windows XP and C:\Program Files (x86)\avaya \Avaya one-x Communicator directory in case of Microsoft Windows Vista and Microsoft Windows 7. If you specify the same parameter in the login.xml file in either of the paths, the parameter specified in the installation path overrides the one specified in the user path. Instead of manually creating the login.xml file, you can open the tool, enter the appropriate information in the fields, and then save the settings to create the login.xml file. If desired, you can also update the login.xml file using this tool. Administering Avaya one-x Communicator R6 August 2010 9

Configuring Login settings Allow auto-login List box to specify whether to prevent the use of auto-login feature. By default, Avaya one-x Communicator allows the use of Auto-login feature. Allow saving login credentials List box to specify whether the user needs to enter extension or user name and password for every login. By default, Avaya one-x Communicator saves login credentials, and the user does not need to enter extension or user name and password for every login. Allow saving login password List box to specify whether the user needs to enter the password at every login. By default, Avaya one-x Communicator saves login password, and the user does not need to enter password for every login. Allow My Computer login mode List box to specify whether to prevent the use of My Computer mode at login. By default, Avaya one-x Communicator allows the use of My Computer mode at login. Allow Desk Phone login mode List box to specify whether to prevent the use of Desk Phone mode at login. By default, Avaya one-x Communicator allows the use of Desk Phone mode at login. Allow Other Phone login mode List box to specify whether to prevent the use of Other Phone mode at login. By default Avaya one-x Communicator allows the use of other Phone mode at login. Save Button to save the Avaya one-x Communicator Login settings. 10 Administering Avaya one-x Communicator R6 August 2010

Specifying Login settings Open Button to open the existing login.xml file for editing. Specifying Login settings Use the Login tab to specify how the end user logs in to Avaya one-x Communicator. 1. Click the Login tab. 2. Enter the appropriate information. 3. Click Save to save the Login settings. Modifying Login settings You can also use the Login tab to modify the existing Login settings. 1. Click the Login tab. 2. Click Open. 3. Select the login.xml file. 4. Click Open to populate the Login settings. 5. Modify the appropriate information, and click Save to update the Login settings. Administering Avaya one-x Communicator R6 August 2010 11

Configuring Login settings 12 Administering Avaya one-x Communicator R6 August 2010

Chapter 3: Configuring Auto-configure settings Auto-configure settings Avaya one-x Communicator retrieves the Auto-configure settings from the 46xxsettings.txt file. Using the discover.xml file, you can enhance Auto-configure to retrieve data for a specific user group, automatically run at startup, and use a settings file that cannot be discovered through DHCP. You can create this file manually in a text editor or by using the Centralized Administration tool. Sample discover.xml file <?xml version="1.0" encoding="utf-8"?> <Discover xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http:// www.w3.org/2001/xmlschema" xmlns="http://xml.avaya.com/endpointapi"> <AutoRun>true</AutoRun> <AutoRunDateTime>2000-12-31T23:59:59</AutoRunDateTime> <Server>109.10.11.12</Server> <ServerDirectory>AvayaEndpoints/</ServerDirectory> <ServerFile>My46xxsettings.txt</ServerFile> <Group>414</Group> </Discover> You can save this file either in the user path or in the installation path and also in both paths. The user path is C:\Documents and Settings\<user>\Application Data\Avaya \Avaya one-x Communicator directory in case of Microsoft Windows XP and C:\Users \<user>\appdata\roaming\avaya\avaya one-x Communicator directory in case of Microsoft Windows Vista and Microsoft Windows 7. The installation path is C:\Program Files\Avaya\Avaya one-x Communicator directory in case of Microsoft Windows XP and C:\Program Files (x86)\avaya \Avaya one-x Communicator directory in case of Microsoft Windows Vista and Microsoft Windows 7. If you specify the same parameter in the discover.xml file in either of the paths, the parameter specified in the installation path overrides the one specified in the user path. Instead of manually creating the discover.xml file, you can open the tool, enter the appropriate information in the fields, and then save the settings to create the discover.xml file. If desired, you can also update the discover.xml file using this tool. Administering Avaya one-x Communicator R6 August 2010 13

Configuring Auto-configure settings Group Field to enter the dedicated user group identifier. By default, Avaya one-x Communicator does not specify a group when retrieving settings from the 46xxsettings.txt file. Auto-configure at startup List box to specify whether you want Avaya one-x Communicator to run Auto-configure at all startups. By default, Avaya one-x Communicator runs only at first startup after installation and never again. Specify a date and time after which the clients must autoconfigure at startup. Check box to specify the date and time after which Avaya one-x Communicator must run Autoconfigure at startup. Avaya one-x Communicator runs Auto-configure at startup if the time specified is after the last Auto-configure-at-startup attempt. Selecting this check box enables the Date and Time fields. Server Field to enter the IP address of the Web server that hosts the settings file. Use only if Avaya one-x Communicator cannot retrieve the Web server address from the DHCP server. This usually happens when Avaya one-x Communicator is running over a virtual private network. Server Directory Field to enter the directory of the settings file used during Auto-configure. Use only if a server has been specified in the Server field, and the settings file is present in a directory on that Web server. Server File Field to enter the name of the settings file to be used during Auto-configure. Use only if this name of this settings file is not 46xxsettings.txt. 14 Administering Avaya one-x Communicator R6 August 2010

Enhancing Auto-configure settings Save Button to save the Avaya one-x Communicator Auto-configure settings. Open Button to open an existing discover.xml file. Enhancing Auto-configure settings Use the Auto-configure tab to enhance the auto-configure settings. 1. Click the Auto-configure tab. 2. Enter the appropriate information. 3. Click Save to save the Avaya one-x Communicator Auto-configure settings. Modifying Auto-configure settings You can also use the Auto-configure tab to modify the existing Auto-configure settings. 1. Click the Auto-configure tab. 2. Click Open. 3. Select the discover.xml file. 4. Click Open to populate the Auto-configure settings. 5. Modify the appropriate information, and click Save to update the Avaya one-x Communicator Auto-configure settings. Administering Avaya one-x Communicator R6 August 2010 15

Configuring Auto-configure settings 16 Administering Avaya one-x Communicator R6 August 2010

Chapter 4: Configuring Dialing Rules Dialing Rules settings If the default dialing rules in Avaya one-x Communicator are not set correctly, you can set these rules by specifying patterns in the dialingrules.xml file. You can create this file manually in a text editor or by using the Centralized Administration tool. Note: You can specify the dialing rules other than the default ones in the 46xxsettings.txt file. Sample dialingrules.xml file <DialingRulesPatternList xmlns="http://xml.avaya.com/endpointapi"> <DialingRulesPattern> <type>0</type> <pattern>^411</pattern> <substring>9</substring> <minlength>3</minlength> <maxlength>3</maxlength> <deletelength>0</deletelength> </DialingRulesPattern> <DialingRulesPattern> <type>0</type> <pattern>^911</pattern> <substring>9</substring> <minlength>3</minlength> <maxlength>3</maxlength> <deletelength>0</deletelength> </DialingRulesPattern> <DialingRulesPattern> <type>0</type> <pattern>^[0-9]811</pattern> <substring>91888</substring> <minlength>10</minlength> <maxlength>11</maxlength> <deletelength>4</deletelength> </DialingRulesPattern> <DialingRulesPattern> <type>0</type> <pattern>811</pattern> <substring>92800</substring> <minlength>10</minlength> <maxlength>11</maxlength> <deletelength>3</deletelength> </DialingRulesPattern> <DialingRulesPattern> <type>1</type> <pattern>9888</pattern> Administering Avaya one-x Communicator R6 August 2010 17

Configuring Dialing Rules <substring>777</substring> <minlength>10</minlength> <maxlength>15</maxlength> <deletelength>4</deletelength> </DialingRulesPattern> <DialingRulesPattern> <type>1</type> <pattern>[0,9]1800</pattern> <substring>666</substring> <minlength>10</minlength> <maxlength>14</maxlength> <deletelength>5</deletelength> </DialingRulesPattern> </DialingRulesPatternList> Order is important. Avaya one-x Communicator returns the transformed string after the first pattern match and does not apply the subsequent rules, including the default ones. You can save this file either in the user path or in the installation path and also in both paths. The user path is C:\Documents and Settings\<user>\Application Data\Avaya \Avaya one-x Communicator directory in case of Microsoft Windows XP and C:\Users \<user>\appdata\roaming\avaya\avaya one-x Communicator directory in case of Microsoft Windows Vista and Microsoft Windows 7. The installation path is C:\Program Files\Avaya\Avaya one-x Communicator directory in case of Microsoft Windows XP and C:\Program Files (x86)\avaya \Avaya one-x Communicator directory in case of Microsoft Windows Vista and Microsoft Windows 7. If you specify the same parameter in the dialingrules.xml file in either of the paths, the parameter specified in the installation path overrides the one specified in the user path. Instead of manually creating the dialingrules.xml file, you can open the tool, enter the appropriate information in the fields, and then save the settings to create the dialingrules.xml file. If desired, you can also update the dialingrules.xml file using this tool. You can use the mouse to change the order of the rules in the list by dragging and dropping. Add Button to open the Add Rule dialog box. Add Rule dialog box field descriptions Use this dialog box to specify a pattern match rule. 18 Administering Avaya one-x Communicator R6 August 2010

Dialing Rules settings Pattern Field to enter a regular expression. The pattern can exist anywhere in the input string, not necessarily from the beginning or the end of the input string. Type List box to specify whether to apply the Dialable rule to all the outgoing numbers before storing the number in the call log or to apply the Normalize rule to all the incoming numbers before storing the number in the call log. Prefix Field to enter the string to be prefixed to the input string after deleting the specified number of characters. Delete Length Field to enter the number of characters, including the + character, to delete from the beginning of the input string. Minimum Length Field to enter the minimum length, including the + character, of the input string Maximum Length Field to enter the maximum length, including the + character, of the input string OK Button to add the pattern match rule and close the Add Rule dialog box. Cancel Button to cancel adding the pattern match rule and close the Add Rule dialog box. Administering Avaya one-x Communicator R6 August 2010 19

Configuring Dialing Rules Remove Button to remove an existing pattern match rule. Save Button to save the Avaya one-x Communicator dialing rules settings. Open Button to open the existing dialingrules.xml file. Configuring Dialing Rules Use the Dialing Rules tab to customize the dialing rules settings. 1. Click the Dialing Rules tab. 2. Click Add to open the Add Rule dialog box. 3. Enter the appropriate information. 4. Click OK to add a new pattern match rule. 5. Click Save to save the Dialing Rules settings. Modifying Dialing Rules you can also use the Dialing Rules tab to modify the existing Dialing Rules settings. 1. Click the Dialing Rules tab. 2. Click Open. 3. Select the dialingrules.xml file. 20 Administering Avaya one-x Communicator R6 August 2010

Modifying Dialing Rules 4. If you want to add a pattern match rule, select a rule and click Remove. 5. If you want to add additional pattern match rules, click Add to open the Add Rule dialog box, enter the appropriate information and click OK. 6. Click Save to update the Dialing Rules settings. Administering Avaya one-x Communicator R6 August 2010 21

Configuring Dialing Rules 22 Administering Avaya one-x Communicator R6 August 2010

Chapter 5: Customizing call log settings Customize settings Avaya one-x Communicator uses the settings defined in the customize.xml to control display of call name and call number in the call log. If the call name does not exist, Avaya one- X Communicator displays only the number. There are exceptional cases where the call name exists but Avaya one-x Communicator does not consider it because it is a non-descriptive system generated case. For such calls, you can edit the customize.xml file to force Avaya one-x Communicator to display both the call name and number for these calls. Sample customize.xml file <?xml version="1.0" encoding="utf-8"?> <CallLog xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" xmlns:xsd="http:// www.w3.org/2001/xmlschema" xmlns="http://xml.avaya.com/endpointapi"> <ShowCallNameAndNumberDefault>true</ShowCallNameAndNumberDefault> </CallLog> You can save this file either in the user path or in the installation path and also in both paths. The user path is C:\Documents and Settings\<user>\Application Data\Avaya \Avaya one-x Communicator directory in case of Windows XP and C:\Users\<user> \AppData\Roaming\Avaya\Avaya one-x Communicator directory in case of Windows Vista and Windows 7. The installation path is C:\Program Files\Avaya\Avaya one-x Communicator directory in case of Windows XP and C:\Program Files (x86)\avaya\avaya one-x Communicator. If you specify the same parameter in the customize.xml file in either of the paths, the parameter specified in the installation path overrides the one specified in the user path. Instead of manually creating the customize.xml file, you can open the tool, enter the appropriate information in the fields, and then save the settings to create the customize.xml file. If desired, you can also update the customize.xml file using this tool. Save Button to save the Avaya one-x Communicator Customize settings. Administering Avaya one-x Communicator R6 August 2010 23

Customizing call log settings Open Button to open the existing customize.xml file for editing. Specifying call log settings Use the Customize tab to forceavaya one-x Communicator to display the call name and number in the call log. 1. Click the Customize tab. 2. In the Show the call name and number in the call log fields, click Yes. 3. Click Save to save the Avaya one-x Communicator call log settings. Modifying call log settings You can also use the Customize tab to modify the existing call log settings. 1. Click the Customize tab. 2. Click Open. 3. Select the customize.xml file. 4. Click Open to populate the Show the call name and number in the call log field. 5. In the Show the call name and number in the call log settings, click Yes. 6. Click Save to update the call log settings. 24 Administering Avaya one-x Communicator R6 August 2010

Chapter 6: Configuring features Features settings When the user installs Avaya one-x Communicator, video and integration withavaya one-x Portal are installed by default. You can enable or disable those features after the user installs Avaya one-x Communicator. Use the Features tab to change the features to which the user can gain access. Allow video List box to specify whether the user can use the video features. Portal List box to specify whether the user can integrate Avaya one-x Communicator with Avaya one- X Portal. Allow Citrix mode List box to specify whether the user can run Avaya one-x Communicator in Citrix mode. 64-bit Windows List box to specify whether to enable or disable both video and Avaya one-x Portal integration or either of the two on 64-bit Windows. Administering Avaya one-x Communicator R6 August 2010 25

Configuring features Changing features settings Use the Features tab to specify the Avaya one-x Communicator features that the user can access. 1. Click the Features tab. 2. Modify the appropriate information. 3. Click Save. 26 Administering Avaya one-x Communicator R6 August 2010

Index A Add Rule...18, 19 dialable...19 Length...19 Maximum Length...19 Minimum Length...19 normalize...19 Pattern...19 prefix...19 Auto-configure...13 15 server file...14 settings...13, 15 Auto-login...10 C Call log settings modifying...24 specifying...24 Customize settings...23 D Dialing Rules...17, 20 settings...17 Dialing Settings Add...18 Open...20 F Remove...20 Features 64-bit Windows...25 Citrix...25 Portal...25 settings...25, 26 Video...25 G Group...14 L Legal notices...2 Login...9, 11 Open...11 settings...9 Login credentials saving...10 Login password...10 N Notices, legal...2 O Overview...7 S Server...14 Server Directory...14 Administering Avaya one-x Communicator R6 August 2010 27

28 Administering Avaya one-x Communicator R6 August 2010