Module: kamailio
Branch: master
Commit: 1d62f9d0310d462b88db1872e3db54d5f148a54c
URL: https://github.com/kamailio/kamailio/commit/1d62f9d0310d462b88db1872e3db54d…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2021-08-24T10:16:52+02:00
ruxc: docs for the new timeouts params
---
Modified: src/modules/ruxc/doc/ruxc_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/1d62f9d0310d462b88db1872e3db54d…
Patch: https://github.com/kamailio/kamailio/commit/1d62f9d0310d462b88db1872e3db54d…
---
diff --git a/src/modules/ruxc/doc/ruxc_admin.xml b/src/modules/ruxc/doc/ruxc_admin.xml
index 2c1aec6285..cdfb201fd7 100644
--- a/src/modules/ruxc/doc/ruxc_admin.xml
+++ b/src/modules/ruxc/doc/ruxc_admin.xml
@@ -62,7 +62,15 @@
<title><varname>http_timeout</varname> (int)</title>
<para>
The interval in miliseconds after which the HTTP GET or POST query
- times out.
+ times out. It is the overall timeout, including DNS resolution, connecting
+ time, redirects, and reading the response body. Slow DNS resolution
+ may cause a request to exceed the timeout, because the DNS request
+ cannot be interrupted with the available APIs. It takes precedence over
+ http_timeout_read() and http_timeout_write(), but not http_timeout_connect.
+ See also the comments in 'https://github.com/algesten/ureq/blob/main/src/agent.rs'.
+ </para>
+ <para>
+ Use 0 to disable setting it in the library.
</para>
<para>
<emphasis>
@@ -75,6 +83,76 @@
...
modparam("ruxc", "http_timeout", 2000)
...
+</programlisting>
+ </example>
+ </section>
+ <section id="ruxc.p.http_timeout_connect">
+ <title><varname>http_timeout_connect</varname> (int)</title>
+ <para>
+ The interval in miliseconds after which to give up on connecting to the
+ HTTP/S server. If http_timeout is set, this one takes precedence. The
+ library beneath has a default 30 seconds connect timeout.
+ </para>
+ <para>
+ Use 0 to disable setting it in the library.
+ </para>
+ <para>
+ <emphasis>
+ Default value is 5000 (5 secs).
+ </emphasis>
+ </para>
+ <example>
+ <title>Set <varname>http_timeout_connect</varname> parameter</title>
+ <programlisting format="linespecific">
+...
+modparam("ruxc", "http_timeout_connect", 2000)
+...
+</programlisting>
+ </example>
+ </section>
+ <section id="ruxc.p.http_timeout_read">
+ <title><varname>http_timeout_read</varname> (int)</title>
+ <para>
+ The interval in miliseconds after which the read on HTTP/S connection
+ socket timeouts. If http_timeout is set, it takes precedence.
+ </para>
+ <para>
+ Use 0 to disable setting it in the library.
+ </para>
+ <para>
+ <emphasis>
+ Default value is 5000 (5 secs).
+ </emphasis>
+ </para>
+ <example>
+ <title>Set <varname>http_timeout_read</varname> parameter</title>
+ <programlisting format="linespecific">
+...
+modparam("ruxc", "http_timeout_read", 2000)
+...
+</programlisting>
+ </example>
+ </section>
+ <section id="ruxc.p.http_timeout_write">
+ <title><varname>http_timeout_write</varname> (int)</title>
+ <para>
+ The interval in miliseconds after which the write on HTTP/S connection
+ socket timeouts. If http_timeout is set, it takes precedence.
+ </para>
+ <para>
+ Use 0 to disable setting it in the library.
+ </para>
+ <para>
+ <emphasis>
+ Default value is 5000 (5 secs).
+ </emphasis>
+ </para>
+ <example>
+ <title>Set <varname>http_timeout_write</varname> parameter</title>
+ <programlisting format="linespecific">
+...
+modparam("ruxc", "http_timeout_write", 2000)
+...
</programlisting>
</example>
</section>
ERROR: kazoo [kz_amqp.c:2238]: kz_amqp_send_ex(): Failed to publish -9 : a socket error occurred
ERROR: kazoo [kz_amqp.c:2707]: kz_amqp_publisher_send(): error sending publish to zone : local , connection id : 1, uri : amqp://admin
Recently, I encountered a problem. The connection between kamailio and rabbitmq was interrupted, which caused the queue of MQ to be blocked and the message could not be consumed。
Above is kamailio's error log。
--
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/2833
Hi,
I want to see if rtp packets are being relayed through kamailio. I am
attmepting to connect rtpengine with kamailio, but am not sure if it is
working, how can I tell?
I have the kamailio server on a different VM than the clients. In
wireshark, no rtp packets show on the server VM and rtp packets only seem
to be going directly through the client VM.
Rtp engine mentions being unable to find hashtables when attempting to
implement a delete_node command.
Thank you very much for your help,
Faiz
<!-- 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)
- [ ] 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
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Removed not used variable "route_mode" in the tm module. This was discovered by @IvanRibakov when using a g++ compiler, which added more strict flags (Ivan's Github is [here](https://github.com/IvanRibakov))
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2830
-- Commit Summary --
* tm - remove not used route_mode var
-- File Changes --
M src/modules/tm/tm_load.h (1)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2830.patchhttps://github.com/kamailio/kamailio/pull/2830.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/2830