[Blink] New Blink QT release 5.6.0 with OpenPGP encrypted file transfers support

[Adrian Georgescu]

Hello,

There is a new version of Blink Qt with end-to-end OpenPGP encrypted file 
transfers support using MSRP push and pull methodologies. The files can be 
synced between multiple devices and downloaded also after Blink becomes online.

File transfers are interoperable with end-points that implement OMA RCS.07, 
including desktop clients like Linphone.

Change-log

   * Added support for filetransfer messages
   * Added support for encrypting/decrypting MSRP file transfers
   * Added support for file encryption/decryption
   * Added support for displaying conference files
   * Added support for pull file transfers
   * Added HTTP download function
   * Added filepane content
   * Added replace function for chat messages
   * Added menuitem in chat to send files
   * Added unique name generator function
   * Support removing messages
   * Fixed displaying decryption error
   * Fixed parsing images in chat, they should be base64 encoded
   * Fixed traceback for incoming messages without disposition
   * Prevent traceback on PGPKeys load when there is no chat in the session
   * Several UI fixes
   * Python >= 3.10 fixes
   * Update help and release notes urls

To install or upgrade the software go to http://icanblink.com 


I wish to express my thanks to NLnet Foundation for helping us with funding the 
works for this development!

https://nlnet.nl/
—
Adrian




signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] DNS-SRV / DNS-NAPTR?

[Adrian Georgescu]

Blink automatically uses DNS NAPTR and SRV records to lookup the proxy address, 
just enter the SIP account as username@domain

There is nothing to configure for this to happen

 —
Adrian




> On 20 Mar 2023, at 19:46, Sebastien Cramatte  wrote:
> 
> Hello,
> 
> Anybody can tell me how to setup Blink on Mac to use DNS-SRV/DNS NAPTR?
> Regards
> 
> 
> --
> 
> 
> Parque Científico de Murcia, Edif. "T", 1ª planta
> Complejo Espinardo -Crta. Madrid KM 388
> 30100 Espinardo (Murcia) - ESPAÑA
> 
> T: +34 902 918 091
> F: +34 868 97 33 97
> M: +34 627 665 283
> E: scrama...@nixus.es 
> W: www.nixus.es 
> 
> [Atención] La información contenida en este e-mail es confidencial, 
> privilegiada y está dirigida exclusivamente a su destinatario. Cualquier 
> revisión, difusión, distribución o copiado de este mensaje sin autorización 
> del propietario está prohibido. Si ha recibido este e-mail por error por 
> favor bórrelo y envíe un mensaje al remitente.
> [Disclaimer] The information contained in this e-mail is privileged and 
> confidential and is intended only for its addressee. Any review, 
> dissemination, distribution or copying of this e-mail is prohibited. If you 
> have received it in error please delete the original message and e-mail us.
> 
> (!) El medio ambiente es responsabilidad de todos.
> Imprime este mail si es absolutamente necesario.
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> 


signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Blink Ubuntu DNS lookup deadlock?

[Adrian Georgescu]

$dig cname guest1.voipgateway.org

;; QUESTION SECTION:
;guest1.voipgateway.org.IN  CNAME

;; ANSWER SECTION:
guest1.voipgateway.org. 21600   IN  CNAME   ws1.voipgateway.org.

The CNAME should not be there for the domain name.

—
Adrian




> On 30 Nov 2022, at 07:15, Tijmen de Mes  wrote:
> 
> Hi,
> 
> I looked at it a bit more and the fact that a CNAME is returned could happen.
> 
> However in my Blink I can’t reproduce this fault, I used the domain 
> guest1.voipgateway.org and I could register(?), if I made a call I got a 
> prompt.
> 
> This is how my logs look:
> 
>   1 2022-11-30 10:59:46.901093 [blink 4977]: DNS lookup NAPTR 
> guest1.voipgateway.org failed: DNS response contains no answer
>   2 2022-11-30 10:59:46.901540 [blink 4977]: DNS lookup SRV 
> _sips._tcp.guest1.voipgateway.org failed: DNS record does not exist
>   3 2022-11-30 10:59:46.901950 [blink 4977]: DNS lookup SRV 
> _sip._tcp.guest1.voipgateway.org failed: DNS record does not exist
>   4 2022-11-30 10:59:46.902359 [blink 4977]: DNS lookup SRV 
> _sip._udp.guest1.voipgateway.org failed: DNS record does not exist
>   5 2022-11-30 10:59:46.902618 [blink 4977]: DNS lookup A 
> guest1.voipgateway.org succeeded, ttl=2675: 212.117.203.57
> 
> I don’t have the flatpack so I can’t tell you if something is wrong in there. 
> The lookups are handled by python3-sipsimple.
> 
> Best regards,
> 
> Timen de Mes
> —
> AG Projects
> 
>> Op 30 nov. 2022, om 10:35 heeft Tijmen de Mes  het 
>> volgende geschreven:
>> 
>> Hi,
>> 
>> The fact that you see the timeouts could be a bug.
>> 
>> The problem is that a NAPTR does exist and is a CNAME? I’ve never seen this 
>> and I am not sure this is even valid in DNS.
>> 
>> AFAIK a NAPTR in this case should return something like:
>> 
>> 20 100 "s" "SIP+D2U" "" _sip._udp.sip2sip.info.
>> 10 100 "s" "SIP+D2T" "" _sip._tcp.sip2sip.info.
>> 25 100 "s" "SIPS+D2T" "" _sips._tcp.sip2sip.info.
>> 
>> After this a SRV lookup would be done.
>> 
>> Are you able to register your account?
>> 
>> 
>> Best regards,
>> 
>> Tijmen de Mes
>> —
>> AG Projects
>> 
>>> Op 29 nov. 2022, om 17:44 heeft g4-l...@tonarchiv.ch het volgende 
>>> geschreven:
>>> 
>>> Hi there
>>> 
>>> A few days ago I updated my OS to Pop! OS / Ubuntu 22.04 LTS with the Blink 
>>> flatpack V5.5.0
>>> 
>>> A few times it worked flawlessly, but most of the time, starting a call 
>>> lags a lot and it simply fails with a beep after a few minutes without any 
>>> further message.
>>> 
>>> The logs shows issues with DNS:
>>> 
>>> 2022-11-29 15:22:37.533993 [blink 2]: DNS lookup NAPTR 
>>> guest1.voipgateway.org failed: no DNS response received, the query has 
>>> timed out
>>> 2022-11-29 15:22:37.534465 [blink 2]: DNS lookup SRV 
>>> _sip._udp.guest1.voipgateway.org failed: no DNS response received, the 
>>> query has timed out
>>> 2022-11-29 15:22:37.534699 [blink 2]: DNS lookup SRV 
>>> _sip._tcp.guest1.voipgateway.org failed: no DNS response received, the 
>>> query has timed out
>>> 2022-11-29 15:22:37.534909 [blink 2]: DNS lookup SRV 
>>> _sips._tcp.guest1.voipgateway.org failed: no DNS response received, the 
>>> query has timed out
>>> 2022-11-29 15:22:37.535100 [blink 2]: DNS lookup A guest1.voipgateway.org 
>>> failed: no DNS response received, the query has timed out
>>> 2022-11-29 15:22:37.637499 [blink 2]: DNS lookup TXT 
>>> xcap.guest1.voipgateway.org failed: DNS record does not exist
>>> 2022-11-29 15:23:08.049049 [blink 2]: DNS lookup NAPTR 
>>> guest1.voipgateway.org failed: no DNS response received, the query has 
>>> timed out
>>> 2022-11-29 15:23:08.049976 [blink 2]: DNS lookup SRV 
>>> _sips._tcp.guest1.voipgateway.org failed: no DNS response received, the 
>>> query has timed out
>>> 2022-11-29 15:23:08.050817 [blink 2]: DNS lookup SRV 
>>> _sip._tcp.guest1.voipgateway.org failed: no DNS response received, the 
>>> query has timed out
>>> 2022-11-29 15:23:08.051510 [blink 2]: DNS lookup SRV 
>>> _sip._udp.guest1.voipgateway.org failed: no DNS response received, the 
>>> query has timed out
>>> 2022-11-29 15:23:08.052161 [blink 2]: DNS lookup A guest1.voipgateway.org 
>>> failed: no DNS response received, the query has timed out
>>> 2022-11-29 15:23:38.498519 [blink 2]: DNS lookup NAPTR 
>>> guest1.voipgateway.org failed: no DNS response received, the query has 
>>> timed out
>>> 2022-11-29 15:23:38.498998 [blink 2]: DNS lookup SRV 
>>> _sip._udp.guest1.voipgateway.org failed: no DNS response received, the 
>>> query has timed out
>>> 2022-11-29 15:23:38.499612 [blink 2]: DNS lookup SRV 
>>> _sip._tcp.guest1.voipgateway.org failed: no DNS response received, the 
>>> query has timed out
>>> 2022-11-29 15:23:38.500547 [blink 2]: DNS lookup SRV 
>>> _sips._tcp.guest1.voipgateway.org failed: no DNS response received, the 
>>> query has timed out
>>> 2022-11-29 15:23:38.501826 [blink 2]: DNS lookup A guest1.voipgateway.org 
>>> failed: no DNS response received, the query has timed out
>>> 2022-11-29 15:24:08.946267 

[Blink] New Blink QT release version 5.5.0 with multiple language support

[Adrian Georgescu]

Hello,

There is a new version of Blink Qt available as a debian package at 
http://icanblink.com

Changelog

  * Added multi-language support
  * Added Dutch translation
  * Added documentation folder doc/
  * Added messaging notes
  * Improved python 3.10 compatibility
  * Added more logging
  * Fixed opening last coversations multiple times

For instructions about adding more languages see:

https://github.com/AGProjects/blink-qt/blob/master/docs/language-translations.md

—
Adrian



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink QT release version 5.4.0 with OTR encryption

[Adrian Georgescu]

Hello,

There is a new version of Blink Qt available as a debian package at 
http://icanblink.com

Changelog

  * Added OTR encryption to SIP Message sessions
  * Add option to add/remove realtime chat during audio/video calls
  * PGP encryption fixes
  * Added more log mesaages

—
Adrian



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink QT release version 5.3.0 with OpenPGP and offline messaging

[Adrian Georgescu]

There is a new version of Blink Qt available as a debian package at 
http://icanblink.com

Changelog

   * Added OpenPGP encryption for SIP Messages
   * Added offline messaging based on SylkServer API
   * Added multiple device synchronization for SIP messages
   * Added message trace/logging
   * Added advanced messaging options in account preferences
   * Improved python 3.10 compatibilty
   * Fixed Google contacts to not use deprecated OOB flow
   * Several fixes for IMDN and history storage

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release for Linux version 5.2.0

[Adrian Georgescu]

Hello,

There is a new Blink Qt release for Linux. Packaging for Debian and Ubuntu will 
soon follow but if you want to build it for your own Linux distribution flavour 
you can use the current code base.

Changelog

blink (5.2.0)

  * Added SIP Message functionality
  * Added history for chat and messages
  * Solved issues with python 3.10
  * Fixed wrong classes on chat messages
  * Fixed background icon path
  * Fixed encryption widget
  * Fixed monkey patch warning
  * Added status support for (chat) messages
  * Use SIP message method as default for 'chat'
  * Added IMDN support for messages
  * Added menuitem to show last conversations
  * Added setting to add unknown message contacts to contact list
  * Fixed google contacts
  * Reorganized 'Advanced' preferences
  * Added option to show name and uri in call history menu
  * Updated copyright years
  * Cleaned up code/syntax

https://icanblink.com 

—
Adrian


___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] TLS and SRTP with Freepbx

[Adrian Georgescu]

Hi Adolfo,

Blink will automatically use TLS if you correctly setup the DNS server serving 
the domain of your SIP account, as described in RFC 3263. Alternatively, you 
can force Blink to use TLS transport by setting the advanced account SIP 
signalling primary proxy setting.

To force use sRTP for outbound calls, you can set the advanced account settings 
RTP media encryption (chose your encryption flavour from the drop down list).

For incoming calls Blink will automatically accept sRTP by default.

Adrian 

> On 13 May 2022, at 14:16, Adolfo Arizpe  wrote:
> 
> Good morning, I am trying to configure TLS and SRTP to connect to a Freepbx 
> 16 server.
> 
> What is the procedure on the Blink side?
> 
> Thanks!
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] MacOS X - audio media stream did not initialize: Unknown audio codecs: iLBC, GSM, speex (0)

[Adrian Georgescu]

The only way is recompiling the software and all dependencies yourself, a task 
of very high complexity.

https://github.com/AGProjects/blink-cocoa 


Regards,
Adrian


> On 6 Apr 2022, at 06:08, David Robinson  wrote:
> 
> I used the Beta version from the website before purchasing through the 
> AppStore. Speex was available then. Now it's been removed.
> 
> I installed the library using brew, hoping Blink would check. Nope.
> 
> Is there a plugin folder or a method to get the codec back again?
> 
> Thanks,
> David
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Blink on Mac-freezes

[Adrian Georgescu]

I would start the client from scratch to eliminate a possible configuration 
problem.

Move this folder

~/Library/Containers/com.agprojects.Blink/

To another name

And start Blink Pro again.

Add your account again and see if the problem persists.

Regards,
Adrian



> On 17 Jan 2022, at 11:35, ja...@jtk.com.pl  wrote:
> 
> Any news in the matter of below problem?
> 
> Pozdrawiam/Best Regards
> 
> JT
> 
> 
> 
>> Wiadomość napisana przez ja...@jtk.com.pl  
>> mailto:ja...@jtk.com.pl>> w dniu 05.01.2022, o godz. 
>> 11:55:
>> 
>> Blink Pro 6.0.3 build 27257 on Mac behaves not stable. After launching app, 
>> trying to input number to call effects in freezing the app. Rotating beach 
>> ball is shown and app is not responding. Before user starts to type or paste 
>>  the number, app is responsible.
>> 
>> Pozdrawiam/Best Regards
>> 
>> JT
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com 
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> 
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] line marked as busy for incoming audio calls

[Adrian Georgescu]

Hm, this is a mumbo-jumbo explanation of Sipgate that is hard to decipher…

Perhaps some logs may help, you can send the logs you find from Window -> Logs 
-> SIP and Window -> Logs -> Activity by email to supp...@ag-projects.com 
<mailto:supp...@ag-projects.com>
 
Regards,
Adrian

> On 17 Jan 2022, at 11:19, Andre Boden  wrote:
> 
> Hi Adrian,
> 
> thank you for your fast answer.
> We use the services of sipgate for our telecommunication. After several calls 
> did not reach me, I asked their customer service. They were able to isolate 
> the problem to the fact that my SIP client marked the line as being busy.
> 
> Best,
> André
> 
> 
> 
> 
>> Am 17.01.2022 um 14:31 schrieb Adrian Georgescu > <mailto:a...@ag-projects.com>>:
>> 
>> Can you clarify how Blink marks the line as being busy?
>> 
>> Adrian
>> 
>>> On 17 Jan 2022, at 10:13, Andre Boden >> <mailto:andre.bo...@algona.de>> wrote:
>>> 
>>> Hello,
>>> 
>>> when I am on my home network, Blink seems to mark the line as busy (even 
>>> though it is not) for incoming external audio calls. Do you know if this 
>>> could be due to a setting in Blink Pro or could be a network setting?
>>> 
>>> Thanks in advance for your answer!
>>> 
>>> 
>>> Best,
>>> 
>>> André Boden
>>> Applications & Training
>>> 
>>> Office Stuttgart
>>> +49 711 217 282 76
>>> 
>>>   <http://www.algona-ic.de/>
>>> Stuttgart HQ | Hedelfinger Strasse 55 | 70327 Stuttgart
>>> Leipzig Sales-Office | Torgauer Straße 231-233 | 04347 Leipzig
>>> Düsseldorf Sales-Office | Prinzenallee 7 | 40549 Düsseldorf
>>> Zürich Repräsentanz Schweiz | Badener Str. 549 | CH-8048 Zürich
>>>   <http://www.algona-ic.de/>  
>>> <https://www.youtube.com/channel/UC8GA7gYpHPPoWBBSITmfUBw>  
>>> <https://www.linkedin.com/company/algona-gmbh>
>>>   <https://maillink.algona.de/index.html>
>>> Handelsregister Stuttgart - HRB 739618 | USt.ID-Nr. DE 281471749
>>> Geschäftsführer: Stefan Prange
>>> 
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>>> https://lists.ag-projects.com/mailman/listinfo/blink 
>>> <https://lists.ag-projects.com/mailman/listinfo/blink>
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>> https://lists.ag-projects.com/mailman/listinfo/blink
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] line marked as busy for incoming audio calls

[Adrian Georgescu]

Can you clarify how Blink marks the line as being busy?

Adrian

> On 17 Jan 2022, at 10:13, Andre Boden  wrote:
> 
> Hello,
> 
> when I am on my home network, Blink seems to mark the line as busy (even 
> though it is not) for incoming external audio calls. Do you know if this 
> could be due to a setting in Blink Pro or could be a network setting?
> 
> Thanks in advance for your answer!
> 
> 
> Best,
> 
> André Boden
> Applications & Training
> 
> Office Stuttgart
> +49 711 217 282 76
> 
>   
> Stuttgart HQ | Hedelfinger Strasse 55 | 70327 Stuttgart
> Leipzig Sales-Office | Torgauer Straße 231-233 | 04347 Leipzig
> Düsseldorf Sales-Office | Prinzenallee 7 | 40549 Düsseldorf
> Zürich Repräsentanz Schweiz | Badener Str. 549 | CH-8048 Zürich
>     
>   
> 
>   
> Handelsregister Stuttgart - HRB 739618 | USt.ID-Nr. DE 281471749
> Geschäftsführer: Stefan Prange
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Python 3.10 compatibility

[Adrian Georgescu]

This is not really blink related because is a problem with a dependency.

Try follow the advice from here:

https://stackoverflow.com/questions/70013988/importerror-cannot-import-name-mutablemapping-from-collections-usr-local

If it works we can make a patch for the dependency package and send it to the 
right place.

Regards,
Adrian



> On 5 Dec 2021, at 13:03, CE  wrote:
> 
> 
> Build of python3-otr on fedora 35 fails. Error is "Import Error: cannot 
> import name 'MutableMapping' from 'collections'.  Error log of build is 
> attached. 
> <3442edd6.txt>___
> Blink mailing list
> Blink@lists.ag-projects.com 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> 
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] BLINK PRO Error (Audio Media Stream Did Not Initiate)

[Adrian Georgescu]

See

https://lists.ag-projects.com/pipermail/blink/2021-December/004256.html 



> On 5 Dec 2021, at 16:34, Eric Jay Alcaraz  wrote:
> 
> Hi,
> 
> Been having the same issue since yesterday. Can anybody assist in resolving 
> this? I'm using a MacBook Air 2020. See screenshot below for reference.
> 
> Thanks!
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] New Blink Pro for Mac 6.0.0

[Adrian Georgescu]

After reseting the codec list you can customise them again and selected only 
G722.


> On 3 Dec 2021, at 08:07, Florian Dargel  wrote:
> 
> Hm, if i do that including G722 my provider (Sipgate) doesnt work with that 
> at all. It does work with just G722 so will try with that. 
> 
> Clicking and unclicking Customize alone doesnt help.
> 
> 
> --
> Florian Dargel
> florian.dar...@gmail.com <mailto:florian.dar...@gmail.com>
> 
> 
> 
> On Fri, 3 Dec 2021 at 10:45, Adrian Georgescu  <mailto:a...@ag-projects.com>> wrote:
> This will reset the codecs to the correct support values.
> 
> Go to
> 
> Settings -> Account -> Advanced settings -> RTP Media and click/un-click 
> Customise checkbox.
> 
> Go to
> 
> Settings -> Advanced -> RTP Media  
> 
> And uncheck any of the following audio codecs: Speex, Gsm, iLBC
> 
> Regards,
> Adrian
> 
>> On 3 Dec 2021, at 07:14, Florian Dargel > <mailto:florian.dar...@gmail.com>> wrote:
>> 
>> Hi Adrian,
>> 
>> after update to 6.0.3. build 27257
>> 
>> I encountered the following error:
>> 
>> "Audio Media Stream Did Not Initialize: Unknown Audio Codecs: Speex, Gsm"
>> 
>> While I would love to use G722 I have found that in the past my broadband 
>> doesnt support that too well and leads to worse quality.
>> 
>> Thanks Florian
>> 
>> --
>> Florian Dargel
>> florian.dar...@gmail.com <mailto:florian.dar...@gmail.com>
>> 
>> 
>> 
>> On Mon, 15 Nov 2021 at 18:39, Adrian Georgescu > <mailto:a...@ag-projects.com>> wrote:
>> There is a new Blink Pro release for Mac available in App Store.
>> 
>> Change-log
>> 
>>  * Added Group menu item to delete all contacts from a group
>>  * Added contact synchronization compatible with Sylk API
>>  * Added message history using SylkServer conversations API
>>  * Added Export PGP private key window and logic
>>  * Decrypt old messages in history viewer
>>  * Set missing account settings for known domains
>>  * Fixed DNS lookups for Bonjour sessions
>>  * Screen sharing fixes
>> 
>> 
>> —
>> Adrian
>> 
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> <https://lists.ag-projects.com/mailman/listinfo/blink>
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> <https://lists.ag-projects.com/mailman/listinfo/blink>
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
> https://lists.ag-projects.com/mailman/listinfo/blink 
> <https://lists.ag-projects.com/mailman/listinfo/blink>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] New Blink Pro for Mac 6.0.0

[Adrian Georgescu]

This will reset the codecs to the correct support values.

Go to

Settings -> Account -> Advanced settings -> RTP Media and click/un-click 
Customise checkbox.

Go to

Settings -> Advanced -> RTP Media  

And uncheck any of the following audio codecs: Speex, Gsm, iLBC

Regards,
Adrian

> On 3 Dec 2021, at 07:14, Florian Dargel  wrote:
> 
> Hi Adrian,
> 
> after update to 6.0.3. build 27257
> 
> I encountered the following error:
> 
> "Audio Media Stream Did Not Initialize: Unknown Audio Codecs: Speex, Gsm"
> 
> While I would love to use G722 I have found that in the past my broadband 
> doesnt support that too well and leads to worse quality.
> 
> Thanks Florian
> 
> --
> Florian Dargel
> florian.dar...@gmail.com <mailto:florian.dar...@gmail.com>
> 
> 
> 
> On Mon, 15 Nov 2021 at 18:39, Adrian Georgescu  <mailto:a...@ag-projects.com>> wrote:
> There is a new Blink Pro release for Mac available in App Store.
> 
> Change-log
> 
>  * Added Group menu item to delete all contacts from a group
>  * Added contact synchronization compatible with Sylk API
>  * Added message history using SylkServer conversations API
>  * Added Export PGP private key window and logic
>  * Decrypt old messages in history viewer
>  * Set missing account settings for known domains
>  * Fixed DNS lookups for Bonjour sessions
>  * Screen sharing fixes
> 
> 
> —
> Adrian
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
> https://lists.ag-projects.com/mailman/listinfo/blink 
> <https://lists.ag-projects.com/mailman/listinfo/blink>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Pro for Mac 6.0.0

[Adrian Georgescu]

There is a new Blink Pro release for Mac available in App Store.

Change-log

 * Added Group menu item to delete all contacts from a group
 * Added contact synchronization compatible with Sylk API
 * Added message history using SylkServer conversations API
 * Added Export PGP private key window and logic
 * Decrypt old messages in history viewer
 * Set missing account settings for known domains
 * Fixed DNS lookups for Bonjour sessions
 * Screen sharing fixes


—
Adrian


___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release for Linux version 5.1.8

[Adrian Georgescu]

There is a new Blink Qt release for Linux.

Changelog

blink (5.1.8)

 * Replaced Let's Encrypt Root CA

—
Adrian


___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] [solved] Re: Expired certificate for Ubuntu Focal Repository?

[Adrian Georgescu]

We need Sven…


> On 5 Nov 2021, at 11:52, g4-l...@tonarchiv.ch wrote:
> 
> It should be approved by Sven, I don't have a sipthor account...
> 
> On 05.11.21 15:35, Adrian Georgescu wrote:
>> Please try again this one:
>> 
>> http://download.ag-projects.com/Blink/Linux/ca.crt 
>> <http://download.ag-projects.com/Blink/Linux/ca.crt>
>> 
>> 
>>> On 5 Nov 2021, at 11:30, g4-l...@tonarchiv.ch <mailto:g4-l...@tonarchiv.ch> 
>>> wrote:
>>> 
>>> # Lets' Encrypt
>>> # Issuer: C = US, O = Internet Security Research Group, CN = ISRG Root X1
>>> # Subject: C = US, O = Let's Encrypt, CN = R3
>> 
>> 
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> <https://lists.ag-projects.com/mailman/listinfo/blink>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] [solved] Re: Expired certificate for Ubuntu Focal Repository?

[Adrian Georgescu]

Please try again this one:

http://download.ag-projects.com/Blink/Linux/ca.crt 



> On 5 Nov 2021, at 11:30, g4-l...@tonarchiv.ch wrote:
> 
> # Lets' Encrypt
> # Issuer: C = US, O = Internet Security Research Group, CN = ISRG Root X1
> # Subject: C = US, O = Let's Encrypt, CN = R3

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] [solved] Re: Expired certificate for Ubuntu Focal Repository?

[Adrian Georgescu]

This one?

Intermediate Certificates

Active
Let’s Encrypt R3 (RSA 2048, O = Let's Encrypt, CN = R3)
Signed by ISRG Root X1 : der 
, pem 
, txt 




> On 5 Nov 2021, at 04:47, g4-l...@tonarchiv.ch wrote:
> 
> ISRG Root X1

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] [solved] Re: Expired certificate for Ubuntu Focal Repository?

[Adrian Georgescu]

I can bundle the new cert and make a new blink package.

Just double checking, where is the authoritative source for the replaced CA 
file?

> On 4 Nov 2021, at 16:07, g4-l...@tonarchiv.ch wrote:
> 
> On 04.11.21 20:04, Lars Noodén wrote:
>> On 11/4/21 20:51, g4-l...@tonarchiv.ch wrote:
>>> 
>>> 
>>> Maybe you can just add the content of
>>> /usr/local/share/ca-certificates/lets-encrypt-r3.crt to the end of this
>>> file...
>>> 
>>> Not sure if you also need some header before the -BEGIN
>>> CERTIFICATE- line...
>>> 
>>> This would be something like:
>>> 
>>> # Lets' Encrypt
>>> # Issuer: C = US, O = Internet Security Research Group, CN = ISRG
>>> Root X1
>>> # Subject: C = US, O = Let's Encrypt, CN = R3
>>> 
>>> The X3 cert of Let's Encrypt in my /usr/share/blink/tls/ca.crt is
>>> definitely outdated.
>>> 
>>> You should probably delete the last smaller block of the two,
>>> starting with
>>> 
>>> -BEGIN CERTIFICATE-
>>> MIIEZTCCA02gAwIBAgIQQAF1BIMUpMghjISpDBbN3zANBgkqhkiG9w0BAQsFADA/
>>> 
>>> But make a backup of /usr/share/blink/tls/ca.crt first!
>> 
>> Thanks!  I made a back up of ca.crt, removed the last certificate, and
>> then appended lets-encrypt-r3.crt to the file.  That has gotten rid of
>> the error.   I can now dial out.
>> 
>> I had previously tried reinstalling Blink so maybe the new certificate
>> needs to be packaged?
>> 
> Glad to hear that it solved the problem!
> 
> Yes, this CRT file is outdated, at least in the latest deb package for
> Focal...
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Expired certificate for Ubuntu Focal Repository?

[Adrian Georgescu]

Try this command in a Terminal:

openssl s_client -connect proxy.sipthor.net:5061 
<http://proxy.sipthor.net:5061/>


> On 28 Oct 2021, at 13:29, Lars Noodén  wrote:
> 
> On 10/28/21 19:18, Adrian Georgescu wrote:
>> If you enable pjsip trace you can find more info about the TLS negotiation...
> 
> Thanks.  Would that be Blink -> Preferences -> Logging -> Trace
> Notifications?  That has a lot of entries about "SSL certificate
> verification error (PJSIP_TLS_ECERTVERIF)"
> 
> I'll send the short log separately, offlist.
> 
> /Lars
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Expired certificate for Ubuntu Focal Repository?

[Adrian Georgescu]

It means that sip2sip.info <http://sip2sip.info/> TLS server certificate is not 
recognised by your system perhaps the CA list is not up to date…



> On 28 Oct 2021, at 13:29, Lars Noodén  wrote:
> 
> On 10/28/21 19:18, Adrian Georgescu wrote:
>> If you enable pjsip trace you can find more info about the TLS negotiation...
> 
> Thanks.  Would that be Blink -> Preferences -> Logging -> Trace
> Notifications?  That has a lot of entries about "SSL certificate
> verification error (PJSIP_TLS_ECERTVERIF)"
> 
> I'll send the short log separately, offlist.
> 
> /Lars
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Expired certificate for Ubuntu Focal Repository?

[Adrian Georgescu]

If you enable pjsip trace you can find more info about the TLS negotiation...

> On 28 Oct 2021, at 13:07, Lars Noodén  wrote:
> 
> On 10/6/21 02:12, Adrian Georgescu wrote:> Sorry for these problems
> still persist, we have a forst of servers
> > and we still could not replace all certs, I am discovering strange
> > combinations of certs /OS incompatibilities still myself.
> >
> > Thank you for reporting Lars, and thank you for clarifications Jeff!
> >
> > Adrian
> 
> Hi,
> 
> I've checked the client I have here and it seems like that might be ok.
> So the expired certificate must be elsewhere and hard to find?
> 
> $ openssl verify -CAfile /usr/share/blink/tls/ca.crt \
>   /usr/share/blink/tls/default.crt
> /usr/share/blink/tls/default.crt: OK
> 
> That's with Blink 5.1.7focal
> 
> /Lars
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] Fwd: Let's Encrypt DST Root CA X3 Expiration

[Adrian Georgescu]

The complexity of the problem…

> Begin forwarded message:
> 
> From: raf 
> Subject: Re: Let's Encrypt DST Root CA X3 Expiration
> Date: 2 October 2021 at 23:32:45 GMT-3
> To: macports-us...@lists.macports.org
> 
> On Sat, Oct 02, 2021 at 04:14:05AM -0500, Ryan Schmidt 
>  wrote:
> 
>> macports.org and other secure web sites that use Let's Encrypt may
>> no longer be accessible to you if you use older versions of macOS
>> or older browsers or user agents. For example, the libcurl in macOS
>> 10.14 can't talk to many Let's Encrypt web sites now, including
>> distfiles.macports.org and packages.macports.org, and MacPorts uses
>> macOS libcurl to download things. Safari and many browsers don't use
>> libcurl so they may be affected differently.
>> 
>> Let's Encrypt is a free certificate provider used by macports.org
>> and many other web sites to provide https encryption. Certificates
>> they issue depend on their "ISRG Root X1" certificate which was
>> cross-signed by the "DST Root CA X3" certificate, because DST Root
>> CA X3 was more widely accepted by browsers when Let's Encrypt got
>> started years ago. Both of these root certificates are included in the
>> certificate chain served by web sites that use Let's Encrypt.
>> 
>> ISRG Root X1 itself has been trusted by browsers for some time
>> now and DST Root CA X3 expired a couple days ago on September 30,
>> 2021. Apparently in order to provide the widest compatibility,
>> certificate chains continue to list the old expired root certificate
>> after the new one. The idea as I understand it is that browsers should
>> see the ISRG Root X1 certificate, realize that it itself is already
>> trusted by the OS or browser, and not even look at the next expired
>> DST Root CA X3 certificate in the chain.
>> 
>> They advertised this root certificate expiration as being a very minor
>> situation, but unfortunately it seems that a large portion of Apple
>> devices cannot deal with this change. On many Macs, it seems that the
>> entire certificate chain is being validated, and the expired extra
>> root certificate is causing the connection to be disallowed. What
>> alerted me to the problem in the first place was seeing many failed
>> builds on our Buildbot system due to fetch failures.
>> 
>> I'm not certain what to do to address this. On the web servers
>> we control, we can apparently remove the expired DST Root CA X3
>> certificate from the chain that we send. That will help those
>> systems that already trust ISRG Root X1. I'm not sure how far back
>> that is. For older systems, we can modify master_sites.tcl and
>> archive_sites.tcl to change which OS versions try to access our mirror
>> servers via https. None of this necessarily helps our build server be
>> able to mirror distfiles in the first place. If you have ideas, let me
>> know.
>> 
>> https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
> 
> There is a discussion on the LetsEncrypt community site
> with instructions for installing the ISRG Root X1
> certificate on older versions of macOS:
> 
>  
> https://community.letsencrypt.org/t/connection-errors-on-apple-devices/161107/16
> 
> Here are instructions for 10.10 and 10.11:
> 
>  
> https://community.letsencrypt.org/t/connection-errors-on-apple-devices/161107/25
> 
> Here's another approach that worked on 10.9.5 and
> 10.11.6 (i.e., override the expiry by always trusting
> DST Root CA X3:
> 
>  
> https://community.letsencrypt.org/t/connection-errors-on-apple-devices/161107/28
> 
> Here's my approach for 10.6.8 because the above didn't
> work (i.e., export root certificates from a later macOS
> and import them):
> 
>  
> https://community.letsencrypt.org/t/connection-errors-on-apple-devices/161107/36
> 
> But these are all client-side fixes. The only
> server-side fix seems to be to change to a different
> certificate authority. I didn't see any mention of
> removing the DST Root CA X3 certificate from the chain.
> That would probably only work from macOS 10.12 onwards.
> ISRG Root X1 is only trusted by macOS since 10.12.
> Earlier than that, it needs to be added.
> 
> The rest is a bit rambly. It might be best to just
> consult the LetsEncrypt community forum above.
> 
> I should mention that I didn't notice any problems with
> macports on 10.6.8. curl has its own root certificates
> and they are fine. And I was able to do an upgrade. But
> I might have already installed the ISRG Root X1
> certificate at least into my "local" keychain before
> trying it (or maybe into the "System" and "System
> Roots" keychains).
> 
> However, I still don't think that it's entirely OK.
> Firefox on 10.6.8 can access macports.org with no
> problem (but it certainly wasn't accessing my
> LetsEncrypt-certified sites beforehand), but Sarafi
> tells me that it can't verify macports.org's identity,
> but it still lets me access it. If I quit and restart
> Safari, and visit macports.org, it does the same thing.
> Firefox uses its own root certificates. 

Re: [Blink] Expired certificate for Ubuntu Focal Repository?

[Adrian Georgescu]

Sorry for these problems still persist, we have a forst of servers and we still 
could not replace all certs, I am discovering strange combinations of certs /OS 
incompatibilities still myself.

Thank you for reporting Lars, and thank you for clarifications Jeff!

Adrian


> On 5 Oct 2021, at 18:19, Jeff Pyle  wrote:
> 
> Lars,
> 
> AG Projects' site uses Let's Encrypt for its certificate, and Let's Encrypt 
> expired an old intermediate one last Thursday.  I suspect what you're seeing 
> is a result.
> 
> The certificates on the AG server are up to date.  It's possible you may need 
> to remove the expired certificate from your own SSL repository, and add the 
> ISRG Root X1 cert from https://letsencrypt.org/certificates/ 
>  if you don't have it already.
> 
> More information is available if you google something like "let's encrypt r3 
> intermediate expiration".
> 
> 
> Regards,
> Jeff
> 
> 
> On Sat, Oct 2, 2021 at 10:37 AM Lars Noodén  > wrote:
> Hello,
> 
> I am noticing some difficulty in updating Blink on Linux Mint.  Linux
> Mint follows the Ubuntu Focal repository, but there seems to be an
> expired certificate:
> 
> $ sudo apt update
> ...
> Err:8 https://ag-projects.com/ubuntu  focal 
> Release
> 
>   Certificate verification failed: The certificate is NOT trusted. The
> certificate chain uses expired certificate.  Could not handshake: Error
> in the certificate verification. [IP: 81.23.228.137 443]
> ...
> 
> $ lsb_release -rd
> Description:Linux Mint 20.1
> Release:20.1
> 
> Who should be notified or is there anything I should do on my end?
> 
> Thanks.
> 
> /Lars
> ___
> Blink mailing list
> Blink@lists.ag-projects.com 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Weird DNS problem

[Adrian Georgescu]

This DNS server entry is produced by your operating system, either is set in 
your network configuration or is learned from DHCP.

Adrian

> On 14 Sep 2021, at 07:29, Noname Nonameovych  wrote:
> 
> I have a weird problem with the Blink`s DNS resolver.
> 
> My network sends me 4 dns servers to use via dhcp. They are working perfectly 
> - there is`nt any other problems other than with Blink.
> 
> I`ve enabled logs and at logs I see that Blink`s DNS resolver initializes 
> with list of 5 dns servers (I preferred to edit out my actual dns servers` 
> addresses):
> 
> 2021-09-14 13:14:26.100803 [blink.exe 592]: Notification 
> name=DNSResolverDidInitialize sender= 0x0a91c350> data=NotificationData(nameservers=['192.168.0.1', 'my_DNS_1', 
> 'my_DNS_2', 'my_DNS_3', 'my_DNS_4'])
> 
> There is no host with ip 192.168.0.1 in my network, no such default addresses 
> are used here.
> 
> Thus it fails to lookup a SIP server ip address:
> 
> 2021-09-14 13:19:00.773883 [blink.exe 592]: Notification name=DNSLookupTrace 
> sender= 
> data=NotificationData(answer=None, query_name='vpbx400124675.mangosip.ru 
> ', context='lookup_sip_proxy', 
> error=Timeout('The DNS operation timed out after 2.95100402832 seconds',), 
> nameservers=['192.168.0.1', 'my_DNS_1', 'my_DNS_2', 'my_DNS_3', 'my_DNS_4'], 
> query_type='A', uri=SIPURI('vpbx400124675.mangosip.ru 
> ', None, None, None, False, {}, {}))
> 
> (and this message repeats thrice at the each register retry)
> 
> Looks like it tries to query the first dns server from the list, fails, and 
> for some reason stucks at the first entry of the dns servers list, not going 
> round-robin onto the other dns servers.
> 
> Where and why is it taking 192.168.0.1 out of nowhere as the first entry of 
> the dns servers list, and how can it be fixed?
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] python-enum34

[Adrian Georgescu]

I pushed the changes.

Thank you!

Regards,
Adrian



> On 3 Sep 2021, at 15:20, Daniel Gnoutcheff  
> wrote:
> 
> On 9/1/21 7:43 AM, Adrian Georgescu wrote:
>> This package is critical, and is also a dependency of python-cryptography 
>> and python-otr packages.
> 
> According to python-enum34's Debian package description, the module it 
> provides is part of the standard library in Python 3.4 and later. Hence, 
> python-cryptography and python-otr require python-enum34, while 
> python3-cryptography and python3-otr do not, presumably requiring python 
> >=3.4 instead.
> 
> Once I removed 'python-enum34' from Blink's debian/control, I successfully 
> built it, installed it, launched it, and placed a test call on a fresh Debian 
> bullseye system where python-enum34 was not installed.  stdout/stderr showed 
> no signs of discomfort.  Seeing as there was no python3 version of 
> python-enum34 on stretch or buster either, this leads me to assume that the 
> Python3 version of Blink is already successfully using the >=3.4 standard 
> library 'enum' module in place of the version formerly provided by 
> python-enum34.
> 
> Hence, I believe the change to debian/control is all that's needed to get 
> Blink to install and run on bullseye.
> 
> HTH,
> -- 
> Daniel Gnoutcheff
> Systems Administrator
> Software Freedom Law Center
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] python-enum34

[Adrian Georgescu]

This package is critical, and is also a dependency of python-cryptography and 
python-otr packages.

Regards,
Adrian

> On 30 Aug 2021, at 18:41, Daniel Gnoutcheff  
> wrote:
> 
> The `blink` Debian packages have a Depends: dependency on python-enum34.  
> That package has been removed from Debian testing and unstable, and it is not 
> included in the recent (Aug 14 2021) "bullseye" stable release.
> 
> With the port to Python3, this package is no longer used by Blink.  It 
> builds, installs, and runs fine once I drop it from debian/control.
> 
> Thanks,
> -- 
> Daniel Gnoutcheff
> Systems Administrator
> Software Freedom Law Center
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release for Linux version 5.1.5

[Adrian Georgescu]

There is a new Blink Qt release for Linux.

Changelog

blink (5.1.5)

 * Screen sharing fixes

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release for Linux version 5.1.4

[Adrian Georgescu]

There is a new Blink Qt release for Linux.

Changelog

blink (5.1.4)

  * Added presence and message_summary account settings

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] SIP PUBLISH failes with 400 Invalid auth header

[Adrian Georgescu]

Like this:

Accounts:
bonjour@local:
display_name = Adrian
enabled = true
rtp:
video_codec_list = VP9, H264, VP8
video_codec_order = VP9, H264, VP8
encryption:
enabled = true


sip:
auto_answer = true


tesxxe...@sip2sip.info:
display_name = "Test me 999"
enabled = true
auth:
password = 67676767

nat_traversal:
stun_server_list =
use_ice = false

presence:
enabled = false

server:
settings_url = "https://blink.sipthor.net/settings.phtml;

sip:
auto_answer = true
tls_name = sip2sip.info <http://sip2sip.info/>


> On 17 Aug 2021, at 14:42, Adrian Georgescu  wrote:
> 
> That section must be added to your account settings, in the same section, 
> inside Accounts.
> 
> You edited the wrong section, BlinkSettings.
> 
> Adrian
> 
> 
>> On 17 Aug 2021, at 09:25, g4-l...@tonarchiv.ch wrote:
>> 
>> Sadly this didn't work.
>> 
>> On Ubuntu I found the .blink/config file with this part:
>> 
>> BlinkSettings:
>>current_state = Invisible
>>enabled = false
>>state_history =
>>presence:
>>current_state = Available
>>state_history =
>> 
>> I changed this to
>> 
>>presence:
>>enabled = false
>>current_state = Available
>>state_history =
>> 
>> (while Blink was off).
>> 
>> I also tried with 'False'
>> 
>> But Blink continues to send PUBLISH messages...
>> 
>> Regards,
>> Till
>> 
>> On 17.08.21 13:59, g4-l...@tonarchiv.ch wrote:
>>> Perfect! Thanks for your reply. I will check this.
>>> 
>>> Regards,
>>> Till
>>> 
>>> On 17.08.21 13:41, Adrian Georgescu wrote:
>>>> To disable sending PUBLISH you can edit the configuration file ~/.blink 
>>>> and add this section:
>>>> 
>>>>  +-- enabled = False
>>>> presence --|
>>>>  +
>>>> 
>>>> Indentation is critical make a backup of the file in case something goes 
>>>> wrong during or with the editing.
>>>> 
>>>> Alternatively you can install sipclients3 package from the same repository 
>>>> as blink, it contains a utility called sip-settings that can edit 
>>>> correctly blink configuration file:
>>>> 
>>>> sip-settings3 -c ~/blink -a set presence.enabled=False
>>>> 
>>>> Regards,
>>>> Adrian
>>>> 
>>>>> On 16 Aug 2021, at 10:46, g4-l...@tonarchiv.ch wrote:
>>>>> 
>>>>> Anyone there?
>>>>> 
>>>>> This seems to be a bug: I set SIP Publish Interval to 3600 seconds. But
>>>>> in the log I see that Blink sends the PUBLISH message at least once a
>>>>> minute...
>>>>> 
>>>>> Cheers
>>>>> T. Wimmer
>>>>> 
>>>>> On 12.08.21 21:39, g4-l...@tonarchiv.ch wrote:
>>>>>> Hi there,
>>>>>> 
>>>>>> My SIP provider asked me to disable SIP PUBLISH on my Blink client.
>>>>>> Their system answers with "400 Invalid auth header", and as far as I
>>>>>> understand, their server will eventually drop the connection for DoS
>>>>>> reasons. (DoS with one request every 10 minutes??)
>>>>>> 
>>>>>> Now I wonder if auth headers can be enabled also for PUBLISH? And if
>>>>>> not, how can PUBLISH be disabled?
>>>>>> 
>>>>>> I'm using the Ubunut client V 5.1.3
>>>>>> 
>>>>>> Best regards
>>>>>> Till Wimmer
>>>>>> 
>>>>> ___
>>>>> Blink mailing list
>>>>> Blink@lists.ag-projects.com
>>>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>>> 
>>>> ___
>>>> Blink mailing list
>>>> Blink@lists.ag-projects.com
>>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/blink
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] SIP PUBLISH failes with 400 Invalid auth header

[Adrian Georgescu]

That section must be added to your account settings, in the same section, 
inside Accounts.

You edited the wrong section, BlinkSettings.

Adrian


> On 17 Aug 2021, at 09:25, g4-l...@tonarchiv.ch wrote:
> 
> Sadly this didn't work.
> 
> On Ubuntu I found the .blink/config file with this part:
> 
> BlinkSettings:
> current_state = Invisible
> enabled = false
> state_history =
> presence:
> current_state = Available
> state_history =
> 
> I changed this to
> 
> presence:
> enabled = false
> current_state = Available
> state_history =
> 
> (while Blink was off).
> 
> I also tried with 'False'
> 
> But Blink continues to send PUBLISH messages...
> 
> Regards,
> Till
> 
> On 17.08.21 13:59, g4-l...@tonarchiv.ch wrote:
>> Perfect! Thanks for your reply. I will check this.
>> 
>> Regards,
>> Till
>> 
>> On 17.08.21 13:41, Adrian Georgescu wrote:
>>> To disable sending PUBLISH you can edit the configuration file ~/.blink and 
>>> add this section:
>>> 
>>>   +-- enabled = False
>>> presence --|
>>>   +
>>> 
>>> Indentation is critical make a backup of the file in case something goes 
>>> wrong during or with the editing.
>>> 
>>> Alternatively you can install sipclients3 package from the same repository 
>>> as blink, it contains a utility called sip-settings that can edit correctly 
>>> blink configuration file:
>>> 
>>> sip-settings3 -c ~/blink -a set presence.enabled=False
>>> 
>>> Regards,
>>> Adrian
>>> 
>>>> On 16 Aug 2021, at 10:46, g4-l...@tonarchiv.ch wrote:
>>>> 
>>>> Anyone there?
>>>> 
>>>> This seems to be a bug: I set SIP Publish Interval to 3600 seconds. But
>>>> in the log I see that Blink sends the PUBLISH message at least once a
>>>> minute...
>>>> 
>>>> Cheers
>>>> T. Wimmer
>>>> 
>>>> On 12.08.21 21:39, g4-l...@tonarchiv.ch wrote:
>>>>> Hi there,
>>>>> 
>>>>> My SIP provider asked me to disable SIP PUBLISH on my Blink client.
>>>>> Their system answers with "400 Invalid auth header", and as far as I
>>>>> understand, their server will eventually drop the connection for DoS
>>>>> reasons. (DoS with one request every 10 minutes??)
>>>>> 
>>>>> Now I wonder if auth headers can be enabled also for PUBLISH? And if
>>>>> not, how can PUBLISH be disabled?
>>>>> 
>>>>> I'm using the Ubunut client V 5.1.3
>>>>> 
>>>>> Best regards
>>>>> Till Wimmer
>>>>> 
>>>> ___
>>>> Blink mailing list
>>>> Blink@lists.ag-projects.com
>>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>> 
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/blink
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] SIP PUBLISH failes with 400 Invalid auth header

[Adrian Georgescu]

The server is miss-behaving.

Adrian



> On 17 Aug 2021, at 09:09, Adrian Georgescu  wrote:
> 
> The server must send 401 in order to challenge the client, then the client 
> replies with another Publish with Auth headers.
> 
> Adrian
> 
> 
>> On 17 Aug 2021, at 09:01, g4-l...@tonarchiv.ch wrote:
>> 
>> Ah I understand. Thanks for the explanation.
>> 
>> Why don't the PUBLISH messages have an auth header? Is this not in the
>> RFC? The missing auth header is the reason why the server rejects the
>> PUBLISH messages...
>> 
>> Cheers
>> Till
>> 
>> On 17.08.21 13:57, Adrian Georgescu wrote:
>>> The Publish interval is used to refresh a Publish that was successful. If 
>>> the Publish fails, like in your case, the client will retransmit it based 
>>> on other internal timers depending on the reason of the failure.
>>> 
>>> Adrian
>>> 
>>>> On 16 Aug 2021, at 10:46, g4-l...@tonarchiv.ch wrote:
>>>> 
>>>> Anyone there?
>>>> 
>>>> This seems to be a bug: I set SIP Publish Interval to 3600 seconds. But
>>>> in the log I see that Blink sends the PUBLISH message at least once a
>>>> minute...
>>>> 
>>>> Cheers
>>>> T. Wimmer
>>>> 
>>>> On 12.08.21 21:39, g4-l...@tonarchiv.ch wrote:
>>>>> Hi there,
>>>>> 
>>>>> My SIP provider asked me to disable SIP PUBLISH on my Blink client.
>>>>> Their system answers with "400 Invalid auth header", and as far as I
>>>>> understand, their server will eventually drop the connection for DoS
>>>>> reasons. (DoS with one request every 10 minutes??)
>>>>> 
>>>>> Now I wonder if auth headers can be enabled also for PUBLISH? And if
>>>>> not, how can PUBLISH be disabled?
>>>>> 
>>>>> I'm using the Ubunut client V 5.1.3
>>>>> 
>>>>> Best regards
>>>>> Till Wimmer
>>>>> 
>>>> ___
>>>> Blink mailing list
>>>> Blink@lists.ag-projects.com
>>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>>> 
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/blink
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
>> 
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] SIP PUBLISH failes with 400 Invalid auth header

[Adrian Georgescu]

The server must send 401 in order to challenge the client, then the client 
replies with another Publish with Auth headers.

Adrian


> On 17 Aug 2021, at 09:01, g4-l...@tonarchiv.ch wrote:
> 
> Ah I understand. Thanks for the explanation.
> 
> Why don't the PUBLISH messages have an auth header? Is this not in the
> RFC? The missing auth header is the reason why the server rejects the
> PUBLISH messages...
> 
> Cheers
> Till
> 
> On 17.08.21 13:57, Adrian Georgescu wrote:
>> The Publish interval is used to refresh a Publish that was successful. If 
>> the Publish fails, like in your case, the client will retransmit it based on 
>> other internal timers depending on the reason of the failure.
>> 
>> Adrian
>> 
>>> On 16 Aug 2021, at 10:46, g4-l...@tonarchiv.ch wrote:
>>> 
>>> Anyone there?
>>> 
>>> This seems to be a bug: I set SIP Publish Interval to 3600 seconds. But
>>> in the log I see that Blink sends the PUBLISH message at least once a
>>> minute...
>>> 
>>> Cheers
>>> T. Wimmer
>>> 
>>> On 12.08.21 21:39, g4-l...@tonarchiv.ch wrote:
>>>> Hi there,
>>>> 
>>>> My SIP provider asked me to disable SIP PUBLISH on my Blink client.
>>>> Their system answers with "400 Invalid auth header", and as far as I
>>>> understand, their server will eventually drop the connection for DoS
>>>> reasons. (DoS with one request every 10 minutes??)
>>>> 
>>>> Now I wonder if auth headers can be enabled also for PUBLISH? And if
>>>> not, how can PUBLISH be disabled?
>>>> 
>>>> I'm using the Ubunut client V 5.1.3
>>>> 
>>>> Best regards
>>>> Till Wimmer
>>>> 
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com
>>> https://lists.ag-projects.com/mailman/listinfo/blink
>>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] SIP PUBLISH failes with 400 Invalid auth header

[Adrian Georgescu]

The Publish interval is used to refresh a Publish that was successful. If the 
Publish fails, like in your case, the client will retransmit it based on other 
internal timers depending on the reason of the failure.

Adrian

> On 16 Aug 2021, at 10:46, g4-l...@tonarchiv.ch wrote:
> 
> Anyone there?
> 
> This seems to be a bug: I set SIP Publish Interval to 3600 seconds. But
> in the log I see that Blink sends the PUBLISH message at least once a
> minute...
> 
> Cheers
> T. Wimmer
> 
> On 12.08.21 21:39, g4-l...@tonarchiv.ch wrote:
>> Hi there,
>> 
>> My SIP provider asked me to disable SIP PUBLISH on my Blink client.
>> Their system answers with "400 Invalid auth header", and as far as I
>> understand, their server will eventually drop the connection for DoS
>> reasons. (DoS with one request every 10 minutes??)
>> 
>> Now I wonder if auth headers can be enabled also for PUBLISH? And if
>> not, how can PUBLISH be disabled?
>> 
>> I'm using the Ubunut client V 5.1.3
>> 
>> Best regards
>> Till Wimmer
>> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] SIP PUBLISH failes with 400 Invalid auth header

[Adrian Georgescu]

To disable sending PUBLISH you can edit the configuration file ~/.blink and add 
this section:

   +-- enabled = False
presence --|
   +

Indentation is critical make a backup of the file in case something goes wrong 
during or with the editing.

Alternatively you can install sipclients3 package from the same repository as 
blink, it contains a utility called sip-settings that can edit correctly blink 
configuration file:

sip-settings3 -c ~/blink -a set presence.enabled=False

Regards,
Adrian

> On 16 Aug 2021, at 10:46, g4-l...@tonarchiv.ch wrote:
> 
> Anyone there?
> 
> This seems to be a bug: I set SIP Publish Interval to 3600 seconds. But
> in the log I see that Blink sends the PUBLISH message at least once a
> minute...
> 
> Cheers
> T. Wimmer
> 
> On 12.08.21 21:39, g4-l...@tonarchiv.ch wrote:
>> Hi there,
>> 
>> My SIP provider asked me to disable SIP PUBLISH on my Blink client.
>> Their system answers with "400 Invalid auth header", and as far as I
>> understand, their server will eventually drop the connection for DoS
>> reasons. (DoS with one request every 10 minutes??)
>> 
>> Now I wonder if auth headers can be enabled also for PUBLISH? And if
>> not, how can PUBLISH be disabled?
>> 
>> I'm using the Ubunut client V 5.1.3
>> 
>> Best regards
>> Till Wimmer
>> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] SSL certificate verification error (PJSIP_TLS_ECERTVERIF)

[Adrian Georgescu]

You must find out why the TLS verification fails.

Perhaps the server has an expired or incorrect certificate.

You can turn on PJSIP trace and check the lines that show what certificate is 
presented by the server.

If the Common Name presented by the server is not the same as the SIP domain of 
your account, you can provide the exact name to verify the certificate against 
in the advanced properties of the account.

Adrian




> On 8 Aug 2021, at 01:24, Lars Noodén  wrote:
> 
> On 8/7/21 10:50 PM, Adrian Georgescu wrote:
>> The quickest fix is to disable the TLS verification in Advanced settings.
>> 
>> Adrian
> 
> Thanks.
> 
> What are the repercussion of that?
> 
> What would the slow fix?
> 
> /Lars
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] SSL certificate verification error (PJSIP_TLS_ECERTVERIF)

[Adrian Georgescu]

The quickest fix is to disable the TLS verification in Advanced settings.

Adrian



> On 7 Aug 2021, at 13:29, Lars Noodén  wrote:
> 
> Hello,
> 
> I am using Blink 5.1.3focal on Linux Mint 20.1 and not able to make any
> outgoing calls today.  The error I get is:
> 
>   SSL certificate verification error (PJSIP_TLS_ECERTVERIF)
> 
> That happens even when calling the test numbers.  What should I update
> to eliminate this error?
> 
> /Lars
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] debian buster

[Adrian Georgescu]

The 200 OK is not correctly handed. Can you enable both notifications and pjsip 
traces as well 

> On 28 Jul 2021, at 19:00, Alberto  wrote:
> 
> Hi,
> I mentioned I'm reproducing this on my own asterisk vm,
> I happen to have the cli open and noticed this error when blink cores
> 
> [Jul 28 22:39:43] WARNING[24030]: pjproject: : tsx0x7f7e5c315d48 
> .Error sending Response msg 200/INVITE/cseq=19985 (tdta0x7f7e50010d68): 
> Invalid operation (PJ_EINVALIDOP)
> 
> 
> 
> On Wed, 28 Jul 2021 at 22:54, Alberto  <mailto:alberto.rina...@gmail.com>> wrote:
> attached, thanks for looking into this.
> 
> On Wed, 28 Jul 2021 at 22:01, Adrian Georgescu  <mailto:a...@ag-projects.com>> wrote:
> Can you show the sip trace. Enable SIP trace file logging.
> 
> Adrian
> 
> 
> 
>> On 28 Jul 2021, at 17:57, Alberto > <mailto:alberto.rina...@gmail.com>> wrote:
>> 
>> I have python3-sipsimple 5.2.5buster  amd64
>> 
>> On Wed, 28 Jul 2021 at 17:57, Adrian Georgescu > <mailto:a...@ag-projects.com>> wrote:
>> What version of python3-sipsimple are you running?
>> 
>> dpkg -l python3-sipsimple 
>> 
>>> On 28 Jul 2021, at 13:50, Alberto >> <mailto:alberto.rina...@gmail.com>> wrote:
>>> 
>>> I could do that, at least now we know that the "Unsupported Protocol" is 
>>> about.
>>> 
>>> But now I have another problem, I tried to make a call using tls 1.2 and 
>>> sdes.
>>> Blink established the call, I got less than half a second of audio, then 
>>> cored.
>>> 
>>> I followed this for crash reports: https://icanblink.com/help/problems-qt/ 
>>> <https://icanblink.com/help/problems-qt/>
>>> but I don't see anything useful here. Any advice?
>>> 
>>> $ gdb -c core blink
>>> GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
>>> Copyright (C) 2020 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later 
>>> <http://gnu.org/licenses/gpl.html <http://gnu.org/licenses/gpl.html>>
>>> This is free software: you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law.
>>> Type "show copying" and "show warranty" for details.
>>> This GDB was configured as "x86_64-linux-gnu".
>>> Type "show configuration" for configuration details.
>>> For bug reporting instructions, please see:
>>> <http://www.gnu.org/software/gdb/bugs/ 
>>> <http://www.gnu.org/software/gdb/bugs/>>.
>>> Find the GDB manual and other documentation resources online at:
>>> <http://www.gnu.org/software/gdb/documentation/ 
>>> <http://www.gnu.org/software/gdb/documentation/>>.
>>> 
>>> For help, type "help".
>>> Type "apropos word" to search for commands related to "word"...
>>> "/usr/bin/blink": not in executable format: file format not recognized
>>> [New LWP 3893]
>>> [New LWP 3887]
>>> [New LWP 3905]
>>> [New LWP 3910]
>>> [New LWP 3914]
>>> [New LWP 3883]
>>> [New LWP 3885]
>>> [New LWP 3891]
>>> [New LWP 3917]
>>> [New LWP 3901]
>>> [New LWP 3884]
>>> [New LWP 3886]
>>> [New LWP 3889]
>>> [New LWP 3890]
>>> [New LWP 3912]
>>> [New LWP 3902]
>>> [New LWP 3913]
>>> [New LWP 3881]
>>> [New LWP 3915]
>>> [New LWP 3916]
>>> Core was generated by `/usr/bin/python3 /usr/bin/blink'.
>>> Program terminated with signal SIGSEGV, Segmentation fault.
>>> #0  0x7f945cf6a955 in ?? ()
>>> [Current thread is 1 (LWP 3893)]
>>> (gdb) 
>>> 
>>> 
>>> 
>>> 
>>> On Wed, 28 Jul 2021 at 17:43, >> <mailto:bl...@neilzone.co.uk>> wrote:
>>> 
>>> 
>>>> On 28 Jul 2021, at 17:24, Alberto >>> <mailto:alberto.rina...@gmail.com>> wrote:
>>>> 
>>>> the problem is that the server only accepts tls 1 and 
>>> 
>>> 
>>> i thought TLS 1.0 and TLS 1.1 had been deprecated?
>>> 
>>> If you had to make it work, could you use asterisk to connect to the SIP 
>>> provider, and then use Blink to connect to asterisk? (In other worse, 
>>> running your own PBX until the SIP trunk provider upgrades their security 
>>> to something more modern.)
>>> 
>>> Best wishes
>

Re: [Blink] debian buster

[Adrian Georgescu]

Please enable logging and check the log files for more information that can 
reveal the reason

https://icanblink.com/help/problems-qt/ 





> On 27 Jul 2021, at 19:31, Alberto  wrote:
> 
> Hi,
> 
> I have reinstalled my debian buster, and immediately added your repository 
> and installed blink.
> But when I try to login to a tls account it says "Registration Failed 
> (Unsupported Protocol)".
> 
> I'm using a backup of the configuration that was working before on the same 
> pc.
> Am I missing something?
> 
> Thanks
> A
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Start minimized

[Adrian Georgescu]

Use this guideline for how to create and send a patch:

https://sipsimpleclient.org/contribute/

So you use darcs to fetch the tree:

QT version: 

darcs clone da...@devel.ag-projects.com:repositories/blink-qt

Cocoa version: 

darcs clone da...@devel.ag-projects.com:repositories/blink-cocoa

Then to record the patch:

darcs record

To send the patch:

darcs send 


> On 26 Jul 2021, at 08:33, Andrey Butirsky  wrote:
> 
> Can I contribute the code somehow to add the feature?
> 
> I was able to find source code of Cocoa version only here:
> 
> http://projects.ag-projects.com/projects/blinkc/wiki/Source_Code
> 
> And no mentioned how one could contribute..
> 
> 
> 
> On 26.07.2021 14:30, Nikolai Stefanov wrote:
>> I don't have an idea, you can try it. I'm using it for Viber on X11 and it's 
>> working great.
>> 
>> _
>> 
>> www.kaminata.net
>> Ела си у дома...
>> 
>> 
>> 
>> 
>> > Оригинално писмо  
>> >От: Andrey Butirsky butir...@gmail.com 
>> >Относно: Re: [Blink] Start minimized 
>> >До: blink@lists.ag-projects.com 
>> >Изпратено на: 26.07.2021 14:22 
>> 
>> I'm using Wayland, does devilspie2 compatible with it?
>> 
>> 
>> On 26.07.2021 13:44, Nikolai Stefanov wrote:
>> > It would be nice for such option but you can use devilspie2 until it's 
>> > implemented.
>> >
>> > _
>> >
>> > > Оригинално писмо 
>> > >От: Andrey Butirsky butir...@gmail.com
>> > >Относно: [Blink] Start minimized
>> > >До: blink@lists.ag-projects.com
>> > >Изпратено на: 26.07.2021 13:26
>> >
>> > Hi,
>> >
>> > is there a way to run Blink for Linux minimized in system tray?
>> >
>> > I put it in the autostart and closing the window on every login is very
>> > annoying..
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
>> 
>> 
>> ___
>> Blink mailing list
>> 
>> Blink@lists.ag-projects.com
>> https://lists.ag-projects.com/mailman/listinfo/blink
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Start minimized

[Adrian Georgescu]

https://github.com/AGProjects 



> On 26 Jul 2021, at 08:33, Andrey Butirsky  wrote:
> 
> Can I contribute the code somehow to add the feature?
> 
> I was able to find source code of Cocoa version only here:
> 
> http://projects.ag-projects.com/projects/blinkc/wiki/Source_Code 
> 
> And no mentioned how one could contribute..
> 
> 
> 
> On 26.07.2021 14:30, Nikolai Stefanov wrote:
>> I don't have an idea, you can try it. I'm using it for Viber on X11 and it's 
>> working great.
>> 
>> _
>> 
>> www.kaminata.net 
>> Ела си у дома...
>> 
>> 
>> 
>> 
>> > Оригинално писмо  
>> >От: Andrey Butirsky butir...@gmail.com  
>> >Относно: Re: [Blink] Start minimized 
>> >До: blink@lists.ag-projects.com  
>> >Изпратено на: 26.07.2021 14:22 
>> 
>> I'm using Wayland, does devilspie2 compatible with it?
>> 
>> 
>> On 26.07.2021 13:44, Nikolai Stefanov wrote:
>> > It would be nice for such option but you can use devilspie2 until it's 
>> > implemented.
>> >
>> > _
>> >
>> > > Оригинално писмо 
>> > >От: Andrey Butirsky butir...@gmail.com <>
>> > >Относно: [Blink] Start minimized
>> > >До: blink@lists.ag-projects.com <>
>> > >Изпратено на: 26.07.2021 13:26
>> >
>> > Hi,
>> >
>> > is there a way to run Blink for Linux minimized in system tray?
>> >
>> > I put it in the autostart and closing the window on every login is very
>> > annoying..
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com <>
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> 
>> 
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com 
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Google contacts integration

[Adrian Georgescu]

We will review this as Google changed again its Contacts API.

Adrian


___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release for Linux version 5.1.1

[Adrian Georgescu]

Hello,

There is a new Blink Qt release for Linux with bug fixes and UI improvements.

blink (5.1.1) 

  * Fixed loading icons from XCAP server
  * Increase the size of some widgets

http://icanblink.com

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] [SIP Beyond VoIP] New Blink for Mac beta version with OpenPGP support

[Adrian Georgescu]

The keys are tied to the sip account used inside the app, the uuid is for 
example for sip:a...@sip2sip.info

The app generates these keys on the fly as they do not yet exists anywhere. 
Also one can replicate these keys among devices to make sure one can read them 
on all devices.

If, when using the same identity as one’s email, for example then you would 
want to reuse an existing key, maybe?

Considering the I start the client, I have a SIP account and want to talk to 
someone lets say  leena...@example.com 

I believe that is fine if I can retrieve the key prior to start a chat. But 
what is the benefit as at the destination one needs a compatible client as well 
and the moment you start it, it will generate a new key and exchange it 
automatically with the other end-point. So the user need not be aware about 
this key exchange, as knowing about it would introduce complexity (manage the 
key manually)

So I am struggling with understanding the possible benefits of importing and 
exporting these keys in to an end-to-end delivery system that takes care 
automatically about this complexity.

Adrian


> On 24 Jun 2021, at 11:08, michiel...@nlnet.nl wrote:
> 
> Signed PGP part
> Hi Adrian,
> 
>> Given that the keys can be used only inside the app, so one must have the 
>> app to make sue of the keys, and the app automatically manages these keys 
>> and exchange them, what would be the benefit of a lookup function in a 
>> public repository for keys?
> 
> keys must be obtained in some way. You can of course get them directly from 
> your contacts, and there are a number of mechanisms you could use like 
> keyservers (e.g. https://keys.openpgp.org),  Web Key Directory, DNS records 
> (OPENPGPKEY records), a service like Keyoxide (https://keyoxide.org) or just 
> plain from the website of your organisation 
> (https://nlnet.nl/people/leenaars.key). The more automated it is, the less 
> likely users are to use it.
> 
> We are supporting some of these efforts as NLnet, so if you want to get in 
> touch let me know.
> 
> Best,
> Michiel
> 
> * Implement message encryption using OpenPGP
 
 THis sounds great. Do you have more information on the implementation. Is 
 it only MESSAGE or SIP messages in general? Have you implemented PGP key 
 lookup somehow?
>>> 
>>> Only SIP Message.
>>> 
>>> We have not implement key lookup but it could be easily added, I suppose..
> 
> 
> --
> Support NLnet, the open internet and open source with just 5 minutes
> of your time. Make a difference today.
> 
> Visit: http://nlnet.nl/help (English) - http://nlnet.nl/ayuda (Espanol)
> 
> - -
> 
> Do you know people that have ideas to improve the internet? Or maybe you have 
> such an idea yourself? Check out what we can do for you at 
> https://nlnet.nl/propose and apply!
> 
> 



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] [SIP Beyond VoIP] New Blink for Mac beta version with OpenPGP support

[Adrian Georgescu]

Hi Olle,

I have a question for you.

Given that the keys can be used only inside the app, so one must have the app 
to make sue of the keys, and the app automatically manages these keys and 
exchange them, what would be the benefit of a lookup function in a public 
repository for keys?

Regards,
Adrian


> On 23 Jun 2021, at 07:35, Adrian Georgescu  wrote:
> 
> 
> 
>> On 23 Jun 2021, at 05:13, Olle E. Johansson > <mailto:o...@edvina.net>> wrote:
>> 
>> 
>> 
>>> On 22 Jun 2021, at 16:55, Adrian Georgescu >> <mailto:a...@ag-projects.com>> wrote:
>>> 
>>> Blink Beta for Mac is now available with messaging features compatible with 
>>> Sylk Messaging Suite.
>>> 
>>> http://icanblink.com/download/ <http://icanblink.com/download/>
>>> 
>>> Changelog:
>>> 
>>> Version 8.5.0
>>> 
>>> June 21st, 2021
>>> 
>>> * Implement message encryption using OpenPGP
>> 
>> THis sounds great. Do you have more information on the implementation. Is it 
>> only MESSAGE or SIP messages in general? Have you implemented PGP key lookup 
>> somehow?
> 
> Only SIP Message.
> 
> We have not implement key lookup but it could be easily added, I suppose..  
> 
>> 
>> Very curious.
>> 
>> As always, thank you for your work!
>> 
>> /O
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> <https://lists.ag-projects.com/mailman/listinfo/blink>
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release for Linux version 5.1.0

[Adrian Georgescu]

Hello,

There is a new Blink Qt release for Linux with new features and critical bug 
fixes.

blink (5.1.0) unstable; urgency=medium

  * Implemented auto answer
  * Added per contact auto answer setting
  * Added NAT traversal preferences panel
  * Fixed XCAP getheaders of HTTP objects, renamed to get in Python3
  * Fixed xcap trace logging
  * Fixed saving local icon
  * Fixed a broken import
  * Rename chat window title
  * Automatically set sip2sip.info server settings URL
  * Refactored application menus
  * Rename some preferences options

VP8/9 video session crashes have been fixed, you must upgrade python3-sipsimple 
package to obtain them. 

http://icanblink.com

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] [SIP Beyond VoIP] New Blink for Mac beta version with OpenPGP support

[Adrian Georgescu]

> On 23 Jun 2021, at 05:13, Olle E. Johansson  wrote:
> 
> 
> 
>> On 22 Jun 2021, at 16:55, Adrian Georgescu > <mailto:a...@ag-projects.com>> wrote:
>> 
>> Blink Beta for Mac is now available with messaging features compatible with 
>> Sylk Messaging Suite.
>> 
>> http://icanblink.com/download/ <http://icanblink.com/download/>
>> 
>> Changelog:
>> 
>> Version 8.5.0
>> 
>> June 21st, 2021
>> 
>> * Implement message encryption using OpenPGP
> 
> THis sounds great. Do you have more information on the implementation. Is it 
> only MESSAGE or SIP messages in general? Have you implemented PGP key lookup 
> somehow?

Only SIP Message.

We have not implement key lookup but it could be easily added, I suppose..  

> 
> Very curious.
> 
> As always, thank you for your work!
> 
> /O
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink for Mac beta version with OpenPGP support

[Adrian Georgescu]

Blink Beta for Mac is now available with messaging features compatible with 
Sylk Messaging Suite.

http://icanblink.com/download/ 

Changelog:

Version 8.5.0

June 21st, 2021

* Implement message encryption using OpenPGP
* Solved blocking green thread because of bad history entries
* Screen sharing fixes
* Video session end fix
* Message replication fixes
* Fixed resizing chat drawer elements
* Fixed sending displayed notifications for message sessions
* Added rendering for delayed messages
* Message session fixes
* History viewer fixes
* File Transfer fixes
* TLS fixes
* DNS Lookup fixes


Regards,
Adrian




___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink for Mac beta version 8.4.3

[Adrian Georgescu]

Blink Beta for Mac is now available with messaging features compatible with 
Sylk Messaging Suite.

http://icanblink.com/download/

Changelog:

Version 8.4.3

June 15th, 2021

• Fixed sending displayed notifications for message sessions
• Added rendering for delayed messages
• Fixed Message window tab dragging
• Message session fixes
• History viewer fixes
• File Transfer fixes
• History viewer fixes
• TLS verification fixes
• DNS lookup fixes


___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release 5.0.0 for Linux Debian and Ubuntu

[Adrian Georgescu]

There is a new version of Blink Qt for Linux.

Changelog


blink (5.0.0) unstable; urgency=medium

  * Added VP9 codec
  * Implemented TLS certificate verification
  * Added per account TLS peer name to verify against
  * Update default CA list
  * Enable by default TLS transport
  * Fixed logging

To update or install go to:

http://icanblink.com

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink for Mac beta version

[Adrian Georgescu]

Blink Beta for Mac is now available with messaging features compatible with the 
upcoming Sylk Messaging Suite.

http://icanblink.com/download/ 

Changelog:

Version 8.3.1

June 8th, 2021

IMDN fixes
Version 8.3.0

June 7th, 2021

Implemented IMDN notifications
Version 8.2.0

June 6th, 2021

TLS improvements
Update audio codecs
Fixed updating chat widgets when session changes
Do not update audio drawer display name with ZRTP peername
Fixed polling log files for size
Fixed decoding SIP trace payload
Bonjour logging improvements
Log DNS Resolver initialization
Log full uri of selected contact when starting session 
Select configured protocol for bonjour neighbours
Added SIP transport selection for Bonjour Account 
Fixed Bonjour lookups
Version 8.1.0

June 2nd, 2021

Added AMR wideband codec
Version 8.0.2

June 1st, 2021

SMS and MSRP CPIM payload fixes
Version 8.0.1

May 28th, 2021

Conference fixes
SMS sessions improvements
Added storage for encryption keys for accounts and contacts
Version 8.0.0

May 9th, 2021

Added VP9 codec
TLS verify server fixes
Version 7.3.0

April 9th, 2021

MSRP chat stream fix
Version 7.2.8

April 1st, 2021

DNS fixes
Version 7.2.8

March 25th, 2021

Fixed handling incoming CPIM payloads for MESSAGE sessions
Version 7.2.7

March 25th, 2021

Fix for incoming calls
Use CPIM envelope for outgoing MESSAGE sessions
Version 7.2.6

March 23rd, 2021

Improve handling of network conditions changes
Added permissions requests for Microphone and Contacts
Version 7.2.5

March 21st, 2021

Improved Spanish and Dutch layouts
Improved logging in Debug window
Fixed handling failed registration notifications
Improved handling of some blocking operations (DNS, XCAP)
Version 7.2.4

March 20th, 2021

Fixed SMS for non-EN languages
Fixed Aqua theme for Session Info Panel
Version 7.2.3

March 18th, 2021

Fixed audio recordings
Version 7.2.2

March 15th, 2021

Fixed rtp stream
Fixed contacts filter
Version 7.2.1

March 14th, 2021

Core fixes
Fixed DNS NAPTR lookup
Added xcap_diff setting
Version 7.2.0

March 13th, 2021

Added back video sessions
Improved logs window
Allow SIP MESSAGE to Bonjour neighbours
Version 7.1.1

March 8th, 2021

Improve drawer resizing
Fixed handling xcap failures logs
Version 7.1.0

March 7th, 2021

Added XCAP trace in Debug Window
Fixed sending DTMF
Avoid positive loops when updating XCAP documents
Fixed generating replication password
Version 7.0.9

March 6th, 2021

Fix for incoming calls
Version 7.0.8

March 5th, 2021

Fixed XCAP replication
Improve Debug window data
Presence fixes
Version 7.0.7

March 2nd, 2021

Fixed display of conference participants
Make package smaller in size
Version 7.0.6

March 1st, 2021

Fixed presence subscriptions
Fixed file transfers
Version 7.0.5

February 28th, 2021

First Notarized by Apple version
Version 7.0.4

February 24th, 2021

OTR encryption improvements and fixes
Version 7.0.3

February 23rd, 2021

Added OTR encryption for MESSAGE sessions
Fixed LDAP queries
Version 7.0.2

February 22nd, 2021

Fixed OTR SMP window
Remove unused icons in SMS window
Enable Shor Messages by default
Disable MWI subscription by default
Added LDAP module
Version 7.0.1

February 20th, 2021

Fixed OTR verification
Version 7.0.0

February 16th, 2021

Migrate app to Python3
Make app compatible with Mac 11.2 Big Sur

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] TLS Server Verify not functioning

[Adrian Georgescu]

This took awhile but is now implemented into latest python3-sipsimple trunk 
based on this thread:

https://github.com/AGProjects/python-sipsimple/pull/7

This and other changes and improvements will be available soon in Blink and 
SylkServer alike.

Regards,
Adrian


> On 20 Mar 2020, at 10:22, Dr. Karl Heinz Grube  
> wrote:
> 
> Hello!
> 
> I have an Asterisk server running and with Linphone and Jami I am able to 
> verify the TLS certificates, but with blink it does not work:
> 
> pjsip_trace.txt:
> 
> [blink 5147] (5) 2020-03-20 12:07:33.353   endpoint Request msg 
> REGISTER/cseq=1 (tdta0x7f648010daf0) created.
> [blink 5147] (5) 2020-03-20 12:07:33.353 tsx0x7f648010c .Transaction created 
> for Request msg REGISTER/cseq=1 (tdta0x7f648010daf0)
> [blink 5147] (5) 2020-03-20 12:07:33.353 tsx0x7f648010c Sending Request msg 
> REGISTER/cseq=1 (tdta0x7f648010daf0) in state Null
> [blink 5147] (5) 2020-03-20 12:07:33.353  sip_resolve.c .Target 
> '10.47.0.14:0' type=TLS resolved to '10.47.0.14:5061' type=TLS (TLS transport)
> [blink 5147] (4) 2020-03-20 12:07:33.353 tlsc0x7f648018 .TLS client transport 
> created
> [blink 5147] (4) 2020-03-20 12:07:33.353 tlsc0x7f648018 .TLS transport 
> 10.133.0.3:43721 is connecting to 10.47.0.14:5061...
> [blink 5147] (5) 2020-03-20 12:07:33.353 tsx0x7f648010c .State changed from 
> Null to Calling, event=TX_MSG
> [blink 5147] (3) 2020-03-20 12:07:33.412 tlsc0x7f648018 TLS connect() error: 
> SSL certificate verification error (PJSIP_TLS_ECERTVERIF) [code=171173]
> [blink 5147] (3) 2020-03-20 12:07:33.412 tsx0x7f648010c Failed to send 
> Request msg REGISTER/cseq=1 (tdta0x7f648010daf0)! err=171173 (SSL certificate 
> verification error (PJSIP_TLS_ECERTVERIF))
> [blink 5147] (5) 2020-03-20 12:07:33.412 tsx0x7f648010c State changed from 
> Calling to Terminated, event=TRANSPORT_ERROR
> [blink 5147] (5) 2020-03-20 12:07:33.412 tlsc0x7f648018 TLS send() error, 
> sent=-171173
> [blink 5147] (5) 2020-03-20 12:07:33.416 tsx0x7f648010c Timeout timer event
> [blink 5147] (5) 2020-03-20 12:07:33.416 tsx0x7f648010c .State changed from 
> Terminated to Destroyed, event=TIMER
> [blink 5147] (5) 2020-03-20 12:07:33.416 tsx0x7f648010c Transaction destroyed!
> 
> /etc/asterisk/sip.conf:
> 
> [general]
> context=public
> bindaddr=::
> tlsbindaddr=::
> allowoverlap=yes
> externip=(replaced for this email)
> localnet=10.0.0.0/255.0.0.0
> qualify=yes
> qualifyfreq=60
> transport=tls,udp
> tlsclientmethod=tlsv1.2
> tlsenable=yes
> udpenable=yes
> tcpenable=no
> encryption=yes
> tlscipher=EDH+aRSA+AES256:EECDH+aRSA+AES256
> tlscertfile=(replaced for this email)
> tlsprivatekey=(replaced for this email)
> rtcachefriends=yes
> nat=auto_force_rport,auto_comedia
> directmedia=no
> subscribecontext=phone-hints
> callcounter=yes
> videosupport=yes
> disallow=all
> allow=g722
> allow=speex
> allow=speex16
> allow=speex32
> allow=ulaw
> allow=alaw
> allow=ilbc
> allow=gsm
> allow=vp8
> 
> 
> I use /etc/ssl/certs/ca-certificates as the CA.
> 
> 
> Oh and I used openssl strace and the certificate is valid (with this CA as 
> well)
> 
> 
> -- Karl
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release 4.1.0 for Linux Debian and Ubuntu

[Adrian Georgescu]

There is a new version of Blink Qt with Google contacts integration.

Changelog

blink (4.1.0)

  * Google Contacts integration
  * Allow calling to all URIs belonging to a contact (right click on reach 
contact for a contextual menu)

To update or install go to:

http://icanblink.com

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Keyboard shortcuts for macOS

[Adrian Georgescu]

The current call can be hangup by pressing the Esc key.

For answering there is no key because there could be multiple incoming calls 
with different media types and is impossible to determine which one to answer. 
Plus you may be typing into another window while receiving an incoming call and 
by mistake a key stroke will be sent to the alert panel.

The shortcut keys can be found here:

http://icanblink.com/help/manual-mac/audio-calls-mac/

Adrian

> On 2 Apr 2021, at 12:13, bl...@neilzone.co.uk wrote:
> 
> First, thank you for bringing Blink back to macOS!
> 
> I have checked the manual without finding anything: are there keyboard 
> shortcuts in Blink for “End call / Hangup”, and to answer an incoming call?
> 
> Best wishes
> 
> Neil
> 
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Pro for Mac OS version 5.1.1

[Adrian Georgescu]

Hello,

There is a new release of Blink Pro in Mac App Store with the following changes:

Version 5.1.1

March 25th, 2021

 * Fix for incoming sessions
 * Improve handling of network conditions changes
 * Use CPIM envelope for outgoing MESSAGE sessions
 * Added Microphone permission request
 * Added Contacts permission request 
 * Improved Spanish and Dutch layouts
 * Improved logging in Debug window
 * Fixed handling failed registration notifications
 * Improved handling of some blocking operations (DNS, XCAP)
 * Fixed Aqua theme for Session Info Panel
 * Fixed audio recordings


Version 5.1.0

March 15th, 2021

 * Added video sessions (VP8 and H.264 codecs)
 * Fixed display name in alert panel
 * Fixes in session info panel
 * Fixed DTMF sending
 * Fixed fitering contacts
 * Fixed handling contact backups
 * Fixed decoding contact icon
 * Fixed decoding server call history data
 * Fixed resizing drawers
 * Fixed generating replication password
 * Make DNS lookup failure fit audio box
 * Capture history exception
 * Allow Message method to Bonjour accounts
 * Several logging fixes and improvements

Version 5.0.0

March 3rd, 2021

 * Migrate to Python 3
 * Renewed TLS certificates
 * Added OTR for SIP MESSAGE sessions


—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Latest Blink for Mac - Microphone issue

[Adrian Georgescu]

We pushed a new update to Mac App Store with the fix. Now we wait for Apple 
approval.

> On 23 Mar 2021, at 10:14, Adrian Georgescu  wrote:
> 
> I confirm that indeed that flag is missing.
> 
> We will make an update right away.
> 
> Adrian
> 
> 
> 
>> On 23 Mar 2021, at 09:03, Radek Henyš > <mailto:r.he...@seznam.cz>> wrote:
>> 
>> NSMicrophoneUsageDescription
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Latest Blink for Mac - Microphone issue

[Adrian Georgescu]

I confirm that indeed that flag is missing.

We will make an update right away.

Adrian



> On 23 Mar 2021, at 09:03, Radek Henyš  wrote:
> 
> NSMicrophoneUsageDescription

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release 4.0.0 (Debian package)

[Adrian Georgescu]

Blink Qt3 is now packaged as .deb for Ubuntu Bionic, Ubuntu Focal and Debian 
Buster 10.

http://icanblink.com 

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Pro for Mac OS version 7.0.0

[Adrian Georgescu]

Blink Pro is back again in Mac App Store and compatible with MacOS Catalina and 
Big Sur.

To update to the new version use your Mac built-in App Store or visit:

http://icanblink.com 

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Blink Qt release 4.0.0

[Adrian Georgescu]

There is a new Blink Qt release for Linux. 


Change-log

blink (4.0.0)

  * Migrated code to Python 3
  * Show sip account registrar address in preferences panel


http://icanblink.com 

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] Blink crashes on Mac

[Adrian Georgescu]

For those who suffer about this.

Unfortunately, we are at the mercy of powers beyond our control.

We have discovered the reason for the recent crashes of Blink on Mac. The 
existing app already in the App Store started to crash on new installations and 
we were not able to submit a new version. Building a version for distribution 
outside the App store hit the same wall.

Despite our efforts to rewrite the app based on latest requirements imposed by 
Apple, the otherwise well working app crashes after being notarised by Apple. 
This seems to be the case for any Python written application.

The core of the problem is described here:

https://github.com/ronaldoussoren/pyobjc/issues/347 


We are witnessing the obvious consequences of an evil policy that started 
awhile ago with the introduction of sandboxing on what was once known to be an 
open computer platform.

We are now adults being treated like children.

We do not like to be playing into a sandbox as adults, do we?

Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] Blink for Mac OS 11.2 Big Sur

[Adrian Georgescu]

Blink for MacOS 11.2 Big Sur can be download from:

http://beta.icanblink.com

Regards,
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] New Blink Qt version for Python3

[Adrian Georgescu]

The main blink-qt repository has been updated with the Python3 changes, use it 
for any further downloads

https://github.com/AGProjects/blink-qt <https://github.com/AGProjects/blink-qt>

Regards,
Adrian

> On 8 Feb 2021, at 06:51, Adrian Georgescu  <mailto:a...@ag-projects.com>> wrote:
> 
> Blink Qt SIP client for Linux and Window is now available for newer Linux 
> distributions running Python version 3.
> 
> The software is available for download at:
> 
> http://download.ag-projects.com/SipSimpleSDK/Python3/ 
> <http://download.ag-projects.com/SipSimpleSDK/Python3/>
> 
> While extensive tests were performed with success for many of the functions 
> present, there may still be bugs related to the migration from Python 2 to 
> Python 3.
> 
> Any feedback is welcome.
> 
> Kind regards,
> Adrian
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Manual installation / build

[Adrian Georgescu]

Check the debian folder. Inside control file you can find all dependencies

Adrian


> On 1 May 2020, at 12:45, Thomas <74cmo...@gmail.com> wrote:
> 
> Hello,
> 
> I want to build the software from tar archives, however the dependencies
> are not clear.
> 
> Can you please share the dependencies, in particular the python modules?
> Is it correct that only python2 is working?
> 
> THX
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New Raspbian repository

[Adrian Georgescu]

sylkserver, blink-qt, sipclients and all their dependencies are now packaged 
for Raspbian operating system so you can run the software on a Raspberry Pi 
running Debian Buster 10 with ease.

The location of the Raspbian repositories are:

debhttp://ag-projects.com/raspbian buster main 
deb-src http://ag-projects.com/raspbian buster main

With the addition of the latest features of the command line clients, one can 
integrate them nicely into IoT projects running on Raspberry Pi, for example 
using one single hardware button to make, receive and hangup calls:

https://sipsimpleclient.org/testing/

—
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Google contacts

[Adrian Georgescu]

Google contacts API is not working for a long time due to undocumented changes 
made by Google. 

Adrian


> On 27 Mar 2020, at 16:12, Alberto  wrote:
> 
> Hi,
> I've configured access to my google contacts, I have 2FA enabled.
> The procedure terminated correctly, but when I restart blink it shows this 
> error:
> 
> ERROR[main] Unhandled exception in notification observer 
>  while 
> handling notification 'GoogleAuthorizationWasAccepted'
> ERROR[main] Traceback (most recent call last):
> ERROR[main]   File 
> "/app/lib/python2.7/site-packages/application/notification.py", line 211, in 
> post_notification
> ERROR[main] observer.handle_notification(notification)
> ERROR[main]   File "/app/lib/python2.7/site-packages/blink/contacts.py", 
> line 945, in handle_notification
> ERROR[main] handler(notification)
> ERROR[main]   File "/app/lib/python2.7/site-packages/blink/contacts.py", 
> line 951, in _NH_GoogleAuthorizationWasAccepted
> ERROR[main] self._service = build('people', 'v1', 
> credentials=notification.data.credentials, http=Http(timeout=10), 
> cache_discovery=False)  # todo: what's the best fix for cache?
> ERROR[main]   File 
> "/app/lib/python2.7/site-packages/googleapiclient/_helpers.py", line 134, in 
> positional_wrapper
> ERROR[main] return wrapped(*args, **kwargs)
> ERROR[main]   File 
> "/app/lib/python2.7/site-packages/googleapiclient/discovery.py", line 235, in 
> build
> ERROR[main] client_options=client_options
> ERROR[main]   File 
> "/app/lib/python2.7/site-packages/googleapiclient/_helpers.py", line 134, in 
> positional_wrapper
> ERROR[main] return wrapped(*args, **kwargs)
> ERROR[main]   File 
> "/app/lib/python2.7/site-packages/googleapiclient/discovery.py", line 345, in 
> build_from_document
> ERROR[main] raise ValueError("Arguments http and credentials are 
> mutually exclusive.")
> ERROR[main] ValueError: Arguments http and credentials are mutually 
> exclusive.
> 
> Do you know what's wrong with it?
> Thanks
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New TLS certificate for all Blink variants

[Adrian Georgescu]

You may have noticed, if you are using Blink client with the default SIP 
accounts from sip2sip.info , that TLS transport does not 
work anymore. This is due to the expiration of the TLS certificate bundled with 
Blink.

To fix this, you can download the new certificate from:

https://github.com/AGProjects/blink-qt/blob/master/resources/tls/default.crt

And replace your current certificate with it.

For Blink for Mac the path of the old certificate is, depending on the 
application:

/Applications/Blink\ Pro.app/Contents/Resources/default.crt 
/Applications/Blink\ Lite.app/Contents/Resources/default.crt 
/Applications/SIP2SIP.app/Contents/Resources/default.crt 

After restarting the application, TLS transport will be functional again.

Regards,
Adrian



___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Flatpak

[Adrian Georgescu]

You need to request a SIP address from a SIP service provider or use the 
built-in SIP account from Blink

Adrian

> On 27 Mar 2020, at 13:22, Alberto  wrote:
> 
> Hi,
> sorry to butt in, but I was planning to learn some flatpak, so I spent a 
> whole week on it.
> It's published here: https://github.com/syco/flathub/tree/blink 
> <https://github.com/syco/flathub/tree/blink>
> 
> I'm sure there are still missing dependencies, but I managed to compile it 
> and make a call, so it's working ok-ish.
> Would be great if the developers could have a look and point out any mistake 
> they notice, I'm sure they know their own application better than me.
> 
> On a separate note, I use kde with breeze dark, and there's an issue with it 
> as you can see it in the below screnshot:
> 
> 
> Thanks everyone..
> 
> 
> On Thu, 19 Mar 2020 at 14:44, Adrian Georgescu  <mailto:a...@ag-projects.com>> wrote:
> We only do Debian and tar archives.
> 
> New volunteers would be welcome as we do not have resources for packaging for 
> every possible distribution out there.
> 
> Regards,
> Adrian
> 
> 
>> On 19 Mar 2020, at 11:43, Nikolai Stefanov > <mailto:m...@abv.bg>> wrote:
>> 
>> But Flatpak is one package for all distributions and will reduce maintenance 
>> efforts :)
>> 
>> _____
>> 
>> www.kaminata.net <http://www.kaminata.net/index.php>
>> Ела си у дома...
>> 
>> 
>> 
>> 
>> > Оригинално писмо  
>> >От: Adrian Georgescu a...@ag-projects.com <mailto:a...@ag-projects.com> 
>> >Относно: Re: [Blink] Flatpak 
>> >До: Blink Support Forum > ><mailto:blink@lists.ag-projects.com>> 
>> >Изпратено на: 19.03.2020 16:13 
>> 
>> We only do Debian and tar archives.
>> 
>> New volunteers would be welcome as we do not have resources for packaging 
>> for every possible distribution out there.
>> 
>> Regards,
>> Adrian
>> 
>> On 19 Mar 2020, at 10:56, Nikolai Stefanov < m...@abv.bg <>> wrote:
>> 
>> Hello, 
>> We can't find them, for they were volunteers and the AUR sites for this 
>> packages are deleted. I think it's in your intrest too more people use 
>> Blink, so Flatpak woud be great :) May be migration to Python 3? 
>> 
>> _ 
>> 
>> www.kaminata.net <http://www.kaminata.net/index.php> 
>> Ела си у дома... 
>> 
>> 
>> 
>> 
>> > Оригинално писмо  
>> >От: Adrian Georgescu a...@ag-projects.com <> 
>> >Относно: Re: [Blink] Flatpak 
>> >До: Blink Support Forum < blink@lists.ag-projects.com <>> 
>> >Изпратено на: 19.03.2020 15:44 
>> 
>> We only provide Debian packages and tar archives ourselves. You must find 
>> those who support those packages and if they need to locate the sources we 
>> can help them.
>> 
>> Adrian
>> 
>> On 19 Mar 2020, at 09:39, Nikolai Stefanov < m...@abv.bg <>> wrote:
>> 
>> Hello, 
>> Some python 2 packages are removed from Arch AUR so Blink can't be used on 
>> Arh and Arch-based distros like Manjaro, Arco etc. Is there any chance for a 
>> Flathub package? 
>> Thank you :) 
>> 
>> _ 
>> 
>> www.kaminata.net <http://www.kaminata.net/index.php> 
>> Ела си у дома... 
>> ___ 
>> Blink mailing list 
>> Blink@lists.ag-projects.com <> 
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> <https://lists.ag-projects.com/mailman/listinfo/blink> 
>> 
>> ___ 
>> Blink mailing list 
>> Blink@lists.ag-projects.com <> 
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> <https://lists.ag-projects.com/mailman/listinfo/blink> 
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>> https://lists.ag-projects.com/mailman/listinfo/blink 
>> <https://lists.ag-projects.com/mailman/listinfo/blink>
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
> https://lists.ag-projects.com/mailman/listinfo/blink 
> <https://lists.ag-projects.com/mailman/listinfo/blink>
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Flatpak

[Adrian Georgescu]

We only do Debian and tar archives.

New volunteers would be welcome as we do not have resources for packaging for 
every possible distribution out there.

Regards,
Adrian


> On 19 Mar 2020, at 11:43, Nikolai Stefanov  wrote:
> 
> But Flatpak is one package for all distributions and will reduce maintenance 
> efforts :)
> 
> _
> 
> www.kaminata.net <http://www.kaminata.net/index.php>
> Ела си у дома...
> 
> 
> 
> 
> > Оригинално писмо  
> >От: Adrian Georgescu a...@ag-projects.com 
> >Относно: Re: [Blink] Flatpak 
> >До: Blink Support Forum  
> >Изпратено на: 19.03.2020 16:13 
> 
> We only do Debian and tar archives.
> 
> New volunteers would be welcome as we do not have resources for packaging for 
> every possible distribution out there.
> 
> Regards,
> Adrian
> 
> On 19 Mar 2020, at 10:56, Nikolai Stefanov < m...@abv.bg <>> wrote:
> 
> Hello, 
> We can't find them, for they were volunteers and the AUR sites for this 
> packages are deleted. I think it's in your intrest too more people use Blink, 
> so Flatpak woud be great :) May be migration to Python 3? 
> 
> _ 
> 
> www.kaminata.net <http://www.kaminata.net/index.php> 
> Ела си у дома... 
> 
> 
> 
> 
> > Оригинално писмо  
> >От: Adrian Georgescu a...@ag-projects.com <> 
> >Относно: Re: [Blink] Flatpak 
> >До: Blink Support Forum < blink@lists.ag-projects.com <>> 
> >Изпратено на: 19.03.2020 15:44 
> 
> We only provide Debian packages and tar archives ourselves. You must find 
> those who support those packages and if they need to locate the sources we 
> can help them.
> 
> Adrian
> 
> On 19 Mar 2020, at 09:39, Nikolai Stefanov < m...@abv.bg <>> wrote:
> 
> Hello, 
> Some python 2 packages are removed from Arch AUR so Blink can't be used on 
> Arh and Arch-based distros like Manjaro, Arco etc. Is there any chance for a 
> Flathub package? 
> Thank you :) 
> 
> _ 
> 
> www.kaminata.net <http://www.kaminata.net/index.php> 
> Ела си у дома... 
> ___ 
> Blink mailing list 
> Blink@lists.ag-projects.com <> 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> <https://lists.ag-projects.com/mailman/listinfo/blink> 
> 
> ___ 
> Blink mailing list 
> Blink@lists.ag-projects.com <> 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Flatpak

[Adrian Georgescu]

We only do Debian and tar archives.

New volunteers would be welcome as we do not have resources for packaging for 
every possible distribution out there.

Regards,
Adrian

> On 19 Mar 2020, at 10:56, Nikolai Stefanov  wrote:
> 
> Hello,
> We can't find them, for they were volunteers and the AUR sites for this 
> packages are deleted. I think it's in your intrest too more people use Blink, 
> so Flatpak woud be great :) May be migration to Python 3?
> 
> _
> 
> www.kaminata.net <http://www.kaminata.net/index.php>
> Ела си у дома...
> 
> 
> 
> 
> >---- Оригинално писмо  
> >От: Adrian Georgescu a...@ag-projects.com 
> >Относно: Re: [Blink] Flatpak 
> >До: Blink Support Forum  
> >Изпратено на: 19.03.2020 15:44 
> 
> We only provide Debian packages and tar archives ourselves. You must find 
> those who support those packages and if they need to locate the sources we 
> can help them.
> 
> Adrian
> 
> On 19 Mar 2020, at 09:39, Nikolai Stefanov < m...@abv.bg <>> wrote:
> 
> Hello, 
> Some python 2 packages are removed from Arch AUR so Blink can't be used on 
> Arh and Arch-based distros like Manjaro, Arco etc. Is there any chance for a 
> Flathub package? 
> Thank you :) 
> 
> _ 
> 
> www.kaminata.net <http://www.kaminata.net/index.php> 
> Ела си у дома... 
> ___ 
> Blink mailing list 
> Blink@lists.ag-projects.com <> 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Flatpak

[Adrian Georgescu]

We only provide Debian packages and tar archives ourselves. You must find those 
who support those packages and if they need to locate the sources we can help 
them.

Adrian

> On 19 Mar 2020, at 09:39, Nikolai Stefanov  wrote:
> 
> Hello,
> Some python 2 packages are removed from Arch AUR so Blink can't be used on 
> Arh and Arch-based distros like Manjaro, Arco etc. Is there any chance for a 
> Flathub package?
> Thank you :)
> 
> _
> 
> www.kaminata.net 
> Ела си у дома...
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] sip2sip.info unreachable via TLS connection

[Adrian Georgescu]

To find out the ports used for SIP TCP and TLS fro a given domain your device 
must perform the following DNS lookups:

dig NAPTR naptr sip2sip.info
sip2sip.info.   3599IN  NAPTR   15 100 "s" "SIPS+D2T" "" 
_sips._tcp.sip2sip.info.


dig SRV _sips._tcp.sip2sip.info.
_sips._tcp.sip2sip.info. 299IN  SRV 100 10 443 proxy.sipthor.net.

The port used for TLS at this moment is 443 but it may change at any time.


Regards,
Adrian


> On 16 Dec 2019, at 15:27, Michael Nagie  wrote:
> 
> Hello,
> I need a little help.
> I've been unable to connect to sip2sip.info via TLS with my Cisco 
> SPA504G device for a couple of days now.
> 
> sip2sip.info status says: all systems operational
> yet I can't establish a secure connection.
> 
> If I choose TCP transport protocol then it can connect otherwise with 
> TLS it says 'Failed - Not Reachable'
> 
> Here's my configuration, it's pretty basic, I didn't change much:
> 
> General
> Line Enable:  yes
> 
> Share Line Appearance
> Share Ext: privateShared User ID: 
> Subscription Expires: 3600Restrict MWI: no
> Monitor User ID:  SCA Unseize Delay: 0
> 
> NAT Settings
> NAT Mapping Enable: noNAT Keep Alive Enable:  no  
> NAT Keep Alive Msg: $NOTIFY NAT Keep Alive Dest: $PROXY
> 
> Network Settings
> SIP TOS/DiffServ Value: 0x68SIP CoS Value: 3
> RTP TOS/DiffServ Value: 0xb8RTP CoS Value: 6
> Network Jitter Level: high  Jitter Buffer Adjustment: up and down 
> 
> SIP Settings
> SIP Transport: TLSSIP Port: 5060
> SIP 100REL Enable: no EXT SIP Port:   
> Auth Resync-Reboot: yes   SIP Proxy-Require:  
> SIP Remote-Party-ID: no   Referor Bye Delay: 4
> Refer-To Target Contact: no   Referee Bye Delay: 0
> SIP Debug Option: noneRefer Target Bye Delay: 0
> Sticky 183: noAuth INVITE: no
> Ntfy Refer On 1xx-To-Inv: yes Use Anonymous With RPID: yes
> Set G729 annexb: none Voice Quality Report Address:
> User Equal Phone: no  
> 
> Call Feature Settings
> Blind Attn-Xfer Enable: noMOH Server: 
> Message Waiting: no   Auth Page: no
> Default Ring: 1   Auth Page Realm:
> Conference Bridge URL:  Auth Page Password:   
> Mailbox ID:   Voice Mail Server:  
> Voice Mail Subscribe Interval:  86400   State Agent:  
> CFWD Notify Serv: no  CFWD Notifier:  
> User ID with Domain: no   Broadsoft ACD: no   
> Auto Ans Page On Active Call: yes Feature Key Sync: no
> HuaWei SBC: yes   Call Park Monitor Enable: yes   
> Enable Broadsoft Hoteling: no Hoteling Sbscrpton Expirs:3600
> 
> Proxy and Registration
> Proxy: sip2sip.info
> Outbound Proxy:   
> Alternate Proxy:  
> Alternate Outbound Proxy:0
> Use Outbound Proxy: noUse OB Proxy In Dialog: yes
> Register: yes Make Call Without Reg: no   
> Register Expires: 3600  Ans Call Without Reg: no  
> Use DNS SRV: yes  DNS SRV Auto Prefix: yes
> Proxy Fallback Intvl: 3600  Proxy Redundancy Method:normal   
> Dual Registration: no Auto Register When Failover:no  
> 
> Subscriber Information
> Display Name: My Name   User ID: user_id
> Password:   Use Auth ID: no
> Auth ID: user_idReversed Auth Realm:  
> Mini Certificate: 
> SRTP Private Key: 
> Resident Online Number: SIP URI:  
> 
> Audio Configuration
> Preferred Codec:  G722Use Pref Codec Only: no 
> Second Preferred Codec: Unspecified Third Prfrrd Codc:Unspcfd
> G711u Enable: yes G711a Enable: yes
> G729a Enable: yes G722 Enable: yes
> G726-16 Enable: yes   G726-24 Enable: yes 
> G726-32 Enable: yes   G726-40 Enable: yes 
> Release Unused Codec: yes DTMF Process AVT: yes
> Silence Supp Enable: yes  DTMF Tx Method: Auto
> DTMF Tx Volume for AVT Packet:0 DTMF AVT Packet Interval:0
> Use Remote Pref Codec: no Codec Negotiation: Default  
> Rx Payload In 18x Media Session: Use Local SDP
> Dial Plan
> Dial Plan:
> (*xx|[3469]11|0|00|[2-9]xx|1xxx[2-9]xxS0|.)
> Caller ID Map:
> Enable IP Dialing: yesEmergency Number:
> 
> 
> -- 
> Best Regards,
> 
> Michael Nagie
> e: promike1...@gmail.com
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Google contacts in different versions of Blink

[Adrian Georgescu]

Google is continuously changing their contacts API without any heads up or 
documentation to 3rd party developers using it. It was a permanent battle for 
many years, and unfortunatly they won.

Adrian

> On 18 Oct 2019, at 05:28, Vladislav Jakubů - ONLINESHOP.cz 
>  wrote:
> 
> Hi,
> 
> I use Blink in Windows 10.
> 
> I have a problem with google contacts in Blink version 3.2.0.
> I do not see google sign-in when I enable google contacts.
> 
> If I enable google contacts in Blink version 3.1.0, google login will work 
> fine, but I will see an empty bookmark in my contacts. After updating Blink 
> to version 3.2.0, the contacts are displayed.
> 
> Is it possible to download the Blink installation file for Windows version 
> 3.1.0?
> 
> Regards,
> 
> Vladislav Jakubu
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Audio Recording Options?

[Adrian Georgescu]

> On 18 Oct 2019, at 13:15, m...@utility6.com  wrote:
> 
> Hi Everyone,
> 
> I'm looking to find out how to alter some recording parameters.
> 
> - is there a way to record in stereo? SO that each leg of the call is on a 
> separate channel? Sometimes if one sides recorded audio is not balanced it 
> can then easily rectified in the recording but normalizing the one channel. 
> Also if both voices are very similar it makes it easy to decipher which leg 
> was the one talking.

There is no setting for this, the recording functionality is hardcodes in 
underlying C libraries.

> 
> - is there a way to set blink to auto record all calls? But still able to 
> turn it off using the record toggle button?

Blink Pro for Mac has auto-recording in the advanced setting of each account.

> 
> - any way to start the recording when the call is initiated, not when the 
> call is connected? I need to record the lead time delay and ringing before 
> the call is answered, we use this information in our analysis of call made.

This is not possible because there is no media yet at that point in time.

> 
> Thanks,
> 
> Mike
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Unable to install Blink from repository

[Adrian Georgescu]

Can you paste the logs


> On 14 Oct 2019, at 18:34, David Keller  wrote:
> 
> Could you please update the repository (at ag-projects.com/debian)
> 
> It won't install on latest stable Debian release (which is Buster) because of 
> broken dependencies.
> 
> Thanks and best regards,
> Dave
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Recommended system specs for Windows

[Adrian Georgescu]

You need a computer with audio input and output. Most built-in microphones in 
cheap computers are of bad quality. We recommend a good quality headset if you 
want to benefit of high quality audio.

Regards,
Adrian


> On 9 Oct 2019, at 10:45, Jared Ritchey  wrote:
> 
> Hello,
> 
> Is there a list of recommended system hardware for Windows?
> 
> -  Jared
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> 


signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Change Folder for Blink Recording

[Adrian Georgescu]

There is no exposed settings for this.

Adrian

> On 1 Oct 2019, at 13:13, Jessirel Cubio  wrote:
> 
> Hi,
> 
> Is it possible to change the default directory for the blink recording?
> 
> Thanks
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> https://lists.ag-projects.com/mailman/listinfo/blink
> 



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Screen sharing on a Windows PC

[Adrian Georgescu]

Is available on both, but not interoperable between Mac and Windows,

Adrian

> On 1 Oct 2019, at 11:35, Jared Ritchey  > wrote:
> 
> Hello,
> 
> Is screen sharing available for Windows computers? Or only Macs? Thanks for 
> any advice! We are having trouble getting screen sharing working on Windows 
> PCs.
> 
> -  Jared Ritchey
> ___
> Blink mailing list
> Blink@lists.ag-projects.com 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> 


signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Blink for Linux hangs on second call when using PulseAudio input device

[Adrian Georgescu]

This patch it made in to trunk and will be available with next Blink release!

Adrian

> On 15 Jul 2019, at 14:48, juleg...@gmail.com wrote:
> 
> Hi
> 
> I just like to confirm.
> Following Tom's advise, I recompiled python-sipsimple with
> 'snd_pcm_drop (pcm)' instead of 'snd_pcm_drain (pcm)' in alsa_dev.c and it 
> works all fine now and the PA device doesn't hang after finishing the call.
> 
> Thanks for this solution!
> 
> Regards, Michael
> 
>> I've been looking into this and once it's hung, you can hook into the
>> thread with the highest cpu usage with gdb and it appears that
>> python-sipsimple is stuck in the alsa function `snd_pcm_drain (pcm);` (
>> https://github.com/AGProjects/python-sipsimple/blob/master/deps/pjsip/pjmedia/src/pjmedia-audiodev/alsa_dev.c#L619
>>  
>> ).
>> I'm not sure if it's the right approach, but the documentation for that
>> function says:
>> 
>> "For stopping the PCM stream immediately, use ::snd_pcm_drop() instead."
>> 
>> 
>> Switching to that function fixes things for me.
>> Michael,
>> 
>> Another option is to tell PA to ignore certain devices.  I use this for a
>> few devices I never want in PA:
>> 
>> $ cat /etc/udev/rules.d/89-pulseaudio-usb.rules
>> > # Ignore SignaLink
>> 
>> ATTRS{idVendor}=="08bb", ATTRS{idProduct}=="2904", ENV{PULSE_IGNORE}="1"
>> > # Ignore Alesis iO|2
>> > ATTRS{idVendor}=="13b2", ATTRS{idProduct}=="0008", ENV{PULSE_IGNORE}="1"
>> 
>> 
>> The ENV{PULSE_IGNORE}="1" is the key to PA leaving it alone.
>> 
>> The vendor and product ID aren't hard to find.  For example, for the old
>> Alesis I use only in JACK:
>> 
>> $ lsusb | grep Alesis
>> > Bus 002 Device 002: ID 13b2:0008 Alesis
>> 
>> 
>> This is on Arch although I suspect it will work the same regardless of the
>> specific PA implementation.
>> 
>> If PA is ignoring your USB headset, you should be able to use it directly
>> in Blink by selecting it in the devices drop-down menus, no?  I don't know
>> that you'll need to go crazy with the loopback device.  In my case I need
>> it only because of the JACK involvement.
>> 
>> 
>> - Jeff
>> 
>> 
>> 
>> 
>> On Sat, May 11, 2019 at 8:15 AM juleg.ch at gmail.com 
>>  > gmail.com >
>> wrote:
>> 
>> > Jeff,
>> >
>> > Thanks a lot for your reply.
>> >
>> > My problems occur while using a USB headset device.
>> > So I can imagine, that with the help of your asound.conf file as a
>> > template, I should be able to configure 2 alsa loopback devices for
>> > exclusiv use in Blink.
>> >
>> > As a temporary workaround for the moment, I disabled the USB audio via
>> > pavucontrol configuration altogether, so it is only seen and selected by
>> > Blink and doesn't pop up in PA at all while accepting or doing phone calls.
>> >
>> > Regards,
>> > Michael
>> >
>> > Date: Tue, 7 May 2019 11:07:17 -0400
>> > From: Jeff Pyle > > > > > >
>> > To: Blink Support Forum > > > > > lists.ag-projects.com 
>> > >
>> > Subject: Re: [Blink] Blink for Linux hangs on second call when using
>> >PulseAudio input device
>> > Message-ID:
>> >> > > 
>> > > > >
>> > Content-Type: text/plain; charset="utf-8"
>> >
>> > Michael,
>> >
>> > My case is likely different, as my goal was to use a JACK-connected audio
>> > device in Blink.  JACK and PA play reasonably well together, but since PA
>> > and Blink don't sometimes, I created an ALSA loopback, integrated it into
>> > my JACK flow, and use it exclusively for connectivity with Blink.  I've
>> > attached my asound.conf.
>> >
>> > Once I have JACK started, I run a script called loop2jack, also attached.
>> > This creates two JACK devices, cloop and ploop, the "capture" loop and
>> > "playback" loop devices, respectively.  In Blink the devices appear as
>> > "Loopback, Loopback PCM" for input and output devices.  Blink does support
>> > JACK natively, but Blink's capture and playback connectors only appear when
>> > the audio device is actively in use.  I don't have any auto-patching
>> > mechanisms running in my JACK environment so this wasn't compatible.  I
>> > find the ALSA loopback approach very good for my needs.
>> >
>> > I also have trouble keeping the loopback PCM device playback level at 100%
>> > in alsamixer.  I haven't spent much time on it.
>> >
>> > All that said...  if you can configure Blink to use your audio device with
>> > ALSA directly, rather than PA, you should be okay, no?  PA will release it,
>> > and you won't have any of the Blink+PA problems we've seen.
>> >
>> 

Re: [Blink] problem with install blink

[Adrian Georgescu]

Ubuntu Bionic is version 18:04, not 16.04.

Adrian

> On 4 Jul 2019, at 16:08, Руслан Рословцев  wrote:
> 
> Hello. I have Ubuntu 16.04 LTS.
> I'm trying to install the program on this instructions:
> http://projects.ag-projects.com/projects/documentation/wiki/Repositories 
> 
> 
> sudo wget -O /etc/apt/trusted.gpg.d/agp-debian-key.gpg 
> http://download.ag-projects.com/agp-debian-key.gpg 
> 
> 
> Add the following lines to /etc/apt/sources.list
> deb http://ag-projects.com/ubuntu  bionic 
> main
> deb-src http://ag-projects.com/ubuntu  bionic 
> main
> 
> sudo apt-get update
> sudo apt-get install blink
> 
> And I have a problem on screenshot.
> 
> Whats wrong with him? Python is install. May be need more newer version 
> Ubuntu?
> ___
> Blink mailing list
> Blink@lists.ag-projects.com 
> https://lists.ag-projects.com/mailman/listinfo/blink 
> 


signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
https://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Blink Lite 4.6.0 Crashing on Mac OS 10.12.6

[Adrian Georgescu]

Without any logs to look at, I can imagine that somehow the application image 
is corrupted. Try remove the app and re-install it again from the store.

Adrian

> On 14 May 2018, at 09:59, Ronette Johnson  wrote:
> 
> Hi,
> 
> 
> I work in our IT dept and I am having an issue with Blink Lite that we have 
> purchased some years ago. Blink lite does not open, it crashes right away 
> upon start up. This is a brand new install on Sierra Mac OS 10.12.6 . I have 
> recently installed Blink lite on other computers at our company with the same 
> OS and different OS’s older and High Sierra with no problem. It’s just this 
> one Mac machine that it keeps crashing on. I’ve created a new profile on the 
> same computer and it still crashes on the computer. Also, I have rebooted the 
> computer several times and uninstalled and reinstalled multiple times. Still  
> the same issue when I click, it jumps as if it will open and then quickly 
> disappears and does not open. Any suggestions? Any information is greatly 
> appreciated.
> 
> 
> 
> Thank you
> Ronette Johnson
> Tech Support
> Endless Pools
> rjohn...@endlesspools.com 
> 
> 
> 
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Automatic accept calls

[Adrian Georgescu]

Mac version has auto-answer, Linux and Windows not.

Adrian

> On 3 Jun 2018, at 12:36, Diego Junior  wrote:
> 
> Dear
> 
> I am Diego Junior (account: diego.jun...@sip2sip.info).
> 
> I need the following help:
> Can you automatically receive audio calls from Blink? I have a remote machine 
> logged in with another sip2sip.info account, but I can not establish a call 
> without human action to "accept" the call on this remote machine.
> 
> It would be a way for me to make the call and another user to accept 
> automatically without human action.
> 
> This would be a common long-running audio call. Note: it is not an electronic 
> secretary.
> 
> 
> Att.
> Diego Junior
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Blink for Mobile SIP2SIP confusion...

[Adrian Georgescu]

The desktop version works with any sip address

The mobile version works indeed only with sip2isp.info 


> On 13 Oct 2018, at 06:05, Daniel Harris  wrote:
> 
> On your website at http://icanblink.com you say:
> 
>> Blink for Mobile is available for iOS and Android, this version only works 
>> with SIP2SIP.
> 
> 
> But in the App Store at 
> https://itunes.apple.com/us/app/blink-for-mobile/id1100356948 you say:
> 
>> You can call and receive calls to and from any publicly routable SIP address 
>> in the world, not just sip2sip.info domain.
> 
> 
> So, which is it?! ;-)
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
> 



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

[Blink] New SIP SIMPLE client SDK release 3.2.0

[Adrian Georgescu]

The software is packaged in .deb format for the latest Ubuntu and Debian Linux 
versions and available as source code at:

https://sipsimpleclient.org/installation/

Changelog

python-sipsimple (3.2.0)

  * Shutdown already started subsystems if application is stopped early
  * Fixed a bug that would hang the application if the engine fails to start
  * Stop the engine thread on engine failure
  * Reset encryption type when the RTP stream ends
  * Use a named logger for sipsimple logging
  * Use modern syntax for catching exception
  * Removed underscore prefix from argument name
  * Fixed typo in notification name
  * Order imports alphabetically
  * Import statement cleanup
  * Removed obsolete build option
  * [core] Removed unnecessary local variables
  * [core] Removed test for failures that cannot happen
  * [core] Fixed the transport being used within an incoming SUBSCRIBE dialog
  * [core] Removed unnecessary semicolon at the end of statement
  * [core] Added missing cdef statement
  * [core] Minimize releasing/acquiring the GIL
  * [core] Propagate exceptions
  * [core] Undo setting incoming subscription transport as it conflicts
  * [core] Removed unused code from setting transport
  * Use the new logging API in python-application 2.5.0
  * Fixed compiling with newer ffmpeg
  * Removed duplicate dependency
  * Update macOS installation instructions
  * Added deb building instructions for Rasberry Pi
  * Removed copyright notices from install files
  * Updated copyright years
  * Replaced deprecated debian package priority
  * Switched from dbg package to dbgsym package

--
Adrian



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Cluttered connection

[Adrian Georgescu]

Hi Mike,

Some logs (Menu Window -> Logs) or snapshots may help us better understand what 
is going on. You can mail them directly to supp...@ag-projects.com 


This could be caused by a codec incompatibility. You can find out which codec 
you use by pressing the i button in the audio drawer for the active call, an 
info panel opens. In the same panel, you can see also network information like 
packet loss, round trip time, those may help to pin point the problem as well.

If the problem is the codec, what you can try is to change the codec 
preferences. You will find the codec list in

Preferences -> Advanced -> RTP media

Regards,
Adrian


> On 14 Aug 2018, at 06:29, Mike Battistella  
> wrote:
> 
> Hello,
> 
> I’m experiencing very bad connections with Blink Pro to the providers 
> Sipgate, Personal-VOIP, Peoplefon (CH).
> If I use the Telefon App on my mac there are no problems (also with my 
> physical SIP phone).
> 
> There is not only latency, but mainly the voice is cluttered (many breaks in 
> the audio for me and the other called person).
> 
> 
> What can I do?
> 
> Regards,
> Mike Battistella
> 
> 
> Mike Battistella
> B.A. Digital Media (FH)
> 
> ---
> Mike Battistella // Interactive Media
> Full-Service Digital Agentur & Beratung
> - Design-Thinking Coaching | Innovations-Workshops
> - Web- und Mobile-Anwendungen | Websites & E-Commerce
> - User-Experience, Interaction & Interface Design | Film & Animationen
> 
> https://interactive.battistella.biz/ 
> https://rethinx.consulting/ 
> 
> Weideliguet 6 | 8598 Bottighofen | Schweiz
> Gottlieb-Daimler-Str. 5 | 78467 Konstanz | Deutschland
> 
> Telefon (CH) +41 44 552 01 55
> Telefon (DE) +49 7531 350 49 58
> -
> Mobile (CH) +41 77 418 43 58
> Mobile (DE) +49 175 373 14 48
> 
> Digital topics blog: http://reality-and-a-half.multiversum.com/ 
> 
> 
> * Testen Sie unser Online-Moodboard Ledavio: www.ledavio.design 
>  *
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Blink Pro crashes on macOS High Sierra (10.13) GM

[Adrian Georgescu]

The answer may be in the Logs window. Menu Window -> Logs -> SIP

If you enable the logs and paste them from that window, we can see what happens

Adrian



> On 4 Jul 2018, at 19:05, Will Falconer, DVM  
> wrote:
> 
> Hi Adrian,
> 
> Just switched over to High Sierra and discovered Blink Pro is not working.
> 
> Here’s what I see:
> 
> 
> 
> Luckily, incoming calls roll over to my cell phone but voice mail is missing 
> and I can use my usual mic/ headsets with the cell.
> 
> Any fix I might try?
> 
> Thanks kindly.
> 
> Will
> 
> 
> Dr. Will Falconer
> Certified Veterinary Homeopath
> Vital Animal | The Natural Path
> Austin, TX
> (512) 288-5400
> drfalco...@vitalanimal.com 
> 
> Changing the World, One Vital Animal at a Time:
> http://VitalAnimal.com 
> 
> Sign on here for your free membership and Vital Animal News:
> Vital Animal Pack! 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Chat Sessions

[Adrian Georgescu]

In the Mac version, check Preferences- > Chat -> Disabled

Adrian

> On 27 Apr 2018, at 10:46, James Shaw  
> wrote:
> 
> Hello Blink,
> 
> Is it possible to disable the chat feature so it’s not available to certain 
> or all users?
> 
> Kind regards,
> 
> James.
> 
> 
> James Shaw | HomeShield Direct Ltd
> Compliance Agent
> 
> HomeShield Direct Ltd
> Heversham House, 20-22 Boundary Road, Hove, BN3 4EF
> 0800 023 6178 | www.homeshielddirect.co.uk 
>  | james.s...@homeshielddirect.co.uk 
> 
> 
> Disclaimer: This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they are 
> addressed. If you have received this email
> in error please notify the system manager. This message contains confidential 
> information and is intended only for the individual named. If you are not the 
> named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender 
> immediately by e-mail if you have received this e-mail by mistake and delete 
> this e-mail from your system. If you are not
> the intended recipient you are notified that disclosing, copying, 
> distributing or taking any action in reliance on the contents of this 
> information is strictly prohibited.
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com 
> http://lists.ag-projects.com/mailman/listinfo/blink 
> 


signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] No module named application

[Adrian Georgescu]

These are not direct Blink dependencies but dependencies of sipsimpleclient, 
see here all packages your may need if you build from scratch.

http://sipsimpleclient.org/projects/sipsimpleclient/wiki/SipInstallation 
<http://sipsimpleclient.org/projects/sipsimpleclient/wiki/SipInstallation>

Adrian


> On 24 Jan 2018, at 19:19, Robert Dyck <rob.d...@telus.net> wrote:
> 
> Well the distro had such a package and I got a little further. Now I need 
> eventlib which is not
> available in the distro. So I tried pip install eventlib.
> 
> [rdyck@blacky ~]$ pip install eventlib
> Collecting eventlib
>  Downloading eventlib-0.1.5.tar.gz
> Collecting celery>=3.0.0 (from eventlib)
>  Downloading celery-4.1.0-py2.py3-none-any.whl (400kB)
>100% || 409kB 1.2MB/s
> Collecting logan==0.5.0 (from eventlib)
>  Downloading logan-0.5.0.tar.gz
> Collecting redis>=2.7.1 (from eventlib)
>  Downloading redis-2.10.6-py2.py3-none-any.whl (64kB)
>100% || 71kB 3.0MB/s
> Collecting ejson (from eventlib)
>  Downloading ejson-0.1.6.tar.gz
> Collecting Django (from eventlib)
>  Downloading Django-2.0.tar.gz (8.0MB)
>100% || 8.0MB 125kB/s
>Complete output from command python setup.py egg_info:
>Traceback (most recent call last):
>  File "", line 1, in 
>  File "/tmp/pip-build-yhNpJK/Django/setup.py", line 32, in 
>version = __import__('django').get_version()
>  File "django/__init__.py", line 1, in 
>from django.utils.version import get_version
>  File "django/utils/version.py", line 61, in 
>    @functools.lru_cache()
>AttributeError: 'module' object has no attribute 'lru_cache'
> 
> On Wednesday, January 24, 2018 6:06:19 AM PST Adrian Georgescu wrote:
> > If you have no package for your distro you can install it manually by using
> >
> > pip install python-application
> >
> > Or
> >
> > easy_install python-application
> >
> >
> > Adrian
> >
> > > On 24 Jan 2018, at 05:00, Robert Dyck <rob.d...@telus.net 
> > > <mailto:rob.d...@telus.net>> wrote:
> > >
> > > I have downloaded the blink source and I believe I correctly compiled it,
> > > after going through dependency hell. When I try to run it I get the
> > > following.>
> > > Traceback (most recent call last):
> > >  File "/usr/bin/blink", line 67, in 
> > >
> > >from blink import Blink
> > >
> > >  File "/usr/lib64/python2.7/site-packages/blink/__init__.py", line 8, in
> > >  >
> > >from application import log
> > >
> > > ImportError: No module named application
> > > I have compiled numerous applications in the past but not with Python. I
> > > am pretty much ignorant of Python. Please help me find the module called
> > > "application". There does not seem to be any file called application.py.
> > >
> > > Thanks in advance for taking the time.
> > > Rob
> > > ___
> > > Blink mailing list
> > > Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com> 
> > > <mailto:Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>>
> > > http://lists.ag-projects.com/mailman/listinfo/blink 
> > > <http://lists.ag-projects.com/mailman/listinfo/blink>
> > > <http://lists.ag-projects.com/mailman/listinfo/blink 
> > > <http://lists.ag-projects.com/mailman/listinfo/blink>>
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
> http://lists.ag-projects.com/mailman/listinfo/blink 
> <http://lists.ag-projects.com/mailman/listinfo/blink>


signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] "beep beep" every 45 seconds

[Adrian Georgescu]

I never heard or saw such thing before. If you wish, we can do a screen sharing 
session to beter understand what the problem is.

You can mail me directly.

Adrian




> On 2 Oct 2017, at 17:48, Oliver Wagner <oliver.wag...@qutico.de> wrote:
> 
> Hello Adrian,
> I noticed this only on IDLE. This "beep beep" is very annoying and I always 
> restart Blink to stop it. Because of this I don't know if this continues 
> while making a phone call. But next time I will try it.
> 
> Oli
> 
> Adrian Georgescu schrieb:
>> Is this during the call or when idle?
>> 
>> Adrian
>> 
>>> On 2 Oct 2017, at 10:16, Oliver Wagner <oli...@wagner-www.de 
>>> <mailto:oli...@wagner-www.de>> wrote:
>>> 
>>> Hello,
>>> 
>>> if blink is running all 45 seconds a "beep beep" is played. After 
>>> terminating "Blink Pro" the "beep beep" is gone. Restarting "Blink Pro" 
>>> there is no "beep beep" ... but after some time the "beep beep" comes back 
>>> and it stops only with terminating "Blink Pro".
>>> 
>>> The "beep beep" is played via bluetooth headset and with default internal 
>>> speaker (if no bluetooth headset ist connected).
>>> 
>>> It would be great if I can disable this "beep beep" ... can you help?
>>> 
>>> Best regards
>>> 
>>> Oli
>>> 
>>> 
>>> 
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>>> http://lists.ag-projects.com/mailman/listinfo/blink 
>>> <http://lists.ag-projects.com/mailman/listinfo/blink>
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>> http://lists.ag-projects.com/mailman/listinfo/blink 
>> <http://lists.ag-projects.com/mailman/listinfo/blink>
> 
> --
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] "beep beep" every 45 seconds

[Adrian Georgescu]

Is this during the call or when idle?

Adrian

> On 2 Oct 2017, at 10:16, Oliver Wagner  wrote:
> 
> Hello,
> 
> if blink is running all 45 seconds a "beep beep" is played. After terminating 
> "Blink Pro" the "beep beep" is gone. Restarting "Blink Pro" there is no "beep 
> beep" ... but after some time the "beep beep" comes back and it stops only 
> with terminating "Blink Pro".
> 
> The "beep beep" is played via bluetooth headset and with default internal 
> speaker (if no bluetooth headset ist connected).
> 
> It would be great if I can disable this "beep beep" ... can you help?
> 
> Best regards
> 
> Oli
> 
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

[Blink] Blink for macOS High Sierra

[Adrian Georgescu]

We have pushed a new Mac version to Mac App Store that solves the compatibility 
with macOS High Sierra.

Once Apple approves it, it will be available for download.

Regards,
Adrian

___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Blink Pro crashes on macOS High Sierra (10.13) GM

[Adrian Georgescu]

I see you run OSX High Sierra.

We don’t have Blink running there yet.

Adrian


> On 19 Sep 2017, at 18:01, Sven Willert <s...@willert.net> wrote:
> 
> Hi,
> 
> It’s a 3,1 GHz Intel Core i7 (MacBook Pro (15 Zoll, 2017)).
> 
> Sven
> 
>> Am 19.09.2017 um 22:59 schrieb Adrian Georgescu <a...@ag-projects.com 
>> <mailto:a...@ag-projects.com>>:
>> 
>> Hi Sven,
>> 
>> What processor runs in your machine?
>> 
>> Adrian
>> 
>> 
>>> On 19 Sep 2017, at 17:22, Sven Willert <s...@willert.net 
>>> <mailto:s...@willert.net>> wrote:
>>> 
>>> Hi,
>>> 
>>> Blink Pro can not start on macOS High Sierra (10.13) GM.
>>> 
>>> Crashed Thread:0  Dispatch queue: com.apple.main-thread
>>> 
>>> Exception Type:EXC_CRASH (SIGABRT)
>>> Exception Codes:   0x, 0x
>>> Exception Note:EXC_CORPSE_NOTIFY
>>> 
>>> Application Specific Information:
>>> *** Terminating app due to uncaught exception 
>>> 'NSInternalInconsistencyException', reason: 
>>> '/Users/adigeo/work/blink/main.m:41 main() PyRun_SimpleFile failed with 
>>> file '/Applications/Blink Pro.app/Contents/Resources/Main.py'.  See console 
>>> for errors.'
>>> terminating with uncaught exception of type NSException
>>> abort() called
>>> 
>>> Please advice.
>>> 
>>> Best regards,
>>> Sven
>>> 
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com <mailto:Blink@lists.ag-projects.com>
>>> http://lists.ag-projects.com/mailman/listinfo/blink
>>> 
>> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] MAC OS Issues

[Adrian Georgescu]

We need to see the logs and SIP trace of the call(s) in question in order to 
determine where the problem is.

Adrian


> On 9 May 2017, at 13:44, Jake Taylor <jake.tay...@ra-is.co.uk> wrote:
> 
> Hi Adrian,
> 
> When are receiving a delay when someone with blink pro on Sierra answers a 
> call, it carries on calling although clicked answer, for around 8 seconds 
> until it answers.. during this time you cannot do anything else via blink and 
> it also continues to call on anyone else's phones that are in the same ring 
> group, however they cannot answer it due to it being answer on the sierra 
> users.
> 
> Hope that is clear.
> 
> Thanks
> 
> Jake
> 
> On 9 May 2017, at 17:39, Adrian Georgescu 
> <a...@ag-projects.com<mailto:a...@ag-projects.com>> wrote:
> 
> What issues do you actually have?
> 
> Adrian
> 
> On 9 May 2017, at 08:26, Jake Taylor 
> <jake.tay...@ra-is.co.uk<mailto:jake.tay...@ra-is.co.uk>> wrote:
> 
> Hi,
> 
> Just curious if there will be any bug fixes for the Blink issues with Mac OS 
> Sierra, that anyone knows of?
> 
> Having big issues with it.
> 
> Thanks!
> 
> Jake
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com<mailto:Blink@lists.ag-projects.com>
> http://lists.ag-projects.com/mailman/listinfo/blink
> 
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com<mailto:Blink@lists.ag-projects.com>
> http://lists.ag-projects.com/mailman/listinfo/blink
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
> 



signature.asc
Description: Message signed with OpenPGP
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Blink on macOS Sierra

[Adrian Georgescu]

The sad thing is that we don’t have an older version, nor a way to rebuild it 
and push it through app store.

Adrian

> On 11 Apr 2017, at 15:02, Daniel Harris <dan...@daha.co.uk> wrote:
> 
> Until you solve this would you be able to do another version compiled with 
> older / not so latest development tools that will enable your software to run 
> on older hardware? Cheers!
> 
>> On 30 Mar 2017, at 15:52, Daniel Harris <dan...@daha.co.uk> wrote:
>> 
>> Wow! That's a great shame and has effectively killed your product. Wow!
>> 
>> I hope you are trying to get Apple to fix this?!
>> 
>> I'm not sure if it is related but Night Shift (introduced in macOS 10.12.4) 
>> is locked out on older Apple hardware. But it can be got around by editing a 
>> few files that arbitrarily state which hardware it can run on. I wonder if 
>> there is some similar for Blink?!
>> https://pikeralpha.wordpress.com/2017/01/30/4398/
>> 
>> Good luck, Have fun!
>> 
>> Cheers Daniel
>> 
>>> On 30 Mar 2017, at 14:59, Adrian Georgescu <a...@ag-projects.com> wrote:
>>> 
>>> Unfortunately we cannot fix this.
>>> 
>>> The software compiled with the latest development tools from Apple does not 
>>> seem to work on any OS version on some older Apple hardware. 
>>> 
>>> Adrian
>>> 
>>> 
>>>> On 30 Mar 2017, at 10:30, Daniel Harris <dan...@daha.co.uk> wrote:
>>>> 
>>>> This is happening for me also but also on 10.11.6 (MacBook Pro (15-inch, 
>>>> Late 2008)) as well as 10.12.4 (Mac Pro (Mid 2010)). Both are version 
>>>> 4.5.1 (27049) updated from the App Store. Any ideas when this will be 
>>>> fixed? Cheers Daniel
>>>> 
>>>>> On 27 Jul 2016, at 18:04, ja...@jtk.com.pl <ja...@jtk.com.pl> wrote:
>>>>> 
>>>>> Blink on macOS Sierra crashes at start. Any plans to fix it soon?
>>>>> 
>>>>> Pozdrawiam/Regards
>>>>> 
>>>>> JT
>>>>> 
>>>>> 
>>>>> 
>>>>> ___
>>>>> Blink mailing list
>>>>> Blink@lists.ag-projects.com
>>>>> http://lists.ag-projects.com/mailman/listinfo/blink
>>>> 
>>>> ___
>>>> Blink mailing list
>>>> Blink@lists.ag-projects.com
>>>> http://lists.ag-projects.com/mailman/listinfo/blink
>>>> 
>>> 
>>> ___
>>> Blink mailing list
>>> Blink@lists.ag-projects.com
>>> http://lists.ag-projects.com/mailman/listinfo/blink
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> http://lists.ag-projects.com/mailman/listinfo/blink
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Blink on macOS Sierra

[Adrian Georgescu]

Unfortunately we cannot fix this.

The software compiled with the latest development tools from Apple does not 
seem to work on any OS version on some older Apple hardware. 

Adrian


> On 30 Mar 2017, at 10:30, Daniel Harris  wrote:
> 
> This is happening for me also but also on 10.11.6 (MacBook Pro (15-inch, Late 
> 2008)) as well as 10.12.4 (Mac Pro (Mid 2010)). Both are version 4.5.1 
> (27049) updated from the App Store. Any ideas when this will be fixed? Cheers 
> Daniel
> 
>> On 27 Jul 2016, at 18:04, ja...@jtk.com.pl  wrote:
>> 
>> Blink on macOS Sierra crashes at start. Any plans to fix it soon?
>> 
>> Pozdrawiam/Regards
>> 
>> JT
>> 
>> 
>> 
>> ___
>> Blink mailing list
>> Blink@lists.ag-projects.com
>> http://lists.ag-projects.com/mailman/listinfo/blink
> 
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] Google Contacts Function Support

[Adrian Georgescu]

The limitation is in the Google Contacts API. They have implemented some quota 
mechanism per application with values that make no sense in real life.  

We are trying to raise this quota its google, and we are still waiting for 
answers from them.

Regards,
Adrian


> On 12 Jan 2017, at 12:19, Alex - Gmail  wrote:
> 
> Guys, 
>  
> I saw that Blik received an update that enables google contacts function 
> again. I ran the application update, but only a small part of the contacts 
> was loaded. I have many contacts in google contacts and would like to know if 
> there is any limitation, number of contacts for example.
>  
> How to load the full list of contacts ?
>  
> Thanks in advance.
>  
> Alex
> ___
> Blink mailing list
> Blink@lists.ag-projects.com 
> http://lists.ag-projects.com/mailman/listinfo/blink 
> 
___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink

Re: [Blink] SIP2SIP with physical VOiP phone

[Adrian Georgescu]

> On 10 Jan 2017, at 16:31, Mike Nagie  wrote:
> 
> Hello,
> I'd like to know whether SIP2SIP accounts fully work with IP phones.

Yes. 

> 
> In my case with GrandStream GXP1625. Could I connect to the server?

I don’t know the model, so while mostly all handphones typically work fine 
nowadays, is impossible to guess if a particular device will work.


> Could I establish an encrypted connection between GXP1625 and Blink?

It depends what encryption your hard phone uses. Blink supports SDES (server 
has access to the key) and ZRTP (end-to-end encryption and key exchange). I 
doubt the hard-phones implement ZRTP, typically they use SEDS which is broken 
by design.

Practically if you want encryption where no intermediaries can listen in, you 
must use ZRTP.

> (I would say yes, Sip is Sip, but I couldn't connect to the Ekiga server 
> with Blink.

Is easy to see why, just open the Logs window an you can see what is wrong.


> That's just a sidenote, I don't want to connect to the Ekiga 
> server with Blink at the very moment, I just don't understand how SIP 
> works. There's a magical fog around this thing. I was kind of curious so 
> I tried to connect to the Ekiga.net server again. It still doesn't 
> connect. It says Registration Failed. While the software Ekiga can 
> connect to it's own server. It's probably their fault and not yours. End 
> of sidenote)
> 
> Thanks a lot!
> ___
> Blink mailing list
> Blink@lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
> 

___
Blink mailing list
Blink@lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink