System Requirements Notice Regarding Content Types, Naming, Size and Format Notice Regarding Sender Information Usage Notice Regarding Reporting MMS Soap Api Sample Codes

User Information Control Notice Regarding GSM Number Format Notice Regarding MMS Sending Method (SendMMS) Error Codes

General

Mobildev Web Service is developed for enabling client end requests to be sent to Mobildev Service –which has a physical three layer architecture- according to certain standards. These requests utilize XML technology and HTTP protocol.

Software developers can access the service at  http://gateway.mobilus.net/mms/mmsws.asmx

System Requirements

Following is the minimum system requirements list in order to use Mobildev MMS SOAP API:

• Windows 98 SE, ME, 2000, XP, 2003, Linux, UNIX or MAC OS

• Internet Explorer 6 SP1 (for Windows Platform)

User Information Control (getUserInfo)

Before starting with sending SMS, SMS user information control must be carried out. If you don’t have a current SMS account please dial +90 216 444 0 554 to obtain a test account from Mobildev Customer Services.

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<getUserInfo xmlns="http://gateway.mobilus.net/mms/">
<UserName>test</UserName>
<CompanyCode>mb1000</CompanyCode>
<Password>1234</Password>
</getUserInfo>
</soap:Body>
</soap:Envelope>

Values Sent
SetUsername: refers to user name associated with your Mobildev SMS account.
SetPassword: refers to password for your SMS user name.
CompanyCode: refers to your channel code associated with your Mobildev SMS account.

Return Values

1. If Successful:

<MMSRoot>
<Status>00</Status>
<ReturnData>
<Credit>1234567</Credit>
<OriginatorList>
<Originator>Originator1</Originator>
<Originator>Originator2</Originator>
</OriginatorList>
</ReturnData>
</MMSRoot>
Credit: Current credit balance of the user account
OriginatorList: Sender Information List of the user account.


2. If Unsuccessful

   <MMSRoot>
<Status>01</Status>
</MMSRoot>

   Status is the error code returned. For more info please check Error Codes Section.

Notice Regarding Content Types, Naming, Size and Format

File Naming must comply with OMA standards. No Turkish characters are allowed.

Notice: Allowed letters and characters are [A-Z], [0-9], _, - , . Space character is not allowed!

The following is the list we recommend and what the system supports:

image/gif

image/jpeg

text/plain

audio/amr

audio/midi

audio/3gpp

video/3gpp

audio/mp3

audio/synthetic formats: (midi, smaf[1-3])

Notice: It is obligatory to specify AAC, audio, video will be sent during definition. It is necessary information while the definition is made!

Content Size:
For the optimum conversion we reach, the recommended maximum message size is 100 K. This is the size of the entire message, it can contain smil, multiple gif and etc.

Notice: When the size of the message exceeds 100 K, it will increase the risk of quality deterioration and/or cause inability to download on cell phones with lower capacity!

Accuracy Of Content:
For the accuracy of the content, third party is responsible. As an example, no corrections will be made on Turkcell side for content with garbage character in header and footer area, corrupt content, incorrect file extension usage. For these matters, content provider will be responsible.

Matters Related To The Content:
Image: Resolution must be as the following:
• Landscape- 320x240
• Square- 240x240

Notice: If there are multiple images in the content, it is recommended to keep the image resolutions at 160x120 with 10 Kb size.

Animated gif:
The following table shows the recommended maximum slide number for each of the animated gif content.

Source Resolution	MMS Size Group	Maximum Number of Frames
Up to 128X128	100Kb	15 frames
128X128 to 176X208	100Kb	10 frames

Notice: Recommended message size is 100 K. For higher resolution, size and frame number will change!

Audio Format:

Audio Format	MMS Size Group	Audio Parameters
NbAMR	100Kb	12,2 kbps, 8 KHz, 16 bps
mp3	100Kb	64 kbps, 32 KHz, 16 bps, stereo
mp3	100Kb-300Kb	128 kbps, 48 KHz, 16 bps, stereo
AAC	100Kb-300Kb	128 kbps, 48 KHz, 16 bps, stereo

Notice: Recommended message size is 100 K.

Video Format:
Must not exceed 30 seconds.
- Average bitrate must be 128 kbps.
- Resolution must be 176 x 144.
- Must support 15 frames.
- Preferred input format:

• 3gp file format
• Video codec: mpeg4
• Audio codec: aac

Text Format:
A slide, consisting of text should not exceed 6 lines. If not, the exceeding part will be spread to the other slides

Notice: Text on each slide must be limited to 18-30 words to avoid subscriber to scroll again and again.

SMIL
As well as other content of an MMS, it is recommended that it also contains SMIL presentation.
- Must comply with SMIL standard: (OMA 1.1, OMA 1.2)

• Content name must be referenced within SMIL.
• Region definitions in the frame must be designed in such a way that they will not fair.
• Each object in SMIL must be associated with a defined region.
• MMS/SMIL layout/region definitions on each slide must comply with OMA. There must be Layout and 2 regions defined per slide and the regions must be Image&text where necessary.
• Each slide (it if contains more than one object) is limited with the following
  • Image ve text
  • Image ve audio
  • Image, audio, ve text
  • Audio ve text
  • Video ve text

- It is recommended that SMIL is made up of maximum 7 slide numbers.

SMIL Content:
In SMIL, video and text could be referenced in a multi-slide –in cases where text and video are on separate slides-. In this case, slide with text content must come first and then the video.

• In SMIL if there is referencing to both image and text at the same time in a slide the text should not exceed 3 lines. Otherwise, text will overlap to other slides.
• If in a slide, an animated gif is referenced, the period of the slide must be adjusted according to the actual animated gif.
• If an animated gif contains only text, then the recommended period is 6 seconds

Notice Regarding GSM Number Format

GSM numbers must be formatted as 05321234567, 5321234567, 905321234567 and written within Numbers parameter node.

Notice: MMS recipient numbers should be formatted as “5321234567”, without the prefixes like “0”, “90”, “0090”!

Notice Regarding Sender Information Usage (Originator)

Sender Information (Alphanumeric/Originator), is the sender name in the messages. This name is 11 characters long and is company dependant.  While sending, the exact sender information –provided by the activation unit during account activation- must be quoted within the Originator Parameter node. 02 Error Code will be returned should Sender Information does not match. Error Code 02 means that the Originator information is not defined.

Notice: The Originator statement cannot contain Turkish characters and  &, <, >, -, ( ), [ ], / signs.

Notice Regarding MMS Sending Method (SendMMS)

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<SendMMS xmlns="http://gateway.mobilus.net/mms/">
<UserName>test</UserName>
<CompanyCode>mb1000</CompanyCode>
<Password>1234</Password>
<Originator>MOBILDEV</Originator>
<Subject>CELEBRATION</Subject>
<GSMNumbers>05321234567</GSMNumbers>
<FileName>string</FileName>
<FileData>base64Binary</FileData>
<SDate>2012-12-31</SDate>
</SendMMS>
</soap:Body>
</soap:Envelope>

Values Sent
Username: refers to user name associated with your Mobildev SMS account..
Password: refers to password for your SMS user name
Originator: Refers to the sender user name that will be displayed on recipient’s device.
Subject: Refers to the MMS header information to send. Maximum 100 characters.

GSMNumbers: Refers to the GSM Numbers List that will receive MMS. In this section, the GSM numbers must be sent via XML!

XML Sample
<GSMNUMBERS>
<GSM>5321234567</GSM>
<GSM>5331234567</GSM>
</GSMNUMBERS>
FileName: refers to the file name field. As file type and file name –that MMS is attached to- is written and displayed by some of the phones –thus file name visible to the user- it is important.
FileData: Byte state of the file to send. As an example: System.IO.File.ReadAllBytes("C:\mms\birthday.gif")
SDate: refers to the date information that the MMS will be sent. Valid format is yyyy-mm-dd hh:mm:ss.ms
Example: 2012-10-01 13:59:59.000

Return Values

If successful:

<MMSRoot>
<Status>00</Status>
<ReturnData>
<ID>26</ID>
</ReturnData>
</MMSRoot>
Status 00 is the operation successful information. If the status information is other than 00, no ReturnData information will be returned. And status value gets one of the error values. Please refer to Error Codes Section.

Notice Regarding Reporting

Reporting (GetReport)
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<getReport xmlns="http://gateway.mobilus.net/mms/">
<UserName>test</UserName>
<CompanyCode>mb1000</CompanyCode>
<Password>1234</Password>
<ID>26</ID>
</getReport>
</soap:Body>
</soap:Envelope>

Username: refers to user name associated with your Mobildev SMS account
Password: refers to password for your SMS user name.
CompanyCode: refers to your channel code associated with your Mobildev SMS account.
ID: refers to the Package ID for the MMS sent.

Return Values
<MMSRoot>
<Status>00</Status>
<ReturnData>
<GSMNo>00905321234567</GSMNo>
<Status>1</Status>
<GSMNo>00905331234567</GSMNo>
<Status>2</Status>
</ReturnData>
</MMSRoot>
Status 00 is the operation successful information. If the status information is other than 00, no ReturnData information will be returned. And status value gets one of the error values. Please refer to Error Codes Section.

In ReturnData, GSMNo refers to the GSM Number information and Status refers to the status of the MMS.

• Status 1; not delivered
• Status 2; sent to Turkcell, waiting
• Status 0; delivered

Reporting For A Period Of Time (getReport)

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<getReport xmlns="http://gateway.mobilus.net/mms/">
<UserName>test</UserName>
<CompanyCode>mb1000</CompanyCode>
<Password>1234</Password>
<SDate>2012-01-01</SDate>
<EDate>2012-01-31</EDate>
</getReport>
</soap:Body>
</soap:Envelope>

Username: refers to user name associated with your Mobildev SMS account
Password: refers to password for your SMS user name.
CompanyCode: refers to the channel code associated with your Mobildev SMS account.

SDate: refers to the starting date of the report. Valid format: yyyy-mm-dd hh:mm:ss.ms Example: 2012-10-01 13:59:59.000

EDate: refers to the ending date of the report. Valid format: yyyy-mm-dd hh:mm:ss.ms Example: 2012-10-01 13:59:59.000

 

Error Codes

Error Code	Description
00	Operation successful
01	Incorrect User Name
02	User’s MMS account is not defined or undefined originator while sending MMS
03	Subject cannot be left blank
04	Subject cannot exceed 100 characters
05	Incorrect GSM Numbers XML
06	Insufficient credits
07	Filename cannot be left blank
08	File type is not of the supported types
09	File Data is empty
10	File size cannot exceed 300 KB
11	No or incorrect ID for the report
99	Unidentified Error

MMS SOAP API Sample Codes

ASP Script

C# Project