,
Andrew & Deborah
-Original Message-
From: Paul Bagyenda [mailto:bagye...@dsmagic.com]
Sent: Tue 5/31/2011 7:27 AM
To: Andrew Caruana
Cc: users@mbuni.org
Subject: Re: [Users] MMS User Provisioning
Hi Andrew,
You want to return the msisdn as standard output, to wit:
#!/bin/bash
echo 00356123
file:
>
> detokenizer-library = "builtin:shell"
> detokenizer-module-parameters = "/usr/local/bin/mmsc_150/test_script"
>
>
> Thanks and kind regards,
>
>
> Andrew & Deborah
>
>
> -Original Message-
> From: kitand...@gmail.co
le:
detokenizer-library = "builtin:shell"
detokenizer-module-parameters = "/usr/local/bin/mmsc_150/test_script"
Thanks and kind regards,
Andrew & Deborah
-Original Message-
From: kitand...@gmail.com on behalf of Paul Bagyenda
Sent: Mon 5/30/2011 7:01 AM
To: Andrew Ca
on type)
- event (sent,received, etc)
- msisdn
- msg ID
- user-agent
- UAProf
> Thanks and regards,
>
>
> Andrew & Deborah
>
>
>
> -Original Message-
> From: kitand...@gmail.com on behalf of Paul Bagyenda
> Sent: Thu 5/26/2011 1:50 PM
> To: Andrew Caruana
6/2011 1:50 PM
To: Andrew Caruana
Cc: users@mbuni.org
Subject: Re: [Users] MMS User Provisioning
User provisioning is entirely outside of Mbuni. All that's required is that for
each incoming MMS Mbuni can determine the sender. This is typically done using
special HTTP headers added by your
User provisioning is entirely outside of Mbuni. All that's required is that
for each incoming MMS Mbuni can determine the sender. This is typically done
using special HTTP headers added by your WAP GW. For billing, again we call
a configured script, which can prevent delivery as needed based on use
