Avaya 3100 Mobile Communicator and Security Instrukcja Użytkownika

Administration and SecurityAvaya 3100 Mobile Communicator3.1NN42030-600, 04.05October 2010

New in this release10 Administration and Security October 2010

12. Select OK.13. When the Certificate Uses prompt appears, select the Internet check box.The root certificate is installed in the device.Installing a

Installing a root certificate on a BlackBerry device in thenon-BES configurationInstall a root certificate on a BlackBerry in the non-BES configuratio

Client certificate management102 Administration and Security October 2010

Chapter 12: Server certificate administrationThis chapter describes the procedures that you use to administer server certificates.• Changing the certi

/usr/java/jdk1.6.0_03/bin/keytool -keypasswd -alias smog-ssl-keypass <oldpw> -new <newpw> -keystore ssl-keystore2. At the prompt, enter &l

Prerequisites• You must be logged into the server as superuser. For more information, see Accessingthe server command line as superuser on page 115.•

For information about how to install certificates on mobile clients see Clientcertificate management on page 99.Variable definitionsVariable Definitio

Important:The admin-ssl-keystore password must always be mobility.4. Respond to the prompts. For the common name (first and last name), enter a FQDNs

Variable Definition<valDays> The number of days that the certificate is valid.Range: 0 to 3600Server certificate administration108 Administr

Chapter 13: MaintenanceThis chapter describes procedures for maintaining the Avaya 3100 Mobile Communicator.• Backing up the Avaya 3100 Mobile Communi

Chapter 2: IntroductionThis document provides information about the administration and security of the Avaya 3100 MobileCommunicator.Avaya 3100 Mobil

Important:Avaya recommends that you copy this backup file to another server or othermedia.When preparing for an upgrade from Release 3.0 to Release 3

Checking the Avaya 3100 Mobile Communicator GatewaySoftware VersionThe Avaya 3100 Mobile Communicator Gateway current software version appears on theS

A Notification Message Failed dialog box appears if the notification is not sentsuccessfully.5. Click Close.Sending a system notification to individua

Gateway after you run the script. For more information about the networkconfig script, seeLinux Platform Base and Applications Installation and Commis

Maintenance114 Administration and Security October 2010

Chapter 14: Common proceduresThis chapter contains commonly used procedures.• Accessing the server command line as nortel on page 115• Accessing the s

Prerequisites• You require the password to the nortel userid on the server.• You require the password to the superuser (root) userid on the server.1.

Navigation•Using the Avaya 3100 Mobile Communicator Web Administration Console on page 13•Administration on page 21• Gateway administration on page 23

Chapter 3: Using the Avaya 3100 MobileCommunicator WebAdministration ConsoleThis chapter describes the Avaya 3100 Mobile Communicator Web Administrat

Table 1: Web Administration Console buttonsButton Screen DescriptionAdd Gateway System ConfigurationDisplays the Add Gatewaywindow. Only active when a

Button Screen DescriptionHelpWeb Administration Console mainwindowDisplays the Avaya 3100 MobileCommunicator pages on http://www.avaya.comInstall Lice

Button Screen DescriptionUnlockSystem Configuration (GatewayActions button)Displays the Unlock Gatewaywindow.View UserPortal Admin Portal Displays the

https://<IP address | hostname>:8553/adminserver2. In the Username field, type the user name.3. In the Password field, type the admin password.

•https://<IP address | FQDN>:8553/adminserver/userportal.html2. Press Enter.The User Portal screen displays.Variable definitionsVariable Definit

Variable definitionsVariable ValueCurrent Password Existing password.The default password for new servers ispasswordNew password New password for the

© 2010 Avaya Inc.All Rights Reserved.NoticeWhile reasonable efforts have been made to ensure that theinformation in this document is complete and accu

Using the Avaya 3100 Mobile Communicator Web Administration Console20 Administration and Security October 2010

Chapter 5: AdministrationThe following chapters describe administration procedures for the Avaya 3100 Mobile Communicator.Navigation• Gateway adminis

Administration22 Administration and Security October 2010

Chapter 5: Gateway administrationThis chapter describes procedures for gateway administration.• Adding an Avaya 3100 Mobile Communicator Gateway serv

Important:In a redundant system, add the local server first.3. Enter the Gateway Address as an IP Address or Fully Qualified Domain Name(FQDN).4. Cli

the Avaya 3100 Mobile Communicator Web Administration Console as an administrator onpage 16.1. Click System Configuration tab.2. Select Gateway Action

PrerequisitesYou must be logged in to the Avaya 3100 Mobile Communicator Web Administration Consoleas administrator. For more information on logging i

7. Click Close.You receive a prompt to restart the server.8. To restart the system, click Yes. The updated Gateway settings are applied.ORTo restart t

Field Description3100 Mobile Communicator Gateway, the prompts playin the language specified in this field.For more information on prompts, see Audio

Field DescriptionUse HTTPS when a certificate infrastructure exists onthe clients and Avaya 3100 Mobile CommunicatorGateway.This parameter applies to

ContentsChapter 1: New in this release...7Features...

Field DescriptionThe mobile phone will dial +41123456789 for directoutbound calls. This PSTN number will be routed to theenterprise as a DID number. W

Field Descriptionwhich the LDAP search begins. Obtain this value fromthe directory administrator.This parameter applies to both servers in the redunda

Field DescriptionThis parameter applies to both servers in the redundantconfiguration.LDAP attribute tag that containsthe user's email addressEnt

The system automatically inserts commas between the entries in the list.8. To save the changes, click OK.Variable definitionsVariable Value<numberc

Configuring the device settingsThe mobile device settings can automatically download to all the clients. A null valuedownloads if a parameter is not c

Field DescriptionExternal: Use Secure Connection Select Yes to enable HTTPS connections on theprimary Avaya 3100 Mobile Communicator Gatewaypublic int

Field DescriptionInternal: Address (IP/host:Port) Enter the address of the secondary Avaya 3100 MobileCommunicator Gateway private interface on thenet

Field DescriptionNative Dialing Numbers For information on configuring this field, see Configuring the emergency telephone numbers onpage 37Auto-Downl

Prerequisites• You must be logged into the Avaya 3100 Mobile Communicator Web AdministrationConsole as administrator. For more information, see Loggin

To block access to a port, clear the corresponding check box for that port.3. In the Admin Server Port Setting section, click Save.Procedure job aidUs

Chapter 6: Mobile client administration...49Client upgrade methods...

Important:Make sure you save a backup copy of your license files in a secure location. You will needthese files if you reinstall or perform major upg

Checking Gateway server statisticsCheck Gateway server statistics to check the number of outgoing calls, incoming calls, InstantConferencing, log ins

Field DescriptionIncoming call (IC) The total number of incoming calls processed by the server for this userOutgoing call(OC)The total number of outgo

Field DescriptionPresenceupdates (PRU)The total number of presence status updates.Presence sets(PRS)The total number of presence status updates on the

Field DescriptionIP Address Contains the IP Address of the Gateway Server.Status information appears to the right of this field.Click the IP Address t

Field Descriptionmessages clear. However, persistent errorconditions (such as missing or incorrectconfiguration settings) immediately generate newalar

PrerequisitesYou must be logged in to the Avaya 3100 Mobile Communicator Web Administration Consoleas administrator. For more information on logging i

The Status field indicates which server is currently active. In a single-server system,this is always the local server.2. To stop the server processes

The system responds with the status of the server processes.2. To start the server, enterappstart start3. To stop the server, enterappstart stop4. To

Chapter 6: Mobile client administrationThis chapter provides information and describes procedures that you use to administer the mobile clients.• Cli

Obtaining the CA signed SSL/TLS certificate for Avaya 3100 Mobile Communicator Gateway Server...94Obtaining the CA-signed certificate for the Av

Table 3: Client upgrade comparisonsInstall or upgrade type Advantages DisadvantagesFrom a computerretains a copy of thesoftware on the computerfor bac

Figure 1: Sample E-mail - Avaya 3100 Mobile Communicator - Client for BlackBerry over theair download on page 51 is a sample message you can send to a

Figure 2: Sample E-mail - Avaya 3100 Mobile Communicator - Client for Nokia over the air downloadFigure 3: Sample E-mail - Avaya 3100 Mobile Communica

Figure 3: Sample E-mail - Avaya 3100 Mobile Communicator - Client for Windows Mobile over the airdownloadUploading the mobile client software filesUse

Logging on to the Avaya 3100 Mobile Communicator Web Administration Console as anadministrator on page 16.• You must have downloaded the updated files

Filtering the mobile client software filesFilter the mobile client software files to view the files by product, platform, and language.PrerequisitesYo

3100 Mobile Communicator - Client for Nokia User Guide, NN42030-102, or Avaya3100 Mobile Communicator - Client for Windows Mobile User Guide, NN42030-

• Avaya 3100 Mobile Communicator - Client Windows Mobile User Guide,NN42030-107Variable definitionsVariable Definition<IP | hostname> The name o

Installing or upgrading the Avaya 3100 MobileCommunicator - Client for BlackBerry using the BlackBerryEnterprise ServerYou can deploy the Avaya 3100 M

Deployment option Uses and advantages Limitationsconnected to the wirelessnetwork.• Can be used to performinitial and upgradesoftware installations.•

6 Administration and Security October 2010

Field DescriptionInitiator The extension, telephone number, or mobile phone numberof the Instant Conferencing initiator.Active Participants Displays t

Chapter 7: User administrationThis chapter describes procedures used to administer users.• Configuring user parameters for autoconfiguration on page

Procedure job aidField DescriptionServer Address The IP Address or Fully Qualified Domain Name (FQDN) ofthe Avaya 3100 Mobile Communicator Gateway Ser

and reconfigure the username and password on the Enterprise Communication Server (ECS).The user can log on again using a new mobile device.If the user

Clearing a user messageYou can clear user messages if the user's queue exceeds normal levels due because of spamreceived while the user was logge

the Avaya 3100 Mobile Communicator Web Administration Console as an administrator onpage 16.1. Click the User Info tab.The User Info page appears with

Field Description- The client is disconnecting.• Out of Coverage: The client cannot communicate with theserver.The Status field updates in real time.P

the Avaya 3100 Mobile Communicator Web Administration Console as an administrator onpage 16.1. Click the User Info tab.2. On the User Info page, click

Field DescriptionBuddy queries(BDQ)The total number of buddy queries.Buddy removes(BDR)The total number of buddies deleted.FeaturesConference (CF)The

Chapter 8: Audio prompt administrationThis chapter provides information and procedures for audio prompt administration.By default, the Avaya 3100 Mob

Chapter 1: New in this releaseThe following sections detail what's new in Avaya 3100 Mobile Communicator Administration and Security,NN42030-600

- Endian: little• Prompts should start with a 100 to 250 millisecond silence before the voice starts, toensure that the prompt is not clipped on playb

Creating a language pack task flow navigation• Preparing prompt translations on page 71• Record the prompts on page 78•Preparing the file structure on

Language and locale code job aidUse the following table to record the language code and local code.Code name Requirements Codes to be usedlanguage_cod

Module Notes Filename Phrase Localized phraseconference linesavailable.GROUPCALL deniedlocked.wavYou could not beconnected. Theconference youtried to

Module Notes Filename Phrase Localized phraseGROUPCALL optionmuteself.wavPress '6' to muteyourself.GROUPCALL optionreport.wavPress '8&a

Module Notes Filename Phrase Localized phraseGROUPCALL thereare.wavIncluding yourself,there are …MEDIA numbers 0to 90.wav zeroMEDIA numbers 0to 91.wav

Module Notes Filename Phrase Localized phraseMEDIA numbers 0to 9 with “0”prefix05.wav oh fiveMEDIA numbers 0to 9 with “0”prefix06.wav oh sixMEDIA numb

Module Notes Filename Phrase Localized phrasenotebelow)MEDIA numbers10 andabove (seenotebelow)16.wav sixteenMEDIA numbers10 andabove (seenotebelow)(an

Module Notes Filename Phrase Localized phraseabove (seenotebelow)MEDIA numbers10 andabove (seenotebelow)(and so on)MEDIA numbers10 andabove (seenotebe

Prerequisites• You need the information in Language and locale code job aid on page 72.• You need the individual prompt files, as created in Record th

July 2010 Standard 04.04. This document is issued to support Avaya 3100Mobile Communicator Release 3.1. This document containseditorial changes.Novemb

Packaging the prompt filesThe prompt files must be packaged into a zip file to deploy the files. The installation processrequires the specific folder

If the langpack.sh tool encounters a problem, it returns a message describing theproblem. Correct the error, recreate the zip file, and retest the lan

1. If not already installed on the server, copy the tested zip file, <zipfilename>.zip, to /home/nortel.2. Stop the Avaya 3100 Mobile Communicat

Warning:If you configure a new default locale, and then later remove the language pack, the Avaya3100 Mobile Communicator Gateway uses the system-def

appstart stop3. Enter the following command:su -If prompted, enter the root password.4. Enter the following command:/opt/MobilityGateway/etc/langpack.

Chapter 10: SecurityThe following chapters provide security information and describe security procedures for the Avaya 3100Mobile Communicator.Navigat

Security86 Administration and Security October 2010

Chapter 10: Server certificate managementThis chapter describes the procedures that you use to manage server certificates. You implement acertificate

Important:In some cases the root certificates for some well-known CAs (such as VeriSign and Entrust) are pre-installed on the server and many client

ResultServer certificate management procedures• Enrolling with a CA on page 89• Generating a CSR for Avaya 3100 Mobile Communicator Gateway Server on

January 2009 Standard 03.04 This document is issued to support Avaya 3100Mobile Communicator Release 3.0. Changes were made to addressformatting issue

Generating a CSR for Avaya 3100 Mobile CommunicatorGateway ServerGenerate a Certificate Signing Request (CSR) for the Avaya 3100 Mobile CommunicatorGa

8. Change ownership of the Avaya 3100 Mobile Communicator Gateway Serverkeystore from root to mobility with the following two commands:chown mobility:

1. Change to the certificate keystore directory. cd /opt/mobilitygw-2.1/server/default/data2. Delete the default Avaya 3100 Mobile Communicator Admini

/usr/java/jdk1.6.0_03/bin/java -cp ../lib/jbosssx.jarorg.jboss.security.plugins.FilePassword mobility 13<password> keystore.passwordVariable def

instructions on installing certificates on mobile clients, see Client certificatemanagement on page 99.Obtaining the CA signed SSL/TLS certificate for

4. Paste the contents into the prompt or Web page.5. Request your signed SSL/TLS certificate.The CA generates your signed SSL/TLS certificate and e-ma

Variable Definition<path-signed_mgcert_file> The full name of the Avaya 3100 MobileCommunicator Gateway TLS certificate,including the pathInstal

Important:Make a backup copy of your keystore databases (ssl-keystore and admin-ssl-keystore) as a precaution against overwriting, deleting, or corru

Server certificate management98 Administration and Security October 2010

Chapter 11: Client certificate managementThis chapter describes the procedures that you use to manage client certificates on the devices.Typically, yo