Displaying 3 results from an estimated 3 matches for "ast_device_onhold".
2010 Mar 04
0
Availstatus returns 20 ?
.../* 5 AST_DEVICE_UNAVAILABLE */ "Unavailable", /*!< Unavailable
(not registered) */
/* 6 AST_DEVICE_RINGING */ "Ringing", /*!< Ring, ring,
ring */
/* 7 AST_DEVICE_RINGINUSE */ "Ring+Inuse", /*!< Ring and in
use */
/* 8 AST_DEVICE_ONHOLD */ "On Hold" /*!< On Hold */
};
Jonas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100304/0a9922df/attachment.htm
2009 Sep 27
1
MeetMe Hints
I've got hints setup for my MeetMe conferences like so:
exten => _60X,hint,MeetMe:${EXTEN}
and they show up in "core show hints" like so
600 at dialtone : MeetMe:600 State:Unavailable
Watchers 1
_60X at dialtone : MeetMe:${EXTEN} State:Unavailable
Watchers 0
I'm wondering why they're Unavailable instead of
2008 Dec 22
1
AMI and ExtensionState command returning bogus 'status' number
...INUSE 2
*
* Device is busy
* AST_DEVICE_BUSY 3
*
* Device is invalid
* AST_DEVICE_INVALID 4
*
* Device is unavailable
* AST_DEVICE_UNAVAILABLE 5
*
* Device is ringing
* AST_DEVICE_RINGING 6
*
* Device is ringing *and* in use
* AST_DEVICE_RINGINUSE 7
*
* Device is on hold
* AST_DEVICE_ONHOLD 8
*
*/
Am I missing something?
Is this a 'bug' or I just blew something?
May I safely base my application on the 'Status' numbers returned as
described in 'devicestate.h'?
Can someone point me to some documentation that can clarify this?
Thank you in advice,
Regars....