<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
We're considering migrating our Kamailio-based product to Gitlab and attempted to setup a PoC of a build pipeline using Gitlab's CI capabilities. We used the same Docker build image but ran into some unexpected problems when running `make`. In short, sequence of steps can be summarised like this:
```
# 1. Generating build config files
make Q=0 cfg PREFIX=/usr/local LOCALBASE=/usr/local cfg_prefix=/tmp doc_prefix=/tmp modules_dirs=modules group_include=standard 'include_modules=inesrp inkeepalive sanity json sctp htable avpops uac uac_redirect rtimer dialog tls' 'skip_modules=stun sipt rtpproxy auth_diameter msrp qos seas siptrace sipcapture xhttp xhttp_rpc acc_diameter call_control mediaproxy topoh topos nat_traversal sms smsops jsonrpcs ss7ops ctl dmq dmq_usrloc mqueue rtpengine malloc_test mangler nosip blst app_sqlang app_jsdt auth_xkeys cfg_rpc sca sctp evrexec exec sdpops sipdump nathelper path pike'
# 2. Since MY_CUSTOM_FLAG variable is custom and is not set by default, injecting it into src/Makefile.defs
sed -i 's/C_DEFS=.*/&\n\o011 -DMY_CUSTOM_FLAG \\/' src/Makefile.defs
# 3. should succeed
make Q=0
```
At this point we expected build to succeed since it's exactly the same sequence of steps as we have been running for almost a year now, but what we got was build failures due to `MY_CUSTOM_FLAG` not being visible:
```
core/dprint.h:301:19: error: 'MY_CUSTOM_FLAG' undeclared (first use in this function)
```
(we're using patched Kamailio sources so don't get sidetracked by `MY_CUSTOM_FLAG` not being actually present in `core/dprint.h:301`)
Although clues seem to be pointing in the direction of new cloud CI environment being the culprit, we're not really sure how to approach this issue and where to start debugging from. Any suggestions?
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
For the record, [here is the Gitlab ticket](https://gitlab.com/gitlab-org/gitlab/issues/198551#note_293261974) with further reproduction details and examples of successful and failing builds
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
Running the code from this repo's `5.1` branch: `git checkout -b 5.1 origin/5.1`
* **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 `uname -a`)
-->
Official Docker `centos:7` image
--
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/2228
<!-- 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/2230
-- Commit Summary --
* update example using IP address reserved for documentation
-- File Changes --
M src/modules/rtjson/doc/rtjson_admin.xml (88)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2230.patchhttps://github.com/kamailio/kamailio/pull/2230.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/2230
Hello,
anyone in the community with Python knowledge using Postgres that can
spend a bit of time to add support in kamcli?
* https://github.com/kamailio/kamcli
It should be mainly about the content of the code corresponding to db
subcommand:
* https://github.com/kamailio/kamcli/blob/master/kamcli/commands/cmd_db.py
The target for it is to replace kamdbctl and has some command line
variants for couple of its functions, now being implemented for MySQL.
The rest of the code relies on sqlalchemy, which should have transparent
support for both mysql and postgress (even more). Testing the other
commands connecting to database with postgres would be good, though.
With more and more diversity in the default shell by main Linux/Unix
distros, we hope to be able to replace in the near future the kamctl and
kamdbctl tools, which are more like bash scripting (a few issue being
reported and fixed lately). Besides that, using python allows better
input/parameter checking/validation as well as more options for
formatted output.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com
Module: kamailio
Branch: 5.3
Commit: 467354de17c83b6c47d06e020060a0bf788c2d39
URL: https://github.com/kamailio/kamailio/commit/467354de17c83b6c47d06e020060a0b…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2020-02-25T08:46:32+01:00
modules: readme files regenerated - modules ... [skip ci]
---
Modified: src/modules/rtpengine/README
Modified: src/modules/rtpproxy/README
---
Diff: https://github.com/kamailio/kamailio/commit/467354de17c83b6c47d06e020060a0b…
Patch: https://github.com/kamailio/kamailio/commit/467354de17c83b6c47d06e020060a0b…
---
diff --git a/src/modules/rtpengine/README b/src/modules/rtpengine/README
index e1d2e082c7..29f3ac0811 100644
--- a/src/modules/rtpengine/README
+++ b/src/modules/rtpengine/README
@@ -2204,7 +2204,7 @@ rtpengine_query();
5.7. rtpengine_manage([flags])
- Manage the RTPProxy session - it combines the functionality of
+ Manage the RTPEngine session - it combines the functionality of
rtpengine_offer(), rtpengine_answer() and rtpengine_delete(), detecting
internally based on message type and method which one to execute.
@@ -2223,7 +2223,9 @@ rtpengine_query();
resuming a suspended transaction (e.g., after t_continue()),
because the context of executed route is FAILURE ROUTE (in other
words, rtpengine_manage() in the route block of t_continue() does
- the same as in failure_route).
+ the same as in failure_route; use a branch route to engage
+ rtpengine for a forwarded branch after resuming the transaction).
+ * It does nothing if used inside event_route[tm:branch-failure:...]
* If reply to INVITE with code >= 300 do rtpengine_delete()
* If reply with SDP to INVITE having code 1xx and 2xx, then do
rtpengine_answer() if the request had SDP or tm is not loaded,
diff --git a/src/modules/rtpproxy/README b/src/modules/rtpproxy/README
index ea6fe92e3a..a3bd709124 100644
--- a/src/modules/rtpproxy/README
+++ b/src/modules/rtpproxy/README
@@ -636,7 +636,9 @@ rtpproxy_destroy();
resuming a suspended transaction (e.g., after t_continue()),
because the context of executed route is FAILURE ROUTE (in other
words, rtpproxy_manage() in the route block of t_continue() does
- the same as in failure_route).
+ the same as in failure_route; use a branch route to engage
+ rtpengine for a forwarded branch after resuming the transaction).
+ * It does nothing if used inside event_route[tm:branch-failure:...]
* If reply to INVITE with code >= 300 do unforce_rtpproxy()
* If reply with SDP to INVITE having code 1xx and 2xx, then do
rtpproxy_answer() if the request had SDP or tm is not loaded,
Module: kamailio
Branch: 5.3
Commit: c8eb4f7a3e875cfb363a4167fdfa66f381b2f4ba
URL: https://github.com/kamailio/kamailio/commit/c8eb4f7a3e875cfb363a4167fdfa66f…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2020-02-25T08:40:27+01:00
rtpproxy: docs updated for rtpproxy_manage()
(cherry picked from commit b15362ec487d14b2a428dabbcce4f3de4cf1fc59)
---
Modified: src/modules/rtpproxy/doc/rtpproxy_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/c8eb4f7a3e875cfb363a4167fdfa66f…
Patch: https://github.com/kamailio/kamailio/commit/c8eb4f7a3e875cfb363a4167fdfa66f…
---
diff --git a/src/modules/rtpproxy/doc/rtpproxy_admin.xml b/src/modules/rtpproxy/doc/rtpproxy_admin.xml
index 203f280f90..536d7c6d0a 100644
--- a/src/modules/rtpproxy/doc/rtpproxy_admin.xml
+++ b/src/modules/rtpproxy/doc/rtpproxy_admin.xml
@@ -685,7 +685,14 @@ rtpproxy_destroy();
this function after resuming a suspended transaction (e.g., after
t_continue()), because the context of executed route is FAILURE
ROUTE (in other words, rtpproxy_manage() in the route block of
- t_continue() does the same as in failure_route).
+ t_continue() does the same as in failure_route; use a branch route
+ to engage rtpengine for a forwarded branch after resuming the
+ transaction).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ It does nothing if used inside event_route[tm:branch-failure:...]
</para>
</listitem>
<listitem>