From 33bdb442ed8966c36a0323ff4e2d357a7a5e7ff9 Mon Sep 17 00:00:00 2001 From: oej Date: Thu, 30 Nov 2006 18:22:10 +0000 Subject: Doxygen updates git-svn-id: http://svn.digium.com/svn/asterisk/trunk@48149 f38db490-d61c-443f-a65b-d21fe96a405b --- main/devicestate.c | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) (limited to 'main/devicestate.c') diff --git a/main/devicestate.c b/main/devicestate.c index 0711a1002..9fe50e6f1 100644 --- a/main/devicestate.c +++ b/main/devicestate.c @@ -22,6 +22,8 @@ * * * \author Mark Spencer + * + * \arg \ref AstExtState */ /*! \page AstExtState Extension and device states in Asterisk * @@ -59,10 +61,26 @@ * - SIP subscriptions, a.k.a. "blinking lamps" or * "buddy lists" * - * None of these handle user states, like an IM presense + * The CLI command "show hints" show last known state + * + * \note None of these handle user states, like an IM presense * system. res_jabber.c can subscribe and watch such states * in jabber/xmpp based systems. * + * \section AstExtStateARch Architecture + * + * When a channel driver or asterisk app changes state for + * a watched object, it alerts the core. The core queues + * a change. When the change is processed, there's a query + * sent to the channel driver/provider if there's a function + * to handle that, otherwise a channel walk is issued to find + * a channel that involves the object. + * + * The changes are queued and processed by a separate thread. + * This thread calls the watchers subscribing to status + * changes for the object. For manager, this results + * in events. For SIP, NOTIFY requests. + * * */ -- cgit v1.2.3