[prev in list] [next in list] [prev in thread] [next in thread] 

List:       serusers
Subject:    Re: [SR-Users] which is better for B2BUA
From:       Mojtaba <mespio () gmail ! com>
Date:       2021-07-31 21:22:26
Message-ID: CABVi_EyEMMG3DZFk1DhgXezyfODZgFT3zooqoqPcV=NX=W6Dtg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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.
>>
>> Cheers
>>
>> Gerry
>>
>>
>>
>> On 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+Media
>> This 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 regards
>> Karsten
>>
>> Am 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<=======>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.
>>>
>>> __________________________________________________________
>> 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

[Attachment #5 (text/html)]

<div dir="ltr"><div>Thanks Guys for your comments.</div><div>@Gerry, I agree with \
you, I have a few experiences working with Yate, It could work great in enterprise \
solutions. Thanks</div><div><div class="gmail-gs"><div class="gmail-gE gmail-iv \
gmail-gt"><table class="gmail-cf gmail-gJ" cellpadding="0"><tbody><tr \
class="gmail-acZ"><td class="gmail-gF gmail-gK"><table class="gmail-cf gmail-ix" \
cellpadding="0"><tbody><tr><td class="gmail-c2">@Denys, Thanks for sharing your \
experience, Although its configurations look complicated, But in signaling, It would \
work great.<br>Just a question, Let me know which scenario is like that you \
use?<br><br>&lt;operators&gt;-------------------&lt;kamailio/RTPEngine&gt;------------ \
----&lt;SEMS&gt;<br>or<br>&lt;operators&gt;----------------&lt;SEMS&gt;-------------------&lt;kamailio/RTPEngine&gt;<br><br><div \
class="gmail-gs"><div class="gmail-gE gmail-iv gmail-gt"><table class="gmail-cf \
gmail-gJ" cellpadding="0"><tbody><tr class="gmail-acZ"><td class="gmail-gF \
gmail-gK"><table class="gmail-cf gmail-ix" cellpadding="0"><tbody><tr><td \
class="gmail-c2"><h3 class="gmail-iw"><span class="gmail-qu" role="gridcell" \
tabindex="-1">  <span \
class="gmail-go"></span></span></h3></td></tr></tbody></table></td></tr></tbody></tabl \
e></div></div></td></tr></tbody></table></td></tr></tbody></table></div></div></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 30, 2021 at 9:15 AM \
Denys Pozniak &lt;<a \
href="mailto:denys.pozniak@gmail.com">denys.pozniak@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div \
dir="ltr">Hello!<br><div>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.<br>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.<br></div></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">вт, 27 июл. 2021 г. в 16:10, Gerry | Rigatta \
&lt;<a href="mailto:gjacobsen@rigatta.com" \
target="_blank">gjacobsen@rigatta.com</a>&gt;:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div>Hi,  <div><div><span \
style="font-family:ArialMT"><br></span></div><div><span \
style="font-family:ArialMT">Some comments on Yate.  </span></div><div><span \
style="font-family:ArialMT"><br></span></div><div>Yate works well as a B2BUA. It is \
very performant and stable. It can bypass media dynamically.  \
</div><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Cheers</div><div><br></div><div>Gerry</div><div><br></div><div><br></div><div><div><br><blockquote \
type="cite"><div>On 27 Jul 2021, at 11:35, Karsten Horsmann &lt;<a \
href="mailto:khorsmann@gmail.com" target="_blank">khorsmann@gmail.com</a>&gt; \
wrote:</div><br><div><div dir="ltr"><div>Hello,</div><div><br></div><div>just for the \
records:</div><div><br></div><div>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.</div><div><br></div><a \
href="https://freeswitch.org/confluence/display/FREESWITCH/Proxy+Media" \
target="_blank">https://freeswitch.org/confluence/display/FREESWITCH/Proxy+Media</a><div>This \
is also possible on a per Call base.</div><div><br></div><div>And you can use \
different  profiles as well in FreeSWITCH.  </div><div><br></div><div>Asterisk \
Experts will have more knowledge what is possible there, and maybe someone told us \
whats going on with Yate.</div><div><br></div><div>Kind  \
regards</div><div>Karsten</div><div><div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">Am Di., 13. Juli 2021 um 10:11  Uhr schrieb Mojtaba &lt;<a \
href="mailto:mespio@gmail.com" \
target="_blank">mespio@gmail.com</a>&gt;:<br></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br clear="all"><div>Hello \
there,</div><div>According to ,<a \
href="https://lists.kamailio.org/pipermail/sr-users/2016-March/092058.html" \
target="_blank">https://lists.kamailio.org/pipermail/sr-users/2016-March/092058.html</a>, \
which talked about   B2BUA (just signalling) in Kamailio.<br></div><div>As i have \
experienced working with SEMS, freeswitch and Kamailio while using B2BUA feature, \
Each of them have pros and cons:</div><div>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:</div><div><br></div><div>Incoming&lt;=======&gt;Kamailio&lt;========&gt;Sems&lt;========&gt;Kamailio&lt;=======&gt;outgoing</div><div><br></div><div>2- \
In sems, you could disable rtp realying. It forces sems to work just as b2bua without \
anchoring RTP<br></div><div>3- Easy to use different active profiles in \
routing.</div><div></div><div><br></div></div></blockquote></div></div></div></div> \
__________________________________________________________<br>Kamailio - Users \
Mailing List - Non Commercial Discussions<br>   * <a \
href="mailto:sr-users@lists.kamailio.org" \
target="_blank">sr-users@lists.kamailio.org</a><br>Important: keep the mailing list \
in the recipients, do not reply only to the sender!<br>Edit mailing list options or \
unsubscribe:<br>   * <a \
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" \
target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br></ \
div></blockquote></div><br></div></div></div>__________________________________________________________<br>
 Kamailio - Users Mailing List - Non Commercial Discussions<br>
   * <a href="mailto:sr-users@lists.kamailio.org" \
                target="_blank">sr-users@lists.kamailio.org</a><br>
Important: keep the mailing list in the recipients, do not reply only to the \
sender!<br> Edit mailing list options or unsubscribe:<br>
   * <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" \
rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
 </blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div \
dir="ltr"><br><div><div>BR,</div><div>Denys \
Pozniak<br></div><div><br></div><div><br></div></div></div></div> \
__________________________________________________________<br> Kamailio - Users \
                Mailing List - Non Commercial Discussions<br>
   * <a href="mailto:sr-users@lists.kamailio.org" \
                target="_blank">sr-users@lists.kamailio.org</a><br>
Important: keep the mailing list in the recipients, do not reply only to the \
sender!<br> Edit mailing list options or unsubscribe:<br>
   * <a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users" \
rel="noreferrer" target="_blank">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><br>
 </blockquote></div><br clear="all"><br>-- <br><div dir="ltr" \
class="gmail_signature">--Mojtaba Esfandiari.S</div>



__________________________________________________________
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


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic