Hi Carsten,Yes, Using SEMS as B2BUA would be good plan, But just a question, Do you skip RTP flow to SEMS, too?ThanksOn Mon, Aug 2, 2021 at 1:46 PM Carsten Bock <carsten@ng-voice.com> wrote:Hi,we even take it one step further:Incoming <-> Kamailio <-> SEMS (B2BUA) <-> Kamailio <-> InterconnectWe do this, to limit the required functionality of SEMS to be a B2BUA and we do all further stuff (Number Portability Lookup, Least-Cost-Routing, Message Manipulation, ..) on Kamailio.I almost hate to say this as Kamailian, but one more alternative to SEMS worth checking is OpenSIPS and its b2b modules.Thanks,Carsten--Carsten Bock I CTO & Founderng-voice GmbH
Trostbrücke 1 I 20457 Hamburg I Germany
T +49 40 524 75 93-40 | M +49 179 2021244 I www.ng-voice.comRegistry Office at Local Court Hamburg, HRB 120189
Managing Directors: Dr. David Bachmann, Carsten Bock__________________________________________________________Am Sa., 31. Juli 2021 um 23:24 Uhr schrieb Mojtaba <mespio@gmail.com>:Thanks Guys for your comments.@Gerry, I agree with you, I have a few experiences working with Yate, It could work great in enterprise solutions. Thanks
@Denys, Thanks for sharing your experience, Although its configurations look complicated, But in signaling, It would work great.
Just a question, Let me know which scenario is like that you use?
<operators>-------------------<kamailio/RTPEngine>----------------<SEMS>
or
<operators>----------------<SEMS>-------------------<kamailio/RTPEngine>
On Fri, Jul 30, 2021 at 9:15 AM Denys Pozniak <denys.pozniak@gmail.com> wrote:Hello!We used sems to interconnect with external operators. But with a heavy call load and with the processing of the media stream, it often crashed.
Now we use Kamailio / Rtpengine for media stream processing and sems for signaling processing. We install all this on one server. It probably looks complicated, but it works great.вт, 27 июл. 2021 г. в 16:10, Gerry | Rigatta <gjacobsen@rigatta.com>:Hi,__________________________________________________________Some comments on Yate.Yate works well as a B2BUA. It is very performant and stable. It can bypass media dynamically.The main beauty of Yate is how it processes calls internally. Yate represents calls internally as messages with parameters (caller, callee, codecs …) . While the call passes from the incoming to the outgoing call leg the message parameters can be manipulated by different yate modules. In turn, message parameters can trigger yate modules for some actions, e.g. start a sip call.The Yate internal messaging allows to build with little code complex call logic. E.g a mysql query result can be used directly for routing. E,g, you can build a switch just with a couple of mysql procedures.CheersGerryOn 27 Jul 2021, at 11:35, Karsten Horsmann <khorsmann@gmail.com> wrote:__________________________________________________________Hello,just for the records:You can also bypass media with FreeSWITCH if you want. The overall handling of many parallel calls is still not so high like in SEMS.https://freeswitch.org/confluence/display/FREESWITCH/Proxy+MediaThis is also possible on a per Call base.And you can use different profiles as well in FreeSWITCH.Asterisk Experts will have more knowledge what is possible there, and maybe someone told us whats going on with Yate.Kind regardsKarstenAm Di., 13. Juli 2021 um 10:11 Uhr schrieb Mojtaba <mespio@gmail.com>:Hello there,According to ,https://lists.kamailio.org/pipermail/sr-users/2016-March/092058.html, which talked about B2BUA (just signalling) in Kamailio.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<=======>outgoing2- In sems, you could disable rtp realying. It forces sems to work just as b2bua without anchoring RTP3- Easy to use different active profiles in routing.
Kamailio - Users Mailing List - Non Commercial Discussions
* 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
Kamailio - Users Mailing List - Non Commercial Discussions
* 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
--__________________________________________________________BR,Denys Pozniak
Kamailio - Users Mailing List - Non Commercial Discussions
* 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
----Mojtaba Esfandiari.S__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* 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
Kamailio - Users Mailing List - Non Commercial Discussions
* 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
----Mojtaba Esfandiari.S__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* 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