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)
----------
Thanks for troubleshooting and providing detailed report.
route[NATMANAGE] is executed from a branch_route in this case. I think the problem is that in this case the transaction is created, the branch route is executed and take a bit to complete. Cancel comes, another process handles it, marking transaction as cancelled. The forst process after execution of branch route is doing a send without checking if someone else canceled its own created transaction.
I will look soon as sources to confirm my guess and get a fix for it if proved valid.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=468#comment1648
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#424 - zombie dialogs in state 5
User who did this - Daniel-Constantin Mierla (miconda)
----------
Just as remark, if you use dlg_manage() before loose_route(), the event route is executed inside dlg_manage(). In your case, is in loose_route() indeed.
Can you give another try with master? I just pushed a patch.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=424#comment1647
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.
Hello,
I've been trying to use the usrloc attributes feature to store and retrieve additional data per location. This works for in-memory tables, but not when db_mode=DB_ONLY.
The attached patch adds this so the xavps are restored when doing a DB lookup for a single aor.
Is this a bugfix for an incomplete feature or do I need to wait for the thaw before committing?
Regards,
Hugh
________________________________
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
Module: sip-router
Branch: master
Commit: 2e047d4536f36627651abba08fbd4d511b299b05
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=2e047d4…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Tue Sep 23 21:57:44 2014 +0200
uuid Minor doc updates
---
modules/uuid/README | 7 +++++--
modules/uuid/doc/uuid_admin.xml | 7 +++++--
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/modules/uuid/README b/modules/uuid/README
index 2b1ce31..1be3f53 100644
--- a/modules/uuid/README
+++ b/modules/uuid/README
@@ -44,7 +44,10 @@ Chapter 1. Admin Guide
1. Overview
This module exports the $uuid(type) class of variables that return
- unique values using libuuid functions.
+ unique values using functions from the libuuid library. UUIDs are used
+ in the +sip.instance media feature tag in SIP, but can also be used for
+ other purposes, like defining a unique session ID for a group of SIP
+ dialogs.
2. Dependencies
@@ -64,7 +67,7 @@ Chapter 1. Admin Guide
3. Usage
- Following variables can be used:
+ The following variables can be used:
* $uuid(g) - return the UUID value using uuid_generate().
* $uuid(r) - return the UUID value using uuid_generate_random().
* $uuid(t) - return the UUID value using uuid_generate_time().
diff --git a/modules/uuid/doc/uuid_admin.xml b/modules/uuid/doc/uuid_admin.xml
index 902d006..5cc0649 100644
--- a/modules/uuid/doc/uuid_admin.xml
+++ b/modules/uuid/doc/uuid_admin.xml
@@ -17,7 +17,10 @@
<title>Overview</title>
<para>
This module exports the $uuid(type) class of variables that return
- unique values using libuuid functions.
+ unique values using functions from the libuuid library. UUIDs are
+ used in the +sip.instance media feature tag in SIP, but can also
+ be used for other purposes, like defining a unique session ID for a
+ group of SIP dialogs.
</para>
</section>
@@ -55,7 +58,7 @@
<section>
<title>Usage</title>
<para>
- Following variables can be used:
+ The following variables can be used:
<itemizedlist>
<listitem>
<para>
Module: sip-router
Branch: master
Commit: 615b79edafc990d2a82394c8b020fd7687dc7bc5
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=615b79e…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Tue Sep 23 21:49:18 2014 +0200
jsonrpc-s Update docs
JSON-RPC is called JSON-RPC with a hyphen.
---
modules/jsonrpc-s/README | 19 ++++++++++---------
modules/jsonrpc-s/doc/jsonrpc-s_admin.xml | 17 +++++++++--------
2 files changed, 19 insertions(+), 17 deletions(-)
diff --git a/modules/jsonrpc-s/README b/modules/jsonrpc-s/README
index c06769b..bb92a7a 100644
--- a/modules/jsonrpc-s/README
+++ b/modules/jsonrpc-s/README
@@ -67,8 +67,9 @@ Chapter 1. Admin Guide
1.1. Limitations
- This module provides JSONRPC server over HTTP implementation, tailored
- for the needs of Kamailio.
+ This module provides a JSON-RPC server over HTTP implementation,
+ tailored for the needs of Kamailio. It implements the Kamailio RPC
+ interface over JSON-RPC.
The JSONRPC-S module uses the xHTTP module to handle HTTP requests.
Read the documentation of the xHTTP module for more details.
@@ -77,10 +78,10 @@ Chapter 1. Admin Guide
* This module does not implement asynchronous RPC commands. It is
unlikely that asynchronous RPC commands will be executed from an
- JSONRPC over HTTP client.
+ JSON-RPC over HTTP client.
* This module does not accept parameters embedded in a structure (see
- RPC documentation for more info about how parameters can be passed
- to RPC).
+ the RPC documentation for more info about how parameters can be
+ passed to RPC).
2. Dependencies
@@ -104,7 +105,7 @@ Chapter 1. Admin Guide
3.1. pretty_format (int)
- Pretty format for JSONRPC response document.
+ Pretty format for JSON-RPC response document.
Default value is '0'.
@@ -167,11 +168,11 @@ event_route[xhttp:request] {
4.2. jsonrpc_exec(cmd)
- Execute JSONRPC command given as parameter.
+ Execute a JSON-RPC command given as a parameter.
- The parameter has to be a full valid JSONRPC document. It can be a
+ The parameter has to be a valid full JSON-RPC document. It can be a
dynamic string with variables. The result of the command can be
- accessed via $jsonrpl(key) variables.
+ accessed via $jsonrpl(key) pseudo variables.
Example 1.3. jsonrpc_exec usage
...
diff --git a/modules/jsonrpc-s/doc/jsonrpc-s_admin.xml b/modules/jsonrpc-s/doc/jsonrpc-s_admin.xml
index 77a0e3a..a12b153 100644
--- a/modules/jsonrpc-s/doc/jsonrpc-s_admin.xml
+++ b/modules/jsonrpc-s/doc/jsonrpc-s_admin.xml
@@ -16,8 +16,9 @@
<section>
<title>Overview</title>
<para>
- This module provides JSONRPC server over HTTP implementation,
- tailored for the needs of &kamailio;.
+ This module provides a JSON-RPC server over HTTP implementation,
+ tailored for the needs of &kamailio;. It implements the &kamailio;
+ RPC interface over JSON-RPC.
<para>
</para>
The JSONRPC-S module uses the xHTTP module to handle HTTP requests.
@@ -31,13 +32,13 @@
<para>
This module does not implement asynchronous RPC commands.
It is unlikely that asynchronous RPC commands will be executed
- from an JSONRPC over HTTP client.
+ from an JSON-RPC over HTTP client.
</para>
</listitem>
<listitem>
<para>
This module does not accept parameters embedded in a structure
- (see RPC documentation for more info about how parameters can be
+ (see the RPC documentation for more info about how parameters can be
passed to RPC).
</para>
</listitem>
@@ -80,7 +81,7 @@
<section>
<title><varname>pretty_format</varname> (int)</title>
<para>
- Pretty format for JSONRPC response document.
+ Pretty format for JSON-RPC response document.
</para>
<para>
<emphasis>
@@ -159,12 +160,12 @@ event_route[xhttp:request] {
<function moreinfo="none">jsonrpc_exec(cmd)</function>
</title>
<para>
- Execute JSONRPC command given as parameter.
+ Execute a JSON-RPC command given as a parameter.
</para>
<para>
- The parameter has to be a full valid JSONRPC document. It can
+ The parameter has to be a valid full JSON-RPC document. It can
be a dynamic string with variables. The result of the command
- can be accessed via $jsonrpl(key) variables.
+ can be accessed via $jsonrpl(key) pseudo variables.
</para>
<example>
<title><function>jsonrpc_exec</function> usage</title>