DN0182152 1

Issue 1-3 en Copyright © Nokia Corporation 2002.
Nokia Multimedia Terminal Gateway Release 1.0.3
Part 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 this
document 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 is
submitted. 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 the
instructions contained in the document are adequate and free of material errors and
omissions. This document is provided on an “AS IS” basis, with no warranty of any kind.
NOKIA CORPORATION SPECIFICALLY DISCLAIMS ANY AND ALL IMPLIED
WARRANTIES, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
FITNESS, MERCHANTABILITY AND TITLE. Further, the information or statements
contained 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 Nokia
Corporation in the agreement under which this document is submitted.
Limitation of Liability. Nokia Corporation’ liability for any errors in the document is
limited 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, ECONOMIC
OR CONSEQUENTIAL, that might arise from the use of or inability to use this document
or anything contained herein.
Intellectual Property Rights. This document and the product it describes are protected by
copyright according to applicable laws. No part of this document may be reproduced or
transmitted in any form or by any means without the prior written permission of Nokia
Corporation. Nokia and Nokia Connecting People are registered trademarks of Nokia
Corporation.
Product names mentioned in this document may be trademarks of their respective
companies and are mentioned for identification purposes only.
Copyright © Nokia Corporation 2002. All rights reserved.
DN0182152 3
Issue 1-3 en Copyright © Nokia Corporation 2002.
Table of contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Product description for TGW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.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
Copyright © Nokia Corporation 2002.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.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. . . . . . . . . . . . . . . 51
4.5.2 Deactivating from the Edit Class of Service Information screen. . . . . . 52
4.6 Activating Class of Service plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
5 Configuring parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
5.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
7.1 Overview of the Logging System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
7.1.1 Events Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
7.2 Logging Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
DN0182152 5
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
9.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
Copyright © Nokia Corporation 2002.
DN0182152
Issue 1-3 en
7
Copyright © Nokia Corporation 2002.
List of Figures
Figure 1 Overview of mobile subscribers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 2 User name field on the Log In screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 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 . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Figure 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 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
Copyright © Nokia Corporation 2002.
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
Copyright © Nokia Corporation 2002.
List of Tables
Table 1 Types of mobile subscribers (defined) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 2 Overview to Administrator Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Table 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
Copyright © Nokia Corporation 2002.
Preface
DN0182152 11
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 Nokia
Artuse™ Multimedia Messaging Service Center (MMS Center). The MMS Center
delivers messages composed of text, images, and other media types between multimedia
terminals.TGW extends the MMS Center by providing storage and views of multimedia
messages. In addition, TGW provides multimedia support for legacy phone owners via
SMS notification, allowing legacy phone owners to view their multimedia messages via
the Web.
1.2 About this document
This document is the Administrator Guide for the Nokia Multimedia Terminal Gateway
Release 1.0.3 . TGW is part of the Multimedia Messaging Service Application Suite.
The Administrator Guide describes routine tasks for administering TGW. These tasks
include 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 the
separate EGW Administrator Guide or VGW Administrator Guide for
specific information on these applications.
The screen captures in this documentation reflect a system that has only
TGW installed.
For a product description of EGW and VGW, see Appendix B.
12
Copyright © Nokia Corporation 2002.
1.3 Audience
This document has two intended audiences:
• System administrators who work directly for operators and who use MMS
Application Administrator to configure and troubleshoot airtime services for TGW
subscribers.
• System supervisors who only access the Subscribers screen of the MMS Application
Administrator for the sole purpose of managing TGW subscribers. The following
figure and table illustrate the various mobile subscribers to which TGW and related
documentation 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
EGW
Subscribers
VGW
Subscribers
Preface
DN0182152 13
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 the
system supervisor. Refer to the following table to determine how/if each
chapter relates to these two audiences.
MMT owner Refers to a subscriber whose mobile terminal has
multimedia capabilities.
TGW subscriber Refers to a mobile phone owner who subscribes to Nokia
Multimedia Terminal Gateway (TGW) services and
therefore has a PA (Personal Album).
Non TGW subscriber Refers to a mobile phone owner who does not subscribe
to Nokia Multimedia Terminal Gateway (TGW) and
therefore does not have a PA (Personal Album).
EGW subscriber Refers to a mobile phone owner who subscribes to Nokia
Multimedia E-mail Gateway (EGW) services. For a
description of EGW, see “Product descriptions for EGW
and VGW” on page 101.
VGW subscriber Refers to a mobile phone owner who subscribes to Nokia
Multimedia Voice Gateway (VGW) services. For a
description of VGW, see “Product descriptions for EGW
and 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 of
the TGW MMS Application
Administrator as well as how to
navigate the application via buttons,
toolbar options, tabs, operational
buttons, and links.
Also provides important cautions or
tips, such as saving changes on each
screen and avoiding use of the
Reload/Refresh button.
System Administrators
and System Supervisors
Table 2 Overview to Administrator Guide
14
Copyright © Nokia Corporation 2002.
Managing TGW
subscribers
Describes using the Subscribers
screen.
Also describes these tasks: creating
and assigning Class of Service,
adding, editing, deactivating/
activating TGW subscribers, and
searching for TGW subscribers.
System Administrators
and System Supervisors
Managing Class
of Service plans
Describes using the Class of Service
screen. A Class of Service (COS) is a
group of features that may be
configured for a group of wireless
terminal users.
Also describes how to manage Class
of Service plans, including creating
new Class of Service plans and
deactivating/activating existing
Class of Service plans.
System Administrators
Configuring
parameters
Describes using the Configuration
screen.
Also describes tasks managing
system properties and events.
System Administrators
Changing
administrator
account settings
Describes using the Administrator
Account screen.
Also describes how to change the
administrator and/or supervisor
password.
System Administrators
Displaying the
log file
Describes using the Log screen.
Also describes displaying and
downloading a log file.
System Administrators
Troubleshooting
Tips
Describes troubleshooting for issues
such as configuring the MMSC,
SMS message building, and the
SMTP server.
System Administrators
Appendix A Defines acronyms and terminology. System Administrators
and System Supervisors
Chapter Description Audience
Table 2 Overview to Administrator Guide (Continued)
Preface
DN0182152 15
Issue 1-3 en Copyright © Nokia Corporation 2002.
1.6 Typographic conventions
The following notes and table provide a list of the typographic conventions that appear in
this document.
Warning: This information helps avoid damage to the phone, personal injury, or
property damage.
Caution: This information helps avoid loss of data.

The task icon marks the beginning of a procedure or task sequence.
1.
2.
3.
Appendix B Provides a product description for
Multimedia E-mail Gateway
(EGW) and Nokia Multimedia
Voice Gateway (VGW).
System Administrators
and System Supervisors
Appendix C Provides descriptions and examples
of the information required in each of
the fields located under the General
tab on the Create Subscriber: Step 1
of 1 screen.
Also provides a description of the
COS features listed on the Create
Subscriber: Step 1 of 1 screen.
System Administrators
and System Supervisors
Appendix D Lists and describes events. System Administrators
Appendix E Lists and describes configuration
parameters.
System Administrators
Chapter Description Audience
Table 2 Overview to Administrator Guide (Continued)
16
Copyright © Nokia Corporation 2002.
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 command
line arguments and database fields.
\ Backslash at the end of lines indicates that
there is insufficient space and the line is
continued in the space below.
| Vertical bar used between choices, for
example in variable data in configuration
file arguments.
“” Used for section and chapter titles.
Table 3 Typographic conventions
Preface
DN0182152 17
Issue 1-3 en Copyright © Nokia Corporation 2002.
Document Document number Audience description
Administrator’s
Web-based Help
Not Applicable Intended for system
administrators who work
directly for the operators and
who are responsible for
configuring and
troubleshooting airtime
services for subscribers.
Subscriber’s
Web-based Help
Not Applicable Intended for TGW subscribers
who are accessing their
messages via their multimedia-
messaging terminal.
Subscriber’s
WAP-based
Help
Not Applicable Intended for TGW subscribers
and non TGW subscribers who
are accessing TGW with the
Wireless Application Protocol
(WAP).
Guide to
Documentation
DN01154073 Intended for anyone seeking
guidelines on how to use the
TGW documentation set.
Describes each document in the
set. Also includes information
on receiving documentation
updates and ordering
documentation.
TGW Subscriber
Content
DN0182164 Intended for operators as
boilerplate content that the
operators can customize for
their TGW subscribers.
Boilerplate content describes
how TGW subscribers use the
MMT as it references TGW.
TGW R1
Commissioning
Guide
DN0182176 Intended for system experts
who install TGW R1 at operator
sites. In most cases, installers
are Nokia employees, though
they can also be installers from
the operator or from a third-
party system integrator.
Table 4 TGW documentation set
18
Copyright © Nokia Corporation 2002.
Customizing the
TGW Interfaces
DN0182188 Intended for system integrators
and operators who are
customizing field labels, screen
colors, online help, and remote
log in procedure for the
subscriber, non TGW
subscriber, and WAP interfaces.
Also intended for translators
who are responsible for
translating the subscriber, non
TGW subscriber, and WAP
interfaces.
Third Party
Development
Guide
DN01161124 Intended for software
developers writing applications
external to TGW but desiring to
integrate with TGW-supplied
functionality. Software
developers writing external
TGW applications can use this
document to gain an
understanding of the TGW
functionality that has been
made available. For each TGW
interface exposed, this
document presents conceptual
information, description of the
exposed interface, and example
interacting code.
TGW Database
Schema Guide
DN01161124 Intended for database
administrators who need to
know the schema that TGW
uses to produce backups or
queries as well as the
relationship between the
various tables.
Release Notes DN0182191 Intended for installers. Also
intended for system
administrators who work
directly for the operators and
who are responsible for
configuring and
troubleshooting airtime
services for TGW subscribers.
Document Document number Audience description
Table 4 TGW documentation set (Continued)
Preface
DN0182152 19
Issue 1-3 en Copyright © Nokia Corporation 2002.
1.8 Related documentation
In addition to TGW, the Application Gateways product line at Nokia offers Nokia
Multimedia E-mail Gateway (EGW) and Nokia Multimedia Voice Gateway (VGW).
The documents described in the following table provide steps on how to administer these
related products.
Technical Notes Available online at
http://
www.online.nokia.com
Intended for installers,
administrators, and operators.
Document Document number Audience description
Table 4 TGW documentation set (Continued)
Document Document number Audience description
EGW Administrator
Guide
DN0182043 Intended for system
administrators who work
directly for the operators
and who are responsible
for configuring and
troubleshooting airtime
services for EGW
subscribers.
VGW Administrator
Guide
DN023897 Intended for system
administrators who work
directly for the operators
and who are responsible
for configuring and
troubleshooting airtime
services for EGW
subscribers.
Table 5 Related administrator documents for the AG product line
20
Copyright © Nokia Corporation 2002.
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 following
documents. 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 about
navigating the MMSC GUI and
background on basic tasks.
Message Handling DN00148708 Provides information about multimedia
message format, routing, and how
messages are handled in the MMSC.
Installing and
Integrating MMSC
DN00148798 Provides instructions for installing and
configuring the MMSC.
Operating MMSC DN00148786 Designed for users who need procedures
for daily, weekly, monthly, and occasional
operations.
Configuring MMSC DN00148774 Provides comprehensive instructions on
configuring the MMSC with a focus on
customizing the product.
External Application
Developer’s Guide
DN00148759 Provides guidelines for developing
interfaces 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
Issue 1-3 en Copyright © Nokia Corporation 2002.
1.9 If you have documentation comments
The Application Gateways product line at Nokia is always interested in improving its
documentation. We value your comments about this guide and other Nokia
documentation.
Simply e-mail your documentation comments to Application Gateways at
ag.documentation@nokia.com
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
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 system
administrators 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 In
screen:
1. Open a browser and enter the URL to access the MMS Application Administrator
login 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
Copyright © Nokia Corporation 2002.
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 immediately
change your password after logging in for the first time. Only administrators
can change the administrator or supervisor password. (“Changing
Administrator Account settings” on page 69 for steps on changing
passwords.)
Figure 3 Password field on the Log In screen
Getting started
DN0182152 25
Issue 1-3 en Copyright © Nokia Corporation 2002.
4. Click the Log In button.
The Subscribers screen appears. You are now logged in to MMS Application
Administrator as the administrator.
Through the navigational menu in the left frame, the administrator has access to the
following 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 Administrator
login 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 the
default password.
4. Click the Log In button.
The Subscribers screen appears. You are now logged in to MMS Application
Administrator as the supervisor. The supervisor has access to the Subscribers screen.
26
Copyright © Nokia Corporation 2002.
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 in
to 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 navigational
frame 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
Issue 1-3 en Copyright © Nokia Corporation 2002.
2.2.2 Toolbar options
Toolbar options are available from MMS Application Administrator screens. These
options access additional screens or operations from the Subscribers, Class of Service,
Configuration, Administration Account, and Log screens.
For example, from the Class of Service Plans toolbar, the options are New COS Plan and
Deactivate.
Figure 4 Example of toolbar options
Click the Configuration button to view, reset, or update the
general system or events configuration.
Click the Admin. Account button to change the administrator or
supervisor 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 Application
Administrator.
Button Description
Table 8 Overview of navigational buttons (Continued)
28
Copyright © Nokia Corporation 2002.
To create a new COS plan, click the Create New COS Plan option from the Class of
Service Plans toolbar.
To deactivate selected COS plans, click the Deactivate option from the Class of Service
Plans toolbar.
2.2.3 Navigational tabs
Navigational tabs let you access additional screens available from the main MMS
Application Administrator screens.
For example, from the Configuration screen, the following navigational tabs are
available: 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
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 a
subscriber 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 Search
Results area. From the Class of Service screen, similar links are also available under the
Name category of the Class of Service Plans area. The links let you access additional
screens for editing subscriber information or Class of Service plans.
For example, to edit subscriber information (including name, MSISDN, e-mail address, or
COS), click the name for the subscriber information that you want to edit.
For example, under the Name category click the name Jon Keatsling.
30
Copyright © Nokia Corporation 2002.
Figure 8 Example of navigational link
Clicking the subscriber’s name lets you access the Edit Subscriber Information screen for
that subscriber.
Figure 9 Edit Subscriber Information screen
Getting started
DN0182152 31
Issue 1-3 en Copyright © Nokia Corporation 2002.
In the same way, if you click a Class of Service plan under the Name category of the Class
of 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 configuration
parameters; changing values for configuration parameters can result in
system failure. Change the values for configuration parameters only if
Nokia Technical Support clearly recommends that you take such
action.
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 the
Configuration screen/Events tab
2.4.1 Saving changes on each screen
Caution: When you make changes on any of the screens for MMS Application
Administrator, it is important to save the changes on each screen before moving on to a
different 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 in
MMS Application Administrator. If you use either the Refresh or Reload button, you will
lose all the data you have on your current screen when MMS Application Administrator
returns 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 of
Service screen, you must click Update (before switching to the next tab), or you will lose
your data.
32
Copyright © Nokia Corporation 2002.
2.4.4 Switching between the System and Events tabs
Caution: When you switch between the System and Events tabs on the Configuration
screen, you must click Update (before switching to the next tab), or you will lose your
data.
2.4.5 Making an entry in your billing system
Caution: You must make an appropriate entry in your billing system when you make
events billable from the Events tab on the Configuration screen.
2.5 Known browser issues
The known browser issues for MMS Application Administrator are as follows:
• Downloading log files from IE 5.1
• Online help browser issues
2.5.1 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 known issue is only true for IE 5.1. The functionality works properly with IE 5.5 and
Netscape versions (4.7 and higher).
2.5.2 Online help browser issues
The following table is a summary of compatibility issues between the online and/or
context-sensitive help with certain browsers.
Browser Online Help Context Sensitive Help
Explorer 5.0 Yes Yes
Explorer 5.5 Yes Yes
Netscape 4.7 Yes No
Netscape 6.0 Yes Yes
Netscape 6.1 Yes Yes

Table 9 Browser compatibility issues between online help and context-sensitive
help
Managing TGW subscribers
DN0182152 33
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 system
administrators and system supervisors.
Topics in this chapter are as follows:
• 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 Plan
screen, create a Class of Service plan (only the administrator can complete
this step). 2.) From the Subscribers screen, add the subscriber, which
includes selecting the COS plan to assign to that subscriber.
34
Copyright © Nokia Corporation 2002.
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 subscribers
according 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 TGW
subscribers 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 criteria
you 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).
Managing TGW subscribers
DN0182152 35
Issue 1-3 en Copyright © Nokia Corporation 2002.
The Search Results toolbar options are as follows:
Assign COS option - lets you assign Class of Service plans to TGW subscribers in the
database.
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 subscriber
accounts 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 have
a 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 system
administrator 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
Copyright © Nokia Corporation 2002.
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 of
the fields.
3. Click Finish.
Managing TGW subscribers
DN0182152 37
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 subscriber
information.
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
Copyright © Nokia Corporation 2002.
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 your
changes 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 at
the same time.
To deactivate TGW subscribers from the Subscriber Search Criteria screen, follow these
steps:
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).
Managing TGW subscribers
DN0182152 39
Issue 1-3 en Copyright © Nokia Corporation 2002.
Note: When you deactivate TGW subscribers, you are making the TGW subscriber
accounts 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 have
a 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, follow
these steps:
1. Under the Search Results toolbar, click the user name for the TGW subscriber whom
you 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
Copyright © Nokia Corporation 2002.
3. In the Status field, change the Active option to Inactive.
Note: When you deactivate TGW subscribers, the subscriber information still
exists in the database. You can reactivate TGW subscriber accounts at any
time, and your TGW subscribers can resume using the service. To reactivate
subscriber accounts, change the Inactive option to Active on the Edit
Subscriber 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 all
subscribers or by completing a search for inactive subscribers.
For example, under the Subscriber Search Criteria toolbar, select Inactive from the
drop-down list in the Show field. Under the Search Results toolbar, MMS
Application 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 to
Active.
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 can
delete 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:
Managing TGW subscribers
DN0182152 41
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 to
assign 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
Copyright © Nokia Corporation 2002.
Figure 20 Assign Class of Service pop-up
3. From the drop-down list box, select the COS to assign to the TGW subscribers you
selected.
Note: The Class of Service name in the screen capture is only for illustration
purposes. The administrator is responsible for creating the specific Class of
Service plans that appear in this drop-down list. For more information on
creating 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 your
search.
Figure 21 Defining your subscriber search from the Search for drop-down list
Managing TGW subscribers
DN0182152 43
Issue 1-3 en Copyright © Nokia Corporation 2002.
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, user
name, MSISDN, e-mail address, COS, or billing ID, depending on the criteria you
define.
For example, if you define Last Name as your search criteria, enter the TGW
subscriber’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 user
name.
Note: Must enter complete user
name to complete search.
MSISDN Enter the TGW subscriber’s MSISDN, a
prefix, or leave the field blank.
The MSI SDN is the mobile telephone
number used by a TGW subscriber in a
GSM/DCS network.
E-mail Enter the TGW subscriber’s e-mail
address.Partial entries such as prefixes are
allowed.
COS (Class of Service) Enter the TGW subscriber’s Class of
Service (COS).
A Class of Service(COS) is a group of
features 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
Copyright © Nokia Corporation 2002.
Figure 22 Searching for a subscriber by last name
Tip: You can also define searches based on starting prefixes. In the example
above, entering just M in the field to the right of the Search for drop-down list
returns 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 the
Search 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
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 a
group 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, Personal
Album (PA) storage time, and enabling/disabling self-provisioning (which includes
changing 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 inactive
COS plan still exists in the database, you cannot assign additional TGW subscribers to
that 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 system
administrators.
Topics in this chapter are as follows:
• 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
Copyright © Nokia Corporation 2002.
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 Service
Plans toolbar.
Content on COS Plans Area Description
Name Lists your TGW Class of Service plan.
A Class of Service (COS) is a group of
features that may be configured for a group
of wireless phone users.
Features that define a TGW COS include
maximum NA size, maximum PA size, NA
storage time, PA storage time, and
enabling/disabling self-provisioning
(which includes changing e-mail address,
password, and address).
Description Describes the terms of your TGW Class of
Service plan.
Table 11 Information under the Class of Service Plans toolbar
Managing Class of Service plans
DN0182152 47
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 plan
is active or inactive.
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 inactive
COS plan still exists in the database, you
cannot assign additional TGW subscribers
to 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
Copyright © Nokia Corporation 2002.
Note: To cancel adding general COS information, you can click the Cancel option
at 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 Application
Administrator allows depends on the capacity of your disk drive.
b.) In the MAX PA size (MB)* field, enter the maximum size in megabytes of the
Personal Album.
Note: See note for step 3a.
c.) In the NA Storage time (Days)* field, enter the maximum time in days to store
messages in the New Album.
d.) In the PA Storage time (Days)* field, enter the maximum time in days to store
messages 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.You
can also click the Previous option to see the information you entered on the
General tab.
Managing Class of Service plans
DN0182152 49
Issue 1-3 en Copyright © Nokia Corporation 2002.
4.4 Editing COS plans
Caution: When you switch between the General and TGW tabs on the Edit Class of
Service screen, you must click Update on each tab (before switching to the next tab), or
you will lose your data.
Note: When you edit an item in a COS plan, you affect all the subscribers assigned
to 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
50
Copyright © Nokia Corporation 2002.
2. To edit general COS information, complete the following steps under the General
tab:
a.) Next to the Status field, select Active or Inactive.
An active Class of Service plan is one that you can assign to new TGW
subscribers.
An inactive Class of Service plan is one that you have deactivated.Though the
inactive COS 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 membership in that COS plan.
Note: * indicates required field.
b.) In the Description field, enter a brief description of the COS plan features.
c.) From the Edit Class of Service toolbar, click the Update option.
Caution: If you go to the TGW tab without clicking Update first, you will lose your data.
3. To edit TGW COS information, complete the following steps under the TGW tab:
a.) Click the TGW tab.The TGW COS information appears.

Figure 28 Accessing TGW COS information under the TGW tab
Note: * indicates required field.
b.) In the MAX NA size (MB)* field, enter the maximum size of the New Album
in megabytes.
c.) In the MAX PA size (MB)* field, enter the maximum size of the Personal
Album in megabytes.
d.) In the NA Storage time (Days)* field, enter the maximum number of days to
store messages in the New Album.
e.) In the PA Storage time (Days)* field, enter the maximum number of days to
store messages in the Personal Album.
Managing Class of Service plans
DN0182152 51
Issue 1-3 en Copyright © Nokia Corporation 2002.
f.) Next to the Self-provisioning field, select the Enabled option to provide TGW
subscribers 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 inactive
COS 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 membership
in 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 the
same 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
Copyright © Nokia Corporation 2002.
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 the
database. You can reactivate the COS plan at any time. To reactivate the
COS 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 at
the 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 you
want to deactivate.

Figure 30 Selecting the COS plan to deactivate
Managing Class of Service plans
DN0182152 53
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 the
Status 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 to
Active on the Edit Class of Service screen.
Note: To cancel deactivation of a COS plan, you can click the Cancel option at any
time from the Edit Class of Service toolbar.
54
Copyright © Nokia Corporation 2002.
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.
Configuring parameters
DN0182152 55
Issue 1-3 en Copyright © Nokia Corporation 2002.
5 Configuring parameters
This chapter explains how to use the MMS Application Administrator Configuration
screen.
Intended audience. The intended audience for this chapter is TGW system
administrators.
Topics in this chapter are as follows:
• 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 and
specify TGW events for Call Detail Records (CDRs), SNMP alarms, and logging.
Note: Call Detail Records (CDRS) are billing records that contain all information
necessary 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
56
Copyright © Nokia Corporation 2002.
5.2.1 Tabs
Above the Configuration Parameters/Properties toolbar, you see System and Events
tabs that let you access additional screens. The following table describes the specific
screens that you can access by clicking the tabs.
5.2.2 System tab configuration parameters
The MMS Application Administrator uses a folder hierarchy to organize the various
categories and subcategories of the configuration parameters.The categories in this folder
hierarchy represent general parameters for your system.
The plus sign to the left of the folders for the configuration parameters shows that the
contents of a given folder or subfolder expand when you click it.
Figure 33 Configuration Parameters area on the Configuration screen
Tab Purpose
System Lets you access the System screen, where
you configure parameters and enter
properties for the general system.
Events Lets you access the Events screen, which
lists all of the events in the system. You can
specify if these events are billable, trigger
an SNMP Alarm, or cause an entry to be
written to the log. You can assign any
combination of these three choices to each
event.
Table 12 Description of tabs available from the Configuration screen
Configuring parameters
DN0182152 57
Issue 1-3 en Copyright © Nokia Corporation 2002.
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
Copyright © Nokia Corporation 2002.
5.3 Managing system properties
After you click the Configuration button, the screen for the System tab is displayed. You
can modify the default properties for a specific category or subcategory of the general
configuration parameters. If you must change the default properties for any category of
the configuration parameters, enter the modified properties in the Properties text boxes.
Caution: Nokia recommends that you do not change values for configuration parameters
described in “Configuration Parameters” on page 119. Changing values for configuration
parameters can result in system failure. Change the values for configuration parameters
only 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 or
subcategory. For example, click the billing folder.
The properties for that category appear to the right in the Properties area 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 Configuration
screen, you must click Update (before switching to the next tab), or you will lose your
data.
Note: To return properties to the last saved values, click Reset from the
Configuration Parameters/Properties toolbar.
5.3.1 Billing properties
The billing properties define how to create and process charging data. Charging data is
stored in a file called a Call Detail Record (CDR). CDRs contain all the information
necessary for a billing system to provide an invoice for a subscriber. For more information
about 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
Configuring parameters
DN0182152 59
Issue 1-3 en Copyright © Nokia Corporation 2002.
• 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.
Default: /opt/wluser/TGWBilling
• 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 (specified
as 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.
Default: /opt/wluser/TGWBilling
60
Copyright © Nokia Corporation 2002.
5.3.2 SMS properties
The SMS properties define how SMS messages are displayed on mobile terminals for
TGW 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 make
available. These properties are combined to create the non TGW subscriber SMS
message. Any combination of these fields cannot exceed 160 characters. The message is
constructed 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. For
example, to display the URL in an SMS message, the value for the
SHOW_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 are
used to construct the SMS message.
• SHOW_NON_SUBSC_TEXT_MSG
Specifies whether or not to display the non TGW subscriber text message. Use the
NON_SUBSC_TEXT_MSG property to specify the non-subscriber message
format.
Default: true
• NON_SUBSC_TEXT_MSG
Specifies the non TGW subscriber SMS message. The non TGW subscriber SMS
message 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.
Configuring parameters
DN0182152 61
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 to
specify 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 specify
the 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
Copyright © Nokia Corporation 2002.
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 the
MSG_EXPIRATION_TIME_LABEL property to specify the actual label
displayed.
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 the
expiration time.
• MSG_EXPIRATION_TIME_UNIT
Specifies 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 be
specified 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 is
optional. However, if it is set to false, and the SMS password property is defined, then the
subscriber must enter a password to log in to TGW.
Folder to open
/ag/security
subscriberPasswordRequired:
Default: false
Range: true; false
Configuring parameters
DN0182152 63
Issue 1-3 en Copyright © Nokia Corporation 2002.
5.3.4 Legacy message storage expiration
The ExpirationInterval property specifies the number of days a message is stored for
legacy devices.
Folder to open
/ag/msis/Tempstore
• ExpirationInterval
Default: 30
64
Copyright © Nokia Corporation 2002.
5.4 Managing events
The purpose of the TGW logging system is to record events generated by TGW
components. 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 a
trap manager, and CDR information is sent to a billing manager. This process allows the
appropriate manager to handle data according to specific events. For a list and description
of 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 TGW
system.

Figure 35 Events screen available from the Events tab
From the Events screen, you can specify if the events listed should be billable, trigger an
SNMP (Simple Network Management Protocol) alarm, or cause an entry to be written
to the log. Any combination of these three choices can be assigned to each event. The list
of events is read dynamically from the system.
Note: When you click Update, you simultaneously update the CDR, SNMP
Alarm, and Log functions for each Event Name that you have selected via
the 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.
Configuring parameters
DN0182152 65
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 be
written 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 read
dynamically from the system.
Figure 36 Allocating CDR, SNMP Alarm, and Log report functions to each Event
Name
5.4.1 Enabling billable events
You can make specific events billable; that is, enable TGW to generate a Call Detail
Record (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 make
events 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
Copyright © Nokia Corporation 2002.
4. Click Update.
When you click Update, you simultaneously update the CDR, SNMP Alarm, and
Log 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 that
manages IP networks, including individual network devices.
One feature of SNMP is an alarm mechanism by which managed notes can notify SNMP
managers of a problem (assuming that the device is configured to SNMP).
To enable SNMP alarms, follow these steps:
1. Click the Configuration button in the left navigational frame.
2. Click the Events tab.
3. Select the check box(es) under SNMP Alarm next to the corresponding event
name(s).
4. Click Update.
When you click Update, you simultaneously update the CDR, SNMP Alarm, and
Log functions for each Event Name that you have selected via the check boxes.
5.4.3 Enabling event logging
To create log entries, follow these steps:
1. Click the Configuration button in the left navigational frame.
2. Click the Events tab.
3. Select the check box(es) under the Log column next to the corresponding event
name(s).
Configuring parameters
DN0182152 67
Issue 1-3 en Copyright © Nokia Corporation 2002.
4. Click Update.
When you click Update, you simultaneously update the CDR, SNMP Alarm, and
Log functions for each Event Name that you have selected via the check boxes.
68
Copyright © Nokia Corporation 2002.
Changing Administrator Account settings
DN0182152 69
Issue 1-3 en Copyright © Nokia Corporation 2002.
6 Changing Administrator Account
settings
This chapter explains how to use the TGW Administrator Account screen.
Intended audience. The intended audience for this chapter is TGW system
administrators.
Topics in this chapter are as follows:
• 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 the
administrator or supervisor password.
6.2 Using the Administrator Account Settings screen
When you click the Admin. Account button, the Administration Account Settings screen
appears.This screen provides two navigational tabs, depending on whether you are
changing 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 your
system, and view your system log.
70
Copyright © Nokia Corporation 2002.
Click the Supervisor tab to change the supervisor password. Tasks that a supervisor can
complete are as follows: adding, editing, deactivating, activating, assigning Class of
Service 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
Issue 1-3 en Copyright © Nokia Corporation 2002.
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
Copyright © Nokia Corporation 2002.
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
Issue 1-3 en Copyright © Nokia Corporation 2001.
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 of
requests made by an TGW subsystem. TGW is capable of generating many events related
to 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 data
and 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” for
handling 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 Trap
Manager.
This chapter explains various aspects of the logging system, including the logging levels,
and shows how to use the TGW Log screen.
Intended audience. The intended audience for this chapter is TGW system
administrators.
Topics in this chapter are as follows:
• 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
Copyright © Nokia Corporation 2001.
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 organize
logging 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 sending
Publisher by its componentID.
2. The Logger sends log records to the queue, which is a standard Java Messaging
Service (JMS) queue. If Persistence is turned on for a particular Listener, then a copy
of each record is first stored in an external file for backup in the event of a system
crash.
3. The Listeners trap the appropriate event information and act upon it according to the
choices 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 for
any 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
Issue 1-3 en Copyright © Nokia Corporation 2001.
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 individual
events to be written to a log file, CDR file, or generated as an SNMP alarm. You can
access this screen from the MMS Application Administrator by clicking the
Configuration button, and then clicking on the Events tab.
The choices you make from this screen directly affect how each event gets handled by the
logging system.
Figure 44 TGW Events Screen
Pub. 1
Pub. 3
Pub. 2 Logger Logging Queue Trap Manager
File Handler
Billing Manager
File
Persistence
Log
Data
Event
Publishers
Listeners
.
.
..
76
Copyright © Nokia Corporation 2001.
7.2 Logging Levels
TGW generates many different events through its Publishers, each with their own default
log level settings. It is important to understand the logging levels used by individual
events and their Publishers. The levels determine the amount of event information that
gets 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 the
optimum level. You can view these by opening the Event Repository in
the folder ag/evtRpt. However, these levels are for viewing and
should not be changed. There is a system performance decrease every
time the repository is rewritten. Publisher log levels, however, can be
changed at run-time. Change a Publisher log level to increase or
decrease the amount of log information for a class of events which are
produced by that Publisher.
Level Category Description
7 Severe Indicates an unexpected, critical error occurred. In general, it
describes events that are very important and that prevent normal
program execution.
6 Warning Indicates the generated event is a potential problem, and not
necessarily an error. This event does not necessarily hamper
system functionality.
5 Info Indicates the generated event is merely an information message,
and not a warning or error. Typically, Info messages will be
written to the administrator console and are of interest to
administrators.
4 Config Used for indicating that there has been a configuration change in
the 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 most
amount of tracing information. Fine messages might include
minor failures which are recoverable. Setting a Publisher log
level to 1 (Finest) ensures a maximum amount of logging for its
class 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
Issue 1-3 en Copyright © Nokia Corporation 2001.
7.3 Publishers
“Publishers” refer to component-level objects that are responsible for sending event
logging information to the logging queue for processing. Each Publisher is directly
associated with a major subsystem level in the database, such as Billing, SNMP, and the
MMSC. 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, while
the MMSC Publisher sends only events pertaining to the MMSC.
78
Copyright © Nokia Corporation 2001.
7.3.1 Log Levels for Publishers vs. Events
Events have their own preset log levels, which can be viewed in the System screen under
the 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 follows
then 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 order
for that event to be logged. If the log level of a single event is less than its Publisher’s log
level, then the event is discarded and not logged. For example, if a single MMSC-related
event such as MMSC_RECEIVER_CREATE_FAILED_CRITICAL is set to 4, and the
MMSC Publisher’s log level is set to 5 or higher, then that event is discarded and not
logged. 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 and
a single event is a typical volume control slider mechanism. Log levels for single events
are fixed at certain levels (preset by Nokia), and should not be changed. Publisher log
levels, however, can be changed at run-time in order to increase or decrease the number of
logs for a class of events (e.g., billing events, SNMP events, etc.). Treat the Publisher log
level as a mechanism to use at any time to fine-tune the publishing rate of whole classes of
events. Never change log levels for individual events.
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.
1
7
log level
Publisher
log level
Single Event
6
5
4
3
2
Use the Publisher log level setting to
increase and decrease log entries for
an entire class of events.
Fixed at one level Configurable
0
1
7
6
5
4
3
2
0
more log entries
fewer log entries
Managing Log Files
DN0182152 79
Issue 1-3 en Copyright © Nokia Corporation 2001.
7.3.2 Publisher Configuration Parameters
Folder Location: ag/logger/publisher
• logLevel — This property sets the log
level for an individual Publisher
subsystem, which affects an entire
class of events. Each Publisher has a
default log level setting of 7, which
can be changed at run-time. See
“Changing the Log Level for
Publishers” for more details.
• componentID — Do not change the componentID! Changing this setting may
result in events not being filtered properly. Each Publisher has a unique componentID
that serves as an identifier. The Logger references this ID when a Publisher sends a log
record in order to help filter records.
If you change the log level value, click Update on the Properties toolbar to save the
change.
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 its
class 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 for
Publishers 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 generated
for that Publisher. A Publisher log level of 1, for example, will generate the most log
entries for a particular Publisher. Conversely, a Publisher level of 7 will generate the
fewest 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 with
TGW’s billing functionality, it may make sense to lower the Billing Publisher log level to
1 (Finest) to maximize the volume of billing information that gets logged. You could then
read 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 would
ensure 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
Copyright © Nokia Corporation 2001.
3. Under the top-level ag folder, click logger and then publisher. There are twelve
Publishers listed, each related to a subsystem in TGW. Click on any of the Publisher
subsystems 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 the
System 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 all
message filtering. The Logger directs messages generated by Publishers to the logging
queue, where they are sorted by the Listeners depending on whether an event has been
designated for a log file, CDR billing file, or an SNMP alarm. The Logger uses some
configuration parameters, which are detailed in the next section.
7.4.1 Logger Configuration Parameters
Folder Location: ag/logger
• debugLevel — This property sets the administrator
level for debugging the Logger. A setting of 0-3 allows
events to be written to the administrator console, while
4-7 turns off logging to the console. Essentially, if this
level is set to 4 or above, no events will be written to the
administrator console. The default level is 3 (on). This
value can be changed at run-time.
Do not change the
componentI D field
for any Publisher.
Managing Log Files
DN0182152 81
Issue 1-3 en Copyright © Nokia Corporation 2001.
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 mount
name where the TGW log files are stored. In
most cases this is the same as the base
directory name.
• baseFileName — This is the name of the log
file that TGW creates. This value can be
changed at run-time.
• rotationCounter — This determines the
total number of log files that gets created in
succession. Log files operate on a rotation
cycle; that is, when one file reaches its
maxFileSize limit (see below), event
information is written to a new file until that
reaches its limit, and so on. The
rotationCounter value determines the
number of new log files that get created
before the first one is overwritten with new
event information. If you specified a value of 1, then only one log file will be used and
will be overwritten when it reaches its maxFileSize limit. The default is 10, which
means that log data will be written across 10 separate log files before returning to
overwrite 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 value
can 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 the
changes.
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 the
information that is applicable to it, as explained below:
• The File Handler retrieves log records and writes them to the file specified in the
fileHandler parameter (tgwlog by default).
• The Billing Manager retrieves only billing information and generates CDRs for
the log records.
• The Trap Manager retrieves only alarm information and generates an alarm to the
SNMP console. These alarms can be retrieved by Network Management System
(NMS) applications.
82
Copyright © Nokia Corporation 2001.
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 the
com.nokia.ag.logger.listener.logger parameter. If you select the
“SNMP Alarm” check box for an event, its ID will appear in the requestTypes field
under 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 means
that a copy of the event information is kept in a separate file before entering the
logging queue. Turning this on ensures that event information is not lost in the event
of a system crash. 1=On; 0=Off. The default is 1. See “Safeguarding Against Event
Log Loss” for more information about log persistence.
• destinationID — Do not change the destinationI D! Changing this setting may
prevent logs, alarms, or CDRs from being generated. For example, if you change the
destinationID for the Billing Manager, CDRs may not be generated. Each Listener has
a unique destinationID that serves as an identifier. The Logger references the
destinationID 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 the
changes.
Figure 47 The Listener configuration parameters
Do not change the
destinationI D field
for any Listener.
Managing Log Files
DN0182152 83
Issue 1-3 en Copyright © Nokia Corporation 2001.
7.5.2 Safeguarding Against Event Log Loss
Normally, event information is constantly moving through the logging queue. In the event
of 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 the
queue. Essentially, Persistence is a means of temporarily backing up event data.
Each Listener contains a configuration parameter (persistentType) that allows you to
enable or disable persistent logging. By default, TGW turns on Persistence for all
Listeners.
7.6 Reading the Log Screen
Click the Log button in the left navigational frame to display the log file. A list of log files
appears in the Log screen, as shown in Figure 48. Remember that the number of log files
listed depends on the value of the rotationCounter parameter in the folder ag/logger/
fileHandler. This setting allows you to partition event information into separate log
files.
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 each
log file. The Download column provides links to the downloadable files.
Figure 48 List of log files in the Log screen
84
Copyright © Nokia Corporation 2001.
7.7 Displaying a log file
To display log files, click the link to the log file under the Log Files column that you want
to view.
The content for the log file appears in the Log File Display screen. See “How to Interpret
the 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
Issue 1-3 en Copyright © Nokia Corporation 2001.
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
Copyright © Nokia Corporation 2001.
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 single
message includes several comma-separated fields. Some of these fields are fixed, such as
the Event Description and Logger ID. Some fields are dynamically generated, such as the
actual message text. Also note that some fields can be null, while others must contain a
known value.
Some of the fields, such as Class Name, Method Name, and Logger ID, are useful mainly
for Nokia technical support staff. Some of the more important fields for normal use
include 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' for
queue: 'default',null,null,108,Thu Apr 04 11:24:17 EST
2002,UI_WEB_SUBSCRIBER_COMPOSE_MSG_EVENT,WEB SUBSCRIBER
COMPOSE 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 the
event log. This field cannot be null.
• Class Name and Method Name — The names of the Java class and method that
generates the event log. These fields can be null.
• Sequence Number — This field is the system-generated sequence number. This field
cannot 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 be
null.
Troubleshooting Tips
DN0182152 87
Issue 1-3 en Copyright © Nokia Corporation 2002.
8 Troubleshooting Tips
This chapter provides tips for system administrators responsible for maintaining TGW.
Intended audience. The intended audience for this chapter is system administrators
who use MMS Application Administrator.
Topics in this chapter are as follows:
• 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 reason
why message delivery can fail.
• For the originating application, you can set up one or more instances. Ensure that the
URL 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 URLs
correspond 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 with
the 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 are
representative of the prefixes in the following file: xkt_whitelist.cf
• Under Event Log, check if the status of events appears routine. (For example, review
EA errors and validation errors.) Ensure that the status of messages also appears
routine. (For example, waiting fetch.)
• To determine why messages are failing, look at logs from the MMSC by opening a
telnet session to the log directory.
• Review the log for the external application (the terminating application).
88
Copyright © Nokia Corporation 2002.
8.1.2 Additional information
For more information about MMSC, refer to the following related documentation.
8.2 Troubleshooting Apache
8.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 about
navigating the MMSC GUI and
background on basic tasks.
Message Handling DN00148708 Provides information about multimedia
message format, routing, and how
messages are handled in the MMSC.
Installing and
Integrating MMSC
DN00148798 Provides instructions for installing and
configuring the MMSC.
Operating MMSC DN00148786 Designed for users who need procedures
for daily, weekly, monthly, and occasional
operations.
Configuring MMSC DN00148774 Provides comprehensive instructions on
configuring the MMSC with a focus on
customizing the product.
External Application
Developer’s Guide
DN00148759 Provides guidelines for developing
interfaces for external applications.
Technical Manual DN00148747 Provides:
• environment variables
• processes
• configuration files
• database tables
Troubleshooting MMS
Center
DN0139402 Provides hints on how to handle
unexpected situations regarding MMSC
Table 14 Additional documentation
Troubleshooting Tips
DN0182152 89
Issue 1-3 en Copyright © Nokia Corporation 2002.
Spacing in the definition of the VirtualHost in the httpd.conf file is incorrect. In the
apache error logs /usr/local/apache/logs/error.log states that the message
could not be delivered (typically with a 404 error code).
The solution
In the following example, the VirtualHost definition in the htpd.conf file has spaces
missing before the first forward slash, and after the * in the first part of the definition. This
definition 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 addresses
and 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.
90
Copyright © Nokia Corporation 2002.
8.3 Troubleshooting Oracle
8.3.1 Blocked connections to the database
Problem
Client connections to the database are blocked.
Possible Cause
The database listener is down.
Solution
Check the status of the listener using the following command:
lsnrctl status
The output shows AGW in the Services summary. If the listener is down, No listener
and connection refused messages display.
To restart the listener as the user oracle, use the following command:
lsnrctl start
8.3.2 Information about Oracle errors
The first place to look for information about error conditions in Oracle is the Oracle
background process log file. This file is located in /u01/app/oracle/admin/AGW/
bdump and is called alert_AGW.log. This file shows error codes or the form ORA
1234. For more details than the error message provides, run that code number against the
error CLI utility called oerr. For example if you see an error message in the log of the
form ORA-1135, with some text following it, you can get more details using the following
command line:
oerr ORA 1135
01135, 00000, "file %s accessed for DML/query is offline"
// *Cause: Attempted to access a data file that is offline
// *Action: Bring the data file back online
This is a typical example in that there is a line describing the error message, followed by
possible causes of that error, followed by suggestions for an action to take, if any. The
action is sometimes missing and, as shown above, it tells an experienced database
administrator what to do, not how to do it. It assumes the database administrator knows
how to perform the action, or that the procedure can be easily looked up.
8.3.3 Backing up the database
It is important to back up your database to avoid loss of data. Also, when you restore a
backed up database, be sure to reset the sequencer number. Each subscriber gets a unique
number and if you re-create the database and then restore, that sequencer starts over. As a
result, creating subscribers fails because the number is already in use for another
subscriber (from the restore).
Troubleshooting Tips
DN0182152 91
Issue 1-3 en Copyright © Nokia Corporation 2002.
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
Copyright © Nokia Corporation 2002.
. 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
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 restore
data and critical systems in the event of system failure or user error. The backup strategy
you adopt will be based on a number of factors including how frequently data changes, the
level of risk you decide to accept for lost data, and the hardware and software available for
implementing a backup strategy.
Note: There are numerous books regarding backups and strategies available
involving many different combinations of hardware and software. The
information provided in this section provides general information about
developing 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 as
quickly as possible in the event of a major system failure.
The following sections describe general information, examples, and suggestions about
developing a backup strategy for user data and system files.
9.1 System Configuration Backups
Because 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 for
implementing 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 to
identical 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 down
time.
94
Copyright © Nokia Corporation 2002.
Note: There are commercial packages that mirror disks, but none of these have
been tested with AGW. Ask your Sun support representative about Sun's
disk suite to mirror the root disk partitions if you are interested in a true
mirror option.
9.1.1 User Data Backups
User data typically changes frequently, and needs to be backed up more regularly than
system files. At a minimum you should backup user data on a daily basis. The backups
involve 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 in
the 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 another
remote protocol.
• Any other file systems the systems administrator has configured for user use (for
example /export/home typically contains the user 's home directories and therefore
needs 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 as
rotating sets of tapes that are recycled over some period of time. For example, the backup
strategy you implement might include the following schedule:
• Eight sets of tapes rotated (overwritten) bi-monthly, with one full backup tape per
month 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 include
Uninterruptible Power Supplies (UPS). UPS provides backup power for a certain amount
Backup overview
DN0182152 95
Issue 1-3 en Copyright © Nokia Corporation 2002.
of time. The amount of time backup power is available depends on the unit's size. The
longer the battery life is, the higher the cost of the unit.
96
Copyright © Nokia Corporation 2002.
DN0182152 97
Issue 1-3 en Copyright © Nokia Corporation 2002.
Appendix A: Acronyms and terminology
The following table describes acronyms and other terminology related to TGW.
Acronym/Term Definition
Administrator Administrators use MMS Application
Administrator to administer the server that
is hosting multimedia messages.
Administration tasks include managing
TGW subscribers, managing Class of
Service 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 an
outside billing package. CDRs contain all
billing information needed for a billing
system to provide an invoice for a
subscriber.
The billing component for TGW
communicates billing information in a Call
Detail Record. The two methods for
transmitting this charging information are
as follows:
• Transmitting charging information to
the MMSC - generating CDRs for
multimedia messages received from the
MMSC
• Generating CDRs directly - generating
CDRs, regardless of the source or
destination of messages
Table 15 Appendix A: Acronyms and Terminology
98
Copyright © Nokia Corporation 2002.
COS
(Class of Service)
A Class of Service (COS) is a group of
features that may be configured for a group
of wireless phone users.
Values that define a TGW subscriber’s
Class of Service include maximum NA
size, maximum PA size, NA storage time,
PA storage time, and enabling/disabling
self-provisioning (which includes
changing 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 inactive
COS plan still exists in the database, you
cannot assign additional TGW subscribers
to 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 Subscriber
ISDN Number)
The mobile telephone number used by a
subscriber in a GSM/DCS network.
NA
(New Album)
This is the subscriber’s album where newly
arrived multimedia messages are stored.
Non TGW subscriber A phone owner not subscribing to TGW
services.
PA
(Personal Album)
This is the TGW subscriber’s main album
where multimedia messages are stored.
Acronym/Term Definition
Table 15 Appendix A: Acronyms and Terminology (Continued)
DN0182152 99
Issue 1-3 en Copyright © Nokia Corporation 2002.
SMSC
(Short Message Service
Center)
The Short Message Service is a store
and forward service, in other words,
short messages are not sent directly
from sender to recipient, but always via
an SMS Center instead.
Each mobile telephone network that
supports SMS has one or more
messaging centers to handle and
manage the short messages.
SNMP
(Simple Network
Management
Protocol)
SNMP is a communication protocol
that manages TCP/IP networks,
including individual network devices.
One feature of SNMP is an alarm
mechanism by which devices can notify
administrators of a problem (assuming
that the device is configured to SNMP.)
Subscriber Anyone who subscribes to mobile phone
service.
Supervisor Supervisors have access to the Subscribers
screen of MMS Application Administrator
for the purpose of managing TGW
subscribers.
Tasks that supervisors can complete are as
follows: searching for TGW subscribers,
assigning Class of Service plans, adding,
editing, and activating/deactivating TGW
subscribers.
TGW subscriber Mobile phone owner who subscribes to
TGW and has a Personal Album (PA).
An active TGW subscriber is currently
using the TGW service.
An inactive TGW subscriber is currently
not using the TGW service, but the
subscriber information still exists in the
database. An inactive TGW subscriber can
be reactivated at any time.
Acronym/Term Definition
Table 15 Appendix A: Acronyms and Terminology (Continued)
100
Copyright © Nokia Corporation 2002.
DN0182152 101
Issue 1-3 en Copyright © Nokia Corporation 2002.
Appendix B: Product descriptions for EGW and VGW
In addition to TGW, the Application Gateways product line at Nokia offers Nokia
Multimedia E-mail Gateway (EGW) and Nokia Multimedia Voice Gateway (VGW). If
you are interested in learning more about these related products, see the following product
descriptions or e-mail the Applications Gateways product line at
AG.productmanagement@nokia.com
Nokia Multimedia E-mail Gateway (EGW)
Nokia Multimedia E-mail Gateway (EGW) fulfills Nokia's promise to offer
GPRS/GSM operators value-added services for multimedia messaging.
By converting message formats, EGW allows multimedia terminals (MMTs) to
send 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 for
consumers and profitable for operators.
Nokia Multimedia Voice Gateway (VGW)
Nokia Multimedia Voice Gateway (VGW) is another part of the broader Nokia effort to
offer GPRS/GSM operators value-added services for multimedia messaging.
VGW combines the ease of use of a voice interface with the instant message delivery
capabilities of Short Message Service (SMS). VGW receives unanswered calls intended
for Multimedia Terminals (MMTs), plays a personal greeting, takes a message, and
forwards the message to the MMSC. The message is then forwarded from the MMSC to
the subscriber’s MMT, where the subscriber can listen to the message at their
convenience.
102
Copyright © Nokia Corporation 2002.
DN0182152 103
Issue 1-3 en Copyright © Nokia Corporation 2002.
Appendix C: Field descriptions for Create Subscriber
This appendix provides tables with the following descriptions for the Create Subscriber
screen:
• Field descriptions for Create Subscriber: Step 1 of 1 screen
• Descriptions of COS features listed on the Create Subscriber: Step 1 of 1 screen
Field descriptions for Create Subscriber: Step 1 of 1 screen
The following table provides descriptions and examples of the information required in
each of the fields located under the General tab on the Create Subscriber: Step 1 of 1
screen.
Field (* indicates
required field)
Description Example
User name* Enter the
subscriber’s user
name.
cpeterson
Status* Active or Inactive An active TGW subscriber is currently
using the TGW service.
An inactive TGW subscriber is currently
not using the TGW service, but the
subscriber information still exists in the
database.
Billing ID* Enter the id for
billing purposes.
This id comes from
your own billing
system.
45693REZ
Password* Enter a password for
the user.
The system encrypts the password you
type.
First name* Enter the
subscriber’s first
name.
Chuck
Last name* Enter the
subscriber’s last
name.
Peterson
Address Enter’s the
subscriber’s street
address.
34 Southey Street
Table 16 Field descriptions for the Create Subscriber screen
104
Copyright © Nokia Corporation 2002.
City Enter the
subscriber’s city.
Salem
State/Province Enter the
subscriber’s state or
province.
NH
Postal code Enter the
subscriber’s postal
code.
03890
Country Enter the
subscriber’s country.
US
E-mail address Enter the
subscriber’s e-mail
address.
cpeterson@genesis.com
MSISDN* Enter the Mobile
Subscriber ISDN
Number in
international
format.
+17815260823
Device e-mail* Enter the multimedia
terminal’s e-mail
address.
+17815260823@carrier.com
SMSC MSISDN* Enter the Mobile
Subscriber ISDN
Number of the
SMSC, in
international format,
to which the
subscriber is
assigned.
+16173882608
Field (* indicates
required field)
Description Example
Table 16 Field descriptions for the Create Subscriber screen (Continued)
DN0182152 105
Issue 1-3 en Copyright © Nokia Corporation 2002.
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 Create
Subscriber: Step 1 of 1 screen.

Class of Service* From the drop-down
list, select the Class
of Service plan to
assign to this
subscriber.
MMS Application
Administrator lists
TGW COS features
based on the COS
you select. COS
features are as
follows: Description,
Max NA Size, Max
PA Size, NA store
Time, 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 that
subscriber.
Use defaults.
Max NA size Lists the maximum size for the
subscriber’s New Album.
The New Albumis the subscriber’s
album where newly arrived
multimedia messages are stored.
4MB
Max PA size Lists the maximum size for the
subscriber’s Personal Album.
The Personal Albumis the TGW
subscriber’s main album where
multimedia messages are stored.
2MB
NA store time Lists how long the message will be
stored in the New Album (NA).
10 days
Table 17 Descriptions of COS features listed on the Create Subscriber screen
Field (* indicates
required field)
Description Example
Table 16 Field descriptions for the Create Subscriber screen (Continued)
106
Copyright © Nokia Corporation 2002.
PA store time Lists how long the message will be
stored in the Personal Album (PA).
100 days
Self provisioning Shows if the subscriber has the
ability to change e-mail address,
password, and address.
Enabled
Disabled
TGW COS Feature Description Example
Table 17 Descriptions of COS features listed on the Create Subscriber screen
DN0182152 107
Issue 1-3 en Copyright © Nokia Corporation 2002.
Appendix D: Description of available TGW events
The following table provides a list of all available TGW event numbers, the corresponding
event names, and a short description of the event.
Event
number
Event name Description
10000 STORE_MM_REQUEST Request the Multimedia
Manager request types: Store
multimedia message request.
10001 STORE_MM_REPLY Reply to the store multimedia
message request
10002 DELETE_MM_REQUEST Request to delete multimedia
message from the personal
album.
10003 DELETE_MM_REPLY Reply to the delete multimedia
message request
10004 BROWSE_MM_REQUEST Request to browse personal
album.
10005 BROWSE_MM_REPLY Reply to browse personal album
action.
10006 FORWARD_MM_REQUEST Request to forward multimedia
message.
10007 FORWARD_MM_REPLY Reply to forward multimedia
message.
10008 SEND_MM_REQUEST Request to send the multimedia
message.
10009 SEND_MM_REPLY Reply to send multimedia
message.
10010 RETRIEVE_MM_REQUEST Request to retrieve the
multimedia message.
10011 RETRIEVE_MM_REPLY Reply to retrieve multimedia
message.
10012 STORE_MM_REQUEST_PAB Request to store multimedia
message in a personal album.
10013 STORE_MM_REQUEST_NAB Request to store multimedia
message in a new album.
10014 STORE_MM_REQUEST_TAB Request to store multimedia
message in a Temp folder
Table 18 Description of available TGW events
108
Copyright © Nokia Corporation 2002.
10015 FORWARD_MM_REQUEST_FROM_WEBWAP_
TO_MMSC
Request to forward multimedia
message from (Web/WAP) to
MMSC
10016 FORWARD_MM_REQUEST_FROM_WEBWAP_
TO_EMAIL
Request to forward multimedia
message from (Web/WAP) to e-
mail address.
10017 RETRIEVE_MM_REQUEST_FROM_WAP_TO_M
MS
Request to retrieve the
multimedia message from WAP
to MMSC
10018 RETRIEVE_MM_REQUEST_FROM_WAP_TO_E
MAIL
Request to retrieve the
multimedia 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 to
MMSC.
10020 SEND_MM_REQUEST_FROM_WEB_TO_EMAIL Request to send a composed
multimedia message from Web
to e-mail address.
10200 SEND_EMAIL_REQUEST Request to send e-mail message
request.
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_FAIL
ED_CRITICAL
Critical error; unable to create
the billing/logger listener.
10403 BILLING_MANAGER_CREATE_FAILED_CRITI
CAL
Critical error; unable to create
billing manager.
10404 BILLING_MD_BEAN_CREATE_FAILED_CRITI
CAL
Critical error; unable to create a
billing java bean.
10405 BILLING_XML_PROCESSOR_BEAN_CREATE_
FAILED_CRITICAL
Critical error; unable to process
an XML billing java bean.
Event
number
Event name Description
Table 18 Description of available TGW events
DN0182152 109
Issue 1-3 en Copyright © Nokia Corporation 2002.
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: MMSC
Terminating Async Receiver-
Originated App.
10701 Forward Msg MMSC Message Received by
Servlet.
10702 Retrieve Msg MMSC Message Received by
TGW application.
10703 Compose Msg MMSC Message Queued by
interface application.
10704 Change Email MMSC Message Received by
interface application.
10705 View Folder MMSC Message Rejected by
Servlet.
10706 View Menu MMSC Message Rejected by
TGW application.
10707 Delete Msg MMSC Message Rejected by
interface application.
10708 Move Msg MMSC Message successfully
processed by Servlet.
10709 Rename Msg MMSC Message successfully
processed by TGW application.
Event
number
Event name Description
Table 18 Description of available TGW events
110
Copyright © Nokia Corporation 2002.
10710 Send Msg MMSC Terminating Async
Receiver-Originated App Reply.
10711 View Msg
10712 Change Password MMSC Message Reply
Received by TGW application.
10713 TMAR_REPLY_QUEUED_TGW MMSC message reply queued
by TGW application.
10714 TMAR_REPLY_RECEIVED_INTERFACE MMSC Message Reply
Received by interface
application.
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 Reply
successfully processed by
interface application.
10720 TERMINATING_MM_SYNC_RECEIVER MMSC Terminating Sync
Receiver-Originated App.
10721 TMSR_MESSAGE_RECEIVED_SERVLET MMSC message received by
servlet.
10722 TMSR_MESSAGE_RECEIVED_TGW MMSC message received by
TGW application.
10723 TMSR_MESSAGE_QUEUED_INTERFACE MMSC Message Queued by
interface application.
10724 TMSR_MESSAGE_RECEIVED_INTERFACE MMSC Message Received by
interface application.
10725 TMSR_MESSAGE_REJECTED_SERVLET MMSC message rejected by
Servlet.
10726 TMSR_MESSAGE_REJECTED_TGW MMSC message rejected by
TGW application.
10727 TMSR_MESSAGE_REJECTED_INTERFACE MMSC Message Rejected by
interface application.
10728 TMSR_MESSAGE_PROCESSED_SERVLET MMSC message successfully
processed by servlet.
Event
number
Event name Description
Table 18 Description of available TGW events
DN0182152 111
Issue 1-3 en Copyright © Nokia Corporation 2002.
10729 TMSR_MESSAGE_PROCESSED_TGW MMSC message successfully
processed by TGW application.
10730 TERMINATING_MM_ASYNC_SENDER MMSC Terminating Async
Sender-Originated App.
10740 TERMINATING_MM_ASYNC_SENDER_REPLY MMSC Terminating Async
Sender-Originated App Reply.
10750 TERMINATING_MM_SYNC_SENDER MMSC Terminating Sync
Sender-Originated App.
10760 TERMINATING_MM_ASYNC_DELIVERY_FAIL
URE
MMSC Terminating Async
Delivery Failure-Originated
App.
10761 TMAD_MESSAGE_RECEIVED_SERVLET MMSC message received by
servlet.
10762 TMAD_MESSAGE_RECEIVED_TGW MMSC message received by
TGW application.
10763 TMAD_MESSAGE_QUEUED_INTERFACE MMSC Message Queued by
interface application.
10764 TMAD_MESSAGE_RECEIVED_INTERFACE MMSC Message Received by
interface application.
10765 TMAD_MESSAGE_REJECTED_SERVLET MMSC message rejected by
servlet.
10766 TMAD_MESSAGE_REJECTED_TGW MMSC message rejected by
TGW application.
10767 TMAD_MESSAGE_REJECTED_INTERFACE MMSC message rejected by
interface 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_FAIL
URE_REPLY
MMSC Terminating Async
Delivery Failure-Originated
App Reply.
10772 TMAD_REPLY_RECEIVED_TGW MMSC Message Reply
Received by TGW application.
10773 TMAD_REPLY_QUEUED_TGW MMSC message reply Queued
by TGW application.
Event
number
Event name Description
Table 18 Description of available TGW events
112
Copyright © Nokia Corporation 2002.
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 Reply
successfully processed by
interface application.
10780 TERMINATING_MM_SYNC_DELIVERY_FAILU
RE
MMSC Terminating Sync
Delivery Failure-Originated
App.
10781 TMSD_MESSAGE_RECEIVED_SERVLET MMSC message received by
servlet.
10782 TMSD_MESSAGE_RECEIVED_TGW MMSC Message received by
TGW application.
10783 TMSD_MESSAGE_QUEUED_INTERFACE MMSC message queued by
interface application.
10784 TMSD_MESSAGE_RECEIVED_INTERFACE MMSC Message Received by
interface application.
10785 TMSD_MESSAGE_REJECTED_SERVLET MMSC message rejected by
servlet.
10786 TMSD_MESSAGE_REJECTED_TGW MMSC message rejected by
TGW application.
10787 TMSD_MESSAGE_REJECTED_INTERFACE MMSC Message Rejected by
interface 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 by
TGW application.
10792 O_MESSAGE_QUEUED_TGW MMSC message queued by
TGW application.
Event
number
Event name Description
Table 18 Description of available TGW events
DN0182152 113
Issue 1-3 en Copyright © Nokia Corporation 2002.
10793 O_MESSAGE_RECEIVED_INTERFACE MMSC Message Received by
interface application.
10794 O_MESSAGE_REJECTED_TGW MMSC message rejected by
TGW application.
10795 O_MESSAGE_REJECTED_INTERFACE MMSC Message Rejected by
interface application.
10796 O_MESSAGE_PROCESSED_INTERFACE MMSC Message successfully
processed by interface
application.
10797 O_ASYNC_REPLY_PROCESSED_INTERFACE MMSC Async Reply
successfully processed by
interface 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_SERVL
ET
MMSC terminating message
received 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_EX
CEEDED
Message delivery failed because
license exceeded.
11706 MMSC_LICENSING_MESSAGE_STORES_EXCE
EDED
No more messages can be stored
with the license.
11707 MMSC_LICENSING_OUTGOING_MESSAGES_E
XCEEDED
No more outgoing messages can
be sent; license exceeded.
Event
number
Event name Description
Table 18 Description of available TGW events
114
Copyright © Nokia Corporation 2002.
11708 MMSC_LICENSING_TOTAL_MESSAGES_EXCE
EDED
MMSC Licensing Manager -
Total Messages.
11728 TMSR_MESSAGE_FILTERED_SERVLET MMSC Message successfully
filtered by TMSR Servlet.
11729 TMSD_MESSAGE_FILTERED_SERVLET MMSC Message successfully
filtered by TMSD Servlet.
11780 TMSD_SERVLET_INIT_FAILED_CRITICAL MMSC TMSD Servlet
initialization failed.
11781 TMAD_SERVLET_INIT_FAILED_CRITICAL MMSC TMAD Servlet
initialization failed.
11782 MMSC_RECEIVER_CREATE_FAILED_CRITICA
L
MMSC Receiver initialization
failed.
11783 MMSC_SENDER_CREATE_FAILED_CRITICAL MMSC Sender initialization
failed.
11784 MMSC_CONNECTION_FAILED_CRITICAL MMSC Connection
initialization failed.
11785 TMSR_SERVLET_INIT_FAILED_CRITICAL MMSC TMSR Servlet
initialization failed.
11786 TMAR_SERVLET_INIT_FAILED_CRITICAL MMSC TMAR Servlet
initialization failed.
11787 MMSC_CONFIG_CHANGE_EVENT Configuration change made.
11788 MMSC_RECEIVER_EVENT Generic operation type for
MMSC Receiver events.
11789 MMSC_SENDER_EVENT Generic operation type for
MMSC 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 the
subsystem
12006 SHUTDOWN_COMPLETE Shutdown of the subsystem done
Event
number
Event name Description
Table 18 Description of available TGW events
DN0182152 115
Issue 1-3 en Copyright © Nokia Corporation 2002.
13001 Successful message store to personal album This event is generated after the
message is successfully stored in
the PA.
13002 Successful message store to new album This event is generated after the
message is successfully stored in
the NA.
13003 Successful store of temporary message This event is generated after the
message is successfully stored in
the temporary album.
13004 Failed message store to personal album This event is generated after the
message is unsuccessfully stored
in the PA.
13005 Failed message store to new album This event is generated after the
message is unsuccessfully stored
in the NA.
13006 Failed store of temporary message This event is generated after the
message is unsuccessfully stored
in the temporary folder album.
13011 Successful user mailbox creation This event is generated when the
user albums are successfully
provisioned
13012 Failed to create user mailbox This event is generated when the
user albums failed to be
provisioned.
13013 Successful user mailbox removal This event is generated when a
user album is successfully
removed.
13014 Failed to remove user mailbox This event is generated when a
user albums failed to be removed
14001 WEB_SUBSCRIBER_LOGIN This event is generated after the
subscriber has been successfully
validated from the Web.
14002 WEB_SUBCSRIBER_LOGOUT This event is generated after the
subscriber on the Web has been
successfully logged out.
14003 WEB_SUBCSRIBER_VIEW_MSG This event is generated when the
Web subscriber wants to retrieve
a message from the PA or NA.
Event
number
Event name Description
Table 18 Description of available TGW events
116
Copyright © Nokia Corporation 2002.
14004 WEB_SUBSCRIBER_MOVE_MSG The Message Store generates
this event after the message has
been successfully moved from
the NA to the PA on the Web.
14005 WEB_SUBSCRIBER_RENAME_MSG The Message Store generates
this event after the message has
been successfully renamed on
the Web.
14006 WEB_SUBSCRIBER_FOWARD_MSG The MMSC Sender generates
this event after the message has
been successfully sent to the
MMSC. The SMTP component
generates this event after the
message has been successfully
sent to the SMTP server.
14007 WEB_SUBSCRIBER_COMPOSE_MSG The MMSC Sender generates
this event after the message has
been successfully sent to the
MMSC on the Web.
14008 WEB_SUBSCRIBER_DELETE_PA_MSG The Message Store generates
this event after a message is
successfully deleted from the PA
on the Web.
14009 WEB_SUBSCRIBER_DELETE_NA_MSG The Message Store generates
this event after a message is
successfully deleted from the
NA on the Web.
14010 WEB_VIEW_TMP_MSG The UI Servlet generates this
event after a message is
successfully returned to the non-
subscriber on the Web.
14011 WEB_BROWSE_PA_MSG The UI Servlet generates this
event after a user browses their
PA via the Web interface
14012 WEB_BROWSE_NA_MSG The UI Servlet generates this
event after a user browses their
NA via the Web interface
Event
number
Event name Description
Table 18 Description of available TGW events
DN0182152 117
Issue 1-3 en Copyright © Nokia Corporation 2002.
14101 WAP_SUBSCRIBER_LOGIN This event is generated after the
subscriber has been successfully
validated from the WAP
interface.
14102 WAP_SUBSCRIBER_LOGOUT This event is generated after the
subscriber has been successfully
logged out.
14103 WAP_SUBSCRIBER_VIEW_MSG This event is generated when the
user retrieves a message via the
Wap menu.
14104 WAP_SUBSCRIBER_MOVE_MSG The Message Store generates
this event after the message has
been successfully moved from
the NA to the PA via WAP.
14105 WAP_SUBSCRIBER_RENAME_MSG The Message Store generates
this event after the message has
been successfully renamed via
the WAP.
14106 WAP_SUBSCRIBER_FORWARD_MSG The MMSC Sender generates
this event after the message has
been successfully sent to the
MMSC from the WAP. The
SMTP component generates this
event after the message has been
successfully sent to the SMTP
server via WAP.
14107 WAP_SUBSCRIBER_DELETE_PA_MSG The Message Store generates
this event after a message is
successfully deleted from the PA
via WAP.
14108 WAP_SUBSCRIBER_DELETE_NA_MSG The Message Store generates
this event after a message is
successfully deleted from the
NA via WAP.
14109 WAP_BROWSE_PA_MSG This event is generated after a
user browses their PA via the
WAP interface
14110 WAP_BROWSE_NA_MSG The Wap Servlet generates this
event after a user browses their
NA via the WAP interface
Event
number
Event name Description
Table 18 Description of available TGW events
118
Copyright © Nokia Corporation 2002.
15001 LIC_EXCEED_SUB_COUNT This event is generated by the
Message Store when an attempt
is made to create a subscriber
after the license has been used
up.
15002 LIC_EXCEED_EAIF_TPS This event is generated when the
number of transactions per
second has exceeded the license
threshold.
15003 LIC_CURRENT_EAIF_TPS This event is generated each
time the MMSC logs
transactions per second over the
limit.
15101 SUBSCRIBER_CREATED This event is generated after a
subscriber has been successfully
created .
15102 SUBSCRIBER_UPDATED This event is generated after the
subscriber has been successfully
modified.
15103 SUBSCRIBER_DEACTIVATED This event is generated after the
subscriber has been successfully
deactivated.
15104 SUBSCRIBER_ACTIVATED This event is generated after the
subscriber has been successfully
activated.
Event
number
Event name Description
Table 18 Description of available TGW events
DN0182152 119
Issue 1-3 en Copyright © Nokia Corporation 2002.
Appendix E: Configuration Parameters
The following tables list configuration parameters and properties displayed in the MMS
Application 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
password
msis.MailStoreProvisioner.CP Domain:
Critical Path users domain
msis.MailStoreProvisioner.CP SMTPdAdminPort:
CP SMTPd management port number
msis.MailStoreProvisioner.CP SMTPdAdminPassword:
CP SMTPd managemement port write
access password
msis.MailStore COSCheckInterval:
Number of seconds between fetches of
subscriber 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 considered
undeliverable
Table 19 Properties set during installation
120
Copyright © Nokia Corporation 2002.
sms MessageQRead:
The max. number of SMS messages that
will be processed when the timer kicks in
snmp portNum:
Specifies the port on the management
station which listens for traps
snmp serverName:
Specifies the address or hostname of the
management station
tgw.smtp portNum:
Specifies the SMTP port number on the
Mail 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 of
the SMTP server
multimediamanager.reflect.async.SMS.CT
OR_NAME.CTOR_ARG
CTOR_ARG0:
Address for the NACS Server for outbound SMS in
sync mode
ui basemsgretrievalURL:
base url
ui usertempdir:
temp directory for unwrapping messages
mmsc.sender maximumMessageContentLength:
Maximum message content length for
outgoing messages (in bytes)
mmsc.sender asyncTerminatingMmscUrls:
Comma-separated list of MMSC URLs to
use for Async Terminating Messages
mmsc.sender
mmscUrls:
Comma-separated list of MMSC URLs to
use for outgoing messages
mmsc.sender
asyncDeliveryFailureMmscUrls:
Comma-separated list of MMSC URLs to
use for Async Delivery Failures
Parameter Property
Table 19 Properties set during installation
DN0182152 121
Issue 1-3 en Copyright © Nokia Corporation 2002.
Parameter Property
msis
debugMode: Turns the message store
component activity tracing on or off
msis
tracingLevel: Defines the message store
degree of tracing detail
msis.TempStore
Size: Defines the per folder size high water
mark for temporary message folders
msis.MailStore
COSCheckInterval: Defines the number of
seconds 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 level
of the TrapManager component
snmp
trapClearInterval: Specifies the time interval
(in milliseconds) that should elapse before
stopping the monitoring of a specific trap
snmp
monInterval: Specifies the time interval (in
milliseconds) which monitors if
trapClearInterval has passed.
snmp
i18Nflag: Specifies whether to
internationalize the message sent to the
management station
tgw.smtp
debugLevel: Specifies the current
debugLevel of the EmailClient component
tgw.smtp
serverName: Specifies either the address or
hostname of the SMTP server
licenseManager
perfDataMode: A boolean value used to
indicate performance data collection (not
supported R1)
Table 20 Properties that should not be changed
122
Copyright © Nokia Corporation 2002.
licenseManager
messageDeliveryFailureThreshold: A licensing
threshold for message delivery failures
(specified in messages / second)
licenseManager
messageStoreRequests: Updated actual rate for
message store requests (specified in
messages / second)
licenseManager
calculationInterval: The calculation interval (in
seconds) for license checking
licenseManager
totalMessagesThreshold: The licensing
threshold for total messages sent and
received (in messages / second)
licenseManager
outgoingMessages: The actual rate for
outgoing messages (specified in messages /
second)
licenseManager
messageStoreRequestsThreshold: Licensing
threshold for message store requests (in
messages / second)
licenseManager
rejectRequestIfExceeded: Boolean value to
indicate that that requests should be
rejected if any of the licensing thresholds
are exceeded
licenseManager
outgoingMessagesThreshold: Licensing
threshold for outgoing messages (specified
in messages / second)
licenseManager
tracingLevel: Tracing level for all License
Manager events (0-OFF, 3-ALL)
licenseManager
totalMessages: Updated actual rate of
incoming and outgoing messages (in
messages / second)
Parameter Property
Table 20 Properties that should not be changed
DN0182152 123
Issue 1-3 en Copyright © Nokia Corporation 2002.
licenseManager
messageDeliveryFailures: Updated actual rate
for message delivery failures (specified in
messages / second)
licenseManager
debugMode: The debugmode for the License
Manager
multimediamanager.reflect.async.SMS
EJB_NAME: JNDI Name
multimediamanager.reflect.async.SMS
PACKAGE_NAME: Package Name
multimediamanager.reflect.async.SMS.REQ
UEST_TYPES.0
METHOD_N_ARGS: Nb of Method Arg
multimediamanager.reflect.async.SMS.REQ
UEST_TYPES.0
REQUEST_TYPE: Request Type
multimediamanager.reflect.async.SMS.REQ
UEST_TYPES.0
METHOD_NAME: Method Name to Call
multimediamanager.reflect.async.SMS.REQ
UEST_TYPES.0.METHOD_TYPE
METHOD_TYPE3: Arg Type 3
multimediamanager.reflect.async.SMS.REQ
UEST_TYPES.0.METHOD_TYPE
METHOD_TYPE2: Arg Type 2
multimediamanager.reflect.async.SMS.REQ
UEST_TYPES.0.METHOD_TYPE
METHOD_TYPE1: Arg Type 1
multimediamanager.reflect.async.SMS.REQ
UEST_TYPES.0.METHOD_TYPE
METHOD_TYPE0: Arg Type 0
multimediamanager.reflect.async.SMS.CTO
R_NAME
CTOR_NAME: Name Of Constructor
multimediamanager.reflect.async.SMS.CTO
R_NAME
CTOR_N_ARGS: Nb Of Constructor Arg
multimediamanager.reflect.async.SMS.CTO
R_NAME.CTOR_TYPE
CTOR_TYPE1: Arg Type 1
multimediamanager.reflect.async.SMS.CTO
R_NAME.CTOR_TYPE
CTOR_TYPE0: Arg Type 0
multimediamanager.reflect.async.SMS.CTO
R_NAME.CTOR_ARG
CTOR_ARG1: Arg Value 1
multimediamanager.reflect.async.MESSAG
E_STORE
EJB_NAME: JNDI Name
multimediamanager.reflect.async.MESSAG
E_STORE
PACKAGE_NAME: Package Name
Parameter Property
Table 20 Properties that should not be changed
124
Copyright © Nokia Corporation 2002.
multimediamanager.reflect.async.MESSAG
E_STORE.REQUEST_TYPES.2
METHOD_N_ARGS: Nb Of Method Arg
multimediamanager.reflect.async.MESSAG
E_STORE.REQUEST_TYPES.2
REQUEST_TYPE: Request Type
multimediamanager.reflect.async.MESSAG
E_STORE.REQUEST_TYPES.2
METHOD_NAME: Method Name to Call
multimediamanager.reflect.async.MESSAG
E_STORE.CTOR_NAME
CTOR_NAME: Name Of Constructor
multimediamanager.reflect.async.MESSAG
E_STORE.CTOR_NAME
CTOR_N_ARGS: Nb Of Constructor Arg
multimediamanager.reflect.async.EMAIL_
CLIENT
EJB_NAME: JNDI Name
multimediamanager.reflect.async.EMAIL_
CLIENT
PACKAGE_NAME: Package Name
multimediamanager.reflect.async.DATABA
SE
EJB_NAME: JNDI Name
multimediamanager.reflect.async.DATABA
SE
PACKAGE_NAME: Package Name
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.REQ
UEST_TYPES.0
METHOD_N_ARGS: Nb of Method Arg
multimediamanager.reflect.sync.SMS.REQ
UEST_TYPES.0
REQUEST_TYPE: Request Type
multimediamanager.reflect.sync.SMS.REQ
UEST_TYPES.0
METHOD_NAME: Method Name to Call
multimediamanager.reflect.sync.SMS.REQ
UEST_TYPES.0.METHOD_TYPE
METHOD_TYPE3: Arg Type 3
multimediamanager.reflect.sync.SMS.REQ
UEST_TYPES.0.METHOD_TYPE
METHOD_TYPE2: Arg Type 2
multimediamanager.reflect.sync.SMS.REQ
UEST_TYPES.0.METHOD_TYPE
METHOD_TYPE1: Arg Type 1
Parameter Property
Table 20 Properties that should not be changed
DN0182152 125
Issue 1-3 en Copyright © Nokia Corporation 2002.
multimediamanager.reflect.sync.SMS.REQ
UEST_TYPES.0.METHOD_TYPE
METHOD_TYPE0: Arg Type 0
multimediamanager.reflect.sync.SMS.CTO
R_NAME
CTOR_NAME: Name Of Constructor
multimediamanager.reflect.sync.SMS.CTO
R_NAME
CTOR_N_ARGS: Nb Of Constructor Arg
multimediamanager.reflect.sync.SMS.CTO
R_NAME.CTOR_TYPE
CTOR_TYPE1: Arg Type 1
multimediamanager.reflect.sync.SMS.CTO
R_NAME.CTOR_TYPE
CTOR_TYPE0: Arg Type 0
multimediamanager.reflect.sync.SMS.CTO
R_NAME.CTOR_ARG
CTOR_ARG1: Arg Value 1
multimediamanager.reflect.sync.MESSAGE
_STORE
EJB_NAME: JNDI Name
multimediamanager.reflect.sync.MESSAGE
_STORE
PACKAGE_NAME: Package Name
multimediamanager.reflect.sync.MESSAGE
_STORE.REQUEST_TYPES.2
METHOD_N_ARGS: Nb Of Method Arg
multimediamanager.reflect.sync.MESSAGE
_STORE.REQUEST_TYPES.2
REQUEST_TYPE: Request Type
multimediamanager.reflect.sync.MESSAGE
_STORE.REQUEST_TYPES.2
METHOD_NAME: Method Name to Call
multimediamanager.reflect.sync.MESSAGE
_STORE.CTOR_NAME
CTOR_NAME: Name Of Constructor
multimediamanager.reflect.sync.MESSAGE
_STORE.CTOR_NAME
CTOR_N_ARGS: Nb Of Constructor Arg
multimediamanager.reflect.sync.EMAIL_C
LIENT
EJB_NAME: JNDI Name
multimediamanager.reflect.sync.EMAIL_C
LIENT
PACKAGE_NAME: Package Name
multimediamanager.reflect.sync.DATABA
SE
EJB_NAME: JNDI Name
multimediamanager.reflect.sync.DATABA
SE
PACKAGE_NAME: Package Name
multimediamanager.reflect.sync.MMSC
EJB_NAME: JNDI Name
multimediamanager.reflect.sync.MMSC
PACKAGE_NAME: Package Name
Parameter Property
Table 20 Properties that should not be changed
126
Copyright © Nokia Corporation 2002.
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 retry
topic
common
RetryInterval: The interval at which the SMS
delivery retry timer will kick in
common
TGWConnFactory: Common JMS connection
factory for TGW components.
common
configTopic: The JNDI name of the Config
Manager topic
common
RetryQueue: The JNDI name of the SMS
retry queue
perf perfInterval:
logger
debugLevel: Debug Level
logger.tool
BillingListenerDN: Dname of the Billing
Listener Application
logger.tool
LogListenerDN: Dname of the Log(File)
Listener Application
Parameter Property
Table 20 Properties that should not be changed
DN0182152 127
Issue 1-3 en Copyright © Nokia Corporation 2002.
logger.tool
TrapListenerDN: Dname of the Trap Listener
Application
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_MANA
GER
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
Table 20 Properties that should not be changed
128
Copyright © Nokia Corporation 2002.
logger.publisher.SMS_SUBSYSTEM
logLevel: Log Level
logger.publisher.SMS_SUBSYSTEM
componentID: Component ID
logger.publisher.SMTP_SUBSYSTEM
logLevel: Log Level
logger.publisher.SMTP_SUBSYSTEM
componentID: Component ID
logger.publisher.LOGGER
logLevel: Log Level
logger.publisher.LOGGER
componentID: Component ID
logger.listener.logger
requestTypes: Request Types which will be
logged to the Log File
logger.listener.logger
logLevel: Log Level for the Log File Handler
logger.listener.logger
persistentType: Persistent Type for the Log
File Handler
logger.listener.logger
destinationID: Destination ID of the Log File
Handler
logger.listener.billing
requestTypes: Request Types for which CDR
has to be generated
logger.listener.billing
logLevel: Log Level of the Billing Listener
logger.listener.billing
persistentType: Persistent Type for the Billing
Listener
logger.listener.billing
destinationID: Destination ID of the Billing
Listener
logger.listener.trapManager
requestTypes: Request Types for which the
Trap will be generated
logger.listener.trapManager
logLevel: Log Level of the Trap Listener
Application
Parameter Property
Table 20 Properties that should not be changed
DN0182152 129
Issue 1-3 en Copyright © Nokia Corporation 2002.
logger.listener.trapManager
persistentType: Persistent Type for the Trap
Listener Application
logger.listener.trapManager
destinationID: Destination ID of the Trap
Listener Application
logger.fileHandler.tgw
mountName: Mount Name
logger.fileHandler.tgw
baseFileName: Initial File Name for the Log
File
logger.fileHandler.tgw
rotationCounter: Rotation Counter
logger.fileHandler.tgw
baseDirName: Base Directory Name for
storing the Logs
logger.fileHandler.tgw
maxFileSize: Maximum size of a file after
which the rotation is done
mmsc.sender
perfDataMode: Boolean value which indicates
whether performance data collection is
being performed (not supported R1)
mmsc.sender
mmReceivedTracingLevel: Tracing level for
received events in MMSC Sender (0- OFF,
1 - MMSC ONLY, 2 - BILLING ONLY, 3 -
ALL)
mmsc.sender
mmRejectedTracingLevel: Tracing level for
rejected 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 sending
subscriber for outgoing messages is
performed
Parameter Property
Table 20 Properties that should not be changed
130
Copyright © Nokia Corporation 2002.
mmsc.sender
destinationAddressesRequired: Boolean value
which indicates whether destination
address(es) are required for outgoing
messages
mmsc.sender
performLicenseChecking: Boolean value which
indicates whether license checking and
updating for outgoing messages is
performed
mmsc.sender
mmSentTracingLevel: Tracing level for
successfully sent events in MMSC Sender
(0- OFF, 1 - MMSC ONLY, 2 - BILLING
ONLY, 3 - ALL)
mmsc.sender
tracingLevel: Tracing level for the MMSC
Sender (0- OFF, 1 - MMSC ONLY, 2 -
BILLING ONLY, 3 - ALL)
mmsc.sender
debugMode: Debugmode for MMSC
receiver components
mmsc.receiver.roareceiver
mmProcessedTracingLevel: Tracing level for
successfully processed events in MMSC
Receiver (0- OFF, 1 - MMSC ONLY, 2 -
BILLING ONLY, 3 - ALL)
mmsc.receiver.roareceiver
continueWithoutRosSubscriber: Boolean value
to indicate if Sync Receiver-Originated
request should be rejected if the subscriber
is not found
mmsc.receiver.roareceiver
screenRoaReceivingSubscriber: Boolean value
to indicate whether to screen the receiving
subscriber for Async Receiver-Originated
Messages
mmsc.receiver.roareceiver
continueWithoutDfaSubscriber: Boolean value
to indicate if Async Delivery-Failure
request should be rejected if the subscriber
is not found
Parameter Property
Table 20 Properties that should not be changed
DN0182152 131
Issue 1-3 en Copyright © Nokia Corporation 2002.
mmsc.receiver.roareceiver
screenDfaReceivingSubscriber: Boolean value
to indicate whether to screen the receiving
subscriber for Async Delivery Failures
mmsc.receiver.roareceiver
continueWithoutRoaSubscriber: Boolean value
to indicate if Async Receiver-Originated
request should be rejected if the subscriber
is not found
mmsc.receiver.roareceiver
screenDfsSendingSubscriber: Boolean value to
indicate whether to screen the sending
subscriber for Sync Delivery Failures
mmsc.receiver.roareceiver
mmReceivedTracingLevel: Tracing level for
received events in MMSC Receiver (0-
OFF, 1 - MMSC ONLY, 2 - BILLING
ONLY, 3 - ALL)
mmsc.receiver.roareceiver
debugMode: Debugmode for MMSC
Receiver components
mmsc.receiver.roareceiver
perfDataMode: Boolean value to indicate
whether performance data is collected (not
supported R1)
mmsc.receiver.roareceiver
screenDfaSendingSubscriber: Boolean value to
indicate whether to screen the sending
subscriber for Async Delivery Failures
mmsc.receiver.roareceiver
performLicenseChecking: Boolean value to
indicate license checking and collection
mmsc.receiver.roareceiver
screenRoaSendingSubscriber: Boolean value to
indicate whether to screen the sending
subscriber for Async Receiver-Originated
Messages
mmsc.receiver.roareceiver
continueWithoutDfsSubscriber: Boolean value
to indicate if Sync Delivery-Failure request
should be rejected if the subscriber is not
found
Parameter Property
Table 20 Properties that should not be changed
132
Copyright © Nokia Corporation 2002.
mmsc.receiver.roareceiver
screenRosReceivingSubscriber: Boolean value
which 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 for
rejected events in MMSC Receiver (0-
OFF, 1 - MMSC ONLY, 2 - BILLING
ONLY, 3 - ALL)
mmsc.receiver.roareceiver
screenDfsReceivingSubscriber: Boolean value
to indicate whether to screen the receiving
subscriber for Sync Delivery Failures
mmsc.receiver.roareceiver
screenRosSendingSubscriber: Boolean value
which indicates whether or not to screen the
sending subscriber for Sync Receiver-
Originated Messages
mmsc.servlet.roaservlet
mmReceivedTracingLevel: Tracing Level
should be set if processed event is to be
logged.
mmsc.servlet.roaservlet
mmProcessedTracingLevel: Tracing Level
should be set if processed event is to be
logged
mmsc.servlet.roaservlet
perfDataMode: Peformance data collecting is
performed with this set (not supported R1)
mmsc.servlet.roaservlet
mmRejectedTracingLevel: Tracing Level
should be set if processed event is to be
logged.
mmsc.servlet.roaservlet
performLicenseChecking: License checking is
performed with this set
Parameter Property
Table 20 Properties that should not be changed
DN0182152 133
Issue 1-3 en Copyright © Nokia Corporation 2002.
mmsc.servlet.roaservlet
maximumMessageContentLength: Maximum
allowed incoming message content length
(in bytes)
mmsc.servlet.roaservlet
debugMode: Debug mode for servlet
mmsc.servlet.roaservlet
tracingLevel: Overall Tracing Level - set to
the appropriate level
mmsc.servlet.dfsservlet
mmReceivedTracingLevel: Tracing Level
should be set if processed event is to be
logged.
mmsc.servlet.dfsservlet
mmProcessedTracingLevel: Tracing Level
should be set if processed event is to be
logged.
mmsc.servlet.dfsservlet
perfDataMode: Peformance data collecting is
performed with this set (not supported R1)
mmsc.servlet.dfsservlet
mmRejectedTracingLevel: Tracing Level
should be set if processed event is to be
logged.
mmsc.servlet.dfsservlet
performLicenseChecking: License checking is
performed with this set
mmsc.servlet.dfsservlet
maximumMessageContentLength: Maximum
allowed 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 Level
should be set if processed event is to be
logged.
Parameter Property
Table 20 Properties that should not be changed
134
Copyright © Nokia Corporation 2002.
mmsc.servlet.rosservlet
mmProcessedTracingLevel: Tracing Level
should 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 Level
should be set if processed event is to be
logged.
mmsc.servlet.rosservlet
performLicenseChecking: License checking is
performed with this set
mmsc.servlet.rosservlet
maximumMessageContentLength: Maximum
allowed incoming message content length
(in bytes)
mmsc.servlet.rosservlet
debugMode: Debug mode for servlet
mmsc.servlet.rosservlet
tracingLevel: Overall Tracing Level - set to
the appropriate level
mmsc.servlet.dfaservlet
mmReceivedTracingLevel: Tracing Level
should be set if received event is to be
logged.
mmsc.servlet.dfaservlet
mmProcessedTracingLevel: Tracing level for
successfully processed events in Delivery-
Failure Async Servlet (0- OFF, 1 - MMSC
ONLY, 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 Level
should be set if received event is to be
logged.
mmsc.servlet.dfaservlet
performLicenseChecking: License checking is
performed with this set
Parameter Property
Table 20 Properties that should not be changed
DN0182152 135
Issue 1-3 en Copyright © Nokia Corporation 2002.
mmsc.servlet.dfaservlet
maximumMessageContentLength: The
maximum message content length (in
bytes) for Delivery-Failure Async
messages
mmsc.servlet.dfaservlet
debugMode: The debugmode for the
Delivery-Failure Async Servlet
mmsc.servlet.dfaservlet
tracingLevel: Overall Tracing Level - set to
the appropriate level
Parameter Property
Table 20 Properties that should not be changed
136
Copyright © Nokia Corporation 2002.
DN0182152 137
Issue 1-3 en Copyright © Nokia Corporation 2002.
Symbols
(CDR) Call Detail Record 97
(COS) Class of Service 97
(EGW) Nokia Multimedia E-mail
Gateway 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 35
Admin. 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 31
use 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, 72
Class 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 29
Reset button 58
Search button 34
Subscribers button 26
C
Call Detail Record (CDR) 97
Cautions
138
Copyright © Nokia Corporation 2002.
avoiding use of Refresh button 31
avoiding use of Reload button 31
making an entry in your billing
system 32
saving changes on each screen 31
switching between General and
TGW tabs 31
switching between System and
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 46
creating 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, 47
Configuration 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 56
System 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 104
Device 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 104
SMSC MSISDN* field 104
State/Province field 104
Status field* 103
User name field* 103
Creating new COS plans 47
DN0182152 139
Issue 1-3 en Copyright © Nokia Corporation 2002.
D
Deactivating
COS plans 51 – 53
from Class of Service Plans screen
51
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 40
Documentation
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 66
SNMP 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 70
Description 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
Copyright © Nokia Corporation 2002.
Search for field 42
Self-provisioning field 48, 51
Show field 40
SMSC MSISDN* field 104
State/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
Issue 1-3 en Copyright © Nokia Corporation 2002.
70
changing supervisor password 72
Configuration property 62
Personal Album, defined 98
Product 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 – 44
Search 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 40
adding 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 99
Subscribers button 26
Subscribers, types of
legacy phone owner 12
MMT owner 13
non TGW subscriber 13
TGW subscriber 13
Supervisor
defined 99
Supervisor tab 70
Switching
between General and TGW tabs
31
between System and Events tabs
32
System configuration backup 93
142
Copyright © Nokia Corporation 2002.
T
Tabs
Administrator tab 69
Events tab 56, 65, 66
examples of 28
General tab 36, 47, 49, 52, 53
Supervisor tab 70
switching between General and
TGW tabs 31
switching between System and
Events tabs 32
System tab 56
TGW tab 31, 48, 49, 50
TGW 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 48
Edit Class of Service toolbar 50
Edit Subscriber Information tool-
bar 38
Search Results toolbar 34, 35, 38,
39, 40, 41
Subscriber Search Criteria toolbar
34, 40
toolbar options, examples of 27
Troubleshooting tips
configuring SMS properties 87
configuring the MMSC 87
Typographic conventions 15
U
Update option 38, 49, 53, 54, 64, 66,
67
User data backup 94