sr-dev June 2011

sr-dev@lists.kamailio.org

32 participants
167 discussions

[tracker] Assignee added: [selects] @v.branch and others are not exported

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A user has added themself to the list of users assigned to this task. FS#138 - [selects] @v.branch and others are not exported User who did this - Iñaki Baz Castillo (ibc) http://sip-router.org/tracker/index.php?do=details&task_id=138 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.

12 years, 9 months

SIP Congestion/Overload Control

by Michael Hirschbichler

Hi all, I am currently developing a module for offering overload control support as proposed in http://tools.ietf.org/html/draft-ietf-soc-overload-control-02 . As background: the idea behind draft-ietf-soc-overload-control-02 is, that the upstream node ads parameters to the own Via-header to signal the next downstream node its ability to understand overload-control signalling. In case of overload of the downstream node, this node downstream node extends the own Via-Header (sent in replies to the upstream node) with e.g., a droprate. Well, and the job of the oc-module will be to 1) add "oc" to the Via-headers in requests (ok) 2) parse the Via-Header of the replies for oc-droprates and durations (ok) 3) keep a list of overloaded downstream-hosts, the droprate and the duration of the droprate (failed - see below) 4) its own droprate and the duration communicated to other upstream neighbors (failed - see below) The module "oc" (currently) exports the following commands and params static cmd_export_t cmds[]={ {"oc_check_enabled", ... {"oc_check_downstream_overloaded", ... {"oc_setdroprate", oc_setdroprate, ... {0,0,0,0,0} }; static param_export_t params[]={ {"oc_enabled", PARAM_INT, &OC_ENABLED}, {0,0,0} }; and the rpc-methods static rpc_export_t rpc_methods[] = { {"oc.stats",...}, {"oc.set_oc"...}, {"oc.set_oc_duration",...}, {0, 0, 0, 0} }; Well, and now my problem: Manipulating the own Via-Header is (in my understanding) a very tricky part: in msg_translator.c the functions "build_req_buf_from_sip_req()" and "build_res_bug_from_sip_res()" are responsible for adding the own Via-Header and its parameters. So, I had to add a function call to functions inside my oc-module: oc_via_manipulation() and oc_builder(). And here is the problem: I cannot access the shared memory variables of the oc-module like oc_duration and oc_droprate when I call the oc_via_manipulation() and oc_builder()-functions from within "build_req_buf_from_sip_req()" and "build_res_bug_from_sip_res()". My conclusion was, that when calling functions of the oc-module from within the ser-"core", the shared-memory variables set by rpc_methods, cmds and params are not accessible. Honestly, I have now no idea how to continue and would be happy on every idea, br Michael -- Michael Hirschbichler, Mag. Dipl.-Ing. Institute of Telecommunications Vienna University of Technology A-1040 Wien, Favoritenstr. 9-11/388 Phone: +43 1 58801 38846

12 years, 9 months

[tracker] Comment added: kamailio 3.1.3 Presence + XCAP problem, is it a bug?

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#133 - kamailio 3.1.3 Presence + XCAP problem, is it a bug? User who did this - Daniel-Constantin Mierla (miconda) ---------- Thanks for analyzing further and providing a patch. I will look soon over it. ---------- More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=133#comment231 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.

12 years, 9 months

[tracker] User took ownership: kamailio 3.1.3 Presence + XCAP problem, is it a bug?

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. Daniel-Constantin Mierla has taken ownership of the following task: FS#133 - kamailio 3.1.3 Presence + XCAP problem, is it a bug? More information can be found at the following URL: https://sip-router.org/tracker/index.php?do=details&task_id=133 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.

12 years, 9 months

async module -- workers

by Matthew Williams

Hi Daniel, Am I correct that t_continue continues processing in the process that calls it? If so, would it make sense for the async module to have an api for other asynchronous modules to hand off to its worker pool before calling t_continue? Or would it be better for each module to have its own pool of workers? Thanks!

12 years, 9 months

[tracker] Task opened: app_python doesn't work

by sip-router

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - arnaud chong (shine) Attached to Project - sip-router Summary - app_python doesn't work Task Type - Bug Report Category - Module Status - Unconfirmed Assigned To - Operating System - Linux Severity - Medium Priority - Normal Reported Version - 3.1 Due in Version - Undecided Due Date - Undecided Details - Hello, When I want to load a python script via the app_python module, kamailio crashes. The module uses dirname & basename (http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blob;f=modules/… lines 103-106). " Both dirname() and basename() may modify the contents of path, so it may be desirable to pass a copy when calling one of these functions." (quote from the manual). The path is actually changed and /my/path/blih.py becomes /my/patrh after the first dirname, so the return of basename is wrong and everything after is broken. More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=137 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.

12 years, 9 months

Virtual Assistant Vacancy

by raf＠iptel.org

Spam detection software, running on the system "mail.iptel.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi there! Let me present you one of the largest worldwide enterprises where I work as a manager of HR department. This company is connected with different areas of activity, such as: - estate property - logistics - private undertaking service - etc. [...] Content analysis details: (17.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [113.166.214.112 listed in zen.spamhaus.org] 0.4 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL 0.8 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server [113.166.214.112 listed in dnsbl.sorbs.net] 0.0 T_RCVD_IN_SEMBLACK RBL: Received from an IP listed in bl.spameatingmonkey.net [113.166.214.112 listed in bl.spameatingmonkey.net] 1.4 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT [113.166.214.112 listed in bb.barracudacentral.org] 0.0 T_URIBL_SEM_FRESH_10 Contains a domain registered less than 10 days ago [URIs: europ-joblist.com] 0.0 T_URIBL_SEM_FRESH_15 Contains a domain registered less than 15 days ago [URIs: europ-joblist.com] 1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist [URIs: europ-joblist.com] 1.5 URIBL_RHS_DOB Contains an URI of a new domain (Day Old Bread) [URIs: europ-joblist.com] 0.0 T_URIBL_SEM_FRESH Contains a domain registered less than 5 days ago [URIs: europ-joblist.com] 1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist [URIs: europ-joblist.com] 0.0 FSL_HELO_NON_FQDN_1 FSL_HELO_NON_FQDN_1 3.8 HELO_LOCALHOST HELO_LOCALHOST 0.7 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines 1.6 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist [URIs: europ-joblist.com] 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5240] 0.0 T_URIBL_BLACK_OVERLAP T_URIBL_BLACK_OVERLAP

12 years, 9 months

Database Management Position

by ser-bugs＠iptel.org

Spam detection software, running on the system "mail.iptel.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Salute! I am the HR manager and I am appealing to you in the name of the large-scale and first-rate company. This company can be found in various branches, such as: * real estate * founding and abatement of enterprises * private undertaking service * etc. [...] Content analysis details: (15.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net [Blocked - see <http://www.spamcop.net/bl.shtml?190.134.177.224>] 3.3 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL [190.134.177.224 listed in zen.spamhaus.org] 0.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [190.134.177.224 listed in dnsbl.sorbs.net] 0.0 T_RCVD_IN_SEMBLACK RBL: Received from an IP listed in bl.spameatingmonkey.net [190.134.177.224 listed in bl.spameatingmonkey.net] 1.4 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT [190.134.177.224 listed in bb.barracudacentral.org] 0.0 T_URIBL_SEM_FRESH_10 Contains a domain registered less than 10 days ago [URIs: europ-joblist.com] 0.0 T_URIBL_SEM_FRESH_15 Contains a domain registered less than 15 days ago [URIs: europ-joblist.com] 1.6 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist [URIs: europ-joblist.com] 1.7 URIBL_BLACK Contains an URL listed in the URIBL blacklist [URIs: europ-joblist.com] 1.5 URIBL_RHS_DOB Contains an URI of a new domain (Day Old Bread) [URIs: europ-joblist.com] 0.0 T_URIBL_SEM_FRESH Contains a domain registered less than 5 days ago [URIs: europ-joblist.com] 1.7 URIBL_DBL_SPAM Contains an URL listed in the DBL blocklist [URIs: europ-joblist.com] 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines 1.5 BAYES_60 BODY: Bayes spam probability is 60 to 80% [score: 0.6181] 1.0 RDNS_DYNAMIC Delivered to internal network by host with dynamic-looking rDNS 0.0 T_URIBL_BLACK_OVERLAP T_URIBL_BLACK_OVERLAP

12 years, 9 months

new module: async - asynchronous SIP request processing in cfg

by Daniel-Constantin Mierla

Hello, a new module is now in GIT master branch, named async. Its purpose is to provide asynchronous SIP request processing using t_suspend()/t_continue() mechanism from tm module. While the tm module had it for quite some time, it was not available for usage in configuration file. There are two functions implemented by now: - async_route(routename, interval) - execute asynchronously a route block after a time interval - aync_sleep(interval) - sleep asynchronously for a time interval and then resume SIP request processing See the readme for more details: http://kamailio.org/docs/modules/devel/modules/async.html Cheers, Daniel -- Daniel-Constantin Mierla -- http://www.asipto.com http://linkedin.com/in/miconda -- http://twitter.com/miconda

12 years, 9 months

git:master: async module: mention $apv and $xavp in documentation Overview.

by I�aki Baz Castillo

Module: sip-router Branch: master Commit: 42620ff1671b0b36b6ff8ee6e02e33c866522f55 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=42620ff… Author: Iñaki Baz Castillo <ibc(a)aliax.net> Committer: Iñaki Baz Castillo <ibc(a)aliax.net> Date: Mon Jun 27 17:09:03 2011 +0200 async module: mention $apv and $xavp in documentation Overview. --- modules/async/README | 4 ++-- modules/async/doc/async_admin.xml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/async/README b/modules/async/README index e01da48..a4e5e46 100644 --- a/modules/async/README +++ b/modules/async/README @@ -67,8 +67,8 @@ Chapter 1. Admin Guide Note that after invoking the an asyncronous operation, the processing will continue later, in another application process. Therefore, do not rely on variables stored in private memory, used shared memory if you - want to get values after the processing is resumend (e.g., $shv(...) of - htable $sht(...)). + want to get values after the processing is resumend (e.g., $avp(...), + $xavp(...), $shv(...), htable $sht(...)). 2. Dependencies diff --git a/modules/async/doc/async_admin.xml b/modules/async/doc/async_admin.xml index 3fbaeab..71e3283 100644 --- a/modules/async/doc/async_admin.xml +++ b/modules/async/doc/async_admin.xml @@ -26,8 +26,8 @@ Note that after invoking the an asyncronous operation, the processing will continue later, in another application process. Therefore, do not rely on variables stored in private memory, used shared memory if you - want to get values after the processing is resumend (e.g., $shv(...) - of htable $sht(...)). + want to get values after the processing is resumend (e.g., $avp(...), + $xavp(...), $shv(...), htable $sht(...)). </para> </section>

12 years, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2011