Hi Douglas,
Sorry for the late reply.
The patch is already done since we are on a recent build.
This is a part of my sipx_logger.rb file.
------------
@@seqnum = 0
@@maxseqnum = (2 ** 32) - 1
@@hostname = Socket.gethostname
@@taskname = "main"
def call(severity, time, progname, msg)
sipx_severity = LOG_LEVEL_LOGGER_TO_SIPX[severity]
time_str = time.utc.strftime("%Y-%m-%dT%H:%M:%S.") << "%06dZ" % time.usec
@@seqnum = 0 if @@seqnum >= @@maxseqnum
@@seqnum = @@seqnum + 1
%Q<"#{time_str}":#{@@seqnum}:CDR:#{sipx_severity}:#{@@hostname}:#{@@taskname}:00000000:cdr:#{msg.chomp.dump}\n>
end
end
------------
So even with this patch, I still encounter these problems...
Greetings,
Henry
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Douglas Hubler
Sent: dinsdag 5 juni 2012 16:31
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] loss of connection to database
On Tue, Jun 5, 2012 at 10:06 AM, Henry Dogger <[email protected]> wrote:
> How can I check if it was the database key or the call-id? I only see
> this entries in the logging..
If you are not going to update your system, please at least check you have this
patch applied
http://forum.sipfoundry.org/index.php?t=msg&th=14928&start=0&S=ac8fb3042683be10e9b1eb099bfce0c1
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
