THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Andrew Pogrebennyk (marduk)
Attached to Project - sip-router
Summary - modules/tmx: t_is_failure_route() code or documentation is wrong
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Low
Priority - Normal
Reported Version - 4.1
Due in Version - Undecided
Due Date - Undecided
Details - Hello,
I'm using kamailio 4.1.4. There is a problem with t_is_failure_route() function. While the documentation says it can be used in any route:
http://www.kamailio.org/docs/modules/4.1.x/modules/tmx.html#idp27024
3.5. t_is_failure_route()
Returns true if the top-executed route block is failure_route.
This function can be used from ANY_ROUTE .
in fact I'm getting an error if I call that function from the branch_route:
Jun 25 11:44:20 sp1 proxy[11942]: ERROR: tmx [t_var.c:500]: pv_get_tm_reply_code(): unsupported route_type 8
(the call flow is simple: after failure_route fires, I call a request route and set a new destination and then the branch route gets called). Please fix either the code (would be nice indeed) or the documentation. Thanks!
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=445
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.
All,
Just FYI: there is a missing piece in documentation which allows sort of proper handling of reg entries in S-CSCF. Here are parameters which I used to limit number of entries in registrar along with proper removal of old, not valid entries.
modparam("ims_usrloc_scscf", "maxcontact", 2)
modparam("ims_usrloc_scscf", "maxcontact_behaviour", 2)
/*!< max contact behaviour - 0-disabled(default),1-reject,2-overwrite*/
This happens to be found on latest 4.1.4 branch.
@Jason: could you please update doc so people won't go through this pain again ? ;-)
thanks
--
Daniel Ciprus
Integration engineer
http://www.acision.com
9954 Mayland Dr
Suite 3100
Richmond, VA 23233
USA
T: +1 804 762 5601
E: daniel.ciprus(a)acision.com<mailto:daniel.ciprus@acision.com>
________________________________
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
Hi,
Before i spend hours reading specs, a question to Diameter-Experts...
Last night our hosting provider had an outage in our datacenter and
had to restart one of our servers. After restarting, all servers came
back up except our database, which failed to start due to replication
issues. Except from our HSS, all components use a redundant database
link, so everything was fine. The HSS started, but failed to connect
to the database and as a result, it responded to all Diameter-Requests
with "5012 Diameter unable to comply", which is correct (i believe)
for Diameter for unspecified error-reasons:
RFC 3588 (page 87):
DIAMETER_UNABLE_TO_COMPLY 5012
This error is returned when a request is rejected for unspecified reasons.
However, ims_auth sends a "403 HSS unable to comply" response back to
the I-CSCF, which will not trigger a re-routing on the I-CSCF as it's
"Forbidden" and not exactly an error (e.g. like "User unknown").
Questions:
- is it correct to the standards, to send a "403" in this case?
Shouldn't it be some reply, which allows re-routing the requests?
- i assume, it would be desirable, to re-route Diameter requests to
another peer in such cases, right?
I've noticed, that MSG_480_HSS_ERROR is actually also sent as a "403"
and not as a "480" (which would trigger a re-routing), as the DEFINE
message would imply....
Thanks,
Carsten
P.S.: Next step for me: Add the redundant database link to the
HSS/OCS, was on my Todo-List too long... ;-)
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Office +49 40 34927219
Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/
Module: sip-router
Branch: master
Commit: c9c8f8d71fdad33caebaea07922901618bcd7825
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=c9c8f8d…
Author: Ovidiu Sas <osas(a)voipembedded.com>
Committer: Ovidiu Sas <osas(a)voipembedded.com>
Date: Tue Jun 17 11:47:50 2014 -0400
auth: document '-8' return code for pv_www_authenticate
---
modules/auth/doc/auth_functions.xml | 12 ++++++++----
1 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/modules/auth/doc/auth_functions.xml b/modules/auth/doc/auth_functions.xml
index 0ab616a..ec33324 100644
--- a/modules/auth/doc/auth_functions.xml
+++ b/modules/auth/doc/auth_functions.xml
@@ -198,26 +198,30 @@ if (!auth_check("$fd", "subscriber", "1")) {
<itemizedlist>
<listitem><para>
<emphasis>-1 (generic error)</emphasis> - some generic error
- occurred and no reply was sent out;
+ occurred and no reply was sent out
</para></listitem>
<listitem><para>
- <emphasis>-2 (invalid password)</emphasis> - wrong password;
+ <emphasis>-2 (invalid password)</emphasis> - wrong password
</para></listitem>
<listitem><para>
<emphasis>-3 (invalid user)</emphasis> - authentication user does
- not exist.
+ not exist
</para></listitem>
<listitem><para>
<emphasis>-4 (nonce expired)</emphasis> - the nonce has expired
</para></listitem>
<listitem><para>
<emphasis>-5 (no credentials)</emphasis> - request does not contain
- an Authorization header with the correct realm.
+ an Authorization header with the correct realm
</para></listitem>
<listitem><para>
<emphasis>-6 (nonce reused)</emphasis> - the nonce has already been
used to authenticate a previous request
</para></listitem>
+ <listitem><para>
+ <emphasis>-8 (auth user mismatch)</emphasis> - the auth user is different
+ then the From/To user
+ </para></listitem>
</itemizedlist>
<para>Meaning of the parameters is as follows:</para>
<itemizedlist>