[Blink] Problems being transferred

Adrian Georgescu ag at ag-projects.com
Wed Jan 13 21:58:05 CET 2016


> On 13 Jan 2016, at 18:57, Jeff Pyle <jeff.pyle at fidelityvoice.com> wrote:
> 
> Hello,
> 
> A colleague of mine is experiencing a problem in Blink Pro when an auto attendant (FreeSWITCH) sends him a REFER to a conference bridge room.  I cannot reproduce the problem on my system.  Screenshots and debugs attached.
> 
> He dials 0549 to connect to the auto attendant, enters a PIN via DTMF, then the AA sends a REFER to point him to the correct conference room on a different server.  Blink reports the transfer as having succeeded (image #1), and the original call disappears from Blink (image #2).  Even though there is an audio session with the conference bridge, the timer never starts. 

> He hangs up the calls (image #3), but it never disappears from the screen. 

If it never disappear I suspect there is a bug in the code. This potentially also explain the fact that the timer does not start. Can you check OS X console application if Blink spits out any exception at that point ?

Adrian


> He calls a different extension 4106 (image #4), cancels it, but the disconnect conference call is still on the screen (image #5).
> 
> 
> - Jeff
> 
> <TransfereeProblems.zip>_______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20160113/6746e6d5/attachment.html>


More information about the Blink mailing list