today i noticed that stored messages are not removed from silo table after delivery and they will be delivered again target ua re-registers after an hour.
target ua receives the stored messages normally and wireshark shows that 200 ok gets back to sr fine. sr does not try to resend message, so i assume that its transaction layer accept the 200 ok.
any ideas why delivered messages stay in silo table. this has worked fine in k.
-- juha
Juha Heinanen writes:
target ua receives the stored messages normally and wireshark shows that 200 ok gets back to sr fine. sr does not try to resend message, so i assume that its transaction layer accept the 200 ok.
any ideas why delivered messages stay in silo table. this has worked fine in k.
i converted in modules_k/msilo/msilo.c m_tm_callback() function all LM_DBGs to LM_INFOs and didn't get anything to syslog when user registered and received stored message from msilo.
so apparently tm didn't call the callback at all even when sending of message request seems to have been completed ok by tm uac function.
could someone how knows the tm callback stuff please check what is going on.
-- juha
-
jh＠tutpro.com