Module: sip-router
Branch: master
Commit: a0ce24fed910050ea3210ded0cc94c9c059e6b55
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=a0ce24f…
Author: Juha Heinanen <jh(a)tutpro.com>
Committer: Juha Heinanen <jh(a)tutpro.com>
Date: Wed Jun 24 22:01:55 2009 +0300
* Core: ser -> sip-router changes
* Changed ser to sip-router.
* Updated mailing lists and URLs.
---
sip-router.cfg.5 | 29 ++++++++++++++---------------
1 files changed, 14 insertions(+), 15 deletions(-)
diff --git a/sip-router.cfg.5 b/sip-router.cfg.5
index e4de8ba..8c89c3f 100644
--- a/sip-router.cfg.5
+++ b/sip-router.cfg.5
@@ -1,16 +1,16 @@
.\" $Id$
-.TH ser.cfg 5 15.07.2002 ser "Sip Express Router"
+.TH sip-router.cfg 5 15.07.2002 sip-router "Sip Express Router"
.\" Process with
-.\" groff -man -Tascii ser.cfg.5
+.\" groff -man -Tascii sip-router.cfg.5
.\"
.SH NAME
-ser.cfg \- ser configuration file
+sip-router.cfg \- sip-router configuration file
.SH SYNOPSIS
-.I /etc/ser/ser.cfg
+.I /etc/sip-router/sip-router.cfg
.SH DESCRIPTION
-.B ser
+.B sip-router
reads the configuration data from
-.I /etc/ser/ser.cfg
+.I /etc/sip-router/sip-router.cfg
(or the file specified with
.B \-f
on the command line).
@@ -24,27 +24,26 @@ This manual page is incomplete. For further information please read the
.I Ser User Guide (http://www.iptel.org/ser/admin.html).
.SH FILES
-.I /etc/ser/ser.cfg
+.I /etc/sip-router/sip-router.cfg
.SH AUTHORS
see
-.B /usr/share/doc/ser/AUTHORS
+.B /usr/share/doc/sip-router/AUTHORS
.SH SEE ALSO
-.BR ser(8)
+.BR sip-router(8)
.PP
-Full documentation on ser, including configuration guidelines, FAQs and
+Full documentation on sip-router, including configuration guidelines, FAQs and
licensing conditions, is available at
-.I http://www.iptel.org/ser/.
+.I http://sip-router.org.
.PP
For reporting bugs see
.I
-http://www.iptel.org/ser/bugs/.
+http://sip-router.org/tracker/
.PP
Mailing lists:
.nf
-serusers(a)iptel.org - ser user community
+sr-users(a)lists.sip-router.org - SIP Router user community
.nf
-serdev(a)iptel.org - ser development, new features and unstable version
-
+sr-dev(a)lists.sip-router.org - SIP Router development, new features and unstable version
On Jun 24, 2009 at 14:16, Edson Gellert Schubert <egschubert(a)gmail.com> wrote:
> Find the missed part of this h350 issue....
>
> H350 compilation was tryed because the module name is not present on the
> "exclude_modules" list. After including it on a clean downloaded source
> it worked as expected.
>
> Could someone update Makefile to include 'h350' on the default excluded
> list?
Done, thanks.
I've excluded a lot of modules that did require external libraries,
including h350 that requires and external *.h.
BTW: you can ignore compilation errors using: make all err_fail=0.
With err_fail=0 the compilation will not stop anymore on errors, it will
continue.
Andrei
Module: sip-router
Branch: master
Commit: 8632598cac189adb557ad0c65f15744ef4256e45
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=8632598…
Author: Andrei Pelinescu-Onciul <andrei(a)iptel.org>
Committer: Andrei Pelinescu-Onciul <andrei(a)iptel.org>
Date: Wed Jun 24 20:01:46 2009 +0200
tm: safety checks for possible escaped neg. ACKs
In normal operation looking up a transaction corresponding to an ACK to a
neg. reply or to a local transaction should end up in script
termination, so when t_relay_to() is called for a neg. ACK, the
transaction should not have been looked up previously. If this
assumption fails, the ACK will be processed normally (resulting at
worst in calling the TMCB_ACK_NEG_IN callback multiple times for
the same ACK) and a warning message will be logged.
---
modules/tm/t_funcs.c | 28 +++++++++++++++++++++++-----
1 files changed, 23 insertions(+), 5 deletions(-)
diff --git a/modules/tm/t_funcs.c b/modules/tm/t_funcs.c
index d60c99e..aa7d1f4 100644
--- a/modules/tm/t_funcs.c
+++ b/modules/tm/t_funcs.c
@@ -271,11 +271,10 @@ int t_relay_to( struct sip_msg *p_msg , struct proxy_l *proxy, int proto,
/* parsing error, memory alloc, whatever ... if via is bad
and we are forced to reply there, return with 0 (->break),
pass error status otherwise
-
- MMA: return value E_SCRIPT means that transaction was already started from the script
- so continue with that transaction
+ MMA: return value E_SCRIPT means that transaction was already started
+ from the script so continue with that transaction
*/
- if (new_tran!=E_SCRIPT) {
+ if (likely(new_tran!=E_SCRIPT)) {
if (new_tran<0) {
ret = (ser_error==E_BAD_VIA && reply_to_via) ? 0 : new_tran;
goto done;
@@ -285,11 +284,30 @@ int t_relay_to( struct sip_msg *p_msg , struct proxy_l *proxy, int proto,
ret = 1;
goto done;
}
+ }else if (unlikely(p_msg->REQ_METHOD==METHOD_ACK)) {
+ /* transaction previously found (E_SCRIPT) and msg==ACK
+ => ack to neg. reply or ack to local trans.
+ => process it and exit */
+ /* FIXME: there's no way to distinguish here between acks to
+ local trans. and neg. acks */
+ /* in normal operation we should never reach this point, if we
+ do WARN(), it might hide some real bug (apart from possibly
+ hiding a bug the most harm done is calling the TMCB_ACK_NEG
+ callbacks twice) */
+ WARN("negative or local ACK caught, please report\n");
+ t=get_t();
+ if (unlikely(has_tran_tmcbs(t, TMCB_ACK_NEG_IN)))
+ run_trans_callbacks(TMCB_ACK_NEG_IN, t, p_msg, 0,
+ p_msg->REQ_METHOD);
+ t_release_transaction(t);
+ ret=1;
+ goto done;
}
/* new transaction */
- /* ACKs do not establish a transaction and are fwd-ed statelessly */
+ /* at this point if the msg is an ACK it is an e2e ACK and
+ e2e ACKs do not establish a transaction and are fwd-ed statelessly */
if ( p_msg->REQ_METHOD==METHOD_ACK) {
DBG( "SER: forwarding ACK statelessly \n");
if (proxy==0) {