sr-dev May 2012

sr-dev@lists.kamailio.org

29 participants
174 discussions

git:master: xhttp: regenerate readme after commit c386968d40aeef9c8
by Henning Westerholt 29 May '12

29 May '12

Module: sip-router Branch: master Commit: 0219f1cda6cf51fbc5d0aa3cc0b575e8cba7f869 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=0219f1c… Author: Henning Westerholt <hw(a)kamailio.org> Committer: Henning Westerholt <hw(a)kamailio.org> Date: Tue May 29 18:08:39 2012 +0200 xhttp: regenerate readme after commit c386968d40aeef9c8 --- modules/xhttp/README | 19 +++++++++++++++---- 1 files changed, 15 insertions(+), 4 deletions(-) diff --git a/modules/xhttp/README b/modules/xhttp/README index c8c8f35..ae77d93 100644 --- a/modules/xhttp/README +++ b/modules/xhttp/README @@ -28,7 +28,8 @@ Alex Balashov 3. Dependencies 3.1. Kamailio Modules - 3.2. External Libraries or Applications + 3.2. Kamailio Core Settings + 3.3. External Libraries or Applications 4. Parameters @@ -54,7 +55,8 @@ Chapter 1. Admin Guide 3. Dependencies 3.1. Kamailio Modules - 3.2. External Libraries or Applications + 3.2. Kamailio Core Settings + 3.3. External Libraries or Applications 4. Parameters @@ -109,14 +111,23 @@ Chapter 1. Admin Guide 3. Dependencies 3.1. Kamailio Modules - 3.2. External Libraries or Applications + 3.2. Kamailio Core Settings + 3.3. External Libraries or Applications 3.1. Kamailio Modules The following modules must be loaded before this module: * sl - stateless reply. -3.2. External Libraries or Applications +3.2. Kamailio Core Settings + + SIP requires a Content-Length header for TCP transport. But most HTTP + clients do not set the content length for normal GET requests. + Therefore, the core must be configured to allow incoming requests + without content length header: + * tcp_accept_no_cl=yes + +3.3. External Libraries or Applications The following libraries or applications must be installed before running Kamailio with this module loaded:

1 0

git:master: add tcp_accept_no_cl=yes to xhttp description
by Klaus Darilion 29 May '12

29 May '12

Module: sip-router Branch: master Commit: c386968d40aeef9c851e896dd6ada9713d9d3c01 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=c386968… Author: Klaus Darilion <klaus.mailinglists(a)pernau.at> Committer: Klaus Darilion <klaus.mailinglists(a)pernau.at> Date: Tue May 29 15:21:23 2012 +0000 add tcp_accept_no_cl=yes to xhttp description --- modules/xhttp/doc/xhttp.txt.html | 93 +++++++++++++++++++++++++++++++++++++ modules/xhttp/doc/xhttp_admin.xml | 15 ++++++ 2 files changed, 108 insertions(+), 0 deletions(-) Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=c38…

1 0

[tracker] Comment added: kamailio crah [pass_fd.c:293]: ERROR: receive_fd: EOF on 46
by sip-router 29 May '12

29 May '12

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#234 - kamailio crah [pass_fd.c:293]: ERROR: receive_fd: EOF on 46 User who did this - David Kovarik (kovik) ---------- kamailio -V version: kamailio 3.3.0-pre2 (x86_64/linux) 62baa1 flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 62baa1 compiled on 09:39:56 May 17 2012 with gcc 4.4.5 ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=234#comment650 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.

1 0

[tracker] Task opened: kamailio crah [pass_fd.c:293]: ERROR: receive_fd: EOF on 46 (Attachment added)
by sip-router 29 May '12

29 May '12

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - David Kovarik (kovik) Attached to Project - sip-router Summary - kamailio crah [pass_fd.c:293]: ERROR: receive_fd: EOF on 46 Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Critical Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - kamailio crash with [pass_fd.c:293]: ERROR: receive_fd: EOF on 46 after auth INVITE from different port from 3g network First INVITE come from port 2833 and auth INVITE from port 56393 One or more files have been attached. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=234 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.

1 0

git:master: registrar(k): check if realm prefix len is >0
by Daniel-Constantin Mierla 29 May '12

29 May '12

Module: sip-router Branch: master Commit: 319a966497a0dc85b5f1a2e43ecae56cd515b902 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=319a966… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: Tue May 29 11:11:49 2012 +0200 registrar(k): check if realm prefix len is >0 --- modules_k/registrar/common.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/modules_k/registrar/common.c b/modules_k/registrar/common.c index 3cd235f..c8a1948 100644 --- a/modules_k/registrar/common.c +++ b/modules_k/registrar/common.c @@ -95,7 +95,7 @@ int extract_aor(str* _uri, str* _a, sip_uri_t *_pu) /* strip prefix (if defined) */ realm_prefix.s = cfg_get(registrar, registrar_cfg, realm_pref).s; realm_prefix.len = cfg_get(registrar, registrar_cfg, realm_pref).len; - if (realm_prefix.len && realm_prefix.len<puri->host.len && + if (realm_prefix.len>0 && realm_prefix.len<puri->host.len && (memcmp(realm_prefix.s, puri->host.s, realm_prefix.len)==0) ) { memcpy(aor_buf + _a->len, puri->host.s + realm_prefix.len, puri->host.len - realm_prefix.len);

1 0

planning the release of v3.3.0
by Daniel-Constantin Mierla 29 May '12

29 May '12

Hello, looking at the volume of reported issues on mailing lists and tracker, upcoming v3.3.0 seems to go well. I have few items on my to-do reported on the mailing list. Otherwise, in my side, I have 3.3.0 running in a production-like environment for about 4 weeks without problems and another one in a pre-production phase. Having in consideration all these, I propose to branch 3.3 on June 11. If everything looks very good at that time (or actually few days before), I think we can do the release also by that date. If not, we can do it a week later. Branching will allow new features development on git master, there are already several contributed patches with new features flowing around on mailing lists and tracker. Therefore, if you are aware of any issue, please report asap on mailing list (sr-dev) or tracker (preferable - http://sip-router.org/tracker/). Other suggestions about planning the release 3.3.0 are welcome, as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu

1 0

shm_free - not setting pointer to zero?
by Richard Good 28 May '12

28 May '12

Hi Is there any reason why shm_free does not set the pointer it is freeing to zero once it is free-ed? Code like: *if (pointer) { shm_free(pointer);* Is not really useful seen as how shm_free does not set the pointer to zero - any double free will still cause a crash. I suppose it forces the developer to be careful with memory management - is this the only reason? Regards Richard. This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at http://www.smilecoms.com/disclaimer

2 1

Kamailio for Debian 7 - deadline
by Daniel Pocock 27 May '12

27 May '12

I notice there has been some attempts to package Kamailio for Debian: http://anonscm.debian.org/viewvc/pkg-voip/kamailio/trunk/debian/control?vie… The Debian 7 freeze is likely to come in mid-June, that would suggest some initial version of the package needs to be uploaded to the FTP queue within the next 1-2 weeks at the latest http://lists.debian.org/debian-devel-announce/2012/05/msg00004.html Are other people interested in pursuing this, even if it is just testing the package?

4 9

T M docs for 3.2
by Olle E. Johansson 25 May '12

25 May '12

" 1.4.6. delete_timer (integer) Time after which a to-be-deleted transaction currently ref-ed by a process will be tried to be deleted again (in milliseconds). Note: this parameter is obsolete for ser 2.1 (in 2.1 the transaction is deleted the moment it's not referenced anymore). Default value is 200 milliseconds." What's the status of the delete_timer in 3.2 and devel (3.3) ? We should propably update docs here. /O

2 2

New Presence Event Package
by David Lake (dlake) 24 May '12

24 May '12

Hi Please excuse the newbie posting, but I really need some help ! I want to expand Kamailio to act as an OMA PoC Server. To do this, I need to build some floor-control using TBCP and add logic to select speakers, etc, which I can do. But.... Before I even do that, I need to support the PUBLISH event "poc-settings" This is where the client declares that it is a PoC device and what it's status is (RFC 4354). I've read, re-read and re-re-read the documentation, but the architecture and how it impacts the various modules is still unclear to me. Here are my questions: 1) I can see that presence_xml is where the "presence" and "winfo...." events are handled. Do I need to expand this to include poc-settings ? 2) The poc-settings per client are sent in the XML body. Where/how does that get parsed, and is that then stored in the MySQL database ? Does that mean that I need to expand the parser to handle the new poc-settings message ? Does that also mean that I need to add new elements to my openser database ? Thanks in advance David

2 1

← Newer
1
2
3
4
5
6
7
8
...
18
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2012