[ previous ] [ next ] [ threads ]
 To :  Monica Tepelus <monica@v...>
 From :  Milan Rukavina <milan@h...>
 Subject :  Re: [yate] maxcall in fork and lateroute
 Date :  Wed, 09 Jun 2010 13:06:38 +0200
Thanks Monica,

I made mistake - actually I was doing the same syntax as you suggested 
but I posted here wrong one.

The real bug in my code was the fact I'm doing this from php/ivr not 
regex route - so I needed to add separate parameter maxcall not a string 
notation.

All is fine now.

Thanks again.

Milan
> Hi,
>
> Try: fork lateroute/900004 | lateroute/900001 | 
> lateroute/900002;maxcall=5000
> If you use regexroute then above syntax is ok, if not add maxcall as a 
> different parameter.
> The 5000 there has no meaning. It would try to call 5000 and 
> lateroute/900001 at the same time.
>
> Also check your lateroute configuration file and be sure "lateroute" 
> is set there since you use an older version. When it was first added 
> "lateroute" wasn't recognized by default.
>
> If it still doesn't work please send a log sniffer enabled.
>
> Monica Tepelus
>
> Milan Rukavina wrote:
>> Hi All,
>>
>> Is it possible to use maxcall paramter in fork in combination with 
>> lateroute, ex.:
>> fork lateroute/900004 | 5000 lateroute/900001 | 5000 
>> lateroute/900002;maxcall=5000
>>
>> I know about drop/next syntax but it's available since 2.2 and we're 
>> using older version. I expected maxcall to move forward targets after 
>> 5s but it doesn't seem to work.
>>
>> Thanks,
>> Milan
>
>