Create new listener on the fly

List overview All Threads
Download

newer

older

RLS is not sending Notify on...

ims ipsec connectivity

H Yavari

25 Oct 2022 25 Oct '22

12:43 p.m.

Hi Kamailio community, I am running an IPsec server beside Kamailio, so I am interested to know if there is any method to create a SIP listener on a specific port on the fly. I mean, when I create the IPsec SAs through the IPsec server, I ask Kamailio to create a listener/handler for that port too.This case might be very rare, but it is always good to hear community ideas. Thank you. Regards,Hossein

Attachments:

attachment.html (text/html — 987 bytes)

Show replies by date

Alex Balashov

25 Oct 25 Oct

3:59 p.m.

Hi, Unfortunately, for a variety of architectural reasons, this is not practical. — Alex

...

On Oct 25, 2022, at 12:43 PM, H Yavari <hyavari(a)rocketmail.com> wrote: Hi Kamailio community, I am running an IPsec server beside Kamailio, so I am interested to know if there is any method to create a SIP listener on a specific port on the fly. I mean, when I create the IPsec SAs through the IPsec server, I ask Kamailio to create a listener/handler for that port too. This case might be very rare, but it is always good to hear community ideas. Thank you. Regards, Hossein __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users(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: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

H Yavari

4:14 p.m.

Thanks Alex.Is there any document or material that tells more about those reasons? Regards,Hossein On Tuesday, October 25, 2022 at 01:00:18 PM PDT, Alex Balashov <abalashov(a)evaristesys.com> wrote: Hi, Unfortunately, for a variety of architectural reasons, this is not practical. — Alex

...

Alex Balashov

4:27 p.m.

Well, no, it just stems from some knowledge of Kamailio’s multiprocess architecture. Kamailio uses a static pool of preforked SIP worker processes, and this is initialised once upon startup. These child processes are spawned for every listener, and communicate and share data using SysV IPC and shared memory. The shared memory pool is likewise initialised upon startup, as is the small fixed-size area of private memory associated with each other worker process (“package memory”). While perhaps not strictly impossible to alter, this setup isn’t particularly amenable to the dynamic creation and destruction of listeners, or the additional child processes they beget. The child processes need to be forked on startup, before their heap is laden with runtime baggage. All this is relatively expensive to initialise. — Alex

...

On Oct 25, 2022, at 4:14 PM, H Yavari <hyavari(a)rocketmail.com> wrote: Thanks Alex. Is there any document or material that tells more about those reasons? Regards, Hossein On Tuesday, October 25, 2022 at 01:00:18 PM PDT, Alex Balashov <abalashov(a)evaristesys.com> wrote: Hi, Unfortunately, for a variety of architectural reasons, this is not practical. — Alex

__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users(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: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

H Yavari

5:02 p.m.

Thanks Alex for your elaboration; you are right. This is the reason that the current ims_ipsec module will create a bunch of listeners at startup that looks not efficient. Regards,Hossein On Tuesday, October 25, 2022 at 01:28:38 PM PDT, Alex Balashov <abalashov(a)evaristesys.com> wrote: Well, no, it just stems from some knowledge of Kamailio’s multiprocess architecture. Kamailio uses a static pool of preforked SIP worker processes, and this is initialised once upon startup. These child processes are spawned for every listener, and communicate and share data using SysV IPC and shared memory. The shared memory pool is likewise initialised upon startup, as is the small fixed-size area of private memory associated with each other worker process (“package memory”). While perhaps not strictly impossible to alter, this setup isn’t particularly amenable to the dynamic creation and destruction of listeners, or the additional child processes they beget. The child processes need to be forked on startup, before their heap is laden with runtime baggage. All this is relatively expensive to initialise. — Alex

...

Carsten Bock

26 Oct 26 Oct

9:34 a.m.

Hi Hossein, yes, you are right, it is in-efficient. It may be fine for a private network/PoC/Lab/ or anything else small, but it will not really work for a commercial network - for that you need something different. Thanks, Carsten -- Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock Am Di., 25. Okt. 2022 um 23:03 Uhr schrieb H Yavari <hyavari(a)rocketmail.com

...

Thanks Alex for your elaboration; you are right. This is the reason that the current ims_ipsec module will create a bunch of listeners at startup that looks not efficient. Regards, Hossein On Tuesday, October 25, 2022 at 01:28:38 PM PDT, Alex Balashov < abalashov(a)evaristesys.com> wrote: Well, no, it just stems from some knowledge of Kamailio’s multiprocess architecture. Kamailio uses a static pool of preforked SIP worker processes, and this is initialised once upon startup. These child processes are spawned for every listener, and communicate and share data using SysV IPC and shared memory. The shared memory pool is likewise initialised upon startup, as is the small fixed-size area of private memory associated with each other worker process (“package memory”). While perhaps not strictly impossible to alter, this setup isn’t particularly amenable to the dynamic creation and destruction of listeners, or the additional child processes they beget. The child processes need to be forked on startup, before their heap is laden with runtime baggage. All this is relatively expensive to initialise. — Alex

abalashov(a)evaristesys.com> wrote:

Hi, Unfortunately, for a variety of architectural reasons, this is not

practical.

— Alex > On Oct 25, 2022, at 12:43 PM, H Yavari <hyavari(a)rocketmail.com> wrote: > > Hi Kamailio community, > > > I am running an IPsec server beside Kamailio, so I am interested to

know if there is any method to create a SIP listener on a specific port on the fly. I mean, when I create the IPsec SAs through the IPsec server, I ask Kamailio to create a listener/handler for that port too.

> This case might be very rare, but it is always good to hear community

ideas.

Thank you. Regards, Hossein

> __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > sr-users(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: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

the sender!

Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

the sender!

Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

H Yavari

12:26 p.m.

Hi Casrten, Thanks for the comment. I know you provide IMS, have you contributed to Kamailio IPsec, or do you have something in-house solution for this part? (I hope this question will not be off-topic) BRHossein On Wednesday, October 26, 2022 at 06:37:33 AM PDT, Carsten Bock <carsten(a)ng-voice.com> wrote: Hi Hossein, yes, you are right, it is in-efficient. It may be fine for a private network/PoC/Lab/ or anything else small, but it will not really work for a commercial network - for that you need something different. Thanks,Carsten --Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock Am Di., 25. Okt. 2022 um 23:03 Uhr schrieb H Yavari <hyavari(a)rocketmail.com>om>: Thanks Alex for your elaboration; you are right. This is the reason that the current ims_ipsec module will create a bunch of listeners at startup that looks not efficient. Regards,Hossein On Tuesday, October 25, 2022 at 01:28:38 PM PDT, Alex Balashov <abalashov(a)evaristesys.com> wrote: Well, no, it just stems from some knowledge of Kamailio’s multiprocess architecture. Kamailio uses a static pool of preforked SIP worker processes, and this is initialised once upon startup. These child processes are spawned for every listener, and communicate and share data using SysV IPC and shared memory. The shared memory pool is likewise initialised upon startup, as is the small fixed-size area of private memory associated with each other worker process (“package memory”). While perhaps not strictly impossible to alter, this setup isn’t particularly amenable to the dynamic creation and destruction of listeners, or the additional child processes they beget. The child processes need to be forked on startup, before their heap is laden with runtime baggage. All this is relatively expensive to initialise. — Alex

...

Carsten Bock

27 Oct 27 Oct

11:20 a.m.

Hi Hossein, due to those limitations, we are using a custom, in-house solution for our MNO/MVNO deployments, which we haven't released as open-source (yet). Thanks, Carsten -- Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock Am Mi., 26. Okt. 2022 um 18:29 Uhr schrieb H Yavari <hyavari(a)rocketmail.com

...

> Hi Casrten, > > Thanks for the comment. I know you provide IMS, have you contributed to > Kamailio IPsec, or do you have something in-house solution for this part? > (I hope this question will not be off-topic) > > BR > Hossein > > > On Wednesday, October 26, 2022 at 06:37:33 AM PDT, Carsten Bock < > carsten(a)ng-voice.com> wrote: > > > Hi Hossein, > > yes, you are right, it is in-efficient. It may be fine for a private > network/PoC/Lab/ or anything else small, but it will not really work for a > commercial network - for that you need something different. > > Thanks, > Carsten > -- > Carsten Bock I CTO & Founder > > ng-voice GmbH > > Trostbrücke 1 I 20457 Hamburg I Germany > T +49 179 2021244 I www.ng-voice.com > > Registry Office at Local Court Hamburg, HRB 120189 > Managing Directors: Dr. David Bachmann, Carsten Bock > > > Am Di., 25. Okt. 2022 um 23:03 Uhr schrieb H Yavari < > hyavari(a)rocketmail.com

...

> > Thanks Alex for your elaboration; you are right. > This is the reason that the current ims_ipsec module will create a bunch > of listeners at startup that looks not efficient. > > > Regards, > Hossein > > > On Tuesday, October 25, 2022 at 01:28:38 PM PDT, Alex Balashov < > abalashov(a)evaristesys.com> wrote: > > > Well, no, it just stems from some knowledge of Kamailio’s multiprocess > architecture. > > Kamailio uses a static pool of preforked SIP worker processes, and this is > initialised once upon startup. These child processes are spawned for every > listener, and communicate and share data using SysV IPC and shared memory. > The shared memory pool is likewise initialised upon startup, as is the > small fixed-size area of private memory associated with each other worker > process (“package memory”). > > While perhaps not strictly impossible to alter, this setup isn’t > particularly amenable to the dynamic creation and destruction of listeners, > or the additional child processes they beget. The child processes need to > be forked on startup, before their heap is laden with runtime baggage. All > this is relatively expensive to initialise. > > — Alex > > > On Oct 25, 2022, at 4:14 PM, H Yavari <hyavari(a)rocketmail.com> wrote: > > > > Thanks Alex. > > Is there any document or material that tells more about those reasons? > > > > > > Regards, > > Hossein > > > > > > On Tuesday, October 25, 2022 at 01:00:18 PM PDT, Alex Balashov < > abalashov(a)evaristesys.com> wrote: > > > > > > Hi, > > > > Unfortunately, for a variety of architectural reasons, this is not > practical. > > > > — Alex > > > > > On Oct 25, 2022, at 12:43 PM, H Yavari <hyavari(a)rocketmail.com> wrote: > > > > > > Hi Kamailio community, > > > > > > > > > I am running an IPsec server beside Kamailio, so I am interested to > know if there is any method to create a SIP listener on a specific port on > the fly. I mean, when I create the IPsec SAs through the IPsec server, I > ask Kamailio to create a listener/handler for that port too. > > > This case might be very rare, but it is always good to hear community > ideas. > > > > > > Thank you. > > > > > > Regards, > > > Hossein > > > > > __________________________________________________________ > > > Kamailio - Users Mailing List - Non Commercial Discussions > > > sr-users(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: > > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > -- > > Alex Balashov | Principal | Evariste Systems LLC > > > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > > > > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions > > sr-users(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: > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions > > sr-users(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: > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > sr-users(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: > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > sr-users(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: > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > sr-users(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: > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > sr-users(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: > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >

Oleg Belousov

23 Nov 23 Nov

10:03 a.m.

...

Hi Casrten, Thanks for the comment. I know you provide IMS, have you contributed to Kamailio IPsec, or do you have something in-house solution for this part? (I hope this question will not be off-topic) BR Hossein On Wednesday, October 26, 2022 at 06:37:33 AM PDT, Carsten Bock < carsten(a)ng-voice.com> wrote: Hi Hossein, yes, you are right, it is in-efficient. It may be fine for a private network/PoC/Lab/ or anything else small, but it will not really work for a commercial network - for that you need something different. Thanks, Carsten -- Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock Am Di., 25. Okt. 2022 um 23:03 Uhr schrieb H Yavari < hyavari(a)rocketmail.com>gt;: Thanks Alex for your elaboration; you are right. This is the reason that the current ims_ipsec module will create a bunch of listeners at startup that looks not efficient. Regards, Hossein On Tuesday, October 25, 2022 at 01:28:38 PM PDT, Alex Balashov < abalashov(a)evaristesys.com> wrote: Well, no, it just stems from some knowledge of Kamailio’s multiprocess architecture. Kamailio uses a static pool of preforked SIP worker processes, and this is initialised once upon startup. These child processes are spawned for every listener, and communicate and share data using SysV IPC and shared memory. The shared memory pool is likewise initialised upon startup, as is the small fixed-size area of private memory associated with each other worker process (“package memory”). While perhaps not strictly impossible to alter, this setup isn’t particularly amenable to the dynamic creation and destruction of listeners, or the additional child processes they beget. The child processes need to be forked on startup, before their heap is laden with runtime baggage. All this is relatively expensive to initialise. — Alex

abalashov(a)evaristesys.com> wrote:

Hi, Unfortunately, for a variety of architectural reasons, this is not

practical.

— Alex > On Oct 25, 2022, at 12:43 PM, H Yavari <hyavari(a)rocketmail.com>

wrote:

> > Hi Kamailio community, > > > I am running an IPsec server beside Kamailio, so I am interested to

> This case might be very rare, but it is always good to hear community

ideas.

Thank you. Regards, Hossein

to the sender!

Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

to the sender!

Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

to the sender!

Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla

10:38 a.m.

Hello, noting I don't use the ims modules and I do not know what they are supposed to do, but the initial design for the pool of worker processes was to be able to call module init and child init callbacks before any traffic is handled. Alex provided details on memory initialization as well. Case by case a module can listen on additional sockets, like ctl does for rpc commands, or lwsc with websocket client connections. If an ims module need work with new sockets, then the module can implement the mechanism for it, the developer has the whole C language at hand. The implementation tcp layer does it with new tcp connections, having a tcp connections manager. Obviously, if someone wants to contribute it for the classic sip workers, a PR can be made, it can be merged upon review. Cheers, Daniel On 23.11.22 16:03, Oleg Belousov wrote:

...

Hello. I'm wondering why not having the ability to create a SIP listener on the fly/usage instead of bunch of listeners at startup can be a limitation. I believe each listener can serve multiple ipsec connections, or it is not the case? -- obelousov.tel <http://obelousov.tel> On Thu, Oct 27, 2022 at 5:26 PM Carsten Bock <carsten(a)ng-voice.com> wrote: Hi Hossein, due to those limitations, we are using a custom, in-house solution for our MNO/MVNO deployments, which we haven't released as open-source (yet). Thanks, Carsten -- Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com <http://www.ng-voice.com/> Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock Am Mi., 26. Okt. 2022 um 18:29 Uhr schrieb H Yavari <hyavari(a)rocketmail.com>om>: Hi Casrten, Thanks for the comment. I know you provide IMS, have you contributed to Kamailio IPsec, or do you have something in-house solution for this part? (I hope this question will not be off-topic) BR Hossein On Wednesday, October 26, 2022 at 06:37:33 AM PDT, Carsten Bock <carsten(a)ng-voice.com> wrote: Hi Hossein, yes, you are right, it is in-efficient. It may be fine for a private network/PoC/Lab/ or anything else small, but it will not really work for a commercial network - for that you need something different. Thanks, Carsten -- Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 179 2021244 I www.ng-voice.com <http://www.ng-voice.com/> Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock Am Di., 25. Okt. 2022 um 23:03 Uhr schrieb H Yavari <hyavari(a)rocketmail.com>om>: Thanks Alex for your elaboration; you are right. This is the reason that the current ims_ipsec module will create a bunch of listeners at startup that looks not efficient. Regards, Hossein On Tuesday, October 25, 2022 at 01:28:38 PM PDT, Alex Balashov <abalashov(a)evaristesys.com> wrote: Well, no, it just stems from some knowledge of Kamailio’s multiprocess architecture. Kamailio uses a static pool of preforked SIP worker processes, and this is initialised once upon startup. These child processes are spawned for every listener, and communicate and share data using SysV IPC and shared memory. The shared memory pool is likewise initialised upon startup, as is the small fixed-size area of private memory associated with each other worker process (“package memory”). While perhaps not strictly impossible to alter, this setup isn’t particularly amenable to the dynamic creation and destruction of listeners, or the additional child processes they beget. The child processes need to be forked on startup, before their heap is laden with runtime baggage. All this is relatively expensive to initialise. — Alex

On Oct 25, 2022, at 4:14 PM, H Yavari

<hyavari(a)rocketmail.com> wrote:

Thanks Alex. Is there any document or material that tells more about

those reasons?

Regards, Hossein On Tuesday, October 25, 2022 at 01:00:18 PM PDT, Alex

Balashov <abalashov(a)evaristesys.com> wrote:

Hi, Unfortunately, for a variety of architectural reasons,

this is not practical.

— Alex > On Oct 25, 2022, at 12:43 PM, H Yavari

<hyavari(a)rocketmail.com> wrote:

> > Hi Kamailio community, > > > I am running an IPsec server beside Kamailio, so I am

interested to know if there is any method to create a SIP listener on a specific port on the fly. I mean, when I create the IPsec SAs through the IPsec server, I ask Kamailio to create a listener/handler for that port too.

> This case might be very rare, but it is always good to

hear community ideas.

Thank you. Regards, Hossein

not reply only to the sender!

> Edit mailing list options or unsubscribe: >

https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

not reply only to the sender!

Edit mailing list options or unsubscribe:

https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

not reply only to the sender!

Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users(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: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users(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: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users(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: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users(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: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users(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: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users(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: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

769

days inactive

798

days old

sr-users@lists.kamailio.org

Manage subscription

9 comments

5 participants

tags (0)

participants (5)

Alex Balashov
Carsten Bock
Daniel-Constantin Mierla
H Yavari
Oleg Belousov