Although the Kamilio has a good performance for working as SBC, But in combination with SEMS, it can have the best performance as an SBC. With Best Regards. Mojtaba Esfandiari.S On Sat, Dec 25, 2021, 16:42 Alex Balashov <abalashov(a)evaristesys.com> wrote:

Alex Balashov writes: I would not say that SEMS has not been maintained. Some bugs have been fixed and currently I don't know any bug that would affect my use of SEMS. If someone finds a bug that affects his/her use of SEMS, pull requests are and have been welcome. -- Juha

It is perhaps in the eye of the beholder. I did not mean to invalidate or ignore your contributions, or those of Sipwise to their fork, etc. I still believe it’s fair to say that there exists no significant commitment to the future of the open-source version, not as a matter of critical mass. — Sent from mobile, with due apologies for brevity and errors.

@Juha Heinanen <jh(a)tutpro.com> As you know, i,ve reported an issue in SEMS before. Im going to have request pull for this update in SEMS. Thanks On Sat, Dec 25, 2021, 21:47 Juha Heinanen <jh(a)tutpro.com> wrote:

Just from my understanding, what feature/s does SEMS have that Freeswitch does not? Thanks! ~Noah

When I consider the viability of an open-source project and the question of maintenance, I take a holistic view of the life cycle, and whether there is some significant base of developers or organisation with a declared commitment to furthering its development and some goals around that. This includes all facets of project management that make it usable to others, including keeping documentation current, etc. Without this, there are just — in the best case — some commits happening. While noble and laudable, these are not propitious for a long-term and durable investment in an esoteric technology or system. And it is far from clear, anyhow, that one or two people’s occasional — if motivated — commits can defend against the encroaching forces of “bit rot”, shifting dependencies and operating environment characteristics, changing library APIs, new packaging systems, and in short all manner of entropy. The community edition of SEMS is not a viable recommendation for the general mass of potential users in this sense. It might work for you because you know it very well and have personally contributed to it for some years, but this doesn’t make it practical for others and I cannot in good conscience recommend it for people who aren’t you, Sipwise or a handful of other shamans verses in its spells. :-) — Sent from mobile, with due apologies for brevity and errors.

I think it’s also worth noting that SEMS is very lean and efficient, and can be easily pared down to doing exactly what you need it to do and not an ounce more. FS is a bureaucratic and resource-hungry monster by comparison. I use SEMS myself and like it very much. It’s sad to see it fall away and I regret that I personally lack the resources to prop it up. Nevertheless, I think it’s a fact that it’s not a dependable input in a future-proof way for lack of active public development and (much) maintenance. I think in the most optimistic view it is merely “very unpolished”. — Sent from mobile, with due apologies for brevity and errors.

I also have written some applications which use some of its SBC capabilities. I feel so happy that the SEMS works powerfully in signaling mode. For some reason, I don't anchor RTP sessions to SEMS and use a media server in Kamailio (LRKProxy). Because of the elasticity of each item, you might find some unusual manner in Sems, they are quite a topic that has no effect on Sems's overall behavior. For these cases, you can have contributions in solving them or using Kamailio. On Sun, Dec 26, 2021 at 11:17 AM Juha Heinanen <jh(a)tutpro.com> wrote: -- --Mojtaba Esfandiari.S

Hi can you share hkw to config sems and kamailio to work together as sbc (semes for signalling and kamailio+rtpengine for media) Thanks. On Mon, Jan 3, 2022, 8:03 PM Denys Pozniak <denys.pozniak(a)gmail.com> wrote: