#### 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
- [ ] 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:
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
The new parameter connect_timeout_ms (global) / timeout_ms (in httpcon) allows to specify a timeout in milliseconds on curl requests.
If this parameter is defined (non zero), then the timeout in seconds is ignored.
If either timeout or timeout_ms is defined at connection level, then they take precedence over the global parameters.
These principles also apply to the file configuration.
The timeout in ms is used internally to set CURLOPT_TIMEOUT_MS.
The value is shown in ms when using RPC "httpclient.listcon".
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3611
-- Commit Summary --
* http_client: Add parameter connect_timeout_ms / timeout_ms (2)
-- File Changes --
M src/modules/http_client/curlcon.c (103)
M src/modules/http_client/doc/http_client_admin.xml (32)
M src/modules/http_client/functions.c (24)
M src/modules/http_client/http_client.c (12)
M src/modules/http_client/http_client.h (13)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3611.patchhttps://github.com/kamailio/kamailio/pull/3611.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3611
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3611(a)github.com>
#### 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 -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Add function to get dialog by internal hash entry and id. This is needed by my other ongoing changes to the ims_charging module for restoring records from database.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3613
-- Commit Summary --
* ims_dialog: Add function to get dialog by hash entry and id
-- File Changes --
M src/modules/ims_dialog/dlg_handlers.c (19)
M src/modules/ims_dialog/dlg_handlers.h (8)
M src/modules/ims_dialog/dlg_load.h (5)
M src/modules/ims_dialog/ims_dialog.c (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3613.patchhttps://github.com/kamailio/kamailio/pull/3613.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3613
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3613(a)github.com>
#### 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
- [ ] 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:
- [x] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
The new parameter connect_timeout_ms (global) / timeout_ms (in httpcon) allows to specify a timeout in milliseconds on curl requests.
If this parameter is defined (non zero), then the timeout in seconds is ignored.
See https://curl.se/libcurl/c/CURLOPT_TIMEOUT_MS.html
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3609
-- Commit Summary --
* http_client: Add parameter connect_timeout_ms / timeout_ms
-- File Changes --
M src/modules/http_client/curlcon.c (55)
M src/modules/http_client/doc/http_client_admin.xml (29)
M src/modules/http_client/functions.c (22)
M src/modules/http_client/http_client.c (12)
M src/modules/http_client/http_client.h (12)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3609.patchhttps://github.com/kamailio/kamailio/pull/3609.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3609
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3609(a)github.com>
<!-- 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
- [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:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] 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 -->
Just a small change in app_ruby_rpc_reload_doc constant which mistakingly says javascript instead of ruby file.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3614
-- Commit Summary --
* app_ruby: Fix rpc documentation typo
-- File Changes --
M src/modules/app_ruby/app_ruby_mod.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3614.patchhttps://github.com/kamailio/kamailio/pull/3614.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3614
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3614(a)github.com>
### Description
I've been looking at the ims_dialog module and notice that the documentation states that db storage is not yet supported.
According to the source code that only partial true. Not sure if it's residues from the other dialog module, or some unfinished work.
After some initial testing and small adjustments, the main issue seems to that for my use the "Dialog-iD"/did is not filled. I can not see this being set for calls that are not "concurrently confirmed".
The field in the database for this id is NON NULL, so the insert fails. It's also used as WHERE-criteria when restarting and fetching the dialog_out entries, belonging to each dialog_in, so it needs to be set for this to work.
This is not really a feature request. It's more about a confirmation that my assumptions are correct, before trying to do the proposed changes.
### Expected behavior
I do assume that this "did"-field should be or be linked to the same did added as Record-Route parameter, identifying each dialog.
#### Actual observed behavior
kamcmd dlg2.list displays NULL for Dialog-ID.
```
kamcmd dlg2.list
{
Size: 4096
Dialogs: {
Dialog: {
Entry: 1096
Id: 8069
RURI: sip:+4791500025@10.111.64.16;user=phone
From: sip:+4746180445@10.111.64.16;user=phone
Call-ID: 34c5d9f15ff42a0564f809cb35e19c75@10.111.64.16:5060
Caller Contact: sip:+4746180445@10.111.64.16:5060
Caller Route Set: <null string>
Dialog-ID: <null string>
From Tag: as4df55540
State: Confirmed
Ref: 2
dlg_outs: {
dlg_out: {
Entry: 2680
Id: 0
}
}
}
}
}
```
### Possible Solutions
Always set this did field when a new dialog is created.
I've also been studying the DB schema. All operations for the dialog_in table are done using hash_entry and hash_id as keys. Why are they not used as primary key instead, which would be much more efficient?
Also, having an integer with auto_increment as primary key would make this stop when the integer hits max value, if it's not reset regularly. I can not see this field used anywhere in the code either, so it could probably just be removed.
The same applies to dialog_out, but this one should have an index on the did field used for looking up the corresponding entries too.
Altering this could have negative impact if there are old entries from a previous running process laying around. A duplicate key on an insert should be handled, and updated instead. The current behaviour would mean that Kamailio instead updates two records with the same values.
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
master
```
* **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`)
-->
```
CentOS 7.9
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3602
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3602(a)github.com>
<!-- 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 -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #3602
#### Description
Added missing code for database backend to work. Tested basic scenarios locally for all db modes.
DB schema could be tweaked according to my thoughts in issue #3602, but that also applies to several other modules which are done in the same matter. Because of that, I didn't consider such a change now.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3603
-- Commit Summary --
* ims_dialog: Add support for database backend
-- File Changes --
M src/modules/ims_dialog/dlg_db_handler.c (9)
M src/modules/ims_dialog/dlg_handlers.c (52)
M src/modules/ims_dialog/dlg_hash.c (5)
M src/modules/ims_dialog/doc/ims_dialog_admin.xml (93)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3603.patchhttps://github.com/kamailio/kamailio/pull/3603.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3603
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3603(a)github.com>
<!-- 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 -->
The timeout_socket feature has been added in 2010, but from the look of it it has been designed for the "ngcp-mediaproxy-ng" and never worked with the real RTPProxy. As such both the documentation and the code needs to be adjusted to make it actually useful with the RTPProxy.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3598
-- Commit Summary --
* Make timeout notification useable by allowing a notify tag to
* Update rtpproxy module documentation:
-- File Changes --
M src/modules/rtpproxy/doc/rtpproxy.xml (2)
M src/modules/rtpproxy/doc/rtpproxy_admin.xml (38)
M src/modules/rtpproxy/rtpproxy.c (53)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3598.patchhttps://github.com/kamailio/kamailio/pull/3598.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3598
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3598(a)github.com>
Module: kamailio
Branch: master
Commit: 190ef9a54df33b4d053a4225e9d6257e0a045008
URL: https://github.com/kamailio/kamailio/commit/190ef9a54df33b4d053a4225e9d6257…
Author: Maksym Sobolyev <sobomax(a)sippysoft.com>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2023-10-20T09:57:47+02:00
rtpproxy: Update rtpproxy module documentation.
o Correct description of the timeout_socket;
o Document timeout_tag_pv;
o Update (c);
o Remove reference to the ngcp-mediaproxy-ng which does not exist
anymore.
---
Modified: src/modules/rtpproxy/doc/rtpproxy.xml
Modified: src/modules/rtpproxy/doc/rtpproxy_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/190ef9a54df33b4d053a4225e9d6257…
Patch: https://github.com/kamailio/kamailio/commit/190ef9a54df33b4d053a4225e9d6257…
---
diff --git a/src/modules/rtpproxy/doc/rtpproxy.xml b/src/modules/rtpproxy/doc/rtpproxy.xml
index 94886eaf404..ee1fdad9fc8 100644
--- a/src/modules/rtpproxy/doc/rtpproxy.xml
+++ b/src/modules/rtpproxy/doc/rtpproxy.xml
@@ -67,7 +67,7 @@
</editor>
</authorgroup>
<copyright>
- <year>2003-2008</year>
+ <year>2003-2023</year>
<holder>Sippy Software, Inc.</holder>
</copyright>
<copyright>
diff --git a/src/modules/rtpproxy/doc/rtpproxy_admin.xml b/src/modules/rtpproxy/doc/rtpproxy_admin.xml
index 79a85edad70..b04baa5e3dc 100644
--- a/src/modules/rtpproxy/doc/rtpproxy_admin.xml
+++ b/src/modules/rtpproxy/doc/rtpproxy_admin.xml
@@ -18,11 +18,7 @@
<title>Overview</title>
<para>
This is a module that enables media streams to be proxied
- via an rtpproxy. Rtpproxies know to work with this module
- are Sippy RTPproxy <ulink url="http://www.rtpproxy.org"></ulink>
- and ngcp-rtpproxy-ng
- <ulink url="http://deb.sipwise.com/spce/2.6/pool/main/n/ngcp-mediaproxy-ng"></ulink>.
- Some features of the rtpproxy module apply only to one of the two rtpproxies.
+ via the Sippy RTPproxy <ulink url="http://www.rtpproxy.org"></ulink>.
</para>
</section>
@@ -235,7 +231,37 @@ modparam("rtpproxy", "nortpproxy_str", "a=sdpmangled:yes\r\n")
<title>Set <varname>timeout_socket</varname> parameter</title>
<programlisting format="linespecific">
...
-modparam("rtpproxy", "timeout_socket", "xmlrpc:http://127.0.0.1:8000/RPC2")
+modparam("rtpproxy", "timeout_socket", "tcp:127.0.0.1:8000")
+...
+</programlisting>
+ </example>
+ </section>
+ <section id="rtpproxy.p.timeout_tag_pv">
+ <title><varname>timeout_tag_pv</varname> (string)</title>
+ <para>
+ The parameter devines the AVP of the string to be provided to the
+ RTP-Proxy.
+ </para>
+ <para>
+ The content of the AVP must be a valid URL-encoded string with
+ no spaces.
+ It will be decoded and send by the RTP proxy to the timeout socket if the
+ media timeout has happened.
+ </para>
+ <para>
+ This parameter is required in order for the timeout notification
+ mechanism to work properly.
+ </para>
+ <para>
+ <emphasis>
+ Default value is <quote></quote> (nothing).
+ </emphasis>
+ </para>
+ <example>
+ <title>Set <varname>timeout_tag_pv</varname> parameter</title>
+ <programlisting format="linespecific">
+...
+modparam("rtpproxy", "timeout_tag_pv", "$avp(rtpp_ntag)")
...
</programlisting>
</example>
Hello,
I would like to set a timeout in milliseconds when using Kamailio module http_client.
From what I read, the module is accepting a parameter "connection_timeout":
https://www.kamailio.org/docs/modules/devel/modules/http_client.html#http_c…
This is used to set curl option "CURLOPT_TIMEOUT".
I would like to set instead curl option "CURLOPT_TIMEOUT_MS".
I think changing the parameter "connection_timeout" from seconds to milliseconds is not a good idea, since it would break existing configurations.
What about adding a new parameter "connection_timeout_ms" to the module ?
Curl documentation says that: "If both CURLOPT_TIMEOUT and CURLOPT_TIMEOUT_MS are set, the value set last is used."
The CURLOPT_TIMEOUT_MS should only be set if the parameter is non-zero, so that the current behaviour is kept if the new parameter is not configured.
What do you think ?
Regards,
Nicolas.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
<!-- 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
- [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:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [x] Related to issue #3074
#### Description
Since some customers are complaining on leftovers at active_watchers. Let's create a cleanup timer for that table too.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3605
-- Commit Summary --
* presence: active_watcher cleanup timer
-- File Changes --
M src/modules/presence/notify.c (33)
M src/modules/presence/notify.h (1)
M src/modules/presence/presence.c (5)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3605.patchhttps://github.com/kamailio/kamailio/pull/3605.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3605
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3605(a)github.com>
<!-- 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/3607
-- Commit Summary --
* Add and apply tls_openssl_clear_errors function.
-- File Changes --
M src/modules/tls/tls_ct_wrq.c (3)
M src/modules/tls/tls_server.c (11)
M src/modules/tls/tls_util.c (15)
M src/modules/tls/tls_util.h (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3607.patchhttps://github.com/kamailio/kamailio/pull/3607.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3607
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3607(a)github.com>
The local-request event route is not documented. When using our friend google I find an old blog post by @miconda but not much else. I can come up with some good text, but need to know what can be done in the route, like
- modify request uri
- add/remove headers
- drop request
- add/modify destination uri ($du)
--
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/980
<!-- 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/3604
-- Commit Summary --
* tools: route_graph - added README file
-- File Changes --
A misc/tools/route_graph/README (16)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3604.patchhttps://github.com/kamailio/kamailio/pull/3604.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3604
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3604(a)github.com>
Module: kamailio
Branch: master
Commit: 976da8c72e9a056b724f584a803a4a8114f70d30
URL: https://github.com/kamailio/kamailio/commit/976da8c72e9a056b724f584a803a4a8…
Author: VoIPNuggets.com <akash(a)voipnuggets.com>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2023-10-18T12:15:55+02:00
tools: route_graph - added README file and updated reference URL [skip ci]
---
Added: misc/tools/route_graph/README
---
Diff: https://github.com/kamailio/kamailio/commit/976da8c72e9a056b724f584a803a4a8…
Patch: https://github.com/kamailio/kamailio/commit/976da8c72e9a056b724f584a803a4a8…
---
diff --git a/misc/tools/route_graph/README b/misc/tools/route_graph/README
new file mode 100644
index 00000000000..c78cc8c49db
--- /dev/null
+++ b/misc/tools/route_graph/README
@@ -0,0 +1,16 @@
+This Python script, route_graph.py, serves as a utility tool for visualizing Kamailio SIP server configuration files.
+It generates a graphical representation of the routing logic defined in the configuration.
+
+Usage:
+1. Clone the GitHub repository:
+ git clone https://github.com/kamailio/kamailio.git
+2. Navigate to the tool's directory:
+ cd kamailio/misc/tools/route_graph/
+3. Run the script on your Kamailio configuration file:
+ python3 route_graph.py /path/to/kamailio.cfg
+
+For a more detailed walkthrough, please refer to this article:
+Visualizing Kamailio Configuration File Using Route Graph Tool.
+https://voipnuggets.com/2023/06/13/visualizing-kamailio-configuration-file-using-route_graph-tool/
+
+[ README written by Akash Gupta ]
Module: kamailio
Branch: master
Commit: 93fc6bc9c965391aa1e4ca546119ce2cc8699fbd
URL: https://github.com/kamailio/kamailio/commit/93fc6bc9c965391aa1e4ca546119ce2…
Author: Kamailio Dev <kamailio.dev(a)kamailio.org>
Committer: Kamailio Dev <kamailio.dev(a)kamailio.org>
Date: 2023-10-18T10:02:28+02:00
modules: readme files regenerated - topos ... [skip ci]
---
Modified: src/modules/topos/README
---
Diff: https://github.com/kamailio/kamailio/commit/93fc6bc9c965391aa1e4ca546119ce2…
Patch: https://github.com/kamailio/kamailio/commit/93fc6bc9c965391aa1e4ca546119ce2…
---
diff --git a/src/modules/topos/README b/src/modules/topos/README
index 033acf3a1e1..ad13698a204 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -233,7 +233,7 @@ modparam("topos", "db_url", "dbdriver://username:password@dbhost/dbname")
Call-id in the SIP message payload or header, so it is safe to not
encode Call-id in such cases. Well-known extensions such as call
transfer or conference join will be added to work with encoded Call-id.
- Topoh module should be loaded with use_mode paramerter set to 1
+ Topoh module should be loaded with use_mode parameter set to 1
Default value is 0 (do not mask).
Module: kamailio
Branch: master
Commit: d2f0e1c31920e5b2b38ddbc823c6bc332fac86a5
URL: https://github.com/kamailio/kamailio/commit/d2f0e1c31920e5b2b38ddbc823c6bc3…
Author: Henning Westerholt <hw(a)gilawa.com>
Committer: Henning Westerholt <hw(a)gilawa.com>
Date: 2023-10-18T07:55:59Z
topos: spelling fix in docs
---
Modified: src/modules/topos/doc/topos_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/d2f0e1c31920e5b2b38ddbc823c6bc3…
Patch: https://github.com/kamailio/kamailio/commit/d2f0e1c31920e5b2b38ddbc823c6bc3…
---
diff --git a/src/modules/topos/doc/topos_admin.xml b/src/modules/topos/doc/topos_admin.xml
index 9c1e4d3df1f..ebedcd13999 100644
--- a/src/modules/topos/doc/topos_admin.xml
+++ b/src/modules/topos/doc/topos_admin.xml
@@ -141,7 +141,7 @@ modparam("topos", "db_url", "&exampledb;")
not encode Call-id in such cases. Well-known extensions such as
call transfer or conference join will be added to work with encoded
Call-id.
- Topoh module should be loaded with use_mode paramerter set to 1
+ Topoh module should be loaded with use_mode parameter set to 1
</para>
<para>
Module: kamailio
Branch: master
Commit: 70ff7c298f257bec48809b9bc80fd06cfe87c7b4
URL: https://github.com/kamailio/kamailio/commit/70ff7c298f257bec48809b9bc80fd06…
Author: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Committer: Victor Seva <linuxmaniac(a)torreviejawireless.org>
Date: 2023-10-18T09:41:01+02:00
github: disable CodeQL scan for pull requests [skip ci]
job is failling due to "java.io.IOException: No space left on device"
---
Modified: .github/workflows/codeql.yml
---
Diff: https://github.com/kamailio/kamailio/commit/70ff7c298f257bec48809b9bc80fd06…
Patch: https://github.com/kamailio/kamailio/commit/70ff7c298f257bec48809b9bc80fd06…
---
diff --git a/.github/workflows/codeql.yml b/.github/workflows/codeql.yml
index 59e3dbf476f..3b36e5edd05 100644
--- a/.github/workflows/codeql.yml
+++ b/.github/workflows/codeql.yml
@@ -1,8 +1,6 @@
name: "CodeQL"
on:
- pull_request:
- branches: [ "master" ]
schedule:
- cron: "30 0 * * *"
# Allows you to run this workflow manually from the Actions tab