sr-dev September 2009

sr-dev@lists.kamailio.org

32 participants
207 discussions

git:master: tls mk cert script: typo fix
by Andrei Pelinescu-Onciul 21 Sep '09

21 Sep '09

Module: sip-router Branch: master Commit: 8205f043c43282a209673364961d23c6b74cee72 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=8205f04… Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Committer: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Date: Mon Sep 21 09:16:14 2009 +0200 tls mk cert script: typo fix --- modules/tls/sip-router_cert.sh | 4 ++-- modules_s/tls/ser_cert.sh | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/tls/sip-router_cert.sh b/modules/tls/sip-router_cert.sh index 4bfb8fc..df08caa 100755 --- a/modules/tls/sip-router_cert.sh +++ b/modules/tls/sip-router_cert.sh @@ -28,12 +28,12 @@ MAILNAME=`cat /etc/mailname 2> /dev/null || echo $FQDN` # test if we have the normal or enhanced getopt getopt -T >/dev/null -if [ $? == 4 ]; then +if [ $? = 4 ]; then LONGOPTS_SUPPORTED=1 fi longopts() { - if [ -z "${LONGOPTS_SUPPORTED}"]; then + if [ -z "${LONGOPTS_SUPPORTED}" ]; then exit; fi case "$1" in diff --git a/modules_s/tls/ser_cert.sh b/modules_s/tls/ser_cert.sh index 4bfb8fc..df08caa 100755 --- a/modules_s/tls/ser_cert.sh +++ b/modules_s/tls/ser_cert.sh @@ -28,12 +28,12 @@ MAILNAME=`cat /etc/mailname 2> /dev/null || echo $FQDN` # test if we have the normal or enhanced getopt getopt -T >/dev/null -if [ $? == 4 ]; then +if [ $? = 4 ]; then LONGOPTS_SUPPORTED=1 fi longopts() { - if [ -z "${LONGOPTS_SUPPORTED}"]; then + if [ -z "${LONGOPTS_SUPPORTED}" ]; then exit; fi case "$1" in

1 0

git:master: tls: makefile fix
by Andrei Pelinescu-Onciul 21 Sep '09

21 Sep '09

Module: sip-router Branch: master Commit: ba3d64ff8d1ec6904df906012d1e9f89e5abdc8a URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=ba3d64f… Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Committer: Andrei Pelinescu-Onciul <andrei(a)iptel.org> Date: Mon Sep 21 09:17:04 2009 +0200 tls: makefile fix - wrong order (extra rules should be placed after include Makefile.modules) Closes FlySpray#17. --- modules/tls/Makefile | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/modules/tls/Makefile b/modules/tls/Makefile index 213a484..8fac654 100644 --- a/modules/tls/Makefile +++ b/modules/tls/Makefile @@ -16,6 +16,11 @@ LIBS+= -L$(LOCALBASE)/lib -L$(LOCALBASE)/ssl/lib -lssl -lcrypto \ # have to add -lz -lkrb5 (zlib and kerberos5). # E.g.: make TLS_HOOKS=1 TLS_EXTRA_LIBS="-lz -lkrb5" + +DEFS+=-DOPENSER_MOD_INTERFACE + +include ../../Makefile.modules + $(cfg_prefix)/$(cfg_dir): mkdir -p $(cfg_prefix)/$(cfg_dir) @@ -24,8 +29,3 @@ install-cfg: $(cfg_prefix)/$(cfg_dir) ./$(SCR_NAME)_cert.sh -d $(cfg_prefix)/$(cfg_dir) install: install-cfg - - -DEFS+=-DOPENSER_MOD_INTERFACE - -include ../../Makefile.modules

1 0

[tracker] Assignee added: Makefile error prevent tls module from being build
by sip-router 21 Sep '09

21 Sep '09

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A user has added themself to the list of users assigned to this task. FS#17 - Makefile error prevent tls module from being build User who did this - Nils Ohlmeier (nils) http://sip-router.org/tracker/index.php?do=details&task_id=17 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: Makefile error prevent tls module from being build
by sip-router 21 Sep '09

21 Sep '09

1 0

[tracker] Comment added: TLS modul problem
by sip-router 20 Sep '09

20 Sep '09

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#14 - TLS modul problem User who did this - Nils Ohlmeier (nils) ---------- I saw the same log message several times as well when I tested TLS support at the SIPit. But I did not debugged the issue that far. In my case I saw additionally saw that SER tried to open a connection from an IP address which is wasn't listening on (it was configured to use an alias IP only, but according to the logs for new TLS connections it used the IP address of the real interface to which the alias IP belonged). ---------- More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=14#comment6 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: Local 487 forwarded upstream (Attachment added)
by sip-router 20 Sep '09

20 Sep '09

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Nils Ohlmeier (nils) Attached to Project - sip-router Summary - Local 487 forwarded upstream Task Type - Bug Report Category - tm Status - Assigned Assigned To - Andrei Pelinescu-Onciul Operating System - Mac OS X (Darwin) Severity - High Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - Setup: - INVITE gets forked to three destinations - branch one answers the call - the two remaining branches are canceled locally - branch two gets canceled normally - branch three answers only the CANCEL request - meanwhile the call is setup and even teared down - finally branch three sends a 487 - tm module does not match the transaction and forwards the 487 upstream Note: the setup included the new topoh module, but that should hopefully does not make any difference. Please find attached a log file on debug level from the scenario described above. 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=16 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] Assignee added: Local 487 forwarded upstream
by sip-router 20 Sep '09

20 Sep '09

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A user has added themself to the list of users assigned to this task. FS#16 - Local 487 forwarded upstream User who did this - Nils Ohlmeier (nils) http://sip-router.org/tracker/index.php?do=details&task_id=16 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] Assignee added: Proto names are causing parser errors
by sip-router 20 Sep '09

20 Sep '09

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A user has added themself to the list of users assigned to this task. FS#15 - Proto names are causing parser errors User who did this - Nils Ohlmeier (nils) http://sip-router.org/tracker/index.php?do=details&task_id=15 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: Proto names are causing parser errors
by sip-router 20 Sep '09

20 Sep '09

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Nils Ohlmeier (nils) Attached to Project - sip-router Summary - Proto names are causing parser errors Task Type - Bug Report Category - Core Status - Assigned Assigned To - Andrei Pelinescu-Onciul Operating System - All Severity - Medium Priority - Normal Reported Version - Development Due in Version - Undecided Due Date - Undecided Details - When the configuration file contains a statement like this: if (proto==TCP) { this is causing a parser errors at the startup of SER like this: 0(26225) : <core> [cfg.y:3163]: parse error in config file /home/lando/sip-router/etc/sip-router-basic.cfg, line 76, column 13-15: syntax error 0(26225) : <core> [cfg.y:3163]: parse error in config file /home/lando/sip-router/etc/sip-router-basic.cfg, line 76, column 13-15: number expected 0(26225) : <core> [cfg.y:3166]: parse error in config file /home/lando/sip-router/etc/sip-router-basic.cfg, line 76, column 16: bad expression 0(26225) : <core> [cfg.y:3166]: parse error in config file /home/lando/sip-router/etc/sip-router-basic.cfg, line 76, column 16: invalid route statement Currently only statements like this are working: if (proto==2) { More information can be found at the following URL: http://sip-router.org/tracker/index.php?do=details&task_id=15 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

[LCR] next_gw() doesn't update $ru
by Iñaki Baz Castillo 19 Sep '09

19 Sep '09

Hi, in failure route I call next_gw(), it success and the request is sent to a second gateway (inspecting with ngrep I see that the sent request has the gw IP as RURI). But if I print (xlog) $ru it still shows the previously selected gw (the first one). This is, the behaviour is correct but $ru is not updated in the script process. I show an example which hopefully would show the issue (xlogs). Basically the script invokes ROUTE_GW which uses LCR to select the first gw, sets FAILURE_ROUTE_GW and calls ROUTE_DEFAULT (in which t_relay is done). FAILURE_ROUTE block also sets FAILURE_ROUTE block, uses LCR to select a new gw and calls to ROUTE_DEFAULT: INVITE sip:1234@sip.mydomain.org - From: ibc - from 222.230.253.254:48254 (Twinkle/1.4.2) [ROUTE GW] LCR: Selected gw ($rd): 222.230.249.81 [ROUTE DEFAULT] $ru = sip:1234@222.230.249.81:0 <---- Seems to be OK 500 "Internal Error" from 222.230.249.81:5060 (GW1) [FAILURE ROUTE GW] CRITICAL: LCR: 500 replied by gw 222.230.249.81 --> Doing failover... [FAILURE ROUTE GW] Selected gw ($rd): 222.230.249.81 <----- WRONG !!! [ROUTE DEFAULT] $ru = sip:1234@222.230.249.81:0 <----- WRONG !!! 503 "Service Unavailable" from 99.121.79.216:5060 (GW2) <----- But the used gw is the expected. [FAILURE ROUTE GW] CRITICAL: LCR: 503 replied by gw 99.121.79.216 --> Doing failover... [FAILURE ROUTE GW] CRITICAL: LCR: No gateways available --> 503 Kamailio 1.5 rev 5925. -- Iñaki Baz Castillo <ibc(a)aliax.net>

3 8

← Newer
1
...
7
8
9
10
11
12
13
...
21
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev September 2009