[asterisk-dev] The "Busy" App.... isn't.

[Matt Fredrickson]

On Thu, Apr 5, 2018 at 9:30 AM, Jared Smith <jaredsmith at jaredsmith.net> wrote:
> On Wed, Apr 4, 2018 at 7:17 PM, Richard Mudgett <rmudgett at digium.com> wrote:
>>
>> The argument is used when the channel is already answered.  The channel
>> will then send
>> the busy tone inband for the specified number of seconds and hangup.  The
>> behavior also
>> depends upon the channel driver.
>>
>> exten = _X.,1,NoOp()
>> same = n,Answer()
>> same = n,Busy(15)
>> same = n,Hangup()
>
>
> My understand is, at least for some channel drivers/technologies, that it
> should also work when the channel is *not* answered, because answering the
> call can mess up your CDR records.  My guess is that's what Steve is trying
> to accomplish here... signal that the "line" is busy and can't be answered,
> without actually answering the call.

In the case of chan_sip (which it looks like he's using), this is
actually what happens (and happened).  If you use the Busy()
application prior to the call being Answer()'d, it sets back the 486
Busy Here indication (as per his original debug).  As a side affect,
since the call is over at this point, this also hangs the channel up
immediately as well.

As mentioned previously, if he were to Answer() the call first, I
think it would wait the 15 seconds desired and play busy tones
in-band.

-- 
Matthew Fredrickson
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA