Hi Richard, I really appreciate your help! However, the initial problem is to avoid the forking for the scenario you mentioned (no matter if it is serial or parallel) if the INVITE is coming from the GW with Request-Disposition: no-fork. The issue is with the “to tag” parameter: https://www.opensips.org/Documentation/Script-CoreVar-3-2#toc90 This is read only and also Bogdan does not recommend to play with this: http://lists.opensips.org/pipermail/users/2022-October/046318.html Here is my original question, I hope you have some idea for this.
> I have call forwarding busy/no answer scenario: A number is from a > gateway, B and C numbers are our own subs. > > The gateway is sending us the INVITE message with > “Request-Disposition: no-fork” header field. > > That means we must use one dialog for the mentioned scenario. > > Currently the To tag we are sending to the GW in the first 180 > ringing/181 Call is being forwarded messages are different to the > To tag in the second 180 ringing and 200 OK (SDP). > > Gateway OpenSips > > INVITE > > ------------------------------------------> > > 100 GIVING IT A TRY > > <-- ----------------------------------------- > > 180 RINGING > > <- ------------------------------------------- > > 181 CALL IS BEING FORWARDED > > <- ------------------------------------------- > > 180 RINGING > > <- ------------------------------------------- > > 200 OK (SDP) > > <- ------------------------------------------- > > What would be the easiest way from OpenSIPS to send the same To > tag (it should be the same from the first 180 ringing through to > the 200 OK) and using one dialog for this scenario? > Cheers, Bela From: Richard Revels via Users<mailto:users@lists.opensips.org> Sent: Friday, 10 February 2023 08:35 To: OpenSIPS users mailling list<mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] Does OpenSIPS support Request-Disposition: no-fork in INVITE message? I'm not looking back to see the old conversation so forgive me if I'm answering the wrong question here. So, I think you want to send the call to a customer, say at their desk. If they don't answer then send the call to, for example, their cellphone. In that case you would want serial forking rather than parallel forking. (and im not testing this so may miss something here but in general) route[0] { $ru = 'sip:me@mydesk.local'; $ru_q = 990; construct_uri("sip", "me", "mycellphone.org<http://mycellphone.org>", "5060", "transport=udp", $avp(newuri)); append_branch(); $ru = $avp(newuri); $ru_q = 980; serialize_branches(); next_branches(); t_on_failure( "find-me" ); t_relay(); } failure_route[find-me] { if( !t_was_cancelled() ) { next_branches(); t_relay(); } } append_branch https://www.opensips.org/Documentation/Script-CoreFunctions-3-2#toc3 $ru https://www.opensips.org/Documentation/Script-CoreVar-3-2#toc79 $ru_q https://www.opensips.org/Documentation/Script-CoreVar-3-2#toc81 On Mon, Feb 6, 2023 at 7:39 PM Bela H <hob...@hotmail.com<mailto:hob...@hotmail.com>> wrote: Hi Bogdan-Andrei, I know this is an old topic but customer is complaining. How is it possible to configure the call forwarding no answer without forking? Cheers, Bela From: Bogdan-Andrei Iancu<mailto:bog...@opensips.org> Sent: Tuesday, 11 October 2022 01:50 To: OpenSIPS users mailling list<mailto:users@lists.opensips.org>; Bela H<mailto:hob...@hotmail.com> Subject: Re: [OpenSIPS-Users] Does OpenSIPS support Request-Disposition: no-fork in INVITE message? Hi Bela, As per prev email, there is nothing to be supported by OpenSIPS, just don;t do forking in your cfg, nothing more. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 27-30 Sept 2022, Athens https://www.opensips.org/events/Summit-2022Athens/ On 9/30/22 12:15 AM, Bela H wrote: Hello, Does OpenSIPS 3.2.6 version support Request-Disposition: no-fork in INVITE message? Cheers, Bela _______________________________________________ Users mailing list Users@lists.opensips.org<mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users@lists.opensips.org<mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
