Hi,
I’m using
kamailio’s silo module to store offline messages in it. I
set extra_hdrs modparam to e.g. : ‘Resent-from-silo’ so the
clients get information that the message has arrived
directly (immediatelly) from the sender or it was stored
offline and comes from silo.
So the
problem is the following:
- if receiver’s
socket is broken (e.g. airplane mode on mobile) and
kamailio ‘thinks’ it is registered, server tries to send
the message
- message will
be timed out and based on config it will be stored in
silo.
- the next step
is to check if receiver is registered or not (since the
client can re-register during 30sec until the message has
timed out)
- If client is
registered, kamailio tries to send the message immediately
with m_dump().
- If the
receiver’s connection is still broken, the message will be
timed out and store in silo.
- In every
store, a new ‘resent’ extra_hdrs value is appended.
When
extra_hdrs length reaches 1024 bytes, the m_dump will fail
and it blocks the dumping of messages to the given receiver.
Question:
can extra_hdrs value be removed before store? Or what can be
the solution not to duplicate the extra_hdrs value in some
bad network situation?
Peter