sr-dev

sr-dev@lists.kamailio.org

16 participants
45399 discussions

git:master:2f35d794: tls: docs for keylog_mode and keylog_file parameters
by Daniel-Constantin Mierla 24 Jul '25

24 Jul '25

Module: kamailio Branch: master Commit: 2f35d794cf9f77d75462e32201b6db8bc51c66f1 URL: https://github.com/kamailio/kamailio/commit/2f35d794cf9f77d75462e32201b6db8… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2025-07-24T12:42:17+02:00 tls: docs for keylog_mode and keylog_file parameters --- Modified: src/modules/tls/doc/params.xml --- Diff: https://github.com/kamailio/kamailio/commit/2f35d794cf9f77d75462e32201b6db8… Patch: https://github.com/kamailio/kamailio/commit/2f35d794cf9f77d75462e32201b6db8… --- diff --git a/src/modules/tls/doc/params.xml b/src/modules/tls/doc/params.xml index 0ed54a2208a..c29c29d073c 100644 --- a/src/modules/tls/doc/params.xml +++ b/src/modules/tls/doc/params.xml @@ -1506,4 +1506,56 @@ verify_client = optional_no_ca </listitem> </itemizedlist> </section> + <section id="tls.p.keylog_mode"> + <title><varname>keylog_mode</varname> (int)</title> + <para> + Control the TLS key logging functionality, available for libssl version + greater than 1.1.0. Its value is composed from bitwise values (can be + made as sum of them): + </para> + <itemizedlist> + <listitem> + <para><emphasis>0</emphasis> - keys logging inactive</para> + </listitem> + <listitem> + <para><emphasis>1 (bit 1)</emphasis> - keys logging active</para> + </listitem> + <listitem> + <para><emphasis>2 (bit 2)</emphasis> - write keys to NOTICE log</para> + </listitem> + <listitem> + <para><emphasis>4 (bit 3)</emphasis> - write keys to file</para> + </listitem> + </itemizedlist> + <para> + The default value: 0. + </para> + <example> + <title>Set <varname>keylog_mode</varname> parameter</title> + <programlisting> +... +modparam("tls", "keylog_mode", 7) +... + </programlisting> + </example> + </section> + <section id="tls.p.keylog_file"> + <title><varname>keylog_file</varname> (str)</title> + <para> + Path to the file where to write the TLS keys. The values are appended + to the content of the file. The value 4 (bit 3) has to be set to + keylog_mode parameter. + </para> + <para> + The default value: NULL. + </para> + <example> + <title>Set <varname>keylog_file</varname> parameter</title> + <programlisting> +... +modparam("tls", "keylog_file", "/tmp/kamailio-tls-keylog.txt") +... + </programlisting> + </example> + </section> </section>

1 0

[kamailio/kamailio] outbound + loose_route: new exit code when flow token does not exist (Issue #4315)
by sergey-safarov 24 Jul '25

24 Jul '25

sergey-safarov created an issue (kamailio/kamailio#4315) ### Description Use case WebRTC client connected to Kaamilio Edge proxy. For network connectivity reasons, the flow token may no longer be valid. In this case, behavior should be described in the [RFC5626, 5.3.1 Processing Incoming Requests](https://datatracker.ietf.org/doc/html/rfc5626#section-5.3.1) > If the flow no longer exists, the proxy SHOULD send a 430 (Flow Failed) response to the request. Also [9.3 Incoming Call and Proxy Crash](https://datatracker.ietf.org/doc/html/rfc5626#section-9.3) > Bob's authoritative proxy first tries the flow to EP1, but EP1 no longer has a flow to Bob, so it responds with a 430 (Flow Failed) response. To get it working, it will be fine to use construction like ``` if (!loose_route()) { switch($rc) { case -4: sl_send_reply("403", "Flow Failed"); exit; case -2: sl_send_reply("403", "Forbidden"); exit; default: xlog("L_ERR", "in request_route\n"); sl_reply_error(); exit; } } ``` Where `loose_route` returns a new error code (`-4` for example). This error code is generated when the flow token points to not existing TCP/TLS/WSS connection. ### Expected behavior Kamailio `loose_route` allows the check of flow token validity before messages related via non-existent TCP/TLS/WSS connections. #### Actual observed behavior For now, Kamailio tries to relay messages to non-existent client connections and generate an error message like ``` 477 Unfortunately error on sending to next hop occurred (477/TM) 500 Message processing error (2/TM) ``` #### How to reproduce Required to start Kamailio with a config like ``` listen=udp:127.0.0.1:5060 listen=tcp:127.0.0.1:5060 loadmodule "pv.so" loadmodule "xlog.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "siputils.so" loadmodule "rr.so" loadmodule "stun.so" loadmodule "outbound.so" modparam("outbound", "force_outbound_flag", 1) modparam("outbound", "flow_token_secret", "kamailio") loadmodule "debugger.so" modparam("debugger", "cfgtrace", 1) modparam("debugger", "log_level_name", "exec") request_route { loose_route(); switch($rc) { case -3: xlog("L_ERR", "loose_route code -3\n"); break; case -2: xlog("L_ERR", "loose_route code -2\n"); break; case -1: xlog("L_ERR", "loose_route code -1\n"); break; case 1: xlog("L_ERR", "loose_route code 1\n"); break; case 2: xlog("L_ERR", "loose_route code 2\n"); break; } record_route(); if (has_totag()) { t_relay(); } else { t_relay_to_udp("127.0.0.1", "5080"); } } ``` Then need to start SIPp server script using the command ``` sipp -sf uas.xml -p 5080 -d 4000 -bind_local 127.0.0.1 ``` And then start SIPp client script using the command ``` sipp -sf uac.xml -m 1 -t t1 127.0.0.1 ``` Where `uac.xml` and `uas.xml` are attached [sipp-scripts.tar.gz](https://github.com/user-attachments/files/21187724/sip… -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4315 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4315(a)github.com>

2 2

git:master:e49d77af: modules: readme files regenerated - topos ... [skip ci]
by Kamailio Dev 23 Jul '25

23 Jul '25

Module: kamailio Branch: master Commit: e49d77af246c52591e76cfdcf0d59970d7349e7e URL: https://github.com/kamailio/kamailio/commit/e49d77af246c52591e76cfdcf0d5997… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2025-07-23T19:46:09+02:00 modules: readme files regenerated - topos ... [skip ci] --- Modified: src/modules/topos/README --- Diff: https://github.com/kamailio/kamailio/commit/e49d77af246c52591e76cfdcf0d5997… Patch: https://github.com/kamailio/kamailio/commit/e49d77af246c52591e76cfdcf0d5997… --- diff --git a/src/modules/topos/README b/src/modules/topos/README index 60a06f6b705..3f4d931cf26 100644 --- a/src/modules/topos/README +++ b/src/modules/topos/README @@ -573,11 +573,14 @@ request_route { It is executed before doing topology stripping processing for an outgoing SIP message. If 'drop' is executed inside the event route, - then the module skips doing the out part of topology hiding. + then the module skips doing the outbound part of topology stripping. - Only fake msg is available in this event route. Inside the event route - the variables $sndto(ip), $sndto(port) and $sndto(proto) point to the - destination. + The event route is executed with an internal fake SIP message for the + purpose of performace (i.e., no parsing of the outgoing message is + done), therefore the R-URI, headers and body do not reflect the content + of the outgoing message. However, inside the event route the variables + $sndto(ip), $sndto(port) and $sndto(proto) point to the real + destination of the SIP message. Example 1.24. Usage of event_route[topos:msg-outgoing] ... @@ -593,11 +596,14 @@ event_route[topos:msg-outgoing] { It is executed before doing topology stripping processing for a SIP message to be sent out, being executed after event_route[topos:msg-outgoing]. If 'drop' is executed inside the event - route, then the module skips doing the out part of topology hiding. + route, then the module skips doing the outbound part of topology + stripping. - A copy of the SIP msg to be sent out is available in this event route. - Inside the event route the variables $sndto(ip), $sndto(port) and - $sndto(proto) point to the destination. + A copy of the SIP message to be sent out is made available in this + event route, thefore the R-URI, headers and body reflect the content of + the outgoing SIP message. Inside the event route the variables + $sndto(ip), $sndto(port) and $sndto(proto) point to the real + destination of the SIP message. Example 1.25. Usage of event_route[topos:msg-sending] ... @@ -612,10 +618,14 @@ event_route[topos:msg-sending] { It is executed before doing topology stripping processing for an incoming SIP message. If 'drop' is executed inside this event route, - then the module skips doing the in part of topology hiding. + then the module skips doing the inbound part of topology stripping. - Only fake msg is available in this event route. $si, $sp and $proto - will have default fake values. + The event route is executed with an internal fake SIP message for the + purpose of performace (i.e., no parsing of the incoming message is + done), therefore the R-URI, headers and body do not reflect the content + of the incoming message. However, inside the event route the variables + $si, $sp and $proto point to the real source address of the SIP + message, as well as the keywords src_port and dst_port. Example 1.26. Usage of event_route[topos:msg-incoming] ... @@ -631,11 +641,13 @@ event_route[topos:msg-incoming] { It is executed before doing topology stripping processing for a SIP message that was received, being executed after event_route[topos:msg-incoing]. If 'drop' is executed inside this event - route, then the module skips doing the in part of topology hiding. + route, then the module skips doing the inbound part of topology hiding. - A copy of the received SIP msg is available in this event route. $si, - $sp and $proto will have correct, expected values. Also src_port and - dst_port can be used here. + A copy of the incoming SIP message is made available in this event + route, thefore the R-URI, headers and body reflect the content of the + incoming SIP message. Inside the event route the variables $si, $sp and + $proto point to the real source address of the SIP message, as well as + the keywords src_port and dst_port. Example 1.27. Usage of event_route[topos:msg-receiving] ...

1 0

git:master:913d60be: topos: docs updated for event routes
by Daniel-Constantin Mierla 23 Jul '25

23 Jul '25

Module: kamailio Branch: master Commit: 913d60bed99eee7dd212831e9153e5a3c39ab4be URL: https://github.com/kamailio/kamailio/commit/913d60bed99eee7dd212831e9153e5a… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2025-07-23T19:41:25+02:00 topos: docs updated for event routes --- Modified: src/modules/topos/doc/topos_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/913d60bed99eee7dd212831e9153e5a… Patch: https://github.com/kamailio/kamailio/commit/913d60bed99eee7dd212831e9153e5a…

1 0

git:master:c6c25e43: sipdump: made the received info available via the faked message in event route
by Daniel-Constantin Mierla 23 Jul '25

23 Jul '25

Module: kamailio Branch: master Commit: c6c25e43c8a24b50b73bf0772d58686cf8944020 URL: https://github.com/kamailio/kamailio/commit/c6c25e43c8a24b50b73bf0772d58686… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2025-07-23T19:41:25+02:00 sipdump: made the received info available via the faked message in event route --- Modified: src/modules/topos/topos_mod.c --- Diff: https://github.com/kamailio/kamailio/commit/c6c25e43c8a24b50b73bf0772d58686… Patch: https://github.com/kamailio/kamailio/commit/c6c25e43c8a24b50b73bf0772d58686… --- diff --git a/src/modules/topos/topos_mod.c b/src/modules/topos/topos_mod.c index 1af28fb8100..6d1bb65d02c 100644 --- a/src/modules/topos/topos_mod.c +++ b/src/modules/topos/topos_mod.c @@ -687,12 +687,13 @@ int tps_get_branch_expire(void) static int tps_execute_event_route(sip_msg_t *msg, sr_event_param_t *evp, int evtype, int evidx, str *evname) { - struct sip_msg *fmsg; + sip_msg_t *fmsg = NULL; struct run_act_ctx ctx; int rtb; sr_kemi_eng_t *keng = NULL; onsend_info_t onsnd_info = {0}; - onsend_info_t *p_onsend_bak; + onsend_info_t *p_onsend_bak = 0; + receive_info_t fmsg_rcv_bak = {0}; if(!(_tps_eventrt_mode & evtype)) { return 0; @@ -717,7 +718,6 @@ static int tps_execute_event_route(sip_msg_t *msg, sr_event_param_t *evp, LM_DBG("executing event_route[topos:%.*s] (%d)\n", evname->len, evname->s, evidx); - fmsg = faked_msg_next(); if(evp->dst) { onsnd_info.to = &evp->dst->to; @@ -728,6 +728,11 @@ static int tps_execute_event_route(sip_msg_t *msg, sr_event_param_t *evp, onsnd_info.len = msg->len; onsnd_info.msg = msg; } else { + fmsg = faked_msg_next(); + fmsg_rcv_bak = fmsg->rcv; + if(evp->rcv != NULL) { + fmsg->rcv = *evp->rcv; + } onsnd_info.buf = fmsg->buf; onsnd_info.len = fmsg->len; onsnd_info.msg = fmsg; @@ -746,10 +751,17 @@ static int tps_execute_event_route(sip_msg_t *msg, sr_event_param_t *evp, < 0) { LM_ERR("error running event route kemi callback\n"); p_onsend = p_onsend_bak; + if(fmsg != NULL && evp->rcv != NULL) { + fmsg->rcv = fmsg_rcv_bak; + } return -1; } } } + if(fmsg != NULL && evp->rcv != NULL) { + fmsg->rcv = fmsg_rcv_bak; + } + set_route_type(rtb); if(ctx.run_flags & DROP_R_F) { LM_DBG("exit due to 'drop' in event route\n");

1 0

git:master:a9d66588: modules: readme files regenerated - topos ... [skip ci]
by Kamailio Dev 23 Jul '25

23 Jul '25

Module: kamailio Branch: master Commit: a9d6658862a5d266853456e5201e6e08b7c81de5 URL: https://github.com/kamailio/kamailio/commit/a9d6658862a5d266853456e5201e6e0… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2025-07-23T19:01:10+02:00 modules: readme files regenerated - topos ... [skip ci] --- Modified: src/modules/topos/README --- Diff: https://github.com/kamailio/kamailio/commit/a9d6658862a5d266853456e5201e6e0… Patch: https://github.com/kamailio/kamailio/commit/a9d6658862a5d266853456e5201e6e0… --- diff --git a/src/modules/topos/README b/src/modules/topos/README index 9c82ff026e1..60a06f6b705 100644 --- a/src/modules/topos/README +++ b/src/modules/topos/README @@ -573,13 +573,11 @@ request_route { It is executed before doing topology stripping processing for an outgoing SIP message. If 'drop' is executed inside the event route, - then the module skips doing the topology hiding. + then the module skips doing the out part of topology hiding. - Inside the event route the variables $sndto(ip), $sndto(port) and - $sndto(proto) point to the destination. The SIP message is not the one - to be sent out, but an internally generated one at startup, to avoid - reparsing the outgoing SIP message for the cases when topology hiding - is not wanted. + Only fake msg is available in this event route. Inside the event route + the variables $sndto(ip), $sndto(port) and $sndto(proto) point to the + destination. Example 1.24. Usage of event_route[topos:msg-outgoing] ... @@ -594,11 +592,12 @@ event_route[topos:msg-outgoing] { It is executed before doing topology stripping processing for a SIP message to be sent out, being executed after - event_route[topos:msg-outgoing]. + event_route[topos:msg-outgoing]. If 'drop' is executed inside the event + route, then the module skips doing the out part of topology hiding. + A copy of the SIP msg to be sent out is available in this event route. Inside the event route the variables $sndto(ip), $sndto(port) and - $sndto(proto) point to the destination. The SIP message is the one to - be sent out. + $sndto(proto) point to the destination. Example 1.25. Usage of event_route[topos:msg-sending] ... @@ -612,13 +611,11 @@ event_route[topos:msg-sending] { 5.3. event_route[topos:msg-incoming] It is executed before doing topology stripping processing for an - incoming SIP message. If 'drop' is executed inside the event route, - then the module skips doing the topology hiding. + incoming SIP message. If 'drop' is executed inside this event route, + then the module skips doing the in part of topology hiding. - Inside the event route the variables $si, $sp and $proto point to the - source address. The SIP message is not the one to be sent out, but an - internally generated one at startup, to avoid reparsing the outgoing - SIP message for the cases when topology hiding is not wanted. + Only fake msg is available in this event route. $si, $sp and $proto + will have default fake values. Example 1.26. Usage of event_route[topos:msg-incoming] ... @@ -633,10 +630,12 @@ event_route[topos:msg-incoming] { It is executed before doing topology stripping processing for a SIP message that was received, being executed after - event_route[topos:msg-incoing]. + event_route[topos:msg-incoing]. If 'drop' is executed inside this event + route, then the module skips doing the in part of topology hiding. - Inside the event route the variables $si, $sp and $proto point to the - source address. The SIP message is the one to be sent out. + A copy of the received SIP msg is available in this event route. $si, + $sp and $proto will have correct, expected values. Also src_port and + dst_port can be used here. Example 1.27. Usage of event_route[topos:msg-receiving] ... @@ -644,5 +643,13 @@ event_route[topos:msg-receiving] { if(is_request() and $fU=="alice") { drop; } + + if($sp==5555 || $si=="1.2.3.4") { + drop; + } + + if(src_port==1234 || dst_port==5678) { + drop; + } } ...

1 0

[kamailio/kamailio] topos: expose rcv data in event routes (PR #4329)
by Stefan Mititelu 23 Jul '25

23 Jul '25

Updated documentation.   #### Pre-Submission Checklist    - [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 - [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:  - [ ] PR should be backported to stable branches - [X] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Right now if I try to log $sp in event_route[topos:msg-receiving], will have value 0. Updated documentation too, related to those event routes. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4329 -- Commit Summary -- * topos: expose rcv data in event routes -- File Changes -- M src/modules/topos/doc/topos_admin.xml (41) M src/modules/topos/topos_mod.c (6) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4329.patch https://github.com/kamailio/kamailio/pull/4329.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4329 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4329(a)github.com>

2 2

git:master:90b350a2: topos: expose rcv data in event routes
by Daniel-Constantin Mierla 23 Jul '25

23 Jul '25

Module: kamailio Branch: master Commit: 90b350a2815bc2ca4c69fda75194322416ced328 URL: https://github.com/kamailio/kamailio/commit/90b350a2815bc2ca4c69fda75194322… Author: Stefan Mititelu <stefan.mititelu(a)net2phone.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2025-07-23T18:52:37+02:00 topos: expose rcv data in event routes Updated documentation. --- Modified: src/modules/topos/doc/topos_admin.xml Modified: src/modules/topos/topos_mod.c --- Diff: https://github.com/kamailio/kamailio/commit/90b350a2815bc2ca4c69fda75194322… Patch: https://github.com/kamailio/kamailio/commit/90b350a2815bc2ca4c69fda75194322…

1 0

[kamailio/kamailio] Parse urn fix (PR #4336)
by Xenofon Karamanos 23 Jul '25

23 Jul '25

#### Pre-Submission Checklist    - [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 - [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:  - [ ] PR should be backported to stable branches - [x] Tested changes locally - [x] Related to issue https://kamailio.org/mailman3/hyperkitty/list/sr-users@lists.kamailio.org/t… #### Description  This PR fixes the bug when failing to parse a URN scheme with a '@' character in the host name. - Format of file - Add some comments on magic numbers You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4336 -- Commit Summary -- * core: Fix urn parsing failing if @ is present * core: add some comment on the hardcoded numbers -- File Changes -- M src/core/parser/parse_uri.c (24) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4336.patch https://github.com/kamailio/kamailio/pull/4336.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4336 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4336(a)github.com>

4 9

git:master:e7bf487c: dispatcher: use always the internal faked message for event routes
by Daniel-Constantin Mierla 23 Jul '25

23 Jul '25

Module: kamailio Branch: master Commit: e7bf487cfcde699fbcd6fd4a6233ef2113570545 URL: https://github.com/kamailio/kamailio/commit/e7bf487cfcde699fbcd6fd4a6233ef2… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2025-07-23T17:24:55+02:00 dispatcher: use always the internal faked message for event routes - being executed on state change, the config message does not provide useful data (e.g., on ds_mark_dst() inside failure route, the UAS request is used, not having uri where it was sent) - the r-uri of the internal faked message is set to the destination uri from the dispatcher record --- Modified: src/modules/dispatcher/dispatch.c --- Diff: https://github.com/kamailio/kamailio/commit/e7bf487cfcde699fbcd6fd4a6233ef2… Patch: https://github.com/kamailio/kamailio/commit/e7bf487cfcde699fbcd6fd4a6233ef2… --- diff --git a/src/modules/dispatcher/dispatch.c b/src/modules/dispatcher/dispatch.c index d51d7b6b1ed..4f33d2789f0 100644 --- a/src/modules/dispatcher/dispatch.c +++ b/src/modules/dispatcher/dispatch.c @@ -3538,7 +3538,7 @@ static void ds_run_route(sip_msg_t *msg, str *uri, char *route, ds_rctx_t *rctx) { int rt, backup_rt; struct run_act_ctx ctx; - sip_msg_t *fmsg; + sip_msg_t *fmsg = NULL; sr_kemi_eng_t *keng = NULL; str evname; @@ -3565,18 +3565,14 @@ static void ds_run_route(sip_msg_t *msg, str *uri, char *route, ds_rctx_t *rctx) } } - if(msg == NULL || msg == FAKED_REPLY) { - if(faked_msg_init() < 0) { - LM_ERR("faked_msg_init() failed\n"); - return; - } - fmsg = faked_msg_next(); - if(rewrite_uri(fmsg, uri) < 0) { - LM_ERR("failed to set r-uri\n"); - return; - } - } else { - fmsg = msg; + if(faked_msg_init() < 0) { + LM_ERR("faked_msg_init() failed\n"); + return; + } + fmsg = faked_msg_next(); + if(rewrite_uri(fmsg, uri) < 0) { + LM_ERR("failed to set r-uri\n"); + return; } if(rt >= 0 || ds_event_callback.len > 0) { @@ -3600,9 +3596,7 @@ static void ds_run_route(sip_msg_t *msg, str *uri, char *route, ds_rctx_t *rctx) set_route_type(backup_rt); _ds_rctx = NULL; } - if(fmsg != msg) { - reset_uri(fmsg); - } + reset_uri(fmsg); }

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev