gt; To: "Jim Van Meggelen"
> Cc: "simple-evcorr-users"
> Sent: Sunday, 24 September, 2023 04:35:50
> Subject: Re: [Simple-evcorr-users] Storing a sequence counter in a context
> hi Jim,
> many thanks for the clarification! I have a better understanding now about t
//www.clearlycore.com
>
>
> *Asterisk: The Definitive GuideFIFTH EDITION NOW AVAILABLE TO DOWNLOAD:*
> https://cdn.oreillystatic.com/pdf/Asterisk_The_Definitive_Guide.pdf
>
> --
>
> *From: *"Risto Vaarandi"
> *To: *"Jim Van Megge
:51:02
> Subject: Re: [Simple-evcorr-users] Storing a sequence counter in a context
> hi Jim,
> the solutions from my previous post were provided without knowing the root
> cause
> of the issue. If the main reason for the problem is the nature of the
> timestamps in the logs (t
://cdn.oreillystatic.com/pdf/Asterisk_The_Definitive_Guide.pdf ]
> From: "Risto Vaarandi"
> To: "Jim Van Meggelen"
> Cc: "simple-evcorr-users"
> Sent: Friday, 22 September, 2023 15:42:28
> Subject: Re: [Simple-evcorr-users] Storing a sequence counter in a context
>
hi Jim,
the solutions from my previous post were provided without knowing the root
cause of the issue. If the main reason for the problem is the nature of the
timestamps in the logs (that is, they are provided with an accuracy of a
second), I would recommend using a different logging scheme with
most syslog servers have the ability to log with subsecond accuracy, and
RFC-5424 requires it in the spec.
David Lang
___
Simple-evcorr-users mailing list
Simple-evcorr-users@lists.sourceforge.net
at 12:50 PM
To: simple-evcorr-users
Subject: [Simple-evcorr-users] Storing a sequence counter in a context
I am using SEC for an atypical use case, where rather than using log events to
correlate events for things like security events, I am using it to parse
through Asterisk logs in order
hi Jim,
let me provide some suggestions how to accomplish this task. First, you
could utilize the context based approach that you have described in your
post. In that case, the numeral that has been retrieved from the context
with the 'pop' action needs to be incremented, and you can do it with
I am using SEC for an atypical use case, where rather than using log events to
correlate events for things like security events, I am using it to parse
through Asterisk logs in order to capture a sequence of phone call events (call
comes in, auto attendant answers, user selects a digit, call is
