5 Jul
2021
5 Jul
'21
11:24 a.m.
Hello Jon,
thank you for the explanation, really helpful.
I was suspecting a situation like this but did not follow SEMS that closely (it's not
used a lot from our customers).
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
-----Original Message-----
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Jon Bonilla
(Manwe)
Sent: Monday, July 5, 2021 10:19 AM
Cc: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] Sipwise SEMS
El Mon, 5 Jul 2021 06:26:12 +0000
Henning Westerholt <hw(a)skalatan.de> escribió:
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?
Public sems was abandoned years ago. It receives some fixes but there's no support
from Frafos. There are several commercial branches which have active development but as I
said, its comercial.
Sipwise has access to those branches because it's a huge contributor, pays a lot of
money to Frafos for that. Mostly because their PBX modules for commercial versions of
their products run on top of sems.
Anyway, the open version is quite stable as it is now. It has bugs that won't ever be
fixed but if you know them it's something you can deal with. Same as the ones of us
still using chan_sip in asterisk, if you know where the bugs are you can live ith it.
--
PekePBX, the multitenant PBX solution
https://pekepbx.com