> Hello Rj!
> Monday September 26 2016 12:27, you wrote to All:
>> All,
>> Has anyone seen an error like that come up before? I'm now running
>> v1.0.6.8 for my 1:120/544 hub node and that error is coming up for
>> when just one of my downlinks attempts to connect:
>> + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: send
>> "/opt/mbse/var/bso/outbound/0000ffa0.tu3" as
"0000ffa0.tu3"
>> + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: size 210469 bytes, dated
>> Sep 20
>> 23:34:29, comp No
>> ? 26-Sep-2016 00:14:54 mbcico[24206] tty_write: hanged_up flag
>> + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: transmitter failure
>> + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: session finished, rc=108
>> + 26-Sep-2016 00:14:56 mbcico[24206] Incoming call failed (rc=108)
>> + 26-Sep-2016 00:14:56 mbcico[24206] Terminated with error 108


>> The other system uses this (which I'm not familiar with...):
>> BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1
>> Also;  depending on the intent of that error message, it may actually
>> be mis-spelled...

> If it is a system defined in your set up

  He's a downlink, so yes he's in my setup.


> try marking it as BINKD v1.0 and see what happens.

   Good point.   Changed it so that it's *not*  1.1 and then ended up with a
different error.

+ 27-Sep-2016 19:28:28 mbcico[18341] Binkp: got M_ERR "Encryption required"
+ 27-Sep-2016 19:28:28 mbcico[18341] Binkp: receiver failure
+ 27-Sep-2016 19:28:28 mbcico[18341] Binkp: session finished, rc=108
+ 27-Sep-2016 19:28:30 mbcico[18341] Incoming call failed (rc=108)


  But I can poll his system with no apparent issues...





jame

--- BBBS/Li6 v4.10 Dada-1