[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  "Raffaele P. Guidi" <roughraf@g...>
 Subject :  Fwd: [yate] call fork problem
 Date :  Sat, 24 Jan 2009 12:30:38 +0100
Hi, I try to repost the question

---------- Forwarded message ----------
From: Raffaele P. Guidi 
Date: Tue, Jan 20, 2009 at 18:43
Subject: Re: [yate] call fork problem
To: yate@v...
Cc: Paul Chitescu 


Hi again, first of al thanks for your quick reply but I tried:
 .*=fork lateroute/1000 lateroute/1001 lateroute/1002;stoperror=busy
and also
 .*=fork 1000 1001 1002;stoperror=busy
with no result - I still have two calls per extension. Another guess? :)

On Tue, Jan 20, 2009 at 13:53, Paul Chitescu  wrote:
> Hi!
>
> Since you are routing the calls to 127.0.0.1 you are creating an extra pair of
> SIP call legs for each extension!
>
> incoming -> fork -> 1000@1... (out) -> 1000@1... (in) -> 1000@....
>
> Please use instead:
>
> .*=fork lateroute/1000 lateroute/1001 lateroute/1002;stoperror=busy
>
> This will delay the per extension routing until the outgoing call leg attempt
> for each extension.
>
> Regards,
>
> Paul
>
>
> On Tuesday 20 January 2009 14:03:02 Raffaele P. Guidi wrote:
>> Hi, I'm trying to make three local (sip) extensions ring when a call
>> comes in from an external provider. The first who picks up the call
>> gets connected and the other ones stop ringing. It seems a job for
>> callfork! I tried the configuration below but it actually creates TWO
>> calls per extension! It otherwise works as expected. Any clue?
>>
>> Thanks,
>>    Raffaele
>>
>> ; regexroute.conf
>>
>> [default]
>> ...
>> ^5352923$=goto from_extprovider
>>
>> [from_extprovider]
>> ^.*$=fork sip/sip:1000@1... sip/sip:1001@1...
>> sip/sip:1002@1...;stoperror=busy
>