Hello,
we are considering to organize a small online event to compensate a bit
the cancellation of Kamailio World 2020, but mainly to discuss about
what is new around Kamailio project and RTC space.
The event was discussed among a couple developers several weeks ago,
when it was clear that the pandemic will last longer, preventing any
on-site event, and the intention to do it was also announced during the
recording of last ClueCon Weekly about Kamailio project at the beginning
of July
(https://www.kamailio.org/w/2020/07/cluecon-weekly-kamailio-updates-july-202…).
The first commit of Kamailio code was done on the 3rd of September 2001,
thus this is like the project's birthday, so a good opportunity to
celebrate that as well.
The event is planned to be 2 sessions of about 4 hours on each day, with
a few presentations per day, but try focus on open discussions about.
The goal is to keep in very informal, without any significant burden for
organizers or participants, not to add to the daily stress with work and
family in the pandemic time. It should be more like meetup style, with
no registration for participants, sessions may not be recorded and can
be done without slides. Likely we will use a (self-hosted) video
conferencing system (Jitsi) for presentations and the IRC or Matrix
channels for chatting.
The time frames we look at are 15:00-19:00 Berlin time zone (13:00-17:00
UTC) on the 2nd and the 3rd of September 2020.
The purpose of this email for now is to see the interest of the
community for such event, reply if you think it is useful to organize it
and you plan to participate.
If there is interest, then I will follow up with more details about
speakers and the structure of the event.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
Hi!
Some READMEs have grown and some lists over modparams and/or functions are long and not ordered in any logical way - new items are added below the rest and it has become a bit messy in my humble point of view.
Would anyone have anything against me starting to reorganise a few - or join in - so that they are easier to go through? Alfabetical or some logical grouping. Sorting by alfabetical will split apart groups like database table name settings, so one has to be careful ;-) Maybe we can add subheaders when there are more than X modparams?
Or shall we leave them the way they are?
/O
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [ ] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2444
-- Commit Summary --
* uac: added uac_event_callback for kemi
-- File Changes --
M src/modules/uac/uac.c (3)
M src/modules/uac/uac_send.c (40)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2444.patchhttps://github.com/kamailio/kamailio/pull/2444.diff
--
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/2444
### Description
Both doc's of master and 5.4 branches mention parameter that is missing from a code https://kamailio.org/docs/modules/5.4.x/modules/usrloc.html#usrloc.p.ka_log…
>
> 3.56. ka_logmsg (str)
> The formatted log specification to be added to the message printed when the keepalive is received and roundtrip time is computed. The log message starts with "keepalive roundtrip: %u.%06u sec - ruid [%.*s]", then concatenates the value of this parameter and the end of line.
but seems it's missing in a code
```
[root@v0p1356-dispatcher kamailio]# kamailio -c
0(18199) ERROR: <core> [core/modparam.c:165]: set_mod_param_regex(): parameter <ka_logmsg> of type <1:string> not found in module <usrloc>
0(18199) CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file kamailio-my.cfg, line 73, column 69: Can't set module parameter
ERROR: bad config file (1 errors)
0(18199) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
[root@v0p1356-dispatcher kamailio]#
```
#### Reproduction
Add
`modparam("usrloc", "ka_logmsg", " to-uri: [$tu] remote-addr: [$sas]")`
to kamailio.cfg
#### Log Messages
```
[root@v0p1356-dispatcher kamailio]# kamailio -c
0(18199) ERROR: <core> [core/modparam.c:165]: set_mod_param_regex(): parameter <ka_logmsg> of type <1:string> not found in module <usrloc>
0(18199) CRITICAL: <core> [core/cfg.y:3592]: yyerror_at(): parse error in config file kamailio-my.cfg, line 73, column 69: Can't set module parameter
ERROR: bad config file (1 errors)
0(18199) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
```
### Additional Information
```
[root@v0p1356-dispatcher kamailio]# kamailio -v
version: kamailio 5.4.0 (x86_64/linux) 6c4fce
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 6c4fce
compiled on 17:15:32 Jul 29 2020 with gcc 4.8.5
[root@v0p1356-dispatcher kamailio]#
```
* **Operating System**:
```
Centos 7
Linux v0p1356-dispatcher 3.10.0-1127.el7.x86_64 #1 SMP Tue Mar 31 23:36:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
```
--
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/2440
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [ ] Commits are split per component (core, individual modules, libs, utils, ...)
- [ ] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Small portability fixes (FreeBSD)
<!-- Describe your changes in detail -->
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2442
-- Commit Summary --
* Makefile.defs: Fixed libs option for FreeBSD
-- File Changes --
M src/Makefile.defs (5)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2442.patchhttps://github.com/kamailio/kamailio/pull/2442.diff
--
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/2442