From razvan at opensips.org  Mon Jan 22 15:05:55 2024
From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=)
Date: Mon, 22 Jan 2024 17:05:55 +0200
Subject: [WG-IMS] OpenSIPS IMS at Fosdem'24
Message-ID: <e830ea1d-2e1e-449f-8933-a4d93463f65d@opensips.org>

Hi, Everyone!

This year history repeats itself, thus myself (Răzvan Crainea) and Liviu 
Chircu will be representing OpenSIPS at the Fosdem'24 conference, where 
will be talking about how you can Provide VoLTE and/or VoNR for IMS 
using OpenSIPS 3.5.
This talk will present the way OpenSIPS is tackling its IMS 
implementation, and will contain a lot of the topics that we developed
within the OpenSIPS IMS Working Group[1] - so if you are interested in 
the topic, make sure you subscribe (if you haven't already) to the group 
and bring your valuable contribution the the IMS topic.
Our presentation starts on Saturday, 17:50[1] in room H.1302, Real Time 
Communications (RTC) devroom[2]. We hope to see as many of you as possible!

[1] http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims
[2] 
https://fosdem.org/2024/schedule/event/fosdem-2024-3614-provide-volte-vonr-using-opensips-3-5/

Happy hacking,
-- 
Răzvan Crainea
OpenSIPS Core Developer / SIPhub CTO
http://www.opensips-solutions.com / https://www.siphub.com


From gmaruzz at gmail.com  Mon Jan 22 15:14:36 2024
From: gmaruzz at gmail.com (Giovanni Maruzzelli)
Date: Mon, 22 Jan 2024 16:14:36 +0100
Subject: [WG-IMS] OpenSIPS IMS at Fosdem'24
In-Reply-To: <e830ea1d-2e1e-449f-8933-a4d93463f65d@opensips.org>
References: <e830ea1d-2e1e-449f-8933-a4d93463f65d@opensips.org>
Message-ID: <CALXCt0qfPhD-9ST57JvB4vv3YBoZssFoCHttWADBw4f07rVzOg@mail.gmail.com>

yeeeeeeeeeeeeee!!!!!!

-giovanni

On Mon, Jan 22, 2024 at 4:06 PM Răzvan Crainea <razvan at opensips.org> wrote:

> Hi, Everyone!
>
> This year history repeats itself, thus myself (Răzvan Crainea) and Liviu
> Chircu will be representing OpenSIPS at the Fosdem'24 conference, where
> will be talking about how you can Provide VoLTE and/or VoNR for IMS
> using OpenSIPS 3.5.
> This talk will present the way OpenSIPS is tackling its IMS
> implementation, and will contain a lot of the topics that we developed
> within the OpenSIPS IMS Working Group[1] - so if you are interested in
> the topic, make sure you subscribe (if you haven't already) to the group
> and bring your valuable contribution the the IMS topic.
> Our presentation starts on Saturday, 17:50[1] in room H.1302, Real Time
> Communications (RTC) devroom[2]. We hope to see as many of you as possible!
>
> [1] http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims
> [2]
>
> https://fosdem.org/2024/schedule/event/fosdem-2024-3614-provide-volte-vonr-using-opensips-3-5/
>
> Happy hacking,
> --
> Răzvan Crainea
> OpenSIPS Core Developer / SIPhub CTO
> http://www.opensips-solutions.com / https://www.siphub.com
>
> _______________________________________________
> Wg-ims mailing list
> Wg-ims at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims
>


-- 
Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/wg-ims/attachments/20240122/b3da3169/attachment.html>

From bogdan at opensips.org  Wed Jan 24 13:10:00 2024
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 24 Jan 2024 15:10:00 +0200
Subject: [WG-IMS] [RFC] HTTP/2 server support for IMS/5G
Message-ID: <73caf9ee-55c9-4cb0-b23c-2685cba68836@opensips.org>

Hi all,

In the IMS world there is a strong need for OpenSIPS to act as server 
for some non-SIP protocols like DIAMETER - this is already on the 
roadmap, part of tech requirements from the IMS Working Group within 
OpenSIPS project. BTW, Liviu will update on this topic within the next days.

Now, in the 5G standard, HTTP/2 is defined as replacement (want to be) 
for DIAMETER. If acting as HTTP/2 client from within OpenSIPS is rather 
trivial (using the rest_client module), the question that arise here is:
      Does anyone see the need for *HTTP/2 server support*, similar to 
the DIAMETER one ??

Is this need more than a theoretical one, with a practical usage for now 
or near future? if so, is anyone willing to get involved into some 
testing here ?

Best regards,

-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/wg-ims/attachments/20240124/208b0f1e/attachment.html>

From a.g at officering.com  Wed Jan 24 14:31:30 2024
From: a.g at officering.com (Alex Goulis)
Date: Wed, 24 Jan 2024 08:31:30 -0600
Subject: [WG-IMS] [RFC] HTTP/2 server support for IMS/5G
In-Reply-To: <73caf9ee-55c9-4cb0-b23c-2685cba68836@opensips.org>
References: <73caf9ee-55c9-4cb0-b23c-2685cba68836@opensips.org>
Message-ID: <CAFyhkvF0=m8J-68St-5-jAJnN64BpE=0TzDwj1q2XwgV5bi90g@mail.gmail.com>

Although I don't see a need to actually replace the diameter you might want
to consider that this is kind of bleeding edge stuff and the more choices
you have for interfacing the better.

The development and maturity of tools available is very fast and fluid and
in the future there might actually be a bona fide need to use the HTTP2

On Wed, Jan 24, 2024, 7:10 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi all,
>
> In the IMS world there is a strong need for OpenSIPS to act as server for
> some non-SIP protocols like DIAMETER - this is already on the roadmap, part
> of tech requirements from the IMS Working Group within OpenSIPS project.
> BTW, Liviu will update on this topic within the next days.
>
> Now, in the 5G standard, HTTP/2 is defined as replacement (want to be) for
> DIAMETER. If acting as HTTP/2 client from within OpenSIPS is rather trivial
> (using the rest_client module), the question that arise here is:
>      Does anyone see the need for *HTTP/2 server support*, similar to the
> DIAMETER one ??
>
> Is this need more than a theoretical one, with a practical usage for now
> or near future? if so, is anyone willing to get involved into some testing
> here ?
>
> Best regards,
>
> --
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> _______________________________________________
> Wg-ims mailing list
> Wg-ims at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/wg-ims/attachments/20240124/15da03a6/attachment.html>

From liviu at opensips.org  Thu Jan 25 16:07:51 2024
From: liviu at opensips.org (Liviu Chircu)
Date: Thu, 25 Jan 2024 18:07:51 +0200
Subject: [WG-IMS] Diameter Server Support
Message-ID: <1b99627c-41ac-e6a6-08a4-8cac3d93b7dc@opensips.org>

Hi all,

One of the first items on the list of expanding the IMS capabilities of 
OpenSIPS is to add support for *processing* *Diameter requests*, not 
just originating them.  Such requests could be a requirement in a 
variety of scenarios, including but not limited to:

* Diameter request (event) when a device loses connection
* Service profile updates sent by the HSS in the form of a Diameter 
request -- Push Profile Request (PPR) 
<https://www.rfc-editor.org/rfc/rfc4740.html#page-41> command, 
especially useful when REGISTER'ing over very long durations (typical in 
IMS)
* Diameter request for terminating a registration -- Registration 
Termination Request (RTR) 
<https://www.rfc-editor.org/rfc/rfc4740.html#page-39> command
* several others

Regarding the implementation, we have already brainstormed the 
/opensips.cfg/ interaction, which will be as follows:

* config: since we're going to be using the freeDiameter library, any 
Diameter commands supported by the OpenSIPS server and their respective 
AVPs are to be extensively defined in the freeDiameter configuration 
file, pre-startup
* runtime: an event route named "*E_DM_<command>*", if any, shall be 
triggered on each Diameter request.  Available parameters:
   - *$param(sess_id)* -- containing the session's unique ID (think of 
it as a transaction ID), which will be needed when building the reply.  
Ideally, this variable is only for informational/logging purposes, with 
the reply being naturally constructed to include the correct Session ID 
by OpenSIPS
   - *$param(app_id)* -- the Diameter Application ID
   - *$param(cmd_code)* -- the Diameter Command Code
   - *$param(avps_json)* -- all AVPs in the request
* runtime: script writers will process the request data, then build a 
*JSON with the AVPs* to be included in the reply
* runtime: finally, the JSON is passed to a new *dm_send_reply()* 
function, similar to the existing dm_send_request() 
<https://opensips.org/docs/modules/3.4.x/aaa_diameter.html#func_dm_send_request>.

Both receival and sending of Diameter messages will be done by the 
existing freeDiameter process, forked by aaa_diameter 
<https://opensips.org/docs/modules/3.4.x/aaa_diameter.html>. OpenSIPS 
workers will interact with this process asynchronously both when 
receiving requests from the Server Thread (to be serialized & passed 
over via a SHM pointer), as well as when directing replies to be 
originated by the freeDiameter Client Thread (similar interaction, via a 
SHM'ized JSON string).

While the development is ongoing, do let us know if there is any special 
request in terms of the above that may have been missed, or maybe w.r.t. 
your interactions with the freeDiameter library in general: are you 
happy with it?  What are some goods/bads around it?

Best regards,

-- 
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 May 14-17 Valencia |www.opensips.org/events
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/wg-ims/attachments/20240125/596e9d9b/attachment.html>

From gmaruzz at gmail.com  Fri Jan 26 08:27:54 2024
From: gmaruzz at gmail.com (Giovanni Maruzzelli)
Date: Fri, 26 Jan 2024 09:27:54 +0100
Subject: [WG-IMS] Diameter Server Support
In-Reply-To: <1b99627c-41ac-e6a6-08a4-8cac3d93b7dc@opensips.org>
References: <1b99627c-41ac-e6a6-08a4-8cac3d93b7dc@opensips.org>
Message-ID: <CALXCt0pP7J4Y8ZpKcXe78+vBnnu+QdF_NxE2uo6KPRb9fTs6Ag@mail.gmail.com>

On Thu, Jan 25, 2024 at 5:08 PM Liviu Chircu <liviu at opensips.org> wrote:

> While the development is ongoing, do let us know if there is any special
> request in terms of the above that may have been missed, or maybe w.r.t.
> your interactions with the freeDiameter library in general: are you happy
> with it?  What are some goods/bads around it?
>
Liviu,
Seems perfect to me
+1

-giovanni

-- 
Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/wg-ims/attachments/20240126/6c016c2f/attachment.html>