Re: [OpenSIPS-Users] RTPProxy Docker Image

[Terrance Devor]

Hello David, Similar to what we have with LXC

OpenSIPS - Proxy, Edge Switch, Managing DIDs and Termination routes, CDR,
LB to Asterisk
Asterisk - PBX, IVR
RTPProxy - Media Relay

Everything containerized using docker and deployed to our k8s cluster.

I would appreciate speaking to anyone that has experience in successfully,
or failed, in trying to do this

On Wed, Dec 21, 2022 at 7:57 PM David Villasmil <
david.villasmil.w...@gmail.com> wrote:

> Can you explain more? I.e: params and such?
> Thanks!
>
> On Tue, 20 Dec 2022 at 22:29, Saint Michael  wrote:
>
>> Opensips+ RTPProxy only works fine with plain LXC containers,
>> privileged, which basically have access to all the resources of the
>> box.
>> That is the model I use with great success.
>>
>> On Tue, Dec 20, 2022 at 2:47 PM Brett Nemeroff 
>> wrote:
>> >
>> > Hello Terrance,
>> > I wouldn't really recommend this. RTPProxy is going to use a lot of
>> ports in a very large range. That just doesn't work great in docker, but
>> even worse in K8S.
>> >
>> > I personally would put the RTPProxy outside of K8S. While you might be
>> able to get it to work, you are likely going against some basic design
>> concepts in containerization. I feel like the tech should propel the
>> solution and not be a hindrance to it. In this case, I'm not sure that K8S
>> is buying you anything of value, but instead creating architectural
>> challenges.
>> >
>> > I'd love to hear feedback or experiences from others. There's always
>> something to learn :)
>> > -Brett
>> >
>> > On Tue, Dec 20, 2022 at 11:43 AM Terrance Devor 
>> wrote:
>> >>
>> >> Was it something I said?
>> >>
>> >> Terrance
>> >>
>> >> On Sun, Dec 18, 2022 at 12:50 PM Terrance Devor 
>> wrote:
>> >>>
>> >>> Hello Everyone,
>> >>>
>> >>> Wow! Blast from the past... I am a long time member of this list,
>> been a while.
>> >>>
>> >>> Question, anyone successful in deploying RTPProxy to a dockerized
>> environment? Preferably to a Kubernetes managed environment.
>> >>>
>> >>> Please Help Team :)
>> >>>
>> >>> Kind Regards,
>> >>> Terrance
>> >>
>> >> ___
>> >> Users mailing list
>> >> Users@lists.opensips.org
>> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>> >
>> > ___
>> > Users mailing list
>> > Users@lists.opensips.org
>> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> --
> Regards,
>
> David Villasmil
> email: david.villasmil.w...@gmail.com
> phone: +34669448337
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] RTPProxy Docker Image

[David Villasmil]

Can you explain more? I.e: params and such?
Thanks!

On Tue, 20 Dec 2022 at 22:29, Saint Michael  wrote:

> Opensips+ RTPProxy only works fine with plain LXC containers,
> privileged, which basically have access to all the resources of the
> box.
> That is the model I use with great success.
>
> On Tue, Dec 20, 2022 at 2:47 PM Brett Nemeroff  wrote:
> >
> > Hello Terrance,
> > I wouldn't really recommend this. RTPProxy is going to use a lot of
> ports in a very large range. That just doesn't work great in docker, but
> even worse in K8S.
> >
> > I personally would put the RTPProxy outside of K8S. While you might be
> able to get it to work, you are likely going against some basic design
> concepts in containerization. I feel like the tech should propel the
> solution and not be a hindrance to it. In this case, I'm not sure that K8S
> is buying you anything of value, but instead creating architectural
> challenges.
> >
> > I'd love to hear feedback or experiences from others. There's always
> something to learn :)
> > -Brett
> >
> > On Tue, Dec 20, 2022 at 11:43 AM Terrance Devor 
> wrote:
> >>
> >> Was it something I said?
> >>
> >> Terrance
> >>
> >> On Sun, Dec 18, 2022 at 12:50 PM Terrance Devor 
> wrote:
> >>>
> >>> Hello Everyone,
> >>>
> >>> Wow! Blast from the past... I am a long time member of this list, been
> a while.
> >>>
> >>> Question, anyone successful in deploying RTPProxy to a dockerized
> environment? Preferably to a Kubernetes managed environment.
> >>>
> >>> Please Help Team :)
> >>>
> >>> Kind Regards,
> >>> Terrance
> >>
> >> ___
> >> Users mailing list
> >> Users@lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 
Regards,

David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] RTPProxy Docker Image

[Terrance Devor]

Hello Bret, another approach we are thinking about is put RTPProxy on a
VPC. As for Opensips and Asterisk, they can live on a k8s with the
understanding that they will not deal with media directly.

If anyone can share their experience, I would be interested in hearing from
you.

Do the RTP guys still follow this mailing list?

On Tue, Dec 20, 2022 at 4:31 PM Saint Michael  wrote:

> Opensips+ RTPProxy only works fine with plain LXC containers,
> privileged, which basically have access to all the resources of the
> box.
> That is the model I use with great success.
>
> On Tue, Dec 20, 2022 at 2:47 PM Brett Nemeroff  wrote:
> >
> > Hello Terrance,
> > I wouldn't really recommend this. RTPProxy is going to use a lot of
> ports in a very large range. That just doesn't work great in docker, but
> even worse in K8S.
> >
> > I personally would put the RTPProxy outside of K8S. While you might be
> able to get it to work, you are likely going against some basic design
> concepts in containerization. I feel like the tech should propel the
> solution and not be a hindrance to it. In this case, I'm not sure that K8S
> is buying you anything of value, but instead creating architectural
> challenges.
> >
> > I'd love to hear feedback or experiences from others. There's always
> something to learn :)
> > -Brett
> >
> > On Tue, Dec 20, 2022 at 11:43 AM Terrance Devor 
> wrote:
> >>
> >> Was it something I said?
> >>
> >> Terrance
> >>
> >> On Sun, Dec 18, 2022 at 12:50 PM Terrance Devor 
> wrote:
> >>>
> >>> Hello Everyone,
> >>>
> >>> Wow! Blast from the past... I am a long time member of this list, been
> a while.
> >>>
> >>> Question, anyone successful in deploying RTPProxy to a dockerized
> environment? Preferably to a Kubernetes managed environment.
> >>>
> >>> Please Help Team :)
> >>>
> >>> Kind Regards,
> >>> Terrance
> >>
> >> ___
> >> Users mailing list
> >> Users@lists.opensips.org
> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Introducing OpenSIPS 3.4

[Bogdan-Andrei Iancu]

Dear OpenSIPS'ers,

We got to that time of year when we start baking a new OpenSIPS major 
version. An new year, a new version, a new topic to be addressed. So let 
me introduce you to the upcoming OpenSIPS 3.4 .


For the upcoming OpenSIPS 3.4 release the main focus is on the 
*/consolidation /*topic, from the testing and features perspectives. 
Shortly said, this mainly (not limited) translates into:


 * Performance testing and code profiling
 * Conformity testing with SIP scenarios
 * More MSRP features (chat, encryption, reports)
 * More IMS features (IPsec, SIP Outbound)
 * More Back2Back (better re-bridging )

For the full list with technical description and details, visit :

https://www.opensips.org/Development/Opensips-3-4-Planning


*IMPORTANT*

As community is important to us and we want to align the OpenSIPS 
roadmap with the needs of our users, be part of the shaping and decision 
making for the OpenSIPS 3.4 Dev Plan via this *Feature Survey 
* - any feedback is important and it matters to us.



Best regards and enjoy the winter holidays!!

--
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Bootcamp 5-16 Dec 2022, online
  https://www.opensips.org/training/OpenSIPS_eBootcamp_2022/

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] kamilio's htable equivalent?

[David Villasmil]

Thanks Daniel,

Amazingly enough I had! But then completely forgot about it.

Thanks!!




On Wed, 21 Dec 2022 at 13:26, Daniel Zanutti 
wrote:

> Hey David
>
> Did you take a look at core functions of cache? ->
> https://www.opensips.org/Documentation/Script-CoreFunctions-3-1#toc4
>
>
> On Wed, Dec 21, 2022 at 9:14 AM David Villasmil <
> david.villasmil.w...@gmail.com> wrote:
>
>> Hello folks,
>>
>> I'm trying to find in opensips an equivalent to kamailio's htable module.
>> Opensips' cachedb_local doesn't have autoexpires...
>>
>> Regards,
>>
>> David Villasmil
>> email: david.villasmil.w...@gmail.com
>> phone: +34669448337
>>
> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-- 
Regards,

David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] kamilio's htable equivalent?

[Daniel Zanutti]

Hey David

Did you take a look at core functions of cache? ->
https://www.opensips.org/Documentation/Script-CoreFunctions-3-1#toc4


On Wed, Dec 21, 2022 at 9:14 AM David Villasmil <
david.villasmil.w...@gmail.com> wrote:

> Hello folks,
>
> I'm trying to find in opensips an equivalent to kamailio's htable module.
> Opensips' cachedb_local doesn't have autoexpires...
>
> Regards,
>
> David Villasmil
> email: david.villasmil.w...@gmail.com
> phone: +34669448337
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] kamilio's htable equivalent?

[David Villasmil]

Hello folks,

I'm trying to find in opensips an equivalent to kamailio's htable module.
Opensips' cachedb_local doesn't have autoexpires...

Regards,

David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] b2b_logic modules and transport protocol (TCP/TLS) conversion

[Ross McKillop via Users]

Hi,

I’m hoping I’m missing something obvious here (and explain well enough below 
what the problem is) - I can get logs etc if required of course.

I’m using the OpenSIPS b2bua module(s) in a scenario where one side of the leg 
is TCP and the other is TLS as follows. 

Host A —TLS--->  OpenSIPS —TCP—> Host B

The configuration is something like the below (variables replaced with what 
they contain for clarity) 

b2b_server_new(“s”);
b2b_client_new(“c”, “sip:u...@hostb.example.com:;transport=tcp”, 
“sip:hostb.example.com:;transport=tcp”)
# have also tried the above without the proxy parameter
b2b_init_request(“b2b_ab”, “”, “b2b_ab_request”, “b2b_ab_reply”);

If the incoming A leg is also TCP this works as expected, however if the 
incoming leg is TLS the connection attempt is made to hostb.example.com on port 
5061 (default TLS port, ignoring the  specified in the b2b_client_new call) 

The INVITE RURI is correct (e.g. INVITE 
sip:u...@hostb.example.com:;transport=tcp) but the Contact header contains 
a reference to the TLS listening port (e.g. Contact: 
)

As this is acting as a B2BUA I would have expected the Contact to be the TCP 
interface on the opensips, and the INVITE to be sent to the URI (and transport 
protocol) provided in the b2b_init_request in the config.

I’ve also tried setting  b2bl_from_spec_param as follows;

modparam("b2b_logic", 
"b2bl_from_spec_param”,”sip:opensips.example.com:5060;transport=tcp”) 

However, this doesn’t change the observed behaviour. 

Why is the port and transport selection being ignored, or am I missing 
something? 

(All the above is based on opensips 3.3.2, if the behaviour has been 
changed/corrected in 3.4 then accept my apologies, I’ll be trying that shortly, 
but wanted to ask here first in case I was missing something obvious!) 

Any insight anyone can offer would be much appreciated. 

Best,
Ross
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users