THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#254 - uacreg functionality: kamailio sending zeroes in header
User who did this - Rus (Sfinx)
----------
My shame: it was bug in tcpdump-4.0, upgrading to tcpdump-4.3 show full packet ;)
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=254#comment752
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#254 - uacreg functionality: kamailio sending zeroes in header
User who did this - Daniel-Constantin Mierla (miconda)
----------
I just did a quick test and worked fine for me:
<code>
REGISTER sip:192.168.178.100 SIP/2.0.
Via: SIP/2.0/UDP 127.0.0.1;branch=z9hG4bKc91d.d7e8f323.0.
To: sip:1qaz@192.168.178.100.
From: sip:1qaz@192.168.178.100;tag=533cb9e91f4b999cf76861cbb9ed54ed-1aa5.
CSeq: 10 REGISTER.
Call-ID: 40dfe6702b91e473-18933(a)127.0.0.1.
Content-Length: 0.
User-Agent: kamailio (3.4.0-dev5 (x86_64/darwin)).
Contact: <sip:1qaz@127.0.0.1:5086>.
Expires: 600.
.
</code>
My record in uacreg is:
<code>
*************************** 1. row ***************************
id: 1
l_uuid: 1qaz
l_username: 1qaz
l_domain: test.com
r_username: 1qaz
r_domain: 192.168.178.100
realm: test.com
auth_username: 1qaz
auth_password: 1qaz
auth_proxy: sip:127.0.0.1:6080
expires: 600
</code>
Can you set debug=4 in config, keep only one record in uacreg table and add the log messages here?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=254#comment751
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.
Module: sip-router
Branch: master
Commit: 15fdde4fa1d662228568cc92e375d94dd86f2578
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=15fdde4…
Author: Olle E. Johansson <oej(a)edvina.net>
Committer: Olle E. Johansson <oej(a)edvina.net>
Date: Mon Nov 19 15:53:17 2012 +0100
AUTH minor documentation updates
---
modules/auth/README | 11 ++++++-----
modules/auth/doc/params.xml | 12 ++++++------
2 files changed, 12 insertions(+), 11 deletions(-)
diff --git a/modules/auth/README b/modules/auth/README
index fa90d51..a429a53 100644
--- a/modules/auth/README
+++ b/modules/auth/README
@@ -443,15 +443,16 @@ modparam("auth", "otn_in_flight_order", 23) # 8 Mb (1Mb memory)
1.3.10. secret (string)
- Secret phrase used to calculate the nonce value. The default is to use
- a random value generated from the random source in the core.
+ Secret phrase used to calculate the nonce value used to challenge the
+ client for authentication.
If you use multiple servers in your installation, and would like to
authenticate on the second server against the nonce generated at the
first one its necessary to explicitly set the secret to the same value
- on all servers. However, the use of a shared (and fixed) secret as
- nonce is insecure, much better is to stay with the default. Any clients
- should send the reply to the server that issued the request.
+ on all servers. However, as the use of a shared (and fixed) secret as
+ nonce is insecure, it is much better is to stay with the default. Any
+ clients should send the authenticated request to the server that issued
+ the challenge.
Default value is randomly generated string.
diff --git a/modules/auth/doc/params.xml b/modules/auth/doc/params.xml
index 2fd35ba..f9c1f8a 100644
--- a/modules/auth/doc/params.xml
+++ b/modules/auth/doc/params.xml
@@ -548,15 +548,15 @@ modparam("auth", "otn_in_flight_order", 23) # 8 Mb (1Mb memory)
<section id="auth.secret">
<title><varname>secret</varname> (string)</title>
- <para>Secret phrase used to calculate the nonce value.
- The default is to use a random value generated from the random source
- in the core.</para>
+ <para>Secret phrase used to calculate the nonce value used to challenge
+ the client for authentication.</para>
<para>If you use multiple servers in your installation, and would like to
authenticate on the second server against the nonce generated at the
first one its necessary to explicitly set the secret to the same value
- on all servers. However, the use of a shared (and fixed) secret as
- nonce is insecure, much better is to stay with the default. Any
- clients should send the reply to the server that issued the request.
+ on all servers. However, as the use of a shared (and fixed) secret as
+ nonce is insecure, it is much better is to stay with the default. Any
+ clients should send the authenticated request to the server that
+ issued the challenge.
</para>
<para>
Default value is randomly generated string.
Friends,
I've been trying to play with the XMLRPC module in Kamailio. It turns out that the answers in some modules are not XML-rpc compliant, so my PHP based XMLrpc library only shows one part of the response.
XMLrpc standards says that there has to be ONE and only ONE structure in a response. When running "htable.dump" I get one param struct per object. There should be a common structure encapsultating all the responses.
It seems like the output of sercmd allows this, but XMLrpc does not.
One quick fix would be to change the xmlrpc module and add an encapsulating structure. This would of course break a lot of clients. We could make it an option so that we're backwards compatible, like a "xmlrpccompliant" modparam. Another fix would be to change all the modules, but that would also change the SER RPC output, which would be a far bigger change.
Anyone that has seen the same issues? Agree with a fix?
/O
Hi!
I would like to silence the debugging from Kamailio while still have my own xlog("L_DBG", ""); being sent to syslog.
The corelog config parameter seems to exist to limit what the kamailio server puts in syslog, while debug is valid for both core and my script logs.
If I set corelog to -1 and debug to 3, I would expect to get no core L_DBG messages in syslog, but it is full with it...
Is this because corelog is not fully implemented across Kamailio or are my assumptions wrong?
The corelog documentation in the cookbook says that the corelog is used to print "some log messages". Would it be worth the effort to make this kamailio-wide?
/O
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#254 - uacreg functionality: kamailio sending zeroes in header
User who did this - Rus (Sfinx)
----------
Sure, but I think this is standart parameters :
Parameters :
modparam("uac", "reg_db_url", SOME_MYSQL_DBURL)
modparam("uac", "reg_timer_interval", 60)
modparam("uac", "reg_contact_addr", "sip.server.com:5060")
User Record :
insert into uacreg (l_uuid, l_username, l_domain, r_username, r_domain, realm, auth_username, auth_password, auth_proxy, expires) values ('XXXXXXXX', 'line-XXXXXXXX', 'demo.host.com', 'XXXXXXXX', 'sip.server.com', 'sip.server.com', 'XXXXXXXX', 'some_secret', 'sip:sip.server.com', 60);
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=254#comment750
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.