OneWay Multipart .pdf

File information

Original filename: OneWay_Multipart.pdf

This PDF 1.4 document has been generated by Writer / LibreOffice 3.5, and has been sent on on 12/11/2015 at 15:26, from IP address 37.46.x.x. The current document download page has been viewed 489 times.
File size: 51 KB (2 pages).
Privacy: public file

Download original PDF file

OneWay_Multipart.pdf (PDF, 51 KB)

Share on social networks

Link to this file download page

Document preview

MagtiCom OneWay Service
v.2.2.0 30.05.2012

MagtiCom customers can send MT (mobile terminated) messages to
sms-enabled users using MagtiCom OneWay Service.
This service is running on HTTP port 80.
VPN connection is required between MagtiCom host and client host.
All requests made by client must be URL-encoded.
Client can use either HTTP POST or GET in their requests.
Client can have one or more SMS short number (xxxx) or string name
which will be visible in from fiels of SMS.
Client will be provided by username, password, client_id. Also
with service_id for each short number.
OneWay Parameters:
username – client username provided by MagtiCom
password – client password provided by MagtiCom
client_id – unique client ID provided by MagtiCom
service_id – unique service ID provided by MagtiCom
to – subscriber msisdn
text – message text

Optional parameter:
coding – message character coding (0 – 7 bit gsm, 1 – 8 bit iso-88591, 2 – Unicode UCS2) Default coding is 0.
If message length is longer than standard sms (7 bit – 160 chars, 8 bit –
140, Unicode – 70), it will be splitted on few sms.

Return codes:
0000 - message_id : Operation successful. message_id is used in
message status tracking query.
0001 : Internal error
0003 : Invalid Request
0004 : Invalid query
0005 : Empty message
0006 : Prefix error
0007 : MSISDN error
Message Status Tracking:

username – client username
password – client password
client_id – unique client ID provided by MagtiCom
service_id – unique service ID provided by MagtiCom
message_id – unique message id returned with mt message
successfull send
Reply Codes:
0 - Undefined
1 - Delivered to phone
2 - Not Delivered to Phone
4 - Queued on SMSC
8 - Delivered to SMSC
16 – Not Delivered to SMSC.
Customer can check message status during next 24 hours. If after
24 hours reply will NOT be “1 - Delivered to phone”, this means
that this message will be removed from queue and will not be
delivered to subscriber. Customer can resend this message.
In case of successful operation customer will get answer:
0000 – 12345678
where 12345678 is Message ID.
Sending Unicode message:
Note: Not all handsets support Unicode messages!
To track status of this message customer must use following URL:

Document preview OneWay_Multipart.pdf - page 1/2

Document preview OneWay_Multipart.pdf - page 2/2

Related documents

oneway multipart
tr cse 2011 01
57143695 improving enterprise access security using rfid
kashflow effective accounting getting started guide v1
spc 3301

Link to this page

Permanent link

Use the permanent link to the download page to share your document on Facebook, Twitter, LinkedIn, or directly with a contact by e-Mail, Messenger, Whatsapp, Line..

Short link

Use the short link to share your document on Twitter or by text message (SMS)


Copy the following HTML code to share your document on a Website or Blog

QR Code

QR Code link to PDF file OneWay_Multipart.pdf