[OpenSIPS-Users] Presence Aggregation Idea

[Damien Sandras]

Hi Saúl,

Le 15/11/11 10:16, Saúl Ibarra Corretgé a écrit :
> Hi Damien,
[...]


>> Would it be a good idea to use the 'q' parameter to determine the various resources priorities and have a new setting in the configuration to choose to only notify the state with the highest priority ?
>>
>> That way, if you have a softphone and a desk phone, if you set your deskphone to "Busy", but put your softphone as "available" and the softphone has the highest priority, people know you are available. Most people would think that "busy" would win, but it can simply mean that I am reachable but do not want to be reachable through my desk phone. That is different than with Jabber, but telephony is different anyway.
>>
>> Well, to summarize, having a "winning" presence device would solve many problems.
> I like the approach :-) And I'd like to propose another one, leveraging the recently added GRUU support in OpenSIPS.
>
> (lets assume all devices support GRUU for a moment)
>
> Each device would publish it's own presence and indicate it's own device ID in the "device_id" element of the presence tuple. The presence agent would aggregate al tuples and push the responsibility of deciding what the real state of a user is to the client. I use the PSi jabber client and while it displays a single state for each of my buddies it also displays the state off all devices if I hover the buddy. That is useful sometimes :-)
>
> Thoughts?

That's also a good idea.

But the problem that we are facing happens with IP Phones from various 
brands : Polycom, SNOM, Grandstream, ...

They all support only one tuple at a time. That is why we also need (I 
think) a way at the server level to aggregate the presence states. What 
do you think ?

Damien