Module: sip-router
Branch: master
Commit: 073620366761402e129d4585bb5728dae7469df6
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=0736203…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Fri Sep 26 22:15:02 2014 +0200
exec: Minor doc updates, adding section ID's
---
modules/exec/README | 4 ++--
modules/exec/doc/exec_admin.xml | 16 ++++++++--------
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/modules/exec/README b/modules/exec/README
index 0b7c1da..b28278d 100644
--- a/modules/exec/README
+++ b/modules/exec/README
@@ -216,5 +216,5 @@ exec_avp("echo TEST", "$avp(s:test)");
5. Known Issues
There is currently no guarantee that scripts ever return and stop
- blocking SIP server. (There is kill.c but it is not used along with the
- current mechanisms based on popen. Besides that kill.c is ugly).
+ blocking the SIP server. (There is kill.c but it is not used along with
+ the current mechanisms based on popen. Besides that kill.c is ugly).
diff --git a/modules/exec/doc/exec_admin.xml b/modules/exec/doc/exec_admin.xml
index 45ae097..0e933ab 100644
--- a/modules/exec/doc/exec_admin.xml
+++ b/modules/exec/doc/exec_admin.xml
@@ -13,7 +13,7 @@
<title>&adminguide;</title>
- <section>
+ <section id="exec.overview">
<title>Overview</title>
<para>
The exec module allows external commands to be executed from a &kamailio;
@@ -112,7 +112,7 @@
<section>
<title>Parameters</title>
- <section>
+ <section id="exec.p.setvars">
<title><varname>setvars</varname> (integer)</title>
<para>
Turn off to disable setting environment variables for executed commands.
@@ -131,7 +131,7 @@ modparam("exec", "setvars", 1)
</programlisting>
</example>
</section>
- <section>
+ <section id="exec.p.time_to_kill">
<title>
<varname>time_to_kill</varname> (integer)
</title>
@@ -156,7 +156,7 @@ modparam("exec", "time_to_kill", 20)
</section>
<section>
<title>Functions</title>
- <section>
+ <section id="exec.f.exec_dset">
<title>
<function moreinfo="none">exec_dset(command)</function>
</title>
@@ -191,7 +191,7 @@ exec_dset("echo TEST > /tmp/$rU.txt");
</programlisting>
</example>
</section>
- <section>
+ <section id="exec.f.exec_msg">
<title>
<function moreinfo="none">exec_msg(command)</function>
</title>
@@ -230,7 +230,7 @@ exec_msg("echo TEST > /tmp/$rU.txt");
</programlisting>
</example>
</section>
- <section>
+ <section id="exec.f.exec_avp">
<title>
<function moreinfo="none">exec_avp(command [, avplist])</function>
</title>
@@ -271,11 +271,11 @@ exec_avp("echo TEST", "$avp(s:test)");
</example>
</section>
</section>
- <section>
+ <section id="exec.known_issues">
<title>Known Issues</title>
<para>
There is currently no guarantee that scripts ever return and stop
- blocking &sip; server. (There is kill.c but it is not used along with
+ blocking the &sip; server. (There is kill.c but it is not used along with
the current mechanisms based on popen. Besides that kill.c is ugly).
</para>
</section>
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Juha Heinanen (jh)
Attached to Project - sip-router
Summary - tm.t_uac_wait does not use advertise address
Task Type - Bug Report
Category - tm
Status - New
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - when listen line has advertise address, tm.t_uac_wait does not use it when it replaces !! strings in headers of outgoing request, for example, in contact uri. as result, sip proxy behind nat cannot be reached from outside using the uri.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=471
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#468 - CANCEL sent shortly after '100 trying' response to INVITE does not always end the call
User who did this - Daniel-Constantin Mierla (miconda)
----------
I pushed a patch to detect if the transaction was canceled during execution of branch_route and skip forwarding the branches.
- http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=b66033d…
If you can test and report back the results, then I will backport, provided all is ok.
On the other hand, this INVITE-CANCEL-1xx race can happen even later. Like the process is losing the CPU just before writing the branch to the socket and the one that gets the CPU gets the CANCEL and processes it. In such case, the race will be caught later by one of the nodes (proxy, or even UA).
The UA should be prepared to handle CANCEL races anyhow, a 200ok can be on the wire towards it at the moment it sends CANCEL. Due to network transmission delays, it is impossible to avoid such races.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=468#comment1650
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
I'm on the latest 4.1 clone and seem to occasionally run into this crash:
#0 0x00007f7bd49e15ce in update_dlg_timer (tl=0x58, timeout=10)
at dlg_timer.c:203
#1 0x00007f7bd49cf35a in dlg_clean_run (ti=73979985) at dlg_hash.c:253
#2 0x00007f7bd49b90ec in dlg_clean_timer_exec (ticks=73979985, param=0x0)
at dialog.c:1246
#3 0x0000000000537091 in fork_sync_timer (child_id=-1,
desc=0x7f7bd49ec431 "Dialog Clean Timer", make_sock=1,
f=0x7f7bd49b90d3 <dlg_clean_timer_exec>, param=0x0, interval=90)
at timer_proc.c:232
#4 0x00007f7bd49b5b7b in child_init (rank=0) at dialog.c:733
The address of 'tl' appears to be bogus; that doesn't look like a valid
64 bit vmem address to me.
I'm investigating further to see if I can track it down, but I don't
have much more information right now.
--
Alex Balashov - Principal
Evariste Systems LLC
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Please be kind to the English language:
http://www.entrepreneur.com/article/232906
Module: sip-router
Branch: master
Commit: 2328948053cfd3bfec0ceef0e3ceca96a01f3271
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2328948…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Fri Sep 26 08:35:13 2014 +0200
call_control: Minor doc updates, adding section ID's
---
modules/call_control/README | 10 ++++----
modules/call_control/doc/call_control_admin.xml | 24 +++++++++++-----------
2 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/modules/call_control/README b/modules/call_control/README
index bd9007b..66c6c01 100644
--- a/modules/call_control/README
+++ b/modules/call_control/README
@@ -172,7 +172,7 @@ Chapter 1. Admin Guide
Boolean flag that specifies if callcontrol should be disabled. This is
useful when you want to use the same Kamailio configuration in two
- different context, one using callcontrol, the other not. In the case
+ different contexts, one using callcontrol, the other not. In the case
callcontrol is disabled, calls to the call_control() function will
return a code indicating that there is no limit associated with the
call, allowing the use of the same configuration without changes.
@@ -186,8 +186,8 @@ modparam("call_control", "disable", 1)
5.2. socket_name (string)
- It is the path to the filesystem socket where the callcontrol
- application listens for commands from the module.
+ The path to the filesystem socket where the callcontrol application
+ listens for commands from the module.
Default value is "/var/run/callcontrol/socket".
@@ -198,10 +198,10 @@ modparam("call_control", "socket_name", "/var/run/callcontrol/socket")
5.3. socket_timeout (int)
- How much time (in milliseconds) to wait for an answer from the
+ How long time (in milliseconds) to wait for an answer from the
callcontrol application.
- Default value is "500" (ms).
+ Default value is "500" ms.
Example 1.3. Setting the socket_timeout parameter
...
diff --git a/modules/call_control/doc/call_control_admin.xml b/modules/call_control/doc/call_control_admin.xml
index b3281db..bce0916 100644
--- a/modules/call_control/doc/call_control_admin.xml
+++ b/modules/call_control/doc/call_control_admin.xml
@@ -13,7 +13,7 @@
<title>&adminguide;</title>
- <section>
+ <section id="call_control.overview">
<title>Overview</title>
<para>
This module allows one to limit the duration of calls and automatically
@@ -164,12 +164,12 @@
<section>
<title>Exported parameters</title>
- <section>
+ <section id="call_control.p.disable">
<title><varname>disable</varname> (int)</title>
<para>
Boolean flag that specifies if callcontrol should be disabled. This
is useful when you want to use the same &kamailio; configuration in
- two different context, one using callcontrol, the other not. In the
+ two different contexts, one using callcontrol, the other not. In the
case callcontrol is disabled, calls to the call_control() function
will return a code indicating that there is no limit associated with
the call, allowing the use of the same configuration without changes.
@@ -191,10 +191,10 @@ modparam("call_control", "disable", 1)
</example>
</section>
- <section>
+ <section id="call_control.p.socket_name">
<title><varname>socket_name</varname> (string)</title>
<para>
- It is the path to the filesystem socket where the callcontrol
+ The path to the filesystem socket where the callcontrol
application listens for commands from the module.
</para>
@@ -215,16 +215,16 @@ modparam("call_control", "socket_name", "/var/run/callcontrol/socket")
</example>
</section>
- <section>
+ <section id="call_control.p.socket_time">
<title><varname>socket_timeout</varname> (int)</title>
<para>
- How much time (in milliseconds) to wait for an answer from the
+ How long time (in milliseconds) to wait for an answer from the
callcontrol application.
</para>
<para>
<emphasis>
- Default value is <quote>500</quote> (ms).
+ Default value is <quote>500</quote> ms.
</emphasis>
</para>
@@ -238,7 +238,7 @@ modparam("call_control", "socket_timeout", 500)
</example>
</section>
- <section>
+ <section id="call_control.p.signaling_ip_avp">
<title><varname>signaling_ip_avp</varname> (string)</title>
<para>
Specification of the AVP which holds the IP address from where
@@ -278,7 +278,7 @@ modparam("call_control", "signaling_ip_avp", "$avp(s:signaling_ip)")
</example>
</section>
- <section>
+ <section id="call_control.p.canonical_uri_avp">
<title><varname>canonical_uri_avp</varname> (string)</title>
<para>
Specification of the AVP which holds an optional application defined
@@ -305,7 +305,7 @@ modparam("call_control", "canonical_uri_avp", "$avp(s:can_uri)")
</example>
</section>
- <section>
+ <section id="call_control.p.diverter_avp_id">
<title><varname>diverter_avp_id</varname> (string)</title>
<para>
Specification of the id of an integer AVP which holds an optional
@@ -351,7 +351,7 @@ route {
<section>
<title>Functions</title>
- <section>
+ <section id="call_control.f.call_control">
<title><function moreinfo="none">call_control()</function></title>
<para>
Trigger the use of callcontrol for the dialog started by the INVITE
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#424 - zombie dialogs in state 5
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=424
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.