Re: Alert (operation 31) was not ACKed - reconnect

[Nikos Balkanas]

Hi,

I thought it was 0 the dedault. But to be sure please set explicitly the 
value in your configuration.

BR,
Nikos
----- Original Message ----- 
From: "Hofferek Attila" <h...@soka.co.hu>
To: "Users Kannel" <users@kannel.org>
Sent: Monday, October 26, 2009 11:34 AM
Subject: Re: Alert (operation 31) was not ACKed - reconnect


Nikos Balkanas Γ­rta:
> Hi,
>
> If the connection is dead, how do you receive Alert 31?

I send message 31, but the answer from smsc is delaying more than 60
seconds.

> Otherwise, by default, if an ACK delays more than 60" the connection
is reset (both period and action are configurable in smsc group).

Thanks.

"wait-ack-expire    number

Defines what kind of action should be taken if the the ack of a message
expires. The options for this value are: 0x00 - disconnect/reconnect,
(default) 0x01 - as is now, re-queue, but this could potentially result
in the msg arriving twice 0x02 - just carry on waiting (given that the
wait-ack should never expire this is the must accurate) "

Now 0x00 or 0x01 is the default?
--
Hofferek Attila