Chanisavail Checks if some of those asked stations are available.
Be aware the AVAILSTATUS variable is utilizing for both apparatus state and cause code. It’s thus possible in order for it to provide a price that can indicate a gadget is available as it is not. It’s suggest that your AVAILORIGCHAN factor can use alternatively to see if it’s the gadget is not.
New in Asterisk 1.8: The ChanIsAvail program now unlocks the Came Back cause code using Another variable, AVAILCAUSECODE, instead of overwriting the device state in the AVAILSTATUS
The following variables will likely put via This application:
$AVAILCHAN — that the title of this available station, in case one proceeds
$AVAILORIGCHAN — the only real station name which is using to make the station
$AVAILSTATUS — the status code to its available station (see”device state. c“)
0 AST_DEVICE_UNKNOWN –“Unknown”; station remains legitimate, but the not known state.
1 AST_DEVICE_NOT_INUSE –“Maybe not in usage”
2 AST_DEVICE being used – – “being used”; the station is as of now being using.
3 AST_DEVICE_BUSY –“hectic”; the channel is currently busy.
The application form returns”either the device condition and source code.”
Selections (brand new in Asterisk v1.2?) :
S — Consider the channel inaccessible if the station is still in use in all (buggy with SIP, always returning 0?!)
J — Confirm jumping to priority n+101 if no station can find it.
Particulars of Chanisavail
At Present, ChanIsAvail just works with ZAP, IAX2, mISDN, Skinny, and SIP stations. MGCP stations are not supporting.
If none of the requested channels are available, the new Asterisk priorities are going to be n+101 (except if this type of priority does not exist).
If anyone of the request channels is available, then the following priority is going to be +1. The channel factor $AVAILCHAN is like to soon be set to the name of this available station.
The channels will be assessing in the order record, therefore, coming to the first available channel at the list in $AVAILCHAN.
Be aware that ChanIsAvail() returns not just the title of this station at $AVAILCHAN, but in addition, appends the station’s SESSIONID. You will probably have to strip the session ID away, as illustrated in the case under.
Above all, ChanIsAvail is maybe not a solution number to inform you, whether the channel is not, it is largely to tell you whether it’d be possible to mail a telephone there 207area code. Whether that call might wind up being approved or not is solely up to the peer we mail the telephone to, plus so they are able to easily deny the telephone though they usually do not appear to be ‘active.’
So: If you would like to use ChanIsAvail to decide if the SIP peer-reviewed is understood and enrolled, However, it is going to continue to work fine. If you wish to make use of it for limiting simultaneous phone calls to your peer, it’s not going to do the job reliably for you.
For notification whether Sip peers are not or online, Therefore, once you’re employing neglect, then you may want to just use the SipPeer(‘title’: standing ) function, and jump primarily based on this. ChanIsAvail will not seem to inform you of the difference between a Sip peer-to-peer that is online, and one that’s offline. Example snippet:
Extend => s,n,Set(VOIPCHECK=0)
Extend => s,n,Place (PEERCHECK1=myprovider-out); SIP peer-reviewed name as described in sip.conf
; Be certain to possess qualifies allowed with this SIP peer!
In the event that you aren’t using real-time, you can assess the SIP/Registry tree of AstDB to your peer-reviewed concerns, so, such as together with the help of the DB_EXIST functionality.
; Observe if status two will be unrestricting. If not, decide to try lineup 1.
We, Will, Need to strip the session off ID and Dial’12345678′ at Zap/2.
; Should neither line 2 nor line Inch can be gotten, play a message.
According to insect 4506, Chanisavail is not designed to find if your mobile phone is in use or not , however, it is simply intended to check if an asterisk may deliver the call out there.
I attempted employing call-limit and Chanisavail SMS, but it’s busted in SIP. In use gets implemented only to friends, therefore, when it gets an incoming call that is not answered, In addition, it gets decremented and also doesn’t remain exactly the exact same, so, which will be a pest infestation.
You need to look at applying bands alternatively.
Limit incoming calls using DEVICE_STATE and also Asterisk 1.6
To limit In-Coming simultaneous calls into the peer, strive for DEVICE_STATE.
Technology resource technology2/resource2 zap/1 and zap/2 channel unavailable availorigchan the canonical channel status code create the channel. The application will check exten 123,1,chanisavail zap/1 requested channels. Know more about Chanisavail. and you can also Read it Unify Office User Groups Overview. and Marks and Spencer.