• o-dd:display
• o-dd:play

As some readers asked me to include additional permission, and I’ve included the following permissions:

• o-dd:print
• o-dd:execute

You can download the package at Net-OmaDrm-0.10.tar.gz.

One of the free library that I’ve using is from Marco Romano. It is a Perl library which can be used to generate EMI/UCP message easily. Please take a look at:

http://search.cpan.org/~nemux/Net-UCP-0.29/

Image Transcoding

The best and free engine that I’ve come across is ImageMagick. You can take a look at www.imagemagick.org. To convert from one format to another is as simple as:

convert rose.jpg rose.png

Audio Transcoding

Searching for free audio transcoding is not as simple as I thought initially until I found this web site at
http://xa.bi/mms/. It describes the difference audio transcoding engine and how they work together to convert different format of audio to/from one another.

Video Transcoding

FFMpeg is always the choice when I ask someone for a free source to transcode video file.

Check out these web site, it should give you a starting point of where to look out for free library and third party software to do transcoding.

To check Forward-Lock, you need to ensure that the following content-type is accepted by the device:

• application/vnd.oma.drm.message

To check Combined Delivery, you need to ensure that the following content-type is accepted by the device:

• application/vnd.oma.drm.message
• application/vnd.oma.drm.rights+xml

To check Separate Delivery, you need to ensure that the following content-type is accepted by the device:

• application/vnd.oma.drm.rights+xml
• application/vnd.oma.drm.rights+wbxml
• application/vnd.oma.drm.content

One more thing is that the device may support (for example) Combined Delivery DRM, but you may not be able to use that in MMS. Thus, further check on “MmsCcppAccept” tag of the User Agent Profile (UAProf) to ensure that it is supported.

Some may wonder why I don’t just check the “DrmClass” tag instead. Well, you can, however, during my investigation, I found out that some mobile phone manufacturers do not include this in the UAProf. Thus, it is much safer to check the DRM’s content-types instead.

I have further modified the previous Mobile::UserAgentProfile library and include this checking into that. I have also make changes to the method calling so that I can hold the profile in memory rather than load the profile from file every time I need to check on the UAProf.

INSTALL

To install, do the following:

perl Makefile.PL
make
make install

The following a a perldoc of this module:

SYNOPSIS

 use Mobile::UserAgentProfile;
 my $uaprof= new Mobile::UserAgentProfile();

DESCRIPTION
This module will retrieve the screen size of the device from the UAProf.

METHODS

new, this method is used to create the UserAgentProfile object. Initial call will be slow if the DefaultCacheDir directory is not found. If DefaultCacheDir is not found, this module will retrieve a list of UAProf from the Internet. The current list is available at here .

Usage:

my $uaprof= new Mobile::UserAgentProfile();

my $uaprof= new Mobile::UserAgentProfile(
     DefaultUrl=>"http://www.artofmobile.com/uaprof/",
     UserAgent=>"UserAgentProfile Grabber",
     DefaultCacheDir=>"UAGrabber"
);

setDevice, this method will retrieve device profile on the UAProf URL. If the UAProf is not found in the DefaultCacheDir directory, this module will retrieve the UAProf from the given url. If the UAProf is found, it will retrieve from DefaultCacheDir directory.

Usage:

     $uaprof->setSize(HTTP_X_WAP_PROFILE=>$HTTP_X_WAP_PROFILE);

Example of accepted value for HTTP_X_WAP_PROFILE:

http://nds1.nds.nokia.com/uaprof/N6070r100.xml

"http://wap.sonyericsson.com/UAprof/K700iR201.xml", "1-bgyyJlyTUYSczJUKDdFYyw=="

getSize, this method will retrieve the size of the device.

Usage:

   my $size= $uaprof->getSize();

isOmaDrmForwardLock, this method will retrieve to see whether it supports the following content-type:

• application/vnd.oma.drm.message

Usage:

   my $support= $uaprof->isOmaDrmForwardLock();

isOmaDrmCombinedDelivery, this method will retrieve to see whether it supports the following content-type:

• application/vnd.oma.drm.message
• application/vnd.oma.drm.rights+xml

Usage:

   my $support= $uaprof->isOmaDrmCombinedDelivery();

isOmaDrmSeparateDelivery, this method will retrieve to see whether it supports the following content-type:

• application/vnd.oma.drm.rights+xml
• application/vnd.oma.drm.rights+wbxml
• application/vnd.oma.drm.content

Usage:

   my $support= $uaprof->isOmaDrmSeparateDelivery();

You can download the package at Mobile-UserAgentProfile-0.10.tgz

User Agent Profile (UAProf) specification is the answer to this problem. It is used to capture capability and preference information for mobile devices. This information can be used by content providers to produce content in an appropriate format for the specific device.

In this article, we will discuss the Perl module which use UAProf to get the screen size of the mobile devices. For further information, you can download a copy of UAProf’s specification at:

Specification of UAProf

INSTALL

To install, do the following:

perl Makefile.PL
make
make install

The following a a perldoc of this module:

SYNOPSIS

 use Mobile::UserAgentProfile;
 my $uaprof= new Mobile::UserAgentProfile();

DESCRIPTION
This module will retrieve the screen size of the device from the UAProf.

METHODS

new, this method is used to create the UserAgentProfile object. initial call will be slow if the DefaultCacheDir directory is not found. If DefaultCacheDir is not found, this module will retrieve a list of UAProf from the Internet. The current list is available at here .

Usage:

my $uaprof= new Mobile::UserAgentProfile();

my $uaprof= new Mobile::UserAgentProfile(
     DefaultUrl=>"http://www.artofmobile.com/uaprof/",
     UserAgent=>"UserAgentProfile Grabber",
     DefaultCacheDir=>"UAGrabber"
);

getSize, this method will retrieve the size of the device based on the UAProf URL. If the UAProf is not found in the DefaultCacheDir directory, this module will retrieve the UAProf from the given url. If the UAProf is found, it will retrieve from DefaultCacheDir directory.

Usage:

     my $size= $uaprof->getSize(HTTP_X_WAP_PROFILE=>$HTTP_X_WAP_PROFILE);

Example of accepted value for HTTP_X_WAP_PROFILE:

http://nds1.nds.nokia.com/uaprof/N6070r100.xml

"http://wap.sonyericsson.com/UAprof/K700iR201.xml", "1-bgyyJlyTUYSczJUKDdFYyw=="

You can download the package at Mobile-UserAgentProfile-0.01.tgz

I have created Net::OmaDrm Perl module so that content providers can format the content-type quickly.

This module support the OMA DRM version 1.0 method of sending content to the handset. A device will declare the support for OMA-DRM by including one of the method which is provided by this module:

• Forward-lock
• Content-Type
• application/vnd.oma.drm.message
• Combined delivery
• Content-Type
• application/vnd.oma.drm.message
• application/vnd.oma.drm.rights+xml
• o-ex:permission
• o-dd:display
• o-dd:play
• o-ex:constraint
• o-dd:count
• o-dd:interval

A detailed document of OMA-DRM can be found at:
http://www.openmobilealliance.org/release_program/drm_v1_0.html

I have tested this module on perl v5.8.5.

INSTALL
To install, do the following:

perl Makefile.PL
make
make install

The following is a perldoc of this module:

SYNOPSIS

use Net::OmaDrm;

my $mydrm = Net::OmaDrm->new($basepath);
my $content= $mydrm->genForwardLock($content_name,$content_type);

DESCRIPTION
This module will encapsulate the media type to a multi-type content with OMA DRM standard.

METHODS
new, this method is used to create the OmaDrm object.

Usage:

my $mydrm = Net::OmaDrm->new($basepath);

The complete list of arguments is:

• $basepath : This is the base path for the content.

genForwardLock, this method will generate the Forward Lock DRM with an input Media Type.

Usage:

my $content= $mydrm->genForwardLock($content_name,$content_type);

The complete list of arguments is:

• $content_name : File name of the content.
• $content_type : Content Type.

genCombinedDelivery, this method will generate multipart content with rights.

Usage:

my $content= $mydrm->genCombinedDelivery($content_name,$content_type,$interval,$count);

Example:

my $content= $mydrm->genCombinedDelivery("image.gif","image/gif","",3);
my $content= $mydrm->genCombinedDelivery("image.gif","image/gif","P30S","");

The complete list of arguments is:

• $content_name : File name of the content.
• $content_type : Content Type.
• $interval : Interval that the content can play.
• $count : Number of time that the content can play.

Sample Source Code

The following is a full source code sample for your reference:

#!/usr/local/bin/perl
use strict;
use Net::OmaDrm;

my $basepath='images';
my $content_name='logo.gif';
my $content_type='image/gif';
my $interval='P60S';
my $count='';

my $mydrm = Net::OmaDrm->new($basepath);
my $content= $mydrm->genCombinedDelivery($content_name,$content_type,$interval,$count);

print "$content\n";

The above sample source code will input the image file, logo.gif and format the DRM content with display permission of 60 seconds. An example URL for this sample is available at http://www.artofmobile.com/logo.pl. Enter this URL in your WAP browser in your phone and download the content.

You can download the package at Net-OmaDrm-0.10.tar.gz.

The following are all the available APIs and whether they are supported or not:

Basic Commands

• http://api.clickatell.com/http/auth
• Yes (But session Not support)
• http://api.clickatell.com/http/ping
• Yes (But session Not support)
• http://api.clickatell.com/http/querymsg
• Yes
• http://api.clickatell.com/http/sendmsg
• Yes

Additional Commands

• http://api.clickatell.com/http/delmsg
• No
• http://api.clickatell.com/http/getbalance
• Yes
• http://api.clickatell.com/http/routeCoverage.php
• Yes
• http://api.clickatell.com/mms/ind_push.php
• Yes
• http://api.clickatell.com/mms/si_push.php
• Yes
• http://api.clickatell.com/http/getmsgcharge
• Yes
• http://api.clickatell.com/http/token_pay
• No

Batch Messaging

• http://api.clickatell.com/http_batch/startbatch
• No
• http://api.clickatell.com/http_batch/senditem
• No
• http://api.clickatell.com/http_batch/quicksend
• No
• http://api.clickatell.com/http_batch/endbatch
• No

I tested this module on perl v5.8.5.

INSTALL

To install the module, perform the usual perl module installation procedures. The following is the steps:

        perl Makefile.PL
        make
        make install

The following is a perldoc of this module:

SYNOPSIS
With SSL

 use Net::Clickatell;

 my $clickatell = Net::Clickatell->new( API_ID => $api_id,
                                      USERNAME => $username,
                                      PASSWORD => $password );
 my $bal=$clickatell->getBalance;

Without SSL

 use Net::Clickatell;

 my $clickatell = Net::Clickatell->new( UseSSL=> 0,
                                       API_ID => $api_id,
                                     USERNAME => $username,
                                     PASSWORD => $password );
 my $bal=$clickatell->getBalance;

DESCRIPTION

Clickatell (http://www.clickatell.com) is a commercial service that allows its users to send SMS messages to anyone in the world. This perl module allow users to send SMS, WAP push and MMS through Clickatell HTTP API.

Please take note that neither this software nor the author are related to Clickatell in any way.

METHODS

new
This method is used to create the Clickatell object.

Usage:

 my $clickatell = Net::Clickatell->new( API_ID => $api_id,
                                          USERNAME => $user,
                                          PASSWORD => $passwd );

The complete list of arguments is:

     API_ID    : Unique number received from Clickatell when an account is created.
     UseSSL    : Tell Clickatell module whether to use SSL or not (0 or 1).
     BaseURL   : Default URL used to connect with Clickatell service.
     UserAgent : Name of the user agent you want to display to Clickatell service.

getBalance
This method will return the Balance of the account.

Usage:

  $clickatell->getBalance;

Succesful example of the return is as followed:
OK: Credit: 100.3

Failed example of the return is as followed:
ERR: 001, Authentication failed

checkCoverage
This method will return the Balance of the account.

Usage:

  $clickatell->checkCoverage($msisdn);

Succesful example of the return is as followed:
OK: This prefix is currently supported. Messages sent to this prefix will be routed. Charge: 1

Failed example of the return is as followed:
ERR: This prefix is not currently supported. Messages sent to this prefix will fail. Please contact support for assistance.

getReturnMessageCharge
This method will return the Message Charge Status.

Usage:

 my $messagecharge=$clickatell->getMessageCharge($smsResult);

Succesful example of the return is as followed:
OK: This prefix is currently supported. Messages sent to this prefix will be routed. Charge: 1

Failed example of the return is as followed:
ERR: This prefix is not currently supported. Messages sent to this prefix will fail. Please contact support for assistance.

sendBasicSMSMessage
This method is used to send a SMS Message.

Usage:

 my $smsResult=$clickatell->sendBasicSMSMessage($from,$to,$msg);

Succesful example of the return is as followed:
OK: ID: dd8f5556c0d3d54bc94a4cd8800f01b4

Failed example of the return is as followed:
ERR: 105, Invalid Destination Address

sendMMNotification
This method is used to send a MMS Notification Push Message.

Usage:

 my $mmsResult=$clickatell->sendMMNotification($from,$to,$tranid,$expiry,$url);

Succesful example of the return is as followed:
OK: ID: dd8f5556c0d3d54bc94a4cd8800f01b4

Failed example of the return is as followed:
ERR: 105, Invalid Destination Address

sendWAPPush
This method is used to send a WAP Push. Currently, only SI WAP Push message is supported.

Usage:

 my $wapResult=$clickatell->sendWAPPush($from,$to,$msg,$url);

Succesful example of the return is as followed:
OK: ID: dd8f5556c0d3d54bc94a4cd8800f01b4

Failed example of the return is as followed:
ERR: 105, Invalid Destination Address

You can download the package at Net-Clickatell-0.10.tgz.

http://search.cpan.org/~cmanley/Mobile-UserAgent-1.05/lib/Mobile/UserAgent.pm

After you download the library, perform the usual installation procedures:

perl Makefile.PL
make
make install

The following is the source code:

#!/usr/local/bin/perl
use strict;

use Mobile::UserAgent;
my $uaobj = new Mobile::UserAgent();

The codes above is the standard declaration so that you can call “Mobile::UserAgent” library. The following 3 lines are used for testing purposes. Uncomment the following 3 lines and comment the above 1 line to do some testing.

#my $useragent = 'Nokia6600/1.0 (4.09.1) SymbianOS/7.0s Series60/2.0 '.
#   'Profile/MIDP-2.0 Configuration/CLDC-1.0';
#my $uaobj = new Mobile::UserAgent($useragent);

The following lines check the User-Agent string and pass the output to the subroutine “printWml” if the device suppose WML or the subroutine “printHtml” if the device doesn’t.

if ($uaobj->success()) {
   my $out='Vendor: ' . $uaobj->vendor()     . "\n";
   $out.='Model:    ' . $uaobj->model()      . "\n";
   $out.='Version:  ' . $uaobj->version()    . "\n";
   $out.='Series60: ' . $uaobj->isSeries60() . "\n";
   &printWml($out);
} else {
   &printHtml("Connecting Client is not a mobile user-agent \n");
}

The subroutine “printWml” is used to print the standard WML content on the device.

sub printWml {
   my $string= shift;
   print "Content-Type: text/vnd.wap.wml\r\n\r\n";
print <

  

      
        $string
      
    

      Test script by Art of Mobile

    

  

EOFWML
}

The subroutine “printHtml” is used to print the standard HTML content on the browser.

sub printHtml{
   my $string= shift;
   print "Content-Type: text/html\r\n\r\n";
print <






$string




EOFHTML
}

You can download the full source code at mobileUserAgent.pl.

You can test the example by pointing your mobile phone’s WAP broswer to this url:

http://www.artofmobile.com/cgi-bin/mobile.pl

Basically, the following is an example in java with remark in the code to explain how this is done:

  public String toSmsBinary() {
    /**
     GSM SMS User Data
     06: UDH Length which is 6
     05: 16 bit address
     04: Length(4)
     0B84: Destination Port(2948)
     23F0: Source Port(9200)

     Wireless Session Protocol
     90: Transaction ID
     06: PDU Type(Push)
     01: Headers Length is 1
     AE: Content-Type is application/vnd.wap.sic

     */
    StringBuilder ud = new StringBuilder().append("0605040b8423f0900601ae");
    ud.append(toWBXML());
    return ud.toString();

  }

The above function creates the GSM SMS User Data and Wireless Session Protocol (WSP) header.

  public String toWBXML() {
    /**
     02: Version number - WBXML version 1.2
     05: SI 1.0 Public Identifier
     6A: Charset=UTF-8 (MIBEnum 106)
     00: String table length
     45: si, with content
     */
    StringBuilder wbxml = new StringBuilder().append("02056a0045");
    wbxml.append(indicationToWBXML());
    wbxml.append("01");
    return wbxml.toString();
  }

The above function creates the WAP Binary XML header and the following function will formulate the rest of the WAP Binary XML body.

  public String indicationToWBXML() {
    StringBuilder wbxml = new StringBuilder().append("c6");
    if (siId != null && siId.length() > 0) {
//si-id attribute
      wbxml.append("11");
// string literal
      wbxml.append("03");
// si-id string
      wbxml.append(hexDump(siId.getBytes()));
// end string
      wbxml.append("00");
    }

    if (href != null && href.length() > 0) {
      if (href.startsWith("http://www.")) {
        wbxml.append("0d");
        href = href.substring(11);
      }
      else if (href.startsWith("https://www.")) {
        wbxml.append("0f");
        href = href.substring(12);
      }
      else if (href.startsWith("http://")) {
        wbxml.append("0c");
        href = href.substring(7);
      }
      else if (href.startsWith("https://")) {
        wbxml.append("0e");
        href = href.substring(8);
      }
//String literal
      wbxml.append("03");
      wbxml.append(hexDump(href.getBytes()));
// end string
      wbxml.append("00");

      wbxml.append(getDecodedAction());

// >
      wbxml.append("01");
// The text value of the URL
      wbxml.append("03");

      byte[] bytes = value.getBytes();
      wbxml.append(hexDump(bytes));
      wbxml.append("00");

    }
    wbxml.append("01");
    return wbxml.toString();
  }

You can download the full source code at SiWapPush.java.

The downloadable zipped file include source code and jar file libraries, and this article will modify this file SMPPTest.java to demonstrate how to do that.

Modify SMPPTest.java and include the following 2 functions:

    private static final String HEXINDEX = "0123456789abcdef          ABCDEF";

    public static byte[] hexToByte(String s) {
        int l = s.length() / 2;
        byte data[] = new byte[l];
        int j = 0;

        for (int i = 0; i < l; i++) {
            char c = s.charAt(j++);
            int n, b;

            n = HEXINDEX.indexOf(c);
            b = (n & 0xf) << 4;
            c = s.charAt(j++);
            n = HEXINDEX.indexOf(c);
            b += (n & 0xf);
            data[i] = (byte) b;
        }
        return data;
    }

The above function is used to convert Hexadecimal to binary data.

    private void wappush() {
        debug.enter(this, "SMPPTest.submit()");

        try {
            SubmitSM request = new SubmitSM();
            SubmitSMResp response;

// input values
            serviceType = getParam("Service type", serviceType);
            sourceAddress = getAddress("Source", sourceAddress);
            destAddress = getAddress("Destination", destAddress);
            replaceIfPresentFlag = getParam("Replace if present flag",
                                            replaceIfPresentFlag);

            payload = getParam("Payload", payload);

            scheduleDeliveryTime = getParam("Schedule delivery time",
                                            scheduleDeliveryTime);
            validityPeriod = getParam("Validity period", validityPeriod);
            esmClass = getParam("Esm class", (byte) 64);
            protocolId = getParam("Protocol id", protocolId);
            priorityFlag = getParam("Priority flag", priorityFlag);
            registeredDelivery = getParam("Registered delivery",
                                          registeredDelivery);
            dataCoding = getParam("Data encoding", (byte) 245);
            smDefaultMsgId = getParam("Sm default msg id", smDefaultMsgId);

// set values
            request.setServiceType(serviceType);
            request.setSourceAddr(sourceAddress);
            request.setDestAddr(destAddress);
            request.setReplaceIfPresentFlag(replaceIfPresentFlag);
            request.setScheduleDeliveryTime(scheduleDeliveryTime);
            request.setValidityPeriod(validityPeriod);
            request.setEsmClass(esmClass);

            request.setProtocolId(protocolId);
            request.setPriorityFlag(priorityFlag);
            request.setRegisteredDelivery(registeredDelivery);
            request.setDataCoding(dataCoding);
            request.setSmDefaultMsgId(smDefaultMsgId);

            request.setShortMessageData(new ByteBuffer(hexToByte(payload)));

// send the request

            int count = 1;
            System.out.println();
            count = getParam(
                    "How many times to submit this message (load test)", count);
            for (int i = 0; i < count; i++) {
                request.assignSequenceNumber(true);
                System.out.print("#" + i + "  ");
                System.out.println("Submit request, wap push");
                if (asynchronous) {
                    session.submit(request);
                    System.out.println();
                } else {
                    response = session.submit(request);
                    System.out.println("Submit response " +
                                       response.debugString());
                    messageId = response.getMessageId();
                }
            }

        } catch (Exception e) {
            event.write(e, "");
            debug.write("Submit operation failed. " + e);
            System.out.println("Submit operation failed. " + e);
        } finally {
            debug.exit(this);
        }
    }

The above "wappush" function is a modification from "SubmitSM" function.

To run the test client:

java -classpath "log4j-1.2.13.jar:openSMPP.jar:./" SMPPTest

The following is the entry for each setting:

-  1 bind
-  2 submit (t/tr)
-  3 wappush (t/tr)
-  4 submit multi (t/tr)
-  5 data (t/tr)
-  6 query (t/tr)
-  7 replace (t/tr)
-  8 cancel (t/tr)
-  9 enquire link (t/tr)
- 10 unbind
- 11 receive message (tr/r)
-  0 exit
> 3

Service type []
Source address TON [1]
Source address NPI [1]
Source address [1111]
Destination address TON [1]
Destination address NPI [1]
Destination address [6591234567]
Replace if present flag [0]
Payload [0605040b8423f0900601ae02056a0045c60d03676f6f676c652e636f6d00070103476f6
f676c652068656c6c6f000101]
Schedule delivery time []
Validity period []
Esm class [64]
Protocol id [0]
Priority flag [0]
Registered delivery [0]
Data encoding [-11]
Sm default msg id [0]

How many times to submit this message (load test) [1]

The PDU for this:
0605040b8423f0900601ae02056a0045c60d03676f6f676c652e636f6d00070103476f6f676c652068656c6c6f000101
will look like the following in Ethereal:

You can download the modified "SMPPTest.java" at http://www.artofmobile.com/posts/SMPPTest.java