I saw your message while I was gone last week. Must be quite a drawing thus far...
It also talks to sipxopenfire to "set/change" a users IM status. BLF on phones, essentially BLF state for XMPP as well but by actually changing your "status" for you so others can see. sipXpresence <=> sipxopenfire Since a user can change some status in XMPP and effect the way a call is routed too... :: XMPP status is DND, then call goes to voicemail if I set that preference in sipxconfig... It also interacts with proxy in that proxy does NOT forward the call to UA or show the missed call, sending it right to VM (even with a registered available UA of ANY type). so sipXopenfire also interacts with sipXproxy... sipXopenfire: Because MyBuddy can "proxy on your behalf" to get items like calls records (missed 9, as an example since I've been gone 9 days), I can have "MyBuddy" "yank" my CDR's to some extent so it also intercats with CallResolver... Presence is also tied to SLA. On Sun, Aug 1, 2010 at 10:55 PM, Douglas Hubler <[email protected]> wrote: > I'm trying to figure out why they are separate projects and services. > > If anyone has documentation on either of these systems, please let me > know. I know sipXrls handles BLF but that's about it. > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
