[OpenSIPS-Users] use of scenario_id in b2b_init_request

[Vlad Patrascu]

Hi Xaled,

The scenario ID is just a transparent identifier for the current B2B 
session. You may use it to identify which session belongs to which of 
your B2B scenarios. You can see this value in the output of b2b_list MI 
function and also you can retrieve it in the script with 
$b2b_logic.scenario (this may be useful if you use a single B2B request 
route, as in the example here: [1]).

Another purpose of the "scenario_id" parameter of b2b_init_request() is 
to be able to choose the internal topology hiding scenario, by providing 
the special value "top hiding".

[1] 
https://opensips.org/docs/modules/3.2.x/b2b_logic.html#b2b_logic.scenario

Regards,

-- 
Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

On 09.04.2021 18:49, xaled at web.de wrote:
> Hi,
>
> I'm trying to understand the B2B module in 3.2 and don't quite get the meaning of scenario_id in b2b_init_request function.
>
> There are multiple examples that use different values in scenario_id
> https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2
>
> b2b_init_request("prepaid"); or b2b_init_request("refer"); but the values "prepaid" or "refer" not used to differentiate anything within route[b2b_logic_request] or anywhere else in documentation.
>
> I get the meaning of req_route parameter of b2b_init_request function to address different B2b logic using different routes, but what does the scenario_id used for?
>
> Thanks,
> Xaled
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users