7 Jun
2024
7 Jun
'24
10:15 a.m.
Hi
I wonder if anyone could maybe recommend what to use as signaling B2BUA
to work with Kamailio to handle spiralling / looping calls and to reduce
the number of Route, Via Header and message size, which cause issue
with a large number of CPE.
Requirements:
* New CallID needs to be generated
* Handling Route and Via
* ~ 2000 concurrent calls.
* Preserving custom SIP X- header
* Routing NOTIFY for MWI etc.
Handling RTP is not required!
What I have been looking at more closely:
= FreeSwitch =
Got stuck trying to solve the dependencies to get it to run/build on
ubuntu jammy.
Has anyone experience in running it in a docker container? Will it
perform?
= Sippy =
Very small, very simple, unfortunately removes customer SIP headers and
does not forward NOTIFY. (It's python, so maybe this could be easily
implemented/fixed).
= SEMS =
Does not seem to be actively developed in the last, couple of years.
Looks quite bloated to me for what I need.
= Asterisk =
Each customer header has to be copied, wants to handle RTP and bridge
by issuing Re-Invites. Not sure how to route stuff like NOTIFY.
Also from experience I fear asterisk would translate sip reply codes
(like 608 and 607) it does not know to some 4XX default.
--
Mit freundlichen Grüssen
-Benoît Panizzon- @ HomeOffice und normal erreichbar
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web http://www.imp.ch
______________________________________________________
7 Jun
7 Jun
10:48 a.m.
On Jun 7, 2024, at 10:15 AM, Benoît Panizzon via
sr-users <sr-users(a)lists.kamailio.org> wrote:
= FreeSwitch =
Got stuck trying to solve the dependencies to get it to run/build on
ubuntu jammy.
Has anyone experience in running it in a docker container? Will it
perform?
Have you tried from their repo?
= SEMS =
Does not seem to be actively developed in the last, couple of years.
Looks quite bloated to me for what I need.
SEMS is still updated— as recently even as last month.
* https://github.com/sems-server/sems
Regards,
Fred Posner
p: +1 (352) 664-3733
https://fred.tel
11:21 a.m.
fs docker:
https://github.com/davidcsi/docker-freeswitch
that's what i always use. Performance depends upon the underlying hardware.
I've seen 5000+ channels _handling rtp_.
Regards,
David Villasmil
email: david.villasmil.work(a)gmail.com
phone: +34669448337
On Fri, Jun 7, 2024 at 5:08 PM Fred Posner via sr-users <
sr-users(a)lists.kamailio.org> wrote:
On Jun 7, 2024, at 10:15 AM, Benoît Panizzon via
sr-users <
sr-users(a)lists.kamailio.org> wrote:
= FreeSwitch =
Got stuck trying to solve the dependencies to get it to run/build on
ubuntu jammy.
Has anyone experience in running it in a docker container? Will it
perform?
Have you tried from their repo?
= SEMS =
Does not seem to be actively developed in the last, couple of years.
Looks quite bloated to me for what I need.
SEMS is still updated— as recently even as last month.
* https://github.com/sems-server/sems
Regards,
Fred Posner
p: +1 (352) 664-3733
https://fred.tel
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(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:
11:48 a.m.
Hey Benoit,
I had the same issue with FreeSWITCH on Jammy, if your issue was with
SpanDSP errors I had to use a specific commit (git checkout d540fdf) to get
around it. This was on FreeSWITCH v1.10.10 compiled from the repo.
As a side note to your original issue around message size, I am using TOPOS
to reduce message size which helped with my specific use case. (NAT'd in
cloud so had to use double RR which had double Via as well)
Thanks,
John
On Fri, 7 Jun 2024 at 15:51, Benoît Panizzon via sr-users <
sr-users(a)lists.kamailio.org> wrote:
Hi
I wonder if anyone could maybe recommend what to use as signaling B2BUA
to work with Kamailio to handle spiralling / looping calls and to reduce
the number of Route, Via Header and message size, which cause issue
with a large number of CPE.
Requirements:
* New CallID needs to be generated
* Handling Route and Via
* ~ 2000 concurrent calls.
* Preserving custom SIP X- header
* Routing NOTIFY for MWI etc.
Handling RTP is not required!
What I have been looking at more closely:
= FreeSwitch =
Got stuck trying to solve the dependencies to get it to run/build on
ubuntu jammy.
Has anyone experience in running it in a docker container? Will it
perform?
= Sippy =
Very small, very simple, unfortunately removes customer SIP headers and
does not forward NOTIFY. (It's python, so maybe this could be easily
implemented/fixed).
= SEMS =
Does not seem to be actively developed in the last, couple of years.
Looks quite bloated to me for what I need.
= Asterisk =
Each customer header has to be copied, wants to handle RTP and bridge
by issuing Re-Invites. Not sure how to route stuff like NOTIFY.
Also from experience I fear asterisk would translate sip reply codes
(like 608 and 607) it does not know to some 4XX default.
--
Mit freundlichen Grüssen
-Benoît Panizzon- @ HomeOffice und normal erreichbar
--
I m p r o W a r e A G - Leiter Commerce Kunden
______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00
CH-4133 Pratteln Fax +41 61 826 93 01
Schweiz Web http://www.imp.ch
______________________________________________________
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(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:
23
days inactive
23
days old
3 comments
4 participants
participants (4)
-
Benoît Panizzon -
David Villasmil -
Fred Posner -
Who AmI