THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#246 - pua_reginfo adds duplicate cseq field in XML body
User who did this - Andrew Pogrebennyk (marduk)
----------
sorry I forgot to select a proper Category for this bug instead of 'core'.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=246#comment718
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.
A new Flyspray task has been opened. Details are below.
User who did this - Andrew Pogrebennyk (marduk)
Attached to Project - sip-router
Summary - pua_reginfo adds duplicate cseq field in XML body
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - I've had some problems trying to parse reginfo xml in branch 3.3 because of duplicate cseq field. AFAICS it is still there in master.
modules_k/pua_reginfo/usrloc_cb.c:
146 /* CSeq Attribute */
147 memset(buf, 0, sizeof(buf));
148 buf_len = snprintf(buf, sizeof(buf), "%d", ptr->cseq);
149 xmlNewProp(contact_node, BAD_CAST "cseq", BAD_CAST buf);
150
151 /* received Attribute */
152 memset(buf, 0, sizeof(buf));
153 buf_len = snprintf(buf, sizeof(buf), "%.*s", ptr->received.len, ptr->received.s);
154 xmlNewProp(contact_node, BAD_CAST "received", BAD_CAST buf);
155
156 /* path Attribute */
157 memset(buf, 0, sizeof(buf));
158 buf_len = snprintf(buf, sizeof(buf), "%.*s", ptr->path.len, ptr->path.s);
159 xmlNewProp(contact_node, BAD_CAST "path", BAD_CAST buf);
160
161 /* user_agent Attribute */
162 memset(buf, 0, sizeof(buf));
163 buf_len = snprintf(buf, sizeof(buf), "%.*s", ptr->user_agent.len, ptr->user_agent.s);
164 xmlNewProp(contact_node, BAD_CAST "user_agent", BAD_CAST buf);
165
166 /* CSeq Attribute */
167 memset(buf, 0, sizeof(buf));
168 buf_len = snprintf(buf, sizeof(buf), "%d", ptr->cseq);
169 xmlNewProp(contact_node, BAD_CAST "cseq", BAD_CAST buf);
Also there's duplicate default_domain definition in README.
modules_k/pua_reginfo/README:
3.1. default_domain(str)
The default domain for the registered users to be used when
constructing the uri for the registrar callback.
Default value is “NULL”.
Example 1.1. Set default_domain parameter
....
modparam("pua_bla", "default_domain", "kamailio.org")
....
3.2. default_domain(str)
The domain to be used to publish information about a user.
Example 1.2. Set default_domain parameter
....
modparam("pua_reginfo", "default_domain", "kamailio.org")
....
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=246
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#245 - kamailio tls debug error
User who did this - Shaobin.Feng (saxon_leo)
----------
Recomplied tls module with "-DTLS_WR_DEBUG -DTLS_RD_DEBUG",and restart one server.
1,connections achieved 90,000 without error log.
2,nothing can do, just wait...
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=245#comment717
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#245 - kamailio tls debug error
User who did this - Shaobin.Feng (saxon_leo)
----------
Thanks for your reply.
Well, there are 4 servers(Kamailio 3.2 on Ubuntu).This is my tls.cfg
[server:default]
method = SSLv23
verify_certificate = no
require_certificate = no
private_key = /usr/local/kamailio-3.2/etc/kamailio/tls/user/user-privkey.pem
certificate = /usr/local/kamailio-3.2/etc/kamailio/tls/user/user-cert.pem
#ca_list = ./modules/tls/cacert.pem
#crl = ./modules/tls/crl.pem
[client:default]
verify_certificate = no
require_certificate = no
At first, one server debug this log. Finally, all of them debug this log.(about 90,000 connections per server)
1,The server run almost 5 months.Did not debug this log(about 50,000 connections per server);
2,Another change as follows:
modparam("tls", "ssl_release_buffers", 1)
modparam("tls", "ssl_freelist_max_len", 0)
3,The connections did not grow anymore,which is predicted to increase.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=245#comment716
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#245 - kamailio tls debug error
User who did this - Klaus Darilion (klaus3000)
----------
Hm, maybe we have to add more debug messages to debug TLS issues.....
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=245#comment715
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#243 - Internal timer lags real time by the startup time
User who did this - Daniel-Constantin Mierla (miconda)
----------
So the re-sync, if it is the case, has to be done after child init. Is is for all processes or just for some, like first child which is used by some modules to load data at startup (like usrloc)?
Maybe you can commit the code for $TSi to be used for testing.
Indeed, a quick fix will be to return time() from ser_time(), but I would like to know the reason of the gap, not to hide something else and eventually to fix it properly.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=243#comment714
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#245 - kamailio tls debug error
User who did this - Shaobin.Feng (saxon_leo)
----------
New tls connection was closed pretty quick,when connections achieved 90,000. I have tested the connections number that it could achieve almost 260,000 connections.
Why did this error be made in operational environment? What's going on?
This just make me crazy.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=245#comment713
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#245 - kamailio tls debug error
User who did this - Shaobin.Feng (saxon_leo)
----------
Yes,just as what your say.
Well, the connections were decreased(60,000),but server also debug those error.
And,the system param are quite normal,like memory,I/O,disk,CPU,and so on.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=245#comment712
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#243 - Internal timer lags real time by the startup time
User who did this - Alex Hermann (axlh)
----------
ser_time() does not lag in the timer process itself, so all the code detecting timer lag is not noticing anything wrong . It does lag in the processes handling SIP messages.
I have no idea where this difference in time perception between processes comes from. As such i have no solution to fix ser_time() and intend to push a trivial fix replacing ser_time() with time() in modules/auth. This fix will at least prevent the creation of already expired nonces in challenges and rejecting nonces "from the future" in authentication attempts.
Anyway, in the entire sip-router source, time() is used 289 times, ser_time() only 12, so i guess it's not a big deal and maybe ser_time should be removed altogether. If ser_time() ever gets fixed, it is trivial to replace every occurance of time() with ser_time().
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=243#comment711
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#245 - kamailio tls debug error
User who did this - Klaus Darilion (klaus3000)
----------
So, the problems do not happen in the beginning, but only after some time and with a lot of established connections, right?
What if you drop connections, does Kamailio recover?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=245#comment710
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.