SolutionsTools & SDKSupport  



Quick Links
 
MMS Quick Start
 
 
Follow this step-by-step guide to quickly setup and start using MMS with the Openwave Phone Simulator 6.2.2. For instructions on how to configure and use the Openwave Phone Simulator V7 for MMS, click here.

After completing these instructions, you will be able to send multimedia messages containing content such as pictures, music, images, graphics and ring tones to any MMS compatible phone using Openwave MMS SDK via the Openwave Multimedia Messaging Services Center (MMSC).

For the purpose of this Quick Start, you use Openwave Phone Simulator (running Openwave Mobile Messaging Client) to receive and view MMS messages via the Openwave Developer MMSC.   However, the Developer MMSC can connect with and deliver messages to any MMS compatible GSM phone, allowing you to test your MMS-enabled applications with a real device over a real wireless network environment.

For an introduction to the MMS SDK, click here.

1. Download the Openwave MMS SDK 

DOWNLOAD the Openwave MMS SDK 3.0.  Save the download file vaspsdk.jar to your PC.


2. Install the MMS SDK on Your PC

You can install the MMS SDK on either a Windows or UNIX based system.  These instructions assume you are using a Windows PC.  For UNIX based instructions, please refer to the Openwave MMS Library Developer's Guide.


The MMS SDK is Java based.  Before you install the MMS SDK, you must first install the J2SE SDK available at java.sun.com.  In addition, you must set the JAVA_HOME environment variable before running any of the SDK sample applications (see Step 7, below).

To install the MMS SDK, open the download file vaspsdk.jar using a file extraction utility, like WinZip or the Java "jar" utility.  Create a new folder in the location:  C:\openwave\vaspsdk and extract the contents of the .jar file into that folder. 

3. Download and Install the Openwave Phone Simulator 

Use Openwave Phone Simulator 6.2.2 (or higher) to test the full range of content supported by Openwave Mobile Messaging Client  The Phone Simulator includes Openwave Mobile Messaging Client, which is used to send, receive, and view MMS messages from a mobile phone.

DOWNLOAD the Openwave Phone Simulator 6.2.2 Main Package.

DOWNLOAD the Openwave Phone Simulator 6.2.2 WAP 1.x Network Plug-In.


Install the Phone Simulator Main Package and WAP Network Plug-in by executing the download files: Openwave_SDK622.exe and Openwave_SDK_622wap.exe (in that order).


4. Create a Subscriber Account on the Openwave Developer MAG

Before you can send and receive MMS content using the Phone Simulator, you must create a subscriber account on the Openwave Developer MAG (oden.openwave.com).  This allows you to test your MMS applications using the same version of Openwave MAG and MMSC deployed by network operators.  


Fill out and submit the  Developer Account Registration Form to create a new account on the Openwave Developer MAG.    After you submit the form, login and go to the Subscriber Provisioning Group Access page.  Click on the Add Subscriber button to bring up the Subscriber Registration Form.  


In the Client ID Format field, ensure the WAP radio button is selected (the default) and change the client ID format to Phone Number (GSM Interim) via the pop-up menu.  In the Client ID field, enter a unique phone number to identify your client account (e.g. your office phone number).  Be sure to enter the complete number, including the country code (for U.S. phone numbers, prepend a "1").  After you submit the form, the system will display your new subscriber profile.


5. Configure the Phone Simulator

In this step, you configure the Phone Simulator to connect with the Openwave Developer MAG and MMSC.

Select Openwave SDK 6.2.2 -> Openwave SDK 6.2.2 WAP from the Windows Programs menu to launch the Phone Simulator.  Select Tools -> Options from the Simulator pull-down menu to display the SDK Configuration dialog. 

In the Device configuration page, clear the UAProf URL field so that it contains
http://developer.openwave.com/uaprof/OPWVSDK62.xml, then click the Apply button.



In the SDK Configuration dialog, click the Server tab to display the Server configuration page. Click the Add button to create a new Server Profile, and then follow these steps to complete the configuration wizard:
  1. In the Gateway dialog, enter oden.openwave.com as the gateway hostname, and then click the Next button.



  2. In the WAP Anonymous dialog, ensure the No radio button is selected (the default), and then click the Next button.



  3. In the WAP Client ID dialog, change the Client ID Format field value by choosing GSM Number from the pop-up menu.  Enter the phone number you specified for your subscriber account (see Step 4, above) in the Client ID field.  Then click the Next button.



  4. In the WAP Secure dialog, ensure the Yes radio button is selected (the default), and then click the Next button.



  5. In the Finished dialog, enter a name for your new Server Profile (e.g. MMS Testing), and then click the Finished button.



Now select your new profile in the Server configuration page, and then click the Settings button.




In the WAP Server Profile dialog, enter the following string into
the MMSC URL field:
http://skara.openwave.com:8088/mms/
Copy the value from the Client ID field (your phone number) into the MSISDN field, and then click the OK button.



Click on the new profile name in the SDK Configuration dialog, click the Activate button to activate it, and then click the OK button to close the window. 



The simulator should now connect with the Developer MAG and display the default subscriber home page, as shown here:



6. Create an MMS Account on the Openwave Developer MMSC

Before you can send MMS messages to your test subscriber, you must create an MMS account for your subscriber on the Openwave Developer MMSC (skara.openwave.com).  The MMSC manages the delivery and storage of MMS messages on behalf of your MAG subscriber. 

To create a new MMS account, simply send a test message from the Phone Simulator to any valid email address (e.g. your personal email address).  The first time you send an MMS message from a phone, the MMSC automatically provisions a new MMS account on behalf of the subscriber, using the phone number as the unique MMS address (e.g. 14155550303@skara.openwave.com).

Select Tools -> Messaging Home from the Phone Simulator pull-down menu.  Scroll down and select ComposeIn the message composition form, enter any text for the message body (e.g. "This is a test message").  Select Menu (press the soft key under the Menu label), and then select Send from the pop-up menu.  In the address form, scroll down to the text entry field, enter your personal email address (e.g. "myname@myisp.com"), and then select Send.

   

When the MMSC receives the send request, it creates the new MMS account and sends a confirmation MMS to the new address.  This results in the MMSC sending a notification message to the Mobile Messaging Client running in the Phone Simulator.  The Mobile Messaging Client displays a pop-up message to alert the user that a new message has arrived.  To confirm the alert, select YES.  This causes the Mobile Messaging Client to download the corresponding MMS message from the MMSC.  The MMS message confirming your new MMS account is then displayed on the phone.

 

7. Configure the MMS SDK Sample Application


Using your favorite text editor, open and edit the file  c:\openwave\vaspsdk\samples\standalone\send.bat


The send.bat file is a script that invokes a sample application called MM7MessageSender.  The sample app demonstrates how to send an MMS message request using Openwave MMS Library.  The MMS Library implements the standard MM7 protocol to communicate and send messages to and from the MMSC.  In addition, the MMS Library provides utility APIs for constructing SMIL content to be included in the MMS message body.


In the next step, you run send.bat to invoke MM7MessageSender.  However, you must first edit the script to specify your Client ID and the multimedia content (files) you want to include in the MMS message body. 

Scroll to the bottom of the send.bat file.  You will see two separate commands, both of which invoke MM7MessageSender.  Comment-out the first command by inserting the word rem at the beginning of the line.  Un-comment the second command by deleting the word rem at the beginning of the line.


In the second command (the one you un-commented) change the value of the -ton argument to be your Client ID
(see Step 4, above)Do not change the value of the -u argument, which the MMSC uses to authenticate and uniquely identify SDK sample applications.  Note that the -slide argument is used to specify one or more content files to include in the MMS message body.  Later on, you can come back and edit the argument value to specify your own multimedia files to create custom slide shows.


The bottom of the script should now look something like this:

rem THIS VERSION OF THE COMMAND IS COMMENTED-OUT
rem %JAVA_HOME%\bin\java" MM7MessageSender -url http://skara.openwave.com:8080/mm7
-ton 14155550303 -u 16504808000 -p developer -f content\test1.txt
rem THIS VERSION OF THE COMMAND IS UN-COMMENTED AND WILL BE INVOKED
"%JAVA_HOME%\bin\java" MM7MessageSender -url http://skara.openwave.com:8080/mm7
-ton 14155550303 -u 16504808000 -p developer
-slide text=content\test1.txt:image=content\yellowfl.gif

Be very careful not to insert any new-line characters between the arguments of a command line (for example, if you copy/pasted the above text from this page).  Each command line must be one contiguous line, or the trailing arguments after the new-line character will be treated as a separate command.


Also note that the script references the JAVA_HOME environment variable to locate the path of the Java runtime.  You must either set this variable via the Windows System Control Panel (recommended), or you must add a line to the beginning of the send.bat script to set the variable explicitly.  For example:

rem
rem Set the JAVA_HOME variable to the Java SDK root directory
rem
set JAVA_HOME=c:\j2sdk1.4.1_02

When you are finished editing send.bat, save your changes and close the file. 


8. Send the MMS Message


First, ensure that the Phone Simulator is still running and is connected to the MAG.

Launch the Windows command interpreter (select Run from the Windows Start Menu and enter cmd). Run the send.bat script that you edited in the previous step, by entering the following commands at the command line prompt:

cd c:\openwave\vaspsdk\samples\standalone
run send.bat

When MM7MessageSender executes, it first sends the MMS message request to the MMSC.  Then the application waits to receive a valid response from the MMSC.  When the app receives the response, it prints the response content (in XML) to the command window.  If you look closely at the response content, you will see a 1000 status code indicating that the MMSC successfully received the MMS message and validated the Client ID.



After
the MMSC receives the MMS message, it sends a notification to the Mobile Messaging Client running in the Phone Simulator.  The Mobile Messaging Client displays a pop-up message to alert the user that a new message has arrived.  To confirm the alert, select YES.  This causes the Mobile Messaging Client to download the MMS message from the MMSC to the phone.



9. View the MMS Message


Select Tools -> Messaging Home from the Phone Simulator pull-down menu.  Scroll down and select Inbox to display the MMS inbox.  You should see an item labeled: Attachments you wanted... (the Subject header is hard-coded in the source code of the MM7MessageSender sample app).  Select this item to display the MMS message content.

 

Before you can view the message content, you must respond to the sender's request for a Read Report.  The Read Report allows the sender to confirm that the endures received the MMS message.  Select Skip to ignore the request and go directly to the MMS message content.  You should see a single page (composed in SMIL), containing the sample image and caption text.

 


The MM7MessageSender application is a very simple application that demonstrates the basic use of the MM7 protocol.  Using Openwave MMS Library, developers can create more powerful applications to compose, send, receive, and manage MMS messages on behalf of end users.  For more information on Openwave MMS Library, please refer to
the Openwave MMS Library Developer's Guide.

 
Copyright © 2000-2008 Openwave Systems Inc.    Openwave  |  Terms & Conditions  |  Privacy Policy