[Users] How to use the failover support in the dispatcher module?

Wolfgang Hottgenroth woho at hottis.de
Mon Jan 16 13:02:27 CET 2006


Thanks for that answer.
I was not aware, that the timeout is also signalled tru a SIP status
internally.

I did

failure_route[2] {
  if (t_check_status("408")) {
    if (! ds_next_domain()) {
      ...
    } else {
      ...
    }
  } else {
    return;
  }
}

Everything but timeout will be forwarded to the user, timeout is handled
by selecting alternative gateway.

Thanks again,
Wolfgang




Daniel-Constantin Mierla wrote:
> Hello,
> 
> in the failure_route[] you can make a selection of the returned reply
> code from the gateways/destinations.
> 
> if(t_check_status("486" /*busy here*/)) {
>    /* do nothing in script ==> forward the reply to the user */
>   exit;
> } else {
>   /* select next gateway ...*/
>  if (! ds_next_domain()) {
>    ....
>  } else {
>      ....
>  }
> }
> 
> Cheers,
> Daniel
> 
> 
> On 01/13/06 16:44, Wolfgang Hottgenroth wrote:
> 
>> Hi,
>>
>>
>> on 18. 12. 2005 Daniel-Constantin Mierla accounted on this list that the
>> dispatcher module now has a kind of failover support. I was really
>> curious for this feature, since I had to config openser to support both
>> load-balancing and failover.
>>
>> Failover works fine: if one PSTNGW is not available, the next one is
>> tried, until one works.
>>
>> But unfortunately, for negative status reports (like 'busy'), the
>> failure_route is also entered and thereby also the failover mechanism is
>> triggered, with the result that a 'busy' is signalled to the A-side as
>> 'no more gws'.
>>
>> (I've tried different mechanisms for ds_select_domain, also I tried with
>> and without the append_branch in the failure_route block.)
>>
>> Any hints for me?
>>
>>
>> Thank you very much!
>> Wolfgang
>>
>> [...]





More information about the sr-users mailing list