### Description
Hello Guys I am having this issue where kamailio is receiving requests from SIPp (we are currently testing the platform and doing QA) but if we do more than 800 concurrent calls kamailio starts failing and slowing the requests, The scenario is the following:
I am sending 5000 calls at 100 CPS on TCP and I am having this route in the configuration file:
```
# Handle the calls to api
route[CALL_API] {
xlog("L_NOTICE"," Call request $var(call_request) method: $rm \n");
$var(loop_true)=1;
while ($var(loop_true)) {
if(!lua_run("call_request","$var(call_request)","$sht(token=>new_token)")) {
xlog("L_NOTICE", "SCRIPT: failed to execute lua function!\n");
}
if ($var(loop_true)){
sleep("1");
}
}
xlog("L_NOTICE", "SCRIPT: Sucess to execute lua function!\n");
}
```
So I am executing a LUA script for the requests and the API response will tell the destination of the call.
At 800 concurrent calls, I can notice SLOWLINESS in the SIPp testing tool, and then I will start receiving 408 timeouts.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
version: kamailio 5.3.8 (x86_64/linux)
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, TLS_PTHREAD_MUTEX_SHARED
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: unknown
compiled with gcc 8.3.0
```
* **Operating System**:
<!--
Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...;
Kernel details (output of `lsb_release -a` and `uname -a`)
-->
```
BUT KAMAILIO IS RUNNING IN A DOCKER CONTAINER
Linux ip-10-10-0-27.us-west-1.compute.internal 4.14.246-187.474.amzn2.x86_64 #1 SMP Tue Sep 7 21:48:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
```
This sounds like a load issue or something because I believe there's a time that it's been added every time we hit the backend and wait for the response.
any help will be appreciated
Regards
Gio
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3068
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3068(a)github.com>
- added vs_certsubject_pvname and vs_pptgrants_pvname config params
- adjusted log level of load/unload events
<!-- 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 -->
- [ ] 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)
- [ ] 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/3063
-- Commit Summary --
* stirshaken: Add PVs to allow access to x509 subject and ppt grants
-- File Changes --
M src/modules/stirshaken/doc/stirshaken_admin.xml (41)
M src/modules/stirshaken/stirshaken_mod.c (72)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3063.patchhttps://github.com/kamailio/kamailio/pull/3063.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3063
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3063(a)github.com>
- Add direction attribute to event route siptrace pseudo-variable.
<!-- 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/3061
-- Commit Summary --
* siptrace: add direction attribute to exported by module pseudo-variable
-- File Changes --
M src/modules/siptrace/siptrace.c (4)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3061.patchhttps://github.com/kamailio/kamailio/pull/3061.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3061
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3061(a)github.com>
There are various pages about the videos from Kamailio World but nothing
there about the license...
https://www.kamailio.org/w/2020/09/kamailio-world-2020-online-video-recordi…https://www.youtube.com/c/KamailioWorld/
There is a fair use doctrine that people can generally use a screenshot
or extract from copyrighted material but it is better to have some
explicit statement there.
Could anybody please clarify this and update the web page?
There are two details required:
1. Who owns the copyright? By default, the name of the volunteer(s) who
recorded the videos or if the work was done under contract, was
copyright transferred to Kamailio, Asipto or anybody else?
2. Which license? The CC BY SA 4.0 license might be a good choice
consistent with existing Kamailio licensing:
BY: must credit the original work (Kamailio or volunteer)
SA: (ShareAlike) - derivative works must also be CC BY SA (viral effect,
like the GPL used for Kamailio itself)
https://creativecommons.org/choose/
I suspect that many speakers are motivated to use their videos in some
commercial context and may not be keen to apply the No Derivatives (ND)
or Non-Commercial (NC) constraints from Creative Commons.
Thanks to those who produced and shared these works for the community.
Regards,
Daniel
--
https://danielpocock.com