Hi Ben.
You shouldn't use next_gw() in failure route if you receive Busy or
Cancel from user:
failure_route[1] {
if (t_check_status("486")) { # Busy Here
xlog("L_INFO", "time [%Tf] FAILURE ROUTE - 486 BUSY
HERE\n");
t_relay();
break;
};
if (t_check_status("487")) { # Request Terminated by CANCEL from
Calling Party
xlog("L_INFO", "time [%Tf] FAILURE ROUTE - 487 CANCEL BY
CALLING PARTY\n");
break;
};
if (!next_gw()) {
t_reply("503", "Service not available - No more
Gateways");
break;
} else {
t_relay();
};
}
Regards.
MaV.-
-----Mensaje original-----
De: Ben Smithurst [SMTP:ben@gradwell.net]
Enviado el: Jueves, 01 de Septiembre de 2005 11:20 a.m.
Para: serusers(a)lists.iptel.org
Asunto: [Serusers] problem with LCR and CANCEL
hello,
apologies if this is a silly question...
Basically when using the LCR module, if I CANCEL the call before the
remote party picks up, the LCR system will place the call again through
the next gateway. I have found quite a few references to this in this
list archives etc, so it is probably something fairly simple I have
setup wrong, but none of the messages I found seemed to solve the
problem for me. :-(
After some googling I have read that this is because the first gateway
is not responding with a 487 (which it is in my case). My config has,
among other bits,
route {
......
t_on_failure("1");
if (!next_gw()) {
sl_send_reply("500", "cannot use next gateway");
break;
};
.....
}
failure_route[1] {
t_on_failure("1");
if (!next_gw()) {
t_reply("503", "No more gateways");
break;
};
t_relay();
}
If required I can provide more details but is there anything obviously
missing from the config above which I should be using?
thanks
-ben
--
Ben Smithurst ben(a)gradwell.net gradwell dot com Ltd
Systems Developer
http://bensmithurst.com/ http://www.gradwell.com/
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers