CardBoardFish SMS Support Area

Here you will find detailed articles, Frequently Asked Questions, and the most recent technical specifications for all CardBoardFish SMS services. There is also a General section where content is listed if it applies to multiple services.

You may still contact support by logging into your customer account from the website, and submitting a ticket from the Support section. Please read through the General FAQ's and specific service FAQ's before contacting technical support.

Sending Binary Messages and Sending Ringtones, Operator Logos, WAP Push, VCards

In order to be able to send messages with content like ringtones, operator logos, WAP push or VCards you need to send a binary message.

You must set the DC value to 2 for binary messages.

You will also need to make sure that your message is hex encoded (all binary messages need to be coded in hex). We have made a free tool available which will convert a message into hex for you- it is available from our website by logging into your online account and then clicking on Support > Online Encoding Tools.

Our systems will also check binary messages to ensure there are no obvious errors- checking the message length, making sure all the characters are in hex etc.

In order to send a binary message to a phone you will need to construct something known as the User Data Header (UDH).

The UDH is a short hex code sent via the UD option of the HTTP SMS request and tells the receiving handset what type of content is contained in the binary message and how to deal with it.

Most UDH's are for Nokia brand phones and Nokia have made available details for constructing Smart Messages in their Smart Messaging Specification which is available in the developer's forum at

Sony Ericsson have also made available information on constructing similar messages for their handsets and it is available at

Once you have the correct UDH for the handset you wish to send to, and have set it with the UD option you can set the M option to the encoded content. Please see common user data headers.

For a full list of options for use with the HTTP SMS request you can consult the HTTP SMS Specification Document article.

A finished example message is illustrated here for sending a ringtone to a Nokia phone.

Example UN=username&P=password&DA=
447000000000&SA=FreeTone&ST=5&M= 024A3A7D0995D995C9B195E521A5B1B1CD0D
BC0400FD1CD496610624CB084125 A242892D049B890A24B31251892CC20C511610824
B4485125A0A251214511624 CB125A2428A231214516890A24B4125224289290491890A
24C31258840841892 CC20C499610824B4485125A09371214496624A312598418A22C21
0496890A24B 4144A2428A&UD=06050415810000&DC=2