I haven’t tested this, so I can’t say for sure, but I think I would have to agree with MSDN as far as the initial bootstrapping goes. The bootstrapping is intended to be done via SMS if it is initiated server side, and this has to do with security and authentication purposes.

You can do a bootstrap from the client side over a generic data connection because this means you are running in a different security context. Similarly when the device has been bootstrapped the actual OMA DM traffic can be run over a generic data connection. (It will be bound to one data connection though probably, so you’ll have to define this in the bootstrap.)

I don’t know if there is a specific reason you want to use OMA DM in your scenario, but as far as Windows Mobile goes maybe some other solution is more suited for your use. (Depending on budget and needs of course.)

While I am happy with the SMS provider I use, (a Norwegian one), I have not done any “benchmarks” comparing providers. NowSMS is a fairly known international provider, and Sybase365 claims to be the world leader. Both should be able to provide what you need. Your local mobile operator may also have a service offering.

First, thanks for all your posts, they are really helpful as there are not too much sources on Device Management.

I wanted to ask you, Do you know of any way to provisioning a DM Server that will be reachable trough Wifi ? (I know, sounds strange, no matter why I want it, just want to know if you came up with sth).

Right now I had no luck, in fact I think its not possible (at least on WM devices), I read on http://msdn.microsoft.com/en-us/library/aa455984.aspx that only GSM-CSD and GSM-GPRS (apart from GSM-SMS, on my understanding) are supported bearers.

What I tried till now is to deploy a CPF file with a WAP provisioning XML with some tests, but of course none work.

*****
On the other hand, could you please point me to an SMS service I could use for sending WBXML and WAP Push msgs ? I mean, I can run up a Kannel, but I need someone to provide me with the real SMS sending thing (no gsm-router wanted..).

I´ll appreciate any light you could bring over these subjects, thanks in advance man!

jrub

Mostly due to the fact that the IMSI has limited value for most people – you either need access to the data from an operator, or some other means of acquiring the number. For instance through an MDM solution, but if you’ve got MDM in place you’ve sort of provisioned them already.

That being said, if I were to investigate further I would take a closer look at the security policies referenced above. Even if the device accepts OTA it might have restrictions regarding network pin messages. Go over all the security settings in the registry on your test device, and see what you can find

I have run into the same issue myself running Kannel on XP. Didn’t see it running Kannel on a Windows Server box as a service though so it could be a combination of Kannel and the OS causing the crash.

But apparently there is a fix/workaround. (I got the solution from my friend David Creedy – I didn’t figure it out myself.)

You need to edit a file – gateway-1.4.1\gwlib\thread.c
Comment out the following lines:

if (mutex->owner == gwthread_self())
panic(0, “%s:%ld: %s: Managed to lock the mutex twice! (Called from %s:%ld:%s.)”, \
__FILE__, (long) __LINE__, __func__, file, (long) line, func);

Your guide is invaluable for this – but I have the same problem when signing the XML with the netwpin – the settings are not stored.
Did you find a way around this?

Moz

After getting Kannel to work under Win XP + cygwin, I ran into some troubles. After ~ 5 Minutes the sms- & wapbox was killed with some strange Error. Ive figured out the Problem comes from cygwin itself (looks like the C Compiler is generating some Bugs).

Now everything works fine with a Debian 5 Installation and Kannel 1.4.3 + OpenSSL. Just use “./configure –enable-ssl” while compiling Kannel and follow the instructions of Andreas’ Tutorial And now it doesnt matter if you use UTF-8 or ISO-8859-1 Encoding, aslong as you set the charset you want (I use a small HTML-Form to generate the URL)

Now Kannel is running flawless and I’m ready to do some Provisioning with 400 Devices.

Only three more dll files are needed in the sms-gw folder (for the SSL), but everyone should easily manage that when getting the “Missing File” error

Again, Thank You for the very good tutorials, keep up the good work! Now I’m going to enjoy some more of your Articles

Do you have any advice for me?
I’m using Kannel 1.4.3, no openssl on cygwin installed, no errors in the box logs. Tried to deactivate the security checks for WAP OMA in the registry of the devices – no luck. played around with different xml files (im always sending via HTTP GET, XML String converted to UTF-8 URL)

thanks in advance,
stephan