29 Jan
2004
29 Jan
'04
3:45 p.m.
Bogdan-Andrei IANCU wrote:
Hi Andres,
The simplest solution is to register all the time a failure route for
INVITES (as you do now) and from the failure route before doing fork
(proxying to the other server) check the reply code and skip the one
like busy :
t_on_failure[x] {
if ( !t_check_status("486|408") ) {
append("xxxxx");
t_relay();
}
}
in this example you will do forking to the other server only if the
reply status from the first INVITE is different than 486 or 408;
t_check_status takes as argument a regular expression
Regards,
Bogdan
Thanks Bogdan,
This sounds promising. Unfortunately our production servers are using
0.8.12 and the "t_check_status" function does not appear to be there. I
will load 0.8.13 in a LAB box and try it out.
--
Andres
Network Admin
http://www.telesip.net