I haven’t experimented with this … so I can’t comment. -ovidiu
On Wed, Oct 18, 2023 at 11:13 Denys Pozniak <[email protected]> wrote: > and comment please this question if possible: > - If nodes operate in anycast + clusterer mode, then in what route should > function t_anycast_replicate() be called? > > > ср, 18 окт. 2023 г. в 16:49, Denys Pozniak <[email protected]>: > >> Thank you for such a cool and detailed answer! >> But I would like to clarify the following: >> >> >Custom headers can be set for each b2b_entity during the entity setup >> via the extra_hdrs and extra_hdrs_bodies [4] [5]. >> Do I understand correctly that this only works for initial invites? >> >> >For now, the outgoing socket is set by opensips internally. There were >> some fixes related to this, make sure that you are using the latest >> opensips version. >> But I have several sockets and how can I influence the choice? >> >> ср, 18 окт. 2023 г. в 15:59, Ovidiu Sas <[email protected]>: >> >>> Hello Denys, >>> >>> Dialog module should *never* be mixed with the b2b module. >>> For b2b calls one can use the $b2b_logic.ctx vars [1]. >>> For b2b tracing use the 'b' scope in trace() [2]. >>> There are some issues as not all provisional replies are traced [3]. >>> Custom headers can be set for each b2b_entity during the entity setup >>> via the extra_hdrs and extra_hdrs_bodies [4] [5]. >>> For now, the outgoing socket is set by opensips internally. There were >>> some fixes related to this, make sure that you are using the latest >>> opensips version. >>> >>> -ovidiu >>> >>> [1] https://opensips.org/docs/modules/3.4.x/b2b_logic.html#b2b_logic.ctx >>> [2] https://opensips.org/docs/modules/3.4.x/tracer.html#func_trace >>> [3] https://github.com/OpenSIPS/opensips/issues/3194 >>> [4] >>> https://opensips.org/docs/modules/3.4.x/b2b_logic.html#func_b2b_server_new >>> [5] >>> https://opensips.org/docs/modules/3.4.x/b2b_logic.html#func_b2b_client_new >>> >>> >>> On Wed, Oct 18, 2023 at 9:16 AM Denys Pozniak <[email protected]> >>> wrote: >>> > >>> > Hello! >>> > >>> > I'm trying to implement topology hiding (b2b_logic) in an existing >>> config, but there are points that are not clear to me: >>> > - Can I somehow use dialog variables in b2b mode? if not, any >>> alternative? I see they are created for the initial leg (with state=3), but >>> not available in the b2b mode; >>> > - How to configure a tracer (proto_hep) in b2b mode? >>> > - How to convert transport and select outgoing socket (the question >>> has already been asked in a separate mail)? >>> > - How can I add the necessary custom X-headers also for in-dialog >>> requests (for example, for re-INVITE)? It does not work via insert_hf in >>> [script_req_route] neither via function b2b_client_new() as well; >>> > - If nodes operate in anycast + clusterer mode, then in what route >>> should function t_anycast_replicate() be called? >>> > >>> > -- >>> > >>> > BR, >>> > Denys Pozniak >>> > >>> > >>> > _______________________________________________ >>> > Users mailing list >>> > [email protected] >>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >>> -- >>> VoIP Embedded, Inc. >>> http://www.voipembedded.com >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >> >> >> -- >> >> BR, >> Denys Pozniak >> >> >> > > -- > > BR, > Denys Pozniak > > > _______________________________________________ > 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
