[SR-Users] Problem with worst case scenario of accessing 15 gateways over the DISPATCHER module - MAX_BRANCHES is reached

Henning Westerholt henning.westerholt at 1und1.de
Wed Jul 6 15:37:49 CEST 2011


On Wednesday 06 July 2011, Klaus Feichtinger wrote:
> the described scenario is not a standard scenario. This would be realistic
> in emergency situations only (e.g. so many calls are coming in and the
> gateways are busy => e.g. responding with "486 Busy Here" ). Also the time
> delay would not be very high, because the fr_timer variable is set to a
> value of 750ms before relaying the call to the dispatcher-targets
> ("t_set_fr([...]))") - this is just for a scenario when the target is
> unreachable.

Hi Klaus,

i understand.

> In case that the dispatcher-target is responding with a negative response
> code (as it was until now), all targets are sequentially addressed within
> a time of lower than 1 second until the error message of the TM module is
> interrupting that process.

1s is of course fast enough.

> However, if there is no alternative to changing the define value of
> MAX_BRANCHES I will use your recommendation for limiting the number of
> gateways that will be addressed over the failure_route. My Question now
> is: how can I count the number of branches / rejections (from the
> failure_route)?
> I've tried using the pseudo_variable $branch(count) (according description
> of the WIKI page), but the value is "0" all the time => not useful. I
> could create a private table and use the sqlops module. Do you have any
> easier alternative recommendation how the number could be limited?

What about just incrementing an variable, like an avp and check this in an if 
case?

Best regards,

Henning



More information about the sr-users mailing list