[Serusers] Cannot capture call status in failure route
Daniel-Constantin Mierla
daniel at iptel.org
Thu May 27 15:43:23 CEST 2004
failure_routes process the initial request, not the reply which caused
the failure.
Daniel
On 5/27/2004 3:35 PM, Zeus Ng wrote:
>I have the following logic.
>
>route {
>...
> t_on_reply("1");
> t_on_failure("1");
> t_relay();
>}
>
>onreply_route[1] {
> xlog("L_NOTICE", "Reply status %rs: Reason %rr\n");
>}
>
>failure_route[1] {
> xlog("L_NOTICE", "Reply status %rs: Reason %rr\n");
> if (status=="408") {
> do something 1
> } else if (status=="480") {
> do something 2
> } else if (status=="486") {
> do something 3
> }
>}
>
>When a reply with 4xx comes in, it first goes through onreply_route[1] and
>get the result printed to syslog. The message is then passed to
>failure_route[1]. But it seems that the status code and reason are gone. I
>get a <null> for both values in the failure route. How should I change the
>script to get that.
>
>Zeus Ng
>
>_______________________________________________
>Serusers mailing list
>serusers at lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers
>
>
>
More information about the sr-users
mailing list