4 Jul
2021
4 Jul
'21
8:40 p.m.
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(a)gmail.com
phone: +34669448337
4 Jul
4 Jul
11:36 p.m.
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(a)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(a)gmail.com
phone: +34669448337
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
5 Jul
5 Jul
5:25 a.m.
Hi David,
SEMS's sbc module (aka B2BUA) works quite well in practice, not just in
theory :)
and yes, you can just pass next hop as a custom header
from mod sbc doc:
next_hop=$H(P-NextHop)
On Sun, Jul 4, 2021 at 11:41 PM David Villasmil <
david.villasmil.work(a)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(a)gmail.com
phone: +34669448337
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
--
Arsen Semenov
8:26 a.m.
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 <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Alex Balashov
Sent: Sunday, July 4, 2021 11:37 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
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
10:18 a.m.
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
10: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
10:42 a.m.
On 05.07.21 10:18, Jon Bonilla (Manwe) wrote:
El Mon, 5 Jul 2021 06:26:12 +0000
Henning Westerholt <hw(a)skalatan.de> escribió:
Maybe abandoned by initial developers, also not getting many new
features. Otherwise, I noticed Juha Heinanen is more or less maintaining
the public version of SEMS. Maybe he can comment on its current state.
Cheers,
Daniel
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
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
12:23 p.m.
I’m using freeswitch in a very simple way, it receives a call, makes an api
http request, and based on the response does some prefixing, etc. it also
provides simple conferencing (three-way call) and provides a very detailed
CDR.
I’m wondering if I could replace it with SEMS.
On Mon, 5 Jul 2021 at 09:45, Daniel-Constantin Mierla <miconda(a)gmail.com>
wrote:
On 05.07.21 10:18, Jon Bonilla (Manwe) wrote:
El Mon, 5 Jul 2021 06:26:12 +0000
Henning Westerholt <hw(a)skalatan.de> <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.
Maybe abandoned by initial developers, also not getting many new features.
Otherwise, I noticed Juha Heinanen is more or less maintaining the public
version of SEMS. Maybe he can comment on its current state.
Cheers,
Daniel
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 solutionhttps://pekepbx.com
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
www.linkedin.com/in/miconda
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
--
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
2:43 p.m.
There is also SEMS forked by yeti-switch project
https://github.com/yeti-switch/sems It has a lot new features but it is
not fully compatible with old modules.
On 05.07.21 11:42, Daniel-Constantin Mierla wrote:
On 05.07.21 10:18, Jon Bonilla (Manwe) wrote:
El Mon, 5 Jul 2021 06:26:12 +0000
Henning Westerholt<hw(a)skalatan.de> escribió:
Maybe abandoned by initial developers, also not getting many new
features. Otherwise, I noticed Juha Heinanen is more or less
maintaining the public version of SEMS. Maybe he can comment on its
current state.
Cheers,
Daniel
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
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
*sr-users(a)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
--
Daniel-Constantin Mierla --www.asipto.com
www.twitter.com/miconda --www.linkedin.com/in/miconda
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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 
3:11 p.m.
Does SEMS support ICE for media negotiation?
On Mon, Jul 5, 2021, 8:45 AM Dmitry Sinina <dmitry.sinina(a)onat.edu.ua>
wrote:
There is also SEMS forked by yeti-switch project
https://github.com/yeti-switch/sems It has a lot new features but it is
not fully compatible with old modules.
On 05.07.21 11:42, Daniel-Constantin Mierla wrote:
On 05.07.21 10:18, Jon Bonilla (Manwe) wrote:
El Mon, 5 Jul 2021 06:26:12 +0000
Henning Westerholt <hw(a)skalatan.de> <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.
Maybe abandoned by initial developers, also not getting many new features.
Otherwise, I noticed Juha Heinanen is more or less maintaining the public
version of SEMS. Maybe he can comment on its current state.
Cheers,
Daniel
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 solutionhttps://pekepbx.com
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
www.linkedin.com/in/miconda
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
3:37 p.m.
https://github.com/yeti-switch/sems - yes
https://github.com/sems-server/sems - no
On 05.07.21 16:11, E. Schmidbauer wrote:
Does SEMS support ICE for media negotiation?
On Mon, Jul 5, 2021, 8:45 AM Dmitry Sinina <dmitry.sinina(a)onat.edu.ua
<mailto:dmitry.sinina@onat.edu.ua>> wrote:
There is also SEMS forked by yeti-switch project
https://github.com/yeti-switch/sems
<https://github.com/yeti-switch/sems> It has a lot new features
but it is not fully compatible with old modules.
On 05.07.21 11:42, Daniel-Constantin Mierla wrote:
On 05.07.21 10:18, Jon Bonilla (Manwe) wrote:
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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 El Mon, 5 Jul 2021 06:26:12 +0000
Henning Westerholt<hw(a)skalatan.de> <mailto:hw@skalatan.de> escribió:
Maybe abandoned by initial developers, also not getting many new
features. Otherwise, I noticed Juha Heinanen is more or less
maintaining the public version of SEMS. Maybe he can comment on
its current state.
Cheers,
Daniel
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 <https://pekepbx.com>
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
*sr-users(a)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
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>
--
Daniel-Constantin Mierla --www.asipto.com <http://www.asipto.com>
www.twitter.com/miconda <http://www.twitter.com/miconda>
--www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
*sr-users(a)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
<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> 
7 Jul
7 Jul
5:13 p.m.
Henning Westerholt writes:
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?
The "development" version (master) of
https://github.com/sems-server/sems is the same as production version.
There is not enough development resources to keep on making new
production branches.
-- Juha
5:19 p.m.
Daniel-Constantin Mierla writes:
If Henning means https://github.com/sems-server/sems by "public
sems", then he does not know what he writes about. It is maintained in
the sense that new contributions and bug fixes will get merged to
master branch.
-- Juha
Public sems
was abandoned years ago.
Maybe abandoned by initial developers, also not getting many new
features. Otherwise, I noticed Juha Heinanen is more or less maintaining
the public version of SEMS. Maybe he can comment on its current state.
5:24 p.m.
David Villasmil writes:
I’m using freeswitch in a very simple way, it receives
a call, makes an api
http request, and based on the response does some prefixing, etc. it also
provides simple conferencing (three-way call) and provides a very detailed
CDR.
I’m wondering if I could replace it with SEMS.
It could be done by sems, but sounds like you could do it with Kamailio
itself too.
5:27 p.m.
Hi Juha,
thank you for the information, understand.
Cheers,
Henning
-----Original Message-----
From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Juha Heinanen
Sent: Wednesday, July 7, 2021 5:13 PM
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] Sipwise SEMS
Henning Westerholt writes:
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?
The "development" version (master) of
https://github.com/sems-server/sems is the same as production version.
There is not enough development resources to keep on making new production branches.
-- Juha
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
5:33 p.m.
Hi Juha,
the "public sems" quote was not from me, but from Jon B. earlier in the thread.
I mentioned initially that I do not follow sems that much, therefore my question.
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 Juha Heinanen
Sent: Wednesday, July 7, 2021 5:19 PM
To: miconda(a)gmail.com; Kamailio (SER) - Users Mailing List
<sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] Sipwise SEMS
Daniel-Constantin Mierla writes:
If Henning means https://github.com/sems-server/sems by "public sems", then he
does not know what he writes about. It is maintained in the sense that new contributions
and bug fixes will get merged to master branch.
-- Juha
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
Public sems
was abandoned years ago.
Maybe abandoned by initial developers, also not getting many new
features. Otherwise, I noticed Juha Heinanen is more or less
maintaining the public version of SEMS. Maybe he can comment on its current state.
5:36 p.m.
Dmitry Sinina writes:
There is also SEMS forked by yeti-switch project
https://github.com/yeti-switch/sems It has a lot new features but it is
not fully compatible with old modules.
Last time I checked, yeti-switch/sems does not have sbc app (at least
not with that name), I had problems with building its dsm app, and it
lacked support for ZRTP.
If these are not show stoppers for someone, then it should be OK to use
yeti-switch/sems.
-- Juha
8 Jul
8 Jul
2:53 p.m.
Currently https://github.com/yeti-switch/sems supports zrtp as well as
srtp-dtls and srtp-sdes. But you are right, old applications like sbc
and dsm requires modifications to run.
On 07.07.21 18:36, Juha Heinanen wrote:
Dmitry Sinina writes:
There is also SEMS forked by yeti-switch project
https://github.com/yeti-switch/sems It has a lot new features but it is
not fully compatible with old modules.
Last time I checked, yeti-switch/sems does
not have sbc app (at least
not with that name), I had problems with building its dsm app, and it
lacked support for ZRTP.
If these are not show stoppers for someone, then it should be OK to use
yeti-switch/sems.
-- Juha
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
2:59 p.m.
Dmitry Sinina writes:
Currently https://github.com/yeti-switch/sems supports
zrtp as well as
srtp-dtls and srtp-sdes. But you are right, old applications like sbc
and dsm requires modifications to run.
What do you mean by "old"? sbc and dsm apps are much younger that many
others.
-- Juha
3:19 p.m.
I mean there are no commits to this modules for years(excluding may be
some cosmetic fixes) when yeti-switch sems core was changed a lot.
On 08.07.21 15:59, Juha Heinanen wrote:
Dmitry Sinina writes:
Currently https://github.com/yeti-switch/sems
supports zrtp as well as
srtp-dtls and srtp-sdes. But you are right, old applications like sbc
and dsm requires modifications to run.
What do you mean by "old"? sbc
and dsm apps are much younger that many
others.
-- Juha
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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 
12 Jul
12 Jul
12:57 p.m.
Hello there,
As i have experienced working with SEMS, freeswitch and Kamailio while
using B2BUA feature, Each of them have pros and cons:
1- The sems is a light sip engine server with several applications (like as
sbc) for using b2bua. All incoming and outgoing calls could go to sems
server for doing b2bua like this:
Incoming<=======>Kamailio<========>Sems<========>Kamailio<=======>outgoing
2- In sems, you could disable rtp realying. It forces sems to work just as
b2bua without anchoring RTP
3- Easy to use different active profiles in routing.
Just a couple of things there are in SEMS. For example, the sems adds
itself (local IP) in Via header, and it couldn't be common in b2bua. like
this:
.
.
.
INVITE sip:200@cloud.domain.com;transport=UDP SIP/2.0
Via: SIP/2.0/UDP
10.10.10.200;branch=z9hG4bK2f53.07a3fd9edaa8c8d609ab2ac6b01a087f.0
*================================>Kamailio
public IP*
*Via: SIP/2.0/UDP
127.0.0.1:5080;received=127.0.0.1;branch=z9hG4bKsPRMNast;rport=5080
===============================>private loopback sems ip*
From: <sip:100@cloud.domain.com
;transport=UDP>;tag=6FFDB493-60EABB3600016ECD-379F9700
To: <sip:200@cloud.domain.com;transport=UDP>
CSeq: 10 INVITE
Call-ID: Y2M1ODQxNTZmMjdkZWZjN2U5MmMyYjBmN2Y2OGY1ODQ._leg2
Route: <sip:mo@127.0.0.1:5060;lr>
Max-Forwards: 69
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO,
SUBSCRIBE
User-Agent: Z 3.3.25608 r25552
Content-Type: application/sdp
Contact: <sip:127.0.0.1:5080;transport=udp>
Content-Length: 246
.
.
.
For this reason, Is there a way to avoid this issue?
Also, Why in Kamailio, there is not b2bua module so that perform all b2bua
functionality? i know it is possible to do this by using other modules like
textops and retransformation ?
Thanks with Best Regards.
Mojtaba
On Thu, Jul 8, 2021 at 5:49 PM Dmitry Sinina <dmitry.sinina(a)onat.edu.ua>
wrote:
I mean there are no commits to this modules for
years(excluding may be
some cosmetic fixes) when yeti-switch sems core was changed a lot.
On 08.07.21 15:59, Juha Heinanen wrote:
--
--Mojtaba Esfandiari.S
Dmitry Sinina writes:
the
sender!
Currently https://github.com/yeti-switch/sems
supports zrtp as well as
srtp-dtls and srtp-sdes. But you are right, old applications like sbc
and dsm requires modifications to run.
What do you mean by "old"? sbc
and dsm apps are much younger that many
others.
-- Juha
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
30 Sep
30 Sep
7:20 p.m.
Thank you Dmitry!
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
On Thu, Jul 8, 2021 at 1:55 PM Dmitry Sinina <dmitry.sinina(a)onat.edu.ua>
wrote:
Currently https://github.com/yeti-switch/sems supports
zrtp as well as
srtp-dtls and srtp-sdes. But you are right, old applications like sbc
and dsm requires modifications to run.
On 07.07.21 18:36, Juha Heinanen wrote:
Dmitry Sinina writes:
the
sender!
There is also SEMS forked by yeti-switch project
https://github.com/yeti-switch/sems It has a lot new features but it is
not fully compatible with old modules.
Last time I checked, yeti-switch/sems does
not have sbc app (at least
not with that name), I had problems with building its dsm app, and it
lacked support for ZRTP.
If these are not show stoppers for someone, then it should be OK to use
yeti-switch/sems.
-- Juha
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)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
936
days inactive
1024
days old
22 comments
10 participants
participants (10)
-
Alex Balashov -
Arsen Semenov -
Daniel-Constantin Mierla -
David Villasmil -
Dmitry Sinina -
E. Schmidbauer -
Henning Westerholt -
Jon Bonilla (Manwe) -
Juha Heinanen -
Mojtaba