11 Jul
2007
11 Jul
'07
9:49 p.m.
At 21:22 11/07/2007, Martin Hoffmann wrote:
Jiri Kuthan wrote:
Indeed: KISS applies to ser.cfg very well.
-jiri
--
Jiri Kuthan http://iptel.org/~jiri/
At 16:41 11/07/2007, JF wrote:
In short: There may be dragons there.
Anyways, I am not sure what you want to do, but you can usually skip the
problem by fixing the Request-URI and sprialing the call to yourself.
For instance, if call forwarding is what you're after, instead of
re-setting the target and just running processing again, you can just
stuff the URI you want to forward to in the Request-URI and call
t_relay() (don't forget the append_branch() if in a failure_route).
As a rule, keep failure and onreply routes simple. Actually, as a rule,
keep your config simple (Though simple does not necessarly mean short).
Is there any particular reason why enum_query cannot be called from
FAILURE_ROUTE?
Not sure. I think it is possible to turn it on but possibly ENUM's processing
latency may conflict with the failure_route located in the middle of
transaction
processing and lead to some blocknig conditions, current TM
maintainer, Andrei, will
certainly know better.