[Blink] Bug with Barging
bmill at socialserve.com
Tue Oct 29 14:15:23 CET 2013
On Oct 29, 2013, at 7:00 AM, blink-request at lists.ag-projects.com wrote:
> Date: Tue, 29 Oct 2013 09:23:04 +0100
> From: Sa?l Ibarra Corretg? <saul at ag-projects.com>
> To: Blink Support Forum <blink at lists.ag-projects.com>
> Subject: Re: [Blink] Bug with Barging
> Message-ID: <78B3F3CB-985C-438A-9F23-12F7EDDCC071 at ag-projects.com>
> Content-Type: text/plain; charset=iso-8859-1
> On Oct 28, 2013, at 10:20 PM, Bryan Miller wrote:
>> In 2.1.0 users could barge a call (chan-spy in asterisk) and the call would not drop even after the person being barged ended the call. (It continues to barge while there is no call, allowing the person barging to continue monitoring the ext for calls made or calls that ring to that ext.) Our version of asterisk has not changed.
>> In 3.3.0, it kind of works. After the call has finished, it will drop the call after 30 seconds. Disabling the "Hangup On Timeout" option allows the call to continue barging. However, if you barge an ext that does not have an active call, it hangs up after 60 seconds, not the normal 30 seconds, in spite of the "Hangup On Timeout" being disabled. It only works if you barge a call that is active.
>> Can you make a code change so that Blink behaves the same as it did in 2.1.0 when there's no RTP data coming in?
> Hi Bryan,
> Call is probably closed due to the lack of RTP. In 3.3.0 there is a setting for it, which defaults to True, but you can change it! Go to the preferences panel, select an account, advanced, RTP Media, and uncheck "Hangup On Timeout" that should do.
Yes. I've disabled this. It presents the problem I described above. If there is no call on the ext you are barging, it hangs up in 60 seconds. If there is a call on the ext that you are barging, it stays connected.
It should stay connected when you barge, irrespective of an active call, after disabling "Hangup On Timeout". It does not.
More information about the Blink