WIRELESS INFORMATION NETWORK LTD

WIN Gateway

Client Configuration Form

Client Name:

Project Number:

Distid:

Version: 1.0

Date:

Confidential

 Wireless Information Network Ltd.

The information contained herein is the property of the Wireless Information Network, and may not be copied, used or disclosed in whole or in part, except with the prior written permission of the Wireless Information Network.

Printed 29/10/18

Integration Document Revision History

Date / Version / Authors / Comments/Reasons For Change
1.0 / Initial Version

Updates of this, related documents, and samples are available at:

Table of Contents

1INTRODUCTION......

1.1Purpose of this Document......

1.2Scope......

1.3Abbreviations and Acronyms......

1.4Related Documents......

2Contact Details......

2.1Third Party......

2.2WIN......

3Communication Transport......

3.1Reports and Admin website......

3.2Connection Method......

3.3IP......

3.3.1Third Party IP Addresses Allowed to Connect......

3.3.2WIN IP Addresses......

3.4HTTP......

3.4.1HTTP TPBound......

3.4.2HTTP WINBound......

3.5FTP Site......

3.5.1WINBound......

3.5.2TPBound......

4Logical Protocol......

4.1Service Group Descriptions......

4.2Service ID Description......

4.3WIN Test Keyword......

4.4Default MT Message Expiry Time......

4.5TPBound Data Routing......

4.6WINBound Message types......

4.7Payload Types – for special WIN processing......

4.8NetworkID (Mobile Network Identifier)......

4.9CostID & charge bands......

4.10Static Spoofing......

4.11WAPPush settings......

4.12Priority......

4.13Volume Expectation......

WIN - ConfidentialPage 1Printed 29/10/18

WIN Gateway Client Configuration Form

1INTRODUCTION

1.1Purpose of this Document

The purpose of this document is to provide a blank form for completion.

A note of the database structures associated with sections of the form that the website must update is included.

The web developer implementing the forms as a website would do best to also read the internal WIN Design document that in particular describes the projects data structures.

1.2Scope

For guidance see the associated Client Configuration Guide document and User Guide document.

Section 2 is for the entry of the communication technique which will be common to all of the services. Section 3 is for the entry of the configuration data that is required for each service.

1.3Abbreviations and Acronyms

Acronym / Full Name
SMS / Short Message Service (commonly known as “text”)
WIN / Wireless Information Network plc
TP / Third Party. This a direct client of WINs. i.e. not a mobile phone end user.
TPBound / refers to communication from WIN to the third party.
This is typically mobile phone originated messages or delivery statuses.
WINBound / refers to communication to WIN from the third party.
This is typically requests for messages to be delivered to mobile phones.
FOC / Free of Charge (used in respect of cost to the mobile end user
PR / Premium Rate
SNR / Single Network Routed
OA Substitution / Originator Address Substitution, sometimes referred to as ‘spoofing’
UDH / User Defined Header
IMSI / International Mobile Subscriber Identity
MO / Mobile Originated SMS message i.e. A SMS message a customer has sent to a shortcode.
MT / Mobile Terminated SMS message i.e. A SMS message sent to a customer.

1.4Related Documents

Title
Client Users Guide
Client Configuration Guide

2Contact Details

2.1Third Party

Company Name
Commercial Contact
Telephone No(s)
Email Address
Technical Contact
Telephone No(s)
Email Address
Operations Department
Telephone No(s)
Email Address
Customer Services
Telephone No(s)
Email Address
Opening Hours

2.2WIN

Account Manager
Telephone No(s)
Email Address
Operations Department / Robin Merrifield
Telephone No(s) / 01494 750 500 (24hrs)
Email Address /

3Communication Transport

3.1Reports and Admin website

URL /
User
Password

3.2Connection Method

Internet
Leased Line

WINBound channel type:

FTP
HTTP

TPBound channel type:

FTP
HTTP

3.3IP

3.3.1Third Party IP Addresses Allowed to Connect

All incoming IP connections must be specified in terms of their IP addresses.

Each client can have up to a maximum of 6 specific IP addresses i.e. an IP range is not allowed.

Valid Client IP Addresses

It is essential that section 3.3.1 be completed.

3.3.2WIN IP Addresses

Outgoing connections from WIN will come from the following IP addresses:

195.74.152.201
195.74.152.28
195.74.152.29
195.74.152.30
195.74.152.34
217.171.111.dd*

It is essential that ALL of the above IP addresses are accepted as valid at the 3rd Party.

* To be advised at time of connection.

3.4HTTP

3.4.1HTTP TPBound

URL
USER
Password

3.4.2HTTP WINBound

Standard URL /
Standard URL (SSL) /
Dual ISP URL /
Dual ISP URL (SSL) /
User
Password
Enable Dual ISP Route (Yes/No)

3.5FTP Site

(Note subdirectories TPBound and WINBound from the default initial login directory will be used – see User Guide for more information)

3.5.1WINBound

To be provided by WIN:

WIN external IP or URL / srv1.win
User
Password

3.5.2TPBound

To be provided by the third party:

WIN external IP or URL
USER
Password

4Logical Protocol

4.1Service Group Descriptions

Service Group / Service Group Name
1
2
…

4.2Service ID Description

ServiceID / Service Group / Service Name / User Network Validation responsibility
( third party | WIN )
1* / WIN Test Service
2
…

If there is more than one TPBound HTTP URL then add a column to indicate which is the required URL.

*WIN Test Service ID – ServiceID 1 must implement the WIN Test Keyword (See below)

4.3WIN Test Keyword

The WIN Test Keyword MUST be setup for every 3rdParty. It enables WIN and the 3rdParty to prove the connectivity between the WIN and the 3rdParty.

WIN Test Keyword
3rd Party response verified (Yes/No)

4.4DefaultMT Message Expiry Time

ServiceID
DefaultMsgExpiryTimeOffsetInMinutes (integer or networks’ defaults)

4.5TPBound Data Routing

ServiceID / Network / Keyword(s) / Short Code

4.6WINBound Message types

Message Types

Please enter below the message type descriptions:

TypeID / Format Type / Description
1 / 1 / Heart Beat - *Not Used*
2 / 1 / Standard Text Message

4.7Payload Types – for special WIN processing

By default payload types will be interpreted as plain text.

For special payloads WIN will instruct how to make such requests as part of processing a completed application form. Please state the payload types required :

Payload Types / Required Yes/No
SMS Tone (Nokia) ( WIN ref. : 153)
SMS Graphic (Nokia) (WIN ref. : 154)
SMS Operator Logo (Nokia) (WIN ref. : 155)
Binary Payload with User Defined Header
8-bit UDH (WIN ref. : 11)
Binary Payload with no User Defined Header
8-bit without UDH (WIN ref. : 12)
WAPPush and bookmarks
International Mobile Subscriber Identity (IMSI)

4.8NetworkID (Mobile Network Identifier)

There is nothing to be completed in this section.

The NetworkID defines which network should be chosen to send a message.

The primary NetworkIDs are defined below.

NetworkID / DESCRIPTION
0 / Leased cost route
1 / Vodafone
2 / O2
3 / Orange
4 / T-Mobile
6 / Three #3

4.9CostID & charge bands

Routing Types:

1Premium Rate Message
2Free – Least Cost Routing
3Free – Least Cost Routing except with messages to T-Mobile phones routed on-network.
4Free - Single Network Routing
5Free - Single Network Routing except with messages to T-Mobile phones routed on-network.

If a routing type of 4 or 5 is requested then please also include the NetworkID in brackets.

CostID / Routing Type / Required Price
(pence) / Network Charge codes
(to be completed by WIN)
Voda / BT / Orange / T-Mobile / Three #3
1 / 4 / Free Bulk Dynamic OA substitute NW70
(Arrives as 89222 if not OA substituted) / - / - / - / - / -
2 / - / - / - / - / -
3 / - / - / - / -
4
5
6

4.10Static Originator Address (OA) substitution

Please enter the static Originator Address (OA) substitution of the source address of WINBound messages.

There is a maximum of 11 characters.

Network / OA Substitution

4.11Priority

To be jointly agreed with WIN

Priority / DESCRIPTION / WINPriority
(to be completed by WIN)
Not Yet Implemented

4.12Volume Expectation

Time Line / Number of Customers / Number of messages per Month / messages per second
at peak time
1 week
1 month
2 months
3 months
6 months
1 year
2 years

WIN - ConfidentialPage 1Printed 29/10/18

WIN Gateway Client Configuration Template