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. 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? I know it is possible to do this by using other modules like textops and retransformation ? And why in Kamailio, there is no b2bua module to perform all b2bua functionality, yet? Thanks with Best Regards.
Hello,
every SIP UA that sends out a request must add a Via header with own address, not matter is the originating UA, intermediary SBC or proxy. The SBC/B2BUA, remove incoming Via headers, but they add one with onw address, otherwise routing of replies does not work.
Anyhow, if you need topology hiding for calls, look at topos or topoh modules in Kamailio.
Cheers, Daniel
On 13.07.21 10:08, Mojtaba wrote:
Hello there, According to ,https://lists.kamailio.org/pipermail/sr-users/2016-March/092058.html 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. 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 mailto:sip%3A200@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 mailto:sip%3A100@cloud.domain.com;transport=UDP>;tag=6FFDB493-60EABB3600016ECD-379F9700 To: <sip:200@cloud.domain.com mailto:sip%3A200@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? I know it is possible to do this by using other modules like textops and retransformation ? And why in Kamailio, there is no b2bua module to perform all b2bua functionality, yet? Thanks with Best Regards.
-- --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:
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.
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 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 mailto:mespio@gmail.com>:
Hello there, According to ,https://lists.kamailio.org/pipermail/sr-users/2016-March/092058.html 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:
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:
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:
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:
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:
--
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:
Hi,
we even take it one step further: Incoming <-> Kamailio <-> SEMS (B2BUA) <-> Kamailio <-> Interconnect
We 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 & Founder
ng-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.com
Registry 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.
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:
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:
--
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:
-- --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:
Hi Carsten, Yes, Using SEMS as B2BUA would be good plan, But just a question, Do you skip RTP flow to SEMS, too? Thanks
On 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 <-> Interconnect
We 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 & Founder
ng-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.com
Registry 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.
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:
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:
--
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:
-- --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:
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:
Hi,
We don't do RTP on this setup, as we only use it for connecting different Consumer-Voice-Platforms with various upstream carriers.
We did trigger RTPEngine once from Kamailio for connecting IPv6 to IPv4 carriers, but we've removed that meanwhile.
Thanks, Carsten
Carsten Bock I CTO & Founder
ng-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.com
Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock
Mojtaba mespio@gmail.com schrieb am Mo., 2. Aug. 2021, 13:04:
Hi Carsten, Yes, Using SEMS as B2BUA would be good plan, But just a question, Do you skip RTP flow to SEMS, too? Thanks
On 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 <-> Interconnect
We 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 & Founder
ng-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.com
Registry 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.
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:
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:
--
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:
-- --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:
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:
-- --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:
@Mojtaba
Just a question, Let me know which scenario is like that you use?
<operators>----------------<SEMS/RTPengine>-------------------<kamailio> -------------------<core>
<SEMS/RTPengine> - this server has 2 interfaces: local and public <kamailio> - controls RTPengine and rewrites SDP
пн, 2 авг. 2021 г. в 20:36, Carsten Bock carsten@ng-voice.com:
Hi,
We don't do RTP on this setup, as we only use it for connecting different Consumer-Voice-Platforms with various upstream carriers.
We did trigger RTPEngine once from Kamailio for connecting IPv6 to IPv4 carriers, but we've removed that meanwhile.
Thanks, Carsten
Carsten Bock I CTO & Founder
ng-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.com
Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock
Mojtaba mespio@gmail.com schrieb am Mo., 2. Aug. 2021, 13:04:
Hi Carsten, Yes, Using SEMS as B2BUA would be good plan, But just a question, Do you skip RTP flow to SEMS, too? Thanks
On 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 <-> Interconnect
We 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 & Founder
ng-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.com
Registry 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.
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:
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:
--
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:
-- --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:
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:
-- --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:
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:
-
Carsten Bock -
Daniel-Constantin Mierla -
Denys Pozniak -
Gerry | Rigatta -
Karsten Horsmann -
Mojtaba