Bulksms V 3.0 File Upload Interface Guide V1.0 Client: Idea

BulkSMS v 3.
0
File Upload Interface Guide
v1.0
Client: Idea
Reference:BulkSMS3.0-File Upload Interface Guide1.0-Idea
Confidentiality Statement
Copyright © 2009-2010, Bharti Telesoft Ltd. All rights reserved. This product or document may not, in
whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium
or machine readable form, by any means electronic, mechanical, photographic, optic recording or
otherwise without prior consent, in writing, of the copyright owner. Statutory declaration under section
52A of the Copyright Act 1957.
i
Restrictions and Copyright Declaration
The information in this document is subject to change without notice and describes only the product defined in the introduction of this
documentation. This document is intended for the use of prospective Bharti Telesoft customers for the sole purpose of the agreement under
which the document is submitted. No part of it may be reproduced or transmitted in any form or means without the prior written permission of
Bharti Telesoft. The intended audience for this document is professional personnel, who assume full responsibility for using the document
appropriately. Bharti Telesoft welcomes customer comments as part of the process of continuous development and improvement of its
documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned
hardware or software products cannot be considered binding, but shall be defined in contextual specific eventual agreement made between Bharti
Telesoft and the customer.
However, Bharti Telesoft has made all reasonable efforts to ensure that the instructions contained in the document are adequate, sufficient and
free of material errors and omissions. Bharti Telesoft will, if necessary, explain issues, which may not be covered by the document. Bharti
Telesoft’s liability for any errors in the document is limited to the documentary correction of errors. Bharti Telesoft will not be responsible, in any
event, for errors in this document or for any damages, incidental or consequential, including monetary losses, that might arise from the use of this
document or the information in it.
This document and the product it describes are considered protected by Patent, Copyright and Trademark laws in accordance with relevant
Indian laws.
The only warranties for Bharti Telesoft products and services are set forth in the express warranty statements accompanying its products and
services. Nothing herein should be construed as constituting an additional warranty. Bharti Telesoft shall not be liable for technical or editorial
errors or omissions contained herein.
The Bharti Telesoft logo is a registered trademark of Bharti Telesoft Ltd. Other product names mentioned in this document may be trademarks of
their respective companies and they are mentioned for identification purposes only.
Copyright © 2009Bharti Telesoft Ltd. All rights reserved.
Document Overview ................................................................................................................................. 1
1.1 SCOPE ....................................................................................................................................................... 1
1.2 CONVENTIONS ............................................................................................................................................ 1
Introduction .............................................................................................................................................. 3
2.1 OVERVIEW ................................................................................................................................................. 3
File Upload Interface ................................................................................................................................ 5
3.1 FEATURES ................................................................................................................................................. 5
3.2 CREATING/CONFIGURING ADMINISTRATOR/LOGIN ACCOUNTS .................................................................... 5
3.3 FILE FORMATS FOR FILE UPLOAD INTERFACE ............................................................................................. 6

3.3.1 FILE FORMAT 1 FOR FILE UPLOAD INTERFACE ............................................................................................. 6
3.3.2 FILE FORMAT 2 FOR FILE UPLOAD INTERFAE................................................................................................ 9
3.4 OPERATIONS OVER FILE UPLOAD INTERFACE ............................................................................................ 12

3.4.1 LOGIN ...................................................................................................................................................... 12
3.4.2 FILE UPLOAD ............................................................................................................................................ 14
3.4.3 LOGOUT ................................................................................................................................................... 16
3.5 CHECKING JOB STATUS ........................................................................................................................... 17
3.6 DELETING/SUSPENDING JOBS .................................................................................................................. 18
3.7 ERROR CODES ......................................................................................................................................... 21

3.7.1 ERROR: 56 - AN INTERNAL ERROR OCCURRED ........................................................................................... 21
3.7.2 ERROR: 62 - MANDATORY PARAMETER MOB_NO IS INVALID OR MISSING ..................................................... 21
3.7.3 ERROR: 63 - MANDATORY PARAMETER TEXT IS MISSING ............................................................................. 21
3.7.4 ERROR: 64 - MESSAGE TYPE BINARY SPECIFIED, BUT UDH PARAMETER OR TEXT MISSING .......................... 21
3.7.5 ERROR: 65 - THIS ACCOUNT IS NOT AUTHORIZED TO SEND BINARY MESSAGES ............................................ 22
3.7.6 ERROR: 701 - TAG F: MISSING OR INVALID FORMAT TYPE ........................................................................... 22
3.7.7 ERROR: 702 - INVALID DELIVERY DATE OR FORMAT AT <LINE_NO>............................................................ 23
3.7.8 ERROR: 703 - <START> TAG DOESN’T EXIST ............................................................................................ 23
3.7.9 ERROR: 704 - LINE SHOULD NOT HAVE F: OR D: AT <LINE_NO>.................................................................. 23
3.7.10 ERROR: 706 - MESSAGE IS EMPTY AT <LINE_NO>............................................................................. 23
3.7.11 ERROR: 707 - MESSAGE LENGTH EXCEEDS MAX ALLOWED VALUE AT <LINE_NO> ............................. 24
3.7.12 ERROR: 715 INVALID VALIDITY PERIOD OR EXPIRED AT <LINE_NO> ................................... 25
iii
3.7.13 ERROR: 716 - FILE DOESN’T HAVE A <END> TAG ............................................................................. 25
3.7.14 ERROR: 718 - THERE SHOULDN’T BE ANY LINE AFTER <END> TAG ................................................... 25
3.7.15 ERROR: 721 - INVALID TAG $TAG AT <LINE_NO> ........................................................................... 25
3.7.16 ERROR: 723 - MESSAGE IS NOT BINARY THOUGH MESSAGE TYPE IS B............................................... 26
3.7.17 ERROR: 724 - MOBILE NUMBER TAG N: SHOULD NOT BE SPECIFIED AT LINE 1 .................................... 26
3.7.18 ERROR: 728 - ACCOUNT IS CROSSING THE RATE LIMIT <RATE_LIMIT> YOU ARE LEFT WITH ONLY
<REMAINING QUOTA> MESSAGES ....................................................................................................................... 26
3.7.19 ERROR: 729 - THE SCHEDULED DATE IS GREATER THAN THE ACCOUNT EXPIRY DATE!....................... 27
3.7.20 ERROR: 733 - ONLY 1,00,000 MESSAGES CAN BE UPLOADED PER JOB ............................................. 27
3.7.21 ERROR: 736 - VALIDITY PERIOD IS GREATER THAN 1 WEEK ............................................................... 27
3.7.22 ERROR: 737 - DUPLICATION OF TAG<TAG_NAME> ............................................................................ 27
3.7.23 ERROR: 738 - DELIVERY DATE IS GREATER THAN ONE YEAR AT <LINE_NO> ...................................... 28
3.7.24 ERROR: 740 - INVALID FORMAT 1 TYPE FILE .................................................................................... 28
3.7.25 ERROR 741 INVALID FORMAT 2 TYPE FILE ....................................................................................... 28
Document Change History .................................................................................................................... 29
Contact Us .............................................................................................................................................. 31
v
vi
vii
1
Document Overview
This chapter gives a brief introduction to the scope and organization of this manual.
1.1 Scope
This document describes the procedure to use various interfaces supported by Bulk SMS.
1.2 Conventions
Window/Screen/Button/Icon/Menu/Field All names as seen in the applications are written in

Names bold.
Examples:
 Click OK to continue.
 The New User window appears.
 Enter your login name in User Name.

Names of File/Section/Document/Path names are written in Italics.
Files/Sections/Documents/Folders/Para
meters Example:
Refer Information.doc for details.
Text to be Entered/Commands/Code Example:
C:> DOS
Command output Example:

User is successfully added.
Key Presses Example:
<Enter>, <Esc>
Source: Bharti Telesoft
 Warning Message
 Notes
Document Overview 1
Interface Guide: BulkSMS – 3.0
2 Document Overview
2
Introduction
2.1 Overview
Bulk Short Message Service (Bulk SMS), as the name suggests, is designed for mass
message delivery. An intermediary gateway between applications and the SMSC, Bulk Short
Message Service is designed to cater to high-volume, high-throughput requirements of
application-to-person (A2P) messaging over the mobile network. Bulk SMS accepts incoming
messages from authorized applications over interfaces such as FTP, CIMD, SMPP, HTTP
and based on predefined business rules directs the messages to the least congested SMSC
on the network. By balancing traffic over multiple SMSCs, Bulk SMS scales existing network
capacity, prevents network overloads and ensures secure, accelerated and optimized delivery
of application messages over the network.
Introduction 3
3
File Upload Interface
File Upload Interface supports manual submission of messages to Bulk SMS web interface.
Clients can manually upload a single message to multiple destinations or personalized
messages to multiple destinations. The message file has to be formatted in accordance with
predefined specifications. The product is intended for clients who can build up a text file
based on an existing database of recipients. As soon as the file is successfully transferred,
Bulk SMS responds with a job ID. The job ID could later be used for referring the status of
each message on the Bulk SMS GUI.
3.1 Features
Bulk SMS supports the following features over the File Upload Interface:
 Text Messaging
Clients can send text messages over the File Upload interface.
 Binary Messaging
Clients can send binary messages like a ring tone or a logo over the File
Upload interface.
 Single Message to Multiple Destinations
Clients can send a single message to multiple recipients over the File
Upload interface.
 Personalized Messages to Multiple Destinations
Clients can send personalized messages to multiple recipients over the File
Upload interface.
 Multi-lingual Messaging
Clients can send messages in English and other languages over the File
Upload interface.
 Deferred Delivery of Messages
Clients can schedule message delivery to a later date over the File Upload
interface.
 Content Filtering
Bulk SMS filters the message content for censored words.
3.2 Creating/Configuring Administrator/Login

Accounts
See Chapter 3 of Bulk SMS User Manual for information on creating/configuring

administrator/login accounts.
File Upload Interface 5

3.3 File Formats for File Upload Interface
Bulk SMS supports two message file formats:

 Format 1
 Format 2
These file formats are discussed below:
3.3.1 File Format 1 for File Upload Interface
Login account users can transmit a single message to multiple destinations using the file
format 1.
The following table lists the mandatory and optional parameters for the header and the body
in file format 1.
F Format Type M X 1
D First delivery O X Any valid future date in

attempt time format ddmmyyyyhhmiss
T Type of O X T (text), B (binary), U

Message – (Arabic)
Binary/Text/Ara
bic
U User Data O X Valid UDH (hex value

Header (for only)
Binary
Messages)
M Message M X Alphanumeric characters

Content excluding the tab
character and new line
V Message O X Numeric digits

Validity Period
Relative: 1 –
255
Absolute:
ddmmyyyyhhm
iss
C Data Coding O X 1 to 255

Scheme
I Protocol O X 1 to 255
Identifier
A Sender Name O X Max of 11 alphanumeric

to be sent characters.
6 File Upload Interface

along with the

message.
R Sender O X Max of 16 Numeric Digits.

Number to be
sent along with
the message.
<START> Denotes the X M First line in the body

beginning of a
block of mobile
numbers
<END> Denotes the X M Last line in the body

end of a block
of mobile
numbers
The syntax for specifying parameters is as follows:
Tag:Value
Example
 Format Type
F:1
 First Delivery attempt
D:31072001152000
D:12082001115500
 Type of message
T:T
T:B
Example of Format 1 File (with mandatory parameters only):
F:1 M:This is a test message

<START>
919845065683
919845032999
<END>
Specify optional parameters for the following message types:
Messages with Validity Period
 Specify a value for V.

The value of V can be specified in the following formats:

Absolute format
ddmmyyyyhhmiss
where, dd=date, mm=month, yyyy=year, hh=hour, mi=minute,
ss=second
Example
F:1 M:This is a test message V:25112005153000
<START>
919845065683
919845032999
<END>
Relative format
Numeric value in the range 0-255.
Example
F:1 M:This is a test message V:15
<START>
919845065683
919845032999
<END>
Messages for Deferred Delivery

Specify the First Delivery Attempt time for deferred message delivery.
Example
F:1 M:This is a test message D:25112005153000
<START>
919845065683
919845032999
<END>
Arabic Messages
Specify the following parameters to send an Arabic message:
 T:U
 C:8
Example
F:1
M:06340633064A06280633064A0628062806340633064A06280633062806
33064A06280633064A06280633064A062806340633064A06280633062806
280633064A06280633064A06280633064A06280633064A06280633062806
33063306280633064A06280633064A06280633064A06280633064A062806
3306280633064A06280633064A0628063406330628 T:U C:8
<START>
919845071843
919845447256

<END>
Binary Messages
Specify the following parameters to send a binary message like a ring tone or a logo:
 C=8
 U:(binary data header)
 T=B
Example
F:1
M:024A3A59059D8591BDBC0400391C938C32C2A82AC2AC2A82AC2AC2AC2A
C28C2AC2E834C2EC28828C28C2882828C28C28C24C28C2A8000
U:06050415810000 T:B
<START>
919845071843
919845447256
<END>
3.3.2 File Format 2 for File Upload Interfae
Login account users can transmit multiple messages to multiple destinations using the file
format 2.
The following table lists mandatory and optional parameters for the header and the body in
file format 2.
F Format Type M X 1
D First delivery O X Any valid future date in

attempt time format ddmmyyyyhhmiss
T Type of Message X O T (text), B (binary), U

– (Arabic)
Binary/Text/Arabi
c
U User Data X O Valid UDH (hex value only)

Header (for
Binary
Messages)
M Message X M Alphanumeric characters

Content excluding the tab character
and new line
V Message Validity X O Numeric digits

Period

Relative: 1 – 165
Absolute:
DdMmYyyyHhMi
Ss
N Destination X M MSISDN number

mobile Number
C Data Coding X O 1 to 255

Scheme.
I Protocol Identifier X O 1 to 255
A Sender Name to X O Max of 11 alphanumeric

be sent along characters.
with the
message.
R Sender Number X O Max of 16 Numeric Digits.

to be sent along
with the
message.
<STA Denotes the X M First line in the body

RT> beginning of a
block of mobile
numbers and
messages
<END Denotes the end X M Last line in the body

> of a block of
mobile numbers
and messages
The syntax for specifying parameters is as follows:
Tag:Value
Example
 Format Type
F:1
 First Delivery attempt

D:31072001152000
D:12082001115500
 Type of message
T:T
T:B

Example of Format 2 File (with mandatory parameters only)
F:2
<START>
M:This is a test message. N:919822312232
M:Hello! N:919855674421
<END>
Specify optional parameters for the following message types:

Messages with Validity Period
Specify a value for V. The value of V can be specified in the following formats:
Absolute format
ddmmyyyyhhmiss
where, dd=date, mm=month, yyyy=year, hh=hour, mi=minute,
ss=second
Example
F:2
<START>
M:Test message N:919845065683 V:25112005153000
M:Hello! N:919845032999 V:23122005153000
<END>
Relative format
Numeric value in the range 0-255.
Example
F:2
<START>
M:Test message. N:919845065683 V:15
M:Hello! N:919845032999 V:12
<END>
Messages for Deferred Delivery
Specify the First Delivery Attempt time for deferred message delivery.
Example
F:2 D:25112005153000
<START>
M:This is a test message N:919845065683
M:This is a test message N:919845032999
<END>
Arabic Messages
Specify the following parameters to send an Arabic message:
 T:U
 C:8

Example
F:2
<START>
M:06340633064A06280633064A0628062806340633064A06280633062806
33064A06280633064A06280633064A062806340633064A06280633062806
280633064A06280633064A06280633064A06280633064A06280633062806
33063306280633064A06280633064A06280633064A06280633064A062806
3306280633064A06280633064A0628063406330628 N:919845071843
T:U C:8
<END>
Binary Messages
Specify the following parameters to send a binary message like a ring tone or a logo:
 C=8
 U:(binary data header)
 T=B
Example
F:2
<START>
N:919845447256 U:06050415810000 T:B
N:919880085656 U:06050415810000 T:B
<END>
3.4 Operations over File Upload Interface
3.4.1 Login
Carry out the following steps to login to File Upload Interface:
 Connect to Bulk SMS Web Interface. The URL for connecting to Bulk SMS Web
Interface is as follows:
http://<ip_address>:<port>
where,
 ip_address refers to the IP address of Bulk SMS server.
 port refers to the HTTP port on the Bulk SMS server.
Example
http://172.16.1.12:91
Bulk SMS returns the following web page:

 Enter username and password.

 Select a language and click “Login”.
Bulk SMS returns the following screen:

3.4.2 File Upload

Carry out the following to upload a file over the File Upload Interface:
 Login to File Upload Interface. (See Section 3.4.1 of Bulk SMS Interface Guide for
more information).
 Click “Upload Job File”.

 Click “Browse”.

 Select the file that has to be uploaded.

The file has to be formatted in Format 1 or Format 2.
(See Section 3.3 of Bulk SMS Interface Guide for more information on File
Formats).
 Click “Upload”.
Bulk SMS returns the number of messages left, out of the quota assigned to the
login account and a job ID that can be used later to check job status.
(See Section 3.5 of Bulk SMS Interface Guide for more information on
Checking Job Status).
3.4.3 Logout
Click “Logout” on the Web Interface screen.
Bulk SMS returns the following screen:

3.5 Checking Job Status

Carry out the following steps to check the status of a job:
 Login to Bulk SMS GUI.
 Enter username and password, select the language, and click “Login”.
Bulk SMS GUI displays the following page.

 Click “Search”.
 Enter the job ID.

 Click “Search”.
This shows the status of the job.
3.6 Deleting/Suspending Jobs
You may need to delete/suspend jobs on occurrence of the following events:
 Incorrect messages are submitted to Bulk SMS.

 Messages are submitted before the scheduled time.
Carry out the following steps to delete/suspend a job:

 Enter username and password, select the language, and click “Login”.
Bulk SMS GUI displays the following page.

 Click “Job Controls”.

Bulk SMS GUI displays the following screen.

 Click “Suspend” to temporarily cease a job.

 Click “Resume” to restart processing a suspended job.
 Click “Delete” to discard a job submitted to Bulk SMS.
 You can suspend or delete a job only if Bulk SMS has not yet concluded it.

3.7 Error Codes
3.7.1 Error: 56 - An internal error occurred

Possible Reason
No specific reason.
Resolution for login account user

Web login account user should reload the job file.
(See Section 3.4.2 of Bulk SMS Interface Guide for information on uploading a job file).
3.7.2 Error: 62 - Mandatory parameter mob_no is invalid

or missing
Possible Reason
Web login account user has not specified the destination mobile number at all in the job file.
OR
Web login account user has not specified a valid MSISDN number for the destination
subscriber.

Web login account user should reload the job file with a valid MSISDN number for the
destination subscriber.
(See Section 3.3 of Bulk SMS Interface Guide for information on job file formats).
3.7.3 Error: 63 - Mandatory parameter text is missing

Possible Reason
Web login account user has not specified the content in the job file.

Web login account user should reload the job file with the message content.
3.7.4 Error: 64 - Message type binary specified, but UDH

parameter or text missing
Possible Reason
Web login account user has set the message type to binary (B), but has not specified the
UDH or the message content in the job file.

Web login account user should specify a valid UDH and binary message content, and reload
the job file.
(See Section 3.4.2 of Bulk SMS Interface Guide for information on file upload).
3.7.5 Error: 65 - This account is not authorized to send

binary messages
Possible Reason
Web login account does not have the privilege to send binary messages.

Contact the Admin account user to obtain permission for sending binary messages.
Resolution for Admin account user

If a login account user reports Error 65, admin account user should carry out the following
steps to allow binary messaging to the login account:

 Click “Edit” against the relevant login account.
 Change the ”Message Type” to “Binary”.
 Click “Done”.
Admin account user can allow binary messaging to a login account user only if the admin
account has the binary messaging privilege.
If the admin account does not have the privilege for binary messaging, admin account user
should contact the operator to obtain permission for binary messaging.
Resolution for operator

Operator should carry out the following steps to allow binary messaging to an admin account:

 Click “Edit” against the relevant package.
 Select “Binary” against “Message Type”.
 Click “Update Package and Accounts”.
3.7.6 Error: 701 - Tag F: missing or Invalid format type

Possible Reason
Web login account user has not specified the format type in the job file header.
OR
Web login account user has specified an invalid value for the format type in the job file
header.

Web login user should reload the job file with a valid format type (F:1 for file format 1 and F:2
for file format 2).

(See Section 3.3 of Bulk SMS Interface Guide for more information on Web file formats).
(See Section 3.4.2 of Bulk SMS Interface Guide for more information on file upload).
3.7.7 Error: 702 - Invalid Delivery Date or Format at

<line_no>
Possible Reason
Web login account user has specified an invalid delivery date in the job file.
Example:
31022006123000
OR
Web login account user has specified the delivery date in an incorrect format in the job file.

Web login account user should reload the job file with a valid date in the following format:
ddmmyyyyhhmiss
3.7.8 Error: 703 - <START> tag doesn’t exist

Possible Reason
Web login account user has not included the <START> tag in the body of the job file.

Web login account user should include the <START> tag at the beginning of the body of the
job file and reload the job file.
3.7.9 Error: 704 - Line should not have F: or D: at

<line_no>
Possible Reason
Web login account user has included header parameters F and/or D tag in the body of the job
file.

Web login account user should ensure that the body of the job file does not include F or D
tag, and reload the job file.
3.7.10 Error: 706 - Message is empty at <line_no>

Possible Reason

Web login account user has not specified the message content in the job file.

Web login account user should specify the message content in the job file and reload the job
file.
3.7.11 Error: 707 - Message length exceeds Max allowed

value at <line_no>
Possible Reason
The number of characters in the message content has exceeded the maximum allowed value.

 Ensure the number of characters in the message content does not exceed the
maximum allowed value.

 Check the value specified against “Maximum Message Size” under “Login
Account Details”.
 Ensure the number of characters in the message content does not exceed the
“Maximum Message Size”.
 Resend the message.
 If the number of characters in the message content cannot be reduced, contact
the admin account user to increase the maximum allowed message size for your
login account.
Resolution for admin account user

Admin account user should carry out the following steps to increase the maximum allowed
message size for a login account:
 Click “Edit” against the relevant login account.
 Modify the value against “Message Size”.
You cannot set the “Message Size” to a value greater than the “Maximum Message Size”
allotted to your admin account.
Contact the operator to increase the maximum allowed message size for your admin account.
Resolution for operator

Operator should carry out the following steps to increase the maximum allowed message size
for an admin account:

 Click “Edit” against the relevant package.

 Modify the value against “Message Size”.

 Click “Update Package and Accounts”.
3.7.12 Error: 715 Invalid Validity Period or expired at

<line_no>
Possible reason
Web login account user has specified an invalid validity period in the job file.

Web login account user should reload the job file with a valid validity period:
1-255 for relative validity period and a date in format ddmmyyyyhhmiss for absolute validity
period.
3.7.13 Error: 716 - File doesn’t have a <END> tag

Possible Reason
Web login account user has not included an <END> tag in the job file.l

Web login account user should include the <END> tag at the end of the body of the job file
and reload the job file.
3.7.14 Error: 718 - There shouldn’t be any line after <END>

tag
Possible Reason
Web login account user has included text after the <END> tag in the job file.

Web login account user should ensure that the <END> tag appears at the end of the job file
and reload the job file.
3.7.15 Error: 721 - INVALID TAG $tag at <line_no>

Possible Reason
Web login account user has specified an invalid value for the tag returned in the error code.

Web login account user should specify a valid value for the tag mentioned in the error and
reload the job file.

3.7.16 Error: 723 - Message is not binary though Message type

is B
Possible Reason
Web login account user has specified the message type as “B” for a message with text
content.

Web login account user should specify the message type as “T” and reload the job file.
3.7.17 Error: 724 - Mobile number tag N: should not be

specified at line 1
Possible Reason
Web login account user has specified the destination mobile number in the job file header.

Web login account user should specify the destination mobile number (tag “N”) in the job file
body and reload the job file.
3.7.18 Error: 728 - Account is crossing the rate limit

<rate_limit> you are left with only <remaining quota>
messages
Possible Reason
Web login account is about to exceed the total number of messages assigned to it.

Web login account user should contact the Admin user to renew the account.
Resolution for admin account user

If a login account user reports Error 728, admin account user should carry out the following
steps to renew the login account:

 Click the relevant login account.
 Click “Edit Login Account”.
 Modify the value against “Job Quota” as required.

3.7.19 Error: 729 - The scheduled date is greater than the

Account Expiry date!
Possible Reason
Web login account user has scheduled the message delivery at a date after the account
expiry date.

Verify the account expiry date on Bulk SMS GUI, and reload the job file with a
date prior to the account expiry date.
3.7.20 Error: 733 - Only 1,00,000 messages can be

uploaded per job
Possible Reason
Web login account user has uploaded a job file with more than 1,00,000 destination mobile
numbers.

Web login account user should ensure the total number of destination mobile numbers in one
job file does not exceed 1,00,000 and reload the job file.
3.7.21 Error: 736 - Validity period is greater than 1 week

Possible Reason
Web login account user has specified a date greater than 1 week for validity period in the job
file.

Web login account user should specify a date within one week from the current date for
validity period and reload the job file.
3.7.22 Error: 737 - Duplication of tag<tag_name>

Possible Reason
Web login account user has specified a certain tag more than once in the job file.

Web login account user should ensure that any tag does not appear more than once for one
entry in the job file, and reload the job file.
3.7.23 Error: 738 - Delivery date is greater than one year at

<line_no>
Possible Reason
Web login account user has scheduled the message delivery at a date after a period of more
than one year from the current date.

Web login account user should specify the delivery date within a period of one year from the
current date and reload the job file.
3.7.24 Error: 740 - Invalid Format 1 Type File

Possible Reason
Web login account user has specified the file format as 1 for a format 2 job file.

Web login account user should specify the correct value for the tag “F” in the job file and
3.7.25 Error 741 Invalid Format 2 Type File

Possible Reason
Web login account user has specified the file format as 2 for a format 1 job file.

Web login account user should specify the correct value for the tag “F” in the job file and

Document Change History
1.0 Initial Sutapa
Source: Bharti Telesoft
Document Change History 29

Contact Us
Delhi Headquarters
Bharti Telesoft Ltd.
F-13, Okhla Phase 1
New Delhi – 110020
Tel: +91 (0) 11 4161 1666
Fax: +91 (0) 11 4161 1777
Bangalore Office
Maruti Towers
138, Airport Road
Bangalore – 560 008
INDIA
Tel: +91 80 4030 1550
Fax: +91 80 4115 0552

th
#4, 12 Km Stone
Bellary Road, Jakkur
Bangalore – 560064
Tel: +91-80-28565852/53/08/09
Fax: +91-80-28565854
Mumbai Office
Unit No1234, Ist Floor
Paradigm Tower, Tower B
Mindspace, Off New Link Road
Malad-West – 400064
India
Tel: +91 22 40774300
Fax: +91 22 40774333
Contact Us 31

Bulksms V 3.0 File Upload Interface Guide V1.0 Client: Idea

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Bulksms V 3.0 File Upload Interface Guide V1.0 Client: Idea

Uploaded by

Copyright:

Available Formats

BulkSMS v 3.

1.1 SCOPE ....................................................................................................................................................... 1

1.2 CONVENTIONS ............................................................................................................................................ 1

2.1 OVERVIEW ................................................................................................................................................. 3

File Upload Interface ................................................................................................................................ 5

3.1 FEATURES ................................................................................................................................................. 5

3.2 CREATING/CONFIGURING ADMINISTRATOR/LOGIN ACCOUNTS .................................................................... 5

3.3 FILE FORMATS FOR FILE UPLOAD INTERFACE ............................................................................................. 6

3.4 OPERATIONS OVER FILE UPLOAD INTERFACE ............................................................................................ 12

3.5 CHECKING JOB STATUS ........................................................................................................................... 17

3.6 DELETING/SUSPENDING JOBS .................................................................................................................. 18

3.7 ERROR CODES ......................................................................................................................................... 21

Document Change History .................................................................................................................... 29

Window/Screen/Button/Icon/Menu/Field All names as seen in the applications are written in

 The New User window appears.

 Enter your login name in User Name.

Command output Example:

3.2 Creating/Configuring Administrator/Login

See Chapter 3 of Bulk SMS User Manual for information on creating/configuring

File Upload Interface 5

3.3 File Formats for File Upload Interface

Bulk SMS supports two message file formats:

3.3.1 File Format 1 for File Upload Interface

D First delivery O X Any valid future date in

T Type of O X T (text), B (binary), U

U User Data O X Valid UDH (hex value

M Message M X Alphanumeric characters

V Message O X Numeric digits

C Data Coding O X 1 to 255

A Sender Name O X Max of 11 alphanumeric

6 File Upload Interface

along with the

R Sender O X Max of 16 Numeric Digits.

<START> Denotes the X M First line in the body

<END> Denotes the X M Last line in the body

The syntax for specifying parameters is as follows:

Example of Format 1 File (with mandatory parameters only):

F:1 M:This is a test message

Specify optional parameters for the following message types:

Messages with Validity Period

 Specify a value for V.

File Upload Interface 7

Messages for Deferred Delivery

8 File Upload Interface

3.3.2 File Format 2 for File Upload Interfae

D First delivery O X Any valid future date in

T Type of Message X O T (text), B (binary), U

U User Data X O Valid UDH (hex value only)

M Message X M Alphanumeric characters

V Message Validity X O Numeric digits

File Upload Interface 9

N Destination X M MSISDN number

C Data Coding X O 1 to 255

I Protocol Identifier X O 1 to 255

A Sender Name to X O Max of 11 alphanumeric

R Sender Number X O Max of 16 Numeric Digits.

<STA Denotes the X M First line in the body

<END Denotes the end X M Last line in the body

The syntax for specifying parameters is as follows:

 First Delivery attempt

10 File Upload Interface

Specify optional parameters for the following message types: