Hi. I'm looking at the change to smsc_emi2.c, which now reads
if (privdata->username == NULL || cfg_get_integer(&keepalive, cfg,
octstr_imm("keepalive")) < 0)
privdata->keepalive = 0;
else
privdata->keepalive = keepalive;
As I read this, it says
"if there is no username/password, we don't do keepalive - we just set it
to 0".
Is this really the way it has to be ? I realise that keepalive
is probably meant to keep such an identifed username/password connection
open,
but it seems to also keep "our" connection "open":
- if we set keepalive to 57(that is, force it in the code...),
we get a much nicer SMSC interaction behaviour. Basically, it stays in
the same state, and processes SMS send requests right away.
