Closed #1920.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1920#event-2248705927___
Kamailio (SER) - Development Mailing List
@sergey-safarov
thanks for your response.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1920#issuecomment-479346706___
Kamailio (SER)
you can try `--timestamps` options
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@sergey-safarov
thanks for your response.
we use kubectl log to get kamailo container's log
kubectl logs kamailio-665b74f766-kqjtp
logs show as below:
**10(29) DEBUG: [db_res.c:138]: db_free_result(): freeing result set at
0x7f12fa02cb88
10(29) DEBUG: [db_res.c:120]: db_new_result():
As workarroud you can start kamailio (or docker container) as service unit.
Then systemd logs will contain timestamp.
Example
```log
[root@node0 ~]# journalctl -flu kamailio-docker
-- Logs begin at Mon 2019-04-01 00:27:18 GMT. --
Apr 03 01:50:11 node0.docker.rcsnet.ru sh[17746]: 68(76) INFO:
Could we add the log timestamp by configuration?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1920#issuecomment-479282633___
Kamailio
here is the current kamailio log example.
### 0(20) INFO: sipcapture [sipcapture.c:459]: parse_table_names(): INFO: table
name:sip_capture
0(20) ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver
error: Lost connection to MySQL server at 'waiting for initial communication
Am Dienstag, 2. April 2019, 21:56:43 CEST schrieb Daniel-Constantin Mierla:
> > Am Dienstag, 2. April 2019, 09:16:37 CEST schrieb Daniel-Constantin
> > Mierla:
> > (removed sr-users)
> >
> >> I am considering to release v5.0.8 to mark the end of official
> >> maintenance for branch 5.0 on
Hello Daniel,
I tried implementing rtpengine on 5.2 and wasn't able to. I had to
downgrade to 5.0 (@henning) is aware of this.
I need to finish something before i can file a bug report, but just FYI.
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Tue,
Hello,
On 02.04.19 19:33, Henning Westerholt wrote:
> Am Dienstag, 2. April 2019, 09:16:37 CEST schrieb Daniel-Constantin Mierla:
> (removed sr-users)
>
>> I am considering to release v5.0.8 to mark the end of official
>> maintenance for branch 5.0 on Thursday, April 4. If no major regression
>>
2019-04-02 (Tue) 19:09 UTC +0200 Henning Westerholt :
> Hi Mikko,
>
> there was a mistake in introducing not valid comments to git master, and this
> needs to be fixed. Have a look to this thread:
>
> https://lists.kamailio.org/pipermail/sr-dev/2019-March/051012.html
OK, thanks. I had that
Am Montag, 1. April 2019, 19:22:13 CEST schrieb Spencer Thomason:
> I’m interested in extending the ENUM module to add support for
> draft-ietf-enum-cnam-08 CNAM queries using ENUM. I’m looking for high
> level guidance as to the best way to implement this and any feedback on
> naming of exported
Am Dienstag, 2. April 2019, 09:16:37 CEST schrieb Daniel-Constantin Mierla:
>
(removed sr-users)
> I am considering to release v5.0.8 to mark the end of official
> maintenance for branch 5.0 on Thursday, April 4. If no major regression
> will be introduced, this will be the last release from
Am Dienstag, 2. April 2019, 18:54:19 CEST schrieb Mikko Lehto:
> Was there rebase done (accidentally or on purpose) in master branch lately?
>
> I ask because typically fast forward merge just flys through without
> excitement, but not this time:
Hi Mikko,
there was a mistake in introducing not
Hi
Was there rebase done (accidentally or on purpose) in master branch lately?
I ask because typically fast forward merge just flys through without
excitement, but not this time:
---
$ git fetch
remote: Enumerating
Module: kamailio
Branch: master
Commit: ce8d36f301d7688255597a67693e47dc14448650
URL:
https://github.com/kamailio/kamailio/commit/ce8d36f301d7688255597a67693e47dc14448650
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-04-02T17:09:53+02:00
lib/srdb1: use system
@ionutionita92 - sip parsing is no longer something very expensive, if can be
avoided, it is good of course. Eventually, it can be made a modparam to control
if one wants to do it at that stage or not. Sometimes is better to have the
option of enabling a feature at the expense of some
@ionutionita92 pushed 1 commit.
a766299942d81121a9bfaee37aae66d965ae06ad siptrace: cehck trace flag for
current traced message
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
@ionutionita92 pushed 1 commit.
e9be76feff5d0f4396703f0b700ee287fcae686c siptrace: add trace_flag after it was
removed
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
ionutionita92 commented on this pull request.
> @@ -656,6 +654,11 @@ hlog("$hdr(P-MyID)", "Another one with a custom
> correlation ID");
Stateless forwarded messages (forward()) are not logged if you set the
flag, use sip_trace() inside onsend_route block.
+
+
Module: kamailio
Branch: master
Commit: 7560edb8aac6b60a5c4392db21c16e4096bf529d
URL:
https://github.com/kamailio/kamailio/commit/7560edb8aac6b60a5c4392db21c16e4096bf529d
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2019-04-02T13:45:56+02:00
lib/srdb1: use the
So, to summarize what I could see being discussed here, if the sip flag that
will allow disabling tracing is back, then it can be merged.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Ahh, ok, I missed that. Thanks!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1918#issuecomment-478947713___
Kamailio (SER) -
Closed #1918.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1918#event-2245949516___
Kamailio (SER) - Development Mailing List
backported fixes to 5.2 branch too
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1917#issuecomment-478919766___
Kamailio (SER) -
Module: kamailio
Branch: 5.2
Commit: d36634a3628ef21088b9930108a0ce845ccc38d6
URL:
https://github.com/kamailio/kamailio/commit/d36634a3628ef21088b9930108a0ce845ccc38d6
Author: Victor Seva
Committer: Victor Seva
Date: 2019-04-02T11:31:12+02:00
kamctl: regenerate db schema files
---
Modified:
Module: kamailio
Branch: 5.2
Commit: 0853dd48f40e4d91c207e5f4f01b4edeb34ef187
URL:
https://github.com/kamailio/kamailio/commit/0853dd48f40e4d91c207e5f4f01b4edeb34ef187
Author: Victor Seva
Committer: Victor Seva
Date: 2019-04-02T11:30:08+02:00
lib/srdb1: update location types for db_redis
Merged #1919 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1919#event-2245863198___
Kamailio (SER) - Development Mailing
Module: kamailio
Branch: master
Commit: ae54cf7bf6c268a3fef8834a57991601e3487d57
URL:
https://github.com/kamailio/kamailio/commit/ae54cf7bf6c268a3fef8834a57991601e3487d57
Author: Victor Seva
Committer: Victor Seva
Date: 2019-04-02T11:28:05+02:00
kamctl: regenerated db schema files
restore
Module: kamailio
Branch: master
Commit: 741f7c08a86fc101a4f0290192dcbacff1673575
URL:
https://github.com/kamailio/kamailio/commit/741f7c08a86fc101a4f0290192dcbacff1673575
Author: Victor Seva
Committer: Victor Seva
Date: 2019-04-02T11:28:05+02:00
lib/srdb1: update location types for db_redis
agranig approved this pull request.
+2, looks good to me
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I think the root cause is this that c9f2aa71b2e0d4a4f71b3da92f97306e86f93eea
was manually updated and lost at 5e0440aa27154c263fc883f3a7cb9680805af6c3
#1919 will restore the intended changes
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
manual schema changes introduced at c9f2aa71b2e0d4a4f71b3da92f97306e86f93eea
were lost by regeneration at 5e0440aa27154c263fc883f3a7cb9680805af6c3
This change sets the types changes at location for db_redis
You can view, comment on, or merge this pull request online at:
grumvalski commented on this pull request.
Thanks!
Looks fine, just a small comment on the doc.
> @@ -656,6 +654,11 @@ hlog("$hdr(P-MyID)", "Another one with a custom
> correlation ID");
Stateless forwarded messages (forward()) are not logged if you set the
flag, use
for me it looks good :-) :+1: Thank you!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/1912#issuecomment-478877949___
Kamailio (SER) -
Hello,
I am considering to release v5.0.8 to mark the end of official
maintenance for branch 5.0 on Thursday, April 4. If no major regression
will be introduced, this will be the last release from branch 5.0.
Afterwards, the stable branches maintained will be 5.1 and 5.2.
In case you have in
36 matches
Mail list logo
