Re: [SR-Users] Sipwise SEMS

Hello Alex, yes, sipwise maintain a fork of it. One related question, the last “official” release 1.6 of sems was in 2015 (at least in public github). Are people just using the development version in production then, also also just maintain their own private fork? Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users &lt;sr-users-bounces(a)lists.kamailio.org&gt; On Behalf Of Alex Balashov Sent: Sunday, July 4, 2021 11:37 PM To: Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.kamailio.org&gt; Subject: Re: [SR-Users] Sipwise SEMS Yes, this is possible, though it’s not clear why you’d want to do this with SEMS when you can just make routing decisions in Kamailio and hint to SEMS B2BUA where to route the call onward, whether via the RURI or a custom header. Also, SEMS does not come from Sipwise, though it is my understanding that they maintain a fork. — Sent from my iPad On Jul 4, 2021, at 2:40 PM, David Villasmil <david.villasmil.work@gmail.com<mailto:david.villasmil.work@gmail.com>> wrote: Hello guys, I know SEMS can provide conference, voicemail, and other services. In theory it’s also a B2BUA. Could I use a python script to provide a simple routing service? I.e.: receive an invite and send it somewhere else based on some routing logic? Thanks all David -- Regards, David Villasmil email: david.villasmil.work@gmail.com<mailto:david.villasmil.work@gmail.com> phone: +34669448337 __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users