Displaying 6 results from an estimated 6 matches for "ast_device_not_inuse".
2007 Mar 03
0
creating new asterisk application
Hi,
I'm writing asterisk application in C language. I need to know what is
state of my asterisk user, so I have found command: ast_device_state(data);
. So if my IP phone is reachable I get status 1
(AST_DEVICE_NOT_INUSE<http://www.asteriskpbx.com/doxygen/1.2/devicestate_8h.html#42ea804da1426b4117686332400b27c2>).
But when I have unplugged my phone's cable , and sip show peer command shows
status UNREACHABLE , but my application again shows status 1 (not in use).
My question ,is it OK? Maybe is better to...
2007 Sep 19
2
AMI extension states
Hi,
Is there a list of all the extension states as sent by the
manager interface? (I know I could look them up in the source
but that involves some "backtracing".)
The ones I know are:
-1: no hint for the extension
0: registered && idle
1: busy
4: unreachable, not registered
8: ringing
I've recently seen 16 (== hold?) but can't find that value
documented anywhere.
2010 Mar 04
0
Availstatus returns 20 ?
...l returns '20' ???
This is what inside /usr/src/asterisk-1.4.25.1/main/devicestate.c :
/*! \brief Device state strings for printing */
static const char *devstatestring[] = {
/* 0 AST_DEVICE_UNKNOWN */ "Unknown", /*!< Valid, but
unknown state */
/* 1 AST_DEVICE_NOT_INUSE */ "Not in use", /*!< Not used */
/* 2 AST_DEVICE IN USE */ "In use", /*!< In use */
/* 3 AST_DEVICE_BUSY */ "Busy", /*!< Busy */
/* 4 AST_DEVICE_INVALID */ "Invalid", /*!< Invalid...
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
...ning the 'Status' as described in
'devicestate.h'
( http://www.asterisk.org/doxygen/1.4/devicestate_8h-source.html ) ,
part of Asterisk source files.
Something like this:
/**
* Device is valid but channel didn't know state
* AST_DEVICE_UNKNOWN 0
*
* Device is not used
* AST_DEVICE_NOT_INUSE 1
*
* Device is in use
* AST_DEVICE_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...
2009 Mar 20
2
Looking for clues to this error message
[Mar 20 12:45:33] WARNING[4940]: app_queue.c:3136 try_calling: The device
state of this queue member, SIP/3617001000, is still 'Not in Use' when it
probably should not be! Please check UPGRADE.txt for correct configuration
settings.
[Cary Fitch]
We are running 1.4.22 and this message popped up in console.
It could be causing our Queues announcement problem, because if all members