Hi , thanks Bogdan this sorted it out and call forking works as a charm :).
The only problem issue I have seen is that sometimes a single registration triggers multiple events below is a log snippet for such an case ( a bit anonymized) 2018-01-31T09:51:56.296843+00:00 info sip-qa-1 cF6apbQMV66SfiQ2phordLXqQQvJIRxj|Route0|REGISTER|Save location|true|us...@domain.com] 2018-01-31T09:51:56.297101+00:00 info sip-qa-1 INSERT_CALL: user us...@domain.com registered the a new contact sip:userA@212.116.71.162:50734;transport=TLS;ob, injecting it in transaction 2018-01-31T09:51:56.297470+00:00 info sip-qa-1 INSERT_CALL: user us...@domain.com registered the a new contact sip:userA@212.116.71.162:50734;transport=TLS;ob, injecting it in transaction 2018-01-31T09:51:56.297803+00:00 info sip-qa-1 INSERT_CALL: user us...@domain.com registered the a new contact sip:userA@212.116.71.162:50734;transport=TLS;ob, injecting it in transaction One could of course check if this contact IP/port have already been injected into the call, but I just wondered if this is anything you have seen before. BR/Olle Från: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Skickat: den 26 januari 2018 15:53 Till: Olle Frimanson <o...@zaark.com>; 'OpenSIPS users mailling list' <users@lists.opensips.org> Ämne: Re: SV: [OpenSIPS-Users] Problem with event based routing Hi, It is illegal to do signalling (like t_relay()) in branch route. Simply remove the whole branch route stuff from your script as you do not need it. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer <http://www.opensips-solutions.com> http://www.opensips-solutions.com OpenSIPS Summit 2018 <http://www.opensips.org/events/Summit-2018Amsterdam> http://www.opensips.org/events/Summit-2018Amsterdam On 01/25/2018 12:31 PM, Olle Frimanson wrote: Hi I call a relay route from the branch route, so its basically Route { . t_wait_for_new_branches(); $avp(filter)= "aor="+ $avp(to_user_uri); notify_on_event("E_UL_CONTACT_INSERT","$avp(filter)", "INSERT_CALL", "40"); t_on_branch(1) If ( lookup(location) route(relay) } route[RELAY] { if (is_method("INVITE")) { t_on_reply("1"); t_on_failure("3"); if (!t_relay()) { . } } } route[INSERT_CALL] { t_inject_branches("event","cancel"); } branch_route[1] { route(RELAY); exit; } BR / Olle PS I send another mail on the same subject since I missed your reply pls ignore that. Från: Bogdan-Andrei Iancu [ <mailto:bog...@opensips.org> mailto:bog...@opensips.org] Skickat: den 24 januari 2018 17:42 Till: OpenSIPS users mailling list <mailto:users@lists.opensips.org> <users@lists.opensips.org>; Olle Frimanson <mailto:o...@zaark.com> <o...@zaark.com> Ämne: Re: [OpenSIPS-Users] Problem with event based routing Hi Olle, Do you call t_relay() from a BRANCH_ROUTE ?? IF so, this is not legal as the branch route is only an inspection and modification route, not a signaling route. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer <http://www.opensips-solutions.com> http://www.opensips-solutions.com OpenSIPS Summit 2018 <http://www.opensips.org/events/Summit-2018Amsterdam> http://www.opensips.org/events/Summit-2018Amsterdam On 01/24/2018 11:33 AM, Olle Frimanson wrote: Hi, We are looking into changing our logic for push notification to the new event based routing that is available in opensips 2.3. In live scenarios everything is working fine but when I relay the call after injecting it into the branch I get the following error: CRITICAL:tm:w_t_relay: unsupported route type: 8 It would be great if you could share the configuration file that is used in the example mention in the blog post. BR/Olle _______________________________________________ Users mailing list <mailto:Users@lists.opensips.org> Users@lists.opensips.org <http://lists.opensips.org/cgi-bin/mailman/listinfo/users> 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