Module: kamailio
Branch: master
Commit: 5272f4e4e302e44ad870bd8b8936c2517848c0ca
URL: https://github.com/kamailio/kamailio/commit/5272f4e4e302e44ad870bd8b8936c25…
Author: Daniel-Constantin Mierla <miconda(a)gmail.com>
Committer: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: 2017-08-28T12:25:09+02:00
rtpengine: documented the flag for call recording
- reported by GH #1221
---
Modified: src/modules/rtpengine/doc/rtpengine_admin.xml
---
Diff: https://github.com/kamailio/kamailio/commit/5272f4e4e302e44ad870bd8b8936c25…
Patch: https://github.com/kamailio/kamailio/commit/5272f4e4e302e44ad870bd8b8936c25…
---
diff --git a/src/modules/rtpengine/doc/rtpengine_admin.xml b/src/modules/rtpengine/doc/rtpengine_admin.xml
index 4a7272629a..15355bb8c0 100644
--- a/src/modules/rtpengine/doc/rtpengine_admin.xml
+++ b/src/modules/rtpengine/doc/rtpengine_admin.xml
@@ -2036,7 +2036,7 @@ rtpengine_offer();
<listitem><para>
<emphasis>no-redis-update</emphasis> - this flag can be used by Kamailio in order
to tell rtpengine not to persist the call into Redis upon receiving offer/answer()
- control commands. If flag is not set, default action is rtpengine persists call
+ control commands. If flag is not set, default action is rtpengine persists call
to redis.
</para></listitem>
<listitem><para>
@@ -2273,7 +2273,16 @@ rtpengine_offer();
in the Sipwise rtpengine proxy. This is especially useful when the first call leg is handled
by some rtpengine machine while the second call leg is handled by other rtpengine machine.
</para></listitem>
+ <listitem><para>
+ <emphasis>record-call=on</emphasis> - instructs RTPEngine to record the session. Use
+ it in rtpengine_offer() to start recording immediately and save the call metadata,
+ as alternative to start_recording().
+ </para></listitem>
</itemizedlist>
+ <para>
+ Check also the documentation of RTPEngine, these flags are documented there as well:
+ <ulink url="https://github.com/sipwise/rtpengine">https://github.com/sipwise/rtpengine</ulink>.
+ </para>
</listitem>
</itemizedlist>
<para>
@@ -2466,8 +2475,11 @@ rtpengine_manage();
<function moreinfo="none">start_recording()</function>
</title>
<para>
- This function will send a signal to the &rtp; proxy to record
- the &rtp; stream on the &rtp; proxy.
+ This function will send a signal to the &rtp; relay to record
+ the &rtp; stream flowing through it. See also the option
+ <quote>record-call=on</quote> for rtpengine_manage()/rtpengine_offer(),
+ which offers an alternative for call recording, saving also call
+ metadata from SDP.
</para>
<para>
This function can be used from REQUEST_ROUTE and ONREPLY_ROUTE.
### Description
<!--
Send async http post request to multiple servers.
-->
### Troubleshooting
#### Reproduction
<!--
Kamailio runs for about 1-2 min till the segfault happens. Sadly there are not many infos in the coredump. I use this config for the http modules:
https://github.com/negbie/heplify/blob/master/kamailio5/http.cfg
-->
#### Debugging Data
```
gdb kamailio core.kamailio.114.1503484559.29804
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kamailio...(no debugging symbols found)...done.
[New LWP 29804]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f4b0a1c23e9 in notification_socket_cb () from /usr/lib/x86_64-linux-gnu/kamailio/modules/http_async_client.so
(gdb) bt full
#0 0x00007f4b0a1c23e9 in notification_socket_cb () from /usr/lib/x86_64-linux-gnu/kamailio/modules/http_async_client.so
No symbol table info available.
#1 0x00007f4b09cf23dc in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
No symbol table info available.
#2 0x00007f4b0a1bec74 in async_http_run_worker () from /usr/lib/x86_64-linux-gnu/kamailio/modules/http_async_client.so
No symbol table info available.
#3 0x00007f4b0a1a886e in ?? () from /usr/lib/x86_64-linux-gnu/kamailio/modules/http_async_client.so
No symbol table info available.
#4 0x000000000053e25a in ?? ()
No symbol table info available.
#5 0x000000000053df78 in ?? ()
No symbol table info available.
#6 0x000000000053e588 in init_child ()
No symbol table info available.
#7 0x0000000000423913 in main_loop ()
No symbol table info available.
#8 0x000000000042a308 in main ()
No symbol table info available.
(gdb)
```
#### Log Messages
```
kernel:[698859.513811] kamailio[29804]: segfault at 0 ip 00007f4b0a1c23e9 sp 00007ffeb48bdc00 error 4 in http_async_client.so[7f4b0a19e000+38000]
/usr/sbin/kamailio[29777]: ALERT: <core> [main.c:743]: handle_sigs(): child process 29804 exited by a signal 11
/usr/sbin/kamailio[29777]: ALERT: <core> [main.c:746]: handle_sigs(): core was generated
systemd[1]: kamailio.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Unit kamailio.service entered failed state.
```
### Additional Information
* **Kamailio Version** - output of `kamailio -v`
```
kamailio 5.0.2 (x86_64/linux)
```
* **Operating System**:
```
Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2
```
--
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/1219
Hi all
After a migration, a customer is reporting one way audio on incoming calls. A
tcpdump capture shows 65 rtp packets in both directions but rtpproxy log shows
RTP stats: 1 in from callee, 64 in from caller, 65 relayed, 0 dropped
Any thoughts?
cheers,
Jon