Sorry Bogdan,

If I understand, this is the scenarious that I implemented.

With the lookup function patch (that add the q value to the input parameter, 
the same assigned to you) Chris can invoke the lookup function three time with 
the three subscriber and obviously three different qvalue. After he can invoke 
the serialize_branches(1) function.
Finally he can use the next_branch route in the failure route block to fork 
sequentially the INVITE on the next subscriber...
And when the next_branch function return "no other branches" he can forward the 
call to the voicemail...

I don't know if the patch is applied but in this way, I think, that Chris can 
solve his problem...

Regards,
        MD

 
-----Messaggio originale-----
Da: [email protected] [mailto:[email protected]] 
Per conto di Bogdan-Andrei Iancu
Inviato: martedì 21 aprile 2009 10:39
A: Chris Maciejewski
Cc: [email protected]
Oggetto: Re: [OpenSIPS-Users] Ring Group - Memory Hunt - with serial forking?

Hi Chris,

Chris Maciejewski wrote:
> Hi,
>
> I am trying to implement a Ring Group with
> a Memory Hunt ring strategy.
>
> The scenario looks as follows:
>
> There is a subscriber A, B and C. All of them are members of the same
> Ring Group.
>
> When there is a INVITE to a "Ring Group" Opensips should send an
> INVITE to subscriber A, after 10 seconds it should send an INVITE to
> subscriber B and after another 10 seconds one more INVITE
> to subscriber C. If there is no 200 OK from A,B or C in 40 seconds,
> call should be forwarded to Voicemail server.
>   
This is something you cannot do right now - to wait N seconds and create 
another branch of an existing call (without cancelling the previous 
branches).

What you want to do is a kind of "asynchronous" parallel forking.

Regards,
Bogdan


_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to