SMS/MMS GATEWAY PRE-REGISTRATION
1 (5)
d:\116095282.doc
BI/PTM/SMS Platform
Configuration Owner November 2007
Version 3.0.5
SMS Platform – SMS/MMS Gateway Service, Registration
Form
All System Senders and Business Applications that need SMS/MMS Sending Service from
SMS Gateway needs to be registered.
This form along with the interface documentation and group sending guide is also available
at http://www.connecting.nokia.com/smsgw
CONTACT INFORMATION
The pre-registration details to be sent to: serviceadmin.sms-gw@nokia.com
Contact Person, Global Product Manager: kimmo.djupsjobacka@nokia.com
Table of Content
Contact information .............................................................................................................................. 1
1. General details ............................................................................................................................. 2
2. SMTP interface specific................................................................................................................ 3
3. HTTP interface specific ................................................................................................................ 3
4. Two Way Messaging or Mobile Originated Messaging ................................................................. 4
5. SPECIAL CASES ......................................................................................................................... 5
Owner:
SMS Platform Configuration Manager
Platform:
SMS Platform
Business Owner: SMS Platform Product Manager
Scope:
SMS-GW – Preregistration Form
Document
Version 3.0.6
Version:
and all previous versions
Location:
Pre-registration-Template.doc
Available in intranet:
http://www.connecting.nokia.com/smsgw
SMS/MMS GATEWAY PRE-REGISTRATION
2 (5)
d:\116095282.doc
BI/PTM/SMS Platform
Configuration Owner November 2007
Version 3.0.5
1. GENERAL DETAILS
Name of System or Business Application:
Business Unit:
Application Name and ID as in SCPR or SPT tools
AND the WBS-Code to be charged1
Business Owner, Application Owner or Service
Manager
Usage description:
A short description of SMS/MMS Service usage and what
your system does. Also a link to home-page if available.
Technical Contact person, SMTP-address:
Technical Contact person, phone-number:
Other contact persons/resource mailboxes to be
added to Information Distribution Group for SMS-Gateway
service breaks etc.
True sender identification:
How you want the sender to be presented in receiver’s
mobile phone when the message arrives. Can be
phonenumber or max 11 characters, no special
characters allowed.
Priority setting2:
Notification flag and destination:
If you want delivery notifications to be sent back for each
SMS, please indicate here to which SMTP-address or
URL you want the notifications to arrive.3
Estimation of amount of messages / month
Average message length (0 – 4000 chars)
Estimation of throughput needed msg/sec:
needed if your application sends lot of messages in one
batch
1
Please note that this information is mandatory and needed for usage charging.
If your application / service is not yet registered in those registers, please. do so first by following the BI SPT
instructions at: http://172.21.141.102/changerequest2.asp
If you can not provide a WBS code, contact SMS Platform Product Manager to agree which Cost Center will be
charged for sent messages.
2 Low = for bulk sending / Medium = default / High = for system alerts, configuration and other time critical
messages
3 The Delivery notifications can be delivered over SMTP as e-mails or over HTTP as XML-documents. For
HTTP/XML setup refer to delivery notification interface documentation
SMS/MMS GATEWAY PRE-REGISTRATION
3 (5)
d:\116095282.doc
BI/PTM/SMS Platform
Configuration Owner November 2007
Version 3.0.5
2. SMTP INTERFACE SPECIFIC
SMTP – Sender identification – FROM:
IT:
This is registered to identify your system. If you have huge
amount of servers/senders to be registered contact
configuration owner for advice
QA:
SMTP – Sender identification – Reply To: TAG:
IT:
(This TAG is recommended – Reply-To: tag can be
specified to increase the security aspects of sender
validation.)
QA:
Error reporting SMTP-address:
IT:
If not specified messages will currently be bounced to the
address in FROM: field of the message
QA:
PROD:
PROD:
PROD:
3. HTTP INTERFACE SPECIFIC
Identifier parameter4
APPLICATION_ID
HTTP – User name
(mandatory if Appliction_ID is not in use. You can
specify this yourself)
HTTP – password5
(mandatory if Appliction_ID is not in use. You can
specify this yourself)
4
HTTP interface users may choose between using an Application_ID as identifier or a username/password
the password must be at least 8 characters and not too simple. This can also be given by SMS-GW Service
Administrator.
5
SMS/MMS GATEWAY PRE-REGISTRATION
4 (5)
d:\116095282.doc
BI/PTM/SMS Platform
Configuration Owner November 2007
Version 3.0.5
4. TWO WAY MESSAGING OR MOBILE ORIGINATED MESSAGING
Identifier
INVOKING COMMAND – KEYWORD
The first word in the incoming message, based on which
the gateway will know which application to invoke
HTTP –URL to be contacted/invoked on your
application side
IT:
QA:
PROD:
TYPE of APPLICATION
PUBLIC or RESTRICTED
Public = allow any mobile user to send messages
Restricted = list gsmnumber of allowed users or define
that all users with phonenumber in NEDI are allowed to
send messages.
IF Application is RESTRICTED, choose type
1. incoming users to be looked up in NEDI
2. automatic registration; HTTP-credentials needed.
Contact Configuration Owner for details.
3. Provide list of users to be registered: gsmnum,
username
Lifetime
Time for a user to respond to the messages sent back
from Business application
=> Session Lifetime in seconds
Default= 1000000
Never expires=-1
Timeout
The timeframe in seconds within which the user has to
respond to a single dialogue question in the chain
Default=1000000
Never expires=-1
Reprocessing
Max times a request is reprocessed if Business
Application is unavailable. (re-try interval 30 minutes)
PARSETYPE, for details refer to the interface description
SMS/MMS GATEWAY PRE-REGISTRATION
5 (5)
d:\116095282.doc
BI/PTM/SMS Platform
Configuration Owner November 2007
1. XML (Default)
2. tidy converter from HTTP to XML
3. NOTES (Group Ware)
Encoding, for details, refer to the interface description
UTF-8
ISO-8859-1
ISO-8859-15
2-way phonenumber to be used
(filled in by Configuration Owner)
If there is a need for application specific incoming
phonenumber, please indicate so and provide
business reason for it.
5. SPECIAL CASES
Special Cases – to be agreed upon with the Configuration
Owner and SMS Platform Manager
Binary Flag
(Yes/No)
- Applicable only if the system sends binary messages,
please contact Configuration Owner
MMS Sending
(Yes/No)
- Applicable only if the system sends rich text content
messages, please contact Configuration Owner
Note limited coverage for MMS sending
Version 3.0.5