Sending an SMS using HTTP

Overview

The MX Telecom SMS Gateway allows SMS messages to be sent using HTTP. This page details the format of the HTTP requests which can be made to the MX Telecom SMS Gateway for less-common types of messages.

Contents

• Ericsson WAP Configurations
• Nokia WAP Configurations
• WAP Bookmark
• Nokia Ringtone
• EMS Ringtone
• Nokia Operator Logo
• Nokia Group Logo
• Nokia Picture Message
• EMS Picture Message
• WAP Push Service Loader
• WAP GSM CSD Configuration

For details on sending more common message types, please click here.

Ericsson WAP Configurations

Parameter	Description
otatype	Set to "ERICSSON"
profile_name	The profile's name
home_page	URL for the home page
home_page_title	Title for the home page
dial_up_number	Number to dial
ip_address	Static IP address
username	Username
password	Password
data_call_type	"ISDN" or "ANALOGUE"

The example below shows a typical HTTP request for a message of this sort:

http://sms.mxtelecom.com/SMSSend?user=myusername&pass=myusername&smsto=44778148446
  &smsfrom=configurationsender&otatype=ERICSSON&profile_name=my+profile
  &home_page=http%3A%2F%2Fwww.myhomepage.com%2F&home_page_title=my+home+page+title
  &dial_up_number=0800+123+456&ip_address=127.0.0.1&username=mywapusername
  &password=mywappassword&data_call_type=ANALOGUE&report=7

An example HTML form for this message type can be found here.

Nokia WAP Configurations

Parameter	Description
otatype	Set to "NOKIA"
profile_name	The profile's name
home_page	URL for the home page
home_page_title	Title for the home page
dial_up_number	Number to dial
ip_address	Static IP address
data_call_speed	"9600", "14000" or "AUTOBAUD"
username	Username
password	Password
gprs_accesspointname	Indicates the Access point name on Gateway GPRS Support Nodes.
data_call_type	"ISDN" or "ANALOGUE"
connection_type	CONT - Continuous TEMP - Temporary CONTSEC - Continuous Secure TEMPSEC - Temporary Secure
bearer_type	"DATA" or "GPRS"
authentication_type	PAP - Normal CHAP - Secure

The example below shows a typical HTTP request for a message of this sort:

http://sms.mxtelecom.com/SMSSend?user=myusername&pass=mypassword&smsto=44778148446
  &smsfrom=configurationsender&otatype=NOKIA&profile_name=myprofile
  &home_page=http%3A%2F%2Fwww.myhomepage.com%2F&home_page_title=my+home+page+title
  &dial_up_number=0800+123+456&ip_address=127.0.0.1&username=mywapusername
  &password=mywappassword&data_call_speed=AUTOBAUD&data_call_type=ISDN
  &connection_type=CONT&bearer_type=DATA&authentication_type=PAP

An example HTML form for this message type can be found here.

WAP Bookmark

Parameter	Description
wap_bookmark_type	Set to "NOKIA" or "ERICSSON"
wap_bookmark_name	Name of the WAP bookmark
wap_bookmark_url	URL for the WAP bookmark

The example below shows a typical HTTP request for a message of this sort:

http://sms.mxtelecom.com/SMSSend?user=myusername&pass=mypassword&smsto=44778148446
  &smsfrom=BookmarkSender&wap_bookmark_type=NOKIA&wap_bookmark_name=wapMX.com
  &wap_bookmark_url=http%3A%2F%2Fwww.wapMX.com%2F

An example HTML form for this message type can be found here.

Nokia Ringtone

Parameter	Description
rtttl	The ringtone in RTTTL format
tune_style	Style of the tune
tune_loop	Number of times for the tune to loop (15=infinite)

The example below shows a typical HTTP request for a message of this sort:

http://sms.mxtelecom.com/SMSSend?user=myusername&pass=mypassword&smsto=44778148446
  &smsfrom=Beverly%20Hills&rtttl=AxelF%3Ad%3D4%2Co%3D5%2Cb%3D160%3Af%23%2C8a.%
  2C8f%23%2C16f%23%2C8a%23%2C8f%23%2C8e%2Cf%23%2C8c.6%2C8f%23%2C16f%23%2C8d6%2
  C8c%236%2C8a%2C8f%23%2C8c%236%2C8f%236%2C16f%23%2C8e%2C16e%2C8c%23%2C8g%23%2
  Cf%23.&tune_style=C&tune_loop=0

An example HTML form for this message type can be found here.

EMS Ringtone Message

Parameter	Description
ems_format	It is used to specify the format of the following data
ems_beat	The tempo of the ringtone.
ems_style	This sets the style of the Melody.Which can be : Normal Style/Continuous Style/Staccato Style
ems_name	Name of the ringtone
ems_composer	The composer of the ringtone
ems_volume	Volume modifier
melody	This is the actual moledy
*smsmsg	Not yet implemented: Optional text to be included with the picture

(Optional parameters are indicated by a *)

An example HTML form for this message type can be found here.

Nokia Operator Logo

Parameter	Description
logo_type	Should be set to "OPERATOR"
img	Hex encoded image data. Formats supported: GIF, PNG, BMP. Image should be 72x14
mobile_operator_code	Hex code of the operator with which the logo will be used.

An example HTML form for this message type can be found here.

Nokia Group Logo

Parameter	Description
logo_type	Should be set to "GROUP"
img	Hex encoded image data. Formats supported: GIF, PNG, BMP. Image should be 72x14

The example below shows a typical HTTP request for a message of this sort:

http://sms.mxtelecom.com/SMSSend?user=myusername&pass=mypassword&smsto=447781484466
  &smsfrom=Artist&logo_type=GROUP&img=89504e470d0a1a0a0000000d49484452000000480000000
  e0103000000b622c87500000006504c5445000000ffffffa5d99fdd00000001624b47440088051d4800
  0000097048597300000b1200000b1201d2dd7efc0000000774494d4507d20716111c19cb88ff0d00000
  07f49444154789c63f80f030c1f0f59b8733c94516e67786779dce2b9cce339c50cb7abf373dfeeddbe
  ed37c3f55fffe35fffad5f8fccbafffb7ffdfbbffff7ff6678fff3bffdf33fffe77f66f8fee95ffce99
  ff5facf197e3faf793ff7f3bef2f30c7fcfeffc6ef7fcceeff90cffe65ffe55effff2af3d0354fdbf7a
  06b80b00b8956169784370d60000000049454e44ae426082
  &mobile_operator_code=32F401&img_text=hello

An example HTML form for this message type can be found here.

Nokia Picture Message

Parameter	Description
logo_type	Should be set to "PICTURE"
img	Hex encoded image data. Formats supported: GIF, PNG, BMP. Image should be 72x28
*smsmsg	Optional text to be included with the picture

(Optional parameters are indicated by a *)

An example HTML form for this message type can be found here.

EMS Picture Message

Parameter	Description
logo_type	Should be set to "EMSPICTURE"
img	Hex encoded image data. Formats supported: GIF, PNG. Message will be rejected if image is too large
*smsmsg	Not yet implemented: Optional text to be included with the picture

(Optional parameters are indicated by a *)

An example HTML form for this message type can be found here.

WAP Push Service Loader

Parameter	Description
pushtype	1 - Type of WAP Push
push_href	This attribute specifies the URI that is used to access the service. If href is empty, or omitted, the SL corresponds to a notification (no service can be initiated).
push_action	This attribute may contain a text string specifying the action to be taken when the SL is received. There are three possible values for the action attribute, each implying: 0 - execute-low : The service identified by the URI provided by the SL s href attribute is loaded in the same way as the user agent otherwise performs method requests initiated by the end-user [WAE]. This implies that service content is fetched either from an origin server or from the client s cache, if available. Once the method request is successfully completed, the user agent loads the service into a clean user agent context and executes it. This MUST be carried out in an non-user-intrusive manner 1 - execute-high : The service is loaded and executed in the same way as for execute-low , but MAY result in a user-intrusive bahavior. 2 - cache : The service is loaded in the same way as for execute-low . However, instead of executing the service (as described above) it is placed in the cache of the client. If no cache exists, the SL MUST be silently discarded.

This type of WAP Push is not supported by recent Nokia handsets. For full details on the WAP 1.2 Push Service Loader see WAP Service Loader Specification.

The example below shows a typical HTTP request for a message of this sort:

http://sms.mxtelecom.com/SMSSend?user=myusername&pass=mypassword&
    smsto=447974128549&smsfrom=1212&pushtype=1&
    push_href=http%3A%2F%2Fwww.mxtelecom.com%2F&push_action=1

An example HTML form for this message type can be found here.

WAP GSM CSD Configuration

Parameter	Description
bearer_type	GSMCSD - Flas as a GSM CSD Configuration
profile_name	Name of the Wap Configuration
proxy	Used to identify the I.P address of the WAP proxy in case of CSD/DATA and service number in case of SMS. In case of USSD is can be IP or MSISDN number
*port	Specifies whether connection less or connection oriented connections should be used
csd_dialstring	Specifies the MSISDN number of the modem pool
*csd_calltype	Indicates the type of circuit switched call to be used for the connection: ISDN ANALOGUE
*csd_callspeed	Indicates the desired call speed to be used for the connection.
*ppp_authtype	Indicates which protocol to use for user authentication.
*ppp_authname	Login name for PPP auth. Length 32 characters
*ppp_authsecret	Password for PPP. Length 21 character.
*ppp_logintype	Specifies whether a automatic or manual login should be performed for PPP
*proxy_authname	Login name for Proxy auth. Length 32 characters
*proxy_authsecret	Password for Proxy. Length 21 character.
*proxy_logintype	Specifies whether a automatic or manual login should be performed for Proxy
*isp_name	Indicates the name of the Internet Service Provider.
*home_page	Sets the default of the homepage for the connection. This need to be the same as the bookmark URL for Nokias.
*bookmark_url	URL of a Bookmark
*bookmark_name	Name of a Bookmark.

An example HTML form for this message type can be found here.

About MX Telecom MX Telecom is a leader in wireless technology. MX Telecom offers an easily accessible gateway to data, voice and video messaging services including 2-way and premium SMS, multimedia messaging, interactive voice response, location-based services, video short codes, Internet and TV related solutions. For more information, MX Telecom can be reached on 1-877-MXTELECOM (+1 877 698 3532), or via email at sales@mxtelecom.com.