You may be in the fortunate situation that your mobile provider offers a GPRS wap server functioning as MMS server as well. Then all you need is the wap GPRS settings for this, e.g. for the German Vodafone MMS service, introduced April 18, 2002, specifically. T-Mobile introduced the service on June 1, 2002, settings see below. (You might try the Swedish site http://www.mi4e.com for a free MMS service.) In my case I pass through the regular wap server of D1, my provider, and continue on to the MMS server elsewhere.
   First I had to get my GPRS wap communication going by choosing Connect, 7Data comm., 1Data accounts, and setting up “T-D1 W@P GPRS”. I got this via an automatic OTA, over-the-air activation, from http://secure.mouse2mobile.com/clients/ericsson/jv/wap. With this I could try wap via GPRS. (German readers find the parameters in my book “Handy und PC”, see http://www.Joern.De/handypc/handypctext.htm#GPRS)
   Then I had to make a copy of this data account, name it differently (I chose “D1 GPRS”), and edit it, so that instead of the standard access point name (APN) “wap.t-d1.de” I use “internet.t-d1.de”, which allows me to get to another wap server than the provider’s. (Side effect: The provider’s wap portal will not work with this setting.)
Connect >
   7Data comm. > 1Data accounts >“D1 GPRS”
   >1Edit >1APN > “internet.t-d1.de” (instead of “wap.t-d1.de”)
   >2User id > t-d1
   >3Password >wap
   >4Password request > 2Off
   >5Allow calls >Automatic
   >6IP address > ... (the IP address is given dynamically, so do not enter one!)
   >7DNS address > ... (do not give a domain name server)
   >8Advan. settings
     >1Authetication > Normal (vs. Secure, None)
     >2Data compr. > 2Off
     >3Header compr. > 2Off
     >4Quality of serv.
       >1Precedence >Subscribed (vs. High, Normal, Low)
       >2Delay > Subscribed (vs. Class 1, Class 2, Class 3, Best effort)
       >3Reliabilty >Class 3 (vs. 1 ... 5)
       >4Peak rate >Subscribed (vs. Class 1 ... 5)
       >5Mean rate >Subscribed (vs. Class 1 ... 18 und Best effort)
Again, you may want to try this profile with some wap, like wap.joern.de.
   Now I need a special wap setting to reach my MMS server. Imagine going trough one wap gateway (named D1 GPRS here) to the real one (I named this one “MMS”). Go out of Data communication, back up to the main menu, and enter the “WAP services” and 6Select profile. I found my dear profiles “T-D1 W@P GPRS” and “T-D1 WAP GSM” there, so I added another, “MMS”. This profile has to point to the IP address of the true MMS server, where I am registered as user. Let’s see:
WAP services
   >6Select profile >“MMS” (vs. my “T-D1 WAP GSM” and “T-D1 W@P GPRS”)
   >8Options >2WAP profiles >“MMS” >1Edit
   >1Chg homepage > This setting really is not important
   >2Connect using >“D1 GPRS” – here refer to the right data account!
   >3IP address > This IP number or URL address you must know from the MMS provider.
   >4User id >491713322017 (in this case my mobile phone number without +)
   >5Password > Again: get it from the MMS provider.
   >6Data mode >Conn oriented (vs. Connection less)
   >7Security >Off
   >8Show pictures >On
   >9Response timer >Seconds: 150
You now must set the “message server”. After having chosen the right MMS wap profile, from the main menu go to Messages, 2MMS, 5Options, 6Message server and set the http address given to you by the MMS provider.
   Stepping back consider setting the 5Auto download to “Confirm” rather than to always “On”. This lets you choose when to download a MMS that has been announced to you (always via SMS) – see “secondly” above.
   Also make sure that your own mobile phone number, sometimes called MSISDN, Mobile Station International Subscriber Directory Identity, e. g. +491713322017, is known to your phone. If you go to Phone book, 7Special numbers, 2My numbers, 1My mobile, then you should see your mobile phone number there.

More about Smil:

Free Real One Player for MMS, specifically able to decode smil: (8.577 kByte):
https://trial.real.com/pt/order.html?ppath=rodnld120401a&language=EN&country=US&dc=242322&src=de_cp,020201r1choice_c1. Beware: Special text characters like umlauts (ü etc.) are not presented correctly by the Real One player.
Try your player here.
Smil basics: http://www.realnetworks.com/resources/realoneplayer/smil/smil_basics.html?UK=X
Tutorial: http://www.helio.org/products/smil/tutorial/chapter1/index.html
and http://www.realnetworks.com/devzone/tutorials/authoring/smil/smil_basics.html?src=r-w3,nosrc
Information on Smil:
http://www.w3.org/TR/smil20/
Smil 2.0 Specs, W3C Working Draft 21 Sept 2000:
http://www.w3.org/TR/2000/WD-smil20-20000921/
http://www.w3.org/AudioVideo/
http://www.cwi.nl/~media/SMIL/
http://www.empirenet.com/~joseram/
Smil Demo:
http://www.realnetworks.com/devzone/showcase/index.html?src=r-w3,nosrc
 
Current smil incompatibility Real One Player vs. T68:
The Real One Player reports: SMIL: Bad attribute near line 0: region region1_2
The smil file looks like this (example):
<smil><head><layout><root-layout/>
<region id="region1_2" top="0" left="0" height="50%" width="100%"/>
<region id="region2_2" top="50%" left="0" height="50%" width="100%"/>
</layout>
</head>
<body><par dur="15000ms"><img src="Cid:0000" region="region1_2" fit="fill"></img>
<text src="Cid:0001" region="region2_2"></text>
</par>
</body>
</smil>
Remedy: Open the smil file with the Editor or Notespad and replace the file names like Cid:0000 with the real ones, delete the lines with “region id”. The Real-palatable file then might look like this:
<smil><head><layout><root-layout/>
</layout>
</head>
<body><par dur="15000ms"><img src="Carlaa.gif" region="region1_2" fit="fill"></img>
<text src="mms.txt" region="region2_2"></text>
</par>
</body>
</smil>
   Another Smil problem has been communicated by Juan Bautista:
In SMIL presentations, the scene is rendered within a window, so we have to give it width and height in the SMIL control file as shown below. (The following source code would create a window with a 300x200 pixels dimension.)
<smil>
   <head>
      <layout>
           <root-layout width="300" height="200" />
      </layout>
   </head>
   <body>
   </body>
</smil>
   However  the SMIL file generated from a T68i looks like this:
<smil>
   <head>
      <layout>
         <root-layout/>  <-- No region size is defined here! and RealPlayer displays an error because it does not know the absolute window size.
          <region id="Image" top="0" left="0" height="50%" width="100%" fit="hidden"/>
          <region id="Text" top="50%" left="0" height="50%" width="100%" fit="hidden"/>
      </layout>
   </head>
   <body>
      <par dur="2000ms">
         <img src="0025.jpg" region="Image"></img>
         <text src="mms.txt" region="Text"></text>
      </par>
   </body>
</smil>
   If we set the window size (e.g. 600x640 pixels), the above message would look like this:
<smil>
   <head>
      <layout>
         <root-layout height="600" width="640"/>
          <region id="Image" top="0" left="0" height="50%" width="100%" fit="hidden"/>
          <region id="Text" top="50%" left="0" height="50%" width="100%" fit="hidden"/>
      </layout>
   </head>
   <body>
      <par dur="2000ms">
         <img src="0025.jpg" region="Image"></img>
         <text src="mms.txt" region="Text"></text>
      </par>
   </body>
</smil>
And RealPlayer now understands it with no problems at all.

More about pictures in the Ericsson T68 (in German see http://www.Joern.De/T68)
   Picture size is 101 × 80 (hight) pixels, or 80 × 60. If your picture is higher than 80 pixels (81 pixels) it will appear very much reduced in size! So take care about pixel size.
   Pictures up to under 3 kByte can be loaded via wap, pictures up to 8 kByte can only be loaded locally via infrared or other connections; they may also be sent by MMS. (To transfer a picture from the PC to the mobile phone via infrared with Windows 98 or later select the picture in your Windows Explorer, click the right mouse button, select “Send to” and “Infared”. With Windows 95 try this.)
   Over-the-air pictures must be gif (not jpg!) or wbmp, the wml source file has to look somewhat like this:
<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="gif" title="Fritz J&#xF6;rn">
<p>
<img src="fritz.gif" alt="Fritz J&#xF6;rn"/>
</p>
</card>
</wml>
(As to the presentation of umlauts in WML see www.Joern.De/tipsn73.htm#wml, German.)
   Local pictures can be jpg, great, over-the-air pictures just wbmp or gif, sorry for that. Don’t be astonished if you miss some of your pictures, when you try to compose a MMS: jpg pictures are automatically ignored for that purpose.
   When you attatch a “Communicam” camera to your T68 you can shoot 24 bit RGB jpg pictures with a resolution of 80 × 60 Pixels = 4,800 Pixels (4 kByte) as seen here at right, 160 × 120 = 19,200 (8 kByte), 320 × 240 = 76,800 (13 kByte) or 640 × 480 = 307,200 (41 kByte). If needed you can rotate the image in the camera. If you send a picture to an e-mail address you might want to do that as a courtesy lest the recipient has a notebook he or she can turn around easily (see my true examples above ...) All but the too big 640 × 480 pictures should be MMS mailable.

Animated gifs work all right with the T68, but only when sent via MMS (or infrared)! If you try to wap-load an animated gif and you find such a small one that loads (ca. 2 kByte, like the beating heart) you’ll just see one single still picture in T68’s wap browser. Here is a tested example, my daughter Carla, 36 kByte. I loaded it via infrared, as “the T68 and T68i appear to be able to receive MMS messages of over 30 kByte but will not send them. Your Carla is 36,323 bytes and is probably too large to resend,” comments James Ewing of mi4e.com – and he’s right: When I cut 2 frames out of Carla’s original 7 frame sequence I get down to 26 kByte and there she is for you, MMS mailable! (When composing an outgoing MMS you just won’t be offered a picture larger 20 kByte, you will just see in under “my pictures”. For larger pictures consider e-mail.) You might like the even smaller hummingbirds (22 kByte), MMS-tested too! Naturally, the movement of gifs is slower in the T68 than in a PC.
   I took Carlas original picture with a Canon Digital Ixus set to video. You get an AVI (“audio video interleaved”) file of one MByte or more. With the free program VirtualDub (<700 kByte download) you open the video and select an appropriate small passage (Carla is just 7 frames). Set video to full processing mode, click on filters, add, select resize, to 101 × 80 pixels (some other sizes won’t pass VirtualDub), and file save as AVI. Never mind the size warning. Now all you need is converting the AVI file into an animated gif. I did this with a free GIF animator (324 kByte download). Select animation looping, repeat forever. Now you have the final animated gif, some ten to fifty kByte. This file you infared transfer into your T68, where it winds up under “my pictures”. (If it “cannot be displayed” and all you see is a red ×, do not despair, just switch the T68 off and back on. Some memory defragmentation always helps: Note that after reception animated gifs are expanded into their individual pictures, blowing up the picture file in the T68!) By the way: More and less decent animated gifs are on my i-mode site http://i.Joern.com.
   May 2004. Here, friends, is an update with Carla at age 2½ relaxing from a bike ride along the Rhine, with Bonn’s Kennedy bridge in the background. It’s a fine screen saver for my newer Sony-Ericsson T610 with 128 × 160 pixels, 186 kByte unexpanded, blowing up to 905 kByte in the mobile phone!
   GIFs have no sound. So you might want to add the corresponding sound with a smil sequence. This will make your MMS into a real little video!
   If you want or need to bother with wap’s WBMP pictures, I suggest to use the converter in the web at teraflops.com/unicon. Just for looking at a wml picture you may want to use a wap emulator, like M3-Gate from numeric.ru, with “skin” set to “April”. Point the emulator at your local file and see the WBMP picture. Note however that many emulators don’t display jpgs of gifs on the other hand.

You’ll encounter problems trying to listen to AMR encoded sound in your PC. Quicktime, RealOne or Windows Media players don’t know this format yet. And the current commerical MMS servers don’t bother to convert to or from wav when transfering a MMS to or from e-mail.
   The Canadian company Voiceage, experts in this speech compression technology using Algebraic-Code-Excited Linear Prediction (ACELP), now has a fine plug-in amr decoder for your Windows Media Player (8.0, 7.1, or 6.4) on Windows 98SE, 2000, ME, and XP available here, 9129 kBytes. A plug-in for Real Networks RealOne Player and Apple QuickTime (Windows and Mac OS X) which will be available soon. Find this and more converters below.
   A simple converter from amr to wav and vice versa can be found directly here (That’s at www.Ericsson.com/mobilityworld. There go to “Open Zone”, “Technologies Messaging”, “Tools and Enablers”, “EMS Converter”. You have to sign in then.) The converter runs under Dos and is called with “converter amr2wav input.amr output.wav” or “converter wav2amr input.wav output.amr”, with “input” containing the recording to be converted. Incidentally, the converter offered at www.Totonox.com/Software.html is exactly the same one, just gift wrapped without mention of its souce ...
   You find an AMR test sample there and right here (3 kByte), also as zip file.
   Real phone fans may use “iMelody” for sounds. This is the glorified ringtone composition method standardized by the Infrared Data Association (IrDA). It even allows you to blink the lights and activate the vibrator alarm. A famous demo lets the T68 “walk” upright on the lable, just rattling along:
   BEGIN:IMELODY
   VERSION:1.2
   FORMAT:CLASS1.0
   NAME:Move-A-Phone v1.0
   BEAT:200
   STYLE:S1
   Melody:(vibeonr5vibeoff@100)*0c3*0c3(ledonr3ledoff@10)*0e3*0e3(vibeonr1vibeoff@30)(vibeonr5vibeoff@100)
   END:IMELODY
Store this in a file, named for example t68walk2.imy, infrared send it to the T68, where it will be stored under “My sounds”. Now “play” it, and be sure to carefully stand the T68 steam engine on a flat table surface!
   ... and as romantic ringing giveaway a real melody from my home country: »Kein schöner Land ...« (more about it)

To somewhat protect copyrighted music or other content Ericsson has made the T68 accept a special content header type. Here is how to protect a picture for example:
   Content-type: application/vnd.mms.ericsson.protected
   X-Mms-Ericsson-Protected: image/gif; name="Carla.gif"
   etc.
The protected entity will not leave the phone digitally, other than by sound or display picture ...

MMS without MMS-C
   Normally you’d expect to get your MMS via a MMS center, typically c/o your provider. Georg Niklfeld pointed this out to me: You can receive MMSs just via wap, you need not to be registered with a given MMS-C. This works with certain settings in the originating wap site, and in your mobile phone.
   The server must offer a notification MMS, typically some 90 byte, telling your phone what to retrieve where. The “real” MMS has so stored in the server as well, containing the full smil encoded mms information. Wap to his site at http://tagtag.com/gold and see. (The example notification MMS is here, the content MMS here, more details in Yahoo’s discussion group on MMS, where you have to sign in. Once in, select messages and start with number 60). Note that the server must hand out these files with MIME type “application/vnd.wap.mms-message”, or else they won’t find their way to the MMS side of your phone. (You must be web master of your server to set this MIME type, a normal user with just a homepage site won’t be able to do this, just as he or she isn’t able to offer wap content. Unfortunately the mobile community here is over-creative in non-standard inventions. On the “other side of the globe” you can store i-mode content easily, see my i.joern.de.)
   The receiving phone must use the very same profile under wap (T68: wap, 6Select profile) and MMS (5Options, 7Wap profile). And the message server entry (5Options, 6Message server) has to have something in it (anything will do, say “http://a.b.c”).
   Should you still get communication errors instead of George’s little MMS sound message, then your wap gateway is (miscievously) set not to let MMS (MIME type) pass through, and you are out ’o luck, sorry.
   Using this MMS-C-less MMSing you can offer your wap readers MMS packages freely, just for the cost of their downloading them (wap reading). Great, eh?

If you get error 404 instead of the expected MMS, then the MMS server has deleted the MMS and you have come too late to get it. Error 404 generally means the Internet page you address is missing. Normally the MMS server deletes messages of a given short validity, say an offer for a last minute trip, or routinely, if you don’t come to fetch your MMS in time – within three days for example with T-Mobile. (MMS server developers are working on a friendlier message.)

Can you imagine how much of my private time it took to make this page? So drop me a line if your found it useful.