Post on 05-Apr-2018
7/31/2019 Mobile x Dge
1/89
Mobi leXdge
Version 6.0
For WinNT/Win2000/WinXP/Win2003/Win2008/Win 7
Release Date: 18 March 2011
Users Manual
2011 MobileXdge Inc
7/31/2019 Mobile x Dge
2/89
7/31/2019 Mobile x Dge
3/89
MOBILEXDGE............................................................................................................................. 1
END USER LICENSE AGREEMENT (EULA)..... ......... ........ ......... ........ ......... ........ ......... ........ ........ 1
WELCOME.................................................................................................................................. 4
WHATS NEW.............................................................................................................................. 5
NEWFEATURES .......................................................................................................................... 5BUGS F IXED ............................................................................................................................... 5THINGS TO NOTE......................................................................................................................... 5
CHAPTER 1 INTRODUCTION ................................................................................................... 7
GETTING STARTED ......................................................................................................................71.1INSTALLATION S ITE................................................................................................................. 7
1.1.1 Safety Rules..................................................................................................................71.1.2 Environment ..................................................................................................................71.1.3 Power Supply Considerations ......................................................................................... 8
1.2THE LICENSE KEY FILE ........................................................................................................... 91.2.1 First Time Registration................................................................................................... 91.2.2 Subsequent Registration ......... ........ ......... ........ ......... ........ ......... ......... ........ ......... ........ .. 9
1.3OVERALL SYSTEM ARCHITECTURE .......................................................................................... 111.4SYSTEM FUNCTIONS ............................................................................................................. 131.5M ISSION CRITICAL FUNCTIONS ............................................................................................... 17
2.5.1 Smart Load Balancing Feature....... ......... ........ ......... ........ ......... ......... ........ ......... ........ 171.5.2 Remote MOX GPRS Modem Feature ........................................................................... 181.5.3 Cross Platform Messaging Feature ............................................................................... 19
1.5.4 MobileXdge Clustering Feature ........ ......... ......... ........ ......... ........ ......... ........ ......... .... 191.5.5 GSM/GPRS/CDMA Modem Redundancy Support Feature ........ ......... ........ ......... ........ ... 201.5.6 Error notification & Reporting Feature via email ............................................................. 21
1.5.7 Message Status Delivery Reporting Feature ........ ........ ......... ........ ......... ........ ......... ....... 21
CHAPTER 2 INSTALLATION................................................................................................... 23
2.1SYSTEM REQUIREMENT......................................................................................................... 232.2INSTALLATION CHECKLIST ...................................................................................................... 23
2.3INSTALL MOBILEXDGE GATEWAY............................................................................................ 23
CHAPTER 3 USING MOBILEXDGE GATEWAY ....................................................................... 29
3.1RUNNING MOBILEXDGE SMS/MMS/WAPPUSH GATEWAY ........................................................ 29
3.2CONFIGURATION SETTING ..................................................................................................... 303.3SCHEDULER CONFIGURATION SETTING.................................................................................... 373.4MMSDIALUP PROFILE SETTING ............................................................................................. 38
3.5EXTERNAL MOXSTATIONS INTERFACE .................................................................................... 433.6CONFIGURING MOBILEXDGE DAEMON ..................................................................................... 44
3.7CONFIGURING WAP/MMS DATA SERVER................................................................................. 473.8SYSTEM TESTING ................................................................................................................. 503.9MOBILEXDGE WAP MAIL ...................................................................................................... 51
CHAPTER 4 USING SAMPLE APPLICATION .......................................................................... 53
4.1TYPE OF MOBILE MESSAGES.................................................................................................. 534.2SMS MESSAGING ................................................................................................................ 544.3WAP PUSH INDICATOR MESSAGING........................................................................................ 54
4.4WAP PUSH MULTI-MEDIA MESSAGING .................................................................................... 554.5MMSINDICATOR MESSAGING ................................................................................................ 564.6MOBILE TICKETING............................................................................................................... 56
4.7MMSMESSAGING ................................................................................................................ 574.8MM1MMSMESSAGING........................................................................................................ 58
4.9INCOMING SMS MESSAGES ................................................................................................... 594.10STATUS DELIVERY REPORTS................................................................................................ 60
7/31/2019 Mobile x Dge
4/89
4.11OUTGOING MESSAGE LOG................................................................................................... 61
4.12INCOMING MMSMESSAGES (VIA MM1)................................................................................. 624.13OUTGOING MESSAGES ........................................................................................................ 634.14MOBILEXDGE STATUS ......................................................................................................... 64
4.15CREATE MMSF ILE............................................................................................................. 65
CHAPTER 5 MOXRULES CUSTOMISATION ........................................................................... 68
5.1MOXRULESVB6PLATFORM............................................................................................... 68
5.2MOXRULESVB.NET2005/C#.NET2005PLATFORM............................................................. 685.3MOXRULES FUNCTIONS ....................................................................................................... 69
5.3.1 GetSendLog(StationStatus).......................................................................................... 69
5.3.2 UpdateSendLog( MsgIndex, Status )............................................................................. 765.3.3 UpdateReceiveLog( MOXID, Sender, Language, Message, TimeStamp, BolUniCode ). ... 775.3.4 UpdateReceiveMMSLog( MOXID, Transaction ID,Subject,location , Sender ) ........ ......... . 77
5.3.5 RetrieveMMSLog( MOXID, Sender, Transaction ID,Subject, MMS Content ) ........... ........ 785.3.6 UpdateErrorLog( Message ) ........ ........ ......... ......... ........ ......... ........ ......... ........ ......... .... 795.3.7 UpdateUnScheduleLog(Message) ................................................................................ 79
5.3.8 UpdateReportLog(MOXStation, ReportID, Sender, TimeStampA,TimeStampB)........ ....... 79
5.3.10 UpdateIndividualSendLog(Message)........................................................................... 815.3.11 GetEmail2SMS(Message) .......................................................................................... 81
5.3.11 CleanEmail4SMS(Message) ......... ........ ......... ........ ......... ......... ........ ......... ........ ......... . 82
CHAPTER 6 MOBILEXDGE COMPONENTS......... ......... ........ ......... ........ ......... ........ ......... ....... 83
6.1MOXRULES ........................................................................................................................ 83
6.2MMSCONVERT.................................................................................................................... 846.3LANGCONVERT .................................................................................................................... 84
CHAPTER 7 TROUBLESHOOT ............................................................................................... 85
7.1GSM/GPRS/CDMAMODEM OPERATION INDICATOR ................................................................ 85
7/31/2019 Mobile x Dge
5/89
1
End User License Agreement (EULA)IMPORTANT-READ CAREFULLY: This MobileXdge End-User License
Agreement ("EULA") is a legal agreement between you (either an individual or
a single entity) and MobileXdge for the MobileXdge software product(s)
identified above which may include associated software components, media,
printed materials, and "online" or electronic documentation ("SOFTWARE
PRODUCT"). By installing, copying, or otherwise using the SOFTWARE
PRODUCT, you agree to be bound by the terms of this EULA. If you do not
agree to the terms of this EULA, do not install or use the SOFTWARE
PRODUCT. If the SOFTWARE PRODUCT was purchased by you, you may
return it to your place of purchase for a full refund.
The SOFTWARE PRODUCT is protected by copyright laws and international
copyright treaties, as well as other intellectual property laws and treaties. The
SOFTWARE PRODUCT is licensed, not sold.
1. GRANT OF LICENSE. The SOFTWARE PRODUCT is licensed as follows:
Installation and Use. MobileXdge Inc grants you the right to install
and use copies of the SOFTWARE PRODUCT on your computers
running validly licensed copies of the operating system for which
the SOFTWARE PRODUCT was designed [e.g., Windows NT(r),
Windows XP, Windows 2000 or Windows 2003].
Backup Copies. You may also make copies of the SOFTWARE
PRODUCT as may be necessary for backup and archival purposes.
2. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.
Maintenance of Copyright Notices. You must not remove or alter
any copyright notices on all copies of the SOFTWARE PRODUCT.
Distribution. You may not distribute copies of the SOFTWARE
PRODUCT to third parties.
7/31/2019 Mobile x Dge
6/89
2
Prohibition on Reverse Engineering, Decompilation, and
Disassembly. You may not reverse engineer, decompile, ordisassemble the SOFTWARE PRODUCT, except and only to the
extent that such activity is expressly permitted by applicable law
notwithstanding this limitation.
Rental. You may not rent, lease, or lend the SOFTWARE
PRODUCT.
Transfer. You may not permanently transfer all of your rights under
this EULA, provided the recipient agrees to the terms of this EULA.
Support Services. MobileXdge may provide you with support
services related to the SOFTWARE PRODUCT ("Support
Services"). Use of Support Services is governed by the
MobileXdge polices and in "on line" documentation and/or other
MobileXdge-provided materials. Any supplemental software code
provided to you as part of the Support Services shall be considered
part of the SOFTWARE PRODUCT and subject to the terms and
conditions of this EULA. With respect to technical information you
provide to MobileXdge as part of the Support Services, MobileXdge
Inc may use such information for its business purposes, including
for product support and development. MobileXdge Inc will not utilize
such technical information in a form that personally identifies you.
Compliance with Applicable Laws. You must comply with all
applicable laws regarding use of the SOFTWARE PRODUCT.
3. TERMINATION. Without prejudice to any other rights, MobileXdge may
terminate this EULA if you fail to comply with the terms and conditions of this
EULA. In such event, you must destroy all copies of the SOFTWARE
PRODUCT.
4. COPYRIGHT. All title, including but not limited to copyrights, in and to the
SOFTWARE PRODUCT and any copies thereof are owned by MobileXdge. All
title and intellectual property rights in and to the content which may be
accessed through use of the SOFTWARE PRODUCT is the property of the
7/31/2019 Mobile x Dge
7/89
3
respective content owner and may be protected by applicable copyright or
other intellectual property laws and treaties. This EULA grants you no rightsto use such content. All rights not expressly granted are reserved by
MobileXdge.
5. NO WARRANTIES. MobileXdge expressly disclaims any warranty for the
SOFTWARE PRODUCT. THE SOFTWARE PRODUCT AND ANY RELATED
DOCUMENTATION IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE
IMPLIED WARRANTIES OR MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NONINFRINGEMENT. THE ENTIRE RISK
ARISING OUT OF USE OR PERFORMANCE OF THE SOFTWARE PRODUCT
REMAINS WITH YOU.
6. LIMITATION OF LIABILITY. To the maximum extent permitted by applicable
law, in no event shall MobileXdge or its suppliers be liable for any special,
incidental, indirect, or consequential damages whatsoever (including,
without limitation, damages for loss of business profits, business
interruption, loss of business information, or any other pecuniary loss)arising out of the use of or inability to use the SOFTWARE PRODUCT or the
provision of or failure to provide Support Services, even if MobileXdge as
been advised of the possibility of such damages. In any case, MobileXdge
entire liability under any provision of this EULA shall be limited to the
greater of the amount actually paid by you for the SOFTWARE PRODUCT or
US$5.00; provided however, if you have entered into a MobileXdge Support
Services Agreement, MobileXdge entire liability regarding Support
Services shall be governed by the terms of that agreement. Because somestates and jurisdictions do not allow the exclusion or limitation of liability,
the above limitation may not apply to you.
7/31/2019 Mobile x Dge
8/89
4
Welcome
Welcome to MobileXdge SMS/MMS/WAP Push Gateway System. With the
Mobile Gateway, you can send and receive SMS/MMS/WAP Push messages
from your own Server system. You may also develop your own business
engine and interact with this users friendly system, MobileXdge
SMS/MMS/WAP Push Gateway. The system is robust and easy to use. All you
need is just a normal Server, and GSM or CDMA modems connected.
The MobileXdge SMS/MMS/WAP Push Gateway supports up to 24 GSM or
CDMA modems, and is multi-lingual supported. It is able to provide load
balancing and concurrent sending SMS/MMS/WAP Push messages, as well as
receiving SMS/MMS messages. As its support multi-lingual, you can send SMS
in Chinese, Japanese, Korea, Vietnam, Thai, Arabic, French, Spanish, German,
etc. All you need to do is specific which language you are using.
This users guide will help you to set up your own MobileXdge SMS/MMS/WAP
Push gateway and provide some resources on how to enhance it. It alsosuggested to you how to implement business orientated system through the
use of MOXRules in Visual Basic 6 / Visual Basic .Net 2005 / C# .Net 2005 .
7/31/2019 Mobile x Dge
9/89
5
Whats New
New Features
1. Support Wavecom CDMA modem in text mode.2. Additional Intelligent Time Control to enable message broadcast to
within a specific time period. For example, you may set the System torelay the SMS/MMS/WAP Push Messages from 8am to 10pm fornormal broadcasting, and allow the system to continuesending/receiving urgent SMS/MMS/WAP Push Messages after the
normal hours.3. Support Customization in Microsoft Visual Basic 6/ Microsoft Visual
Basic .Net 2005/ Microsoft C# 2005.4. Additional MOX Station status parameter within the GetSendLog
function. The MOX Station Status parameter contains the currentmessage Queue of the MOX Station. This allows the MobileXdgeprogrammer an information to decide which MOX Station to use if hechoose to use manual mode in sending the messages.
5. The Email Rules has been merged with the MOXRules.
6. Additional function: UpdateIndividualSentLog has been created toreturn every messages that has been sent out successfully. Thisallow the system to have the exact status of the message sent, evenif the record contacts batches of mobile phone numbers to be sent.
Bugs Fixed
1. The MimeSniffer has been removed from MobileXdge to preventanti-virus program interfering the operation of MobileXdge.
2. A bug has been fixed for the receiving of Concatenated SMSmessages.
3. A bug has been fixed for sending Concatedated SMS messages.
Things to Note
1. There is 1 additional parameter settings "ACTIVETIME" added in the"mobilexdge.cfg" for each SMSGW_STN configurations to allow thesystem to be able to pause the messages to be broadcast in the
7/31/2019 Mobile x Dge
10/89
6
queue after operational hours and resume the broadcasting the next
day.2. There is two additional parameters settings added in the"mobilexdge.cfg":-- DATABACKUP: Setting to allow the system to auto backup the datain the Queue.- MOXRULES: 1 - Loads Microsoft Visual Basic .Net MOXRules; 2 -Loads Microsoft C# .Net 2005 MOXRules; 3 - Loads Microsoft VisualBasic 6 MOXRules
3. There is an additional Table "IndividualMsgLog" to store the returnstatus of every single message sent.
4. Receiving of MMS via POP3 Protocol has been removed.
7/31/2019 Mobile x Dge
11/89
7
Chapter 1 Introduction
Getting Started
In order for a smooth operation and installation of the MobileXdge
SMS/MMS/WAP Push Gateway, please follows the guidelines stated below:
Install the GSM/CDMA Modem on a suitable site
Obtain a License Key file for the software installation
1.1 Installation Site
1.1.1 Safety Rules
The GSM/GPRS/CDMA Modem needs to be install on a suitable site where the
environment is compliance to the safety rules of operating the modem. Aleaflet of the safety rules of operating the GSM/GPRS/CDMA modem can be
found in the box that housed the GSM/GPRS/CDMA modem.
1.1.2 Environment
As the GSM/GPRS/CDMA Modem operate on radio frequencies, its
environment need to be free from disturbance noise of the GSM/CDMA
network. Such noise like electrical power noise, electromagnetic interference,
etc.
The signal strength of the GSM/CDMA network around the installation site also
contributes to the performance of the MobileXdge Gateway. If the installation
site has poor reception of GSM/CDMA network signals, the GSM/GPRS/CDMA
modem will have difficulties in sending or receiving short messages. To boots
up the signal strength of the GSM/CDMA network around the installation site,
please consult the telecom operator of the SIM card used.
7/31/2019 Mobile x Dge
12/89
8
The operating temperature range for the GSM/GPRS/CDMA modem is from
20C to +55
C.
1.1.3 Power Supply Considerations
Check the power at your site to ensure that your are receiving clean power
(free of spikes and noise). Install a power conditioner if necessary.
The power adapter that accompanied the GSM/GPRS/CDMA modem operate atmaximum current of 500mA, 230V, 50Hz power supply.
7/31/2019 Mobile x Dge
13/89
9
1.2 The License Key File
A License Key File is needed in order for the MobileXdge SMS/MMS/WAP Push
Gateway to operate. The CD activation key is labelled on the MobileXdge
Installation CD.
1.2.1 First Time Registration
First Time Registration means that the license key has new and has not been
registered online via MobileXdge Registration web site. To get your CD Key,
you need to obtain it by using the Registration Manager provided in the CD.
Please install the software in the live machine. Upon executing the
Registration Manager for MobileXdge SMS/MMS/WAP Push Gateway, you will
be prompt to enter your Company Name, and the CD key that can be found at
the back of the CD Case. Once you have generated the Registration Key, copy
the Registration Key information and visit http://www.mobilexdge.com to
continue with your registration. Once you have registered successfully, the
system will generate a License Key file. Copy the License Key file into the
windows system directory (for Win2000/NT/XP/2003, the directory is
c:\windows\system32). Rename the License key to MobileXdge.key. If you have
purchased additional port license, please repeat the above process and copy
the license key file for the additional ports to the sub directory License of the
installed directory.
1.2.2 Subsequent Registration
Subsequent registration means that the license key has been registered online
before. You may need to subsequent registration if you want to migrate the
existing MobileXdge SMS/MMS/WAP Push Gateway to a new PC Server or the
PC Server has been corrupted.
To get your CD Key, you need to obtain it by using the Registration Manager
provided in the CD. Please install the software in the live machine. Upon
executing the Registration Manager for MobileXdge SMS/MMS/WAP Push
7/31/2019 Mobile x Dge
14/89
10
Gateway, you will be prompt to enter your Company Name, and the CD key that
can be found at the back of the CD Case. Once you have generated theRegistration Key, copy the Registration Key information and email to our
support team at support@mobilexdge.com. Our support Team will response to
your request on the new license key file within the next 4 hours. Copy the
License Key file into the windows system directory (for Win2000/NT/XP/2003,
the directory is c:\windows\system32). Rename the License key to
MobileXdge.key. If you have purchased additional port license, please repeat
the above process and copy the license key file for the additional ports to the
sub directory License of the installed directory.
7/31/2019 Mobile x Dge
15/89
11
1.3 Overall System Architecture
The above diagram shows the overall system architecture of MobileXdge
SMS/MMS/WAP Push Gateway. It consists of 10 main components. The Core
MobileXdge Gateway System, Multi-Lingual Support Component, MOX
Stations, M-Coupon, M-Ticketing, M-Advertising, M-Survey, M-Mail, MOXRules
Open Source Component and EmailRules Open Source Component.
Core MobileXdge Gateway System: This is the main system component of the
MobileXdge Gateway System. Most of the co-ordination of the sending and
receiving of the SMS/MMS/WAP Push Messages is done with here.
Multi-lingual Support Component: This component handles all the conversion of
data receive/Send to different languages depending on the language selected.
MOX Stations Component: This component handles the incoming and outgoing
SMS/MMS/WAP Push Messages. Each of the MOX Stations acts directly and
Core MobileXdge Gateway System
Multi-Lingual Support
MOX Stations
(Up to 24 GSM Modems)
M-Coupon M-Ticketing M-Advertising M-Survey M-Mail
MOXRules Integration to third partysystem
(Open Source in VB6, VB.Net 2005/ C#.Net 2005)
MOXRules Channel email to SMS(Open Source in VB6, VB.Net 2005/ C#
.Net 2005)
Other Third Party Enterprise System
Any protocols Via POP3rotocol
Internet Email Server
7/31/2019 Mobile x Dge
16/89
12
independently on the Virtual processors, which is emulated during the start up
of MobileXdge SMS/MMS/WAP Push Gateway. There are a total of 24 Virtualprocessors within. With this technology which our R&D Team has developed,
it enables high speed and concurrent sending/receiving of SMS/MMS/WAP
Push Messages.
M-Coupon Component: This component handles the creation and
transformation of the MMS Coupons.
M-Ticketing Component: This component handles the real-time creation of bar
coded ID, which will be embedded together with MMS Message.
M-Advertising Component: This component the creation and transformation of
the MMS Advertisement Message.
M-Survey Component: This component handles the incoming SMS Messages
that the end user responded from the M-Survey. The system can concurrently
handles up to a maximum of 24 different SMS Channels, with different rules set
defined for each channels.
M-Mail Component: these components process the incoming emails and
channel them to the end user via SMS.
MOXRules Component: This component handles all the business rules and the
email forwarding rules of the users. This component is written in VB6/VB.Net
2005/C#.Net 2005 and is open source. With the open source concept, users are
able to further customise the system to integrate seamlessly into any third
party enterprise applications with minimum effort.
7/31/2019 Mobile x Dge
17/89
13
1.4 System Functions
The MobileXdge SMS/MMS/WAP Push Gateway is designed to send and
SMS/MMS messages, as well as transmission of WAP Push Message via a PC
Server. It is made so robust that it can seamlessly integrate with any third
party applications. Hence, it gives companies a great window of business
opportunities to explore into the Mobile market.
MobileXdge SMS/MMS/WAP Push Gateway runs as a Windows Service, which
can be Start and Stop easily, just by a click of a button. System configuration
is also can be done easily by changing the setting in the configuration file
(MOBILEXDGE.CFG) which is located in the folder \Config.
The Load Balancing Configuration File (SchedulerList.cfg) is located in the
folder \Config. This configuration file contains the Load
Balancing Settings to auto route the SMS/MMS/WAP Push Messages to the
desired port/ GSM/CDMA modem. This feature enables company to send SMS
directly to the designated Telecom, rather than cross-telco. If the prefix is left
empty in Load Balancing Configuration File, MobileXdge SMS/MMS/WAP PushGateway will auto schedule the messages equally to all available ports/ GSM
/CDMA modems.
7/31/2019 Mobile x Dge
18/89
14
MOBILEXDGE.CFG
[MOBILEXDGE]LOGEDITOR=C:\WINNT40\system32\Notepad.exeLOGENABLE=YLOGFILE=c:\MobileXdge\LOGFILES\mobilexdge.LOGARCHIVEDIR=c:\MobileXdge\ArchiveSTATSFILE=C:\MobileXdge\Stats\stats.txtFTPSVR=210.193.11.1FTPID=AdminFTPPWD=adminMMSSVR=210.193.11.19/mmsFILEFOLDER=C:\MobileXdge\WapEmailSTARTUP=YSMSCRESP=YAUTOSHUTDOWN=Y
RETRYLIMIT=1STNLIMIT=10RELOADLIMIT=2DATABACKUP=NMOXRULES=1
[EMAILSVR]POP3SVR=po.email.comPOP3PORT=110SMTPSVR=smtp.email.comSMTPPORT=25POP3TIMER=1POP3TIMEOUT=999999
[SMSFWDAC]SMSFWDMAIL=name@email.comSMSFWDID=name@email.comSMSFWDPWD=1234STARTUP=N
[SMSGW_STN_1]COMPORT=1MODEMSETTING=115200,N,8,1TIMEOUT=1000RECVINT=5LOGENABLE=YLOGFILE=c:\MobileXdge\LOGFILES\Stn_1.LOGACTIVETIME=00:00-00:00MM1MMSSVR=http://mms.e-ideas.com.sg:10021/mmsc
GPRSPROFILE=SingTelMM1WAPSVR=165.21.42.84MM1WAPPORT=8080MM1IP=165.21.42.84MM1MASK=255.255.255.255ASSIGNIP=10.23STARTUP=Y
[SMSGW_STN_2]
...[SMSGW_STN_24]
7/31/2019 Mobile x Dge
19/89
15
The MobileXdge SMS/MMS/WAP Push Gateway supports up to 24
GSM/GPRS/CDMA modems (the standard package comes with one PortLicense).
The MobileXdge SMS/MMS/WAP Push Gateway will constantly call the
MOXRules, which is pre-customised by the users for specific business needs
and purpose.
The MobileXdge SMS/MMS/WAP Push Gateway also come with a main events
log (MobileXdge.LOG), and 24 other MOX Stations log file, STN_X, which will
track all transmission, as well as reception from the GSM/GPRS/CDMA
modem. In other words, its provides a detail audit trail of all the activities of the
MobileXdge SMS/MMS/WAP Push Gateway, as well as the GSM/GPRS/CDMA
modem. This events log files can also use as a diagnosis tools to fault find on
the SMS/MMS/WAP Push Gateway if there is any unusually activities. In
addition, the system will generate two separate files:
MobileXdgeDotNetError.txt and MXError.txt when errors occurs within the
MOXRules.
The MobileXdge SMS/MMS/WAP Push Gateway supports multi-lingual SMS
messaging. Hence, you can send and receive SMS in Chinese, Japanese,
Korea, Vietnam, Thai, Arabic, French, Spanish, German, etc. All you need to do
is specific which language you are using during the transmission of SMS
Messages. Below is the List of Languages MobileXdge Gateway Support:
Code Language
ARB Arabic
BAL Baltic
CHS Chinese Simplified
CHT Chinese Traditional
7/31/2019 Mobile x Dge
20/89
16
CYR Cyrillic
ENG English
GRE Greek
HED Hebrew
JAP Japanese
KOR Korean
LT1 Latin 1
LT2 Latin 2
LT5 Latin 5
UNI Unicode
THA Thai
VIM Vietnam
7/31/2019 Mobile x Dge
21/89
17
1.5 Mission Critical Functions
In addition to the mobile messaging features, MobileXdge SMS/MMS/WAP
Push Gateway is built with Mission Critical features that enable the system
to handle modems failover, MobileXdge Gateway clustering, load-balancing,
and other features that are deem mission critical to the enterprises.
3.5.1 Smart Load Balancing Feature
MobileXdge SMS/MMS/WAP Push Gateway has a built-in Load balancing
capabilities of up to 24 GSM/GPRS/CDMA modems. The system allow to
manually specify which GSM/GPRS/CDMA modems to transmit the
SMS/MMS/WAP Push messages or allow the system to provide auto load
balancing according to a predefined route table.
7/31/2019 Mobile x Dge
22/89
18
1.5.2 Remote MOX GPRS Modem Feature
MobileXdge SMS/MMS/WAP Push Gateway robust architecture can be
configured to access remote GPRS modems across various countries via the
MOX Remote Ports. This means that you need just one MobileXdge
SMS/MMS/WAP Push Gateway residing in one country, and the physical GPRSmodems can be installed and placed in other countries. In addition, you will
just need to manage one centralised database. Thus, with MOX Remote Ports,
administrating and maintaining the MobileXdge SMS/MMS/WAP Push
Gateway made easier.
7/31/2019 Mobile x Dge
23/89
19
1.5.3 Cross Platform Messaging Feature
The robustness of the system to support cross platform messaging from a
variety of platforms like Unix, Linux, OpenVMS, AS400, Windows OS, etc via a
generic low level perl script
1.5.4 MobileXdge Clustering Feature
MobileXdge SMS/MMS/WAP Push Gateway supports clustering to enable
high availability of the system. When all the MobileXdge SMS/MMS/WAP
Push Gateway are all operating, the mobile messages load will be shared
within the cluster. In the scenario whereby any one of the MobileXdge
7/31/2019 Mobile x Dge
24/89
20
SMS/MMS/WAP Push Gateway fails, the other MobileXdge SMS/MMS/WAP
Push Gateway will take to the load of the system that failed to operate.
1.5.5 GSM/GPRS/CDMA Modem RedundancySupport Feature
MobileXdge SMS/MMS/WAP Push Gateway allows up to 24 GSM/CDMA
modems to be connected. In the event when there is a failure in the
GSM/CDMA modem hardware, the MobileXdge SMS/MMS/WAP Push
Gateway will be able to detects the failure in the GSM/CDMA modem hardware
and shutdown the MOX station that operates on the GSM/CDMA modem; if
there are still some SMS/MMS/WAP Push messages stuck in the queue of the
MOX station, the system will be able to rescue the messages and re-distributethem to all the GSM/CDMA modems that are operating.
7/31/2019 Mobile x Dge
25/89
21
1.5.6 Error notification & Reporting Feature via email
MobileXdge SMS/MMS/WAP Push Gateway comes with an MX Daemon that
monitors the MobileXdge SMS/MMS/WAP Push Gateway. In the event if the
MobileXdge SMS/MMs/WAP Push Gateway cease to operate due to some
fatal error, the MX Daemon will generate an alert email to the administrator. In
addition, the system allow you to configure to receive daily, weekly and
monthly reports on the status and statistics of the MobileXdgeSMS/MMs/WAP Push Gateway.
1.5.7 Message Status Delivery Reporting Feature
7/31/2019 Mobile x Dge
26/89
22
MobileXdge SMS/MMS/WAP Push Gateway can be configured to receive
Message Status Delivery Report. This feature is crucial for organisation thatneeds a detailed record on the status of every messages sent, like when it
reaches the mobile operator, and when it reached the mobile phone.
7/31/2019 Mobile x Dge
27/89
23
Chapter 2 Installation
2.1 System Requirement
Please ensure that the system, which you are intended to install the
MobileXdge SMS/MMS/WAP Push Gateway, must satisfied the minimum
requirement as listed below:
Intel Pentium 4 and above personal computer
Microsoft Windows 98/2000/2003/2008/7 or NT 4.0 (Service Pack4) or higher
512 Mbytes of RAM
A mouse and keyboard that is supported by Windows OperatingSystem
A hard disk with at least 1GB of free space for the program.
At least one free serial port for the GSM/GPRS/CDMA Modem tobe connected
2.2 Installation checklist
To run MobileXdge SMS/MMS/WAP Push Gateway successfully, you need:
Minimum system requirements as listed in previous section
License KEY file that you can obtain after you registered theMobileXdge SMS/MMS/WAP Push Gateway
One or more GSM/CDMA Modem(s) with valid SIM card(s)
Complete the necessary steps in Chapter 1 of this guide.
2.3 Install MobileXdge Gateway
7/31/2019 Mobile x Dge
28/89
24
Install MobileXdge SMS/MMS/WAP Push Gateway 6.0 from the web browser,
which will auto-run default.htm from the installation CD provided.
Install the Registration Manager from the web browser, which will auto-run
default.htm from the installation CD provided.
After installing the above Setup programs, restart the Windows Server. Start
the Registration Manager. You will be prompt to enter your Company Name,
and the CD key, which can be found at the back of the CD Case. Once you
have generated the Registration Key, copy the Registration Key information
and visit http://www.mobilexdge.com to continue with your registration. Once
you have registered successfully, the system will generate a License Key file.
Copy the License Key file into the windows system directory (for
Win2000/NT/2003, the directory is c:\windows\system32). Rename the License
key to MobileXdge.key. If you have purchased additional port license, please
repeat the above process and copy the license key file for the additional ports
to the sub directory License of the installed directory.
The next few pages will guide you to install the MobileXdge SMS/MMS/WAP
Push Gateway.
7/31/2019 Mobile x Dge
29/89
25
Step 1:
Step 2:
7/31/2019 Mobile x Dge
30/89
26
Step 3:
Step 4:
7/31/2019 Mobile x Dge
31/89
27
Step 5:
Step 6:
7/31/2019 Mobile x Dge
32/89
28
Step 7:
7/31/2019 Mobile x Dge
33/89
29
Chapter 3 Using MobileXdge Gateway
3.1 Running MobileXdge SMS/MMS/WAP PushGateway
It is important to check if the modem port is being set correctly before
executing MobileXdge SMS/MMS/WAP Push Gateway in the config file named
under MobileXdge.CFG.
Ensure that the GSM/GPRS/CDMA modem(s) are connected to the system you
are running the MobileXdge SMS/MMS/WAP Push Gateway.
7/31/2019 Mobile x Dge
34/89
30
3.2 Configuration Setting
There are three Configurations setting you need to configure before you start
operating the system: MobileXdge.cfg, SchedulerList.cfg, and the Internet
Information Server. In this chapter, we will discuss in great details on the
setting of the MobileXdge System as well as the Microsoft IIS Server.
MOBILEXDGE.CFG
MMSSVR=210.193.11.19/mmsFILEFOLDER=C:\MobileXdge\WapEmail
STARTUP=YSMSCRESP=YAUTOSHUTDOWN=YRETRYLIMIT=1STNLIMIT=10RELOADLIMIT=2DATABACKUP=NMOXRULES=1
[EMAILSVR]POP3SVR=po.email.comPOP3PORT=110SMTPSVR=smtp.email.comSMTPPORT=25POP3TIMER=1POP3TIMEOUT=999999
[SMSFWDAC]SMSFWDMAIL=name@email.comSMSFWDID=name@email.comSMSFWDPWD=1234STARTUP=N
[SMSGW_STN_1]COMPORT=1MODEMSETTING=115200,N,8,1TIMEOUT=1000RECVINT=5LOGENABLE=Y
LOGFILE=c:\MobileXdge\LOGFILES\Stn_1.LOGACTIVETIME=00:00-00:00MM1MMSSVR=http://mms.e-ideas.com.sg:10021/mmscGPRSPROFILE=SingTelMM1WAPSVR=165.21.42.84MM1WAPPORT=8080MM1IP=165.21.42.84MM1MASK=255.255.255.255ASSIGNIP=10.23STARTUP=Y...
.Cont
7/31/2019 Mobile x Dge
35/89
31
[MOBILEXDGE]: Configuration of the Main MobileXdge SMS/MMS/WAP Push
Gateway
LOGEDITOR: The text editor for viewing the log files
LOGENABLE: Set if you want the system to log the events/activities (Y/N)
LOGFILE: Determine the log file
ARCHIVEDIR: Set the archive directory where the system stores the daily
archive log files
STATSFILE: Set the text file in which the MobileXdge SMS/MMS/WAP Push
Gateway stores its real-time statistics of the system.
[[SMSGW_STN_2]COMPORT=2
MODEMSETTING=115200,N,8,1TIMEOUT=1000RECVINT=5LOGENABLE=YLOGFILE=c:\MobileXdge\LOGFILES\Stn_2.LOGACTIVETIME=00:00-00:00MM1MMSSVR=http://mms.starhubgee.com.sg:8002GPRSPROFILE=StarhubMM1WAPSVR=10.12.01.80MM1WAPPORT=8080MM1IP=10.12.0.0MM1MASK=255.255.0.0ASSIGNIP=10.17STARTUP=N
[SMSGW_STN_3]COMPORT=3MODEMSETTING=115200,N,8,1TIMEOUT=1000RECVINT=5LOGENABLE=YLOGFILE=c:\MobileXdge\LOGFILES\Stn_3.LOGACTIVETIME=00:00-00:00MM1MMSSVR=http://172.16.14.20:8002GPRSPROFILE=M1MM1WAPSVR=172.16.14.10MM1WAPPORT=8080MM1IP=172.16.0.0MM1MASK=255.255.0.0ASSIGNIP=172.STARTUP=N..
7/31/2019 Mobile x Dge
36/89
32
FTPSVR: The identification of the FTP Server that accepts the MMS messages
content and WAP Multi-media data.
FTPID: The identification of the user account for FTP Server that accepts the
MMS messages content and WAP Multi-media data.
FTPPWD: The identification of the user password of the user account for FTP
Server that accepts the MMS messages content and WAP Multi-media data.
MMSSVR: The identification of the MMS Server that stores the MMS messages
content and WAP Multi-media data.
FILEFOLDER: If the MMS messages content and WAP Multi-media data is to be
stored in the MMS Server within its local area network, you need to set the
setting to the path which will direct the MMS messages content and WAP
Multi-media data to the MMS Server.
STARTUP: Set if you want the system to start upon the execution of
MobileXdge SMS/MMS/WAP Push Gateway (Y/N)
SMSCRESP: Set if you want the system to enable retrieval of the SMS Centre
auto response message (Y/N)
AUTOSHUTDOWN: Set if you want the system to continue to operate even
without a GSM/GPRS/CDMA modem (Y/N).
RETRYLIMIT: Set the system to retry if fails to send. Recommended is 2
STNLIMIT: Set the system to auto shutdown if it fails to send successfully for a
consecutive number of times.
RELOADLIMIT: Set the system to re-activate the MOX Station by performing a
power reset of the physical GSM/GPRS/CDMA modem if the GSM/GPRS/CDMA
modem fail to function.
DATABACKUP=N
MOXRULES=1
7/31/2019 Mobile x Dge
37/89
33
DATABACKUP: Set the system to backup the messages in the queue pending
to be sent. If the parameter is set to Y, the system will backup the messagesduring runtime. If the system shutdown abnormally, it will restore back the
queue upon the next bootup of the system.
MOXRULES: Set the system to use either one of the below MOXRules: -
1. MOXRulesVBNet: Use 1 if you want to use the MOXRules in VB.Net 2005.
The open source code is found in the folder c:\mobilexdge\
MOXRulesVBNet folder.
2. MOXRulesCSNet: Use 2 if you want to use the MOXRules in C#.Net 2005.
The open source code is found in the folder c:\mobilexdge\
MOXRulesCSNet folder.
3. MOXRules: Use 3 if you want to use the MOXRules in VB 6. The open
source code is found in the folder c:\mobilexdge\ MOXRules folder.
Please note that you will need to copy the compiled DLL to the
c:\mobilexdge folder.
[EMAILSVR]: Configuration of the Internet Email Server for the reception of
MMS Message, and forwarding of Email to SMS Messages.
POP3SVR: The POP3 Server address
POP3PORT: The POP3 Server Port number
SMTPSVR: The SMTP Server Address
SMTPPORT: The SMTP Server Port number
POP3TIMER: Configuration on time interval to poll the POP3 and SMTP Server.
[MMSRECVAC]: Configuration of the Internet Email account for the retrieval of
MMS Message.
MMSRECVEMAIL: The Email address for MMS Message retrieval
7/31/2019 Mobile x Dge
38/89
34
MMSRECVID: The Email account ID for MMS Message retrieval.
MMSRECVPWD: The Email account password for MMS Message retrieval
MMSFILEFOLDER: The file folder which the system store the incoming MMS
Message.
STARTUP: Set if you want the system to start polling the MMS Account upon
the execution of MobileXdge Gateway (Y/N)
SMSCRESP: Set if you want the system to get the Telco status reports for themessages sent. Value is (Y/N).
[MMSRECVAC]: Configuration of the Internet Email account for the retrieval of
MMS Message.
MMSRECVEMAIL: The Email address for MMS Message retrieval
MMSRECVID: The Email account ID for MMS Message retrieval.
MMSRECVPWD: The Email account password for MMS Message retrieval
MMSFILEFOLDER: The file folder which the system store the incoming MMS
Message.
STARTUP: Set if you want the system to start polling the MMS Account upon
the execution of MobileXdge Gateway (Y/N)
[SMSFWDAC]: Configuration of the Internet Email account for the retrieval of
MMS Message.
SMSFWDMAIL: The Email address for email forwarding via SMS.
SMSFWDID: The Email account ID for email forwarding via SMS.
SMSFWDPWD: The Email account password for email forwarding via SMS.
7/31/2019 Mobile x Dge
39/89
35
STARTUP: Set if you want the system to start polling the SMS forwarding
Account upon the execution of MobileXdge Gateway (Y/N)
[SMSGW_STN_1]: Configuration of the MOX stations
COMPORT: Set the communication port where the GSM/GPRS/CDMA modem
is attached
MODEMSETTING: Setting of the GSM/CDMA modem (Speed,parity,bit,stop bit)
TIMEOUT: Set the waiting time of the station
RECVINT: Set the checking of incoming SMS Messages after certain number of
outgoing SMS/MMS/WAP Push Messages.
LOGENABLE: Set if you want the system to log the events/activities(Y/N)
LOGFILE: Determine the log file
ACTIVETIME: Set the operational hour for the system. Default is 00:00-00:00.Once you set to 00:00-00:00, it means 24 hours operational. Please note that
this feature allows the system to control time of sending messages, in
particular during a message broadcast. The system will pauses all messages
in the queue when the operation hour is over and continue the next day.
Please note that the system will still allow new messages to be sent even after
the operational hours. (This feature allows the system to handle urgent
messages that need to be sent immediately)
MM1MMSSVR: Set the Telco MMS Server
GPRSPROFILE: Set the Dialup profile
MM1WAPSVR: The Telco WAP Server
MM1WAPPORT: The Telco WAP Server Port
MM1IP: The destination IP Address in which the IP Traffic will be routed
7/31/2019 Mobile x Dge
40/89
36
MM1MASK: The subnet mask of the destination IP Address
ASSIGNIP: The IP address assigned by the telecom. This IP address can be a
partial IP. This parameter is used by the system to re-route IP traffic according
to the IP address specified.
STARTUP: Set if you want the system to start upon the execution of
MobileXdge Gateway (Y/N)
7/31/2019 Mobile x Dge
41/89
37
3.3 Scheduler Configuration Setting
You can configure the scheduler settings of MobileXdge SMS/MMS/WAP Push
Gateway through the configuration file SchedulerList.CFG.
There are all together 24 port settings you can configure. If all the Phpx are left
blank, MobileXdge SMS/MMS/WAP Push Gateway will take control of the auto
scheduling for all the outgoing SMS/MMS/WAP Push Messages.
The Scheduler Configuration settings are extremely useful in countries where
the Telco do not provide cross SMS/MMS/WAP Push Messaging facilities. In
this case, you can configure the PhPx. PhPx is the parameters where you can
set the prefix of the designated phone numbers which belongs to the particular
Telco. For example, in PhPx1, the parameter is set to only accept any mobile
phone numbers starting with the number +6590 or 90.
It is recommended that you leave the last available PhPx empty. This to cater
for any unforeseen mobile numbers prefix which is not specified in the
pervious prefix for the GSM/GPRS/CDMA modem.
PhPx1 = +6590,90
PhPx2 = +6391,+6392
PhPx3 = +6012
PhPx4 =
.
.
.
.
PhPx16 =
PhPx17 =
PhPx18 =
PhPx19 =
PhPx20 =
PhPx21 =
PhPx22 =
PhPx23 =
PhPx24 =
7/31/2019 Mobile x Dge
42/89
38
3.4 MMS Dialup Profile Setting
MobileXdge SMS/MMS/WAP Push Gateway allows you to send and receive
MMS via MM1 protocol, which requires you to set up the dialup profile in
Microsoft Windows that connects to the GPRS/3G network. (Please note that
CDMA modem is not supported for MMS functions). Below are the steps: -
Step 1:
Step 2:
7/31/2019 Mobile x Dge
43/89
39
Step 3:
Step 4:
7/31/2019 Mobile x Dge
44/89
40
Step 5:
Step 6:
7/31/2019 Mobile x Dge
45/89
41
Step 7:
Step 8:
7/31/2019 Mobile x Dge
46/89
42
Step 9:
7/31/2019 Mobile x Dge
47/89
43
3.5 External MOX stations Interface
MobileXdge SMS/MMS/WAP Push Gateway allows you to re-activate the MOX
Stations via any third party application. To re-active the MOX Station, you will
need to access to the Restart.txt file located in the Stats folder. The
Restart.txt consists of 24 Zeros 0, in which each 0 represents a MOX
Station. Whenever you need to activate the individual MOX Station, you will
need to change the 0 to 1. MobileXdge SMS/MMS/WAP Push Gateway
will process the request and re-activate the particular MOX Station. Thereafter,
MobileXdge SMS/MMS/WAP Push Gateway will reset the 1 to 0. Below is
the content of the Restart.txt file:
000000000000000000000000
7/31/2019 Mobile x Dge
48/89
44
3.6 Configuring MobileXdge Daemon
MobileXdge SMS/MMS/WAP Push Gateway is widely used in mission critical
operations. This MobileXdge Daemon provides transmission of emails to the
system administrator if there is any failure or status change in the individual
MOX Stations in the MobileXdge SMS/MMS/WAP Push Gateway as well as
generation of daily, weekly monthly report via email.
The MobileXdge Daemon allows you to conduct diagnostic on the system to
send out email alerts. To enable the diagnostic mode, you will need to run the
MobileXdge Daemon with a t parameter at the end of the program. Below is
the detail:-
C:\MobileXdge\MXDaemon\MXDaemon.exe t
7/31/2019 Mobile x Dge
49/89
45
[MXDAEMON]: Configuration of the MobileXdge Daemon
MXDAEMONSMTPSVR: The SMTP Server IP Address or name
MXDAEMONSMTPPORT: The SMTP Server Port number, default is 25
MXDAEMONNAME:The email account ID
MXDAEMONFROMAC: The email address of the sender
MXDAEMONPWD: The email account password
MXDAEMONTOAC: The email address of the recipient
MXRESTART: Instruct if to restart the MobileXdge Gateway if it shutdown due
to modem failure. (Y/N)
MXSTATFILE: The file where holds the statistics of the MobileXdge
SMS/MMS/WAP Push Gateway
ADHOCRPT: To set the system to allow sending of email if there is any fault in
MobileXdge SMS/MMS/WAP Push Gateway; value (Y/N).
DAILYRPT: To set the system to report the statistics of the system daily; (Y/N).
[MXDAEMON]
MXDAEMONSMTPSVR=210.193.11.18MXDAEMONSMTPPORT=25
MXDAEMONNAME=MXDAEMON
MXDAEMONFROMAC=sly@mobilexdge.com
MXDAEMONPWD=password
MXDAEMONTOAC=sly@mobilexdge.com
MXRESTART=Y
MXSTATFILE=c:\mobilexdge\stats\stats.txt
ADHOCRPT=Y
DAILYRPT=Y
WEEKLYRPT=Y
MONTHLYRPT=Y
7/31/2019 Mobile x Dge
50/89
46
WEEKLYRPT: To set the system to report the statistics of the system weekly;
(Y/N).
MONTHLYRPT: To set the system to report the statistics of the system
monthly; (Y/N).
7/31/2019 Mobile x Dge
51/89
47
3.7 Configuring Wap/MMS Data Server
As MMS messaging encompassed 3 types of technology: SMS Technology,
Wap Technology and GRPS Technology, there is a need to configure your IIS
Server to be a Wap server and MMS Data Server. To configure the IIS Server
as Wap Server, right click the select the properties page.
7/31/2019 Mobile x Dge
52/89
48
Click on the Add Button, Add an additional wml header name and the header
value as show in the diagram above.
7/31/2019 Mobile x Dge
53/89
49
Click on the File Type Button and add the following settings:-
Associated extension Content type (MIME)
.bmp Image/bmp
.gif Image/gif
.jar Application/java-archive
.jpg Image/jpeg
.mid Audio/midi
.wbmp Image/vnd.wap.wbmp
.wml Text/vnd.wap.wml
.mms Application/vnd.wap.mms-
message
7/31/2019 Mobile x Dge
54/89
50
3.8 System Testing
There is a system test button situated on the main screen of the MobileXdge
SMS/MMS/WAP Push Gateway. This is to allow you to performance a simple
test on the MobileXdge Gateway on each individual MOX Stations. When you
first installed the system, you can use this function to test the operability of
the system. Click on the button of the MobileXdge Gateway and
a new test window will appear.
Type in a valid mobile phone number and a test message in the text box
provided respectively. Click the button to send out the test message.
An OK pop-up window will appear if the message send out successfully.
7/31/2019 Mobile x Dge
55/89
51
3.9 MobileXdge WAP Mail
MobileXdge comes with a WAP Email System, which enables users to send
email via their mobile phone. This features, together with the functions of
email forwarding within MobileXdge MMS/SMS/WAP Push Gateway enables
users to be able to not only work remotely, but also only with a mobile phone.
MobileXdge WAP Mail application is located in the sub folder WAPMail of the
installed folder of MobileXdge. Please note that you need to relocate folder into
the WAP Server. The default page is MOXMail.asp. When accessing the
MobileXdge WAPMail, you should connect the phone to the MOXMail.asp,
which you will be able to send email from your mobile phone via WAP.
Please note that if your WAP Server is located on a PC Server different from
the MobileXdge MMS/SMS/WAP Push Gateway, you need to copy the
component vbSendMail.dll into the windows system directory and register
the component.
After successful installation of the MobileXdge WAPMail, you will be able toaccess the WAP Mail System from MobileXdge. The screens shots are
provided below:-
Welcome toMobileXdge
WAPMail
Proceed
7/31/2019 Mobile x Dge
56/89
52
MobileXdge WAP Mail (Send) Screen Shot
From:
[]To:[]Subject:
[]Message:[]
7/31/2019 Mobile x Dge
57/89
53
Chapter 4 Using Sample Application
4.1 Type of Mobile Messages
MobileXdge comes with a sample VB6 application. This application has been
developed to demonstrate the features of the MobileXdge Gateway. As the
application is open source, you will be able to further customise the
application to cater for your requirements. Below is the screen shots of the
application. There are all together seven types of mobile messages: SMS
Message/ MMS Indicator Message/ WAP Push Indicator Message/ MMS
Message/MM1 MMS Message/ WAP Push Message/ Mobile Ticketing.
When preparing to transmit the message, you need to define at least a valid
mobile phone number in the mobile phone field. You can import the mobile
phone number from an external file. The format of the file has to be as follows:-
You can also set the message priority in the priority check box & the status
delivery report option in the delivery report check box. You may choose which
port the messages is going to route manually, or allow the system to auto
schedule the messages.
+6590123456+6012847373
+4733635222..
7/31/2019 Mobile x Dge
58/89
54
4.2 SMS Messaging
In the SMS Messaging Option, you will need to select the language for SMS
Messaging. As well as, you will need to enter the actual SMS Message for
transmission.
4.3 WAP Push Indicator Messaging
WAP Push Indicator message allows you to define a particular WML page to be
push directly to the mobile user. You will need to enter the Title of the Content,
and the URL location of the WML page. E.g.
210.193.11.19/WAP/Welcome.wml. Please note that you do not need to enter
http://.
7/31/2019 Mobile x Dge
59/89
55
4.4 WAP Push Multi-media Messaging
WAP Push Multi-media message allows you to transmit Multi-media WAP page
directly to the mobile phone. (Note that the receiving end mobile phone has to
be a MMS/WAP phone, with GPRS connection activated). In order for the
successful transmission, you need a WAP server to contain the WAP Push
Multi-media message. You will need to define the content title, as well as the
WAP Push Multi-media content file, normally a wml file. Note that the
MobileXdge Gateway will retrieve all content found within the defined file
directory, and transfer it to the WAP Server via FTP protocol or normal file
copy protocol. FTP protocol is more applicable in situation where the WAP
Server and the MobileXdge Gateway is not within the same network. There aresome examples that come with the application located in the subfolder
samples\ppg.
7/31/2019 Mobile x Dge
60/89
56
4.5 MMS Indicator Messaging
MMS Indicator Message allows you to define the mms file that the mobile
phone will retrieve from. You will need to define the mms file located in the
server. E.g.: http://210.193.11.19/wap/min.mms. Please note that you need to
include http://.
4.6 Mobile Ticketing
7/31/2019 Mobile x Dge
61/89
57
MobileXdges Mobile Ticketing provides real-time generation of barcode ticket
number into jpeg picture format. This mobile ticket will then be transmitted tothe mobile users. You will need to enter the title of the message, the WML file.
You will need to enter the ticket number, which the system will then
dynamically create a barcode signature for you. There are some examples that
come with the application located in the subfolder samples\MKT.
Please note that you will need to defined as follows in the wml file:
The MTICKET.jpg will be auto-generated by the system, thus you will need to
define mticket.jpg within the WML file.
4.7 MMS Messaging
Get Coupon
7/31/2019 Mobile x Dge
62/89
58
MMS Messaging allows you to transmit MMS message to the mobile phone
users. The file will need to be an MMS file, and has to bear the file extension.MMS. You can create the MMS File by using the Create MMS File function
within the application. There are some examples that come with the application
located in the subfolder samples\mms.
4.8 MM1 MMS Messaging
MMS1 MMS Messaging allows you to transmit MMS message directly via the
GPRS/3G Network to the mobile phone users. You can add CC and BCC list of
mobile numbers(maximum of 20 mobile numbers can be added to the CC or
BCC list).
7/31/2019 Mobile x Dge
63/89
59
4.9 Incoming SMS Messages
The system enables you to view the SMS message received. The Field PortX
indicates source MOX Station which the SMS message is being received.
MobileXdge Gateway supports reception of concatenated messages, and
automatically joins the Multi-related messages into a single message.
7/31/2019 Mobile x Dge
64/89
60
4.10 Status Delivery Reports
The system enables you to view the SMS message received. The Field PortX
indicates source MOX Station which the SMS message is being received.
7/31/2019 Mobile x Dge
65/89
61
4.11 Outgoing Message Log
The system enables you to view the timestamp of individual message sent. For
example, you have a batch of ten mobile numbers to be sent in a broadcast, it
will create ten records here, showing the timestamp of each message sent.
7/31/2019 Mobile x Dge
66/89
62
4.12 Incoming MMS Messages (Via MM1)
The system enables you to view the MMS records received. The actual content
of the MMS message received is stored in c:\mobilexdge\mms folder. The
subfolder name corresponds to the MsgIndex of the received MMS message
record.
7/31/2019 Mobile x Dge
67/89
63
4.13 Outgoing Messages
The system enables you to view the outgoing messages that have been sent.
7/31/2019 Mobile x Dge
68/89
64
4.14 MobileXdge Status
The system enables you to view status of the MobileXdge SMS/MMS/WAP
Push Gateway, as well as the status of the individual MOX Stations control the
GSM/GPRS/CDMA modem. Below is the detail of the status:-
Time Stamp The time in which the status is recorded
Q Number of message(s) in Queue
S Number of message(s) Sent
F Number of message(s) Failed
R Number of message(s) received
E Estimated time in seconds that the system will take to process all
messages in the queue.
A Status of the MOX Station
7/31/2019 Mobile x Dge
69/89
65
4.15 Create MMS File
The system comes with a sample MMS File creation utility, which enables you
to create the mms file. You can have a selection to use either formatted SMIL
file to include the MMS content and data presentation, or directly the data
items without any display formatting via MOX file. Below are the samples of
the file format:
MMS Header File:
X-Mms-Message-Type: m-retrieve-conf
X-Mms-Transaction-Id: 12345678
X-Mms-Version: 1.0
Message-Id: 1111
Date: Wed Oct 24 09:55:52 2002
7/31/2019 Mobile x Dge
70/89
66
From: sales@mobilexdge.com
To: sales@mobilexdge.com
Subject: MobileXdge MMSC Sample
X-Mms-Message-Class: Personal
X-Mms-Priority: Normal
X-Mms-Delivery-Report: No
X-Mms-Read-Reply: No
Content-type: application/vnd.wap.multipart.related
In most cases, you will only need to change the From: and the To: fields.
The two fields need to be in the email address format. Please note that these
two fields will be shown in the mobile phones of the users. And the user will be
able to reply the message via email back to the MobileXdge Gateway.
SMIL File:
7/31/2019 Mobile x Dge
71/89
67
MOX File:
Macs-1.gif
Macs-2.gif
Macs-3.gif
7/31/2019 Mobile x Dge
72/89
68
Chapter 5 MOXRules Customisation
You can customise MobileXdge SMS/MMS/WAP Push Gateway according to
your business need by changing the database and its calling application. A
sample application is included in the installation of MobileXdge Gateway. If
you are using Visual Basic 6 as your development tools, the VB6 project file is
located in the folder \MOXRules. If you are using Visual Basic .Net 2005 as
your development tools, the VB.Net project file is located in the folder
\MOXRulesVBNet. If you are using C# .Net 2005 as your development tools,
the C#.Net project file is located in the folder \MOXRulesCSNet. Please notethat you will need to copy the compiled DLL into C:\mobilexdge folder for the
changes to take effect.
5.1 MOXRules VB6 Platform
Whenever there is new changes made to the MOXRules.vbp, you will need to
perform the following steps: -
Compile the MOXRules.vbp to MOXRules.dll.
Copy the MOXRules.dll into the C:\MobileXdge folder.
At the Command line, issue REGSVR32 C:\MobileXdge\MOXRules.dll.
Change the MOXRULES parameter to 3 in the config file
MobileXdge.cfg.
5.2 MOXRules VB.Net 2005/ C#.Net 2005 Platform
Whenever there is new changes made to the MOXRulesVBNet/MOXRulesCSNet
project, you will need to perform the following steps: -
If you are using VB.Net 2005: -
Compile the MOXRulesVBNet to MOXRulesVBnet.dll
7/31/2019 Mobile x Dge
73/89
69
Copy the MOXRulesVBnet.dll into C:\mobilexdge folder.
Change the MOXRULES parameter to 1 in the config file
MobileXdge.cfg.
If you are using C#.Net 2005: -
Compile the MOXRulesCSNet to MOXRulesCSnet.dll
Copy the MOXRulesCSnet.dll into C:\mobilexdge folder.
Change the MOXRULES parameter to 2 in the config file
MobileXdge.cfg.
5.3 MOXRules Functions
The MobileXdge SMS/MMS/WAP Push Gateway will execute the application
extension MOXRules.dll/ MOXRulesVBNet.dll/ MOXRulesCSNet.dll forsending or receiving messages, and email to SMS/WAP Push Messages, as
well as updating the database. Hence, you can create your own application
according to your need. Below a the functions needed for the MobileXdge
Gateway System to process.
5.3.1 GetSendLog(StationStatus)
This function will be called by the MobileXdge gateway to request from thecustomise application for any UN-send message/s. The StationStatus
parameter provides information on current queue of the MOX Stations. If there
are messages to be send, this function will return a string in one of the
following format:
SMS Return String Format:
Type Description Notation
Type I SMS Message SMS
7/31/2019 Mobile x Dge
74/89
70
Message Format :
Fields Data DescriptionSeparator | MobileXdge Message SeparatorPortX 0 to 24 MobileXdge MOX Station. 0 Auto
schedule.Separator ^ Field SeparatorMsgType SMS MobileXdge Message ClassificationSeparator ^ Field SeparatorMsgID 00001 The unique identifier of the message
Separator ^ Field SeparatorHPNo +6590128501 Mobile Phone NumberSeparator ^ Field SeparatorMessage Test SMS MessageSeparator ^ Field SeparatorSmartMsg 0/1 Smart Message Indication (True/False)Separator ^ Field Separator
SMSCStatus 0/1 SMSC Response Indication (True/False)Separator ^ Field Separator
Lang ENG Language identifierSeparator ^ Field SeparatorPriority 0/1 Priority Setting
|PortX^SMS^Message Index^Mobile Phone Numbers^Message^SmartMsg^SMSC^Lang^Priorty
Push Proxy Gateway Indicator String format:
Type Description NotationType II Push Proxy Gateway Indicator PPGIND
Message Format :
Fields Data DescriptionSeparator | MobileXdge Message Separator
PortX 0 to 24 MobileXdge MOX Station. 0 Autoschedule.
7/31/2019 Mobile x Dge
75/89
71
Separator ^ Field Separator
MsgType PPGIND MobileXdge Message ClassificationSeparator ^ Field SeparatorMsgID 00001 The unique identifier of the messageSeparator ^ Field SeparatorHPNo +6590128501 Mobile Phone Number
Separator ^ Field SeparatorPPG_Title MobileXdge Push Proxy Gateway TitleSeparator ^ Field SeparatorPPG_URL 210.193.11.1
9/wap.wml
The URL of the PPG WAP Push Message
Separator ^ Field SeparatorSMSCStatus 0/1 SMSC Response Indication (True/False)Separator ^ Field SeparatorLang UNI Language identifierSeparator ^ Field SeparatorPriority 0/1 Priority Setting
|PortX^PPGIND^Message Index^Mobile Phone^PPG Title^PPG URL^SMSC^UNI^Priorty
Multi Media Service Indicator String format:
Type Description NotationType III MMS Indicator MMSIND
Message Format :
Fields Data DescriptionSeparator | MobileXdge Message SeparatorPortX 0 to 24 MobileXdge MOX Station. 0 Auto
schedule.Separator ^ Field SeparatorMsgType MMSIND MobileXdge Message ClassificationSeparator ^ Field SeparatorMsgID 00001 The unique identifier of the message
Separator ^ Field SeparatorHPNo +6590128501 Mobile Phone Number
7/31/2019 Mobile x Dge
76/89
72
Separator ^ Field Separator
MMS_URL 210.193.11.19/promo.mms The URL of the MMS Message
Separator ^ Field Separator
SMSCStatus
0/1 SMSC Response Indication(True/False)
Separator ^ Field SeparatorLang UNI Language identifierSeparator ^ Field Separator
Priority 0/1 Priority Setting
|PortX^MMSIND^Message Index^Mobile Phone^MMS URL^SMSC^UNI^Priorty
Push Proxy Gateway String Format:
Type Description NotationType IV Push Proxy Gateway Message PPG
Message Format :
Fields Data DescriptionSeparator | MobileXdge Message SeparatorPortX 0 to 24 MobileXdge MOX Station. 0 Auto
schedule.Separator ^ Field SeparatorMsgType PPG MobileXdge Message Classification
Separator ^ Field SeparatorMsgID 00001 The unique identifier of the message
Separator ^ Field SeparatorHPNo +6590128501 Mobile Phone NumberSeparator ^ Field SeparatorPPG_Title MobileXdge Push Proxy Gateway TitleSeparator ^ Field SeparatorSourceFile
C:\test\ppg\test.wml
Directory of the PPG Message
Separator ^ Field SeparatorTransfer 0/1 0- FTP/ 1- File Copy
7/31/2019 Mobile x Dge
77/89
73
Separator ^ Field Separator
SMSCStatus 0/1 SMSC Response Indication(True/False)Separator ^ Field Separator
Lang UNI Language identifierSeparator ^ Field SeparatorPriority 0/1 Priority Setting
|PortX^PPG^Message Index^Mobile Phone^PPG Title^SourceFile^TransferMethod^SMSC^UNI^Priorty
Mobile Ticketing String Format:
Type Description NotationType V Mobile Ticketing Message MKT
Message Format :
Fields Data DescriptionSeparator | MobileXdge Message SeparatorPortX 0 to 24 MobileXdge MOX Station. 0 Auto
schedule.Separator ^ Field SeparatorMsgType MKT MobileXdge Message Classification
Separator ^ Field SeparatorMsgID 00001 The unique identifier of the messageSeparator ^ Field Separator
HPNo +6590128501 Mobile Phone NumberSeparator ^ Field SeparatorPPG_Title MobileXdge Push Proxy Gateway TitleSeparator ^ Field SeparatorSourceFile
C:\test\ppg\test.wml
Directory of the PPG Message
Separator ^ Field Separator
7/31/2019 Mobile x Dge
78/89
74
Ticket No 8888 Mobile Ticket Number
Separator ^ Field SeparatorTransfer 0/1 0- FTP/ 1- File CopySeparator ^ Field SeparatorSMSCStatus
0/1 SMSC Response Indication(True/False)
Separator ^ Field SeparatorLang UNI Language identifierSeparator ^ Field SeparatorPriority 0/1 Priority Setting
|PortX^MKT^Message Index^Mobile Phone^PPG Title^SourceFile^TicketNo^TransferMethod^SMSC^UNI^Priorty
Multi Media Service String Format:
Type Description NotationType VI MMS Message MMS
Message Format :
Fields Data DescriptionSeparator | MobileXdge Message SeparatorPortX 0 to 24 MobileXdge MOX Station. 0 Auto
schedule.Separator ^ Field Separator
MsgType MMS MobileXdge Message ClassificationSeparator ^ Field SeparatorMsgID 00001 The unique identifier of the messageSeparator ^ Field SeparatorHPNo +6590128501 Mobile Phone NumberSeparator ^ Field SeparatorSource File C:\test\ppg\tes
t.mmsDirectory of the MMS Message
Separator ^ Field Separator
Transfer 0/1 0- FTP/ 1- File Copy
7/31/2019 Mobile x Dge
79/89
75
Separator ^ Field Separator
SMSCStatus 0/1 SMSC Response Indication(True/False)Separator ^ Field Separator
Lang UNI Language identifierSeparator ^ Field SeparatorPriority 0/1 Priority Setting
|PortX^MMS^Message Index^Mobile Phone^SourceFile^Transfer Method^SMSC^UNI^Priorty
If there is no message to send, this function MUST return a string .
MobileXdge SMS/MMS/WAP Push Gateway will ONLY recognise the formats as
specified above in order for it to send out the message.
MM1 Multi Media Service String Format:
Type Description NotationType VII MM1 MMS Message MM1
Message Format :
Fields Data DescriptionSeparator | MobileXdge Message SeparatorPortX 0 to 24 MobileXdge MOX Station. 0 Auto
schedule.Separator ^ Field SeparatorMsgType MM1 MobileXdge Message ClassificationSeparator ^ Field SeparatorMsgID 00001 The unique identifier of the messageSeparator ^ Field SeparatorHPNo +6590128501 Mobile Phone NumbersSeparator ^ Field Separator
CC +6590128508 CC List of Mobile numbers. Multiplemobile numbers has to be seperated bycommas. Please note that a total
7/31/2019 Mobile x Dge
80/89
76
maximum of 20 mobile numbers can be
included in the CC and BCC List.Separator ^ Field SeparatorBCC +6590128509 BCC List of mobile numbers. Multiple
mobile numbers has to be seperated bycommas. Please note that a totalmaximum of 20 mobile numbers can beincluded in the CC and BCC List.
Separator ^ Field Separator
EncodeType
us-ascii or utf-8
The character set encoding. Supporteither us-ascii or utf-8
Separator ^ Field SeparatorSubject MM1 Title The subject of the messageSeparator ^ Field Separator
Files Multi-mediafiles
The multimedia files name andlocation. Multiple files have to beseperated by commas
Separator ^ Field SeparatorPriority 0/1 Priority Setting
|PortX^MM1^Message Index^Mobile Phone^CC^BCC^Encode Type^Subject^Files^Priorty
If there is no message to send, this function MUST return a string .
MobileXdge SMS/MMS/WAP Push Gateway will ONLY recognise the formats as
specified above in order for it to send out the message.
5.3.2 UpdateSendLog( MsgIndex, Status )
This function will be call by the SMS gateway to update the database of the
customise application. This is to indicate that the message of reference
was sent out successfully.
is of String data type, and
7/31/2019 Mobile x Dge
81/89
77
is of String data type with Length is 1. This Status is to be updated in
the MsgSent Table of the SMSLog database. The default is set to Y formessage that was sent successfully.
This function MUST return a string either OK for successful update in the
database, or ERROR if update process failed.
5.3.3 UpdateReceiveLog( MOXID, Sender, Language,Message, TimeStamp, BolUniCode )
This function will be call by the MobileXdge gateway to update the database
when a message is received by the MobileXdge gateway.
is the MOX Station ID, which the GSM/GPRS/CDMA Modems
connect. This ID will enable you to identify which modem the SMS message is
being received. This will allows the system to handles up to a maximum of 24
different business rules set.
is the mobile number of the sender of the message
is the language content of the text message received
is the text message received.
is the Date/Time of the message received
is the type of SMS message received
This function MUST return either OK if message is updated to the database,
or ERROR if its fail to update the database.
5.3.4 UpdateReceiveMMSLog( MOXID, TransactionID,Subject,location , Sender )
This function will be call by the MobileXdge gateway to update the databasewhen a MMS indicator message is received by the MobileXdge gateway.
7/31/2019 Mobile x Dge
82/89
78
is the MOX Station ID, which the GSM/GPRS/CDMA Modems
connect. This ID will enable you to identify which modem the SMS message isbeing received. This will allows the system to handles up to a maximum of 24
different business rules set.
is the unique MMS transaction ID from the telco.
is the subject of the MMS message
is the URL location of the MMS message at the telco.
is the mobile number of the sender of the message
This function MUST return either OK if message is updated to the database,
or ERROR if its fail to update the database.
5.3.5 RetrieveMMSLog( MOXID, Sender, Transaction
ID,Subject, MMS Content )This function will be call by the MobileXdge gateway to update the database
after MobileXdge gateway has downloaded the MMS content.
is the MOX Station ID, which the GSM/GPRS/CDMA Modems
connect. This ID will enable you to identify which modem the SMS message is
being received. This will allows the system to handles up to a maximum of 24
different business rules set.
is the mobile number of the sender of the message
is the unique MMS transaction ID from the telco.
is the subject of the MMS message
is the MMS content downloaded from the telco.
This function MUST return either OK if message is updated to the database,or ERROR if its fail to update the database.
7/31/2019 Mobile x Dge
83/89
79
5.3.6 UpdateErrorLog( Message )
This function will called by the SMS Gateway when there is failed messages.
is the message details. The content of the Message includes the
unique ID that allows the system to perform detail audit of the message.
This function MUST return either OK if message is updated to the database,
or ERROR if its fail to update the database.
5.3.7 UpdateUnScheduleLog(Message)
These functions will be called by the MobileXdge SMS/MMS/WAP Push
Gateway when the system is unable to find a port prefix which match the
mobile phone number. MobileXdge SMS/MMS/WAP Push Gateway will also try
to transmit the mobile messages out to the first available port.
is the message details the content of the Message includes the
unique ID that allows the system to perform detail audit of the message.
This function MUST return either OK if message is updated to the database,
or ERROR if its fail to update the database.
5.3.8 UpdateReportLog(MOXStation, ReportID,
Sender, TimeStampA,TimeStampB)These functions will called by the MobileXdge SMS/MMS/WAP Push Gateway
when the system is set to get the delivery report from the SMS Centre. Please
note that if you want to get the delivery report, you need to configure the
SMSCRESP to Y in the mobilexdge.cfg configuration file, and also set the
SMSC indicator to 1 in the outgoing message during the transmission of
messages.
7/31/2019 Mobile x Dge
84/89
80
Please note that the system will only get the delivery report only if the mobile
phone set is on. If the mobile phone set is off, there will be no any deliveryreport. For cross-telco messaging, TimeStampB is the time stamp of the
message has been delivered to the other telecom.
is the MOX Station in which the delivery report messages is
received.
is the message ID from the Telecom.
is mobile phone number in which the message has been sent.
is the time stamp in which the message reach the telecom.
is the time stamp in which the message reach the designated
mobile set.
This function MUST return either OK if message is updated to the database,
or ERROR if its fail to update the database.
5.3.9 UpdateSysStats(MX As String, Stn01 As String,Stn02 As String, Stn03 As String, Stn04 As String,Stn05 As String, Stn06 As String, Stn07 As String,Stn08 As String, Stn09 As String, Stn10 As String,Stn11 As String, Stn12 As String, Stn13 As String,Stn14 As String, Stn15 As String, Stn16 As String,Stn17 As String, Stn18 As String, Stn19 As String,Stn20 As String, Stn21 As String, Stn22 As String,Stn23 As String, Stn24 As String) As String
These functions will be called by the MobileXdge SMS/MMS/WAP Push
Gateway to return the status of the MobileXdge SMS/MMS/WAP Push Gateway
and its individual MOX stations.
7/31/2019 Mobile x Dge
85/89
81
is the status information of the MobileXdge SMS/MMS/WAP Push
Gateway. The status string consists of the following:-
S Number of messages Sent
R Number of messages received
F Number of messages failed to send
is the status information of each individual
GSM/GPRS/CDMA modem station returned by the MobileXdge SMS/MMS/WAPPush Gateway. The status string consists of the following:-
Q Number of messages in Queue
S Number of messages Sent
F Number of messages failed to send
E Estimated time to finish the broadcast
A Active status of the MOX modem stations
5.3.10 UpdateIndividualSentLog(Message)
This function will be call by the MobileXdge SMS/MMS/WAP Push gateway
whenever message has been successfully sent. This function provides a real-time timestamp of the message sent via the MOX Station.
5.3.11 GetEmail2SMS(Message)
This function will be call by the MobileXdge SMS/MMS/WAP Push gateway to
converts email Message to SMS or WAP Push Messaging. It can be
customised to retrieve the mobile numbers based on the email address within
the email received. In addition, the user can customise the functions to utilised
7/31/2019 Mobile x Dge
86/89
82
various fields like the Subject, content, From email address, and the To email
address field of the email content received.
5.3.11 CleanEmail4SMS(Message)
This function will be call by the MobileXdge SMS/MMS/WAP Push gateway to
filter off any unwanted data within the content of the email. This function
allows you to format the content of the email, which later will be converted to
SMS messaging.
7/31/2019 Mobile x Dge
87/89
83
Chapter 6 MobileXdge Components
6.1 MOXRules
MOXRules component is one of the most important components in
MobileXdge Gateway. It enables users to customised/configure/fine tune the
applications to the business requirements. There are three development
platforms for MOXRules: Visual Basic 6, Visual Basic.Net 2005 and C# .Net
2005. If you are using Visual Basic 6 as your development platform, the project
file can be found in the subfolder MOXRules within the installed folder. Aftercustomisation of the MOXRules, you need to save the file and recompile it to
MOXRules.dll. After compilation, you will need copy this updated version of
MOXRules.dll into C:\MobileXdge directory of the Server which MobileXdge
Gateway has been installed. You will need to issue REGSVR32
C:\MobileXdgeMOXRules.dll at the command line to re-register the
component. Please note that you need to change the MOXRULES parameter to
3 in the Mobilexdge.cfg.
If you are using Visual Basic.Net 2005 as your development platform, the
project file can be found in the subfolder MOXRulesVBNet. After
customisation of the MOXRulesVBNet, you need to save the file and recompile
it to MOXRulesVbNet.dll. After compilation, you will need to copy this updated
version of MOXRulesVBNet.dll into the installed MobileXdge Folder. Please
note that you need to change the MOXRULES parameter to 1 in the
Mobilexdge.cfg.
If you are using C#.Net 2005 as your development platform, the project file canbe found in the subfolder MOXRulesCSNet. After customisation of the
MOXRulesCSNet, you need to save the file and recompile it to
MOXRulesCSNet.dll. After compilation, you will need to copy this updated
version of MOXRulesCSNet.dll into the installed MobileXdge Folder. Please
note that you need to change the MOXRULES parameter to 2 in the
Mobilexdge.cfg.
7/31/2019 Mobile x Dge
88/89
84
6.2 MMSConvert
MMSConvert.dll enables you to create MMS Data file on the fly. You will need
to input a MMS header file, a SMIL or MOX file for the system to create the
MMS file. This file (.mms) will eventually be transmitted to the mobile users as
an MMS Message. This component is located in the Windows System
directory, named as MMSConvert.dll
You will need to define the below in VB6 project:-
Public MMSConvert As New MMSConvert.ClassGen
You can call the MMSConvert component as follows:-
MMSConvert.File2MMS(MMSHdr, MMSSmil_MOX, DirMMSOut.Path & "\" &
MMSOutputFile)
6.3 LangConvert
LangConvert.dll enables you to receive the SMS data and convert it to the
expected foreign language like Chinese Simplified, Chinese Traditional, Korea,
Japanese, Vietnam, Thai, etc. Please note that the different code pages are
located in the subfolder CodePage.
You can call the LangConvert component as follows:-
LangConvertObj.LangConvert(Codepage, ReceivedSMSData)
Codepages for all the foreign languages are located in the subfolder
Codepage of the installed directory of the MobileXdge gateway.
7/31/2019 Mobile x Dge
89/89
Chapter 7 Troubleshoot
7.1 GSM/GPRS/CDMA Modem Operation Indicator
The operation indicator (red light) situated beside the SIM cardholder should
be blinking after the GSM/CDMA modem is power on after a few seconds. If the
indicator is continuously grow after the GSM/CDMA modem is power on, there
are a few possibilities:
1. No SIM card was insert in the SIM cards holder of theGSM/CDMA modem; or the SIM card was not inserted properly inthe SIM cards holder.
2. Inserted SIM card is LOCKED. A Locked SIM card meant that ithad been presented the PIN1 code three times with a wrong code.The SIM card can only be unlock by using the PUK1 of the SIM
card. Please consult your SIM card operator for assistance.
3. The inserted SIM card required to presents the PIN1 code in orderto operate. Please set the SIM card Power On Password to OFFbefore inserting it to the SIM cardholder of the GSM/CDMAmodem. Refer to your mobile equipment (such as Mobile phone)manual for instruction.
4. The Inserted SIM card is damage. Please verify the SIM card with
mobile equipment such as a mobile phone, to check that it isfunctional.