30 Jul
2004
30 Jul
'04
11:05 a.m.
Hi Bogdan,
We upgraded to v0.8.14, and t_check_status works as you described, and perfectly for what
we want to accomplish.
Thank you,
Dave
----- Original Message -----
From: Bogdan-Andrei IANCU <iancu(a)fokus.fraunhofer.de>
Date: Thursday, July 29, 2004 3:19 am
Subject: Re: [Serusers] t_check_status/t_on_failure does not work with ser v.0.8.12 rpm
David Lee wrote:
Hello,
In the admin documentation of ser, it says that all messages
greater than 300 are
considered failures when using t_on_failure.
In our scenario, we would like the ability to forward to a voice
mail on 4xx
failure, but not on 302 failure. We are using XTEN
Pro softphones and want to be able to allow users the
functionality to forward to another SIP url (uses 302). But when
ser is seeing 302 (and t_on_failure is active) it considers it a
failure and immediately runs failure route block (to voicemail).
So our users cannot using forwarding to URL.
An example would be ... When I'm out for lunch I would like to
forward my
line to my secretary first before going to voicemail.
We saw some mention of t_check_status ... but ser wont start
with that in the
cfg. We are using ser v.0.8.12 rpm. Is that in
a unstable version only. If some could post how to accomplish
this it would be appreciated.
yes, indeed, the answer is t_on_failure - this function didn't
existed
in the original release 0.8.12 (so, not present in rpm), but you
can
find it in the cvs tree of 0.8.12 - so, get the sources from cvs.
bogdan