[Dxspider-support] Is $calltick actually being used?

[Kin]

Hi Dirk,

I'm analysing these two spots, and it seems to me that $calltick is not
actually being applied. Instead, it appears to be replaced by $dupecall.

Spot-1
1743764875^PC61^28482.0^4X4HQ^
4-Apr-2025^1107Z^CQing^ON3FZT^PA1RBZ^91.177.93.57^H27^

DXDupe::add key: X4X4HQ|ON3FZT|28482|1743764820|CQING time: 11:17:55Z (time
de llegada al nodo) 
DXDupe::add key: X4X4HQ|28482 time: 11:09:00Z
DXDupe::add key: X4X4HQ|CQING time: 11:13:00Z
DXDupe::add key: X4X4HQ time: 11:08:05Z
DXDupe::add key: XON3FZT time: 11:08:05Z
DXDupe::add key: X91.177.93.57 time: 11:08:05Z

Spot-2
1743764885^PC61^28482.0^4X4HQ^
4-Apr-2025^1107Z^CQing^ON3FZT^PA1RBZ^91.177.93.57^H27^

DXDupe::add key: X4X4HQ|ON3FZT|28482|1743764820|CQING time: 11:18:05Z (time
de llegada al nodo)
DXDupe::add key: X4X4HQ|28482 time: 11:09:00Z
DXDupe::add key: X4X4HQ|CQING time: 11:13:00Z
DXDupe::add key: X4X4HQ time: 11:08:15Z ***
DXDupe::add key: XON3FZT time: 11:08:15Z ***
DXDupe::add key: X91.177.93.57 time: 11:08:15Z ***

Note ***
Previous expiration t = 11:07:55Z = 1743764875
$main::systime = 11:08:05Z = 1743764885
Threshold ($Spot::dupecallthreshold) = 35
So: t < $main::systime + 35 -> OK
New value calculated: 1743764885 + 5 = 1743764890 = 11:08:10Z
($main::systime is equal to the arrival time of the second spot)

However, that value is not actually used. Instead, it is replaced with:
$main::systime + $dupecall = 1743764885 + 10 = 1743764895 = 11:08:15Z

The keys X4X4HQ, XON3FZT, and X91.177.93.57 are all renewed using $dupecall
(10 seconds), not $calltick.
The $calltick = 5 is effectively not applied here, because:
Even though the code computes t + $calltick, it is overwritten by:
DXDupe::add($ldupkey, $main::systime + $dupecall)

Variable values used:
$Spot::dupage 600
$Spot::dupeqrgcall 65
$Spot::dupecallinfo 305
$Spot::dupecall 10
$Spot::calltick 5
$Spot::dupecallthreshold 35

Is my understanding correct?

Kin EA3CV