Hello,

On 03/29/07 21:56, Juha Heinanen wrote:
Kobi Eshun writes:

> I wrote a patch that does this about 6 weeks ago, although it > probably will not compile against 1.2x any more. It turned out to be > quite a big patch (about 1600 lines) although some of it was > cosmetic. The big "problem" with adding support for message-summary > is that the presence module implements two specific event RFCs, > "presence" and "presence.winfo." Much of the logic in the module > assumes this (or did at the time).

kobi,

this does not sound very promising. i would have thought that adding
support for such a simple event package would not be more than a couple
of hundred lines of code.  openser von slides say about presence
implementation:

modular design for presence
one presence engine
several (specialized or not) components to inject presence
information
this design enables:
presence support for non-SIP entities
publish the CPU usage of your desktop
publish weather information
publish the stock size from your store
presence support for old SIP phones
easy creation for custom/complex presence extensions

just to shed some light here. The modular concept referred to collecting presence information (e.g., from subscribers, from usrloc, from MI). Unfortunately, the event types for presence sometimes require very different processing. You can make a module to publish presence information for MWI using SIMPLE specification, not the text-based old version.

You can have a virtual user voice.messages which can be added by your subscribers to their buddy list and they will see in status the number of voice messages - some similar examples (not per user) using MI you can find at:

http://openser.org/dokuwiki/doku.php/presence:pua-modules#publish_details_from_system

As Anca said, development effort is ongoing to make presence server implementation as much modular as possible based on event type, too.

Cheers,
Daniel


> For the record, we ended up not using the message summary event > package for our application because it leaves unsolved the problem of > presenting the list of available messages to the client.

there are several sip phones that somehow can do that (nokia phones for
example).

-- juha

_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel


_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel

Reply via email to