Module: sip-router
Branch: master
Commit: e09bc9d58b472e2becdba2b5745d26b703018b9a
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=e09bc9d…
Author: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Committer: Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>
Date: Wed May 2 17:48:47 2012 +0100
modules_k/rls: Updated module documentation
---
modules_k/rls/README | 9 ---------
modules_k/rls/doc/rls_admin.xml | 15 ++-------------
2 files changed, 2 insertions(+), 22 deletions(-)
diff --git a/modules_k/rls/README b/modules_k/rls/README
index 955b16d..62c9f96 100644
--- a/modules_k/rls/README
+++ b/modules_k/rls/README
@@ -267,15 +267,6 @@ modparam("rls", "xcap_db_url", "dbdriver://username:password@dbhost/dbname")
in a database, allowing scalability at the expense of speed. Mode 1 is
reserved.
- The RLS modules uses SQL BEGIN/COMMIT statements around related sets of
- database queries to make sure they are a single transaction when
- database only mode is used. This means you should ensure that automatic
- retries/reconnects are disabled for your database (for example, by
- setting the retries parameter for db_mysql or db_postgres to 0). This
- is needed because if the connection fails any unCOMMITed queries will
- be automatically rolled back by the database. This means that automatic
- retries could result in data inconsistencies.
-
Default value is “0”
Example 1.4. Set db_mode parameter
diff --git a/modules_k/rls/doc/rls_admin.xml b/modules_k/rls/doc/rls_admin.xml
index 18f784f..6386f10 100644
--- a/modules_k/rls/doc/rls_admin.xml
+++ b/modules_k/rls/doc/rls_admin.xml
@@ -171,19 +171,8 @@ modparam("rls", "xcap_db_url", "&exampledb;")
<para>
The module supports 2 modes of operation, high speed memory
based storage (mode 0), and database only (mode 2) where all
- data is stored in a database, allowing scalability at the expense of speed.
- Mode 1 is reserved.
- </para>
- <para>
- The RLS modules uses SQL BEGIN/COMMIT statements around related
- sets of database queries to make sure they are a single
- transaction when database only mode is used. This means you
- should ensure that automatic retries/reconnects are disabled
- for your database (for example, by setting the retries
- parameter for db_mysql or db_postgres to 0). This is needed
- because if the connection fails any unCOMMITed queries will
- be automatically rolled back by the database. This means that
- automatic retries could result in data inconsistencies.
+ data is stored in a database, allowing scalability at the
+ expense of speed. Mode 1 is reserved.
</para>
<para>
<emphasis> Default value is <quote>0</quote>
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#228 - notify cseq is not incremented
User who did this - Juha Heinanen (jh)
Reason for closing: Fixed
Additional comments about closing: Thanks to Anca, the bug is now fixed.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=228
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.
while doing some presence tests with master i noticed that when presence
server sends notify that terminates subscription due to change in xcap
authorization rules, cseq in the notify is same as in previous one.
rfc3261 says in 12.2.1 UAC Behavior:
Requests within a dialog MUST contain strictly monotonically
increasing and contiguous CSeq sequence numbers (increasing-by-one)
in each direction (excepting ACK and CANCEL of course, whose numbers
equal the requests being acknowledged or cancelled).
so this looks like a bug to twinkle (and me). below is sip debug from
twinkle (subscriber).
-- juha
+++ 2-5-2012 08:50:41.158705 INFO SIP ::process_sip_msg
Received from: tcp:192.98.103.10:5060
NOTIFY sip:jh@192.98.103.10:5074;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.98.103.10;branch=z9hG4bK4da2.6447f6ae08e84f0c0fbec6f7090757cc.0;i=c1
Via: SIP/2.0/TCP 127.0.0.1:5082;branch=z9hG4bK4da2.4e788af3000000000000000000000000.0
To: sip:jh@test.fi;tag=pqazy
From: sip:test@test.fi;tag=4a664ec84c547b2d0bc0fe8965f834e4-8a4b
CSeq: 2 NOTIFY
Call-ID: byxobtomskpzmos(a)siika.tutpro.com
Content-Length: 210
User-Agent: OpenXg Presence/XCAP Server (3.3.0-dev8 (x86_64/linux))
Max-Forwards: 69
Event: presence
Contact: <sip:127.0.0.1:5082;alias=127.0.0.1~35306~2;transport=tcp>
Subscription-State: active;expires=3670
Content-Type: application/pidf+xml
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" entity="sip:test@test.fi">
<tuple id="gxsdoz">
<status>
<basic>open</basic>
</status>
</tuple>
</presence>
---
+++ 2-5-2012 08:50:41.161169 INFO SIP ::send_sip_tcp
Send to: tcp:192.98.103.10:5060
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.98.103.10;branch=z9hG4bK4da2.6447f6ae08e84f0c0fbec6f7090757cc.0;i=c1,SIP/2.0/TCP 127.0.0.1:5082;branch=z9hG4bK4da2.4e788af3000000000000000000000000.0
To: <sip:jh@test.fi>;tag=pqazy
From: <sip:test@test.fi>;tag=4a664ec84c547b2d0bc0fe8965f834e4-8a4b
Call-ID: byxobtomskpzmos(a)siika.tutpro.com
CSeq: 2 NOTIFY
Server: Twinkle/1.4.2
Content-Length: 0
---
+++ 2-5-2012 08:51:00.381465 INFO SIP ::process_sip_msg
Received from: tcp:192.98.103.10:5060
NOTIFY sip:jh@192.98.103.10:5074;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.98.103.10;branch=z9hG4bK4da2.fd70b43b9da3c3b488208a61595b1112.0;i=c1
Via: SIP/2.0/TCP 127.0.0.1:5082;branch=z9hG4bK4da2.444a74e2000000000000000000000000.0
To: sip:jh@test.fi;tag=pqazy
From: sip:test@test.fi;tag=4a664ec84c547b2d0bc0fe8965f834e4-8a4b
CSeq: 2 NOTIFY
Call-ID: byxobtomskpzmos(a)siika.tutpro.com
Content-Length: 0
User-Agent: OpenXg Presence/XCAP Server (3.3.0-dev8 (x86_64/linux))
Max-Forwards: 69
Event: presence
Contact: <sip:127.0.0.1:5082;alias=127.0.0.1~35306~2;transport=tcp>
Subscription-State: terminated;reason=terminated
---
+++ 2-5-2012 08:51:00.381794 WARNING NORMAL t_subscription_dialog::recvd_request
CSeq seqnr is out of sequence.
Reveived seqnr: 2
Remote seqnr: 2
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 - notify cseq is not incremented
Task Type - Bug Report
Category - Module
Status - New
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - while doing some presence tests with master i noticed that when presence server sends notify that terminates subscription due to change in xcap authorization rules and pres_update_watchers() call, cseq in the notify is same as in previous one.
rfc3261 says in 12.2.1 UAC Behavior:
Requests within a dialog MUST contain strictly monotonically
increasing and contiguous CSeq sequence numbers (increasing-by-one)
in each direction (excepting ACK and CANCEL of course, whose numbers
equal the requests being acknowledged or cancelled).
so this looks like a bug to twinkle (and me). below is sip debug from twinkle (the subscriber).
-- juha
+++ 2-5-2012 08:50:41.158705 INFO SIP ::process_sip_msg
Received from: tcp:192.98.103.10:5060
NOTIFY sip:jh@192.98.103.10:5074;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.98.103.10;branch=z9hG4bK4da2.6447f6ae08e84f0c0fbec6f7090757cc.0;i=c1
Via: SIP/2.0/TCP 127.0.0.1:5082;branch=z9hG4bK4da2.4e788af3000000000000000000000000.0
To: sip:jh@test.fi;tag=pqazy
From: sip:test@test.fi;tag=4a664ec84c547b2d0bc0fe8965f834e4-8a4b
CSeq: 2 NOTIFY
Call-ID: byxobtomskpzmos(a)siika.tutpro.com
Content-Length: 210
User-Agent: OpenXg Presence/XCAP Server (3.3.0-dev8 (x86_64/linux))
Max-Forwards: 69
Event: presence
Contact: <sip:127.0.0.1:5082;alias=127.0.0.1~35306~2;transport=tcp>
Subscription-State: active;expires=3670
Content-Type: application/pidf+xml
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" entity="sip:test@test.fi">
<tuple id="gxsdoz">
<status>
<basic>open</basic>
</status>
</tuple>
</presence>
---
+++ 2-5-2012 08:50:41.161169 INFO SIP ::send_sip_tcp
Send to: tcp:192.98.103.10:5060
SIP/2.0 200 OK
Via: SIP/2.0/TCP 192.98.103.10;branch=z9hG4bK4da2.6447f6ae08e84f0c0fbec6f7090757cc.0;i=c1,SIP/2.0/TCP 127.0.0.1:5082;branch=z9hG4bK4da2.4e788af3000000000000000000000000.0
To: <sip:jh@test.fi>;tag=pqazy
From: <sip:test@test.fi>;tag=4a664ec84c547b2d0bc0fe8965f834e4-8a4b
Call-ID: byxobtomskpzmos(a)siika.tutpro.com
CSeq: 2 NOTIFY
Server: Twinkle/1.4.2
Content-Length: 0
---
+++ 2-5-2012 08:51:00.381465 INFO SIP ::process_sip_msg
Received from: tcp:192.98.103.10:5060
NOTIFY sip:jh@192.98.103.10:5074;transport=tcp SIP/2.0
Via: SIP/2.0/TCP 192.98.103.10;branch=z9hG4bK4da2.fd70b43b9da3c3b488208a61595b1112.0;i=c1
Via: SIP/2.0/TCP 127.0.0.1:5082;branch=z9hG4bK4da2.444a74e2000000000000000000000000.0
To: sip:jh@test.fi;tag=pqazy
From: sip:test@test.fi;tag=4a664ec84c547b2d0bc0fe8965f834e4-8a4b
CSeq: 2 NOTIFY
Call-ID: byxobtomskpzmos(a)siika.tutpro.com
Content-Length: 0
User-Agent: OpenXg Presence/XCAP Server (3.3.0-dev8 (x86_64/linux))
Max-Forwards: 69
Event: presence
Contact: <sip:127.0.0.1:5082;alias=127.0.0.1~35306~2;transport=tcp>
Subscription-State: terminated;reason=terminated
---
+++ 2-5-2012 08:51:00.381794 WARNING NORMAL t_subscription_dialog::recvd_request
CSeq seqnr is out of sequence.
Reveived seqnr: 2
Remote seqnr: 2
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=228
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.