Add some comments on queue system behaviour and how it affects the

SIP channel

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@53143 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/channels/chan_sip.c b/channels/chan_sip.c
index 334a33a424caa631c096d5dee3b33d18414bfbbb..7d96fb3f20a86c01c9fa6be1f7c660ca93a0f96b 100644 (file)
--- a/channels/chan_sip.c
+++ b/channels/chan_sip.c
@@ -15135,6 +15135,12 @@ static int sip_poke_peer(struct sip_peer *peer)
        If we return AST_DEVICE_UNKNOWN, the device state engine will try to find
        out a state by walking the channel list.
 
+       The queue system (\ref app_queue.c) treats a member as "active"
+       if devicestate is != AST_DEVICE_UNAVAILBALE && != AST_DEVICE_INVALID
+
+       When placing a call to the queue member, queue system sets a member to busy if
+       != AST_DEVICE_NOT_INUSE and != AST_DEVICE_UNKNOWN
+
 */
 static int sip_devicestate(void *data)
 {