Multimedia Messaging Service Center (MMSC) V 2.6

Multimedia Messaging Service
Center (MMSC) v 2.6

User Manual v 1.0
R efer enc e: MMSC- 2.6-UM -1.0
Confidentiality Statement
Copyright © 2009-2010, Comviva Technologies Ltd. All rights reserved. This product or document
may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any
electronic medium or machine readable form, by any means electronic, mechanical, photographic,
optic recording or otherwise without prior consent, in writing, of the copyright owner. Statutory
declaration under section 52A of the Copyright Act 1957.
i
Restrictions and Copyright Declaration
The information in this document is subject to change without notice and describes only the product defined in the introduction of this
documentation. This document is intended for the use of prospective Comviva customers for the sole purpose of the agreement under which the
document is submitted. No part of it may be reproduced or transmitted in any form or means without the prior written permission of Comviva. The
intended audience for this document is professional personnel, who assume full responsibility for using the document appropriately. Comviva
welcomes customer comments as part of the process of continuous development and improvement of its documentation. The information or
statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be
considered binding, but shall be defined in contextual specific eventual agreement made between Comviva and the customer.
However, Comviva has made all reasonable efforts to ensure that the instructions contained in the document are adequate, sufficient and free of
material errors and omissions. Comviva will, if necessary, explain issues, which may not be covered by the document. Comviva’s liability for any
errors in the document is limited to the documentary correction of errors. Comviva will not be responsible, in any event, for errors in this document
or for any damages, incidental or consequential, including monetary losses, that might arise from the use of this document or the information in it.
This document and the product it describes are considered protected by Patent, Copyright and Trademark laws in accordance with relevant
Indian laws.
The only warranties for Comviva products and services are set forth in the express warranty statements accompanying its products and services.
Nothing herein should be construed as constituting an additional warranty. Comviva shall not be liable for technical or editorial errors or omissions
contained herein.
The Comviva logo is a registered trademark of Comviva Technologies Ltd. Other product names mentioned in this document may be trademarks
of their respective companies and they are mentioned for identification purposes only.
Copyright © 2009 Comviva Technologies Ltd. All rights reserved.
iii
Contents
1 Document Overview .................................................................................................................................1
1.1 Scope .............................................................................................................................................................. 1
1.2 Audience......................................................................................................................................................... 1
1.3 Conventions ................................................................................................................................................... 1
1.4 Acronyms and Abbreviations ..................................................................................................................... 2
1.5 Feedback and Suggestions ......................................................................................................................... 2
2 Introduction ...............................................................................................................................................3
2.1 Overview ......................................................................................................................................................... 3
2.2 Features .......................................................................................................................................................... 3
2.3 MMSC Architecture and Interfaces ............................................................................................................ 4
2.4 Server Management ...................................................................................................................................... 9
2.5 Working of MMSC ......................................................................................................................................... 9
3 Web-based Operations.......................................................................................................................... 11
3.1 Login ............................................................................................................................................................. 11
3.2 Configuration Management ....................................................................................................................... 15

3.2.1 Server Configuration ..................................................................................................................................... 15
3.2.2 Monitor Agent ................................................................................................................................................ 26
3.2.3 Volume Manager ........................................................................................................................................... 30
3.2.4 Database ....................................................................................................................................................... 32
3.2.5 Receive CGI Configuration ........................................................................................................................... 33
3.2.6 Retrieve CGI Configuration .......................................................................................................................... 35
3.2.7 Billing.............................................................................................................................................................. 37
3.2.8 MMSC Lookup ............................................................................................................................................... 45
3.2.9 Provisioning Server ....................................................................................................................................... 47
3.2.10 Webtop Interface ................................................................................................................................. 50
3.3 Message Dispatcher ................................................................................................................................... 53

3.3.1 Push Configuration........................................................................................................................................ 53
3.3.2 SMS Configuration ........................................................................................................................................ 57
3.3.3 E-mail Configuration...................................................................................................................................... 65
iv
3.3.4 Application ..................................................................................................................................................... 68
3.4 Auxiliaries..................................................................................................................................................... 71
3.4.1 Mail Agent ...................................................................................................................................................... 71
3.4.2 MM7 ............................................................................................................................................................... 74
3.4.3 Auxiliaries Configuration ............................................................................................................................... 76
3.5 Status Manager............................................................................................................................................ 78
3.6 Subscriber Manager - Provisioning ......................................................................................................... 79

3.6.1 Add Subscribers ............................................................................................................................................ 79
3.6.2 Edit Subscriber .............................................................................................................................................. 81
3.7 Subscriber Manager- Black & White Subscriber List ............................................................................ 83

3.7.1 Add Subscribers ............................................................................................................................................ 83
3.7.2 Edit Subscribers ............................................................................................................................................ 84
3.8 Subscriber Manager-Services................................................................................................................... 85
3.9 Subscriber Manager-PPG .......................................................................................................................... 88
3.10 Subscriber Manager-Search Utility .......................................................................................................... 90

3.10.1 Services List ........................................................................................................................................ 90
3.10.2 Subscriber List – With Services.......................................................................................................... 92
3.10.3 Subscriber List – With Content Format .............................................................................................. 93
3.11 Statistics Manager ...................................................................................................................................... 94

3.11.1 Statistics Reports ................................................................................................................................ 96
3.12 Usage Reports ........................................................................................................................................... 100

3.12.1 Configuration ..................................................................................................................................... 109
3.13 Message Manager ..................................................................................................................................... 110

3.13.1 Message Trace-MMSC ..................................................................................................................... 110
3.13.2 MMSC Log ......................................................................................................................................... 112
3.13.3 MM3 ................................................................................................................................................... 113
3.14 Configuration ............................................................................................................................................. 116
3.15 User Manager ............................................................................................................................................. 117
Appendix A — MMSC CDRs .................................................................................................................. 121
Appendix B — MMSC Directories ......................................................................................................... 129
Appendix C — MMSC Traps .................................................................................................................. 135
v
Appendix D — Customer Support ........................................................................................................ 139
Document Change History .................................................................................................................... 141
Contact Us................................................................................................................................................ 143
vi
Figures
Figure 2-1: Block Diagram ................................................................................................................. 4
Figure 2-2: MM1 ................................................................................................................................ 5
Figure 2-3: MMS Call Flows ............................................................................................................... 6
Figure 2-4: MM3 Call Flows ............................................................................................................... 6
Figure 2-5: MM4 ................................................................................................................................ 7
Figure 2-6: MM4 Block Diagram......................................................................................................... 7
Figure 2-7: MM4 Call Flow ................................................................................................................. 7
Figure 2-8: MM7 Call Flow ................................................................................................................ 8
Figure 3-1: Login ............................................................................................................................. 11
Figure 3-2: Home Page ................................................................................................................... 12
Figure 3-3: Add Instance.................................................................................................................. 12
Figure 3-4: Add Instance.................................................................................................................. 13
Figure 3-5: Instance added to Instance Manager ............................................................................. 13
Figure 3-6: Edit Instance .................................................................................................................. 13
Figure 3-7: Instance Edited .............................................................................................................. 14
Figure 3-8: Instance Configuration ................................................................................................... 14
Figure 3-9: Server Configuration ...................................................................................................... 15
Figure 3-10: Server Configuration- Message Types ......................................................................... 24
Figure 3-11: Edit Server Configuration ............................................................................................. 25
Figure 3-12: Edit Server Configuration-MessageTypes .................................................................... 26
Figure 3-13: MM Monitor Configuration ............................................................................................ 27
Figure 3-14: MM Monitor Configuration-Edit ..................................................................................... 30
Figure 3-15: Volume Manager ......................................................................................................... 31
Figure 3-16: Edit Volume Manager .................................................................................................. 32
Figure 3-17: MM Database Manager................................................................................................ 32
Figure 3-18: MM Database Configuration-Edit ................................................................................. 33
Figure 3-19: Receive CGI Configuration........................................................................................... 34
Figure 3-20: Edit Receive CGI Configuration.................................................................................... 35
Figure 3-21: Retrieve CGI Configuration .......................................................................................... 35
Figure 3-22: Edit Retrieve CGI Configuration ................................................................................... 37
Figure 3-23: Billing Configuration ..................................................................................................... 37
Figure 3-24: Edit Billing Configuration .............................................................................................. 39
Figure 3-25: Price List...................................................................................................................... 40
Figure 3-26: Add Price ..................................................................................................................... 41
Figure 3-27: Edit Price ..................................................................................................................... 43
Figure 3-28: Device Configuration.................................................................................................... 43
Figure 3-29: Add Device Mapping .................................................................................................... 44
Figure 3-30: Edit Device Mapping .................................................................................................... 44
Figure 3-31: DNS Enum Configuration ............................................................................................. 45
Figure 3-32: Edit DNS Enum Configuration ...................................................................................... 47
Figure 3-33: Provisioning Server Configuration ................................................................................ 48
Figure 3-34: Edit Provisioning Server Configuration ......................................................................... 50
Figure 3-35: Webtop Interface Configuration .................................................................................... 51
Figure 3-36: Edit Webtop Interface Configuration ............................................................................. 53
Figure 3-37: PUSH Configuration..................................................................................................... 54
Figure 3-38: Edit Push Configuration ............................................................................................... 57
Figure 3-39: SMS Configuration....................................................................................................... 58
Figure 3-40: Database and SMS Configuration- (Contd) .................................................................. 60
Figure 3-41: PPG Configuration- (Contd) ......................................................................................... 61
Figure 3-42: SMS Message Contents- (contd) ................................................................................. 62
Figure 3-43: SMS Configuration-Edit................................................................................................ 64
Figure 3-44: EMAIL Configuration .................................................................................................... 65
Figure 3-45: Edit EMAIL Configuration ............................................................................................. 68
Figure 3-46: Application Terminated Configuration ........................................................................... 69
Figure 3-47: Application Terminated Configuration-Edit.................................................................... 71
Figure 3-48: Mail Agent Configuration .............................................................................................. 72
Figure 3-49: Mail Agent Configuration-Edit....................................................................................... 74
vii
Figure 3-50: MM7 Interface Configuration ........................................................................................ 75
Figure 3-51: Edit MM7 Interface Configuration ................................................................................. 76
Figure 3-52: Auxiliaries Configuration .............................................................................................. 77
Figure 3-53: Auxiliaires Configuration - Edit ..................................................................................... 78
Figure 3-54: Status Manager ........................................................................................................... 78
Figure 3-55: Subscriber Registration ................................................................................................ 79
Figure 3-56: Edit Subscriber ............................................................................................................ 81
Figure 3-57: Subscriber List ............................................................................................................. 81
Figure 3-58: Subscriber List-Edit ...................................................................................................... 83
Figure 3-59: Black and White Subscribers-Add ................................................................................ 83
Figure 3-60: Black and White Subscribers-Search ........................................................................... 84
Figure 3-61: Black and White Subscribers List ................................................................................. 85
Figure 3-62: Black and White Subscribers-Edit ................................................................................ 85
Figure 3-63: Service List .................................................................................................................. 85
Figure 3-64: Add Service ................................................................................................................. 86
Figure 3-65: PPG List ...................................................................................................................... 88
Figure 3-66: Add PPG ..................................................................................................................... 89
Figure 3-67: Edit PPG...................................................................................................................... 90
Figure 3-68: Service Options ........................................................................................................... 90
Figure 3-69: Service List Search Result ........................................................................................... 92
Figure 3-70: Subscriber’s List-With Service List ............................................................................... 93
Figure 3-71: Subscriber’s List Result-With Service ........................................................................... 93
Figure 3-72: Subscriber’s List-Content Format ................................................................................. 94
Figure 3-73: Subscriber’s List Result- Content Format ..................................................................... 94
Figure 3-74: Statistics Manager ....................................................................................................... 95
Figure 3-75: Statistic Reports........................................................................................................... 96
Figure 3-76: Get User info based on phone number ......................................................................... 96
Figure 3-77: User Information report based on phone number.......................................................... 97
Figure 3-78: Top n Users ................................................................................................................. 97
Figure 3-79: Top n MMS input criteria ............................................................................................. 98
Figure 3-80: Top n MMS result ....................................................................................................... 99
Figure 3-81: Message Class .......................................................................................................... 100
Figure 3-82: Usage Reports ........................................................................................................... 100
Figure 3-83: Defined Period Over Service ...................................................................................... 100
Figure 3-84: Defined Period Over Service-Report .......................................................................... 101
Figure 3-85: Defined Period Over User Agent ................................................................................ 102
Figure 3-86: Defined Period Over User Agent-Report .................................................................... 102
Figure 3-87: Defined Period Over Originate Domain ...................................................................... 103
Figure 3-88: Defined Period Over Originate Domain-Report ........................................................... 103
Figure 3-89: Defined Period Over Terminate Domain ..................................................................... 104
Figure 3-90: Defined Period Over Terminate Domain-Report ......................................................... 104
Figure 3-91: Success/Fail Rate ...................................................................................................... 105
Figure 3-92: Success/Fail Rate-Report .......................................................................................... 105
Figure 3-93: Success/Fail Rate in MO............................................................................................ 106
Figure 3-94: Success/Fail Rate in MO-Report ................................................................................ 106
Figure 3-95: Defined Period over IOT ............................................................................................ 107
Figure 3-96: Defined Period over IOT-Reports ............................................................................... 107
Figure 3-97: Number of Messages in Range of Size ...................................................................... 108
Figure 3-98: Number of Message in Range of Size-Reports ........................................................... 108
Figure 3-99: Graphs ...................................................................................................................... 109
Figure 3-100: Reports Configuration .............................................................................................. 109
Figure 3-101: Edit Reports Configuration ....................................................................................... 110
Figure 3-102: Message Manager - MMSC ..................................................................................... 110
Figure 3-103: Message Manager - MMSC ..................................................................................... 111
Figure 3-104: Message Manager-MMSC-Report ............................................................................ 112
Figure 3-105: Message Manager- Export MMSC Configuration ...................................................... 112
Figure 3-106: MMSC LOG ............................................................................................................. 113
Figure 3-107: Message Manager-MM3 .......................................................................................... 114
Figure 3-108: Message Manager-MM3 Report ............................................................................... 115
Figure 3-109: Message Manager- Export MM3 Configuration ......................................................... 115
viii
Figure 3-110: MMSC Message Trace Configuration ....................................................................... 116
Figure 3-111: Message Manager-Edit MM3 and MMSC Configuration ........................................... 117
Figure 3-112: User Manager .......................................................................................................... 117
Figure 3-113: Add User ................................................................................................................. 118
Figure 3-114: User Added -Confirmation ........................................................................................ 119
Figure 3-115: Edit User.................................................................................................................. 120
Figure 3-116: Include File .............................................................................................................. 133
ix
Tables
Table 1: Conventions......................................................................................................................... 1
Table 2: Acronyms and Abbreviations ................................................................................................ 2
Table 4: Field Description of Add Instance ....................................................................................... 12
Table 5: Field Description of Server configuration ............................................................................ 16
Table 6: Field Description of Server Configuration-Contd….............................................................. 24
Table 7: Field Description of MM Monitor Configuration ................................................................... 27
Table 8: Field Description of Volume Manager ................................................................................. 31
Table 9: Field Description of Database ............................................................................................ 32
Table 10: Field Description of Receive CGI Configuration ................................................................ 34
Table 11: Field Description of Retrieve CGI Configuration ................................................................ 36
Table 12: Field Description of Billing Configuration........................................................................... 37
Table 13: Field Description of Price Configuration ............................................................................ 40
Table 14: Field Description of Add Price .......................................................................................... 41
Table 15: Field Description of Device Mapping................................................................................. 44
Table 16: Field Description of DNS Configuration ............................................................................ 45
Table 17: Field Description of Provisioning Server Configuration...................................................... 48
Table 18: Field Description of Webtop Interface ............................................................................... 51
Table 19: Field Description of PUSH Configuration .......................................................................... 54
Table 20: Field Description of SMS Configuration (Common Parameters) ........................................ 58
Table 21: Field Description of Primary/Secondary Database and SMS Configuration ....................... 60
Table 22: Field Description of Primary and Secondary PPG Configuration ....................................... 61
Table 23: Field Description of SMS Message Contents .................................................................... 62
Table 24: Field Description of E-mail Configuration .......................................................................... 66
Table 25: Field Description of Application Terminated Configuration ................................................ 69
Table 26: Field Description of Auxiliaries.......................................................................................... 72
Table 27: Field Description of MM7.................................................................................................. 75
Table 28: Field Description of Auxiliaries Configuration .................................................................... 77
Table 29: Field Description of Subscriber Registration (Add Subscriber) .......................................... 79
Table 30: Field Description of Subscriber Registration ..................................................................... 82
Table 31: Field Description of Black & White Subscriber Registration............................................... 84
Table 32: Field Description of Service List ....................................................................................... 86
Table 33: Field Description of Add Service....................................................................................... 87
Table 34: Field Description of PPG List ............................................................................................ 88
Table 35: Field Description of Service Options ................................................................................. 91
Table 36: Field Description of MMSC Statistics ................................................................................ 95
Table 37: Field Description of Top n MMS ....................................................................................... 98
Table 38: Field Description of Top n MMS Results ........................................................................... 99
Table 39: Field Description of Define Period over Service-Report................................................... 101
Table 40: Field Description of Number of Messages in the Range Size .......................................... 108
Table 41: Field Description of Message Trace-MMSC .................................................................... 111
Table 42: Field Description of MMSC Log ...................................................................................... 113
Table 43: Field Description of MM3................................................................................................ 114
Table 44: Field Description of Configuration ................................................................................... 116
Table 45: Field Description of User Manager ................................................................................. 118
Table 46: MMSC CDR Fields ......................................................................................................... 121
Table 47: Status Value .................................................................................................................. 126
Table 48: Field Description of Record Types .................................................................................. 127
Table 49: Field Description of exe Directory ................................................................................... 129
Table 50: Field Description of Conf Directory ................................................................................. 129
Table 51: Field Description of fcgi Directory ................................................................................... 130
Table 52: Field Description of log Directory .................................................................................... 130
Table 53: Field Description of Scripts Directory .............................................................................. 131
Table 3: Field Description of scripts directory ................................................................................. 131
Table 54: Field Description of Scripts/Health Directory ................................................................... 131
Table 4: Field Description of scripts/health directory....................................................................... 131
Table 55: Field Description of mdata/stat Directory ........................................................................ 131
Table 56: Field Description of mdata/trap Directory ........................................................................ 132
xi
Table 57: Field Description of gui Directory .................................................................................... 132
Table 5: Field Description of gui directory ...................................................................................... 132
Table 6: SLA Matrix ....................................................................................................................... 139
Table 7: Document Change History ............................................................................................... 141
xii
1 Document Overview
This chapter gives a brief introduction to the scope and organization of this manual.
1.1 Scope
This manual gives comprehensive information on the functionality, features and operations of
MMSC.
1.2 Audience
The information contained in this manual is for system administrators, network engineers and
other users of the MMSC.
1.3 Conventions
Table 1: Conventions
Information Convention
Window/Screen/Button/Icon/Menu/Field All names as seen in the applications are written in

Names/parameters bold.
Examples:
 Click OK to continue.
 The New User window appears.
 Enter your login name in User Name.

Names of File/Section/Document/Path names are written in Italics.
Files/Sections/Documents/Folders/
Example:
Refer to Information.doc for details.
Text to be Entered/Commands/Code Example:
C:> DOS
Command output Example:

User is successfully added.
Key Presses Example:
<Enter>, <Esc>
Source: Comviva
 Warning Message
 Notes
Document Overview 1
User Manual: MMSC – 2.6
1 .4 Ac ro ny ms an d Ab b rev ia tio n s
Table 2: Acronyms and Abbreviations
Term Full Form
AT Application Terminated
CIMD Computer Interface to Message Distribution
GPRS General Packet Radio Service
GSM Global Systems for Mobile Communication
3GPP Third Generation Partnership Project
HTTP Hypertext Markup Language
JPEG Joint Pictures Expert Group
LAN Local Area Network
MBPS Mega Bytes Per Second
MIDI Musical Instrument Digital Interface
MMS Multimedia Message Service
MMSC Multimedia Messaging Service Center
SOAP Simple Access Object Protocol
SMS Short Message Service
SMTP Simple Mail Transfer Protocol
VAS Value Added Service
VASP Value Added Service Providers
WAP Wireless Application Protocol
WSP Wireless Session Protocol
1 .5 F e ed ba c k a n d Su gg es tio n s
Thank you for taking the time to comment on Comviva documentation. It is our goal to provide
you with the accurate, timely, and useful documentation. Please send your valuable comments,
suggestions and feedback to techwriters@comviva.com.
2 Document Overview
2 Introduction
2.1 Overview
Congratulations on purchasing the MMSC. The MMSC provides the means of delivering the
multimedia messaging service over the various mobile technologies such as GSM, CDMA
and so on to the MMS subscriber. MMS (Multimedia Messaging Service) is a technology that
allows the users of MMS enabled mobile phones to send and receive messages with
formatted text, graphics, and photographic images, audio and video clips. Video sequences,
audio clips and high-quality images can be downloaded to the phone from WAP sites, or use
an attached accessory, such as a digital camera, to capture and send an MMS message.
MMS messages can be sent either to another MMS-enabled mobile phone or to an e-mail
address. Photos, sound and video clips can also be stored in the phone for later use. MMS
supports standard image formats such as GIF and JPEG, video formats such as MPEG 4 and
audio formats such as MP3 and MIDI. Multimedia messaging takes advantage of the high
transmission speeds, something that the GPRS and the new high-speed 3G technologies can
provide, to deliver multimedia content and value added services to the end user.
MMS offers total freedom to convey ideas, exchange information or to express oneself. The
technology is all about presenting the content in the way you prefer. The MMSC enables
smooth service take offs and provides Operators with new opportunities in service
differentiation. It provides long-term storage for multimedia messages and storage capacity in
addition to the terminal’s memory capacity. These services can be accessed via Web. Legacy
phone support enables mobile users to experience multimedia messaging via SMS. If the
receiver does not have a multimedia terminal, on receipt of a multimedia message he/she will
be notified via SMS, which can be accessed via Web. MMS solution can be seamlessly
integrated to the Operator’s existing network infrastructure. Smooth assimilation ensures that
billing, network management, and other systems work effectively and efficiently with new
applications. The MMSC provides a cost effective and highly scalable MMS solution for easy
implementation on an existing WAP infrastructure.
2.2 Features
The MMSC includes the following features:
 Support for standard interfaces like HTTP (MM1-interface services) and SOAP
(MM7-interface services).
 Communication with other MMS systems (MM4-interface services). Full support to
3GPP release 6.5 (third generation partnership project).
 Support for different message flows.
 Mobile originated (phone to Web/phone)
 Mobile terminated (Web to phone)
 Application originated (Web to phone)
 Application terminated (phone to Web)
 Mail originated (Web to phone)
 Mail terminated (phone to Web)
 Legacy terminal support.
 Non-multimedia terminal users receive an SMS detailing how to retrieve their
messages
 Multiple viewing of messages
 Operator configurable SMS message
 Album services.
Introduction 3
 Store, browse, retrieve, forward multimedia messages

 Compose new multimedia messages
 Notification of new messages
 Web-based administration.
 Provisioning on request
 Self-provisioning features
 GUI for every component
 Class of service based subscriber management·
 Support for CDR’s.
 SNMP support.
 Different database support (MySQL/Oracle).
 Billing support (MM8) as per 3GPP.
 Subscriber is a person who is provisioned in the MMSC database for using the MMSC services of
the Operator.
2.3 MMSC Architecture and Interfaces

The working of the MMSC is described in the diagram shown below. The interfaces used are
explained in detail with their call flow diagrams in the following sections.
Figure 2-1: Block Diagram
MM1
This interface defines the means to send messages from MMS phone to another MMS
enabled phone. It also allows pushing of information from the MMSC to the MMS client as
part of MM notifications. The interface can be realized over WSP using a WAP gateway or by
using HTTP. MM notifications require a push proxy gateway as these notifications are sent to
client devices using WAP push.
4 Introduction
Figure 2-2: MM1
Introduction 5
The following figure shows the call flow for MM1 interface and the components that come in to
picture when this interface is used.
Figure 2-3: MMS Call Flows
MM3
Legacy systems like SMTP can send MM message using this interface. Example: mail to
phone. The MM3 interface allows an MMSC to communicate with external (legacy)
messaging systems. One such example is the interface to available E-mail messaging
systems. Mails can be sent from mobile devices to a valid E-mail address. Mails can be
received from E-mail clients for destination mobile devices. The interface protocol used is the
Simple Mail Transfer Protocol (SMTP).
Figure 2-4: MM3 Call Flows
6 Introduction
MM4
MMS system can send the request to other MMS system using MM4 interface. This interface
is necessary for exchanging multimedia messages between distinct MMS environment. The
originator MMSC (MMSC associated with the sender of a MM) has to send the message to
each of the recipients’ MMSC using SMTP. The MMSC has to resolve the recipient's MMSC
domain name to an IP address (example using DNS, domain name server, based on the
recipient's address).
Figure 2-5: MM4
MM4 support with MMSC requires Qmail installation. The MMSC machine could have the
Qmail installation else Qmail could be on the same LAN.
Figure 2-6: MM4 Block Diagram
MMSC implements ENUM based forwarding (DNSENUM) as part of MM4 delivery

implementation. This works by looking into a standard database and matching a range of
MSISDN’s to a MMSC. On submit of MM message, if message is not in home network, then
the DNSENUM server is contacted to determine recipient MMSC. The recipient MMSC is then
contacted over the MM4 interface (SMTP). MMSC uses DNSENUM as it has the advantage
of being an industry standard database implementation. The following figure shows the call
flow for MM4 interface.
Figure 2-7: MM4 Call Flow
Introduction 7
MM6
This is an Interface between the MMS proxy relay and the MMS storage. These databases
maintain user specific information such as user profiles and subscription parameters. User
profile in the MMS shall be able to support the ability to create, update, store, transfer,
interrogate, manage and retrieve a user’s MM profiles. The MM profiles shall allow a user to
configure and personalize his multimedia messaging environment with the multimedia
messaging profiles (Example which media types and notifications that shall be delivered to
the recipient, such as voice only or text only).
MM7
This interface allows VAS applications to request service from MMSC (message submission,
and so on.) and to obtain messages from remote MMS user agents. VAS may be provided by
the network Operator of the MMSC or by third-party VASP (providers). VAS can send request
to the MMS system using MM7 interface over HTTP. The following figure shows the call flow
for MM7 interface.
Figure 2-8: MM7 Call Flow
MM8
Interface between the MMS proxy relay and the Billing Mediation Agent (BMA). The BMA and
the MMSC have a propriety interface. Only CDRs generated according those standards. The
MM8 interface provides billing records for billing clients based on their usage of MMS
services. Two basic forms of billing namely pre-paid and postpaid are supported. Pre-paid
billing is implemented by interfacing with the billing system of the MSP. Post-paid billing is
implemented by writing CDR files for MMS services used.
The other interfaces are:
 SMPP
 Short Messaging Peer To Peer
 CIMD
 Computer Interface to Message Distribution
 SMSC
 Short Messaging Service Center
 HTTP
 Hyper Text Transfer Protocol
8 Introduction
 WSP: Wireless Session Protocol

 VAS: Value Added Services
2 .4 S e rv e r M an ag e me n t
This section provides the information about the servers providing MMS services. The
following are the MMSC servers:
 DNS-enum server: When a subscriber sends MM messages to another subscriber
who is not under the Operator’s domain, the MMSC sends the message over the
MM4 interface to other Operator’s MMSC. This requires the resolution of the
subscriber’s phone number to an SMTP address. DNS-ENUM is a protocol that is
used to achieve this objective. DNS-ENUM server resides along with the MMSC
and has been designed in a manner that allows easy integration with DNS-ENUM
once the protocol has been standardized and implemented. Currently this
component uses static tables for phone number resolution to SMTP addresses.
 Receive server: Any message submitted by the user to MMSC will come to
receive server. Receive server verifies the credentials (subscription, destination
address like mobile number, other Operator mobile number and so on) of the
sender and the destination and accordingly generate a notification.
 Retrieve server: When the subscriber is notified of a message in the MMSC via a
MMS notification, user device connects to MMSC to retrieve the message stored
against message reference sent in MMS notification.
 Push dispatcher: If the valid subscriber of the home network sends MM to valid
subscriber of the same network then the notification is sent using this dispatcher.
 SMS dispatcher: Valid subscriber sending an MM to non-subscribed user then an
SMS notification is sent using this dispatcher to the non-subscribed user.
 Mail dispatcher: When the subscriber is sending an MM to an E-mail address or to
another network over MM4 then the message is routed to the destination by the
mail dispatcher, which in turn connects to SMTP server, rely of the network.
 Application dispatcher: Any MMS user sending message to short code configured
in the MMSC uses this dispatcher. This notification is forwarded to the application
configured for the short code by the MM7 dispatcher that is the AT dispatcher.
 Mediation server/agent: It is an integrated module in the MMSC, which provides
interface between the MMSC and the billing server. The mediation agent helps the
MMSC to interface with different implementations.
 Provisioning server: To provision the users to use the MMSC services of the
network Operators.
 MMBox monitor: The MMBox monitor is a component of the MMSC that is used
for management of each user’s MMBox. Another important task of this component
is to transfer CDR records from the MMSC to the billing server. A configuration
entry can be set in this component as to when the CDRs are required to be
transferred from the MMSC to the billing server.
2 .5 Wo rk in g o f M M SC
 When a mobile user sends a multimedia message to another mobile user (a
predefined number) the MMS client establishes a session with the WAP gateway.
This takes place in accordance with the wireless session protocol. The interface
between the MMS client and the WAP gateway is provided by MM1
 The Identity server captures the caller ID (through the RAS) and provides the
same to the MMSC and WAP gateway.
 The WAP gateway forwards the data received to the MMS proxy relay.
Introduction 9
 The proxy relay stores the data to be forwarded in the MMS storage. (It should be
noted that the MMS proxy relay along with the MMS storage constitutes the
MMSC).
 It should be noted that the MMSC communicates with the SMSC through the
PPG. The PPG uses CIMD or SMPP protocols to communicate with the SMSC.
The MMSC sends an alert message to the recipient informing that he/she has
received a new MM (Multimedia Message).
 If the recipient wishes to get the MMS and affirms the request sent, which is done
through the WAP which in turn communicates with MMSC, the MMS is retrieved
from the MMS storage and the MMSC sends this message to the recipient’s
mobile.
 If the message needs to be sent to a user who is under the influence of a foreign
MMSC, then the 2 MMSCs communicate with each other using the MM4 interface
and ensure that the message reaches the appropriate user.
 The entity VAS (Value Added Services) can be used by service providers for
submitting messages to the MMSC, which in turn will be forwarded to the
appropriate user. This entity offers services like advertisements, news, stock
quotes, birthday wishes, or for sending any important messages, and so on to the
end users.
 The MMS relay/server may support services, in addition to user-to-user
messaging, that are either provided by the MMS Operator or by third-party Value
Added Service Providers (VASP). Example, the services that may be provided
are:
 Messages that originate from the VASP to a single or mass-distribution of
recipients
 Messages that originate from a MMS relay/server to the VASP that may
generate a VASP reply or a new MM submission.
 The legacy system comes into picture for providing the additional feature like mail
through MMS.
10 Introduction
3 Web-based Operations
This chapter describes the remote administration and configuration parameters of the MMSC.
After successful installation of the MMSC a directory by name GUI is created under the path
of MMSC installed directory. This directory contains programs and pages related to Web
based configuration.
 Web browsers like Internet Explorer 4.0 and above or Netscape 6.0 and above can be used to
access this administration tool.
3.1 Login
To access the application GUI:
 Start the Internet Explorer.
 Type the following URL Error! Hyperlink reference not valid., in the address
bar:
Where ipaddress is the IP of the machine where MMSC is installed.
To login for the first time, use admin as the username and type admin123 as password.
 It is advisable to change the password for security reasons. This feature is available in user
management link (Refer section 3.15).
Figure 3-1: Login
 Enter your username and password in User name and Password.

 Click Login.
Web-based Operations 11
If the login ID and password entered are correct, the home page appears.
Figure 3-2: Home Page
To add a new instance:

 Click Add.
The following screen is displayed.
Figure 3-3: Add Instance
The following table provides a description of the screen fields.
Table 4: Field Description of Add Instance
Field Description Default/Example
Instance Name The name of the MMSC instance

MMSC instance should be installed
Port The port on which the instance is
listening
Admin Path The path where the MMSC admin
module is installed
 Enter the field values.

 Click Ok.
Figure 3-4: Add Instance
 Click Ok.
Figure 3-5: Instance added to Instance Manager
 The instance is added under the Instance manager.

To edit the instance configuration:
 Click .
Figure 3-6: Edit Instance
 It has same fields as add instance.

 The Instance name and IP address cannot be edited.
 Enter the values.
 Click Ok.
Figure 3-7: Instance Edited
To view the instance configuration:

 Click Instance Name.
The following screen is displayed
Figure 3-8: Instance Configuration
3.2 Configuration Management

This feature is used to configure the receive/retrieve server.
3.2.1 Server Configuration

Configuration Management > Server Configuration
The Server Configuration screen is displayed.
Figure 3-9: Server Configuration
Table 5: Field Description of Server configuration
MMSC Name The name of the MMSC server Example: MMSC

Service Provider Name The name of the service provider Example: WAP
Phone Domain Name The domain name used for sending Example: receive
MMS to WAP-PHONE type
IP Address It is the interface IP address at Default: 127.0.0.1

which the receive server accepts
connections
Receive TCP Port It is the TCP port at which the Default: 14100
receive server listens for incoming
requests. The configuration comes
with a default port number; it is
recommended that this value
should not be changed
Retrieve IP Address It is the interface IP address at Default: 127.0.0.1
which the retrieve server accepts
connections
Retrieve TCP Port It is the TCP port at which the Default: 14110
retrieve server listens for incoming
Server Receive Timeout The timeout in seconds after which Example: 30
the TCP receive call is aborted and
an error is logged. This may arise
when a client request has not been
sent properly or some fragments
are lost. In that case, instead of
making the receive/retrieve server
wait indefinitely for the request, the
receive call is timed out. A value of
4-5 seconds may be used on a fast
Ethernet, for slower networks (dial-
up lines), a value of 20 seconds is
sufficient
Accept Thread Pool The number of threads that are Example: 10
waiting to receive a request.
Typical values must not be more
than 10 and a value of 10 is more
than enough to handle large
volumes of traffic
HTTP Thread Pool The maximum number of threads Example: 0
that are created for the HTTP
handler in the MMSC. If a value of
0 is specified, only 1 thread is
created that will service all HTTP
requests
Receive HTTP Port Port number where the receive Example: 0
server listens for HTTP requests
from MMS clients. A value of 0
disables the HTTP listener in the
receive server
Retrieve HTTP Port Port number where the retrieve Example: 0

server listens for HTTP requests
from MMS clients. A value of 0
disables the HTTP listener in the
retrieve server
Retrieve Server URL It is the URL, which is sent out to Default: http://127.0.0.1:80/m1
destination clients in the notification (Script Alias)
message. The configuration comes
with a default URL; it is
Brew Trigger ClassID The class ID sent as part of brew Example: 3000
notification sent to the brew
devices
MM1 Interface Maximum This parameter specifies the This is applied only if the
Message Size maximum message size in interface level message size
kilobytes at the MM1 interface level check is enabled .Example: 200
MM1 Interface Allowed This parameter specifies the This is applied only if the
Content Type(s) allowed content types at the MM1 Interface level content type
interface level filtering is enabled. Example:
text/vnd.wap.wml
MM1 Interface Restricted The restricted content types at the This is applied only if the
Content Type(s): MM1 Interface level interface level content type
filtering is enabled. Example:
application/vnd.wap.wmlscriptc
MM3 Interface Maximum The maximum message size in This is applied only if the
Message Size kilobytes at the MM3 interface level Interface level message size
check is enabled. Example: 200
MM3 Interface Allowed The allowed content types at the This is applied only if the
Content Type(s) MM3 interface level. interface level content type
text/vnd.wap.wml
Content Type(s) MM3 interface level interface level content type
Message Size kilobytes at the MM4 Interface level Interface level message size
text/vnd.wap.wml
Message Size kilobytes at the MM7 interface level interface level message size
text/vnd.wap.wml

Content Type(s): MM7 interface level interface level content type
MM1 Support If enabled MM1 originated Default: Enabled
messages are processed
MM3 Support If enabled MMS can be sent to E- Default: Enabled
mail domain
MM4 Support If enabled, the routing of MM can Default: Enabled
be done from one domain to other
domain
MM7 Support If enabled, MM can be sent to or Default: Enabled
accepted from application
MM7 to MM4 support This specifies whether the request
for sending an MM from value
added services to other network
mobile terminal is enabled or not
Allow MM7 Sent Item Entry This specifies whether an MM sent
from value added services should
be stored in sent-item folder of the
value added service provider or not
Prepaid-Billing Support If flag is true then prepaid billing Default: Disabled
support is enabled
Bill Submit Request It specifies whether to bill for MMS
submit request when prepaid billing
is enabled
Bill Forward Request It specifies whether to bill for MMS
forward request when prepaid
billing is enabled
Bill Retrieve Request It specifies whether to bill MMS
retrieve request when prepaid
billing is enabled
Content Type Check This specifies, whether content Default: Disabled
type checking is to be done based
on the 'Allow content type list'
parameter before delivering it
Allowed Content Type List This defines the list of allowed Example: text /plain
content types; the content type
checking is to be done based on
this list before delivering it
Black and White Subscribers Verifies the sender; receiver(s) are Example: Enabled
Check in black, white list before delivering
MM
ContentAdaptationSupport If enabled the media elements will Example: jpeg to gif.MMS
be converted from one format to
other based on the receiver .
Adaptation Server IP Address Defines interface IP address at Example: 127.0.0.1
which adaptation server accepts
requests
Adaptation Server Port Defines port number at which Example: 17788
adaptation server listens for
requests
Adaptation Timeout The time in seconds to wait for Example: 30
response from the adaptation
server
Authenticate Sender If enabled the subscriber is

authenticated against his
subscription for sending the
message.
Auto Provision This parameter specifies whether
auto provisioning is enabled or not.
If sender is selected, it specifies
that the Sender of the MM is auto
provisioned. If ‘sender and receiver’
is selected then both sender as
well as receiver of the MM is auto
provisioned. MMSC does not
require users to be provisioned
before they can send and receive
multimedia messages (although the
phones themselves must be
provisioned for multimedia
messaging). Unprovisioned users
are provisioned either the first time
they send a multimedia message
(mobile-originated auto
provisioning) or the first time they
receive a multimedia message
(mobile-terminated auto
provisioning).
Auto Provisioning Billing Type Specifies the billing type of the auto Example: Prepaid or Postpaid. 1
provisioned user means default auto provision
billing type for prepaid billing. 2->
default auto provision billing type
for postpaid
Domain Phone List Defines the phone lists that are a Example: 9865*
part of the MMSC's home domain.
An entry consists of the phone
number format and is in the form of
a regular expression. It can accept
the two wildcard characters, * and
?. Using this, an administrator may
define a phone domain for a whole
set of phones
Other Domain Phone List Defines the phone lists that are not Example: 9886*
part of the MMSC's home domain.
An entry consists of the phone
set of phones
Nation Code It is the unique country code for Example: 91(India)
which the MMSC is serving
Network Type This parameter identifies whether Example: 1
MMSC is in GSM/CDMA network. 0
means MMSC in CDMA network.1
means MMSC in GSM network
Delivery Report It specifies whether the delivery
report support is enabled or
disabled.1 for enable and 0 for
disable
Delete MM on Download This specifies whether the MM

should be deleted from the user
inbox on retrieval or not. If enabled
the MM is deleted from the user
inbox after successful retrieval by
the client otherwise the MM kept in
user inbox till the MM expires. 1 for
enable and 0 for disable
Mail Domain Name Defines the domain name the Example: jataayusoft.com
MMSC attaches with the phone
number when the message is being
sent to any mail id or to any other
MMSC
MM Expiry Time The default expiry time of an MM in Example: 7*24*SECS_IN_HR.
hours, if originator is not explicitly
specified the expiry time of the
MMS message
SMS Alert on MMBOX full This parameter specifies whether
to send an SMS message to the
recipient/sender of the MM box full.
If the originator is selected, the
MMBOX full notification message
specified in the originator SMS alert
message' is sent to the sender. If
the recipient (1) is selected, the
MMBOX full notification message
specified in the recipient SMS alert
message is sent to the recipient. If
the disable (0) is selected, the
MMBOX full notification message is
not sent.
Originator SMS Alert Message This configuration parameter Example: The MM submission to
specifies the SMS message to be XMU has failed because the MM
sent to the originator of the MM in inbox is full
case the recipient user inbox is full.
The Message should contain a
string "XMU”, which will be
replaced with the recipient user
phone number whose inbox is full
Recipient SMS Alert Message Specifies the SMS message to be Example: Your MM Inbox is full.
sent to the recipient of the MM in Delete old multimedia messages
case of his inbox is full to receive new MM
Legacy Notification Message Specifies the SMS message to be
sent to the recipient of the MM in
case the recipient is legacy Mobile
terminal. The message should
contain XMMSFROM, XMMSKEY
as part of SMS message, which will
be, replace with the originator
mobile number and generated
message key respectively.
Example: You have got an MMS
from XMMSFROM and the
message key is XMMSKEY
Database Connections The number of database Example: 10
connections to be established
Notify Retry Counter Specifies the number of retries the Example: 5
dispatcher has to try before
deleting entries from the dispatcher
tables in case of failure in
dispatching
Retrieve Subscriber Provision If enabled, the retriever of the MMS

message will be provisioned
automatically if user is not already
provisioned.
Notification Address Show All If enabled, the address of the
sender will be sent to the
destination client even though the
originator has requested for
address hiding.
Time Zone Specifies the time zone value in Example: +530
which MMSC is serving requests
Old Log Directory The directory name under which Example:. /logs/old/
yesterday's logs will be stored
Log Level The amount of logging that will be
done in the log file of the
receive/retrieve server. The
following levels are defined
 Critical (1)
 Warning (4)
 Debug (7)
The critical level implies least
logging, while the debug level gives
rise to maximum logging. A
warning level is the best choice and
is recommended
Disable MMS Gateway If enabled the routing of inbound
MM7 messages based on message
subject is enabled, otherwise the
routing is not done based on
subject
Remove Duplicate Recipient The removal of duplicate recipients Example: 1
from the "to”, "bcc" and "cc"
address. If enabled duplicate
recipients are removed from the
"to", "bcc" and "cc". By this we can
ensure that an MMS will reach to
the recipient only once. 1 is to
enable the feature and 0 for disable
Forward Limit Limit to forward the MMS by MMSC Example: 1.
to the recipient. This is defined by
the ADMIN to all the subscribers.
Once value is specified to this
parameter, MMSC will forward
MMS to recipients depending on
the limit
Interface Level Message Size This specifies whether the
Check messages should be checked for
size at the interface level. If
enabled the messages will be
checked at the interface level
Interface Level Content type Specifies whether the messages
Filtering should be checked for content type
at the interface level. If enabled the
messages will be filtered at the
interface level
Hide Multiple Destinations Specifies whether the recipients’

address is disclosed or not. If
disabled the recipient’s addresses
is disclosed to the recipients
Backward Number Specifies whether the backward
Compatibility number compatibility is enabled or
not. If enabled the backward
number compatibility is enabled
Use Plus Before MSISDN Specifies whether the plus sign (+)
is to be added while sending the
MSISDN headers. If enabled the
plus sign (+) is added while
sending the MSISDN headers
Proxy For AT Messages Specifies whether the proxy server
is used or not while sending the
messages to the application. If
enabled the AT messages are sent
to the proxy and then proxy sends
the messages to the application,
otherwise the AT messages are
sent to the application itself
LDAP Database Support Specifies whether to enable the
LDAP support or not for the MM6
interface
Socket pool Support The socket pool support for the
DNS server. When the enabled the
pool of socket connections will be
provided to DNS server otherwise
no socket pool support. 1 for
MNP Support The sending of E-mail instead of
SMS for legacy users. When
enabled the E-mail will be sent to
the legacy user instead of SMS
otherwise SMS will be sent. 1 for
MM3 Relay Support Avoid the mail loop backing if MNP
support enabled. If enabled the
mail loop backing will be cancelled
otherwise mail loop backing will
there. 1 for enable and 0 for disable
HTTP Persistent Connections Provides the http persistent
Support connection support. If enabled http
persistent connection support will
be provided otherwise normal
connection. 1 for enable and 0 for
disable
MSISDN Override with MMS When enabled MSISDN override
From Address With MMS from address otherwise
no override of MSISDN with the
MMS from address
MM4 Mail Domain Name Specifies the mail domain name, Example:jataayusoft.com
which the MMSC will send when
delivering an MM to the mail user
or other network user, as part of
domain name of the sender
address
Reject Message Decides whether to reject the

message or not. When it is enabled
message will be rejected otherwise
message is allowed for the
submission.
Webtop URL The URL for the Webtop. Webtop
must be installed
VASID Length This specifies the length of the Default: 5
VASID. The length of the VASID
should not exceed more than 9
Auto Generate Password Specifies whether to use auto- Default: Enabled
generated password or not. When
enabled the auto generated
password will be used for the user
at the time of provisioning
User Password Password for the user at the time of
provisioning. When auto generate
password parameter is disabled
then configured password is used
during auto provisioning the user
Domain Resolution Required The MNP (Mobile Number
Portability) support to the MMSC.
When enabled (1) the MNP support
will be added to MMSC. When
disabled (0) then MNP feature will
be disabled.
Scroll down in Figure: Server Configuration to view the following screen.
Figure 3-10: Server Configuration- Message Types
Table 6: Field Description of Server Configuration-Contd…
Message Types This section allows blocking of

messages based on the type (of
PDU). If enabled, the
corresponding message PDU is
accepted and served by MMSC. If
disabled, the corresponding
message PDU is blocked by
MMSC.
Following MM1 related message
types could be blocked/unblocked.
MM1_submit.REQ
MM1_notification.RES
MM1_retrieve.REQ
MM1_acknowledgement.REQ
MM1_forward.REQ
Following MMBox related message
types can be blocked/unblocked.
M-Mbox-Upload.req
M-Mbox-View.req
M-Mbox-Delete.req
M-Mbox-Store.req
Following MM7 related message
types can be blocked/unblocked.
MM7_submit.REQ
MM7_cancel.REQ
MM7_replace.REQ
MM7_deliver.RES
MM7_delivery_report.RES
MM7_read_reply.RES
To edit the server configuration:

1. Click Edit.
Figure 3-11: Edit Server Configuration
 It has same fields as add server configuration.

Scroll down in Figure: Edit Server Configuration to view the following screen.
Figure 3-12: Edit Server Configuration-MessageTypes

 Click Save.
3.2.2 Monitor Agent

This section provides the information needed for configuring the MMBox monitor. It identifies
the old messages and cleans up expired MM from the user’s inbox periodically and generates
CDRs.
Configuration Management>Monitor Agent
The MM Monitor Configuration screen is displayed.
Figure 3-13: MM Monitor Configuration
Table 7: Field Description of MM Monitor Configuration
Database Server IP Address The IP address of the database Example: 192.10.3.4

server
Database Server Port Number The port number at which database Example: 1521
server listens
Database Username The username for database access Example: system
Database User Password: This parameter specifies the Example: manager
password for database user, who is
allowed to access MMSC database
Database Name The database name where the Example: 127.0.0.1:DEMO
MMSC tables are created
Hot Billing Service This parameter is used to enable Example: Enable
hot billing support. Hot billing is a
real time billing where the CDRs
are generated in real time manner.
That is for a very small time
interval (maybe one or two seconds
in hot Billing Interval parameter)
and the mediation server is
contacted to check for the balance

of the prepaid subscriber
Hot Billing Interval Interval time for subsequent hot Example: 60

billing queries. Range from 1
seconds to (24 * 60 * 60) seconds
Hot Billing File Path The directory name under which Example: /tmp
the CDR files are created
Fail Over Service This parameter indicates that Example: Enable
whether failover service thread has
to be enabled or not. A backup
operation that automatically
switches to a standby database,
server or network if the primary
system fails or is temporarily shut
down for servicing. Failover is an
important fault tolerance function of
mission-critical systems that rely on
constant accessibility
Fail Over Server IP The Interface IP address at which Example: 127.0.0.1
the failover service thread is active
Fail Over Server Port The port number at which the Example: 18884
failover service is listening
FTP Service This parameter specifies whether Example: Enable.
FTPing of CDRs to remote
machine is enabled or not
FTP Server IP The interface IP address of the Example: 127.0.0.1
FTP server
FTP Server Port The FTP server listening port Example: 21
FTP User Name This parameter specifies the Example: ftpuser
username to connect FTP server
FTP Password The password used to connect to Example: ftppasswd
FTP server
FTP Directory Path The directory on the FTP server to Example: /tmp/cdrstorage
which you want to upload CDR files
Receive CDR Table Name The name of the receiving CDR Example: receiving_cdr
table
Retrieve CDR Table Name The name of the retrieving CDR Example: retrieving_cdr
table
Push Dispatcher Table Name This is the name of the table where Example: pi_dispatcher
delivery reports are kept. A default
value has been provided and it is
recommended that this value be
not changed
Retry Time This parameter specifies the time in Recommended value: 60
seconds after which the MMBox of
users are checked for unwanted
messages and expired messages.
Start Time This is the start time for MMBOX This parameter is effective when
monitor (24 hr clock format hhmm). retry time is set to 0. Example:
0300
Hierarchy Level The directory level at which the Example: 1
time information about the last
cleanup is stored
Directory Access Timeout The timeout value in hours for Example: 1

accessing user directories for
cleanup
MM Expiry Time The expiry time of an MM in the Example: 24
user inbox
Non MM Expiry Time This parameter specifies the expiry Example: 48
time of an MM in the guest user
space
Delete CDRs Enable this parameter to delete the Example: Enabled
MMBOX monitor CDR entries from
the database
Zip CDR Files This parameter specifies whether Example: Enabled
to compress CDR files or not
Delivery Report This parameter specifies whether Example: Enabled
delivery report has to be generated
for expired message or not
Max CDR Record Select The maximum number of records Example: 10000
allowed to be selected for a single
database query
Old Logs Directory This specifies the path for the old Example: log/old_logs/
log rotation directory
receive/retrieve server.
The following levels are defined
 Critical Level
 Warning Level
 Debug Level
is recommended.
Default: Critical
BER (Basic Encoding Rules) This specifies the encoding support
Encoding Support for the CDR's. When enabled, the
CDR's will be encoded in the BER
otherwise no encoding is done.
HB (Hot Billing) Filename This specifies the filename for the
hot billing system
Logfile This specifies the file in which Example: monitor.log
mmbox monitor logs its activity
Enable SMS Success Alert This specifies whether to send
SMS alert or not to the
administrator regarding the
success and failure MMS. When
enabled the SMS alert will be sent
to the administrator, otherwise this
facility will be disabled
Time for the SMS Alert This parameter specifies the time Example: 1300 (indicates the
of dispatching the SMS. The time 1PM)
format should be in 24 (HHMM)
hour format
Webtop CDR Tablename The Webtop CDR table name Example: WEPTOP_CDR
Waptop CDR Tablename This specifies the Waptop CDR Example: WAPTOP_CDR
table name
To edit the MM monitor configuration:

 Click Edit.
Figure 3-14: MM Monitor Configuration-Edit
 Modify the required field values.

 Click Save.
3.2.3 Volume Manager

Volume manager is used to configure HDD space for MMSC.
Configuration Management>Volume Manager
The Volume Manager screen is displayed.
Figure 3-15: Volume Manager
Table 8: Field Description of Volume Manager
Mount Path It is the path where the subscribers

have their MM box. The MM box is
similar to an inbox and is used to
store the subscriber’s MM messages.
Each user has a separate MMBOX
created in this folder. The value must
be a valid absolute file path, which
already exists; the volume manager
will not create this path if it is not
present. Example: ./tmp
MMSC Space This is the space used by the MMSC
to store messages for users who are
not subscribed to the system. This
space is also used by the MMSC for
its own internal usage. The value
specified here is appended to the
path specified in 'Mount Path' and
then used. The value must be a valid
file path, which already exists; the
volume manager will not create this
path, if it is not present.
Log File The name of the file where the logs
generated by volume manager are
stored. Example: fs_api.log
To edit volume manager:

 Click Edit.
Figure 3-16: Edit Volume Manager

 Click Save.
3.2.4 Database
The MMSC makes use of the database to store information related to the incoming and
outgoing messages. The user name and password must be entered for authentication
purpose. The following components of the MMSC use the database.
 Default server
 CDR server
 Message dispatcher server
Subscriber server
Configuration Management>Database
The MM Database Configuration screen is displayed.
Figure 3-17: MM Database Manager
Table 9: Field Description of Database
Default Database Server Port The port at which the database is Default: 3306 for MySQL
listening for requests
Default Username The database user name used by
MMSC to connect to the database
Default Password The database password used by
MMSC to authenticate the
username for database connectivity
Default Connection String The unique identifier for connecting

to the database. A valid connect
string should be entered in this field
as improper values may restrict
proper connection setup with the
database
 For MySQL version the connect string should have IP address of the MySQL server appended to
the connect string. Example 127.0.0.1::mydb
To edit database configuration:

 Click Edit.
Figure 3-18: MM Database Configuration-Edit

 Click Save.
3.2.5 Receive CGI Configuration

This is an interface where a request comes first and then it is forwarded to the MMSC.
Configuration Management > Receive CGI
The Receive CGI Configuration screen is displayed.
Figure 3-19: Receive CGI Configuration
Table 10: Field Description of Receive CGI Configuration
Field Description Pre-requisites
Receive Server IP Address This is the IP address of the Example: 127.0.0.1

machine where the MMSC receive
server is running
Receive Server Port It is the TCP port at which receive Example: 18400
server is listening for request. A
default value has been given and it
is recommended that this value not
be changed
Response Wait Time This is the maximum time interval Example: 60
in seconds within which the receive
server must send a response back
to the receive agent, for a single
transaction
Access Correlation Header The name of the HTTP header, Example:
Name which contains the access X_ACCESSCORRELATION
correlation. This is the text string by
which the http server represents
this header
XMSISDN Header Name It is the name of the HTTP header, Example: HTTP_X_MSISDN
which is sent by the WAP gateway
and identifies the subscriber ID
(phone number) of the user. This is
the text string by which the http
server represents this header
XMSISDN Header Value The default value to be sent as part Example: +919800000000
of XMSISDN header value if the
XMSISDN header is missing
HTTP Header Name List The list of header to be sent to the Example: NASIP GGSNIP
receive server. Each header should
be separated by space character
Log Level: Amount of logging that is done in
the log file of the receive agent
application. The following levels are
defined
 Critical
Field Description Pre-requisites
 Warning
 Debug
is recommended.
To configure receive CGI configuration:

 Click Edit.
Figure 3-20: Edit Receive CGI Configuration

 Click Save.
3.2.6 Retrieve CGI Configuration

This is the interface between the retrieve server and the phone. When the user retrieves the
message, the message passes through this interface from MMSC and then to the phone.
Configuration Management>Retrieve CGI Configuration
The Retrieve CGI Configuration screen is displayed.
Figure 3-21: Retrieve CGI Configuration

Table 11: Field Description of Retrieve CGI Configuration
Retrieve Server IP Address It is the IP address where the

retrieve CGI is running. Example:
127.0.0.1
Retrieve Server Port This is the TCP port at which the Example: 18410
MMSC retrieve server is listening
for requests. A default value has
been given and it is recommended
that this value should not be
changed.
Response Wait Time This is the maximum time interval Example: 60
in seconds within which the retrieve
server must send a response back
to the retrieve agent, for a single
transaction
Access Correlation Header The name of the HTTP header, Example:
Name which contains the access X_ACCESSCORRELATION
correlation. This is the text string by
which the HTTP server represents
this header
XMSISDN Header Name It is the name of the HTTP header, Example: HTTP_X_MSISDN
which is sent by the WAP gateway
and identifies the subscriber ID
(phone number) of the user
XMSISDN Header Value The default value to be sent as part Example: +919800000000
of XMSISDN header value, if the
XMSISDN header is missing
HTTP Header Name List The list of header to be sent to the Example: NASIP GGSNIP
retrieve server. Each header
should be separated by space
character
done in the log file of the retrieve
agent application. The following
levels are defined
 Critical
 Warning
 Debug
logging while the debug level gives
is recommended.
To edit retrieve CGI configuration:

 Click Edit.
Figure 3-22: Edit Retrieve CGI Configuration

 Click Save.
3.2.7 Billing
This handles request for pre-paid billing and provides an interface to the Operator’s pre-paid
billing system.
Configuration Management> Billing
The Billing Configuration screen is displayed.
Figure 3-23: Billing Configuration
Table 12: Field Description of Billing Configuration
Billing Server IP Address It is the IP address at which billing Example: 127.0.0.1 or

mediation agent is listening for 10.20.30.40

requests
Billing Server Port It is the port number at which the Example: 18450
billing mediation agent listens for
recommended that this value should
not be changed
Billing Server Receive Timeout It is the timeout in seconds after Example: 30
which the TCP receive call is aborted
and an error is logged. This may arise
sent properly or some fragments are
lost. In that case, instead of making
the billing mediation agent waits
indefinitely for the request, the
receive call is timed out. A value of 4-
5 seconds may be used on a fast
Ethernet, for slower networks (dial-up
lines), a value of 20 seconds is
sufficient
Maximum DB Connections The maximum number of database Example: 5
connections to be established
Charging URL The charging URL to be used for the Example: http://127.0.0.1
billing purpose
Refunding URL The refunding URL to be used for the Example: http://127.0.0.1
billing purpose
Application ID The unique application ID for the Example: 7000
billing purpose
Minimum SN (Serial Number) The minimum SN of the billing server Example: 60000000
Maximum SN The maximum SN of the billing server Example: 70000000
Accept Thread Pool Number of threads that are waiting to Example: 5
receive a billing request. Typical
values must not be more than 10 and
a value of 10 is more than enough to
handle large volumes of traffic
Log File It is the name of the file, which is Example: billing.log
used by the billing mediation agent
for logging the information. However,
when the billing mediation agent is
started, a log file is specified in the
command line parameters, and since
command line parameters have a
higher precedence than parameters
in configuration files, this parameter
may not have effect
Stat File It is the file where the Billing Example: billing.stat
Mediation Agent records some basic
statistics. This information may be
used while displaying statistics and
reports to the administrator
Old Logs Path This is the path where the billing Example: log/old_logs/
mediation agent rotates and stores
the old log files. This parameter can
accept both, relative and absolute
paths. A valid path must be entered in
this field and it is assumed that the

path already exists. The billing
mediation agent will not create the
specified folder, if the path is non-
existent
Log Level The amount of logging that will be Default log level: Debug
Receive/Retrieve Server. The
following levels are defined
 Critical Level
 Warning Level
 Debug Level
The critical level implies least logging
while the debug level gives rise to
maximum logging. A warning level is
the best choice and is recommended.
To edit billing configuration:

 Click Edit.
Figure 3-24: Edit Billing Configuration

 Click Save.
Price Configuration
This feature provides the price information depending on the service type and the size of the
message.
Billing Agent>Price Configuration

The Prices List screen is displayed.
Figure 3-25: Price List
Table 13: Field Description of Price Configuration
Enable/Disable This field specifies the

corresponding price configuration is
enabled or disabled.
Service Type This parameter specifies the
charging is done while sending
message or receiving message or
sending&receiving message.
Name This parameter specifies the name
of the price configuration.
Size This parameter specifies the
minimum and maximum message
sizes separated by hyphen (-).
Rate This parameter specifies the
amount to be charged for a unit.
To delete price list:

 Select the price list.
 Click Delete.
 The DEFAULT named price list cannot be deleted.

To add price list:
 Click Add.
Figure 3-26: Add Price
 Enter the required field values.

 Click Save.
Table 14: Field Description of Add Price
Section Name Name of the price configuration.

Event Type This parameter specifies the event
type of the price configuration.
From MSISDN The MSISDN numbers for which Example: 9198*
the message from this number will
come under this price configuration
To MSISDN The MSISDN numbers for which Example: 66*
the message starting with this
number will come under this price
configuration
Originator Domain The originator domain for the price
configuration.
Destination Domain Destination domain for the price
configuration.
From MSISDN Dont Start MSISDN numbers in the “from”
field of the message, those which
are not starting with this number
will come under this price
configuration.
To MSISDN Don’t Start MSISDN numbers in the “To” field

of the message which are not
starting with this number will come
under this price configuration.
Interface Type Message types for which the price Example: MM1, MM3 and so on
configuration is applied
Minimum Size (Bytes) Minimum message size of the price
configuration.
Maximum Size (Bytes) Maximum message size of the
price configuration.
User Agent User agent for which the price Example: Mobile, Webtop.
configuration is applied
Subject Subject of the message
Prepaid Rate Prepaid rate to be taken for a unit
for this price configuration
Postpaid Rate Postpaid rate to be taken for a unit
for this price configuration
Service Type Charging is done while sending
message or receiving message or
sending&receiving message
Charged Party Charging is done for sender or
receiver
Enable/Disable Corresponding price configuration
is enabled or disabled
To edit price list:

 Click .
Figure 3-27: Edit Price
 It has same fields as the Add Price.

 Edit the required field values.
 Click Save.
Device Configuration
The device-mapping configuration is used to categorize mobile handsets and applications
based on user agents.
Billing Agent>Device Configuration
The Device Mapping List screen is displayed.
Figure 3-28: Device Configuration
Table 15: Field Description of Device Mapping
Device Name The unique device name like

mobile, Webtop, and BMG.
Mapping Value This field is used to define the user
agent value for the handsets and
applications like Sony*, Nokia* and
Samsung.
To delete device mapping list:

 Select the device.
 Click Delete.
To add device configuration:

 Click Add.
The following is the screen is displayed.
Figure 3-29: Add Device Mapping

 Click Save.
To edit device configuration:

 Click .
Figure 3-30: Edit Device Mapping
 It has same fields as the Add Device Mapping.

 The device name cannot be edited.
 Edit the mapping value.

 Click Save.
3.2.8 MMSC Lookup

The domain name system enum helps the administrator to direct the MM message to the
appropriate MMS Proxy Relay. This becomes necessary if the service providers of the sender
and receiver are not the same.
Configuration Management>MMSC Lookup
The DNS Enum Configuration screen is displayed.
Figure 3-31: DNS Enum Configuration
Table 16: Field Description of DNS Configuration
DNS ENUM Server IP Address IP Address at which the DE (DNS Example: 127.0.0.1 or
Enum) server will wait for DNS- 10.20.30.40
ENUM requests
DNS Enum Server Port TCP port at which the DE server Example: 18440
will listen for DNS-ENUM requests.
Only valid port numbers are
allowed. The configuration comes
DNS ENUM Server Receive Timeout in seconds after which the Example: 30
Timeout TCP receive call is aborted and an
error is logged. This may arise
sent properly or some fragments
are lost. In that case, instead of
making the DE server wait
sufficient

waiting to receive a DNS-ENUM
request. Typical values must not be
more than 10 and a value of 10 is
more than enough to handle large
volumes of traffic
Log File It is the name of the log file, which Example: des_server.log
is used by the DE server for
logging of information. However,
when the DE server is started, a
log file is specified in the command
line parameters, and since
command line parameters have a
higher precedence, than
parameters in configuration files,
this parameter may not have effect
Stat File This is the file where the DE server Example: des_server.stat
records some basic statistics. This
information may be used while
displaying statistics and reports to
the administrator
Old Logs Path This is the path where the DE Example: log/old_logs/
server rotates and stores the old
log files. This parameter can accept
both, relative and absolute paths. A
valid path must be entered in this
field and it is assumed that the path
already exists. The DE server will
not create the specified folder, if
the path is non-existent
done in the log file of the DE
server. The following levels are
defined:
 Critical Level
 Warning Level
 Debug Level
is recommended.
DNS Enum Records Defines the static tables that are Example: 9845* mms1.co.in
used by the DE server to make
lookups for DNS-ENUM requests.
An entry consists of two values.
The first value specifies the phone
set of phones. The second value is
the domain name of the phones,
which fall into the category defined
by the first value. The domain
name must be a fully qualified valid
domain name
The above record specifies that the

domain for all phones, which have
the first 4 digits as '9845' is
mms1.co.in.
To edit DNS Enum configuration:

 Click Edit.
Figure 3-32: Edit DNS Enum Configuration
 Edit the field values.

 Click Save.
3.2.9 Provisioning Server

The administrator has the rights to allow certain machines to have an access to the
provisioning server. This can be specified in the provisioning server configuration.
Configuration Management>Provisioning Server
The Provisioning Server configuration screen is displayed.
Figure 3-33: Provisioning Server Configuration
Table 17: Field Description of Provisioning Server Configuration
Server IP Address It is the IP address of the machine Example: 127.0.0.1 or

where the provisioning server is 10.20.30.40
running.
Server Tcp Port It is the port number at which the Example: 18430
provisioning server is listening.
Server UDP Port The UDP port at which the Example: 6666
provisioning server waits for
requests.
Server Receive Timeout It is the timeout in seconds after Example: 30
which the TCP receive call is
aborted and an error is logged.
This may arise when a client
request has not been sent properly
or some fragments are lost. In that
case, instead of making the
receive/retrieve server wait
sufficient.
waiting to receive a request.
Typical values must not be more
than 10 and a value of 10 is more
than enough to handle large
volumes of traffic
Database Server IP Address It is the IP address where the Example: 127.0.0.1
MMSC Database is
installed/running
Database Server Port It is the port number on which the Example: 5432
database communicates
Database Connect String It is the unique identifier for Example: DEMO

connecting to the database. This is
the connect string which is used to
connect to the database. A valid
connect string should be entered in
this field as improper values may
restrict proper connection setup
with the database
Database User The database username and
Name/Password password for accessing the
database must be entered for
authentication purposes.
connection pool to be established
SMS Alert If the flag is set to true, a welcome Example: 1
notification will be sent whenever a
new user is subscribed
SMS Message The content of SMS alert, if the Example: Succeeded
user wants SMS alert after
provisioning
Allowed Client List The administrator has the rights to Example: *
allow certain machines to have an
access to the provisioning server.
This can be specified in the allow
list. The list must consist only of
valid IPv4 addresses, as
hostnames are not supported.
Wildcards, * and ?, are supported.
Multiple values can be specified
and must be separated by at least
one white space. By default, all
clients are allowed to connect
Log File It is the name of the log file, which Example: prov_server.log
is used by the provisioning server
for logging of information. However,
when the provisioning server is
started, a log file is specified in the
command line parameters, and
since command line parameters
have a higher precedence than
parameters in configuration files,
this parameter may not have effect
Old Logs Path This is the path where the Example: log/old_logs/
provisioning server rotates and
stores the old log files. This
parameter can accept both, relative
and absolute paths. A valid path
must be entered in this field and it
is assumed that the path already
exists. The provisioning server will
not create the specified folder, if
the path is non-existent
Log Level The amount of logging that is done
in the log file of the provisioning
server.
 Critical Level
 Warning Level
 Debug Level
is recommended.
LDAP Database Support This specifies whether to enable
the LDAP support or not for the
MM6 interface.
To edit provisioning server configuration:

 Click Edit.
Figure 3-34: Edit Provisioning Server Configuration

 Click Save.
3.2.10 Webtop Interface

The Webtop is used by the subscriber to view the MM messages if the phone is not MM
enabled. This section provides the information needed for the configuring the Webtop
Interface.
Configuration Management > Webtop Interface

The Webtop Interface Configuration screen is displayed.
Figure 3-35: Webtop Interface Configuration
Table 18: Field Description of Webtop Interface
Receive Agent Specifies the fully qualified MMSC Example: http://127.0.0.1/mms/

receive agent URL
Proxy Server IP Address The interface IP address of the Example 192.10.3.44.
proxy server used
Proxy Server Port The port number of proxy server at Example 5001
which it listens for incoming
requests
Allowed IP Addresses The list of IP address allowed to Example: * (indicates all the IP
send MMS via Webtop Interface Addresses)
Retrieve Agent The fully qualified MMSC retrieve Example: http://127.0.0.1/mms/
agent URL
Billing Specifies, the billing is enabled or Example: Enable
disabled
Download Transactions Specifies, the downloading Example: Enable
transactions is enabled or disabled
Database User Name: The user name used to connect to Example MMSC_Database
the database server
Database Password The password used to connect to
the database for the above-
specified user.
Database Connection String The connect string which is used to Example MySQL: 127.0.0.1:
connect to the database. A valid demo

with the database
Log File Name The name of the log file used to log Example. /wt.log
information
in the log file of the mail2mms
defined
 Critical
 Warning
 Debug
is recommended.
LDAP Database Support To enable/disable the LDAP
database support for the MM6
interface
Decode UTF Encoded Subject To decode the UTF encoded
subject. When enabled the UTF
encoded subject will be decoded
otherwise no decoding of the
subject
LDAP IP Address The IP address for the LDAP Example: 127.0.0.1
database. This should be valid IP
LDAP Port The port number of the LDAP Example: 389

database
LDAP Password The LDAP password. This is Example: user

basically for the authentication for
the database usage
LDAP Database Information LDAP database information
LDAP Database Connections Maximum number of connections in

connection pool for LDAP database
To edit Webtop Interface configuration:

 Click Edit.
Figure 3-36: Edit Webtop Interface Configuration

 Click Save.
3.3 Message Dispatcher

Based on the destination user (E-mail, MM enabled or legacy phone user) the different kinds
of message dispatchers (push, E-mail, SMS and application) are used to send the notification.
3.3.1 Push Configuration

The following section explains the push server configuration.
Message Dispatcher>Push Configuration
The PUSH Configuration screen is displayed.
Figure 3-37: PUSH Configuration
Table 19: Field Description of PUSH Configuration
Push Mode The mode to be used for pushing

the messages. Messages can be
pushed using Push Proxy Gateway
(PPG) or by directly connecting to
SMS gateway.
Protocol Type The protocol type whether
CIMD/SMPP to be used while
delivering push message.
Retry Time The time in seconds to wait before Example: 5
resending the already sent push
notifications.
Polling Time The time in seconds to wait before Example: 2
selecting new entries from the
dispatcher database.
Thread Pool The number of threads to be Example: 10

created to dispatch push messages
connections to be initialized
Failover Check Time The time in minutes to wait before Example: 5
resending the notification message,
which are failed in the previous
attempt
Old Logs Directory Path The directory name in which the old Example:./oldlogs/
log files are stored
SMS Message Type The format of the push message.
That is whether the message is
UTF-8(25) or PUSH-OTA(40).
Example: 40
in the log file of the Push
configuration. The following levels
are defined
 Critical Level
 Warning Level
 Debug Level
Default: Debug
is recommended.
Push Configuration (Primary/Secondary Configuration)
PPG Address It is the URL of the push proxy Example: http://ppg-server-
gateway. Push messages are address/ppg
submitted to this URL using the
PAP protocol
Application-Id This is the application-Id of the Example: 7777
message and is used for
authentication of the application
submitting the push message. A
valid value must be obtained from
the PPG configuration and updated
here
Priority It is the priority that is assigned to
the push messages submitted by
the MMSC to the PPG. The
following values are defined.
 Low
 Normal
 High
Push Type This specifies the type of delivery
method the PPG should employ to
deliver the push message. The
Confirmed Push Confirmed pushes are push

messages with a receipt
confirmation sent to the content
provider or application that
originated the push message.
Unconfirmed Push Unconfirmed push messages do
not require a receipt confirmation to
be sent back to the content
provider or application. The
content provider or application can
specify when sending a push
whether the push is unconfirmed or
confirmed.
Bearer Type It is the parameter which decides
the bearer on which message is to
be pushed. The following values
are defined.
 CSD
 SMS
Database Connect String This is the connect string which is Example: DEMO
used to connect to the database. A
valid connect string should be
entered in this field as improper
values may restrict proper
connection setup with the database
Database User Name and The User Name and Password are
Password necessary for authentication
purpose.
SMS Gateway IP Address It is the IP address of the SMS Example: 192.10.2.3
gateway
SMS Gateway Port It is the port on which the SMS Example: 4569
gateway is listening for requests
There are 2 configuration entities for PUSH namely the primary and the secondary
configuration. If the primary configuration fails then the secondary configuration starts
functioning.
To edit push configuration:
 Click Edit.
The configuration screen is displayed.
Figure 3-38: Edit Push Configuration

 Click Save.
3.3.2 SMS Configuration

The SMS configuration contains the following parameters to be configured:
 Common parameters
 Primary database and SMS gateway configuration
 Secondary database and SMS gateway configuration
 Primary PPG configuration
 Secondary PPG configuration
 SMS message content
Message Dispatcher > SMS Configuration
The SMS Configuration screen is displayed.
Figure 3-39: SMS Configuration
Table 20: Field Description of SMS Configuration (Common Parameters)
Submit Mode Specifies whether SMS messages

are submitted via SMS gateway or
PPG.
Protocol Type Specifies which protocol to be used
while submitting message to the
SMS gateway or PPG. The
protocols are: CIMD and SMPP.
Delivery Report It is the flag that tells SMS Example: Enable
dispatcher that it should wait for the
delivery report of SMS message. If
enabled, then the message from
the dispatcher database is
removed only after it gets the
delivery report and it will delete the
message as soon as it delivers the
message to the SMS gateway
Fail Over Service Indicates whether Failover service
has to be enabled or not.
Fail Over IP Service Address The interface IP address at which Example: 127.0.0.1
the Failover service thread is active
Fail Over Service Port The port number at which the Example: 18884
Failover service is listening
SMS Gateway Connection The number of initial connections to Example: 10
Pool be established with SMS gateway
Push Response Timeout The time in seconds to wait for Example: 30
response from the SMS gateway

before closing the connection with
the transaction
Polling Interval The time in seconds of monitor Default: 30
process to monitor the database to
delete the expired messages and
bad requests. It is recommended to
keep the polling interval as 30
seconds for efficient operations
created to dispatch push messages
Fail Over Check Time The time in minutes to wait before Example: 1
sending the notification, which has
failed in the previous submit
Old Logs Directory Path This is the path where the SMS Example:../log/old_logs/
dispatcher rotates and stores the
old log files. This parameter can
paths. A valid path must be entered
in this field and it is assumed that
the path already exists. The SMS
dispatcher will not create the
existent
done in the log file of the SMS
Configuration. The following levels
are defined
 Critical
 Warning
 Debug
warning Level is the best choice
and is recommended.
Scroll down to view the primary and secondary database and SMS gateway configuration
parameters.
Figure 3-40: Database and SMS Configuration- (Contd)
Table 21: Field Description of Primary/Secondary Database and SMS Configuration
SMS Dispatcher Table Name This represents the table name of Default value is
dispatcher database where the "sms_dispatcher"
SMS dispatcher reads the
message. A default value is
provided and it is recommended
that this value is not changed
Database Username The user name of the dispatcher
database
Database Password It is the password for dispatcher
database
Database Connect string This is connection string for the Example: DEMO
database. A valid connect string
should be entered in this field as
improper values may restrict proper
SMS Gateway IP Address The IP address of the machine Example: 127.0.0.1
where the SMS gateway is running.
It must be a valid IPv4 address only
SMS Gateway Port This field represents the port Example: 7788
number where SMS gateway is
listening for messages to dispatch.
The SMS dispatcher will connect to
that port for delivering messages
SMS Gateway Username The username of the SMS gateway
SMS Gateway Password The password of the SMS gateway
Scroll down to view the Primary and Secondary PPG Configuration parameters.
Figure 3-41: PPG Configuration- (Contd)
Table 22: Field Description of Primary and Secondary PPG Configuration
PPG Address This is the URL of PPG (Push Example: http://ppg-server-

Proxy Gateway). Push messages address/ppg
are submitted to this URL using the
PAP protocol. The URL must be a
fully qualified valid URL
Application ID This is the application-ID of the Example: 7777
message and is used for
authentication of the application
submitting the push message. A
valid value must be obtained from
the PPG configuration and updated
here
Priority The priority of the message to be
sent via PPG. The priorities are:
 Low
 Normal
 High
Push Type The type of push message to be
sent. The push types are:
 Pre-confirmed
 Confirmed
 Unconfirmed
Bearer Type The kind of bearer used to deliver
messages. The bearer types are
CSD and SMS.
Protocol Type Specifies whether to use CIMD or
SMPP protocol for delivering

messages
 If the primary configuration fails then the secondary configuration starts functioning.
Scroll down to view the SMS message contents parameters.
Figure 3-42: SMS Message Contents- (contd)
Table 23: Field Description of SMS Message Contents
SMS Message Content Type The list of headers which are to be Example: To: Include
included as part of SMS message.
If a specific header and its
corresponding value is to be
included as part of SMS message
then 'Include' option has to be

selected, else 'Exclude' option
should be selected
Data Coding Scheme The data coding scheme used. The default value is 0 (zero)
This value should be in between 0
to 4
To edit SMS configuration:

 Click Edit.
Figure 3-43: SMS Configuration-Edit

 Click Save.
3.3.3 E-mail Configuration

If the destination user is the E-mail client then the E-mail dispatcher is used.
Message Dispatcher>Email Configuration
The EMAIL Configuration screen is displayed.
Figure 3-44: EMAIL Configuration
Table 24: Field Description of E-mail Configuration

created to dispatch pushes
messages
Polling Time The time in seconds to wait before Example: 5
selecting the new entries from the
dispatcher database
sending the mail that has failed in
the previous submit
SMTP Timeout The time in seconds to wait before Example: 30
sending closing the connection with
SMTP server
Content Disposition The content-type, which should be Example: image/png
sent as inline attachment when
mail is sent
Old Logs Directory Path This is the path where the mail Example: ./logs/oldlogs/
the path already exists. The mail
existent.
done in the log file of the E-mail
configuration. The following levels
are defined
 Critical Level
 Warning Level
 Debug Level
is recommended
SMTP Hostname Host name of the SMTP server Example: hostname
Domain Name Routing Enable domain wise SMTP. When
enabled the domain name wise
routing is done for the mails from
the MMSC
MTA (Mail Transfer Agent) The list of MTA configuration Example: localhost,
List: names for domain wise routing jataayusoft.com
(SMTP). This facility will be
affective only when the "Domain
Name Routing" parameter is
enabled. Configure the MTA list

with the comma (,) separation
SMTP Server IP Address It is the IP Address of the machine Example: 127.0.0.1

where the SMTP server is installed
SMTP Server Port This is the port number where the Example: 25
SMTP server is waiting for requests
Mail Mode The protocol to be used between Example: SMTP
SMTP server and the mail
dispatcher. The mode can either be
SMTP or ESMTP
ESMTP UserName and The user name and password are As such, this field is only
Password: necessary for authentication effective when the Mail Mode is
purposes ESMTP
UserName and UserPassword It is the username and password
for dispatcher database
Database Connect String It is the unique identifier for Example: DEMO
connecting to the database. This is
the connect string which is used to
connect to the database. A valid
with the database
To edit SMS configuration:

 Click Edit.
There are 2 configuration entities for EMAIL namely the primary and the secondary.
 If the primary configuration fails then the secondary configuration starts functioning.
Figure 3-45: Edit EMAIL Configuration

 Click Save.
3.3.4 Application
Click “Application” link to modify the settings for application. This configuration is used for
application-terminated messages.
Message Dispatcher>Application
The Application Terminated Configuration screen is displayed.
Figure 3-46: Application Terminated Configuration
Table 25: Field Description of Application Terminated Configuration
Database Connections The number of database Example: 5.

connection to be initialized.
Thread Pool The number of threads to be Example: 5.
created to dispatch messages
sending the notification, which has
failed in the previous submit
Polling Time: The time in seconds to wait before Example: 3
selecting the next few records from
the dispatcher table
HTTP Basic Authentication Basic authentication is required or

not, if proxy is enabled
HTTP Proxy The specifies whether HTTP proxy

is required or not for AT messages.
If enabled the proxy checking is
done on AT messages
No Proxy For Enter the IP addresses if HTTP
proxy is not required for messages
from these IP addresses. The
multiple IP addresses are
separated by comma (,)
Old Logs Directory Path This is the path where the AT
the path already exists. The AT
existent. Example: ../log/old_logs/
in the log file of the AT dispatcher.
 Critical Level
 Warning Level
 Debug Level
is recommended
Proxy Server IP Address The IP address of the proxy server Example 192.10.3.5.
Proxy Port The port on which the proxy server Example 4500
is listening
Database User Name This is the username that is used Example: username
when connecting to the database.
This is a mechanism, which is used
for authentication by the database.
A valid username must be entered
in this field
Database User Password It is password for the username,
which is used to connect to the
database
Database Connect String This is the connect string which is Example: DEMO
used to connect to the database. A
valid connect string should be
entered in this field as improper
values may restrict proper
To edit application terminated configuration:

 Click Edit.
Figure 3-47: Application Terminated Configuration-Edit
 Modify the field values.

 Click Save.
3.4 Auxiliaries
This section provides the information needed for configuring the Mail Agent.
Auxiliaries
3.4.1 Mail Agent

The feature is used to configure the mail agent which is used by the MMSC to receive mails.
Auxiliaries>Mail Agent
The Mail Agent screen is displayed.
Figure 3-48: Mail Agent Configuration
Table 26: Field Description of Auxiliaries
Receive Agent URL It is the http URL for MMSC relay Example:
server http://127.0.0.1/fcgi/recieve_agen
t.cgi
Secondary Receive Agent The MMSC access point URL to be Example: http://127.0.0.1/mms/
URL used in case primary MMSC
access URL specified is not
responding. It must be a fully
qualified valid URL
Proxy Server IP Address This is the IP address of the proxy Example: 10.20.30.40
server, if the mail agent does not
have direct access to the receive
agent URL
Proxy Server Port It is the port at which the proxy Example: 3128
server is listening for requests
MM3X-MSISDNH Header It is the MSISDN header name that Example: X-MSISDN
Name is used by the MMSC to get the
subscriber’s ID. This is the text
string by which the http server
represents this header
MM3X-MSISDNH Header It is the value of the above- Example: +919800000001
Value mentioned header that is the phone
number
MM3 Bounce Message This specifies whether sending of

Support bounce mail to MM3 message is
enabled or not
MM4 Bounce Message This specifies whether sending of
Support bounce mail to the MM4 message
is enabled or not
Smtp Server IP Address Interface IP address of the SMTP Example: 27.0.0.1
server used for sending mails
Smtp Server Port Port number at which the SMTP Example: 25
server listens for incoming requests
Denied From List The list of users from which the MM Example:
is not allowed. This is used to filter mailerdaemon@mmsc1.com
the message from MM3 interface
based on from address
Denied MMS Message Type The list of MMS message type be Example: MM4_Forward.RES
List not allowed. This is used to filter
the message from MM4 Interface
based on MMS Message Type
Bounce Mail From Address This parameter specifies, the value Example: <MAILER-
of the “From” header sent as part of DAEMON@mmsc.com>
bounce mail
Mail Report Allowed This specifies whether the mail Example yes
message with Content type
“multipart/report” is allowed to
process or not
Generate CDR This specifies whether the CDR for Example: 1
the mail2mms is to be generated or
not. If yes it generates the CDR, in
the path specified by Mail2mms
CDR path
Mail2SMS CDR Path The absolute path and file name for Example:
the file of mail2mms CDR /home/mmsc/mail2mms/mailmm
s.cdr
Max Allowed MM Size The maximum size of the MM Example: 20
message allowed in kilobytes. This
is used to filter message based on
the size of the message
Add Content ID Header This specifies whether to add
content-ID HTTP header if this
header is not present as part of
message
MM3 Message Spooling The temporary directory name Example: /tmp/spool
Directory where incoming mail data is stored.
This value should be valid directory
path.
Delete Spooled Message This specifies whether to delete
spooled mail message from the
temporary directory.
done in the log file of the mail2mms
defined
 Critical
 Warning
 Debug
is recommended.
To edit the mail agent:

 Click Edit.
Figure 3-49: Mail Agent Configuration-Edit

 Click Save.
3.4.2 MM7
This feature describes the configuration parameters of SOAP – MM7 interface of MMSC.
Auxiliaries > MM7 Interface
The MM7 Interface Configuration screen is displayed.
Figure 3-50: MM7 Interface Configuration
Table 27: Field Description of MM7
Receive Agent URL It is the http URL of receive agent Example:

http://127.0.0.1/fcgi/recieve_agen
t.cgi
AT Save Dir This is the directory where all Example: /var/tmp/saved_data
application terminated messages
will be stored
X-MSISDN Header Name It is the name of the HTTP header, Example: X-MSISDN
which contains the MSISDN
number of the client. This is the text
string by which the http server
represents this header
HTTP Basic Authentication This parameter specifies whether
the VAS user is validated against
the MMSC subscriber information
before processing the VAS request
based on the username and
password available in the HTTP
headers
JNDI Support This parameter specifies whether
the servlet container supports JNDI
or not
JNDI Data Source The name of the data source Example: jdbc/TestDB
specified in server.xml of the
servlet engine, which is used to
create database pool
Data Source The name of the data source used Example: For MySQL
to connect to the database using jdbc:mysql:IPADDRESS:PORT/

JDBC DBNAME?user=USERNAME&p
assword=PASSWORD;
MM7 Name Space The name space given for MM7 Example: MM7Interface
MM7 Supported Versions The comma-separated list of MM7 Example:5.6.0,5.3.0,6.5.0,1.0,6.8
version supported by the MM7 .0,6.6.0,6.5.0,6.4.0,6.3.0,5.10.0,5
Interface .8.0,5.5.0
MMSC Max Request The maximum number to MMS Example: 10
request sent to MMSC at a time
IP Based Authentication The authentication of VAS user
depending on the IP. This is only
for the MM7 interface. This
authentication can be used for all
types of submit requests. It should
be enabled to make use of IP
based authentication
Allowed IP The IP’s, which are allowed for Example: 192.10.3.62,
authentication. Enter the IP's with 192.10.3.120, 127.0.0.1
comma separation
To edit MM7:
 Click Edit.
Figure 3-51: Edit MM7 Interface Configuration

 Click Save.
3.4.3 Auxiliaries Configuration

The auxiliary’s configuration is the configurations of MM3 and MM7 IP address, port,
adminpath and installation paths. This section provides the facility to change the auxiliaries’
configuration.
Auxiliaries>Auxiliaries Configuration
The Auxiliaries Configuration screen is displayed.
Figure 3-52: Auxiliaries Configuration
Table 28: Field Description of Auxiliaries Configuration
MM3 IP Address MM3 IP address is the IP where Example 192.10.3.124

the MM3 interface of the MMSC
server is installed
MM3 Port MM3 port is the port where the
MM3 interface of the MMSC server
is listening.
MM3 Adminpath MM3 admin path is the alias path of
the admin module installed at the
machine where MM3 interface of
the MMSC server is installed
MM3 Installation Path MM3 installation path is the Example:
absolute installation path of the adminmodule/adminmodule
MM3 interface on the machine
where the MM3 interface of the
MMSC server is installed
MM7 IP Address MM7 IP address is the IP address Example 192.10.3.124.
MMSC server is installed
MM7 Port MM7 port is the port where the
MM7 interface of the MMSC server
is listening
MM7 Adminpath MM7 admin path is the alias path of
the admin module installed at the
machine where MM7 interface of
the MMSC server is installed
MM7 Installation Path MM7 installation path is the
absolute installation path of the
MM7Interface on the machine
MMSC server is installed.
To edit the auxiliaries:

 Click Edit.
Figure 3-53: Auxiliaires Configuration - Edit

 Click Save.
3.5 Status Manager

The status of the selected server instance with its components can be viewed using this
feature. If the services are not running, then you can start the server from this page.
Status Manager
The Status Manager screen is displayed.
Figure 3-54: Status Manager
To start the corresponding MMSC service:

 Click Start
To stop the corresponding services running:

 Click Stop
To restart the corresponding services:

 Click Restart.
3.6 Subscriber Manager - Provisioning

This option helps you to provision a user or application/content provider.
Subscriber Manager
3.6.1 Add Subscribers

The administrator can register a subscriber to the MMSC.
Subscriber Manager>Provisioning>Add Subscribers
The Subscriber Registration screen is displayed.
Figure 3-55: Subscriber Registration
Table 29: Field Description of Subscriber Registration (Add Subscriber)
User Name This is the mobile number of the Example: 9845012345

subscriber. Every user shall be

distinguished by unique user name
(MSISDN/ IMSI/ VASID)
Password The password to be set for the
above username.
Email ID The E-mail ID of the subscriber Example: hr@jataayusoft.com
Service Name This is the service ID, which
assigns some defined properties to
subscriber. For every username a
service must exist that has
reference to service ID in the class
table. A service could be defined
based on following attributes,
 service ID
 volume (1 MB default)
 service options
 type of billing.
Subscriber Type The subscriber type can be phone Example: Phone User
user, partially MMS capable, VAS
user or mail user
MMS Service To send and receive MMS you Example: Enabled
need to enable this parameter.
Users can enable/disable the MMS
service
User MMBOX Size This parameter specifies the Example: 1024
registered user multimedia
message inbox size in terms of
Kilobytes
VASP ID It is the ID of the value added
service provided by the service
provider (or by some other service).
If the subscriber type is VAS then
VASP ID and VAS URL information
must be present. Example: 8888
VASP URL It is the URL of the VASP, which
allows the destination client to
determine the sender of a VAS
message. VASP
URL = http://127.0.0.1:8080/soap/
servlet/Messagerouter|MM7interfac
e|DeliverRequest|DeliverRequest|D
eliverRequest
Distribution List This is a list of number to which the Example: 919880112345,919880
message has to be distributed 123456
Law Intercept This parameter specifies a list of Example: 919880112345,
number, which is to be traced 919880123456
VAS Message Class Allowed This specifies the message class
that is allowed for the particular
VAS. If specified, only messages
with these message classes shall
be allowed. Currently this field can
only take three values - personal,
informational, advertisement. Valid
only for VAS Users.
Allowed Content Type(s) This specifies the list of content Example: text/plain, image/png ,
type(s) allowed to send and receive audio/mid
by the subscriber
Restricted Content Type(s) This specifies the list of content Example: application/word
type(s) not allowed to send and
receive by the subscriber
To add the subscriber:

 Click Add.
3.6.2 Edit Subscriber

This links helps you to edit the subscriber details.
Subscriber Manager>Provisioning>Edit Subscriber
The Edit Subscriber screen is displayed.
Figure 3-56: Edit Subscriber
 Enter the username.

 Click Search.
Figure 3-57: Subscriber List
Table 30: Field Description of Subscriber Registration
Username This is the mobile number of the Example: 9845012345

subscriber. Every user shall be
distinguished by unique user name
(MSISDN/ IMSI/ VASID)
Password The alphanumeric string to
authenticate the username
Email Id E-mail ID of the user
Service Name The service type used by the user
as postpaid or prepaid
Subscriber Type This parameter specifies the
subscriber type: The different
subscriber types are:
Phone user
Partially MMS capable
VAS User
Non-MMS User
Mail User
Brew User
WAP Phone
Allowed Content Type The content types, which the user
is allowed to send, are configured
using this parameter
Restricted Content Type The content types, which the user
is restricted to send, are configured
using this parameter
 Scroll horizontally to view the rest of the parameters.

To edit the subscriber details:
 Click .
Figure 3-58: Subscriber List-Edit
It has the same fields as the Add Subscriber screen.

 Click Save.
3 . 7 S u bs c r i b e r M an a ge r - B l a c k & W h it e S u b sc r i b e r L i s t
This section provides the information required for setting up global level black and white list
subscribers. Black subscribers are the one who are not permitted to send the MMS.
Subscriber Manager>Black & White Subscribers
3.7.1 Add Subscribers

This link allows you to configure black and white subscriber.
Subscriber Manager>Black & White Subscribers>Add Subscriber
The Black & White Subscriber Registration screen is displayed.
Figure 3-59: Black and White Subscribers-Add
Table 31: Field Description of Black & White Subscriber Registration
Username The user name can be MSISDN/ Example:

IMSI/ VASID and user can specify Username = 9845012345
group of users using wildcard Username = 9845*
character '*'
Type These subscription types are used Example: Subscriber type = MO-
to allow and deny incoming & Black
outgoing messages.
Mobile Originator Black (MO-
Black): User is not able to send any
messages.
Mobile Originator White (MO-
White): User is able to send
messages.
Mobile Terminator Black (MT-
Black): User is not able to receive
any messages.
Mobile Terminator White (MT-
White): User able to receive
messages
To add the subscriber:

 Click Add.
3.7.2 Edit Subscribers

This links allows you to edit the subscriber details.
Subscriber Manager>Black & White Subscribers>Edit Subscriber
The Edit Black & White Subscriber screen is displayed.
Figure 3-60: Black and White Subscribers-Search
To edit the subscriber:

 Enter the username of the subscriber you want to edit. If you are not sure of the
username, type “*”.
 Click Search.
Figure 3-61: Black and White Subscribers List
 Click .
Figure 3-62: Black and White Subscribers-Edit
The username cannot be edited.

 Edit the subscriber type.
 Click Save.
3.8 Subscriber Manager-Services

This option helps you to configure the services. The services can include the blocking of
particular numbers from receiving MM, allowing or denying MM for the configured services
etc. The service options are defined below.
Subscriber Manager>Services
The Service List screen is displayed.
Figure 3-63: Service List
Table 32: Field Description of Service List
Service ID The service ID by which this service

will be identified. The service ID is
given as a link with the help of which
administrator can view the details of
that service
Service Name The name of service
Allowed Volume The allowed user MMBOX size in
kilobytes
Billing Type The billing method used for the user Example: Prepaid or Postpaid
belonging to this service
 The services with id 1 and 2 cannot be deleted.

To add the service:

Click Add.
The Add Service screen is displayed.
Figure 3-64: Add Service
Table 33: Field Description of Add Service
Service ID This parameter specifies the service

ID by which this service will be
identified. The service ID is given as
a link with the help of which
administrator can view the details of
that service
Black/White List Service The subscriber is allowed to specify
list of users from whom you do not
want to receive MM or want to
receive MM even though the user is
specified in the black list
MO Copy Service If enabled, the subscriber is allowed
to specify the list of users you want to
copy the sent MM. If disabled, this
option is not available to subscriber
MT Copy Service If enabled, the subscriber is allowed
copy the received MM to. If disabled,
this option is not available to
subscriber
MO Allowed If enabled, the subscriber is allowed
to send MM. If disabled, this option is
not available to subscriber
MT Allowed If enabled, the subscriber is allowed
to receive MM. If disabled, this option
is not available to subscriber
MT Forward Service If enabled, the subscriber is allowed
forward the received MM. If disabled,
subscriber
Legacy Support If enabled, the subscriber’s expired
messages will be sent to the mail
address. If disabled, this service is
PPG Service If enabled, the subscriber is allowed
to send the messages through the
multiple PPG’s. If disabled, the
default PPG is used
Distribution Service If enabled, the subscriber is allowed
to specify the distribution list, which
consists of users to which the MM
has to be sent if the group name is
specified in the To/Cc/Bcc list of
sending list. It is an alias for group of
users. If disabled, this option is not
available to subscribers.
Premium Content Access If enabled, the subscriber is allowed
to access the contents provided by
content providers (premium contents)
in addition to the public contents
(non-premium contents) from the
public gallery of WebTop. If disabled,

the subscriber is allowed to access
only non-premium contents.
Future Delivery Service If enabled, the subscriber is allowed
to use the future delivery option for
MM from your handset. If disabled,
this option is not allowed to
subscribers.

 Click Save.
3.9 Subscriber Manager-PPG

This option helps you to configure the PPG for submission of mms notification to the user.
Using this configuration you can create list of push proxy gateway, which can be used in
services configured above.
Subscriber Manager>PPG
The PPG List screen is displayed.
Figure 3-65: PPG List
Table 34: Field Description of PPG List
PPG ID The PPG-ID

Application ID The application-ID of the message
and is used for authentication of
the application submitting the push
message. A valid value must be
obtained from the PPG
configuration and updated here
Primary URL The primary URL of the PPG. This
is an mandatory field
Secondary URL The secondary URL of the PPG.
This is optional field
Push Type The type of delivery method the
PPG should employ to deliver the
push message. The following
values are defined.
 Confirmed Push
 Prefer Confirmed Push
 Unconfirmed Push
Bearer Type The bearer on which push
message is to be pushed. The
 CSD
 SMS
Priority The priority of the push message.
The following values are defined.
 Low
 Normal
 High
To add PPG:
 Click Add.
The Add PPG screen is displayed.
Figure 3-66: Add PPG

 Click Save.
To edit PPG
 Click .
The Edit PPG screen is displayed.
Figure 3-67: Edit PPG
 The PPG ID field cannot be edited. It has same fields as Add PPG screen.
 Enter the values
 Click Save
3.10 Subscriber Manager-Search Utilit y

This section is used to view the services provided to the subscribers. You can search the
subscriber’s based on the services and content type allowed or denied.
Subscriber Manager>Search Utility
3.10.1 Services List

This section specifies the service options enabled/ disabled for the service class. Following
are the service options available.
Subscriber Manager>Search Utility>Services List
The Subscriber Manager screen is displayed.
Figure 3-68: Service Options
Table 35: Field Description of Service Options
Black/White List Service If enabled the subscriber is allowed

to specify list of users from which
he/she does not want to receive
MM or wants to receive MM, even
though the user is specified in the
black list
MO Copy Service If enabled, the subscriber is
allowed to specify the list of users
he/she wants to copy the sent MM.
If disabled, this option is not
available to subscriber
MT Copy Service If enabled, the subscriber is
he/she wants to copy the received
MM to. If disabled, this option is not
available to subscriber
MO Allowed If enabled, the subscriber is
allowed to send MM. If disabled,
subscriber
MT Allowed If enabled, the subscriber is
allowed to receive MM. If disabled,
subscriber
Mobile Originate Max Size If enabled, the subscriber is
allowed to send message of
specified size in the mobile
originate max size. If disabled, this
service is not available to
subscriber
Mobile Terminate Max Size If enabled, the subscriber is
allowed to receive message of
specified size in the mobile
terminate max size. If disabled, this
service is not available to
subscriber
MT Forward Service If enabled, the subscriber is
he/she wants to forward the
received MM. If disabled, this
option is not available to subscriber
Legacy Support If enabled, the subscriber expired
messages will be send to the mail
address. If disabled, this service is
PPG Service If enabled, the subscriber is
allowed to send the messages
through the multiple PPG’s. If
disabled, the default PPG is used
Distribution Service If enabled, the subscriber is
allowed to specify The distribution
list, which consists of users to
which the MM has to be sent if the
group name is specified in the

To/Cc/Bcc list of sending list. It is
an alias for group of users. If
disabled, this option is not available
to subscribers
Premium Content Access If enabled, the subscriber is
allowed to access the contents
provided by content providers
(premium contents) in addition to
the public contents (non-premium
contents) from the public gallery of
WebTop. If disabled, the subscriber
is allowed to access only non-
premium contents
Future Delivery Service If enabled, the subscriber is
allowed to use the future delivery
option for MM from his/her handset.
If disabled, this option is not
allowed to subscribers.
To view the service list:

 Select the service options.
 Click Search.
Figure 3-69: Service List Search Result
 The selected service options are displayed as result.

3.10.2 Subscriber List – With Services
This option helps you to display the service options enabled/ disabled for the subscriber name
specified in the text box. You can search the subscriber’s with the specific services type.
Subscriber Manager>Search Utility>With Services
Figure 3-70: Subscriber’s List-With Service List
To view the subscriber list:

 Enter the user name. It can be MSISDN/ IMSI/ VASID and user can specify group
of users using wildcard character '*'. Example: 9845012345, 9845*.
 Select the Service Options.
 Click Search.
The following the screen is displayed. The selected service options are displayed as result.
Figure 3-71: Subscriber’s List Result-With Service
3.10.3 Subscriber List – With Content Format

This option helps you to search the subscribers based on the content types.
Subscriber Manager>Search Utility>With Content Format
Figure 3-72: Subscriber’s List-Content Format
To view the subscriber list:

 Enter the user name. The user name can be MSISDN/ IMSI/ VASID and user can
specify group of users using wildcard character '*' to filter the list of subscribers
who have the specified content formats. Example: 9845012345, 9845*.
 Select the Content Format.
 Click Search.
The following the screen is displayed.
Figure 3-73: Subscriber’s List Result- Content Format
3.11 Statistics Manager

A reporting service logs transaction events. This data enables the generation of various types
of reports.
With the data-mining results, reports can be generated on a daily, weekly, or monthly basis.
Compiling transaction and performance data for a fixed period of time can also generate
reports. Generated reports stored for an arbitrary period can be used to generate historical
trend reports.
The MMS statistics reporting tool uses server log files and LDAP information in the directory
to return a variety of useful reports on account information, message statistics, number of
each type of device used, and number of each type of media used in messages.
The statistics gives the overview of the resource with respect to the MMSC components.
Using this statistics you can monitor MMSC for smoother functioning. The status (running or
not) of the components, memory usage, and CPU usage and disk space can be viewed here.
Statistics Manager
Figure 3-74: Statistics Manager
Table 36: Field Description of MMSC Statistics
Server The name of the MMSC server

component
Status The status of the server Example: Running
components
Process ID This is the process ID of the
respective process
Memory Usage Utilization of the RAM by the
respective server component
process
CPU Usage Utilization of the available
processor unit by server
component process
Total Memory Usage Utilization of the RAM by the parent
and child process
Total CPU Usage Utilization of the available
processor unit both by child and
parent
Total Disk Space Used The total disk space used by all the

processes
Total Disk space Free The total disk space free
3.11.1 Statistics Reports

To view Statistics reports
Statistics Manager>Statistics Reports
Figure 3-75: Statistic Reports
Report based on Phone Number

This report gives the information of MM messages sent, MM messages failed, MM messages
pending, MM messages forwarded, reply charged MM messages sent, reply charged MM
messages accessed, priority of messages, delivery report requested, read reply requested of
particular user.
Statistics Manager>Statistics Reports>Get user info based on originating phone
number/destination phone number
Figure 3-76: Get User info based on phone number
To view report
 Enter the user name with the country code. The username will be the mobile
number of the user. Example: 919880176768.
 Click OK.
 The username should not have any special characters like + before the number and also any
spaces.
The following result screen is displayed.
Figure 3-77: User Information report based on phone number
Top n Users
This report gives the information of top senders and top receivers based on the number of
mm messages sent or received.
Statistics Manager>Statistics Reports>Top n user’s accessing the system depending
on number of mms sent/received
Figure 3-78: Top n Users
1. Click Next to view the next set of results.

2. Click Back to navigate to the previous results.
Top n MMS
This report gives the information of messages based on the size of the message.
Statistics Manager>Statistics Reports>Top n mms messages accessed depending on
size
Figure 3-79: Top n MMS input criteria
Table 37: Field Description of Top n MMS
Size The size of the message

Above/Below The criteria defines the size of the Size should be specified to select
message (Above the specified size this option
or below)
Sent/Received Message The sent or received message
To view report:
 Click OK.
Figure 3-80: Top n MMS result
Table 38: Field Description of Top n MMS Results
MM Message sender The mobile number of the sender

MM Message receiver The mobile number o the receiver
of the message
MM Message size The size of the message sent or
received
Message Class
For the sent or received MM, user can define the attributes like personal message,
advertisement or Informational.
 Personal: A typical phone-to-phone MMS message. One user sending a personal
message to another user.
 Advertisement: A message that contains an advertisement. Example banks
describing new schemes or sale from some departmental store and so on.
 Informational: This is an application-generated message that is not an
advertisement. For example, football results that a user receives for being
subscribed to a sports information service.
 Auto: This is the application generated message like read report, delivery report
and so on assumption is that this would be for a system generated message. as
an example, perhaps for some information regarding the user's account with the
service provider.
Statistics Manager>Statistics Reports>Message Class
Figure 3-81: Message Class
3 .1 2 Us ag e Re p o rts
The feature is used to view the reports defined for specified period (from and to date) over
various criteria (the user agent, originate domain) for MMSC usage.
Statistics Manager>Usage Reports
Figure 3-82: Usage Reports
Period over Service

pending in a definite period for given interface and given service.
Statistics Manager>Usage Reports>Defined Period Over Service
Figure 3-83: Defined Period Over Service

To view report:
 Select the period from when the report is to be generated in From Date.
 Select the period till when the report is to be generated in To Date.
 Select the interface and service.
 Click OK.
The Statistics Manager screen is displayed.
Figure 3-84: Defined Period Over Service-Report
Table 39: Field Description of Define Period over Service-Report
Timestamp Date and time of the message sent

Message ID Unique number which identifies the
message
Originator Specifies sender address
Recipient The receiver address
Record Type The status of the message
 Click Next to view the next set of results.

 Click Export to download the report to your local disk.
Period over User Agent

pending in a definite period for given user agent.
Statistics Manager>Usage Reports>Define Period Over UserAgent

Figure 3-85: Defined Period Over User Agent
To view report:
 Enter the user agent name (like the Nokia, Mozilla).
 Click OK.
Figure 3-86: Defined Period Over User Agent-Report
 The field description is the same as that for the Period Over Service result screen.
Period Over Originate Domain
pending in a definite period for given originate domain.
Statistics Manager>Usage Reports>Define Period Over Originate Domain

Figure 3-87: Defined Period Over Originate Domain
To view report:
 Enter the Originate Domain (from where the messages where sent).
 Click OK.
Figure 3-88: Defined Period Over Originate Domain-Report
Period Over Terminate Domain
pending in a definite period for given terminate domain.
Statistics Manager>Usage Reports>Define Period Over Terminate Domain

Figure 3-89: Defined Period Over Terminate Domain
To view report:
 Enter the terminate domain ((like the yahoo, rediff).
 Click OK.
Figure 3-90: Defined Period Over Terminate Domain-Report
Successful/Fail Rate, Throughput, Average Message
This report gives the information of MM messages success/fail count, total record of success
and failure and the success rate for a definite period.
Statistics Manager>Usage Reports> Defined Period Success/Fail Rate, Throughput,
Average Message Size

Figure 3-91: Success/Fail Rate
To view report:
1. Select the period from when the report is to be generated in From Date.
2. Select the period till when the report is to be generated in To Date.
3. Select the graph type. This is used for selecting the type of graph depending
on the system administrator requirement.
i. All: Graph for submit and retrieve (both the cases)
ii. Submit: Graph for Submit only
iii. Retrieve: Graph for Retrieve only
4. Click OK.
Figure 3-92: Success/Fail Rate-Report
Success/Fail Rate in MO
This report gives the information of MM Messages success/fail rate for a definite period and
for given status like the service denied messages (service_denied), message submitted
successfully (Ok) and so on. Enter the From and To date and select the status. You can
select more than one status by holding the control key and selecting the parameters.

Statistics Manager>Usage Reports> Defined Period Success/Fail Rate in MO

Figure 3-93: Success/Fail Rate in MO
To view report:
 Select the status. You can select the multiple statuses.
 Click OK.
Figure 3-94: Success/Fail Rate in MO-Report
Defined Period Over IOT
This statistics gives the information of the defined period of interoperability test.
Statistics Manager>Usage Reports> Defined Period over IOT

Figure 3-95: Defined Period over IOT
To view report:
 Enter the username.
 Click OK.
Figure 3-96: Defined Period over IOT-Reports
Number of Messages in the Range of Size

This section gives the information of the number of messages having the message size in the
range 0-10,11-30,31-50,51-100 and 100-above.
Statistics Manager>Number of Messages in the Range Size

Figure 3-97: Number of Messages in Range of Size
To view report:
 Click OK.
Figure 3-98: Number of Message in Range of Size-Reports
Table 40: Field Description of Number of Messages in the Range Size
Message Size Range (KB) This parameter specifies the size

range of the message
Number of messages The total number of message sent
or received for different size ranges
Graphs
This option gives the information about the performance of the MMSC in terms of graph.
Statistics Manager>Graph

Figure 3-99: Graphs
The following are the different types of graphs displayed.

 MMS to MMS Success graph: This graph displays the number of MMS sent
successfully to the MMS destination client.
 MMS to MMS Failure graph: This graph displays number of MMS failed, while
sending from MMS client to the destination MMS client.
 MMS to MAIL Success graph: This graph displays number of MMS sent
successfully from MMS client to the MAIL client.
 MMS to MAIL Failure graph: This graph displays number of MMS failed, while
sending from MMS client to the MAIL client.
3.12.1 Configuration
The number of rows to display the results for the generated reports can be defined here.
Example: 10. This means you can view 10 rows of results in a single page.
Statistics Manager>Configuration
The Reports Configuration screen is displayed.
Figure 3-100: Reports Configuration
To edit the configuration:

 Click Edit.

Figure 3-101: Edit Reports Configuration
 Enter the value in Row to Display field.

 Click Save.
3.13 Message Manager

Message Manager is used to identify the message originated or terminated for a particular
user in a particular time. This is used for tracing whether the user has submitted the message
and notification has sent for that user or not and so on. When user sends MMS from mail
account we can trace that information also.
Message Manager
Figure 3-102: Message Manager - MMSC
3.13.1 Message Trace-MMSC

This section provides the functionality to trace the messages and it provides the information of
the message status. Data can be analyzed using the message tracing tool and reports can be
generated using the MMS statistics reporting tool.
Message Manager>Message Trace>MMSC

Figure 3-103: Message Manager - MMSC
Table 41: Field Description of Message Trace-MMSC
Originator Address This is the identification of the Example: 919886366369, 91988

subscriber who sends the 6.
message. Country code should be
provided along with the originator
address
Recipient Address This is the identification of the Example: 919886366369 ,
subscriber who received the 919886
message. Country code should be
provided along with the recipient
address
MMSC Time Zone MMSC time zone specifies the
system time of the MMSC where it
is running.
Local Time Zone Local time zone represents the
time zone, which we need to
convert the timestamp to local time
zone.
To view the report:

 Click Submit.

Figure 3-104: Message Manager-MMSC-Report
To view the next set of records:

 Click Next.
To download the records in CVS format:

 Click Export.
Figure 3-105: Message Manager- Export MMSC Configuration
To save the report:

 Click Save.
To open the report without saving:

 Click Open.
3.13.2 MMSC Log

This option is used to view the log generated by the user on that particular day.
Message Manager>MMSC Log

Figure 3-106: MMSC LOG
Table 42: Field Description of MMSC Log
Originator Address Originator address is the Example:

identification of the subscriber who 919886366369, 919886968606
sends the message
On Date The date for which you want to see

the logs of subscriber. The date
has to be selected from the
calendar. The date should be either
present date or previous date and it
should not be future date.
Log Type Log type specifies the type of log
user wants to see for the particular
subscriber. It can be either receive
log or retrieve log
To view the report:

 Click Submit.
3.13.3 MM3
This feature is used to trace the messages and view information of the MM3 message status.
Message Manager>MM3

Figure 3-107: Message Manager-MM3
Table 43: Field Description of MM3
Originator Address This is the address of the e-mail Example:

user. Here you can provide mmsc@jataayusoft.com, jata
either originator address or ayu, mmsc
recipient address or the sub
string of the originator address
Recipient Address This is the identification of the Example:
subscriber who received the 9845012345@domainname.c
message. You can also provide om
the sub string of the recipient
address
Read from This parameter specifies from
where the records have to be
read. The records can be read
from Maillog or CDR.
Mail Log refers to the records
from the log files, which is
written by qmail.
CDR option refers to trace the
messages from the CDR files,
which is written by mail2mms
binary file
MMSC Time Zone MMSC Time Zone represents
the GMT time of that MMSC
running
Local Time Zone Local Time Zone represents the
time zone, which we need to
convert the timestamp of
message to display
To view the report:

 Click Submit.

Figure 3-108: Message Manager-MM3 Report
 To view the next set of records, click Next.

 To download the records in cvs format, click Export.
Figure 3-109: Message Manager- Export MM3 Configuration
To save the report:

 Click Save.
To open the report without saving:

 Click Open.

3.14 Configuration
This section provides the facility to change the MMSC and MM3 configuration.
Configuration
Figure 3-110: MMSC Message Trace Configuration
Table 44: Field Description of Configuration
Rows To Display This is the number of rows of

results to be displayed in a single
page. This number should be
greater than 0 and less than 1000.
This parameter is configurable for
MMSC messages and MM3
messages
Log File Path This is the absolute path of the log Example: /var/log/maillog
file in which the qmail generates
the logs for mm3 messages
CDR File Path This file path is the absolute path of Example: /var/log/maillog
the CDR file in which the mail2mms
generate the CDRs for
mm3messages
To edit the configuration:

 Click Edit.

Figure 3-111: Message Manager-Edit MM3 and MMSC Configuration

 Click Save.
3.15 User Manager

This section lists all the users of this server and provides the information needed for creating,
modifying and deleting user accounts for administering MMSC service.
User Manager
Figure 3-112: User Manager
To add a new user:

 Click New.

Figure 3-113: Add User
Table 45: Field Description of User Manager
Field Description Default/Examples
Username This parameter specifies the name Example: user1

of the user to be created
Password This parameter specifies the Example: xyz
password to be used to access the
above username account
Instance Management This field helps you to set the
permissions for the user
Instance Specific
Instance Select the instance name to assign
the access rights
The following configuration is
instance specific, which you have
chosen in the previous field. These
fields specify the permissions for
the following services:
 Server Management
 Configuration Management
 Dispatcher Management
 Provisioning Management
 Black & White Subscriber

Field Description Default/Examples

Management
 Auxiliaries Management
 User Management
 Statistics Management
 Reports Management
 Message Trace Management

The permission that can be
assigned are:
 Read Permission: Only the

services can be viewed.
 ReadWrite Permission: The

services can be edited.
 None: No access to this

service.

 Click Add.
Figure 3-114: User Added -Confirmation
To edit the user:

 Click Edit.

Figure 3-115: Edit User
 It has the same fields as add user.

 The Username cannot be edited.
 Click Update.

Appendix A — MMSC CDRs
Table 46: MMSC CDR Fields
Field Name Definition Contraint Description
MMSVersion The MMS version of the

recipient MMS server
Access Correlation The unique identifier Required BLANK

delivered by the used
access network domain
of the originator MMS
User agent.
Acknowledgement Request It is the Message Required for MM4 [1/0]

acknowledgement forward
request from the client.
Timestamp It is the time when the Required

CDR is generated.
Charge Information This gives the charging [charge-id]:[charge-

information set by the type]
service provider to a
particular client during charge-id
his registration. 1 :– charge
0 :– no-charge
charge-type
1 – normal
2 – prepaid
Content Type This field gives the Required
message content type.
Example: Image/jpeg.
DeliveryReportRequested If the delivery report Required [1/0]

request comes from the
mobile client then this
field is set.
DurationOfTransmission This field stores the

total time taken to
deliver the message by
MMSC.
EarliestTimeOfDelivery The time when the

message is delivered.
Forward Counter The counter indicating

the number of times the
particular MM was
forwarded.
Appendix A — MMSC CDRs 121

Forwarding Address This is the address(es)

of the forwarding mms
user agent.
LocalRecordSeqNo Consecutive record [no of lakhs].[sequence

number created by this no]
node. The number is
allocated sequentially
including all CDR types.
Message Class It is the class of Personal (= default),

message, which will be
downloaded. Advertisement
Information
MessageID This is the unique ID Unique, Required

given to each message
transacted through
MMSC.
MessageReferenece This is the encrypted

path of File System
where message has
been stored.
Message Size The size of the MM

content.
MMComponentList This is the List of the BLANK

media components with
volume size.
OriginatorAddress The phone/IP Address

of the client who
originated the request.
OriginatorMMSServer If message is coming Required

from same or other
MMSC then the domain
name of MMSC will be
stored.
Priority Message Priority Low

Medium
High
ReadReplyRequested If the client is sending Required

MM with Read Reply
request then the field


will be set.
Status DEFINED BELOW

RecepientAddressList The recipient address. Addresses separated
by semi-colon (;)
RecepientMMSServer If request is being sent Required field for

to same or other MMSC MM4
then the domain name
of the MMSC will be
stored.
Record Extension A set of BLANK

network/manufacturer
specific extensions to
the record.
Record Type MMSC can get many Required DEFINED BELOW

type of request like
Acknowledgement,
notification indication
and so on. This field is
being used to store the
message type and also
known as Record Type.
Reply Charging This field is set if Read [1/0]

Reply request is being
charged by the Service
Provider.
ReplyChargingID The unique ID given to

the message.
ReplyChargingSize In The Originator MM!

Submission CDR this
parameter indicates
whether the originator
MMS User Agent has
requested reply-
charging (value TRUE)
or not (value FALSE). In
the Recipient MM1
notification request
record it indicates a
whether reply to this
particular original MM is
free of charge.
Reply Deadline In the Originator MM1
submission CDR in
case of reply-charging,
this field indicates the
latest time of
submission of replies
granted to the recipient
as specified by the


originator MMS User
Agent. In the recipient
MM1 notification
request CDR,in case
ofreply-charging,this
filed indicates the latest
time of submission of a
reply granted to the
recipient as specified in
the
MM1_notification.REQ.
Sender Visibility This Boolean value [1/0]

indicates whether the
originator MMS User
Agent has requested
her address to be
hidden from the
recipient (Value TRUE)
or (value FALSE)
Status Text Each message status is

associated with a
message text along with
the status CODE.
Submission Time The time when Required field for

message was submitted MM4
to MMSC.
TimeOfExpiry The expiry time for the

message set by the
client.
VASPID ID of the Value Added MM7

service Provider.
Service Code Service Code: MM7

Information supplied by
the VASP, which may
be included in charging
information.
ClientIPPort This field contains the
IP Address and the IP
Port of the client
application that is
transacting with the
MMSC
User Agent This field contains the
HTTP User Agent of the
client application that is
transacting with the
MMSC.
Originating Interface This field provides
information on the
interface that is used for


an MMS transaction
and the handset
attributes of the
originating subscriber
initiating the MMS
transaction.
Terminating Interface This field provides
information on the
recipient related
interface that is used for
an MMS transaction
and the handset
attributes of the
recipient subscriber.
MMSCName This field contains the
name that has been
assigned to an MMSC
instance. This name
shall be defined in the
configuration file of an
MMSC instance.
MMSCServerIP This field contains the
IP address where the
MMSC listens for
incoming requests from
MMS clients. This IP
address shall be
defined in the
MMSC instance.
CDRType This field contains the
billing type of the
subscriber initiating the
transaction with the
MMSC. The values that
shall be present in this
field are as described
below.
0 – Unknown billing
type
1 – Pre-paid subscriber
2 – Post-paid subscriber
ServiceClassID This field contains the

class identifier of the
subscriber who is
initiating the transaction
with the MMSC.
ServiceProviderName This field contains the
name of the
Operator/client who has
installed the MMSC to
provide MMS services.
This value shall be
defined in the
MMSC instance.

Status Value
Table 47: Status Value
Assigned Value Type of Status Explanation
Read Status
1 STATUS_READ
2 STATUS_DELETED_WITHOUT_BEING_READ
Error Status
3 STATUS_OK
4 STATUS_UNSPECIFIED
5 STATUS_SERVICE_DENIED
6 STATUS_MSG_FORMAT_CORRUPT`
7 STATUS_SNDING_ADDR_UNRESOLVED
8 STATUS_MESSAGE_NOT_FOUND
9 STATUS_NW_PROBLEM
10 STATUS_CONTENT_NOT_ACCEPTED
11 STATUS_UNSUPPORTED_MESSAGE
12 STATUS_TRANSIENT_FAILURE
13 TRANSIENT_SENDING_ADDR_UNRESOLVED
14 STATUS_TRANSIENT_MESSAGE_NOT_FOUND
15 STATUS_TRANSIENT_NETWORK_PROBLEM
16 STATUS_PERMANENT_FAILURE
17 STATUS_PERMANENT_SERVICE_DENIED
18 STATUS_PERMANENT_MESSAGE_FORMAT_CO
RRUPT
19 STATUS_PERMANENT_SENDING_ADDRESS_UN
RESOLVED
20 STATUS_PERMANENT_MESSAGE_NOT_FOUND
21 STATUS_PERMANENT_CONTENT_NOT_ACCEP
TED
22 STATUS_PERMANENT_REPLY_CHARGING_LIM_
NOT_MET
23 STATUS_PERMANENT_REPLY_REQUEST_NOT_
ACCEPTED
24 STATUS_PERMANENT_REPLY_CHARGING_FOR
WARDING_DENIED
25 STATUS_PERMANENT_REPLY_CHARGING_NOT
_SUPPORTED
26 STATUS_RETRIEVED
27 STATUS_REJECTED
28 STATUS_EXPIRED
29 STATUS_DEFFERED
30 STATUS_UNRECOGNIZED

Assigned Value Type of Status Explanation
31 STATUS_INDETERMINATE
Record Type Values

Table 48: Field Description of Record Types
Assigned Value Interface Record type
MM1
1 MM1 Submit Request
2 MM1 Submit Response
3 MM1 Notification Request
4 MM1 Notification Response
5 MM1 Retrieve Response
6 MM1 Acknowledgement Request
7 MM1 Forward Request
8 MM1 Forward Response
9 MM1 Delivery Report Request
10 MM1 Read Reply Recipient Request
11 MM1 Read Reply Originator Request
12 MM1 MMBOX Store Request
13 MM1 MMBOX Store Response
14 MM1 MMBOX View Request
15 MM1 MMBOX View Response
16 MM1 MMBOX Upload Request
17 MM1 MMBOX Upload Response
18 MM1 MMBOX Delete Request
19 MM1 MMBOX Delete Response
20 MM4
21 MM4 Forward Request
22 MM4 Forward Response
24 MM4 Delivery Report Response
25 MM4 Read Reply Request
26 MM4 Read Reply Response
MM7
27 MM7 Submit Request
28 MM7 Submit Response
29 MM7 Deliver Request
30 MM7 Deliver Response
31 MM7 Cancel Request
32 MM7 Cancel Response

Assigned Value Interface Record type
33 MM7 Replace Request

34 MM7 Replace Response
36 MM7 Delivery Report Response
37 MM7 Read Reply Request
38 MM7 Read Reply Response
39 MM7 RS Error Request
40 MM7 VASP Error Response

Appendix B — MMSC Directories
The details of all the files that are generated on installation under various sub-directories are
as below:
exe directory
Table 49: Field Description of exe Directory
File Name Description
adaptation_broker This exe takes care of content adaptation functionality of the MMSC
at_dispatcher Notification dispatcher of application terminated messages over the
MM7 interface
des_server Takes care of DNS enumeration functionality of MM4 interface
mail_dispatcher It is the notification dispatcher for the mail messages over the MM3
interface
mediation_server Takes care of the prepaid interface of the MMSC for interaction with the
prepaid network
mmbox_monitor Takes care of CDR generation functionality of MMSC
pi_dispatcher Notification dispatcher for mobile terminated MMS notifications over the
MM1 interface.
prov_server Takes care of the provisioning interface of the MMSC.
recv_server It is the MM1 interface of the MMSC for MO MMS messages.
retr_server It is the MM1 interface of the MMSC for the retrieval of MT MMS
messages.
sms_dispatcher Notification dispatcher for MT SMS notification for legacy phones over
the MM1 interface
Notification_server It is used to handle notification for legacy devices which cannot store
multiple notifications.
conf directory
Table 50: Field Description of Conf Directory
adaptation.conf Configuration file used by adaptation broker server.

at_dispatcher.conf Configuration file used by AT DISPATCHER server
bma.conf Billing mediation server configuration file
database.conf Configuration file used by receive and retrieve server for database
connection information
des.conf DNS-ENUM server configuration file.
dns_enum.conf DNS-ENUM client configuration file.
fs_api.conf It is the configuration for File system path where User MM is stored
mail_dispatcher.conf MAIL DISPATCHER server configuration file.
monitor.conf MMbox monitor configuration file
pi_dispatcher.conf PI DISPATCHER configuration file.
provisioning.conf Configuration file containing provisioning server information.
Appendix B — MMSC Directories 129

prvserver.conf Configuration file used by provisioning server

rcvserver.conf For receive and retrieve server
sms_dispatcher.conf SMS Dispatcher configuration file
user_profile.conf Configuration file for the user profile UI.
userinfo.conf File controlling the access to the admin UI.
uierr.conf Error codes for the UI
fcgi directory
Table 51: Field Description of fcgi Directory
receive_agent.cgi Common Gateway Interface program which connects receive server

receive_agent.conf Configuration file used by receive_agent.cgi application.
retrieve_agent.cgi Common Gateway Interface program which connects retrieve server
retrieve_agent.conf Configuration file used by retrieve_agent.cgi application.
log directory
Table 52: Field Description of log Directory
at_dispatcher.log Log file for the at dispatcher transactions

bma_parent.log Log file for the billing mediation server transactions
des_parent.log Parent Process log file of DNS-ENUM server
dns_server.log Log file generated by the child process of DNS-ENUM server
leatrace.log Log file for tracing Law Enforcement Authority related operations
mail_dispatcher.log Log file generated by the mail dispatcher server
mediation_server.log Log file generated by the mediation server
mmbox_monitor.log Log file generated by the mmbox monitor server
nohup.out System generated file when servers are generated
pi_dispatcher.log Log file for the pi dispatcher transactions
prov.log Log file generated by the provisioning server child process.
prov_parent.log Log file generated by the provisioning server parent process.
rcvs_parent.log Log file generated by the receive server parent process.
recv_server.log Log file for the receive server transactions
retr_server.log Log file for the retrieve server transactions
sms_dispatcher.log Log file for the SMS dispatcher transactions

scripts directory
Table 53: Field Description of Scripts Directory
Table 3: Field Description of scripts directory
configure_control.sh Template file for generating SNMP scripts

mmsc_control.sh SNMP script for MMSC start/stop operations
scripts/health/ directory
Table 54: Field Description of Scripts/Health Directory
Table 4: Field Description of scripts/health directory
health.sh Script file for health monitoring of the MMSC

vmstat_trace.sh Script file for system monitoring
mdata
Under this directory you have the following sub-directory:
 pid
 stat
 trap
mdata/stat/
Table 55: Field Description of mdata/stat Directory
at_dispatcher.stat AT Dispatcher statistics file

des_server.stat DES server statistics file
mail_dispatcher.stat Mail dispatcher statistics file
mediation_server.stat Billing mediation server statistics file
mmbox_monitor.stat MMBox Monitor statistics file
nserver.stat Notification server statistics file
pi_dispatcher.stat PI dispatcher statistics file
prov_server.stat Provisioning server statistics file
recv_server.stat Receive server statistics file
retr_server.stat Retrieve sderver statistics file
sms_dispatcher.stat SMS dispatcher statistics file

mdata/trap/
Table 56: Field Description of mdata/trap Directory
at_dispatcher.trp AT Dispatcher trap file

des_server.trp DES server trap file
mail_dispatcher.trp Mail Dispatcher trap file
mediation_server.trp Billing mediation server trap file
mmbox_monitor.trp MMBox Monitor trap file
nserver.trp Notification server trap file
pi_dispatcher.trp PI dispatcher trap file
prov_server.trp Provisioning server trap file
recv_server.trp Receive server trap file
retr_server.trp Retrieve server trap file
sms_dispatcher.trp SMS dispatcher trap file
gui
The files under this directory are the cgi files used for Web interface.
Table 57: Field Description of gui Directory
Table 5: Field Description of gui directory
INCLUDE This files contains the details of the various directory paths. The screen
below shows the INCLUDE file.

Figure 3-116: Include File
gui/conf
This directory contains the GUI configuration files.
gui/log
This directory contains the logs of the Web interface.

Appendix C — MMSC Traps
S No. Component Trap File Condition Trap name Critical/ Trap String
Name Name Warning
/Info
1 at_dispatcher at_dispatcher.t When AT dispatcher will try to mmsATDispa Info The VAS
rp post the data to application tcherTrap Connectivity is
server. And if it will fail to do Down.
the same.
2 at_dispatcher at_dispatcher.t When, AT dispatcher will try to mmsMaxDB Critical Maximum number
rp init multiple connections to the Connection of database
data base. And if it will fail with connections is
the secondary configuration made.
also due to too many
connections to the database.
3 at_dispatcher at_dispatcher.t When AT dispatcher will try to mmsDBTrap Critical MMSC Database
rp init multiple connections to the Error.
data base. And if it will fail with
the secondary configuration
also.
4 at_dispatcher at_dispatcher.t When AT dispatcher will be mmsATDispa Info Dispatcher for
rp start. tcherTrap sending AT
notifications is
started.
5 at_dispatcher at_dispatcher.t When AT dispatcher will be mmsATDispa Warning Dispatcher for
rp stopped. tcherTrap sending AT
notifications is
stopped.
6 mediation_se mediation_ser When mediation server will be mmsMediatio Info Mediation server
rver ver.trp start. nServerTrap status is running.
7 mediation_se mediation_ser When mediation server will be mmsMediatio Warning Mediation server
rver ver.trp stop. nServerTrap status is stopped.
8 des_server des_server.trp When DES server will be start. mmsDesServ Info DES server
eRTrap started.
9 des_server des_server.trp When DES server will be stop. mmsDesServ Warning DES server
eRTrap stopped.
10 Mail2mms mail_dispatche When Mail2MMS will try to mmsSMTPTr Warning MMSC Mail
r.trp connect with SMTP server & if ap Server Error.
it will fail.
11 Mail2mms mail2mms.trp While mail2mms will try to mmsMail2M Warning Error in Mail to
connect to the receive server MSTrap MMS message
URL by using any one of the sending.
primary & secondary and if it
will fail.
12 mail_disapatc mail_dispatch While mail)dispatcher will mmsESMTP Warning MMSC ESMTP
her er.trp initialize the connection with the Trap Error.
ESMTP server & if it will fail.
13 mail_disapatc mail_dispatch When mail_dispatcher will mmsMaxDB Critical Maximum number

her er.trp initializ the multiple connections Connection of database
to the database using connections is
secondary configuration & error made.
occurred due to too many
connections.
Appendix C — MMSC Traps 135

Name Name Warning
/Info
14 mail_disapatc mail_dispatch While mail_dispatcher will mmsDBTrap Critical MMSC Database

her er.trp initialize the multiple Error.
connections to the database
using secondary configuration
& error occurred in making
connections
15 mail_disapatc mail_dispatch When mail_dispatcher will try to mmsSMTPTr Warning Mail Interface used
her er.trp connect to the SMTP server & if ap for MM3/MM4 is
error will occurr in making Down.
connection.
16 mail_disapatc mail_dispatch When mail dispatcher will be mmsSMTPTr Info Dispatcher for
her er.trp start. ap sending mails is
started.
17 mail_disapatc mail_dispatch When mail dispatcher will be mmsSMTPTr Warning Dispatcher for
her er.trp stop. ap sending mails is
stopped.
18 mail_disapatc mail_dispatch When mail_dispatcher will try to mmsSMTPTr Warning MMSC Mail Server
her er.trp connect to the SMTP server & if ap Error.
error will occur in making
connection.
19 mmbox_moni mmbox_monit When mmbox monitor will be mmsMMBox Info Mmbox monitor for
tor or.trp start to clean up for expired MonitorTrap monitoring expired
MMS. messages is
started.
20 mmbox_moni mmbox_monit While mmbox monitor will stop mmsMMBox Info Mmbox monitor for
tor or.trp after clean up expired MMS. MonitorTrap monitoring expired
messages is
stopped.
21 mmbox_moni mmbox_monit When mmbox_monitor will mmsMaxDB Critical Maximum number
tor or.trp initialize the multiple Connection of database
connections to the database connections is
using secondary configuration & made.
if error will occur due to too
many connections
22 mmbox_moni mmbox_monit While initializing the multiple mmsDBTrap Critical MMSC Database
tor or.trp connections to the database Error.
using secondary configuration &
error occurred in making
connections
23 mmbox_moni mms_count.tr When configurable parameter TotalMMSCo Info Total success
tor p “EnableSMSSuccessAlert” to untTrap MMS=<number>
the monitor.conf will be enable, & Total failure
then at configured time for MMS=<number>
paranmeter “TimeforSmsAlert”. on <date>
28 pi_dispatcher pi_dispatcher.t When PI dispatcher will be start. mmsPIDispa Info Dispatcher for
rp tacherTrap sending PI
notifications is
started.
29 pi_dispatcher pi_dispatcher.t When PI dispatcher will be stop. mmsPIDispa Warning Dispatcher for
rp tacherTrap sending PI
notifications is
stopped.

Name Name Warning
/Info
30 pi_dispatcher pi_dispatcher.t When PI dispatcher will mmsDBTrap Critical MMSC Database

rp initialize the multiple Error.
using secondary configuration &
if error will occur in making
connections
31 pi_dispatcher pi_dispatcher.t When error will occur in pushing mmsPPGTra Warning MMSC PPG Error.
rp the message to the PPG. p
32 pi_dispatcher pi_dispatcher.t When PI dispatcher will mmsMaxDB Critical Maximum number
rp initialize the multiple Connection of database
using secondary configuration & made.
if error will occur due to too
many connections
33 pi_dispatcher pi_dispatcher.t When PI dispatcher will bind the mmsSMSG Warning MMSC SMS
rp SMS gateway & if error will WTrap Gateway Error.
occur.
34 recv_server recv_server.tr When recv_server will be stop. mmsRecvSe Warning Receive server is
p rverTrap stopped.
35 recv_server recv_server.tr When recv_server will be start. mmsRecvSe Info Receive server is
p rverTrap started.
36 recv_server retr_server.trp When retr_server will be stop. mmsRetrSer Warning Retrieve server is
verTrap stopped.
37 recv_server retr_server.trp When retr_server will be start. mmsRetrSer Info Retrieve server is
verTrap started.
38 recv_server recv_server.tr When recv server will try to mmsSubscri Warning Unable to connect
p connect the subscription server ptionServerT to subscription
& if error will occur. rap server.
39 prov_server prov_server.tr When provisioning server will mmsProvSer Info Subscriber
p be start. verTrap provisioning
server is started.
40 prov_server prov_server.tr When provisioning server will mmsProvSer Warning Subscriber
p be stop. verTrap provisioning
server is stopped.
41 prov_server prov_server.tr When provisioning server will mmsDBTrap Critical MMSC database
p initialize the multiple Error.
& if error will occur in making
connections
42 prov_server prov_server.tr While provision server will mmsMaxDB Critical Maximum number
p initialize the multiple Connection of database
using secondary configuration made.
& if error will occur due to too
many connections
43 sms_dispatc sms_dispatch When sms dispatcher will try to mmsSMSG Warning MMSC SMS
her er.trp connect the SMS Gateway & if WTrap Gateway Error.
error will occur.
44 sms_dispatc sms_dispatch When sms dispatcher will be mmsSMSDis Info Dispatcher for
her er.trp start. patcherTrap sending
notification as

Name Name Warning
/Info
SMS is started.
45 sms_dispatc sms_dispatch When sms dispatcher will be mmsSMSDis Warning Dispatcher for
her er.trp stop. patcherTrap sending
notification as
SMS is stopped.
46 sms_dispatc sms_dispatch When sms dispatcher will mmsDBTrap Critical MMSC Database
her er.trp initialize the multiple Error.
& if error will occur in making
connections
47 sms_dispatc sms_dispatch When sms dispatcher will mmsMaxDB Critical Maximum number
her er.trp initialize the multiple Connection of database
using secondary configuration made.
& if error will occur due to too
many connections

Appendix D — Customer Support
SLA Matrix
The following table represents the Service Level Agreement (SLA) matrix of Comviva. This
matrix describes the different problems that impact the Comviva’s client business, the
corrective action that would be taken by Comviva to solve such problems, and the minimum
time that would be required to take such corrective actions.
Table 6: SLA Matrix
Problem Response Work-around SLA

Severity Time
30 minutes 4 hours
Emergency/ The correction work starts immediately and
continues until a work-around solution is
Critical available. After a work-around solution is
available, the case is downgraded to the
Major category.
2 hours 72 hours
Major/High Comviva’s personnel shall start working
immediately on the problem, and continue
till a work-around solution is found.
24 hours 3 weeks
Minor/Low Software correction shall be available within
3 weeks.
72 hours N/A
Enhancements Comviva will start development if the client
has asked for
enhancements/customizations.
Requires a Go-ahead from authorized
Customer personnel, and an approval of
Purchase Order.
Source: Comviva
Appendix D — Customer Support 139

Document Change History
Table 7: Document Change History
Version Description of Comments Date of Creation Author

Number Changes
1.0 Initial Release 9 June 2008 Prema
Source: Comviva
Document Change History 154

Contact Us
Corporate Office
A-26, Info City
Sector 34
Gurgaon 122001
Haryana, India
T: +91-124-4819000
F: +91-124-4819777
Bangalore Office
4, 12th Km
Bellary Road, Jakkur
Bangalore 560064
India
T: +91-80-43401600
F: +91-80-28565854
Mumbai Office
Unit 1-4, 1st Floor, Paradigm Tower
Tower B, Mindspace
Malad(W), Mumbai 400064, India
T: +91-22-40774300
F: +91-22-40774333
E-mail: techwriters@comviva.com
Contact Us 155

Multimedia Messaging Service Center (MMSC) V 2.6

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Multimedia Messaging Service Center (MMSC) V 2.6

Enviado por

Direitos autorais:

Formatos disponíveis

Multimedia Messaging Service

Center (MMSC) v 2.6

1.1 Scope .............................................................................................................................................................. 1

1.3 Conventions ................................................................................................................................................... 1

1.4 Acronyms and Abbreviations ..................................................................................................................... 2

1.5 Feedback and Suggestions ......................................................................................................................... 2

2.1 Overview ......................................................................................................................................................... 3

2.2 Features .......................................................................................................................................................... 3

2.3 MMSC Architecture and Interfaces ............................................................................................................ 4

2.4 Server Management ...................................................................................................................................... 9

2.5 Working of MMSC ......................................................................................................................................... 9

3.1 Login ............................................................................................................................................................. 11

3.2 Configuration Management ....................................................................................................................... 15

3.3 Message Dispatcher ................................................................................................................................... 53

3.5 Status Manager............................................................................................................................................ 78

3.6 Subscriber Manager - Provisioning ......................................................................................................... 79

3.7 Subscriber Manager- Black & White Subscriber List ............................................................................ 83

3.8 Subscriber Manager-Services................................................................................................................... 85

3.9 Subscriber Manager-PPG .......................................................................................................................... 88

3.10 Subscriber Manager-Search Utility .......................................................................................................... 90

3.11 Statistics Manager ...................................................................................................................................... 94

3.12 Usage Reports ........................................................................................................................................... 100

3.13 Message Manager ..................................................................................................................................... 110

3.14 Configuration ............................................................................................................................................. 116

3.15 User Manager ............................................................................................................................................. 117

Appendix A — MMSC CDRs .................................................................................................................. 121

Appendix B — MMSC Directories ......................................................................................................... 129

Appendix C — MMSC Traps .................................................................................................................. 135

Document Change History .................................................................................................................... 141

Contact Us................................................................................................................................................ 143

Window/Screen/Button/Icon/Menu/Field All names as seen in the applications are written in

 The New User window appears.

 Enter your login name in User Name.

Command output Example:

Term Full Form

 Store, browse, retrieve, forward multimedia messages

2.3 MMSC Architecture and Interfaces

Figure 2-1: Block Diagram

Figure 2-2: MM1

Figure 2-3: MMS Call Flows

Figure 2-4: MM3 Call Flows

Figure 2-5: MM4

Figure 2-6: MM4 Block Diagram

MMSC implements ENUM based forwarding (DNSENUM) as part of MM4 delivery

Figure 2-7: MM4 Call Flow

Figure 2-8: MM7 Call Flow

 WSP: Wireless Session Protocol

Figure 3-1: Login

 Enter your username and password in User name and Password.

Figure 3-2: Home Page

To add a new instance:

Figure 3-3: Add Instance

The following table provides a description of the screen fields.

Table 4: Field Description of Add Instance

Field Description Default/Example

Instance Name The name of the MMSC instance

 Enter the field values.

The following screen is displayed.

Figure 3-4: Add Instance

Figure 3-5: Instance added to Instance Manager

 The instance is added under the Instance manager.

Figure 3-6: Edit Instance