Using "Kamailio in a mobile world" as a base, I have the following routes to store information about the current transaction, however, if the transaction is already cancelled registrations for the user will still trigger `ts_append`, raising an error as the htable hasn't expired yet.
Is there anyway to remove the htable entry when the original transaction cancels? Or something else that I'm missing?
Hi, the easiest thing you can do is to manually delete the entry in the htable (I suppose that you are referring to the one used in the example) when a CANCEL is received. Cheers,
Federico
On Thu, Oct 4, 2018 at 12:35 PM Dan Quinney danq@dial9.co.uk wrote:
Using "Kamailio in a mobile world" as a base, I have the following routes to store information about the current transaction, however, if the transaction is already cancelled registrations for the user will still trigger `ts_append`, raising an error as the htable hasn't expired yet.
Is there anyway to remove the htable entry when the original transaction cancels? Or something else that I'm missing? _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-
Dan Quinney -
Federico Cabiddu