Hi!
If you don't have a t_on_failure() call in the failure_route, you will only
have two failure_routes, isn't it??
You said that you didn't receive the 487 message from the gateway after
cancel... so the code:
if (t_check_status("487")) { # Request Terminated by CANCEL from
[....]
hasn't any effect.
I had the same problem. If the user calls a gateway that is dead, lcr
searches for the next gateway although the user has canceled before (bored
;-).
I still don't have a solution.
Sebastian
----- Original Message -----
From: "Ben Smithurst" <ben(a)gradwell.net>
To: "Miguel Angel Villar" <mavilla(a)redvoiss.net>
Cc: <serusers(a)lists.iptel.org>
Sent: Thursday, September 01, 2005 12:37 PM
Subject: Re: [Serusers] problem with LCR and CANCEL
Miguel Angel Villar wrote:
Hi Ben.
You shouldn't use next_gw() in failure route if you receive Busy or
Cancel from user:
failure_route[1] {
...
thanks for the quick reply!
I was sure I'd tried that already... :-(
Your example works fine though - I think the key thing I had wrong
before was having a t_on_failure call inside the failure route - I'm
sure I saw this in an example config somewhere, and while I thought it
seemed odd, assumed there was a good reason for it. Evidently not. :-)
Using your failure block has made it all seem to work fine.
thanks again
-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