29 Jan
2004
29 Jan
'04
3:58 p.m.
At 08:04 PM 1/29/2004, David R. Kompel wrote:
I'm glad this issue was brought up when it was,
cause I was just about
to post on it :) I am using the same trick for voice mail. The problem
is, if the user is busy, there is no way to detect it, since
t_on_failure doesn't call the failure_route[x], if only one of the forks
in the dset gets an error from the UAS.
It would be nice to see a way that the failure_route could get called if
any fork gets an error, and had a way to test for other existing forks,
and cancel them, and then re-direct the call.
I am not sure if there is a benefit in forking to N destinations and giving
on N-1 of them if one fails... what is the use case? (I naively thought you
fork in parallel to try as many destinations as you wish and fall back to
other alternative such as voicemail only if none of these original destinations
succeded.)
-jiri