Skip to main content

Outlook 2003 SMS Add-in

Larkware turned up this free Microsoft SMS addin for Outlook2003 that allows you to send (but not receive) text messages within the Outlook2003 client.

MOSA toolbar

Great...except I can't get it to work with my C500 smartphone acting as the modem it requires to send the SMS - apparently the "Standard Modem over Bluetooth link" that the c500 provides to the PC does not support PDU format messages :(

MOSA send failed PDU error

As a freebie this would have been great to use - I'm not sure I send enough SMS's to warrant buying something like this software from Jeyo to do this although it's pretty cheap and gets good reviews....oh well!

Comments

Just pay the guys at Jeyo - skinflint. (I'm going to post again on my Plaxo-ActiveSync experience soon - it's not a very happy picture I'm afraid.)
Whilst I'm commenting - PDU is the byte-level format / protocol that SMS uses. SMS are actually 140 bytes long, but text messaging extends that to 160 characters by using 7-bit byte encoding.

It may be that the freebie software is setting individual byte-values and that messaging API that the C500 exposes simply can't cope with 8-bit custom PDU values, on the assumption that no one would ever want to send a binary SMS.

If so, then it would be another example of M$'s lack of phone-awareness.

I bet you a beer that a Nokia would work?
This comment has been removed by a blog administrator.
Unknown said…
Hey Hugo, challenge accepted - I'll press gang someone into lending me a Nokia ASAP and report back the results. A yuletide beer will be welcome! ;-)

Popular posts from this blog

Walk-Thru: Using Wolfpack to automatically deploy and smoke test your system

First, some history... The advent of NuGet has revolutionised many many aspects of the .Net ecosystem; MyGet, Chocolatey & OctopusDeploy to name a few solutions building upon its success bring even more features to the table. I also spotted that NuGet could solve a problem I was having with my OSS System Monitoring software Wolfpack ; essentially this is a core application framework that uses plugins for extension ( Wolfpack Contrib ) but how to unify, standardise and streamline how these plugins are made available? NuGet to the rescue again - I wrapped the NuGet infrastructure (I deem NuGet to be so ubiquitous and stable that is has transcended into the software "infrastrucuture" hall of fame) with a new OSS project called Sidewinder . Sidewinder allows me to wrap all my little extension and plugins in NuGet packages and deploy them directly from the Wolfpack application - it even allows me to issue a new version of Wolfpack and have Wolfpack update itself, sweet huh...

Configuration in .Net 2.0

11-Dec-2007 Update I've updated this post to fix the broken images and replaced them with inline text for the example xml and accompanying C# code. This post has been by far the most hit on this blog and along with the comments about the missing images I thought it was time to update it! Whilst recreating the examples below I zipped up the working source code and xml file and loaded this onto my Project Distributor site - please download it to get a full working custom configuration to play with! Just click on the CustomConfigExampleSource link on the right hand side, then the "Source" link to get the zip. We are in the process of converting our codebase to .Net 2.0. We've used Enterprise Library to great effect so decided that we should continue with this in the form of the Jan 2006 release which targets 2.0 and I've got the job of porting our Logging, Data Access etc wrappers to EntLib 2.0. ...And so far so good - the EntLib docs aren't bad and the migrati...

Deployment - the final (.Net) frontier

[Update 19th Apr 2012]  - mission complete!...v2.4.0 of Wolfpack has been released and this includes a new set of plugins that can automatically download a NuGet package then execute a deployment tool (eg: DropkicK, MSBuild.exe) - it can even run NUnit tests (via the console runner). Wolfpack v2.4.0 Wolfpack.Contrib.Deployment [Original Post] Another day, another project and deployment raises its head... Thinking that this problem must have been cracked by now I had a look around the .Net landscape and found two interesting solutions. Octopus Deploy - a .Net convention based deployment system using NuGet packages, loosely based on AppHarbour's approach. DropkicK (aka DK) - another awesome initiative from Dru Sellers et al. I like the simplicity of Octopus but also like DK's  fluent code based deployment. Hmmm, this has got me thinking - Wolfpack could easily be adapted to be used as a deployment agent. Wolfpack can already monitor a NuGet feed for new pac...