b2b_logic should respect $du and $ru in scripting mode like it respects $du and $ru in topology hiding mode.
First I do not agree in preserving the $ru - this must be taken from the scenario, IMO.
Now, about the $du, according to you patch, this should be followed only for the "init" clients; it should not be used for further client nodes, right ?
$ru may be changed before b2b_init_request. topology hiding takes it like this way.
For example, I use drouting before b2b_init_request. Without this patch topology hiding works, but scenarios don't.
$du is only for init.
Nick, I agree that topo hiding has to read the $ru to know where to send the call (as topp hiding has no scenario).
But if this case, you have a scenario and the destination is controlled by the xml scenario (client nodes have the <destination> node to tell the new RURI on the outbound part) and not by the received RURI.
My opinion is script should get $ru and $du for init, like topo hiding.
You may just change topo hiding to script and everything should works.
But it's no problem because script can use params. So, if you don't agree, this case may be closed. Thanks.
Well, it is NOT the same as topo hiding - in topo hiding scenario, the call is sent out to the destination received in RURI - and in this case, it should follow the RURI + DURI.
When using a B2BUA scenario script, it is not a simple pass through, but what is the destination is controlled via script - and in the XML script, you say where the call is to be sent. In this case, what was the received RURI is completely irrelevant, IMHO.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.