[OpenSIPS-Users] use of scenario_id in b2b_init_request
xaled at web.de
xaled at web.de
Fri Apr 9 21:06:55 EST 2021
thank you, I missed the $b2b_logic.scenario variable that can be used to differentiate logic within route[b2b_logic_request]. Now it is clear to me.
It would be good to include it as an example in the B2B tutorial or B2B module documentation.
From: Users <users-bounces at lists.opensips.org> On Behalf Of Vlad Patrascu
Sent: Friday, April 9, 2021 7:12 PM
To: users at lists.opensips.org
Subject: Re: [OpenSIPS-Users] use of scenario_id in b2b_init_request
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: ).
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".
On 09.04.2021 18:49, xaled at web.de wrote:
> 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
> 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?
> Users mailing list
> Users at lists.opensips.org
Users mailing list
Users at lists.opensips.org
More information about the Users