[Blink] New Blink Qt 3.0.0 version for MS Windows

Adrian Georgescu ag at ag-projects.com
Fri May 12 21:25:17 CEST 2017

My claim is that the underlying library used by Blink implements call transfer correctly. From my point of view it is safe to assume that the other end-points or their networks are misbehaving, unless one can prove otherwise. The failure reason can be found by providing the SIP trace of the call in question. It may be too technical but there is no other way.

The problem with troubleshooting call transfer on public Internet is that it involves 3 separate entities, and each of them may belong to different vendor, service or network.


> On 12 May 2017, at 15:58, Mediacast Guy <mediacastguy at gmail.com> wrote:
> On 5/9/2017 1:41 AM, Dan Pascu wrote:
>>> I called into a SIP number using my cell phone and tried to transfer the call to another cell phone. It didn't work.
>> I literally addressed this particular example in my answer above and stated that it won't work as SIP-to-PSTN gateways
>> do not support call transfer.
>>> Then I tried to transfer to another SIP number it didn't work.
>> If one leg of the call was still a mobile phone, nothing changed nothing changed, so yes it would still not work.
>>> What I don't understand is why it worked before. It's
>>> confusing because I've been told that "call transfer is a function of the client not of the provider." Isn't Blink the
>>> client?
>> It takes two to tango. I laid down the conditions that need to be satisfied in my answer above. Both endpoints
>> (clients) need to support call transfer. One endpoint/client (Blink) cannot magically make the other endpoint
>> initiate/participate in a call transfer if the other endpoint/client doesn't support call transfer.
>> In all your examples that do not work you mention one endpoint being a mobile phone, hence one endpoint/client is a
>> SIP-to-PSTN gateway that doesn't support this.
>> Plus if you want to talk specifics as to why your particular attempt failed, we cannot do that by guessing what is
>> wrong or inferring the cause from loose descriptions. A SIP trace will show what is going on. 
> Too much caffeine? Don't assume everyone else understands this as well as you do. Otherwise, thanks for the answer.
> _______________________________________________
> 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/20170512/c2628d19/attachment.html>

More information about the Blink mailing list