Iñaki,
What you suggest is a valid way to manage presence.
This all comes down to how presence data from different sources is
aggregated. This was discussed quite a bit once, and then we concluded
that it isn't something that we knew how to standardize. So presence
aggregation is an area for product innovation. Some may want it the way
you suggest. Others may really want a single view of presence.
Thanks,
Paul
Iñaki Baz Castillo wrote:
> Hi, SIMPLE presence is a bit annoying when the AoR for him presence
> status we subscribe has registered various locations.
>
> I just ask a lazy question: wouldn't be useful if the SIP presence
> mechanism shows each AoR's contact separately? For example:
>
> - bob AoR is registered from phone1 and phone2.
> - bob phone1 sends a PUBLISH indicating some field describing him
> location ("home" for example).
> - bob phone2 sends a PUBLISH indicating him location ("office").
> - alice subscribes to bob presence status.
> - alice receives a NOTIFY describing the state of bob AoR for "home"
> resource and the state of "office" resource.
> - alice's phone would render two "faces" of bob AoR.
> - If bob at home sets "offline" status then alice would be bob
> "office" status as offline, but would remain seeing "home" resource as
> online.
>
> Is it feasible with the current(s) espec(s)?
>
> Thanks a lot.
>
>
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
