[sr-dev] git:5.3:467354de: modules: readme files regenerated - modules ... [skip ci]

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,