Module: kamailio
Branch: master
Commit: 6462571bbdf1270516243b6759a26625ca874b80
URL: https://github.com/kamailio/kamailio/commit/6462571bbdf1270516243b6759a2662…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2022-02-16T09:39:43+01:00
async: docs for async task data functions
---
Modified: src/modules/async/doc/async_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/6462571bbdf1270516243b6759a2662…
Patch: https://github.com/kamailio/kamailio/commit/6462571bbdf1270516243b6759a2662…
---
diff --git a/src/modules/async/doc/async_admin.xml b/src/modules/async/doc/async_admin.xml
index 1db4d60e9e..b0e5ec45bd 100644
--- a/src/modules/async/doc/async_admin.xml
+++ b/src/modules/async/doc/async_admin.xml
@@ -370,6 +370,74 @@ route[RESUME] {
exit;
}
...
+</programlisting>
+ </example>
+ </section>
+ <section id="async.f.async_task_data">
+ <title>
+ <function moreinfo="none">async_task_data(routename, data)</function>
+ </title>
+ <para>
+ Send the data to a asynchronous task process (in the first group) that
+ executes the route[rountename] and makes the data available via $async(data).
+ </para>
+ <para>
+ The current SIP message is not suspended and it is not available in
+ the asynchronous task process, a local faked SIP request is used there.
+ </para>
+ <para>
+ The parameters can contain variables.
+ </para>
+ <para>
+ This function can be used from ANY_ROUTE.
+ </para>
+ <example>
+ <title><function>async_task_data</function> usage</title>
+ <programlisting format="linespecific">
+...
+async_workers_group="name=abc;workers=4;nonblock=0;usleep=0"
+...
+request_route {
+ ...
+ async_task_data("RESUME", "caller: $fU - callee: $tU");
+ ...
+}
+route[RESUME] {
+ xinfo("$async(data)\n");
+ exit;
+}
+...
+</programlisting>
+ </example>
+ </section>
+ <section id="async.f.async_task_group_data">
+ <title>
+ <function moreinfo="none">async_task_group_data(routename, groupname, data)</function>
+ </title>
+ <para>
+ Similar to async_task_route(), but allows to specify the name of the group
+ for asynchronous workers. See also 'async_workers_group' core global
+ parameter.
+ </para>
+ <para>
+ This function can be used from ANY_ROUTE.
+ </para>
+ <example>
+ <title><function>async_task_group_data</function> usage</title>
+ <programlisting format="linespecific">
+...
+async_workers_group="name=abc;workers=4;nonblock=0;usleep=0"
+...
+request_route {
+ ...
+ async_task_data("RESUME", "abc", "caller: $fU - callee: $tU");
+ ...
+}
+route[RESUME] {
+ xinfo("$async(data)\n");
+ exit;
+}
+...
</programlisting>
</example>
</section>
Hi. I have simple call flow:
```
UAS PROXY UAS
1 | INVITE | |
|---------->| |
2 | 100 | |
|<----------| |
3 | | INVITE |
| |---------->|
4 | | 100 |
| |<----------|
5 | | 180 |
| |<----------|
6 | 180 | |
|<----------| |
7 | | 183 |
| |<----------|
8 | 183 | |
|<----------| |
9 | CANCEL | |
|---------->| |
10| | CANCEL |
| |---------->|
11| 200 | |
|<----------| |
12| | 200 |
| |<----------|
13| | 487 |
| |<----------|
14| | ACK |
| |---------->|
15| 487 | |
|<----------| |
16| ACK | |
|---------->| |
```
One of our customers complains that TO-TAGs in 183 (packet 8) and 200(packet 11) are not equal(their devices see 3 to-tag during 1 dialog). I found in RFC 3261that it's ok(https://datatracker.ietf.org/doc/html/rfc3261#section-16.10).
183 is forwarded from UAS(UAS sets to-tag) and 200 is generated by Kamailio. This is why to-tags in 183 and 200 are not equal.
Is it possible to use to-tag from master branch(ofc if we have received a reply from UAS and we have this tag)?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3021
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3021(a)github.com>
kamailio[20903]: ERROR: <core> [core/tcp_main.c:3101]: tcp_init(): bind(2d, 0x7f7cff0ff610, 16) on xxx.xxx.xx.xx:5060 : Address already in use
#Sudo kamailio status
ERROR: connect_unix_sock: connect(/var/run/kamailio//kamailio_ctl): No such file or directory
Thanks
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3027
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3027(a)github.com>
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
If there is no content to be filled in a section, the entire section can be removed.
You can delete the comments from the template sections when filling.
You can delete next line and everything above before submitting (it is a comment).
-->
### Description
<!--
Explain what you did, what you expected to happen, and what actually happened.
-->
### Troubleshooting
#### Reproduction
<!--
If the issue can be reproduced, describe how it can be done.
-->
#### Debugging Data
<!--
If you got a core dump, use gdb to extract troubleshooting data - full backtrace,
local variables and the list of the code at the issue location.
gdb /path/to/kamailio /path/to/corefile
bt full
info locals
list
If you are familiar with gdb, feel free to attach more of what you consider to
be relevant.
-->
```
(paste your debugging data here)
```
#### Log Messages
<!--
Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your log messages here)
```
#### SIP Traffic
<!--
If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site).
-->
```
(paste your sip traffic here)
```
### Possible Solutions
<!--
If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix.
-->
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
(paste your output here)
```
* **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 `lsb_release -a` and `uname -a`)
-->
```
(paste your output here)
```
Hello Experts,
please help me to change port service from default 5060 port into other port due to security reason. Since I have change port in kamailio.cfg file, but services cannot fly normally that shown client unable login online (status not online).
![image](https://user-images.githubusercontent.com/76675592/154027407-24ab423b-302b-435e-bad4-5dcb22a5ad3d.png)
Besides, I need to run the kamailio services after install default kamailio, I have not found where procedure found in this installation process.
Thanks
Bp
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3026
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3026(a)github.com>