<!-- 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, ...)
- [X] 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
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [ X ] 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
<!-- Describe your changes in detail -->
Hello, what we've done in these commits:
- ported corresponding functions from MI fifo to RPC (see cr_rpc.c)
- used the helper functions from MI, in RPC (see cr_rpc_helper.c)
- updated doc
- deleted MI fifo files
Hopefully nobody uses the MI commands for this module. Please let me know otherwise, in order to delete the last commit of this PR.
Thanks,
Stefan
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2225
-- Commit Summary --
* carrierroute: organize and add new rpc commands
* carrierroute: add new rpc commands
* carrierroute: update doc for the new rpc commands
* carrierroute: remove mi fifo files
-- File Changes --
M src/modules/carrierroute/carrierroute.c (50)
D src/modules/carrierroute/cr_fifo.c (1243)
A src/modules/carrierroute/cr_rpc.c (369)
R src/modules/carrierroute/cr_rpc.h (79)
A src/modules/carrierroute/cr_rpc_helper.c (589)
M src/modules/carrierroute/doc/carrierroute_db.xml (2)
M src/modules/carrierroute/doc/rpc.xml (129)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2225.patchhttps://github.com/kamailio/kamailio/pull/2225.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/2225
Module: kamailio
Branch: master
Commit: 3d28b4c3fcb2131c0f360487b0d233ed93388aac
URL: https://github.com/kamailio/kamailio/commit/3d28b4c3fcb2131c0f360487b0d233e…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2020-02-23T12:31:14+01:00
modules: readme files regenerated - rtpengine ... [skip ci]
---
Modified: src/modules/rtpengine/README
Modified: src/modules/rtpproxy/README
---
Diff: https://github.com/kamailio/kamailio/commit/3d28b4c3fcb2131c0f360487b0d233e…
Patch: https://github.com/kamailio/kamailio/commit/3d28b4c3fcb2131c0f360487b0d233e…
---
diff --git a/src/modules/rtpengine/README b/src/modules/rtpengine/README
index 67e7b4475f..d6ae750551 100644
--- a/src/modules/rtpengine/README
+++ b/src/modules/rtpengine/README
@@ -2210,7 +2210,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.
@@ -2229,7 +2229,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 93cb48b609..c40d15810e 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: master
Commit: b15362ec487d14b2a428dabbcce4f3de4cf1fc59
URL: https://github.com/kamailio/kamailio/commit/b15362ec487d14b2a428dabbcce4f3d…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2020-02-23T12:30:02+01:00
rtpproxy: docs updated for rtpproxy_manage()
---
Modified: src/modules/rtpproxy/doc/rtpproxy_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/b15362ec487d14b2a428dabbcce4f3d…
Patch: https://github.com/kamailio/kamailio/commit/b15362ec487d14b2a428dabbcce4f3d…
---
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>
Module: kamailio
Branch: master
Commit: bdba22bb9b573c7b32a7de45154f9159c725715f
URL: https://github.com/kamailio/kamailio/commit/bdba22bb9b573c7b32a7de45154f915…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2020-02-23T12:29:44+01:00
rtpengine: docs updated for rtpengine_manage()
---
Modified: src/modules/rtpengine/doc/rtpengine_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/bdba22bb9b573c7b32a7de45154f915…
Patch: https://github.com/kamailio/kamailio/commit/bdba22bb9b573c7b32a7de45154f915…
---
diff --git a/src/modules/rtpengine/doc/rtpengine_admin.xml b/src/modules/rtpengine/doc/rtpengine_admin.xml
index f4213f2cab..fafff2e4c5 100644
--- a/src/modules/rtpengine/doc/rtpengine_admin.xml
+++ b/src/modules/rtpengine/doc/rtpengine_admin.xml
@@ -2564,7 +2564,7 @@ rtpengine_query();
<function moreinfo="none">rtpengine_manage([flags])</function>
</title>
<para>
- 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.
</para>
@@ -2601,7 +2601,14 @@ rtpengine_query();
this function after 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).
+ 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>