TGW 1.0.3 Admin Guide

8/11/2019 TGW 1.0.3 Admin Guide

http://slidepdf.com/reader/full/tgw-103-admin-guide 1/141

DN0182152 1

Issue 1-3 en Copyright © Nokia Corporation 2002.

Nokia Multimedia Terminal Gateway Release 1.0.3Part of the Multimedia Messaging Service Application Suite

Administrator Guide



2

Copyright © Nokia Corporation 2002.

PURPOSE. This document describes the product(s) defined in the introduction of thisdocument and is subject to change without notice. This document is intended for the use of

Nokia Corporation’s customers for the sole purposes of the agreement under which it issubmitted. It has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it.PROVIDED “AS IS”. Nokia Corporation has used reasonable efforts to ensure that theinstructions contained in the document are adequate and free of material errors andomissions. This document is provided on an “AS IS” basis, with no warranty of any kind.

NOKIA CORPORATION SPECIFICALLY DISCLAIMS ANY AND ALL IMPLIEDWARRANTIES, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OFFITNESS, MERCHANTABILITY AND TITLE. Further, the information or statementscontained in this document concerning the suitability, capacity or performance of the

product(s) concerned are not binding, except as may explicitly be agreed to by NokiaCorporation in the agreement under which this document is submitted.

Limitation of Liability. Nokia Corporation’ liability for any errors in the document islimited to the documentary correction of errors. IN NO EVENT SHALL Nokia

Corporation HAVE ANY LIABILITY FOR ANY DAMAGES OF WHATEVER NATURE, WHETHER DIRECT, INDIRECT, SPECIAL, INCIDENTAL, ECONOMICOR CONSEQUENTIAL, that might arise from the use of or inability to use this documentor anything contained herein.

Intellectual Property Rights. This document and the product it describes are protected bycopyright according to applicable laws. No part of this document may be reproduced ortransmitted in any form or by any means without the prior written permission of NokiaCorporation. Nokia and Nokia Connecting People are registered trademarks of NokiaCorporation.

Product names mentioned in this document may be trademarks of their respectivecompanies and are mentioned for identification purposes only.

Copyright © Nokia Corporation 2002. All rights reserved.



DN0182152 3


Table of contents

1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Product description for TGW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1.2 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3 Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.4 Mobile subscriber types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

1.5 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.6 Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.7 TGW documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.8 Related documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.9 If you have documentation comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1.10 Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.1 Logging in/logging out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.1.1 Logging in as the administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.1.2 Logging in as the supervisor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.1.3 Logging out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.2 Navigating the interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.2.1 Navigational buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.2.2 Toolbar options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.2.3 Navigational tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.2.4 Operational buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.2.5 Navigational links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.3 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.3.1 Avoid changing values for configuration parameters . . . . . . . . . . . . . . 31

2.4 Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.4.1 Saving changes on each screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.4.2 Avoiding the Refresh or Reload buttons . . . . . . . . . . . . . . . . . . . . . . . . 31

2.4.3 Switching between the General and TGW tabs . . . . . . . . . . . . . . . . . . . 31

2.4.4 Switching between the System and Events tabs . . . . . . . . . . . . . . . . . . 32

2.4.5 Making an entry in your billing system . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.5 Known browser issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.5.1 Downloading log files from IE 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.5.2 Online help browser issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3 Managing TGW subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.2 Using the Subscriber Search Criteria screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.2.1 Subscriber Search Criteria toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.2.2 Search Results toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.3 Adding TGW subscribers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.4 Editing TGW subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.5 Deactivating existing TGW subscribers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38



4


3.5.1 Deactivating from the Subscriber Search Criteria screen . . . . . . . . . . . 38

3.5.2 Deactivating from the Edit Subscriber Information screen . . . . . . . . . . 39

3.6 Activating TGW subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403.7 Deleting TGW subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

3.8 Assigning Class of Service plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.9 Searching for TGW subscribers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4 Managing Class of Service plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.2 Using the Class of Service Plans screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.3 Creating new COS plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.4 Editing COS plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.5 Deactivating COS plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4.5.1 Deactivating from the Class of Service Plans screen. . . . . . . . . . . . . . . 514.5.2 Deactivating from the Edit Class of Service Information screen. . . . . . 52

4.6 Activating Class of Service plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5 Configuring parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555.1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.2 Using the Configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5.2.1 Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.2.2 System tab configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.2.3 System tab properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.3 Managing system properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.3.1 Billing properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.3.2 SMS properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

5.3.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.3.4 Legacy message storage expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.4 Managing events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.4.1 Enabling billable events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

5.4.2 Enabling SNMP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.4.3 Enabling event logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

6 Changing Administrator Account settings . . . . . . . . . . . . . . . . . . . . . . . . . 69

6.1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696.2 Using the Administrator Account Settings screen . . . . . . . . . . . . . . . . . . . . . . . . 69

6.3 Changing the administrator password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6.4 Changing the supervisor password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

7 Managing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737.1 Overview of the Logging System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

7.1.1 Events Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.2 Logging Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76



DN0182152 5


7.3 Publishers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

7.3.1 Log Levels for Publishers vs. Events. . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7.3.2 Publisher Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

7.3.3 Changing the Log Level for Publishers . . . . . . . . . . . . . . . . . . . . . . . . . 79

7.4 The Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

7.4.1 Logger Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

7.5 Listeners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

7.5.1 Listener Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

7.5.2 Safeguarding Against Event Log Loss. . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.6 Reading the Log Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.7 Displaying a log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7.8 Downloading a log file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7.9 How to Interpret the Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

8 Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 878.1 Troubleshooting the MMSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

8.1.1 Message delivery failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

8.1.2 Additional information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

8.2 Troubleshooting Apache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

8.2.1 Incorrect spacing in the VirtualHost definition . . . . . . . . . . . . . . . . . . . 88

8.2.2 How to check the httpd.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

8.3 Troubleshooting Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

8.3.1 Blocked connections to the database . . . . . . . . . . . . . . . . . . . . . . . . . 90

8.3.2 Information about Oracle errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

8.3.3 Backing up the database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

9 Backup overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939.1 System Configuration Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

9.1.1 User Data Backups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

9.1.2 Backup Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

9.1.3 Uninterruptible power supplies (UPS) . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Appendix A: Acronyms and terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Appendix B: Product descriptions for EGW and VGW. . . . . . . . . . . . . . . . . . . 101

Appendix C: Field descriptions for Create Subscriber . . . . . . . . . . . . . . . . . . 103

Appendix D: Description of available TGW events. . . . . . . . . . . . . . . . . . . . . . 107

Appendix E: Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119



6




DN0182152

Issue 1-3 en

7


List of Figures

Figure 1 Overview of mobile subscribers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Figure 2 User name field on the Log In screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 3 Password field on the Log In screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Figure 4 Example of toolbar options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Figure 5 Example of navigational tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Figure 6 Search button as example of an operational button . . . . . . . . . . . . . . . . . . . . . . . 29

Figure 7 Change button as example of an operational button . . . . . . . . . . . . . . . . . . . . . . 29

Figure 8 Example of navigational link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 9 Edit Subscriber Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Figure 10 Fields available under the Subscriber Search Criteria screen . . . . . . . . . . . . . . . 34

Figure 11 Area under the Search Results toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Figure 12 The Create Subscriber: Step 1 of 1 screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Figure 13 Linking to Edit Subscriber Information screen . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 14 The Edit Subscriber Information screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Figure 15 Deactivating from the Subscriber screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Figure 16 Deactivating from the Edit Subscriber Information screen . . . . . . . . . . . . . . . . . 39

Figure 17 The Edit Subscriber Information screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Figure 18 Deleting from the Subscriber screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Figure 19 Selecting TGW subscribers to which to assign a COS . . . . . . . . . . . . . . . . . . . . 41

Figure 20 Assign Class of Service pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Figure 21 Defining your subscriber search from the Search for drop-down list . . . . . . . . . 42

Figure 22 Searching for a subscriber by last name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Figure 23 The Class of Service Plans screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 24 The Create Class of Service:step 1 of 2 screen . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Figure 25 The Create Class of Service: step 2 of 2 screen . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Figure 26 Selecting the COS plan to edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Figure 27 The Edit Class of Service screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Figure 28 Accessing TGW COS information under the TGW tab. . . . . . . . . . . . . . . . . . . . 50

Figure 29 Deactivating from Class of Service Plans screen. . . . . . . . . . . . . . . . . . . . . . . . . 51

Figure 30 Selecting the COS plan to deactivate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Figure 31 The Edit Class of Service screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 32 Changing COS status from Active to Inactive. . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Figure 33 Configuration Parameters area on the Configuration screen . . . . . . . . . . . . . . . . 56

Figure 34 Properties area on the Configuration screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 35 Events screen available from the Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Figure 36 Allocating CDR, SNMP Alarm, and Log report functions to each Event Name. 65

Figure 37 Current password field on the Administrator tab . . . . . . . . . . . . . . . . . . . . . . . . . 70

Figure 38 New password field on the Administrator tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Figure 39 Confirm new password field on the Administrator tab . . . . . . . . . . . . . . . . . . . . 71

Figure 40 Changing the administrator password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figure 41 New password field on the Supervisor tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Figure 42 Confirm new password field on the Supervisor tab . . . . . . . . . . . . . . . . . . . . . . . 72



8


Figure 43 TGW logging conceptual model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Figure 44 TGW Events Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Figure 45 Publisher Log Level Concept: the Publisher log level setting should be treated like

a slider control - increase or decrease the Publisher level so fewer or more individual events get

logged. 78

Figure 46 The Publisher configuration parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Figure 47 The Listener configuration parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Figure 48 List of log files in the Log screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Figure 49 Log File Display screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Figure 50 Selecting the log file to download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85



DN0182152

Issue 1-3 en

9


List of Tables

Table 1 Types of mobile subscribers (defined) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Table 2 Overview to Administrator Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 3 Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Table 4 TGW documentation set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Table 5 Related administrator documents for the AG product line. . . . . . . . . . . . . . . . . . 19

Table 6 Documentation related to the MMSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Table 7 Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Table 8 Overview of navigational buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Table 9 Browser compatibility issues between online help and context-sensitive help . . 32

Table 10 Ways to define subscriber searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Table 11 Information under the Class of Service Plans toolbar . . . . . . . . . . . . . . . . . . . . . 46

Table 12 Description of tabs available from the Configuration screen. . . . . . . . . . . . . . . . 56

Table 13 Log levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Table 14 Additional documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Table 15 Appendix A: Acronyms and Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Table 16 Field descriptions for the Create Subscriber screen. . . . . . . . . . . . . . . . . . . . . . 103

Table 17 Descriptions of COS features listed on the Create Subscriber screen . . . . . . . . 105

Table 18 Description of available TGW events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Table 19 Properties set during installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Table 20 Properties that should not be changed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121



10




Preface

DN0182152 11


1 Preface

The preface provides the following introductory topics:

• Product description for TGW

• About this document

• Audience

• Scope

• Typographic conventions

• TGW documentation

• Related documentation

• If you have documentation comments

• Revision history

1.1 Product description for TGW

Nokia Multimedia Terminal Gateway (TGW) is a companion application to the NokiaArtuse™ Multimedia Messaging Service Center (MMS Center). The MMS Centerdelivers messages composed of text, images, and other media types between multimediaterminals.TGW extends the MMS Center by providing storage and views of multimediamessages. In addition, TGW provides multimedia support for legacy phone owners viaSMS notification, allowing legacy phone owners to view their multimedia messages viathe Web.

1.2 About this document

This document is the Administrator Guide for the Nokia Multimedia Terminal GatewayRelease 1.0.3 . TGW is part of the Multimedia Messaging Service Application Suite.

The Administrator Guide describes routine tasks for administering TGW. These tasksinclude managing TGW subscribers, managing Class of Service plans, configuring

parameters, changing administrator account settings, and displaying log files.

Note: If you are administering Nokia Multimedia E-mail Gateway (EGW) and/or Nokia Multimedia Voice Gateway (VGW) in addition to TGW, refer to theseparate EGW Administrator Guide or VGW Administrator Guide forspecific information on these applications.

The screen captures in this documentation reflect a system that has onlyTGW installed.

For a product description of EGW and VGW, see Appendix B.



12


1.3 Audience

This document has two intended audiences:

• System administrators who work directly for operators and who use MMSApplication Administrator to configure and troubleshoot airtime services for TGWsubscribers.

• System supervisors who only access the Subscribers screen of the MMS ApplicationAdministrator for the sole purpose of managing TGW subscribers. The followingfigure and table illustrate the various mobile subscribers to which TGW and relateddocumentation refer.

1.4 Mobile subscriber types

Figure 1 and Table 1 provide an overview of the types of mobile subscribers

Figure 1 Overview of mobile subscribers

Mobile subscriber Description

Subscriber Refers to anyone using a mobile phone.

Legacy phone owner Refers to a subscriber whose mobile, SMS-capable phone does not have multimedia capabilities.

Table 1 Types of mobile subscribers (defined)

Legacy Phone Owners

SMS Capable

MMT Owners

MMS Capable

TGW Subscribers

Mobile Subscribers

EGWSubscribers

VGWSubscribers



Preface

DN0182152 13


1.5 Scope

The following table describes the major sections in this document.

Note: Most chapters of this document apply only to the system administrator;however, some chapters apply to both the system administrator and thesystem supervisor. Refer to the following table to determine how/if eachchapter relates to these two audiences.

MMT owner Refers to a subscriber whose mobile terminal hasmultimedia capabilities.

TGW subscriber Refers to a mobile phone owner who subscribes to NokiaMultimedia Terminal Gateway (TGW) services andtherefore has a PA (Personal Album).

Non TGW subscriber Refers to a mobile phone owner who does not subscribeto Nokia Multimedia Terminal Gateway (TGW) andtherefore does not have a PA (Personal Album).

EGW subscriber Refers to a mobile phone owner who subscribes to NokiaMultimedia E-mail Gateway (EGW) services. For adescription of EGW, see “Product descriptions for EGWand VGW” on page 101.

VGW subscriber Refers to a mobile phone owner who subscribes to NokiaMultimedia Voice Gateway (VGW) services. For adescription of VGW, see “Product descriptions for EGWand VGW” on page 101.

Mobile subscriber Description

Table 1 Types of mobile subscribers (defined)

Chapter Description Audience

Getting Started Describes how to log in and log out ofthe TGW MMS ApplicationAdministrator as well as how tonavigate the application via buttons,

toolbar options, tabs, operational buttons, and links.

Also provides important cautions ortips, such as saving changes on eachscreen and avoiding use of theReload/Refresh button.

System Administratorsand System Supervisors

Table 2 Overview to Administrator Guide



14


Managing TGWsubscribers

Describes using the Subscribers screen.

Also describes these tasks: creatingand assigning Class of Service,adding, editing, deactivating/activating TGW subscribers, andsearching for TGW subscribers.

System Administratorsand System Supervisors

Managing Classof Service plans

Describes using the Class of Service screen. A Class of Service (COS) is agroup of features that may beconfigured for a group of wirelessterminal users.

Also describes how to manage Classof Service plans, including creatingnew Class of Service plans anddeactivating/activating existingClass of Service plans.

System Administrators

Configuring parameters

Describes using the Configuration screen.

Also describes tasks managingsystem properties and events.


Changingadministratoraccount settings

Describes using the Administrator Account screen.

Also describes how to change theadministrator and/or supervisor

password.


Displaying thelog file

Describes using the Log screen.

Also describes displaying anddownloading a log file.


Troubleshooting

Tips

Describes troubleshooting for issues

such as configuring the MMSC,SMS message building, and theSMTP server.


Appendix A Defines acronyms and terminology. System Administratorsand System Supervisors

Chapter Description Audience

Table 2 Overview to Administrator Guide (Continued)





16


Note: This information provides explanatory information.

Tip: This information provides helpful guidelines for easy operation.

1.7 TGW documentation

For more information on Nokia Multimedia Terminal Gateway Release 1.0.3 (TGW R1),refer to the complete TGW documentation set, as described in the following table.

Convention Description

Courier Font Used for file names, lines of

code, names of processes, and

commands.

Heavy courier Used for command line user input.

Bold Used for textual parts of graphical user

interface, including menu items, buttons,toolbar names and options, and tabs.

Italics Used for screen names and document titles.

Bold I talics Used for emphasis.

< Italics> (Angle Brackets) With italics text, used for variable data.

[___] (Square Brackets) Used for optional data such as commandline arguments and database fields.

\ Backslash at the end of lines indicates that

there is insufficient space and the line iscontinued in the space below.

| Vertical bar used between choices, forexample in variable data in configurationfile arguments.

“” Used for section and chapter titles.

Table 3 Typographic conventions



Preface

DN0182152 17


Document Document number Audience description

Administrator’sWeb-based Help Not Applicable Intended for systemadministrators who workdirectly for the operators andwho are responsible forconfiguring andtroubleshooting airtimeservices for subscribers.

Subscriber’sWeb-based Help

Not Applicable Intended for TGW subscriberswho are accessing theirmessages via their multimedia-messaging terminal.

Subscriber’sWAP-basedHelp

Not Applicable Intended for TGW subscribersand non TGW subscribers whoare accessing TGW with theWireless Application Protocol(WAP).

Guide to Documentation

DN01154073 Intended for anyone seekingguidelines on how to use theTGW documentation set.Describes each document in theset. Also includes informationon receiving documentationupdates and ordering

documentation.

TGW SubscriberContent

DN0182164 Intended for operators as boilerplate content that theoperators can customize fortheir TGW subscribers.Boilerplate content describeshow TGW subscribers use theMMT as it references TGW.

TGW R1CommissioningGuide

DN0182176 Intended for system expertswho install TGW R1 at operatorsites. In most cases, installers

are Nokia employees, thoughthey can also be installers fromthe operator or from a third-

party system integrator.

Table 4 TGW documentation set



18


Customizing theTGW Interfaces

DN0182188 Intended for system integratorsand operators who are

customizing field labels, screencolors, online help, and remotelog in procedure for thesubscriber, non TGWsubscriber, and WAP interfaces.Also intended for translatorswho are responsible fortranslating the subscriber, nonTGW subscriber, and WAPinterfaces.

Third Party DevelopmentGuide

DN01161124 Intended for softwaredevelopers writing applicationsexternal to TGW but desiring tointegrate with TGW-suppliedfunctionality. Softwaredevelopers writing externalTGW applications can use thisdocument to gain anunderstanding of the TGWfunctionality that has beenmade available. For each TGWinterface exposed, thisdocument presents conceptualinformation, description of the

exposed interface, and exampleinteracting code.

TGW DatabaseSchema Guide

DN01161124 Intended for databaseadministrators who need toknow the schema that TGWuses to produce backups orqueries as well as therelationship between thevarious tables.

Release Notes DN0182191 Intended for installers. Alsointended for system

administrators who workdirectly for the operators andwho are responsible forconfiguring andtroubleshooting airtimeservices for TGW subscribers.


Table 4 TGW documentation set (Continued)



Preface

DN0182152 19


1.8 Related documentation

In addition to TGW, the Application Gateways product line at Nokia offers NokiaMultimedia E-mail Gateway (EGW) and Nokia Multimedia Voice Gateway (VGW).

The documents described in the following table provide steps on how to administer theserelated products.

Technical Notes Available online at

http://www.online.nokia.com

Intended for installers,administrators, and operators.


Table 4 TGW documentation set (Continued)


EGW AdministratorGuide

DN0182043 Intended for systemadministrators who workdirectly for the operatorsand who are responsiblefor configuring andtroubleshooting airtimeservices for EGWsubscribers.

VGW AdministratorGuide

DN023897 Intended for systemadministrators who workdirectly for the operatorsand who are responsiblefor configuring andtroubleshooting airtimeservices for EGWsubscribers.

Table 5 Related administrator documents for the AG product line



20


For more information on the Nokia Artuse™ Multimedia Messaging Service Center(MMSC), refer to the following documents, available online at this location:

http://www.online.nokia.com

For more information on Nokia Activ Server (NACS) 2.1, refer to the followingdocuments. You can find these documents in PDF format on the Nokia Activ Server 2.1 CD.

Nokia Activ Server Getting Started Guide

Nokia Activ Server Administration Guide

Document Document # Description

Graphical User Interface

DN00148723 Provides descriptive information aboutnavigating the MMSC GUI and

background on basic tasks.

Message Handling DN00148708 Provides information about multimediamessage format, routing, and howmessages are handled in the MMSC.

Installing and Integrating MMSC

DN00148798 Provides instructions for installing andconfiguring the MMSC.

Operating MMSC DN00148786 Designed for users who need proceduresfor daily, weekly, monthly, and occasionaloperations.

Configuring MMSC DN00148774 Provides comprehensive instructions onconfiguring the MMSC with a focus oncustomizing the product.

External Application Developer’s Guide

DN00148759 Provides guidelines for developinginterfaces for external applications.

Technical Manual DN00148747 Provides information on environment

variables, processes, configuration files,and database tables.

Table 6 Documentation related to the MMSC



Preface

DN0182152 21


1.9 If you have documentation comments

The Application Gateways product line at Nokia is always interested in improving itsdocumentation. We value your comments about this guide and other Nokiadocumentation.

Simply e-mail your documentation comments to Application Gateways at

[email protected]

In all your correspondence, please include the title of the document, its document number,release version, and the specific section upon which you are commenting.

1.10 Revision history

Table 7 shows a list of all revisions for this document.

Date Issue Release version

Jan. 29, 2002 1-0 en 1.0.

April 2002 1-1 en 1.0.1

July 2002 1-2 en 1.0.2

August 2002 1-3 en 1.0.3

Table 7 Revision history



Getting started

DN0182152 23


2 Getting started

This chapter describes how to get started using the MMS Application Administrator.

Intended audience. The intended audience for this chapter is TGW systemadministrators and system supervisors.

Topics in this chapter are as follows:

• Logging in/logging out

• Navigating the interface

• Navigational buttons

• Toolbar options

• Navigational tabs

• Operational buttons• Navigational links

• Warnings

• Cautions

• Known browser issues

2.1 Logging in/logging out

The following sections describe how to log in and log out of TGW.

2.1.1 Logging in as the administrator

To log in to TGW as the administrator, complete the following steps from the Log Inscreen:

1. Open a browser and enter the URL to access the MMS Application Administratorlogin screen. For example, enter:

http://ipaddress/en/webadmin/login.jsp

For ipaddress enter the ip address for the TGW server.

2. In the User name field, enter your user name.



24


Note: The user name for the administrator is admin.

Figure 2 User name field on the Log In screen

3. In the Password field, enter your password.

Note: The default password is tgw. Nokia recommends that you immediatelychange your password after logging in for the first time. Only administratorscan change the administrator or supervisor password. (“ChangingAdministrator Account settings” on page 69 for steps on changing

passwords.)

Figure 3 Password field on the Log In screen



Getting started

DN0182152 25


4. Click the Log In button.

The Subscribers screen appears. You are now logged in to MMS ApplicationAdministrator as the administrator.

Through the navigational menu in the left frame, the administrator has access to thefollowing screens: Subscribers, Class of Service, Configuration, Admin. Account ,

Log , and Help.

2.1.2 Logging in as the supervisor

To log in to TGW as the supervisor, complete the following steps from the Log In screen:

1. Open a browser and enter the URL to access the MMS Application Administratorlogin screen. For example, enter:

http://ipaddress/en/webadmin/login.jsp

For ipaddress enter the ip address for the TGW server.

2. In the User name field, enter your user name.

Note: The user name for the supervisor is supervisor.

3. In the Password field, enter your password.

Note: The default password is tgw. See your system administrator to change thedefault password.

4. Click the Log In button.

The Subscribers screen appears. You are now logged in to MMS ApplicationAdministrator as the supervisor. The supervisor has access to the Subscribers screen.



26


2.1.3 Logging out

To log out of TGW, complete the following step:

In the left navigational frame, which is available from all screens, click the Log Out

button.

You are now logged out of the system.The Log In screen appears, so you can log back into MMS Application Administrator.

2.2 Navigating the interface

To navigate the interface, use the following controls:

• Navigational buttons

• Toolbar options

• Navigational tabs

• Operational buttons

• Navigational links

2.2.1 Navigational buttons

To navigate the interface, click the buttons in the left navigational frame. The navigationalframe includes the following buttons: Subscribers, Class of Service, Configuration, Admin. Account, and Log buttons.

Button Description

Click the Subscribers button to add, edit, deactivate/activate,assign a COS plan to, or search for TGW subscribers.

Click the Class of Service button to add, edit, or to deactivate/activate a COS plan.

Table 8 Overview of navigational buttons



Getting started

DN0182152 27


2.2.2 Toolbar options

Toolbar options are available from MMS Application Administrator screens. Theseoptions access additional screens or operations from the Subscribers, Class of Service,Configuration, Administration Account , and Log screen s.

For example, from the Class of Service Plans toolbar, the options are New COS PlanandDeactivate.

Figure 4 Example of toolbar options

Click the Configuration button to view, reset, or update thegeneral system or events configuration.

Click the Admin. Account button to change the administrator orsupervisor password.

Click the Log button to view text log files.

Click the Help button for topics on how to use TGW.

Click the Log Out button to log out of MMS ApplicationAdministrator.

Button Description

Table 8 Overview of navigational buttons (Continued)



28


To create a new COS plan, click the Create New COS Plan option from the Class ofService Plans toolbar.

To deactivate selected COS plans, click the Deactivate option from the Class of ServicePlans toolbar.

2.2.3 Navigational tabs

Navigational tabs let you access additional screens available from the main MMSApplication Administrator screens.

For example, from the Configuration screen, the following navigational tabs areavailable: System and Events tabs.

Figure 5 Example of navigational tabs

Click the System tab to view the System screen that relates to configuration.



Getting started

DN0182152 29


Click the Events tab to view the Events screen that relates to configuration.

2.2.4 Operational buttons

In addition to navigational buttons, the interface for the MMS Application Administrator provides additional buttons for common operations.

An example of an operational button is the Search button on the Subscribers screen.Under the Subscriber Search Criteria toolbar, click the Search button to complete asubscriber search according to the criteria you define.

Figure 6 Search button as example of an operational button

Another example of an operational button is the Change button on the Administrator Account Settings screen. Under Administrator Account Settings, click the Change button to change your password.

Figure 7 Change button as example of an operational button

2.2.5 Navigational links

From the Subscribers screen, links are available under the Name category of the SearchResults area. From the Class of Service screen, similar links are also available under theName category of the Class of Service Plans area. The links let you access additionalscreens for editing subscriber information or Class of Service plans.

For example, to edit subscriber information (including name, MSISDN, e-mail address, orCOS), click the name for the subscriber information that you want to edit.

For example, under the Name category click the name Jon Keatsling.



30


Figure 8 Example of navigational link

Clicking the subscriber’s name lets you access the Edit Subscriber Information screen forthat subscriber.

Figure 9 Edit Subscriber Information screen



Getting started

DN0182152 31


In the same way, if you click a Class of Service plan under the Name category of the Classof Service screen, the link lets you access the Edit Class of Service screen

2.3 Warnings

This information helps avoid damage to the phone, personal injury, or property damage.

2.3.1 Avoid changing values for configuration parameters

Warning: Nokia recommends that you do not change values for configurationparameters; changing values for configuration parameters can result insystem failure. Change the values for configuration parameters only if Nokia Technical Support clearly recommends that you take suchaction.

2.4 Cautions

The information in the following topics helps avoid loss of data:

• Saving changes on each screen

• Avoiding the Refresh or Reload button

• Switching between the General and TGW tabs on the Edit Class of Service screen

• Switching between the System and Events tabs on the Configuration screen

• Making an entry in your billing system when you make events billable from theConfiguration screen/Events tab

2.4.1 Saving changes on each screen

Caution: When you make changes on any of the screens for MMS ApplicationAdministrator, it is important to save the changes on each screen before moving on to adifferent screen. You cannot save changes for multiple screens from a single screen.

2.4.2 Avoiding the Refresh or Reload buttons

Caution: Using your browser's Refresh or Reload button has no beneficial effect inMMS Application Administrator. If you use either the Refresh or Reload button, you willlose all the data you have on your current screen when MMS Application Administratorreturns you to the Subscriber screen.

2.4.3 Switching between the General and TGW tabs

Caution: When you switch between the General and TGW tabs on the Edit Class ofService screen, you must click Update (before switching to the next tab), or you will loseyour data.





Managing TGW subscribers

DN0182152 33


3 Managing TGW subscribers

This chapter explains how to use the MMS Application Administrator Subscriber Search

Criteria screen.

Intended audience. The intended audience for this chapter is TGW systemadministrators and system supervisors.


• Getting started

• Using the Subscriber Search Criteria screen

• Adding TGW subscribers

• Editing TGW subscribers

• Deactivating TGW subscribers

• Deleting TGW subscribers

• Activating TGW subscribers

• Assigning Class of Service plans to TGW subscribers

• Searching for TGW subscribers

3.1 Getting started

Click the Subscribers button in the left navigational frame to add, edit, deactivate,activate, assign Class of Service plans to, and search for TGW subscribers.

Tip: To add subscribers, follow these steps: 1.) From the Class of Service Planscreen, create a Class of Service plan (only the administrator can completethis step). 2.) From the Subscribers screen, add the subscriber, whichincludes selecting the COS plan to assign to that subscriber.



34


3.2 Using the Subscriber Search Criteria screen

The Subscriber Search Criteria screen presents Search Results toolbars.

3.2.1 Subscriber Search Criteria toolbar

The fields under the Subscriber Search Criteria screen let you locate TGW subscribersaccording to the following predefined criteria: Last Name, User Name, MSISDN, E-mail, COS (Class of Service), and Billing ID.

Figure 10 Fields available under the Subscriber Search Criteria screen

In the Show field, you can define whether to show All TGW subscribers, Active TGWsubscribers only, or Inactive TGW subscribers only. The default is Active.

In the Records per page field, you can define the scope of your search as 50, 100, or 500.The default is 50 records.

To complete your search, click the Search button.

3.2.2 Search Results toolbar

The area under Search Results toolbar shows the TGW subscribers that meet the criteriayou have defined.

Figure 11 Area under the Search Results toolbar

The Search Results area shows each TGW subscriber’s Name, User Name, MSISDN,E-mail address, and COS (Class of Service).




DN0182152 35


The Search Results toolbar options are as follows:

Assign COS option - lets you assign Class of Service plans to TGW subscribers in thedatabase.

Create New Subscriber option - lets you add new TGW subscribers to the database.Deactivate option - lets you deactivate TGW subscribers.

Note: When you deactivate TGW subscribers, you are making the TGW subscriberaccounts inactive. If a deactivated TGW subscriber has a unique MSISDN,then you can reactivate that subscriber at any time by selecting the Activeoption on the Edit Subscriber Information screen. An active user must havea unique MSISDN.

3.3 Adding TGW subscribers

To add TGW subscribers, follow these steps:

Tip: Before you can add a subscriber on the Subscribers screen, the systemadministrator must first define a Class of Service on the Class of Service

Plans screen.

(“Creating new COS plans” on page 47.)

1. From the Search Results toolbar, click the Create New Subscriber option.

The Create Subscriber: Step 1 of 1 screen appears.



36


Figure 12 The Create Subscriber: Step 1 of 1 screen

2. Complete the information required for each of the fields under the General tab.

Note: The * indicates a required field.

Refer to Appendix C for descriptions and examples of the information required in each ofthe fields.

3. Click Finish.




DN0182152 37


3.4 Editing TGW subscribers

To edit TGW subscribers, follow these steps:

1. Click the name of the TGW subscriber for whom you want to edit subscriberinformation.

The TGW subscriber’s user name is a link to the Edit Subscriber Information screen.

Figure 13 Linking to Edit Subscriber Information screen

The Edit Subscriber Information screen appears.

Figure 14 The Edit Subscriber Information screen



38


2. Under the General tab of the Edit Subscriber Information screen, follow these steps:

a.) Place your cursor in the field next to any label to edit subscriber information.

b.) Enter the modified information.

c.) From the Edit Subscriber Information toolbar, click Update to save yourchanges to the database.

Note: Click the TGW tab to view the subscriber’s Class of Service information.

3.5 Deactivating existing TGW subscribers

You can deactivate existing TGW subscribers in two ways:

• Deactivating from the Subscriber Search Criteria screen

• Deactivating from the Edit Subscriber Information screen

3.5.1 Deactivating from the Subscriber Search Criteria screen

From the Subscriber Search Criteria screen, you can deactivate one or more subscribers atthe same time.

To deactivate TGW subscribers from the Subscriber Search Criteria screen, follow thesesteps:

1. In the check box(es), select the TGW subscriber(s) whom you want to deactivate.

Figure 15 Deactivating from the Subscriber screen

2. From the Search Results toolbar, click the Deactivate option.

MMS Application Administrator deactivates the selected TGW subscriber(s).




DN0182152 39


Note: When you deactivate TGW subscribers, you are making the TGW subscriberaccounts inactive. If a deactivated TGW subscriber has a unique MSISDN,then you can reactivate that subscriber at any time by selecting the Active option on the Edit Subscriber Information screen. An active user must havea unique MSISDN.

3.5.2 Deactivating from the Edit Subscriber Information screen

From the Edit Subscriber Information screen, you can only deactivate a single subscriber.

To deactivate a TGW subscriber from the Edit Subscriber Information screen, followthese steps:

1. Under the Search Results toolbar, click the user name for the TGW subscriber whomyou want to deactivate.

Figure 16 Deactivating from the Edit Subscriber Information screen

2. The Edit Subscriber Information screen appears.

Figure 17 The Edit Subscriber Information screen



40


3. In the Status field, change the Active option to Inactive.

Note: When you deactivate TGW subscribers, the subscriber information stillexists in the database. You can reactivate TGW subscriber accounts at any

time, and your TGW subscribers can resume using the service. To reactivatesubscriber accounts, change the Inactive option to Active on the EditSubscriber Information screen.

4. Click Update.

MMS Application Administrator deactivates the TGW subscriber.

3.6 Activating TGW subscribers

If a deactivated TGW subscriber has a unique MSISDN, then you can activate that

subscriber at any time.

To activate a TGW subscriber, follow these steps:

1. From the Subscribers screen, view inactive subscribers by completing a search for allsubscribers or by completing a search for inactive subscribers.

For example, under the Subscriber Search Criteria toolbar, select Inactive from thedrop-down list in the Show field. Under the Search Results toolbar, MMSApplication Administrator lists all inactive subscribers in gray.

2. Click the name of the inactive subscriber whom you want to activate.

The name is a link to the Edit Subscriber Information screen.

3. On the Edit Subscriber Information screen, change the Status field from Inactive toActive.

4. Click Update.

MMS Application Administrator activates the subscriber.

3.7 Deleting TGW subscribers

There are two ways to delete TGW subscribers:

• From the Edit Subscriber screen

Use the Edit Subscriber screen if you want to review more detail about a subscriber before deleting.

• From the Subscriber Search Criteria screen

Use the Subscriber Search Criteria to locate one or more subscriber records. You candelete multiple subscribers from the Subscriber Search Criteria screen.

To delete TGW subscribers from the Edit Subscriber screen, click Delete.

To delete TGW subscribers from the Subscriber Search Criteria screen:




DN0182152 41


1. Enter search criteria to create a list of one or more subscribers.

2. In the check box(es), select the TGW subscriber(s) whom you want to delete.

Figure 18 Deleting from the Subscriber screen

3. From the Search Results toolbar, click Delete.

MMS Application Administrator deletes the selected TGW subscriber(s).

3.8 Assigning Class of Service plans

To assign a Class of Service (COS) plan to TGW subscribers, follow these steps:

1. Under the Search Results toolbar, select the TGW subscribers to which you want toassign a COS.

Figure 19 Selecting TGW subscribers to which to assign a COS

2. From the Search Results toolbar, click the Assign COS option.

The Assign Class of Service pop-up appears.



42


Figure 20 Assign Class of Service pop-up

3. From the drop-down list box, select the COS to assign to the TGW subscribers youselected.

Note: The Class of Service name in the screen capture is only for illustration purposes. The administrator is responsible for creating the specific Class ofService plans that appear in this drop-down list. For more information oncreating new COS plans, “Creating new COS plans” on page 47.

4. Click OK .

3.9 Searching for TGW subscribers

To locate your TGW subscribers in the MMS Application Administrator’s database,complete the following steps under the Subscriber Search Criteria toolbar:

1. In the drop-down list next to the Search for field, select the criteria to define yoursearch.

Figure 21 Defining your subscriber search from the Search for drop-down list




DN0182152 43


The following table describes the possible ways to define your search.

2. In the field to the right of the Search for drop-down list, enter the last name, username, MSISDN, e-mail address, COS, or billing ID, depending on the criteria youdefine.

For example, if you define Last Name as your search criteria, enter the TGWsubscriber’s last name in the text box.

In the example that follows, the last name McKay appears in the text box.

Search Criteria Description

Last Name Enter the TGW subscriber’s last name, a prefix, or leave the field blank.

User Name Enter the TGW subscriber’s complete username.

Note: Must enter complete username to complete search.

MSISDN Enter the TGW subscriber’s MSISDN, a prefix, or leave the field blank.

The MSISDN is the mobile telephonenumber used by a TGW subscriber in aGSM/DCS network.

E-mail Enter the TGW subscriber’s e-mailaddress.Partial entries such as prefixes areallowed.

COS (Class of Service) Enter the TGW subscriber’s Class ofService (COS).

A Class of Service (COS ) is a group offeatures that may be configured for a group

of wireless phone users.Billing ID Enter the TGW subscriber’s billing ID

from the billing system.

Table 10 Ways to define subscriber searches



44


Figure 22 Searching for a subscriber by last name

Tip: You can also define searches based on starting prefixes. In the exampleabove, entering just M in the field to the right of the Search for drop-down listreturns results for all last names starting with the letter M in the database.Leaving the field blank will return all subscriber records up to the number of records you have specified.

If searching for MSISDNs, entering +1781 in the field to the right of theSearch for drop-down list returns results for all numbers starting with that

prefix.

You must enter a complete user name when searching by user name.



Managing Class of Service plans

DN0182152 45


4 Managing Class of Service plans

This chapter explains how to use the MMS Application Administrator Class of Service

Plans screen. A Class of Service (COS) is a group of features that may be configured for agroup of wireless phone users.

Values that define a TGW subscriber’s Class of Service include maximum New Album(NA) size, maximum Personal Album (PA) size, New Album (NA) storage time, PersonalAlbum (PA) storage time, and enabling/disabling self-provisioning (which includeschanging e-mail address, password, and address).

An active Class of Service plan is one that your TGW subscribers are using.

An inactive Class of Service plan is one that you have deactivated. Though the inactiveCOS plan still exists in the database, you cannot assign additional TGW subscribers tothat plan. Existing subscribers, however, who are members of an inactive COS, retain

membership in that COS plan.

Intended audience. The intended audience for this chapter is TGW systemadministrators.


• Getting started

• Using the Class of Service Plans screen

• Creating Class of Service plans

• Editing existing Class of Service plans

• Deactivating existing Class of Service plans

• Activating Class of Service plans

4.1 Getting started

Click the Class of Service button to add, edit, deactivate, or activate a Class of Service plan.



46


4.2 Using the Class of Service Plans screen

The Class of Service Plans screen presents the Class of Service Plans toolbar with Create New COS Plan and Deactivate options.

Figure 23 The Class of Service Plans screen

The following table describes the information that appears under the Class of ServicePlans toolbar.

Content on COS Plans Area Description

Name Lists your TGW Class of Service plan.

A Class of Service (COS) is a group offeatures that may be configured for a groupof wireless phone users.

Features that define a TGW COS includemaximum NA size, maximum PA size, NAstorage time, PA storage time, andenabling/disabling self-provisioning(which includes changing e-mail address,

password, and address).

Description Describes the terms of your TGW Class ofService plan.

Table 11 Information under the Class of Service Plans toolbar




DN0182152 47


4.3 Creating new COS plans

To create COS plans, follow these steps:

1. From the Class of Service Plans toolbar, click the New COS Plan option.

The Create Class of Service: step 1 of 2 screen appears.

Figure 24 The Create Class of Service:step 1 of 2 screen

2. Complete the following information under the General tab:

Note: * indicates required field.

a.) In the Status field, select the Active or Inactive option.

b.) In the Name* field, enter the name of the COS plan.

c.) In the Description field, enter a brief description of the COS plan features.

d.) From the Create Class of Service: step 1 of 2 toolbar, click the Next option.

Status Indicates whether the Class of Service planis active or inactive.

An active Class of Service plan is one thatyour TGW subscribers are using.

An inactive Class of Service plan is one thatyou have deactivated. Though the inactiveCOS plan still exists in the database, youcannot assign additional TGW subscribersto that plan. Existing subscribers, however,who are members of an inactive COS,retain membership in that COS plan.

Content on COS Plans Area Description

Table 11 Information under the Class of Service Plans toolbar (Continued)



48


Note: To cancel adding general COS information, you can click the Cancel optionat any time from the Create New Class of Service toolbar.

The Create Class of Service: step 2 of 2 screen appears.

Figure 25 The Create Class of Service: step 2 of 2 screen

3. Complete the following information under the TGW tab:

Note: * indicates required field.

a.) In the MAX NA size (MB)* field, enter the maximum size in megabytes of the New Album.

Note: No limit exists for the maximum size. The size MMS ApplicationAdministrator allows depends on the capacity of your disk drive.

b.) In the MAX PA size (MB)* field, enter the maximum size in megabytes of thePersonal Album.

Note: See note for step 3a.

c.) In the NA Storage time (Days)* field, enter the maximum time in days to storemessages in the New Album.

d.) In the PA Storage time (Days)* field, enter the maximum time in days to storemessages in the Personal Album.

e.) Next to the Self Provisioning field, select the Enabled option if you want to

provide TGW subscribers the ability to change password or e-mail address;otherwise, select Disabled.

f.) From the Create Class of Service: step 2 of 2 toolbar, click the Finish option.

Note: To cancel adding general TGW COS information, you can click the Cancel option at any time from the Create Class of Service: step 2 of 2 toolbar.Youcan also click the Previous option to see the information you entered on theGeneral tab.




DN0182152 49


4.4 Editing COS plans

Caution: When you switch between the General and TGW tabs on the Edit Class ofService screen, you must click Update on each tab (before switching to the next tab), oryou will lose your data.

Note: When you edit an item in a COS plan, you affect all the subscribers assignedto that COS plan.

To edit COS plans, follow these steps:

1. Under the Class of Service Plans toolbar, click the name of the COS you want to edit.

Figure 26 Selecting the COS plan to edit

The Edit Class of Service screen appears.

Figure 27 The Edit Class of Service screen






DN0182152 51


f.) Next to the Self-provisioning field, select the Enabled option to provide TGWsubscribers with the ability to change password or e-mail address; otherwise,select Disabled.

g.) From the Edit Class of Service toolbar, click the Update option.

4.5 Deactivating COS plans

When you deactivate a COS plan, the COS plan’s status changes from active to inactive.

An active Class of Service plan is one that you can assign to any TGW subscribers.

An inactive Class of Service plan is one that you have deactivated.Though the inactiveCOS plan still exists in the database, you cannot assign new TGW subscribers to that plan.Existing subscribers, however, who are members of an inactive COS, retain membershipin that COS plan.

You can deactivate existing COS plans from two screens:

• Class of Service Plans screen

• Edit Class of Service screen

4.5.1 Deactivating from the Class of Service Plans screen

From the Class of Service Plans screen, you can deactivate one or more COS plans at thesame time.

To deactivate COS plans from the Class of Service Plans screen, follow these steps:

1. In the check box(es), select the COS plan(s) that you want to deactivate.

Figure 29 Deactivating from Class of Service Plans screen



52


2. From the Class of Service Plans toolbar, click the Deactivate option.

MMS Application Administrator deactivates the selected COS plan(s).

Note: When you deactivate COS plans, the COS information still exists in thedatabase. You can reactivate the COS plan at any time. To reactivate theCOS plan, change the Inactive status to Active on the General tab of the

Edit Class of Service screen.

Deactivated plans still appear in gray on the Class of Service Plans screen atthe bottom of the screen, under the active plans.

4.5.2 Deactivating from the Edit Class of Service Information screen

From the Edit Class of Service screen, you can only deactivate a single COS plan.

To deactivate a COS plan from the Edit Class of Service screen, follow these steps:

1. Under the Class of Service Plans toolbar, click the name of the COS plan that youwant to deactivate.

Figure 30 Selecting the COS plan to deactivate




DN0182152 53


The Edit Class of Service screen appears.

Figure 31 The Edit Class of Service screen

2. From the General tab of the Edit Class of Service screen, change the option in theStatus field from Active to Inactive.

Figure 32 Changing COS status from Active to Inactive.

3. Click Update.

MMS Application Administrator deactivates the COS plan.

Note: When you deactivate COS plans, the information still exists in the database.You can reactivate the COS plan at any time by changing Inactive back toActive on the Edit Class of Service screen.

Note: To cancel deactivation of a COS plan, you can click the Canceloption at anytime from the Edit Class of Service toolbar.



54


4.6 Activating Class of Service plans

To activate a COS plan, follow these steps:

1. Click the name of the inactive COS plan that you want to activate.

The name is a link to the Edit Class of Service screen.

2. On the Edit Class of Service screen, change the Status field from Inactive to Active.

3. Click Update.

MMS Application Administrator activates the COS plan.




DN0182152 55


5 Configuring parameters

This chapter explains how to use the MMS Application Administrator Configuration

screen.



• Getting started

• Using the Configuration screen

• Managing system properties

• Managing TGW events

5.1 Getting started

Click the Configuration button in the left navigational frame to configure parameters andspecify TGW events for Call Detail Records (CDRs), SNMP alarms, and logging.

Note: Call Detail Records (CDRS) are billing records that contain all informationnecessary for a billing system to provide an invoice for a subscriber.

5.2 Using the Configuration screen

On the Configuration screen, you see the following tabs:

• System tab

• Events tab






DN0182152 57


5.2.3 System tab properties

After clicking a category in the folder hierarchy for configuration parameters, the properties for that category appear to the right in the Properties area of the screen.

Figure 34 Properties area on the Configuration screen



58


5.3 Managing system properties

After you click the Configuration button, the screen for the System tab is displayed. Youcan modify the default properties for a specific category or subcategory of the generalconfiguration parameters. If you must change the default properties for any category ofthe configuration parameters, enter the modified properties in the Properties text boxes.

Caution: Nokia recommends that you do not change values for configuration parametersdescribed in “Configuration Parameters” on page 119. Changing values for configuration

parameters can result in system failure. Change the values for configuration parametersonly if Nokia Technical Support clearly recommends that you take such action.

To modify properties for the general system, follow these steps:

1. In the folder hierarchy under Configuration Parameters, click a category orsubcategory. For example, click the billing folder.

The properties for that category appear to the right in the Propertiesarea of the screen.

2. Modify the properties for each item in the text boxes as necessary.

3. Click Update to enter or modify the properties.

MMS Application updates the property.

Caution: When you switch between the System and Events tabs on the Configurationscreen, you must click Update (before switching to the next tab), or you will lose yourdata.

Note: To return properties to the last saved values, click Reset from theConfiguration Parameters/Properties toolbar.

5.3.1 Billing properties

The billing properties define how to create and process charging data. Charging data isstored in a file called a Call Detail Record (CDR). CDRs contain all the informationnecessary for a billing system to provide an invoice for a subscriber. For more informationabout processing CDRs, refer to the Billing Interface Specification.

Folder to open

/ag/billing

Properties• cdrFileSize

Specifies the maximum size of CDR files (in bytes).

Default: 1000 bytes

• numberOfCdrFiles

Specifies the number of simultaneous CDR and XML files to create.

Default: 1




DN0182152 59


• maximumStorageTimeForCdrFiles

Specifies the maximum storage time allowed for CDR and XML files in hours.

Default: 72 hours

• processedCdrFileSystemName

Specifies where to store post-processed flat CDR files.

Default: /opt/wluser/TGWBilling

• rawCdrFileSystemName

Specifies where to store raw (in-process) CDR files.


• generateXmlCdrs

Specifies whether CDRs in XML format are generated.

Default: false• cdrXmlProcessingStartTimes

A comma-separated list of start times for CDR and XML post-processing (specifiedas hhmm, which is 24 hour clock format).

Default: 0130

• billingCenterUrlSet

A comma-separated list of billing center URLs for posting XML formatted CDRs.

Default: http://localhost/

• storeXmlCdrsfalse

Indicates whether or not to store XML CDRs in the file system.

Default: false

• sendXmlCdrsfalse

Boolean value to indicate whether XML CDRs should be sent to the billing center.

Default: false

• locationOfXmlCdrFiles

Specifies where to store XML CDR files.




60


5.3.2 SMS properties

The SMS properties define how SMS messages are displayed on mobile terminals forTGW subscribers and non TGW subscribers.

Folder to open

/ag/multimediamanager/sms

Subscriber SMS message

To modify the SMS message for TGW subscribers, modify the following property:

• SUBSC_TEXT_MSG

The text message cannot exceed 160 characters.

Default: New Multimedia Message in New Album

Non-subscriber SMS message

The non TGW subscriber text message is a combination of SMS properties you makeavailable. These properties are combined to create the non TGW subscriber SMSmessage. Any combination of these fields cannot exceed 160 characters. The message isconstructed using properties in the following order:

NON_SUBSC_TEXT_MSG + URL + MSG_ID_LABEL + MSG_ID + PASS_LABEL + password + SENDER_ID_LABEL + SENDER_ID + MSG_EXPIRATON_TIME_LABEL +MSG_EXPIRATON_TIME

Note: Some of the properties affect the appearance of other properties. Forexample, to display the URL in an SMS message, the value for theSHOW_URL property must be true and you must enter the address in the

URL property.

The following is a list of SMS properties and descriptions, presented in the order they areused to construct the SMS message.

• SHOW_NON_SUBSC_TEXT_MSG

Specifies whether or not to display the non TGW subscriber text message. Use theNON_SUBSC_TEXT_MSG property to specify the non-subscriber messageformat.

Default: true

• NON_SUBSC_TEXT_MSG

Specifies the non TGW subscriber SMS message. The non TGW subscriber SMSmessage is a the text string you enter for this field, plus the following SMS properties:

URL + MSG_ID_LABEL + MSG_ID + PASS_LABEL + password + SENDER_ID_LABEL +SENDER_ID + MSG_EXPIRATON_TIME_LABEL + MSG_EXPIRATON_TIME

Any combination of these fields cannot exceed 160 characters.

Default: New Multimedia Message in

• SHOW_URL

Specifies whether or not to display the URL for accessing a multimedia message.




DN0182152 61


Default: true

• URL

Specifies the URL to access for retrieving multimedia messages.

• SHOW_PASS_AND_MSG_ID

Specifies whether or not to display the password and message ID.

Default: false

• SHOW_MSG_ID_LABEL

Specifies whether or not to display the message ID label.

If you set SHOW_MSG_ID_LABEL to true, use the MSG_ID_LABEL property tospecify the actual label displayed.

Default: true

• MSG_ID_LABEL

Specifies the message ID label.

Default: Msg ID:

• SHOW_PASS_LABEL

Specifies whether or not to display the password label.

If you set SHOW_PASS_LABEL to true, use the PASS_LABEL property to specifythe actual label displayed.

Default: true

• PASS_LABEL

Specifies the password label.

Default: Password:

• SHOW_SENDER_ID

Specifies whether or not to display the sender ID.

Default: true

• SHOW_SENDER_ID_LABEL

Specifies whether or not to display the sender ID label.

If you set SHOW_SENDER_ID_LABEL to true, use the SENDER_ID_LABEL property to specify the actual label displayed.

Default: true

• SENDER_ID_LABEL

Specifies the sender ID label.

Default: From:

• SHOW_MSG_EXPIRATON_TIME

Specifies whether or not to display the message expiration time.



62


Default: true

• SHOW_MSG_EXPIRATON_TIME_LABEL

Specifies whether or not to display the message expiration time label.

If you set SHOW_MSG_EXPIRATON_TIME_LABEL to true, use theMSG_EXPIRATION_TIME_LABEL property to specify the actual labeldisplayed.

Default: true

• MSG_EXPIRATION_TIME_LABEL

Specifies the message expiration time label.

Default: Message will expire in:

See “Legacy message storage expiration” on page 63 for information about setting theexpiration time.

• MSG_EXPIRATION_TIME_UNITSpecifies the text for the message expiration unit of measurement.

Default: days

• SMS_DEFAULT_ROUTING_MSISDN

Specifies the default MSISDN routing number

5.3.3 Security

The subscriberPasswordRequired property specifies whether a password must bespecified when a subscriber is created or modified. If the password property is set to true,

then when the subscriber is created it must have a password. If it’s false, the password isoptional. However, if it is set to false, and the SMS password property is defined, then thesubscriber must enter a password to log in to TGW.

Folder to open

/ag/security

subscriberPasswordRequired:

Default: false

Range: true; false




DN0182152 63


5.3.4 Legacy message storage expiration

The ExpirationInterval property specifies the number of days a message is stored forlegacy devices.

Folder to open

/ag/msis/Tempstore

• ExpirationInterval

Default: 30



64


5.4 Managing events

The purpose of the TGW logging system is to record events generated by TGWcomponents. Upon receiving data, the logging system determines where to send the data.For example, log information is sent to a log file manager, alarm information is sent to atrap manager, and CDR information is sent to a billing manager. This process allows theappropriate manager to handle data according to specific events. For a list and descriptionof TGW events see “Description of available TGW events” on page 107.

After you click Events, the Events screen for this tab lists all of the events in the TGWsystem.

Figure 35 Events screen available from the Events tab

From the Events screen, you can specify if the events listed should be billable, trigger anSNMP (Simple Network Management Protocol) alarm, or cause an entry to be writtento the log. Any combination of these three choices can be assigned to each event. The listof events is read dynamically from the system.

Note: When you click Update, you simultaneously update the CDR , SNMPAlarm, and Log functions for each Event Name that you have selected viathe check boxes. You do not have to restart TGW for these changes to take

place.

TGW writes a Call Detail Record to a file that you can FTP from TGW to a billing system.CDRs contain billing information per transaction, for use by an outside billing package.CDRs will not be lost in the event of a system crash.




DN0182152 65


The following example shows how you can specify if the events listed generate CDRs,trigger an SNMP (Simple Network Management Protocol) alarm, or cause an entry to bewritten to the log. Any combination of these three choices can be assigned to each event

by selecting the appropriate check boxes next to the event names. The list of events is readdynamically from the system.

Figure 36 Allocating CDR , SNMP Alarm, and Log report functions to each EventName

5.4.1 Enabling billable events

You can make specific events billable; that is, enable TGW to generate a Call DetailRecord (CDR). CDRs are records that contain billing information per transaction, for use

by an outside billing package.

Caution: You must make an appropriate entry in your billing system when you makeevents billable in TGW.

To generate CDRs, follow these steps:

1. Click the Configuration button in the left navigational frame.

2. Click the Events tab.

3. Next to the corresponding event name(s), select the check box(es) under the CDR heading.



66


4. Click Update.

When you click Update, you simultaneously update the CDR , SNMP Alarm, andLog functions for each Event Name that you have selected via the check boxes.

5.4.2 Enabling SNMP alarms

Simple Network Management Protocol (SNMP) is a communication protocol thatmanages IP networks, including individual network devices.

One feature of SNMP is an alarm mechanism by which managed notes can notify SNMPmanagers of a problem (assuming that the device is configured to SNMP).

To enable SNMP alarms, follow these steps:


2. Click the Events tab.

3. Select the check box(es) under SNMP Alarm next to the corresponding eventname(s).

4. Click Update.


5.4.3 Enabling event logging

To create log entries, follow these steps:


2. Click the Events tab.3. Select the check box(es) under the Log column next to the corresponding event

name(s).




DN0182152 67


4. Click Update.




68




Changing Administrator Account settings

DN0182152 69


6 Changing Administrator Accountsettings

This chapter explains how to use the TGW Administrator Account screen.



• Getting started

• Using the Administrator Account screen

• Changing the administrator password

• Changing the supervisor password

6.1 Getting started

Click the Admin. Account button in the left navigational frame to change theadministrator or supervisor password.

6.2 Using the Administrator Account Settings screen

When you click the Admin. Account button, the Administration Account Settings screenappears.This screen provides two navigational tabs, depending on whether you arechanging an administrator or supervisor password:

• Administrator tab

• Supervisor tab

Click the Administrator tab to change your administrator password. As an administrator,you can manage your TGW subscribers, manage Class of Service plans, configure yoursystem, and view your system log.



70


Click the Supervisor tab to change the supervisor password. Tasks that a supervisor can

complete are as follows: adding, editing, deactivating, activating, assigning Class ofService plans, and searching for TGW subscribers.

6.3 Changing the administrator password

To change the administrator password, follow these steps:

1. In the text box for the Current password field, enter your current password.

Figure 37 Current password field on the Administrator tab

2. In the text box for the New password field, enter your new password.

Figure 38 New password field on the Administrator tab



Changing Administrator Account settings

DN0182152 71


3. In the text box for the Confirm new password field, re-enter your new password.

Figure 39 Confirm new password field on the Administrator tab

4. Click the Change button.

Figure 40 Changing the administrator password

MMS Application Administrator changes the administrator password.



72


6.4 Changing the supervisor password

Under the Supervisor tab, you can change the supervisor password.

Follow these steps:

1. In the text box for the New password field, enter the new supervisor password.

Figure 41 New password field on the Supervisor tab

2. In the text box for the Confirm new password field, re-enter the new supervisor password.

Figure 42 Confirm new password field on the Supervisor tab

3. Click the Change button.

MMS Application Administrator changes the supervisor password.



Managing Log Files

DN0182152 73


7 Managing Log Files

The purpose of the TGW logging system is to record and manage events generated by

different TGW components.

Events are notification messages that acknowledge the success, failure, or condition ofrequests made by an TGW subsystem. TGW is capable of generating many events relatedto various actions. For example, an event could confirm that a message was stored in a

personal album.

Upon receiving event information, the logging system determines where to send the dataand how to act on it. Using the Events screen in the MMS Application Administrator ,administrators can designate which events are written to the TGW log file, which ones are

billable, and which ones trigger an SNMP alarm. TGW uses three “Listeners” forhandling various kinds of event-generated information: a File Handler, a Billing Manager,and a Trap Manager. For example, log information is sent to the File Handler, CDR

information is sent to the Billing Manager, and alarm information is sent to the TrapManager.

This chapter explains various aspects of the logging system, including the logging levels,and shows how to use the TGW Log screen.



• Overview of the Logging System

• Logging Levels

• Publishers

• The Logger

• Listeners

• Reading the Log Screen

• Displaying a log file

• Downloading a log file

• How to Interpret the Log File



74


7.1 Overview of the Logging System

In TGW, the logging system constantly monitors and manages system events in the background. As system events occur, they get generated as SNMP alarms, written to CDR billing files, or written to the TGW log files.1

To the administrator then, the logging system operates as a single module. Conceptually,however, the logging system consists of several components that collectively organizelogging activity. These components include:

• Publishers

• The Logger

• Listeners

Figure 43 depicts the TGW conceptual model for event logging. Essentially, TGW publishes events and acts upon them according to the way they are configured in the

Events screen of the MMS Application Administrator .The flow of logging activity is as follows:

1. TGW Publishers send events to the Logger component, which identifies the sendingPublisher by its componentID.

2. The Logger sends log records to the queue, which is a standard Java MessagingService (JMS) queue. If Persistence is turned on for a particular Listener, then a copyof each record is first stored in an external file for backup in the event of a systemcrash.

3. The Listeners trap the appropriate event information and act upon it according to thechoices you made in the Events screen (whether you have “CDR,” “SNMP Alarm,” or

“Loggable” selected for each event). This means that depending on your choices forany given event:

• The Billing Manager writes billing information to CDR files.

• The Trap Manager generates SNMP alarms to the administrator console.2

• The File Handler writes to the log file.

1. Access log files by clicking the Log button in the MMS Application Administrator .

2. SNMP alarms can be used by NMS applications to help monitor IP networks.



Managing Log Files

DN0182152 75


Figure 43 TGW logging conceptual model

7.1.1 Events Screen

A portion of the Events screen is shown below. This is where you can configure individualevents to be written to a log file, CDR file, or generated as an SNMP alarm. You canaccess this screen from the MMS Application Administrator by clicking theConfiguration button, and then clicking on the Events tab.

The choices you make from this screen directly affect how each event gets handled by thelogging system.

Figure 44 TGW Events Screen

Pub. 1

Pub. 3

Pub. 2 Logger Logging Queue Trap Manager

File Handler

Billing Manager

File

Persistence

LogData

EventPublishers Listeners

....



76


7.2 Logging Levels

TGW generates many different events through its Publishers, each with their own defaultlog level settings. It is important to understand the logging levels used by individualevents and their Publishers. The levels determine the amount of event information thatgets recorded to the TGW log file.

There are eight logging levels, numbered 0-7, as shown in Table 13.

Warning: Individual events have fixed log levels, preset by Nokia to be at theoptimum level. You can view these by opening the Event Repository inthe folder ag/evtRpt. However, these levels are for viewing andshoul d not be changed . There is a system performance decrease everytime the repository is rewritten. Publisher log levels, however, can bechanged at run-time. Change a Publisher log level to increase ordecrease the amount of log information for a class of events which areproduced by that Publisher.

Level Category Description

7 Severe Indicates an unexpected, critical error occurred. In general, itdescribes events that are very important and that prevent normal

program execution.

6 Warning Indicates the generated event is a potential problem, and notnecessarily an error. This event does not necessarily hampersystem functionality.

5 Info Indicates the generated event is merely an information message,and not a warning or error. Typically, Info messages will bewritten to the administrator console and are of interest toadministrators.

4 Config Used for indicating that there has been a configuration change inthe system parameter. This is intended to assist in debugging

problems that may be associated with a particular configuration.

3 Fine Levels 1-3 differ only in the granularity of the logging detail.For example, Finest is the most verbose and produces the mostamount of tracing information. Fine messages might includeminor failures which are recoverable. Setting a Publisher log

level to 1 (Finest) ensures a maximum amount of logging for itsclass of events. This is especially useful for troubleshooting

problems occurring with a particular event class, such as billing.

2 Finer

1 Finest

0 Off Turns off logging.

Table 13 Log levels



Managing Log Files

DN0182152 77


7.3 Publishers

“Publishers” refer to component-level objects that are responsible for sending eventlogging information to the logging queue for processing. Each Publisher is directlyassociated with a major subsystem level in the database, such as Billing, SNMP, and theMMSC. Each Publisher can produce several events related to the subsystem it represents.For example, the Billing Publisher sends only billing-related events to the Logger, whilethe MMSC Publisher sends only events pertaining to the MMSC.



78


7.3.1 Log Levels for Publishers vs. Events

Events have their own preset log levels, which can be viewed in the System screen underthe ag/EvtRpt folder (note that events are listed by Event ID). Publishers also have

their own log level settings. Since Publishers produce entire classes of events, it followsthen that the Publisher log level affects an entire class of events and not just a single event.

An individual event’s log level must be greater or equal to its Publisher log level in orderfor that event to be logged. If the log level of a single event is less than its Publisher’s loglevel, then the event is discarded and not logged. For example, if a single MMSC-relatedevent such as MMSC_RECEIVER_CREATE_FAILED_CRITICAL is set to 4, and theMMSC Publisher’s log level is set to 5 or higher, then that event is discarded and notlogged. However, if the MMSC event’s log level is 5 or higher, than it will be logged

because its Publisher level is 5.

A useful analogy for understanding the difference between log levels for a Publisher anda single event is a typical volume control slider mechanism. Log levels for single eventsare fixed at certain levels (preset by Nokia), and should not be changed. Publisher loglevels, however, can be changed at run-time in order to increase or decrease the number oflogs for a class of events (e.g., billing events, SNMP events, etc.). Treat the Publisher loglevel as a mechanism to use at any time to fine-tune the publishing rate of whole classes ofevents. Never change log levels for individual events.

Figure 45 Publisher Log Level Concept: the Publisher log level setting should betreated like a slider control - increase or decrease the Publisher level so feweror more individual events get logged.

1

7

log levelPublisher

log levelSingle Event

6

5

4

3

2

Use the Publisher log level setting toincrease and decrease log entries for an entire class of events.

Fixed at one levelConfigurable

0

1

7

6

5

4

3

2

0

more log entries

fewer log entries



Managing Log Files

DN0182152 79


7.3.2 Publisher Configuration Parameters

Folder Location: ag/logger/publisher

• logLevel — This property sets the loglevel for an individual Publishersubsystem, which affects an entireclass of events. Each Publisher has adefault log level setting of 7, whichcan be changed at run-time. See“Changing the Log Level forPublishers” for more details.

• componentID —Do not change the componentI D! Changing this setting mayresult in events not being filtered properly. Each Publisher has a unique componentIDthat serves as an identifier. The Logger references this ID when a Publisher sends a logrecord in order to help filter records.

If you change the log level value, click Update on the Properties toolbar to save thechange.

7.3.3 Changing the Log Level for Publishers

Folder Location: ag/logger/publisher

Every Publisher has a default log level of 7, which means that only “Severe” events in itsclass will be written to the log file; that is, only individual events with log levels of 7.Unlike the log levels for individual events, you can change default log levels forPublishers at run-time. In most cases you will not need to change the Publisher log levels.However, there are valid reasons for lowering or raising Publisher log levels.

Lowering a Publisher’s log level causes more individual event log entries to be generatedfor that Publisher. A Publisher log level of 1, for example, will generate the most logentries for a particular Publisher. Conversely, a Publisher level of 7 will generate thefewest possible log entries for that Publisher, since only “Severe” events will be logged.

One key reason why you might want to decrease the Publisher log level is to troubleshoot problems in a particular TGW subsystem. For example, if there is an overall problem withTGW’s billing functionality, it may make sense to lower the Billing Publisher log level to1 (Finest) to maximize the volume of billing information that gets logged. You could thenread the log file contents to aid in troubleshooting the problem.

One reason to increase the Publisher level is to prevent unnecessary events from being

logged, which could drain system performance. So, for example, a log level of 7 wouldensure that only the most critical events get recorded.

Refer to “Logging Levels” for more information on what each logging level means.

To view or change the log level of a Publisher, complete the following steps:

1. In the MMS Application Administrator , click the Configuration button.

2. After a few seconds, the configuration parameters appear in a tree-view in the left pane of the System screen.



80


3. Under the top-level ag folder, click logger and then publisher. There are twelvePublishers listed, each related to a subsystem in TGW. Click on any of the Publishersubsystems to see its properties.

4. To enter a new log level (0-7) for any of the Publishers, type a number in the logLevel

field. All Publishers use a default log level of 7.

5. To accept the new value, click the Update button in the top right-hand corner of theSystem screen.

Note: A logLevel of 0 turns off logging for that Publisher’s events.

Figure 46 The Publisher configuration parameters

7.4 The Logger

In the conceptual model for the TGW logging system, the Logger component handles allmessage filtering. The Logger directs messages generated by Publishers to the loggingqueue, where they are sorted by the Listeners depending on whether an event has beendesignated for a log file, CDR billing file, or an SNMP alarm. The Logger uses someconfiguration parameters, which are detailed in the next section.

7.4.1 Logger Configuration Parameters

Folder Location: ag/logger

• debugLevel — This property sets the administratorlevel for debugging the Logger. A setting of 0-3 allowsevents to be written to the administrator console, while4-7 turns off logging to the console. Essentially, if thislevel is set to 4 or above, no events will be written to theadministrator console. The default level is 3 (on). Thisvalue can be changed at run-time.

Do not change the

componentI D fi eld

for any Publi sher.



Managing Log Files

DN0182152 81


Folder Location: ag/logger/fileHandler

The File Handler writes the log records to the default log file tgwlog . The configuration parameters in this folder all relate to this log file.

• mountName — This is the Unix mountname where the TGW log files are stored. Inmost cases this is the same as the basedirectory name.

• baseFileName — This is the name of the logfile that TGW creates. This value can bechanged at run-time.

• rotationCounter — This determines thetotal number of log files that gets created insuccession. Log files operate on a rotationcycle; that is, when one file reaches its

maxFileSize limit (see below), eventinformation is written to a new file until thatreaches its limit, and so on. TherotationCounter value determines thenumber of new log files that get created

before the first one is overwritten with newevent information. If you specified a value of 1, then only one log file will be used andwill be overwritten when it reaches its maxFileSize limit. The default is 10, whichmeans that log data will be written across 10 separate log files before returning tooverwrite the first one. This value can be changed at run-time.

• baseDirName — This is the full path where the TGW log files are stored. This valuecan be changed at run-time.

• maxFileSize — Indicates the maximum size of the log file(s) that get created.Generally, this should be left at the default setting of 2.0 MB.

If you change any of the field values, click Update on the Properties toolbar to save thechanges.

7.5 Listeners

Listeners retrieve event information stored in the Weblogic Java Messaging Service(JMS) logging queue, and then act on it in different ways. Each Listener acts on theinformation that is applicable to it, as explained below:

• The File Handler retrieves log records and writes them to the file specified in thefileHandler parameter (tgwlog by default).

• The Billing Manager retrieves only billing information and generates CDRs forthe log records.

• The Trap Manager retrieves only alarm information and generates an alarm to theSNMP console. These alarms can be retrieved by Network Management System(NMS) applications.



82


7.5.1 Listener Configuration Parameters

Location: com.nokia.ag.logger.listener

• requestTypes — Lists all the events associated with this Listener, by event ID. A 5-digit ID number gets inserted into this field whenever you configure an event in the Events screen. For example, if you select the “Log” check box for a certain event in the Events screen, its event ID will appear in the requestTypes field under thecom.nokia.ag.logger.listener.logger parameter. If you select the“SNMP Alarm” check box for an event, its ID will appear in the requestTypes fieldunder the com.nokia.ag.logger.listener.trapManager parameter.

• logLevel — Log levels are not currently used in TGW.

• persistentType — Determines whether event data is kept persistent, which meansthat a copy of the event information is kept in a separate file before entering thelogging queue. Turning this on ensures that event information is not lost in the eventof a system crash. 1=On; 0=Off. The default is 1. See “Safeguarding Against EventLog Loss” for more information about log persistence.

• destinationID —Do not change the destinationID! Changing this setting may prevent logs, alarms, or CDRs from being generated. For example, if you change thedestinationID for the Billing Manager, CDRs may not be generated. Each Listener hasa unique destinationID that serves as an identifier. The Logger references thedestinationID in order to send log records to the appropriate Listener.

If you change any of the field values, click Update on the Properties toolbar to save thechanges.

Figure 47 The Listener configuration parameters

Do not change the

destinati onID field for any Li stener.



Managing Log Files

DN0182152 83


7.5.2 Safeguarding Against Event Log Loss

Normally, event information is constantly moving through the logging queue. In the eventof a system crash, information that happens to be in the logging queue at the time of the

crash may be lost. However, a logging feature called Persistence helps to avoid this.When Persistence is turned on, copies of the current event strings are kept in a separate file before entering the queue. If a system crash occurs, this information will be restored in thequeue. Essentially, Persistence is a means of temporarily backing up event data.

Each Listener contains a configuration parameter (persistentType) that allows you toenable or disable persistent logging. By default, TGW turns on Persistence for allListeners.

7.6 Reading the Log Screen

Click the Log button in the left navigational frame to display the log file. A list of log filesappears in the Log screen, as shown in Figure 48. Remember that the number of log fileslisted depends on the value of the rotationCounter parameter in the folder ag/logger/

fileHandler. This setting allows you to partition event information into separate logfiles.

Use the Log screen to display or download the content of individual log files. The names

for each log file appear as links under the Log Files column. The Size column lists the size(in KB) of each log file. The Date column lists the date and time of the last entry to eachlog file. The Download column provides links to the downloadable files.

Figure 48 List of log files in the Log screen



84


7.7 Displaying a log file

To display log files, click the link to the log file under the Log Files column that you wantto view.

The content for the log file appears in the Log File Display screen. See “How to Interpretthe Log File” for information about the log file display contents.

Figure 49 Log File Display screen

Each message begins with the event name, which displays in UPPER CASE.A single event message consists of several comma-separated fields.



Managing Log Files

DN0182152 85


7.8 Downloading a log file

You can choose to download and save log files on your computer. To download a log file,complete the following steps:

1. Click the Download link for the log file that you want to download.

Figure 50 Selecting the log file to download

2. Follow the instructions that appear and save the log file to the desired location.

Caution: Downloading log files from IE 5.1

If you are using IE 5.1 (5.01 with SP2) and you click the Download link on the Log screen,then MMS Application Administrator displays the log on the screen; however, if the log is

empty, the downloading process for the file begins.

This is a known issue for IE 5.1 only. The functionality works properly with IE 5.5 and Netscape versions (4.7 and higher).



86


7.9 How to Interpret the Log File

This section explains how to interpret the contents displayed in the log file.

All events are written to the log file as a line of text, which constitutes a log entry. A singlemessage includes several comma-separated fields. Some of these fields are fixed, such asthe Event Description and Logger ID. Some fields are dynamically generated, such as theactual message text. Also note that some fields can be null, while others must contain aknown value.

Some of the fields, such as Class Name, Method Name, and Logger ID, are useful mainlyfor Nokia technical support staff. Some of the more important fields for normal useinclude the Event Description, Event Level, Timestamp, and Text.

A logging message consists of the following fields, in the order shown:

Event Name, Event Level, Publisher ID, Executing Thread

Name, Class Name, Method Name, Sequence Number, Timestamp,

Event ID, Text Entry.

For example:

WEB_SUBSCRIBER_COMPOSE_MSG,Info,9004,ExecuteThread: '30' forqueue: 'default',null,null,108,Thu Apr 04 11:24:17 EST2002,UI_WEB_SUBSCRIBER_COMPOSE_MSG_EVENT,WEB SUBSCRIBERCOMPOSE MSG EVENT TRIGGERED: msisdn +19985551234

• Event Name — This field is the descriptive name of the event stored in the database.This field cannot be null.

• Event Level — This field is the log level of the event (e.g., Finest, Warning, Info).

See “Logging Levels” for explanations of all the levels. This field cannot be null.• Publisher ID — This field is the componentID that the Logger uses to identify the

TGW subsystem publishing the event (i.e., the Publisher). This field cannot be null.

• Executing Thread Name — This field is the Java executing thread that generates theevent log. This field cannot be null.

• Class Name and Method Name — The names of the Java class and method thatgenerates the event log. These fields can be null.

• Sequence Number — This field is the system-generated sequence number. This fieldcannot be null.

• Timestamp — This field is the system time and date when the event was logged. This

field cannot be null.• Description ID — This is an identifier used for an event’s description. Usually, this

text string is more detailed than the Event Name. This field can be null.

• Text Entry — This field contains the actual text that was logged. This field can benull.



Troubleshooting Tips

DN0182152 87


8 Troubleshooting Tips

This chapter provides tips for system administrators responsible for maintaining TGW.

Intended audience. The intended audience for this chapter is system administratorswho use MMS Application Administrator.


• Troubleshooting the MMSC

• Troubleshooting Apache

• Troubleshooting Oracle

8.1 Troubleshooting the MMSC

8.1.1 Message delivery failure

Review the following list to help ensure correct configuration of the Nokia Artuse™Multimedia Messaging Service Center (MMSC). Each item describes a possible reasonwhy message delivery can fail.

• For the originating application, you can set up one or more instances. Ensure that theURL for the Listen_To port field corresponds to the URL in the configuration

parameters.

• For the originating application, ensure that the MMS/sender and MMS URLscorrespond to the instances for the originating application in the MMSC.

• For the terminating application, ensure that the Server_ID and Server_Port_Number are pointing to the correct Apache server and port.

• Under System Configuration, ensure that the terminating application is set up withthe proper rule in the following file: xkr_mm_rules.cf.

• Ensure that the timestamp does not exceed the expiration time.

• Under System Configuration, ensure that the prefixes of the phone numbers arerepresentative of the prefixes in the following file: xkt_whitelist.cf

• Under Event Log, check if the status of events appears routine. (For example, reviewEA errors and validation errors.) Ensure that the status of messages also appearsroutine. (For example, waiting fetch.)

• To determine why messages are failing, look at logs from the MMSC by opening atelnet session to the log directory.

• Review the log for the external application (the terminating application).



88


8.1.2 Additional information

For more information about MMSC, refer to the following related documentation.

8.2 Troubleshooting Apache8.2.1 Incorrect spacing in the VirtualHost definition

The problem

Messages to the MMSC are rejected even though the MMSC is configured correctly.

The possible cause

Document Document # Description

Graphical User Interface

DN00148723 Provides descriptive information aboutnavigating the MMSC GUI and

background on basic tasks.

Message Handling DN00148708 Provides information about multimediamessage format, routing, and howmessages are handled in the MMSC.

Installing and Integrating MMSC

DN00148798 Provides instructions for installing andconfiguring the MMSC.

Operating MMSC DN00148786 Designed for users who need proceduresfor daily, weekly, monthly, and occasionaloperations.

Configuring MMSC DN00148774 Provides comprehensive instructions onconfiguring the MMSC with a focus oncustomizing the product.

External Application Developer’s Guide

DN00148759 Provides guidelines for developinginterfaces for external applications.

Technical Manual DN00148747 Provides:

• environment variables• processes

• configuration files

• database tables

Troubleshooting MMSCenter

DN0139402 Provides hints on how to handleunexpected situations regarding MMSC

Table 14 Additional documentation




DN0182152 89


Spacing in the definition of the VirtualHost in the httpd.conf file is incorrect. In theapache error logs /usr/local/apache/logs/error.log states that the messagecould not be delivered (typically with a 404 error code).

The solution

In the following example, the VirtualHost definition in the htpd.conf file has spacesmissing before the first forward slash, and after the * in the first part of the definition. Thisdefinition would cause messages to the MMSC to be rejected.

<VirtualHost <server_name>:<receive_port1> RewriteEngine on

RewriteRule/.*http://<server_name>:<listen_port>/

MmscServletApp/ReceiverOriginatedSyncServlet/ [P]

</VirtualHost>

The following example VirtualHost definition has the correct spacing:

<VirtualHost <server_name>:<receive_port1> RewriteEngine on

RewriteRule /.* http://<server_name>:<listen_port>/

MmscServletApp/ReceiverOriginatedSyncServlet/ [P]

</VirtualHost>

8.2.2 How to check the httpd.conf file

To check the httpd.conf file for spacing or other possible errors, do the following:

1. Stop the apache server using the following command:

/usr/local/apache/bin/./apachectl stop

2. View the httpd.conf file using the following command:

vi /usr/local/apache/bin/conf/httpd.conf

3. Refer to the TGW Commissioning guide to be sure you have the correct IP addressesand ports configured.

4. Run a syntax test using the following command:

/usr/local/apache/bin/./apachectl configtest

5. Check the apache logs using the following commands:

more /usr/local/apache/logs/ access_log

more /usr/local/apache/logs/ error_log

6. Start apache using the following command:

/usr/local/apache/bin/./apachectl start

7. Check to be sure that apache started using the following command:

http://IP_Address_of_Apache_Server

8. Check the apache logs again.






DN0182152 91


The following command backs up and exports the schema and data (including Sequences)owned by the application.

Note: Log in as Oracle.

EXP SYSTEM/< password > OWNER=AGW FILE="EXPAGW.dmp"

LOG="EXPLOGAGW.log" CONSISTENT=Y

If running remotely include the tnsname:

EXP SYSTEM/<password>@AGW.WORLD OWNER=AGW FILE="EXPAGW.dmp"

LOG="EXPLOGAGW.log" CONSISTENT=Y

The following text appears in the log:

Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production

With the Partitioning option

JServer Release 8.1.7.0.0 - Production

Export done in WE8ISO8859P1 character set and UTF8 NCHAR character set

server uses UTF8 character set (possible charset conversion)

About to export specified users ...

. exporting pre-schema procedural objects and actions

. exporting foreign function library names for user AGW

. exporting object type definitions for user AGW

About to export AGW's objects ...

. exporting database links

. exporting sequence numbers

. exporting cluster definitions

. about to export AGW's tables via Conventional Path ...

. . exporting table ACTION_TBL 0 rows exported

. . exporting table ADMINISTRATOR_TBL 3 rows exported

. . exporting table CACHE_LOOKUP_TBL 0 rows exported

. . exporting table CLASS_OF_SERVICE_PARAMETER_TBL 3 rows exported

. . exporting table CLASS_OF_SERVICE_TBL 1 rows exported

. . exporting table CONDITION_TBL 0 rows exported

. . exporting table CONFIG_PARAMETER_KEY_TBL 1502 rows exported

. . exporting table CONFIG_PARAMETER_VALUE_TBL 1695 rows exported

. . exporting table MESSAGE_IDENTITY_STORE_TBL 0 rows exported

. . exporting table PARAMETER_TBL 29 rows exported

. . exporting table RULE_TBL 0 rows exported

. . exporting table SUBSCRIBER_PARAMETER_TBL 38 rows exported

. . exporting table SUBSCRIBER_TBL 2 rows exported

. . exporting table TEMPORARY_ALBUM_POOL_TBL 0 rows exported

. . exporting table USER_TBL 5 rows exported

. exporting synonyms

. exporting views

. exporting stored procedures

. exporting operators

. exporting referential integrity constraints



92


. exporting triggers

. exporting indextypes

. exporting bitmap, functional and extensible indexes

. exporting posttables actions

. exporting snapshots

. exporting snapshot logs

. exporting job queues

. exporting refresh groups and children

. exporting dimensions

. exporting post-schema procedural objects and actions

. exporting statistics

Export terminated successfully without warnings



Backup overview

DN0182152 93


9 Backup overview

Developing a backup strategy is critical to protecting important data. The backup strategy

must include a method for backing up important data, as well as a mechanism to restoredata and critical systems in the event of system failure or user error. The backup strategyyou adopt will be based on a number of factors including how frequently data changes, thelevel of risk you decide to accept for lost data, and the hardware and software available forimplementing a backup strategy.

Note: There are numerous books regarding backups and strategies availableinvolving many different combinations of hardware and software. Theinformation provided in this section provides general information aboutdeveloping a backup strategy. You must develop a specific backup strategy

based on your particular needs.

The backup strategy you develop will involve two general groups of data:

• User data - The first group addresses user data, which typically changes frequently.Your strategy for backing up user data will depend upon how often user data changes.

• System files - The second group comprises system files necessary for the system to boot and run. You use the system backups to restore the machine to its original state asquickly as possible in the event of a major system failure.

The following sections describe general information, examples, and suggestions aboutdeveloping a backup strategy for user data and system files.

9.1 System Configuration BackupsBecause the system can be customized for each environment, it is important to make

periodic system backups to provide quick recovery with minimum operator intervention,in the event of system failure. These backups also provide a quick method forimplementing new machines.

Using backup software such as Legato Networker, create a schedule for performing backups of the root disk. The following file systems should be included in the backup:

• / (root)

• /usr

• /opt• /var

For faster recoveries, you should consider backing up the root disks of the server toidentical SCSI drives. Your backup schedule could include a nightly backup to this drive.In the event of a fatal root disk crash on one of the main servers, the machine could be

booted from the external SCSI disk drive while incurring as little as 20 minutes of downtime.



94


Note: There are commercial packages that mirror disks, but none of these have been tested with AGW. Ask your Sun support representative about Sun'sdisk suite to mirror the root disk partitions if you are interested in a truemirror option.

9.1.1 User Data Backups

User data typically changes frequently, and needs to be backed up more regularly thansystem files. At a minimum you should backup user data on a daily basis. The backupsinvolve three areas:

• User files within the Oracle database

• Files that are in the UNIX file system space

• Files containing subscriber messages within Critical Path

To perform the backups, you should purchase a commercially available software product.Your user data backup strategy should provide a schedule for both full and incremental

backups of user data, for UNIX, Oracle, and system configuration files. These files are inthe following locations:

• The Oracle directories /u01, /u02, /u03, /u04

• Criticalpath /cp/mbx (data resides on the NetApps server or second Sun Box)

Note: You must make sure your backup software can back up over NFS or anotherremote protocol.

• Any other file systems the systems administrator has configured for user use (forexample /export/home typically contains the user 's home directories and thereforeneeds to be backed up.

9.1.2 Backup Schedules

It is important in any backup strategy to have a combination of archive tapes, as well asrotating sets of tapes that are recycled over some period of time. For example, the backupstrategy you implement might include the following schedule:

• Eight sets of tapes rotated (overwritten) bi-monthly, with one full backup tape permonth preserved for offsite archive

• Full backups performed every Friday at 2:11am• Incremental backups performed every night, except Friday, at 2:11am

• Archives (fulls) performed as systems change / tapes stored locally

9.1.3 Uninterruptible power supplies (UPS)

To prevent losing systems and data in the event of power interruptions, you should includeUninterruptible Power Supplies (UPS). UPS provides backup power for a certain amount



Backup overview

DN0182152 95


of time. The amount of time backup power is available depends on the unit's size. Thelonger the battery life is, the higher the cost of the unit.



96




DN0182152 97


Appendix A: Acronyms and terminology

The following table describes acronyms and other terminology related to TGW.

Acronym/Term Definition

Administrator Administrators use MMS ApplicationAdministrator to administer the server thatis hosting multimedia messages.

Administration tasks include managingTGW subscribers, managing Class ofService plans, configuring the system,changing administrator or supervisor

passwords, and viewing your system log.

CDR

(Call Detail Record)

CDRs are records that contain billing

information per transaction, for use by anoutside billing package. CDRs contain all billing information needed for a billingsystem to provide an invoice for asubscriber.

The billing component for TGWcommunicates billing information in a CallDetail Record. The two methods fortransmitting this charging information areas follows:

• Transmitting charging information tothe MMSC - generating CDRs for

multimedia messages received from theMMSC

• Generating CDRs directly - generatingCDRs, regardless of the source ordestination of messages

Table 15 Appendix A: Acronyms and Terminology



98


COS(Class of Service)

A Class of Service (COS) is a group offeatures that may be configured for a group

of wireless phone users.

Values that define a TGW subscriber’sClass of Service include maximum NAsize, maximum PA size, NA storage time,PA storage time, and enabling/disablingself-provisioning (which includeschanging e-mail address, password, andaddress.)

An active Class of Service plan is one thatyour TGW subscribers are using.

An inactive Class of Service plan is one thatyou have deactivated. Though the inactiveCOS plan still exists in the database, youcannot assign additional TGW subscribersto that plan. Existing subscribers, however,who are members of an inactive COS,retain membership in that COS plan.

Legacy phone owner A subscriber whose mobile phone has SMS but does not have multimedia capabilities.

MMT owner A subscriber whose mobile terminal has

multimedia capabilities.

MSISDN(Mobile SubscriberISDN Number)

The mobile telephone number used by asubscriber in a GSM/DCS network.

NA(New Album)

This is the subscriber’s album where newlyarrived multimedia messages are stored.

Non TGW subscriber A phone owner not subscribing to TGWservices.

PA(Personal Album)

This is the TGW subscriber’s main albumwhere multimedia messages are stored.


Table 15 Appendix A: Acronyms and Terminology (Continued)



DN0182152 99


SMSC(Short Message Service

Center)

The Short Message Service is a storeand forward service, in other words,short messages are not sent directlyfrom sender to recipient, but always viaan SMS Center instead.

Each mobile telephone network thatsupports SMS has one or moremessaging centers to handle andmanage the short messages.

SNMP

(Simple NetworkManagementProtocol)

SNMP is a communication protocolthat manages TCP/IP networks,including individual network devices.

One feature of SNMP is an alarmmechanism by which devices can notifyadministrators of a problem (assumingthat the device is configured to SNMP.)

Subscriber Anyone who subscribes to mobile phoneservice.

Supervisor Supervisors have access to the Subscribersscreen of MMS Application Administratorfor the purpose of managing TGW

subscribers.

Tasks that supervisors can complete are asfollows: searching for TGW subscribers,assigning Class of Service plans, adding,editing, and activating/deactivating TGWsubscribers.

TGW subscriber Mobile phone owner who subscribes toTGW and has a Personal Album (PA).

An active TGW subscriber is currentlyusing the TGW service.

An inactive TGW subscriber is currentlynot using the TGW service, but thesubscriber information still exists in thedatabase. An inactive TGW subscriber can

be reactivated at any time.


Table 15 Appendix A: Acronyms and Terminology (Continued)



100




DN0182152 101


Appendix B: Product descriptions for EGW and VGW

In addition to TGW, the Application Gateways product line at Nokia offers NokiaMultimedia E-mail Gateway (EGW) and Nokia Multimedia Voice Gateway (VGW). If

you are interested in learning more about these related products, see the following productdescriptions or e-mail the Applications Gateways product line at

[email protected]

Nokia Multimedia E-mail Gateway (EGW)

Nokia Multimedia E-mail Gateway (EGW) fulfills Nokia's promise to offerGPRS/GSM operators value-added services for multimedia messaging.

By converting message formats, EGW allows multimedia terminals (MMTs) tosend messages to the Internet and receive messages sent from the internet.

The joining of the mobile and internet messaging worlds is enhanced by EGW's

ability to convert e-mail message attachments to fit the capabilities of MMTs.EGW also provides a rules engine that gives operators and phone owners the

power to control the number and type of messages that are sent to the MMT.

Taken together, EGW's features make multimedia messaging exciting forconsumers and profitable for operators.

Nokia Multimedia Voice Gateway (VGW)

Nokia Multimedia Voice Gateway (VGW) is another part of the broader Nokia effort tooffer GPRS/GSM operators value-added services for multimedia messaging.

VGW combines the ease of use of a voice interface with the instant message deliverycapabilities of Short Message Service (SMS). VGW receives unanswered calls intended

for Multimedia Terminals (MMTs), plays a personal greeting, takes a message, andforwards the message to the MMSC. The message is then forwarded from the MMSC tothe subscriber’s MMT, where the subscriber can listen to the message at theirconvenience.



102






104


City Enter the

subscriber’s city.

Salem

State/Province Enter thesubscriber’s state or

province.

NH

Postal code Enter thesubscriber’s postalcode.

03890

Country Enter thesubscriber’s country.

US

E-mail address Enter the

subscriber’s e-mailaddress.

[email protected]

MSISDN* Enter the MobileSubscriber ISDN

Number ininternationalformat.

+17815260823

Device e-mail* Enter the multimediaterminal’s e-mailaddress.

[email protected]

SMSC MSISDN* Enter the MobileSubscriber ISDN

Number of theSMSC, ininternational format,to which thesubscriber isassigned.

+16173882608

Field (* indicatesrequired field)

Description Example

Table 16 Field descriptions for the Create Subscriber screen (Continued)



DN0182152 105


Descriptions of COS features listed on the Create Subscriber: Step 1 of 1 screen

The following table provides descriptions of the COS features listed on the CreateSubscriber: Step 1 of 1 screen.

Class of Service* From the drop-down

list, select the Classof Service plan toassign to thissubscriber.

MMS ApplicationAdministrator listsTGW COS features

based on the COSyou select. COSfeatures are asfollows: Description,Max NA Size, MaxPA Size, NA storeTime, PA store time,Self-provisioning.

You are responsible for defining your own

Class of Service plans.

TGW COS Feature Description Example

Description Lists the COS assigned to thatsubscriber.

Use defaults.

Max NA size Lists the maximum size for thesubscriber’s New Album.

TheNew Album is the subscriber’salbum where newly arrivedmultimedia messages are stored.

4MB

Max PA size Lists the maximum size for thesubscriber’s Personal Album.

The Personal Album is the TGWsubscriber’s main album wheremultimedia messages are stored.

2MB

NA store time Lists how long the message will bestored in the New Album (NA).

10 days

Table 17 Descriptions of COS features listed on the Create Subscriber screen

Field (* indicatesrequired field)

Description Example

Table 16 Field descriptions for the Create Subscriber screen (Continued)



106


PA store time Lists how long the message will bestored in the Personal Album (PA).

100 days

Self provisioning Shows if the subscriber has theability to change e-mail address,

password, and address.

EnabledDisabled

TGW COS Feature Description Example

Table 17 Descriptions of COS features listed on the Create Subscriber screen



DN0182152 107


Appendix D: Description of available TGW events

The following table provides a list of all available TGW event numbers, the correspondingevent names, and a short description of the event.

Eventnumber

Event name Description

10000 STORE_MM_REQUEST Request the MultimediaManager request types: Storemultimedia message request.

10001 STORE_MM_REPLY Reply to the store multimediamessage request

10002 DELETE_MM_REQUEST Request to delete multimediamessage from the personal

album.

10003 DELETE_MM_REPLY Reply to the delete multimediamessage request

10004 BROWSE_MM_REQUEST Request to browse personalalbum.

10005 BROWSE_MM_REPLY Reply to browse personal albumaction.

10006 FORWARD_MM_REQUEST Request to forward multimediamessage.

10007 FORWARD_MM_REPLY Reply to forward multimediamessage.

10008 SEND_MM_REQUEST Request to send the multimediamessage.

10009 SEND_MM_REPLY Reply to send multimediamessage.

10010 RETRIEVE_MM_REQUEST Request to retrieve themultimedia message.

10011 RETRIEVE_MM_REPLY Reply to retrieve multimediamessage.

10012 STORE_MM_REQUEST_PAB Request to store multimediamessage in a personal album.

10013 STORE_MM_REQUEST_NAB Request to store multimediamessage in a new album.

10014 STORE_MM_REQUEST_TAB Request to store multimediamessage in a Temp folder

Table 18 Description of available TGW events



108


10015 FORWARD_MM_REQUEST_FROM_WEBWAP_

TO_MMSC

Request to forward multimedia

message from (Web/WAP) toMMSC

10016 FORWARD_MM_REQUEST_FROM_WEBWAP_ TO_EMAIL

Request to forward multimediamessage from (Web/WAP) to e-mail address.

10017 RETRIEVE_MM_REQUEST_FROM_WAP_TO_MMS

Request to retrieve themultimedia message from WAPto MMSC

10018 RETRIEVE_MM_REQUEST_FROM_WAP_TO_EMAIL

Request to retrieve themultimedia message from WAP

to a composed e-mail address.10019 SEND_MM_REQUEST_FROM_WEB_TO_MMSC Send a composed multimedia

message request from Web toMMSC.

10020 SEND_MM_REQUEST_FROM_WEB_TO_EMAIL Request to send a composedmultimedia message from Webto e-mail address.

10200 SEND_EMAIL_REQUEST Request to send e-mail messagerequest.

10201 SEND_EMAIL_REPLY Send a Reply to an email

message.

10202 SMTP_SERVER_DOWN SMTP Server down

10203 SMTP_SERVER_UP SMTP server started

10300 TRAP_REQUEST Request to the trap manager

10400 BILLING_REQUEST Request to the billing manager.

10401 BILLING_REPLY Reply to billing request.

10402 BILLING_LOGGER_LISTENER_CREATE_FAILED_CRITICAL

Critical error; unable to createthe billing/logger listener.

10403 BILLING_MANAGER_CREATE_FAILED_CRITICAL

Critical error; unable to create billing manager.

10404 BILLING_MD_BEAN_CREATE_FAILED_CRITICAL

Critical error; unable to create a billing java bean.

10405 BILLING_XML_PROCESSOR_BEAN_CREATE_ FAILED_CRITICAL

Critical error; unable to processan XML billing java bean.

Eventnumber





DN0182152 109


10500 LOG_REQUEST Request to the log.

10501 LOG_REPLY Reply to a log request.

10502 LOG_DEBUG Set logging to debug levels.

10503 LOG_WARNING Set logging to warning level.

10504 LOG_TRACE Log tracing information.

10505 LOG_EXCEPTION The log threw an exception.

10506 LOG_MAJOR Log a major problem.

10507 LOGGER_INIT_COMPLETE Logger Init complete event

10508 LOGGER_SHUTDOWN Logger Shutdown

10509 LOG_INFO Log Info

10600 PERF_DATA Performance Manager:Performance data

10700 Login The MMSC Interface: MMSCTerminating Async Receiver-Originated App.

10701 Forward Msg MMSC Message Received byServlet.

10702 Retrieve Msg MMSC Message Received byTGW application.

10703 Compose Msg MMSC Message Queued byinterface application.

10704 Change Email MMSC Message Received byinterface application.

10705 View Folder MMSC Message Rejected byServlet.

10706 View Menu MMSC Message Rejected byTGW application.

10707 Delete Msg MMSC Message Rejected byinterface application.

10708 Move Msg MMSC Message successfully processed by Servlet.

10709 Rename Msg MMSC Message successfully processed by TGW application.

Eventnumber





110


10710 Send Msg MMSC Terminating Async

Receiver-Originated App Reply.

10711 View Msg

10712 Change Password MMSC Message ReplyReceived by TGW application.

10713 TMAR_REPLY_QUEUED_TGW MMSC message reply queued by TGW application.

10714 TMAR_REPLY_RECEIVED_INTERFACE MMSC Message ReplyReceived by interfaceapplication.

10716 TMAR_REPLY_REJECTED_TGW MMSC message reply rejected by TGW application.

10717 TMAR_REPLY_REJECTED_INTERFACE MMSC Message Reply Rejected by interface application.

10719 TMAR_REPLY_PROCESSED_INTERFACE MMSC Message Replysuccessfully processed byinterface application.

10720 TERMINATING_MM_SYNC_RECEIVER MMSC Terminating SyncReceiver-Originated App.

10721 TMSR_MESSAGE_RECEIVED_SERVLET MMSC message received by

servlet.

10722 TMSR_MESSAGE_RECEIVED_TGW MMSC message received byTGW application.

10723 TMSR_MESSAGE_QUEUED_INTERFACE MMSC Message Queued byinterface application.

10724 TMSR_MESSAGE_RECEIVED_INTERFACE MMSC Message Received byinterface application.

10725 TMSR_MESSAGE_REJECTED_SERVLET MMSC message rejected byServlet.

10726 TMSR_MESSAGE_REJECTED_TGW MMSC message rejected byTGW application.

10727 TMSR_MESSAGE_REJECTED_INTERFACE MMSC Message Rejected byinterface application.

10728 TMSR_MESSAGE_PROCESSED_SERVLET MMSC message successfully processed by servlet.

Eventnumber





DN0182152 111


10729 TMSR_MESSAGE_PROCESSED_TGW MMSC message successfully

processed by TGW application.

10730 TERMINATING_MM_ASYNC_SENDER MMSC Terminating AsyncSender-Originated App.

10740 TERMINATING_MM_ASYNC_SENDER_REPLY MMSC Terminating AsyncSender-Originated App Reply.

10750 TERMINATING_MM_SYNC_SENDER MMSC Terminating SyncSender-Originated App.

10760 TERMINATING_MM_ASYNC_DELIVERY_FAILURE

MMSC Terminating AsyncDelivery Failure-OriginatedApp.

10761 TMAD_MESSAGE_RECEIVED_SERVLET MMSC message received byservlet.

10762 TMAD_MESSAGE_RECEIVED_TGW MMSC message received byTGW application.

10763 TMAD_MESSAGE_QUEUED_INTERFACE MMSC Message Queued byinterface application.

10764 TMAD_MESSAGE_RECEIVED_INTERFACE MMSC Message Received byinterface application.

10765 TMAD_MESSAGE_REJECTED_SERVLET MMSC message rejected by

servlet.

10766 TMAD_MESSAGE_REJECTED_TGW MMSC message rejected byTGW application.

10767 TMAD_MESSAGE_REJECTED_INTERFACE MMSC message rejected byinterface application.

10768 TMAD_MESSAGE_PROCESSED_SERVLET MMSC message successfully processed by Servlet.

10769 TMAD_MESSAGE_PROCESSED_TGW MMSC Message successfully processed by TGW application.

10770 TERMINATING_MM_ASYNC_DELIVERY_FAILURE_REPLY

MMSC Terminating AsyncDelivery Failure-OriginatedApp Reply.

10772 TMAD_REPLY_RECEIVED_TGW MMSC Message ReplyReceived by TGW application.

10773 TMAD_REPLY_QUEUED_TGW MMSC message reply Queued by TGW application.

Eventnumber





112


10774 TMAD_REPLY_RECEIVED_INTERFACE MMSC message reply received

by interface application.

10776 TMAD_REPLY_REJECTED_TGW MMSC message reply Rejected by TGW application.

10777 TMAD_REPLY_REJECTED_INTERFACE MMSC Message Reply rejected by interface application.

10779 TMAD_REPLY_PROCESSED_INTERFACE MMSC Message Replysuccessfully processed byinterface application.

10780 TERMINATING_MM_SYNC_DELIVERY_FAILURE

MMSC Terminating SyncDelivery Failure-OriginatedApp.

10781 TMSD_MESSAGE_RECEIVED_SERVLET MMSC message received byservlet.

10782 TMSD_MESSAGE_RECEIVED_TGW MMSC Message received byTGW application.

10783 TMSD_MESSAGE_QUEUED_INTERFACE MMSC message queued byinterface application.

10784 TMSD_MESSAGE_RECEIVED_INTERFACE MMSC Message Received byinterface application.

10785 TMSD_MESSAGE_REJECTED_SERVLET MMSC message rejected byservlet.

10786 TMSD_MESSAGE_REJECTED_TGW MMSC message rejected byTGW application.

10787 TMSD_MESSAGE_REJECTED_INTERFACE MMSC Message Rejected byinterface application.

10788 TMSD_MESSAGE_PROCESSED_SERVLET MMSC message successfully processed by servlet.

10789 TMSD_MESSAGE_PROCESSED_TGW MMSC message successfully

processed by TGW application.10790 ORIGINATING_MM MMSC Originating App.

10791 O_MESSAGE_RECEIVED_TGW MMSC message received byTGW application.

10792 O_MESSAGE_QUEUED_TGW MMSC message queued byTGW application.

Eventnumber





DN0182152 113


10793 O_MESSAGE_RECEIVED_INTERFACE MMSC Message Received by

interface application.

10794 O_MESSAGE_REJECTED_TGW MMSC message rejected byTGW application.

10795 O_MESSAGE_REJECTED_INTERFACE MMSC Message Rejected byinterface application.

10796 O_MESSAGE_PROCESSED_INTERFACE MMSC Message successfully processed by interfaceapplication.

10797 O_ASYNC_REPLY_PROCESSED_INTERFACE MMSC Async Replysuccessfully processed byinterface application.

10799 MMSC_UNKNOWN Unknown MMSC-related App.

10801 SMS_SUBSYSTEM_INIT Initialization of SMS complete

10802 SMS_SUBSYSTEM_SHUTDOWN SMS system down.

10803 SEND_SMS Send SMS Message

10804 SMS_SEND_SUCCESS Successful SMS Sent.

10805 SMS_SEND_FAIL Failed SMS Send.

11700 TERMINATING_MESSAGE_RECEIVED_SERVLET MMSC terminating messagereceived by Servlet.

11701 MMSC_LICENSING_DELIVERY_FAILURES License check failed.

11702 MMSC_LICENSING_MESSAGE_STORES MMSC Licensing Manager -Message Stores.

11703 MMSC_LICENSING_OUTGOING_MESSAGES MMSC Licensing Manager -Outgoing Messages.

11704 MMSC_LICENSING_TOTAL_MESSAGES MMSC Licensing Manager -Total Messages.

11705 MMSC_LICENSING_DELIVERY_FAILURES_EXCEEDED Message delivery failed becauselicense exceeded.

11706 MMSC_LICENSING_MESSAGE_STORES_EXCEEDED

No more messages can be storedwith the license.

11707 MMSC_LICENSING_OUTGOING_MESSAGES_EXCEEDED

No more outgoing messages can be sent; license exceeded.

Eventnumber





114


11708 MMSC_LICENSING_TOTAL_MESSAGES_EXCE

EDED

MMSC Licensing Manager -

Total Messages.

11728 TMSR_MESSAGE_FILTERED_SERVLET MMSC Message successfullyfiltered by TMSR Servlet.

11729 TMSD_MESSAGE_FILTERED_SERVLET MMSC Message successfullyfiltered by TMSD Servlet.

11780 TMSD_SERVLET_INIT_FAILED_CRITICAL MMSC TMSD Servletinitialization failed.

11781 TMAD_SERVLET_INIT_FAILED_CRITICAL MMSC TMAD Servletinitialization failed.

11782 MMSC_RECEIVER_CREATE_FAILED_CRITICAL

MMSC Receiver initializationfailed.

11783 MMSC_SENDER_CREATE_FAILED_CRITICAL MMSC Sender initializationfailed.

11784 MMSC_CONNECTION_FAILED_CRITICAL MMSC Connectioninitialization failed.

11785 TMSR_SERVLET_INIT_FAILED_CRITICAL MMSC TMSR Servletinitialization failed.

11786 TMAR_SERVLET_INIT_FAILED_CRITICAL MMSC TMAR Servletinitialization failed.

11787 MMSC_CONFIG_CHANGE_EVENT Configuration change made.

11788 MMSC_RECEIVER_EVENT Generic operation type forMMSC Receiver events.

11789 MMSC_SENDER_EVENT Generic operation type forMMSC Sender events.

12000 ATTRIBUTE_CHANGE Attribute value change event

12001 ENTRY_CREATION New Entry created

12002 INVALID_AVC Invalid Attribute value change

12003 ENTRY_DELETION Entry deleted

12004 STATE_CHANGE State change of a subsystem

12005 INIT_COMPLETE Initialisation complete of thesubsystem

12006 SHUTDOWN_COMPLETE Shutdown of the subsystem done

Eventnumber





DN0182152 115


13001 Successful message store to personal album This event is generated after the

message is successfully stored inthe PA.

13002 Successful message store to new album This event is generated after themessage is successfully stored inthe NA.

13003 Successful store of temporary message This event is generated after themessage is successfully stored inthe temporary album.

13004 Failed message store to personal album This event is generated after themessage is unsuccessfully stored

in the PA.13005 Failed message store to new album This event is generated after the

message is unsuccessfully storedin the NA.

13006 Failed store of temporary message This event is generated after themessage is unsuccessfully storedin the temporary folder album.

13011 Successful user mailbox creation This event is generated when theuser albums are successfully

provisioned

13012 Failed to create user mailbox This event is generated when theuser albums failed to be

provisioned.

13013 Successful user mailbox removal This event is generated when auser album is successfullyremoved.

13014 Failed to remove user mailbox This event is generated when auser albums failed to be removed

14001 WEB_SUBSCRIBER_LOGIN This event is generated after thesubscriber has been successfully

validated from the Web.14002 WEB_SUBCSRIBER_LOGOUT This event is generated after the

subscriber on the Web has beensuccessfully logged out.

14003 WEB_SUBCSRIBER_VIEW_MSG This event is generated when theWeb subscriber wants to retrievea message from the PA or NA.

Eventnumber





116


14004 WEB_SUBSCRIBER_MOVE_MSG The Message Store generates

this event after the message has been successfully moved fromthe NA to the PA on the Web.

14005 WEB_SUBSCRIBER_RENAME_MSG The Message Store generatesthis event after the message has

been successfully renamed onthe Web.

14006 WEB_SUBSCRIBER_FOWARD_MSG The MMSC Sender generatesthis event after the message has

been successfully sent to theMMSC. The SMTP component

generates this event after themessage has been successfullysent to the SMTP server.

14007 WEB_SUBSCRIBER_COMPOSE_MSG The MMSC Sender generatesthis event after the message has

been successfully sent to theMMSC on the Web.

14008 WEB_SUBSCRIBER_DELETE_PA_MSG The Message Store generatesthis event after a message issuccessfully deleted from the PAon the Web.

14009 WEB_SUBSCRIBER_DELETE_NA_MSG The Message Store generatesthis event after a message issuccessfully deleted from the

NA on the Web.

14010 WEB_VIEW_TMP_MSG The UI Servlet generates thisevent after a message issuccessfully returned to the non-subscriber on the Web.

14011 WEB_BROWSE_PA_MSG The UI Servlet generates thisevent after a user browses their

PA via the Web interface14012 WEB_BROWSE_NA_MSG The UI Servlet generates this

event after a user browses their NA via the Web interface

Eventnumber





DN0182152 117


14101 WAP_SUBSCRIBER_LOGIN This event is generated after the

subscriber has been successfullyvalidated from the WAPinterface.

14102 WAP_SUBSCRIBER_LOGOUT This event is generated after thesubscriber has been successfullylogged out.

14103 WAP_SUBSCRIBER_VIEW_MSG This event is generated when theuser retrieves a message via theWap menu.

14104 WAP_SUBSCRIBER_MOVE_MSG The Message Store generates

this event after the message has been successfully moved fromthe NA to the PA via WAP.

14105 WAP_SUBSCRIBER_RENAME_MSG The Message Store generatesthis event after the message has

been successfully renamed viathe WAP.

14106 WAP_SUBSCRIBER_FORWARD_MSG The MMSC Sender generatesthis event after the message has

been successfully sent to theMMSC from the WAP. The

SMTP component generates thisevent after the message has beensuccessfully sent to the SMTPserver via WAP.

14107 WAP_SUBSCRIBER_DELETE_PA_MSG The Message Store generatesthis event after a message issuccessfully deleted from the PAvia WAP.

14108 WAP_SUBSCRIBER_DELETE_NA_MSG The Message Store generatesthis event after a message issuccessfully deleted from the

NA via WAP.14109 WAP_BROWSE_PA_MSG This event is generated after a

user browses their PA via theWAP interface

14110 WAP_BROWSE_NA_MSG The Wap Servlet generates thisevent after a user browses their

NA via the WAP interface

Eventnumber





118


15001 LIC_EXCEED_SUB_COUNT This event is generated by the

Message Store when an attemptis made to create a subscriberafter the license has been usedup.

15002 LIC_EXCEED_EAIF_TPS This event is generated when thenumber of transactions persecond has exceeded the licensethreshold.

15003 LIC_CURRENT_EAIF_TPS This event is generated eachtime the MMSC logstransactions per second over the

limit.

15101 SUBSCRIBER_CREATED This event is generated after asubscriber has been successfullycreated .

15102 SUBSCRIBER_UPDATED This event is generated after thesubscriber has been successfullymodified.

15103 SUBSCRIBER_DEACTIVATED This event is generated after thesubscriber has been successfullydeactivated.

15104 SUBSCRIBER_ACTIVATED This event is generated after thesubscriber has been successfullyactivated.

Eventnumber





DN0182152 119


Appendix E: Configuration Parameters

The following tables list configuration parameters and properties displayed in the MMSApplication Administrator Configuration screen.

Table 19 lists configuration parameters and properties that are set during installation.These properties should not be changed in day to day operations.

Table 20 lists configuration properties that should never be changed. Changing these properties can result in system failure.

Parameter Property

msis.MailStoreProvisioner.CP IMSdAdminPort: CP IMSd management port number

msis.MailStoreProvisioner.CP IMSdAdminPassword: CP IMSd managemement port write access

passwordmsis.MailStoreProvisioner.CP Domain:

Critical Path users domain

msis.MailStoreProvisioner.CP SMTPdAdminPort:

CP SMTPd management port number

msis.MailStoreProvisioner.CP SMTPdAdminPassword: CP SMTPd managemement port writeaccess password

msis.MailStore COSCheckInterval:

Number of seconds between fetches ofsubscriber class of service parameters

values

msis.MailStore Host:

IMAP server host name

msis.MailStore SuperUserPassword: IMAP privileged user password

msis.MailStore SuperUser: IMAP4 privileged user logon name

msis.MailStore PingTTL: Seconds between connection sanity checks

msis.MailStore IMAPPort:

Port on which the IMAP server listens

sms DeliveryRetryCount: The number of times an SMS delivery will

be attempted before being consideredundeliverable

Table 19 Properties set during installation



120


sms MessageQRead:

The max. number of SMS messages that

will be processed when the timer kicks in

snmp portNum: Specifies the port on the managementstation which listens for traps

snmp serverName: Specifies the address or hostname of themanagement station

tgw.smtp portNum: Specifies the SMTP port number on theMail Server

tgw.smtp password:

Used for authentication on ESMTP servers

tgw.smtp username: Used for authentication on ESMTP servers

tgw.smtp serverName: Specifies either the address or hostname ofthe SMTP server

multimediamanager.reflect.async.SMS.CTOR_NAME.CTOR_ARG

CTOR_ARG0:Address for the NACS Server for outbound SMS insync mode

ui basemsgretrievalURL:

base url

ui usertempdir: temp directory for unwrapping messages

mmsc.sender maximumMessageContentLength:Maximum message content length foroutgoing messages (in bytes)

mmsc.sender asyncTerminatingMmscUrls:

Comma-separated list of MMSC URLs touse for Async Terminating Messages

mmsc.sender mmscUrls: Comma-separated list of MMSC URLs touse for outgoing messages

mmsc.sender asyncDeliveryFailureMmscUrls: Comma-separated list of MMSC URLs touse for Async Delivery Failures

Parameter Property

Table 19 Properties set during installation



DN0182152 121


Parameter Property

msisdebugMode: Turns the message storecomponent activity tracing on or off

msis tracingLevel: Defines the message storedegree of tracing detail

msis.TempStore Size: Defines the per folder size high watermark for temporary message folders

msis.MailStore COSCheckInterval: Defines the number ofseconds between fetches of subscriber class

of service parameters values

msis.MailStore PingTTL: Defines the number of seconds between connection sanity checks

snmp debugLevel: Specifies the current debug levelof the TrapManager component

snmp trapClearInterval:Specifies the time interval(in milliseconds) that should elapse beforestopping the monitoring of a specific trap

snmp monInterval: Specifies the time interval (inmilliseconds) which monitors iftrapClearInterval has passed.

snmp i18Nflag:Specifies whether tointernationalize the message sent to themanagement station

tgw.smtp debugLevel: Specifies the currentdebugLevel of the EmailClient component

tgw.smtp serverName: Specifies either the address orhostname of the SMTP server

licenseManager perfDataMode: A boolean value used toindicate performance data collection (notsupported R1)

Table 20 Properties that should not be changed



122


licenseManager messageDeliveryFailureThreshold: A licensingthreshold for message delivery failures

(specified in messages / second)

licenseManager messageStoreRequests: Updated actual rate formessage store requests (specified inmessages / second)

licenseManager calculationInterval:The calculation interval (inseconds) for license checking

licenseManager totalMessagesThreshold: The licensingthreshold for total messages sent and

received (in messages / second)

licenseManager outgoingMessages: The actual rate foroutgoing messages (specified in messages /second)

licenseManager messageStoreRequestsThreshold: Licensingthreshold for message store requests (inmessages / second)

licenseManager rejectRequestIfExceeded: Boolean value toindicate that that requests should berejected if any of the licensing thresholdsare exceeded

licenseManager outgoingMessagesThreshold: Licensingthreshold for outgoing messages (specifiedin messages / second)

licenseManager tracingLevel: Tracing level for all LicenseManager events (0-OFF, 3-ALL)

licenseManager totalMessages:Updated actual rate ofincoming and outgoing messages (inmessages / second)

Parameter Property




DN0182152 123


licenseManager messageDeliveryFailures: Updated actual ratefor message delivery failures (specified in

messages / second)

licenseManager debugMode: The debugmode for the LicenseManager

multimediamanager.reflect.async.SMS EJB_NAME: JNDI Name

multimediamanager.reflect.async.SMS PACKAGE_NAME: Package Name

multimediamanager.reflect.async.SMS.REQUEST_TYPES.0

METHOD_N_ARGS: Nb of Method Arg


REQUEST_TYPE:Request Type


METHOD_NAME: Method Name to Call

multimediamanager.reflect.async.SMS.REQUEST_TYPES.0.METHOD_TYPE

METHOD_TYPE3: Arg Type 3







multimediamanager.reflect.async.SMS.CTOR_NAME

CTOR_NAME: Name Of Constructor

multimediamanager.reflect.async.SMS.CTOR_NAME

CTOR_N_ARGS: Nb Of Constructor Arg

multimediamanager.reflect.async.SMS.CTOR_NAME.CTOR_TYPE

CTOR_TYPE1: Arg Type 1

multimediamanager.reflect.async.SMS.CTOR_NAME.CTOR_TYPE


multimediamanager.reflect.async.SMS.CTOR_NAME.CTOR_ARG

CTOR_ARG1: Arg Value 1

multimediamanager.reflect.async.MESSAGE_STORE

EJB_NAME: JNDI Name

multimediamanager.reflect.async.MESSAGE_STORE

PACKAGE_NAME: Package Name

Parameter Property




124


multimediamanager.reflect.async.MESSAGE_STORE.REQUEST_TYPES.2

METHOD_N_ARGS: Nb Of Method Arg





multimediamanager.reflect.async.MESSAGE_STORE.CTOR_NAME


multimediamanager.reflect.async.MESSAGE_STORE.CTOR_NAME


multimediamanager.reflect.async.EMAIL_ CLIENT

EJB_NAME: JNDI Name

multimediamanager.reflect.async.EMAIL_ CLIENT


multimediamanager.reflect.async.DATABASE

EJB_NAME: JNDI Name

multimediamanager.reflect.async.DATABASE


multimediamanager.reflect.async.MMSC EJB_NAME: JNDI Name

multimediamanager.reflect.async.MMSC PACKAGE_NAME: Package Name

multimediamanager.reflect.sync.SMS EJB_NAME: JNDI Name

multimediamanager.reflect.sync.SMS PACKAGE_NAME: Package Name

multimediamanager.reflect.sync.SMS.REQUEST_TYPES.0

METHOD_N_ARGS: Nb of Method Arg


REQUEST_TYPE: Request Type



multimediamanager.reflect.sync.SMS.REQUEST_TYPES.0.METHOD_TYPE






Parameter Property




DN0182152 125




multimediamanager.reflect.sync.SMS.CTOR_NAME


multimediamanager.reflect.sync.SMS.CTOR_NAME


multimediamanager.reflect.sync.SMS.CTOR_NAME.CTOR_TYPE


multimediamanager.reflect.sync.SMS.CTOR_NAME.CTOR_TYPE


multimediamanager.reflect.sync.SMS.CTOR_NAME.CTOR_ARG

CTOR_ARG1: Arg Value 1

multimediamanager.reflect.sync.MESSAGE _STORE

EJB_NAME: JNDI Name

multimediamanager.reflect.sync.MESSAGE _STORE


multimediamanager.reflect.sync.MESSAGE _STORE.REQUEST_TYPES.2

METHOD_N_ARGS: Nb Of Method Arg





multimediamanager.reflect.sync.MESSAGE _STORE.CTOR_NAME


multimediamanager.reflect.sync.MESSAGE _STORE.CTOR_NAME


multimediamanager.reflect.sync.EMAIL_CLIENT

EJB_NAME: JNDI Name

multimediamanager.reflect.sync.EMAIL_CLIENT


multimediamanager.reflect.sync.DATABASE

EJB_NAME: JNDI Name

multimediamanager.reflect.sync.DATABASE


multimediamanager.reflect.sync.MMSC EJB_NAME: JNDI Name

multimediamanager.reflect.sync.MMSC PACKAGE_NAME: Package Name

Parameter Property




126


multimediamanager.elements traceLevel: Trace Level

multimediamanager.elements loggerName: Logger Name

multimediamanager.elements topicName: Topic Name

multimediamanager.elements state: State of component

multimediamanager.elements smsName: SMS Name

multimediamanager.elements snmpName: SNMP Name

multimediamanager.elements connectionFactory: Connection Factory Name

common RetryTopic: The JNDI name of the SMS retrytopic

common RetryInterval: The interval at which the SMSdelivery retry timer will kick in

common TGWConnFactory: Common JMS connectionfactory for TGW components.

common configTopic: The JNDI name of the ConfigManager topic

common RetryQueue: The JNDI name of the SMSretry queue

perf perfInterval:

logger debugLevel: Debug Level

logger.tool BillingListenerDN: Dname of the BillingListener Application

logger.tool LogListenerDN: Dname of the Log(File)Listener Application

Parameter Property




DN0182152 127


logger.tool TrapListenerDN: Dname of the Trap ListenerApplication

logger.publisher.BILLING_SUBSYSTEM logLevel:Log Level

logger.publisher.BILLING_SUBSYSTEM componentID: Component ID

logger.publisher.SNMP_SUBSYSTEM logLevel:Log Level

logger.publisher.SNMP_SUBSYSTEM componentID: Component ID

logger.publisher.MMSC_SUBSYSTEM logLevel:Log Level

logger.publisher.MMSC_SUBSYSTEM componentID: Component ID

logger.publisher.TESTCLIENT logLevel: Log Level

logger.publisher.TESTCLIENT componentID: Component ID

logger.publisher.PERFORMANCE_MANAGER

logLevel:Log Level

logger.publisher.PERFORMANCE_MANA

GER componentID: Component ID

.logger.publisher.CONFIG_MANAGER logLevel:Log Level

.logger.publisher.CONFIG_MANAGER componentID: Component ID

logger.publisher.MSGSTORE logLevel:Log Level

logger.publisher.MSGSTORE componentID: Component ID

logger.publisher.UI_SUBSYSTEM logLevel:Log Level

logger.publisher.UI_SUBSYSTEM componentID: Component ID

logger.publisher.DBSYSTEM logLevel: Log Level

logger.publisher.DBSYSTEM componentID: Component ID

Parameter Property






DN0182152 129


logger.listener.trapManager persistentType: Persistent Type for the TrapListener Application

logger.listener.trapManager destinationID:Destination ID of the TrapListener Application

logger.fileHandler.tgw mountName: Mount Name

logger.fileHandler.tgw baseFileName: Initial File Name for the LogFile

logger.fileHandler.tgw rotationCounter: Rotation Counter

logger.fileHandler.tgw baseDirName: Base Directory Name forstoring the Logs

logger.fileHandler.tgw maxFileSize: Maximum size of a file afterwhich the rotation is done

mmsc.sender perfDataMode:Boolean value which indicateswhether performance data collection is

being performed (not supported R1)

mmsc.sender mmReceivedTracingLevel: Tracing level forreceived events in MMSC Sender (0- OFF,1 - MMSC ONLY, 2 - BILLING ONLY, 3 -ALL)

mmsc.sender mmRejectedTracingLevel: Tracing level forrejected events in MMSC Sender (0- OFF, 1- MMSC ONLY, 2 - BILLING ONLY, 3 -ALL)

mmsc.sender screenSendingSubscriber: Boolean value which

indicates whether screening of the sendingsubscriber for outgoing messages is

performed

Parameter Property




130


mmsc.sender destinationAddressesRequired: Boolean valuewhich indicates whether destination

address(es) are required for outgoingmessages

mmsc.sender performLicenseChecking: Boolean value whichindicates whether license checking andupdating for outgoing messages is

performed

mmsc.sender mmSentTracingLevel: Tracing level forsuccessfully sent events in MMSC Sender(0- OFF, 1 - MMSC ONLY, 2 - BILLING

ONLY, 3 - ALL)

mmsc.sender tracingLevel: Tracing level for the MMSCSender (0- OFF, 1 - MMSC ONLY, 2 -BILLING ONLY, 3 - ALL)

mmsc.sender debugMode: Debugmode for MMSCreceiver components

mmsc.receiver.roareceiver mmProcessedTracingLevel: Tracing level forsuccessfully processed events in MMSCReceiver (0- OFF, 1 - MMSC ONLY, 2 -

BILLING ONLY, 3 - ALL)

mmsc.receiver.roareceiver continueWithoutRosSubscriber: Boolean valueto indicate if Sync Receiver-Originatedrequest should be rejected if the subscriberis not found

mmsc.receiver.roareceiver screenRoaReceivingSubscriber: Boolean valueto indicate whether to screen the receivingsubscriber for Async Receiver-OriginatedMessages

mmsc.receiver.roareceiver continueWithoutDfaSubscriber: Boolean valueto indicate if Async Delivery-Failurerequest should be rejected if the subscriberis not found

Parameter Property




DN0182152 131


mmsc.receiver.roareceiver screenDfaReceivingSubscriber: Boolean valueto indicate whether to screen the receiving

subscriber for Async Delivery Failures

mmsc.receiver.roareceiver continueWithoutRoaSubscriber: Boolean valueto indicate if Async Receiver-Originatedrequest should be rejected if the subscriberis not found

mmsc.receiver.roareceiver screenDfsSendingSubscriber: Boolean value toindicate whether to screen the sendingsubscriber for Sync Delivery Failures

mmsc.receiver.roareceiver mmReceivedTracingLevel: Tracing level forreceived events in MMSC Receiver (0-OFF, 1 - MMSC ONLY, 2 - BILLINGONLY, 3 - ALL)

mmsc.receiver.roareceiver debugMode: Debugmode for MMSCReceiver components

mmsc.receiver.roareceiver perfDataMode: Boolean value to indicatewhether performance data is collected (notsupported R1)

mmsc.receiver.roareceiver screenDfaSendingSubscriber: Boolean value toindicate whether to screen the sendingsubscriber for Async Delivery Failures

mmsc.receiver.roareceiver performLicenseChecking: Boolean value toindicate license checking and collection

mmsc.receiver.roareceiver screenRoaSendingSubscriber: Boolean value toindicate whether to screen the sendingsubscriber for Async Receiver-Originated

Messages

mmsc.receiver.roareceiver continueWithoutDfsSubscriber: Boolean valueto indicate if Sync Delivery-Failure requestshould be rejected if the subscriber is notfound

Parameter Property




132


mmsc.receiver.roareceiver screenRosReceivingSubscriber: Boolean valuewhich indicates whether or not to screen the

receiving subscriber for Sync Receiver-Originated Messages

mmsc.receiver.roareceiver tracingLevel: Tracing level (0- OFF, 1 -MMSC ONLY, 2 - BILLING ONLY, 3 -ALL)

mmsc.receiver.roareceiver mmRejectedTracingLevel: Tracing level forrejected events in MMSC Receiver (0-OFF, 1 - MMSC ONLY, 2 - BILLINGONLY, 3 - ALL)

mmsc.receiver.roareceiver screenDfsReceivingSubscriber: Boolean valueto indicate whether to screen the receivingsubscriber for Sync Delivery Failures

mmsc.receiver.roareceiver screenRosSendingSubscriber: Boolean valuewhich indicates whether or not to screen thesending subscriber for Sync Receiver-Originated Messages

mmsc.servlet.roaservlet mmReceivedTracingLevel: Tracing Level

should be set if processed event is to belogged.

mmsc.servlet.roaservlet mmProcessedTracingLevel: Tracing Levelshould be set if processed event is to belogged

mmsc.servlet.roaservlet perfDataMode: Peformance data collecting is performed with this set (not supported R1)

mmsc.servlet.roaservlet mmRejectedTracingLevel: Tracing Levelshould be set if processed event is to be

logged.

mmsc.servlet.roaservlet performLicenseChecking: License checking is performed with this set

Parameter Property




DN0182152 133


mmsc.servlet.roaservlet maximumMessageContentLength: Maximumallowed incoming message content length

(in bytes)

mmsc.servlet.roaservlet debugMode: Debug mode for servlet

mmsc.servlet.roaservlet tracingLevel: Overall Tracing Level - set tothe appropriate level

mmsc.servlet.dfsservlet mmReceivedTracingLevel: Tracing Levelshould be set if processed event is to belogged.

mmsc.servlet.dfsservlet mmProcessedTracingLevel: Tracing Levelshould be set if processed event is to belogged.

mmsc.servlet.dfsservlet perfDataMode: Peformance data collecting is performed with this set (not supported R1)

mmsc.servlet.dfsservlet mmRejectedTracingLevel: Tracing Levelshould be set if processed event is to belogged.

mmsc.servlet.dfsservlet performLicenseChecking: License checking is performed with this set

mmsc.servlet.dfsservlet maximumMessageContentLength: Maximumallowed incoming message content length(in bytes)

mmsc.servlet.dfsservlet debugMode: Debug mode for servlet

mmsc.servlet.dfsservlet tracingLevel: Overall Tracing Level - set to

the appropriate level

mmsc.servlet.rosservlet mmReceivedTracingLevel: Tracing Levelshould be set if processed event is to belogged.

Parameter Property




134


mmsc.servlet.rosservlet mmProcessedTracingLevel: Tracing Levelshould be set if processed event is to be

logged.

mmsc.servlet.rosservlet perfDataMode: Peformance data collecting is performed with this set (not supported R1)

mmsc.servlet.rosservlet mmRejectedTracingLevel: Tracing Levelshould be set if processed event is to belogged.

mmsc.servlet.rosservlet performLicenseChecking: License checking is performed with this set

mmsc.servlet.rosservlet maximumMessageContentLength: Maximumallowed incoming message content length(in bytes)

mmsc.servlet.rosservlet debugMode: Debug mode for servlet

mmsc.servlet.rosservlet tracingLevel: Overall Tracing Level - set tothe appropriate level

mmsc.servlet.dfaservlet mmReceivedTracingLevel: Tracing Levelshould be set if received event is to belogged.

mmsc.servlet.dfaservlet mmProcessedTracingLevel: Tracing level forsuccessfully processed events in Delivery-Failure Async Servlet (0- OFF, 1 - MMSCONLY, 2 - BILLING ONLY, 3 - ALL)

mmsc.servlet.dfaservlet perfDataMode: Peformance data collecting is performed with this set (not supported R1)

mmsc.servlet.dfaservlet mmRejectedTracingLevel: Tracing Levelshould be set if received event is to belogged.

mmsc.servlet.dfaservlet performLicenseChecking: License checking is performed with this set

Parameter Property




DN0182152 135


mmsc.servlet.dfaservlet maximumMessageContentLength: Themaximum message content length (in

bytes) for Delivery-Failure Asyncmessages

mmsc.servlet.dfaservlet debugMode: The debugmode for theDelivery-Failure Async Servlet

mmsc.servlet.dfaservlet tracingLevel: Overall Tracing Level - set tothe appropriate level

Parameter Property




136




DN0182152 137


Symbols

(CDR) Call Detail Record 97

(COS) Class of Service 97

(EGW) Nokia Multimedia E-mailGateway 101

(MSISDN) Mobile Subscriber ISDN

Number 98

(NA) New Album 98

(PA) Personal Album 98

(SMSC) Short Message Service

Center 99

(SNMP) Simple Network

Management Protocol 99

(TGW) Nokia Multimedia Terminal

Gateway 11

(VGW) Nokia Multimedia Voice

Gateway 101

A

Activating

Class of Service plans 54

TGW subscribers 40

Adding TGW subscribers 35Admin. Account button 27

Administrator

Administrator tab 69

defined 97

Administrator Account Settings

screen

changing the administrator pass-

word 70

Assigning Class of Service plans

Assign Class of Service pop-up 41

steps for 41

Audience for this guide

system administrators 12

system supervisors 12

Avoiding

switching between General and

TGW tabs 31

switching between System and

Events tabs 32

use of Refresh button 31use of Reload button 31

B

Backup overview 93

Backup schedules 94

Billing

Configuration properties 58

Billing system 32

Browser issues

context-sensitive help browser is-

sues 32

downloading log files from IE 5.1

32, 85

online help browser issues 32

Buttons

Admin. Account button 27

avoiding use of Refresh button 31

avoiding use of Reload button 31

Change button 71, 72Class of Service button 26

Configuration button 27

Finish button 36

Help button 27

Log button 27

Log Out button 27

navigational buttons 26

OK button 42

operational buttons 29Reset button 58

Search button 34

Subscribers button 26

C

Call Detail Record (CDR) 97

Cautions



138


avoiding use of Refresh button 31

avoiding use of Reload button 31

making an entry in your billing

system 32saving changes on each screen 31


TGW tabs 31


Events tabs 32

Change button 71, 72

Changing passwords

administrator password 70

supervisor password 72

Class of Service (COS) plans

active, defined 47

defined 97

inactive, defined 45, 47

overview 46

Class of Service button 26

Class of Service Plans screen

activating Class of Service plans

54

Class of Service Plans toolbar 46creating new COS plans 47

deactivating COS plans 51 – 53

deactivating from Class of Service

Plans screen 51

deactivating from Edit Class of

Service Information

screen 52

editing COS plans 49

inactive Class of Service plan, de-

fined 45, 47Configuration button 27

Configuration screen

enabling billable events 65

enabling event logging 66

enabling SNMP alarms 66

making an entry in your billing

system 32

managing events 64 – 65

managing system properties 58

System tab configuration parame-

ters 56System tab properties 57

tabs 56

Configuring

parameters 56

properties 56

Context-sensitive help 32

COS features

description 105

Max NA size 105

Max PA size 105

NA store time 105

PA store time 106

Self-provisioning 106

Create Subscriber screen

Address field 103

Billing id* field 103

City field 104

Class of Service* field 105

Country field 104Device e-mail* field 104

E-mail address field 104

field descriptions for Create Sub-

scriber screen 103

First name* field 103

Last name* field 103

MSISDN* field 104

Password* field 103

Postal code field 104SMSC MSISDN* field 104

State/Province field 104

Status field* 103

User name field* 103

Creating new COS plans 47



DN0182152 139


D

Deactivating

COS plans 51 – 53

from Class of Service Plans screen51

from Edit Class of Service Infor-

mation screen 52

from Edit Subscriber Information

screen 39 – 40

from Subscriber Search Criteria

screen 38 – 39, 40 – ??,

40 – ??, 40 – ??

TGW subscribers 38 – 40

Defining subscriber searches

by billing ID 43

by COS 43

by E-mail 43

by last name 43

by MSISDN 43

by starting prefixes 44

by User Name 43

Deleteing

Subscribers 40Documentation

for Nokia Artuse™ Multimedia

Messaging Service Center

(MMSC) 20

for Nokia Multimedia Terminal

Gateway Release (TGW)

16

revision history 21

sending comments 21

typographic conventions 15

Download column for log file 85

Download link for log file 85

E

Editing

COS plans 49

TGW subscribers 37

Enabling

billable events 65

event logging 66SNMP alarms 66

Events 56

enabling billable events 65

enabling event logging 66

enabling SNMP alarms 66

Events tab 65, 66

F

Field descriptions for Create

Subscriber screen 103

Fields

Address field 103

Billing id* field 103

City field 104

Class of Service* field 105

Confirm new password field 70,

71, 72

Country field 104

Current password field 70Description field 47

Description* field 50

Device e-mail* field 104

E-mail address field 104

First name* field 103

Last name* field 103

MAX NA size (MB)* field 48

MAX PA size (MB)* field 48

MSISDN field 104 NA Storage time (days)* field 50

Name* field 47

New password field 70, 72

PA Storage time (Days)* field 48,

50

Password* field 103

Postal code field 104



140


Search for field 42

Self-provisioning field 48, 51

Show field 40

SMSC MSISDN* field 104State/Province field 104

Status field 40, 47, 50, 54

Status* field 103

User name* field 103

G

General tab 36, 47, 52, 53

Getting started

cautions 31

logging in 23

logging out 23

navigational buttons 26

navigational links 29

navigational tabs 28

operational buttons 29

toolbar options 27

H

Help button 27

L

Legacy phone owner, defined 98

Log button 27

Log Out button 27

Log screen

downloading a log file 85

Logging in

as administrator 23

as supervisor 25

default password 24, 25

default user name 24, 25

Logging Out 26

M

Making an entry in billing system 32

Managing

Class of Service plans 45 – 54

events 58 – ??, 64 – 67

TGW subscribers 33 – 44

MMT owner, defined 98

Multimedia Messaging Service

Center( MMSC)

documentation 20

N

New Album, defined 98 Nokia Multimedia E-mail Gateway

(EGW) 101

Nokia Multimedia Voice Gateway

(VGW) 101

Non TGW subscriber, defined 98

O

OK button 42

Online help 32

Options

Active option 39, 40

Active option on Edit Subscriber

Information screen 35

Assign COS option 35, 41

Cancel option 48

Create New Subscriber option 35

Deactivate option 35, 38, 41, 46,

52

Inactive option 40 New COS Plan option 46, 47

Update option 38, 49, 50, 53, 54,

64, 66, 67

P

Password

changing administrator password



DN0182152 141


70

changing supervisor password 72

Configuration property 62

Personal Album, defined 98Product descriptions

Nokia Multimedia E-mail Gate-

way (EGW) 101

Nokia Multimedia Terminal Gate-

way (TGW) 11

Nokia Multimedia Voice Gateway

(VGW) 101

R

Refresh button 31

Reload button 31

Reset button 58

S

Saving changes on each screen 31

Screens

Administrator Account Settings

screen 69 – 72

Class of Service plans screen 46 – 54

Configuration screen 55 – 67

Create Class of Service

step 2 of 2 screen 48

Edit Class of Service Information

screen 52

Edit Subscriber Information

screen 37, 39

Subscriber Search Criteria screen

33 – 44Search for drop-down list 43

Searching for TGW subscribers 42 –

44

Short Message Service Center

(SMSC), defined 99

Simple Network Management

Protocol (SNMP), defined 99

SMS

Configuration properties 60

Subscriber Search Criteria screen

activating TGW subscribers 40adding TGW subscribers 35

assigning Class of Service plans

41

deactivating TGW subscribers 37

editing TGW subscribers 37

getting started 33

Search Results toolbar 34

searching for TGW subscribers 42

Subscriber Search Criteria toolbar

34

Subscriber searches, defining

by Billing ID 43

by COS 43

by E-mail 43

by last name 43

by MSISDN 43

by starting prefixes 44

by user name 43

Subscriber, defined 99Subscribers button 26

Subscribers, types of

legacy phone owner 12

MMT owner 13

non TGW subscriber 13

TGW subscriber 13

Supervisor

defined 99

Supervisor tab 70Switching

between General and TGW tabs

31

between System and Events tabs

32

System configuration backup 93



T

Tabs

Administrator tab 69

Events tab 56, 65, 66

examples of 28

General tab 36, 47, 49, 52, 53

Supervisor tab 70


TGW tabs 31


Events tabs 32

System tab 56

TGW tab 31, 48, 49, 50TGW subscriber, defined 99

TGW tab 48, 50

Toolbars

Class of Service Plans toolbar 46,

47, 49, 52

Configuration Parameters/Proper-

ties toolbar 58

Create Class of Service

step 1 of 2 toolbar 47

step 2 of 2 toolbar 48Edit Class of Service toolbar 50

Edit S b ib I f ti t l

User data backup 94

TGW 1.0.3 Admin Guide

Documents