Thanks for that patch. Some code gets written at the wrong time of day!
On MM4 authorisation, that had put that on a back burner. The reason for this is that it wasn't clear how to implement it. Must the sender use authenticated smtp? How does info get passed on to mbuni?
On MM7, the idea is a good one. We can modularise in the same way as was done for billing, etc. Once we have the MM7 itself well tested, we can move on to that.
On Apr 14, 2005, at 23:10, Dziugas Baltrunas wrote:
Hi Paul,
while looking at MM7 implementation code and escpecially at mmlib/mms_strings.c (tried to understand once again (C) Lars Wirzenius preprocessor tricks), I found some minors bugs. Diff attached.
Btw, are there any plans to implement VASP authorization for MM4? Another approach would be to unify these credentials (wrote about this some time ago). I'm thinking about a patch which would make a possibility to authorize VASP's calling some external module (which would query DB for example). I think it's important because operator often has lots of duplicates of the same VASP (for each SMPP, MM MM7, MM MM4, PPG etc. connection).
On 4/14/05, Paul Bagyenda <[EMAIL PROTECTED]> wrote:Thanks Dziugas,
As I understand it, sf.net anonymous cvs is a couple of hours behind the developer one. Give it sometime and the changes should be visble. Otherwise my cvs would be lying to me :)
On Apr 14, 2005, at 15:19, Dziugas Baltrunas wrote:
Hi Paul,
congratulations once again for such a useful feature implementation!
It seems that Sourceforge again has long delays or you forgot to commit the changes, because MM7 changes are missing (at least doc/userguide.shtml and some others).
On 4/14/05, Paul Bagyenda <[EMAIL PROTECTED]> wrote:CVS has been updated with our first implementation of MMS VAS support
in Mbuni.
The short story: Mbuni now supports sending and receiving MMS via the MM7/SOAP protocol as specified in 3GPP 23.140. Get CVS and play.
The longer story: In the config file for mbuni (cvs version that is) you can define one or more value added services providers (VASPs). The userguide (found in the doc/ directory) explains how to do this. (A sample config file sent.) Mbuni will then accept messages from VASPs and send them on, and will also send messages to VASPs when received.
Since this required yet more changes to Kannel, you must first patch
and install Kannel before compiling Mbuni. (Patch file is in directory
misc-patches/.) Specifically, we updated the Kannel config file format
to include the new directives, and also added a new function to
mime.[ch] (existing ones were somewhat broken).
For testing purposes, the Openwave MMS SDK (found at http://developer.openwave.com/dvl/tools_and_sdk/openwave_mobile_sdk/ mms_sdk/) is useful. It also comes with the actual source code (very useful, since the supplied lib -- vaspapi.jar -- has a bug or two). The SonyEricsson lib seems a bit limited...
Next we plan to implement the EAIF interface, while we clean-up the
SOAP code. Very good feedback has been received on the mmbox code, and
a number of fixes have been done in the meantime. All on cvs.
Please send feedback. Lets hope no bugs were introduced :)
Cheers
Paul
PS: cvs browsing: http://cvs.sourceforge.net/viewcvs.py/mbuni/mbuni/
_______________________________________________ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
-- Dziugas
_______________________________________________ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
_______________________________________________ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
-- Dziugas <mbuni_patch.txt>_______________________________________________ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
_______________________________________________ Devel mailing list Devel@mbuni.org http://mbuni.org/mailman/listinfo/devel_mbuni.org
