Earlier, I asked:
> I have a design question about this - why is PA making an XML RPC call
> to sipXivr to get the presence status? Presence status is maintained
> in
> sipXrls - this seems like an excessively complicated way to go about
> this. Shouldn't PA get presence from sipXrls?
Martin Pepin wrote:
> As for the XML-RPC call, it is designed to query the "sip-presence"
> field of UnifiedPresence. The sip-presence field is actually updated by
> the Openfire plug-in which makes use of sipXrls to determine this
> information.
>
> "2009-09-29T12:25:21.072000Z":2:sipXivr:INFO:bcmdesk2180.ca.nortel.com:m
> ain:00000000:sipxivr:"Unified Presence: {status-code=ok, sip-id=201,
> custom-presence-message=On the phone, unified-presence=not-available,
> [email protected], xmpp-presence=OFFLINE,
> sip-presence=BUSY}"
>
> "2009-09-29T12:26:11.601000Z":2:sipXivr:INFO:bcmdesk2180.ca.nortel.com:m
> ain:00000000:sipxivr:"Unified Presence: {status-code=ok, sip-id=201,
> custom-presence-message=, unified-presence=available-for-phone,
> [email protected], xmpp-presence=OFFLINE,
> sip-presence=IDLE}"
>
> When a user is on a call, sip-presence shows "BUSY". Otherwise,
> sip-presence shows "IDLE" or "UNDETERMINED". This information is
> required by the Personal Assistant feature.
I guess I'd like a big-picture view of:
* Which component 'owns' presence?
* Which components affect it
* Where they get the data
* How they update the integrated/unified presence state
* How that state is made available
Can someone please draw this picture so we can all look at it and make
sure that everyone agrees?
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
