Now SMS/MMS Gateway v5.0 http://www.nowsms.com

More documents

Recommendations

Info

“Server Host Name” specifies the TCP/IP address or host name of the UCP/EMI server. “Server Port” specifies the TCP/IP port on the UCP/EMI server to which the gateway should connect. “User Name” specifies the user name for the gateway to use when connecting to the UCP/EMI server. “Password” specifies the password for the gateway to use when connecting to the UCP/EMI server. Note: Some UCP/EMI systems may not require a username and password, and validate your account based only on the TCP/IP address of your system. If the username and password fields are left blank, the gateway will not send a UCP- 60 bind message to the server to login. Now SMS/MMS Gateway v5.0 19
“Local Port”, if set, should be set to the value of a TCP/IP port number on the gateway PC. If set, the gateway will initiate all connections to the UCP/EMI server from this port. “Sender Address” specifies the default sender address (phone number) to apply to outbound SMS messages. The UCP/EMI server may override this setting. Check “Allow Sender Address Override” if you want to allow messages submitted to the gateway to be able to specify a sender address. If this box is checked, and a sender address is present in a message being submitted to an UCP/EMI based SMSC, the sender address in the message will be submitted to the SMSC. The UCP/EMI server may override this setting. Some UCP/EMI servers may require that clients submit keep-alive messages to the server every so many seconds or minutes, or the server will time out the connection. To enable keep-alive messages, specify a value in seconds for the “Keep-Alive” setting. (Note: The gateway uses a UCP-31 message for the keep-alive message.) Check the “Enable Receive Messages” box if you wish to receive messages from the UCP/EMI server. When this box is checked, the gateway can either receive messages using a single connection to the UCP/EMI server, or the “Receive Port” setting can specify a TCP/IP port number on the gateway PC that will listen for connections from the UCP/EMI server, and receive messages. (Note: The “Receive Port” should be left blank for most configurations. This setting should only be specified if the UCP/EMI service provider will initiate connections to your server when it has a message to deliver, which is a rare configuration. Most service connections require that your server initiate all connections to the service provider, and the “Receive Port” setting is not used in those configurations.) Check the “Receive MMS Messages” box if you will be receiving MMS Notification messages via the SMSC. Note that not all service providers support the routing of MMS notification messages via an SMSC connection. If MMS messages will be received via the SMSC connection, it is necessary to also configure additional MMS settings. The “MMS Settings” dialog will display a dialog with additional configuration settings that are required for enabling the gateway to be able to receive MMS messages from the operator network. For additional configuration information on processing received MMS messages, please refer to 2-Way MMS Support. The “Routing” group of options is used when multiple SMSC connections are defined to the gateway. These options define what messages should be routed to this connection. The Routing options are common to SMPP, GSM Modem, Now SMS/MMS Gateway v5.0 20
Page 1 and 2: Now SMS/MMS Gateway v5.0 http://www
Page 3 and 4: 2-WAY SMS SUPPORT..................
Page 5 and 6: Supports Unicode (UTF-8) formats fo
Page 7 and 8: GSM Modems A GSM modem can be an ex
Page 9 and 10: Select an available modem and press
Page 11 and 12: If the Now SMS/MMS Gateway should p
Page 13 and 14: “SMPP Version” specifies the ve
Page 15 and 16: The Now SMS/MMS Gateway uses intell
Page 17 and 18: “Host Name” specifies a DNS hos
Page 19 and 20: @@UDHBin@@ @@PID@@ @@PIDdecimal@@ @
Page 21: UCP/EMI SMSC The gateway supports t
Page 25 and 26: CIMD2 SMSC The gateway supports the
Page 27 and 28: Check “Allow Sender Address Overr
Page 29 and 30: service. Note that if the gateway s
Page 31 and 32: If “Support any outbound message
Page 33 and 34: The “Event Log” button displays
Page 35 and 36: The PC that is running the gateway
Page 37 and 38: If you want to enable sending limit
Page 39 and 40: “User Name” and “Password”
Page 41 and 42: Web Menu Interface When the menu dr
Page 43 and 44: Send Text Message To send a text me
Page 45 and 46: To send a Nokia ring tone, you must
Page 47 and 48: Nokia Operator logos are one of the
Page 49 and 50: fields which are included as URL pa
Page 51 and 52: Send MMS Message It no longer requi
Page 53 and 54: Send WAP Multimedia Message The “
Page 55 and 56: Settings are operator specific, so
Page 57 and 58: Send OMA OTA Settings The gateway s
Page 59 and 60: Send XML Settings Document The “S
Page 61 and 62: Sending Text Messages To send a tex
Page 63 and 64: Sending Binary Messages To send a b
Page 65 and 66: Sending WAP Push Messages To send a
Page 67 and 68: Sending WAP OTA Messages To send a
Page 69 and 70: OTA_CSD_CALLTYPE - maps to TYPE=ADD
Page 71 and 72: Sending OMA Provisioning Content OT
Page 73 and 74:
It is also possible to send Provisi
Page 75 and 76:
http://127.0.0.1:8800/?PhoneNumber=
Page 77 and 78:
file and include any referenced fil
Page 79 and 80:
The MMSC Messaging Server built int
Page 81 and 82:
standard SMTP port number is 25, an
Page 83 and 84:
To define a user to use the MMSC, y
Page 85 and 86:
Now SMS/MMS Gateway v5.0 82
Page 87 and 88:
The “VoiceMail” parameter can b
Page 89 and 90:
terminology of the gateway, this fi
Page 91 and 92:
2-Way MMS Support Support for proce
Page 93 and 94:
"Route via MM7" - MM7 is an XML/SOA
Page 95 and 96:
“Account Name” specifies a logi
Page 97 and 98:
“Standard MMS Delivery” means t
Page 99 and 100:
Now SMS/MMS Proprietary URL Submiss
Page 101 and 102:
MM7 Before submitting a message via
Page 103 and 104:
R0lGODdhZAAwAOMAAAAAAIGJjGltcDE0OOf
Page 105 and 106:
The MM4/SMTP dialog looks something
Page 107 and 108:
EAIF Before submitting a message vi
Page 109 and 110:
When a GSM phone or GSM modem recei
Page 111 and 112:
The “MMS Settings” dialog speci
Page 113 and 114:
When the Now SMS/MMS Gateway receiv
Page 115 and 116:
By default, the Now SMS/MMS Gateway
Page 117 and 118:
transmitted via the MMSC connection
Page 119 and 120:
For most GSM/GPRS modems, it is not
Page 121 and 122:
When defining a VASP account that i
Page 123 and 124:
Data Same as “Text” parameter n
Page 125 and 126:
OTA_PROXY OTA_PROXY_TYPE OTA_PROXY_
Page 127 and 128:
Technical Bulletins This section co
Page 129 and 130:
MsgCount=#### (number of recipients
Page 131 and 132:
To=RecipientPhoneNumber MessageID=S
Page 133 and 134:
To configure the Now MMSC to read t
Page 135 and 136:
typically includes the username tha
Page 137 and 138:
2-Way SMS Returning a Non-Text Resp
Page 139 and 140:
(“http://127.0.0.1:8800/?PhoneNum
Page 141 and 142:
How to Disable Socket Pooling http:
Page 143 and 144:
Faster GSM Modem Speeds with SMS ov
Page 145 and 146:
Routing MMS Notifications via a WAP
show all

Now SMS/MMS Gateway v5.0 http://www.nowsms.com

Create successful ePaper yourself

Delete template?

Save as template?