2 Dec
2014
2 Dec
'14
5:34 a.m.
Has nobody ever seen something similar?
*Jan **Gaida*
Ingeniero Desarrollo Software C/ Marconi 3 (PTM)
28760 Tres Cantos
Spain
jan.gaida(a)grupoamper.com | www.grupoamper.com
On 24 November 2014 at 11:52, Jan Gaida <jan.gaida(a)grupoamper.com> wrote:
Hello,
We are upgrading our servers to Kamailio 4.2 and we see a lot of error
messages "Failed to delete subscription from memory".
Scenario:
This happens every time there is a Notify Timeout (408) and Kamailio tries
to delete the subscription.
Consequences:
I don't know whether the delete fails because the entry did never exist,
was already deleted or because the comparison (to_tag, callid or from_tag)
is incorrect. It would be nice to at least have some details in the log
message.
I have not noticed any consequences to general functionality.
I suspect the commit (74d73953327ad7702922b27ba37c71e3283659c3) to be
responsible for this error because it introduced some extra checks on
deletion.
Does this happen to anybody else? What may be configured incorrectly on
our system?
Kind regards
*Jan **Gaida*
Ingeniero Desarrollo Software C/ Marconi 3 (PTM)
28760 Tres Cantos
Spain
jan.gaida(a)grupoamper.com | www.grupoamper.com
--
This message and any attachments are intended only for the use of the
individual to whom they are addressed and it may contain information that
is privileged or confidential. If you have received this communication by
mistake, please notify us immediately by e-mail or telephone.The storage,
recording, use or disclosure of this e-mail and its attachments by anyone
other than the intended recipient is strictly prohibited. This message has
been verified using antivirus software; however, the sender is not
responsible for any damage to hardware or software resulting from the
presence of any virus.
Este mensaje y cualquier anexo son exclusivamente para la persona a quien
van dirigidos y pueden contener información privilegiada o confidencial. Si
usted ha recibido esta comunicación por error, le agradecemos notificarlo
de inmediato por esta misma vía o por teléfono. Está prohibida su
retención, grabación, utilización o divulgación con cualquier propósito.
Este mensaje ha sido verificado con software antivirus; sin embargo, el
remitente no se hace responsable en caso de que en éste o en los archivos
adjuntos haya presencia de algún virus que pueda generar daños en los
equipos o programas del destinatario.