This item was closed on the sf and therefore I can't post my comments there.
So here they are:
It is true that for complex b2bua scenarios it is not possible to have
a t_on_failure() mechanism. However, this should be possible for the
simple "topo hiding" scenario where we have a one to one mapping
between the UAS and UAC components of the b2bua entity.
Having this functionality enabled for "topo hiding" scenario will help
in deploying a single b2bua server with sequential forking
capabilities instead of tho servers deployment: one doing b2bua
functionality and the proxy doing lcr, failover and so on.
In order to avoid confusion (which scenario can and which one cannot
do t_on_failure), the ability to arm a failure route for "topo hiding"
should be provided as a param to b2b_init_request. Something like:
...
# initiate "top hiding" scenario with t_on_failure(10)
b2b_init_request("top hiding", "10");
...
If the second param is empty, there will be no t_on_failure handling
I think the simple "topo hiding" scenario will be widely used if it
provides enough flexibility.
Regards,
Ovidiu Sas
On Fri, Sep 25, 2009 at 4:49 AM, SourceForge.net
<nore...@sourceforge.net> wrote:
> Bugs item #2865413, was opened at 2009-09-24 03:51
> Message generated for change (Settings changed) made by bogdan_iancu
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2865413&group_id=232389
>
> Please note that this message will contain a full copy of the comment thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: modules
> Group: trunk
>>Status: Closed
>>Resolution: Invalid
> Priority: 5
> Private: No
> Submitted By: Sergey Okhapkin (sokhapkin)
>>Assigned to: Bogdan-Andrei Iancu (bogdan_iancu)
> Summary: failure route is not executed with b2bua
>
> Initial Comment:
> t_on_failure("1");
> b2b_init_request("top hiding");
>
> Failure route is not executed when b2bua client gets negative response like
> SIP 503.
>
> ----------------------------------------------------------------------
>
>>Comment By: Bogdan-Andrei Iancu (bogdan_iancu)
> Date: 2009-09-25 11:49
>
> Message:
> Hi Sergey,
>
> I had a similar discussion cu Ovidiu Sas on this topic.
>
> It is impossible to have a t_on_failure() mechanism (which is transaction
> specific) on a B2BUA scenario (where you have multiple dialogs, with
> multiple transactions) - for complex scenarios, with multiple dialogs, you
> cannot say for which transaction to trigger the failure route for.....the
> "topo hiding" scenario is a very simple B2BUA scenario, but you cannot have
> a general "on_failure" concept for all b2bua scenarios.
>
> How I see this solved, is very simple: consider that b2bua is a separate
> instance (logically speaking) which selects types/classes of destinations.
> A proxy instance will responsible for routing inside the class of
> destinations.
>
> For ex: in a scenario we can sent in the first place the call to Media
> Server for some announcement and later to PSTN GW. In a first step, the
> b2bua scenario will sent to proxy the call with RURI pointing to "a class"
> of media servers - the proxy will select the proper media server and do the
> failover between the media servers, totally transparent for the b2bua. In a
> similar way, on the second step, the b2bua scenario will indicate to proxy
> that it wants to have the call to be sent to PSTN GW (as type of
> destination) - the proxy will do lcr, drouting, failover between the GW.
>
> Hope all this story will help you :)
>
> Regards,
> Bogdan
>
> ----------------------------------------------------------------------
>
> You can respond by visiting:
> https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2865413&group_id=232389
>
> _______________________________________________
> Devel mailing list
> Devel@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>
_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
