[Blink] Problems being transferred

[Adrian Georgescu]

This problem is indeed critical and explains why Blink stops processing., This must be fixed in the underlying core library SIP SIMPLE Client SDK not Blink.

Can you submit a bug report together with the SIP trace that caused this and this exception to:

http://sipsimpleclient.org/projects/sipsimpleclient/issues <http://sipsimpleclient.org/projects/sipsimpleclient/issues>

I will make sure it gets fixed.

Adrian

> On 14 Jan 2016, at 15:05, Jeff Pyle <jeff.pyle at fidelityvoice.com> wrote:
> 
> <type 'exceptions.AttributeError'>: 'sipsimple.core._core.ToHeader' object has no attribute 'user'
> 1/14/16 08:31:37.712	Blink Pro[93442]	(
> 	0   CoreFoundation                      0x00007fff9b920ae2 __exceptionPreprocess + 178
> 	1   libobjc.A.dylib                     0x00007fff9072f73c objc_exception_throw + 48
> 	2   CoreFoundation                      0x00007fff9b920679 -[NSException raise] + 9
> 	3   _objc.so                            0x000000010db62e07 PyObjCErr_ToObjCWithGILState + 46
> 	4   _objc.so                            0x000000010db4f84d method_stub + 4966
> 	5   _objc.so                            0x000000010db4325b ffi_closure_unix64_inner + 511
> 	6   _objc.so                            0x000000010db4291e ffi_closure_unix64 + 70
> 	7   CoreFoundation                      0x00007fff9b866bc4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
> 	8   CoreFoundation                      0x00007fff9b866853 __CFRunLoopDoTimer + 1075
> 	9   CoreFoundation                      0x00007fff9b8e4e6a __CFRunLoopDoTimers + 298
> 	10  CoreFoundation                      0x00007fff9b821cd1 __CFRunLoopRun + 1841
> 	11  CoreFoundation                      0x00007fff9b821338 CFRunLoopRunSpecific + 296
> 	12  HIToolbox                           0x00007fff879bd935 RunCurrentEventLoopInMode + 235
> 	13  HIToolbox                           0x00007fff879bd76f ReceiveNextEventCommon + 432
> 	14  HIToolbox                           0x00007fff879bd5af _BlockUntilNextEventMatchingListInModeWithFilter + 71
> 	15  AppKit                              0x00007fff8b7d60ee _DPSNextEvent + 1067
> 	16  AppKit                              0x00007fff8bba2943 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
> 	17  AppKit                              0x00007fff8b7cbfc8 -[NSApplication run] + 682
> 	18  AppKit                              0x00007fff8b74e520 NSApplicationMain + 1176
> 	19  _AppKit.so                          0x000000010e4d3835 objc_NSApplicationMain + 286
> 	20  libpython2.7.dylib                  0x000000010ac5aa0b PyEval_EvalFrameEx + 13400
> 	21  libpython2.7.dylib                  0x000000010ac573c1 PyEval_EvalCodeEx + 1583
> 	22  libpython2.7.dylib                  0x000000010ac5d4ae _PyEval_SliceIndex + 342
> 	23  libpython2.7.dylib                  0x000000010ac5a30c PyEval_EvalFrameEx + 11609
> 	24  libpython2.7.dylib                  0x000000010ac573c1 PyEval_EvalCodeEx + 1583
> 	25  libpython2.7.dylib                  0x000000010ac56d8c PyEval_EvalCode + 54
> 	26  libpython2.7.dylib                  0x000000010ac76a42 PyParser_ASTFromFile + 300
> 	27  libpython2.7.dylib                  0x000000010ac76ae5 PyRun_FileExFlags + 133
> 	28  libpython2.7.dylib                  0x000000010ac76634 PyRun_SimpleFileExFlags + 698
> 	29  Blink Pro                           0x000000010abc7348 Blink Pro + 4936
> 	30  libdyld.dylib                       0x00007fff91cb75ad start + 1
> )
> 
> Full log attached.
> 
> 
> - Jeff
> 
> 
> 
> 
> On Wed, Jan 13, 2016 at 3:58 PM, Adrian Georgescu <ag at ag-projects.com <mailto:ag at ag-projects.com>> wrote:
> 
>> On 13 Jan 2016, at 18:57, Jeff Pyle <jeff.pyle at fidelityvoice.com <mailto: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_pro.log>_______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com <mailto:Blink at lists.ag-projects.com>
> http://lists.ag-projects.com/mailman/listinfo/blink <http://lists.ag-projects.com/mailman/listinfo/blink>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20160114/b3de8230/attachment-0001.html>