|
Descriptions
The UltraWAVE SMS Email Gateway (SMEG) is a software application that provides bi-directional SMS to email support, allowing email messages to be sent to SMS recipients, and vice versa. The SMEG software may reside in the UW EMS Server or run on a standalone server.
The SMEG relays short messages and internet email messages between the UltraWAVE Short Message Center (SMSC) and the host email server. It links to the host email server and short message center via SMTP and SMPP respectively. UW Gateway routes email messages and short messages between them with appropriate format conversion.
The basic functions of the SMEG include:
To send an SMS message to an email recipient, the user includes the email address of the intended recipient as the beginning text of the MO SMS message in the following format:
1
|
Without subject:
|
[<to-address><space>]<Message>
|
2
|
With subject:
|
[<to-address><space>](subject)<message>
|
* The [ ] denote optional fields and < > delimit fields
Examples:
1
|
Without subject:
|
Short message "john@gateway.com This is a test message." will be sent to email recipient john@gateway.com with empty email subject and text contents "This is a test message."
|
2
|
With subject:
|
Short message "john@gateway.com (Test the UW Gateway)This is a test message." will be sent to email recipient john@gateway.com with the email subject "Test the UW Gateway" and text contents "This is a test message."
|
|
To send an SMS message to multiple email recipients, the user may include multiple email addresses beginning address field of the MO SMS message. Multiple addresses may be identified in MO SMS message by separating each address by a comma in the following format:
1
|
Without subject:
|
[<address1,address2,address3><space>]<Message>
|
2
|
With subject:
|
[<address1,address2,address3><space>](subject)<message>
|
|
When an SMS recipient receives an e-mail message via SMS, the received short message will appear in the following format:
1
|
Without subject:
|
[<from-address><space>]<Message>
|
2
|
With subject:
|
[<from-address><space>](subject)<message>
|
Examples:
Email
|
Sender:
|
john@gateway.com
|
Subject:
|
Test the UW Gateway
|
Contents:
|
This is a test message.
|
SMS received
|
john@gateway.com (Test the UW Gateway)This is a test message.
|
|
To reply to an email message, the SMS recipient must include the email sender’s address in the reply message to inform the UW Gateway where the message should be replied to for the UW Gateway to direct the message to the correct email recipient.
|
In order to avoid the SMS or email messages losing when the Gateway is down, the SMEG is designed to work in a master-slave mode. A critical alarm will be sent to the UW EMS to notify the operator when the master server is suspending. Then the slave server can be manually shifted to master to take over the SMPP and SMTP links.
Telnet the slave server and follow the procedures described as below to do the shift:
login: www
Password for www: 123456
[www@omc-0 ~]$ su -
Password:
//Enter the root password
[root@omc-0 ~]# cd /usr/local/omc/bin/
[root@omc-0 bin]# ./setRunMode
//Run the Mode Selection script
This is Slave server!!
+-------------------------+
| 1.Single OMC |
| 2.Dual OMC |
+-------------------------+
Please select OMC run mode:1
//Enter 1 to activate the SMEG process
[root@omc-0 ~]#
|
|
See Also
•SMEG Parameter Dictionary
•Configure SMS Email Gateway
Feature List
Feature
|
Descriptions
|
Capacity
|
50k BHSM
|
Interfaces
|
SMPP over TCP to SMSC
SMTP to host email server
SNMP to EMS
|
SMS to Email Service
|
Convert text messages received from SMSC in pre-defined format into email format and then forwards it to the email recipients through the host email server.
|
Email to SMS Service
|
Convert emails from the email server into text message and then forward it to the SMS recipients through the SMSC.
|
License Control
|
Application flag
0 to 50k at 1k BHSM
|
SMEG Parameter Dictionary
Parameter
|
Definition
|
Range
|
System
|
--
|
--
|
•License |
(Read Only) The maximum BHSM capacity of SMEG determined by License Control. SMEG will stop transiting SMS once the traffic reaches the maximum BHSM.
|
0 - 50K
|
•CC |
Country Code identifies the country's network.
|
Numeric max 4 digits
|
•NDC |
National Destination Code defines the national calling area or national network to which the subscriber belongs.
|
Numeric max 6 digits
|
•Max SMS per Email |
Define the maximum number of SMS can be concatenated per long email.
|
0 - 10
|
•Local Domain Name |
This name is the domain-part after the @ sign in the email address. This email address is used to transfer emails from email server to SMEG. Normally, it is the SMEG's host name.
|
--
|
•Domain Name for Email |
The domain name of email server is the domain-part after the @ sign in the email address. This email address is used to communicate emails between external email servers and the email server which connected with SMEG. It is the domain name which can be looked up in the public Domain Name System.
|
--
|
•Flag |
Enable or disable SMEG service.
|
•Enable •Disable |
Protocol
|
--
|
--
|
•SMPP Link Alias |
Alias of the SMPP link which corresponds to the link configured in EMS >Configuration >NSS >SMPP.
|
--
|
•SMTP Email Server IP |
The IP address of the email server.
|
Dotted decimal format
|
•SMTP Authentication Flag |
SMTP Authentication provides an access control mechanism. It is used to allow legitimate users to relay mail while denying relay service to unauthorized users, such as spammers. Configure the authentication parameters when it is enabled on the email server side.
|
•Enable •Disable |
•SMTP Authentication User |
User name for SMTP Authentication.
|
--
|
•SMTP Authentication Password |
Password for SMTP Authentication.
|
Numeric max 16 digits
|
Allowed User Prefix
|
--
|
Max 16 items
|
•Prefix |
Support up to 16 prefixes which determine the ranges of subscribers allowed to receive email messages.
|
Numeric max 16 digits
|
Return to
•Tasks List
•Elements List
2.1.1.8
|