From bogdan at opensips.org  Tue Nov 14 14:06:37 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 14 Nov 2023 16:06:37 +0200
Subject: [WG-IMS] test
Message-ID: <b592ab04-7c62-cd90-4ad5-eb4a4983f2d2@opensips.org>

test

-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com



From bogdan at opensips.org  Tue Nov 14 14:32:14 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 14 Nov 2023 16:32:14 +0200
Subject: [WG-IMS] Introducing OpenSIPS 3.5
Message-ID: <d74fa9df-689a-90a2-5e9b-ac653f31f00d@opensips.org>

Dear OpenSIPS'ers,

The 3.4 release is still fresh, but we already started to work on 
planning the next major release, the OpenSIPS 3.5. This release is to be 
*IMS focused*.

Bits and pieces of the*IMS (IP Multimedia Subsystem) *topic were part of 
the previous OpenSIPS release, but 3.5 aims to fully focus on the IMS 
part. Considering the traction and need of IMS solutions, we see the 
implementation of a consistent and large IMS support in OpenSIPS as a 
mandatory step in order to answer to the needs of the industry.

This year we introduce a new concept of an *OpenSIPS Working Group*. And 
the *IMS OpenSIPS Working Group* 
<https://www.opensips.org/Development/Working-Groups#ims-owg> is the 
first one, aiming to gather people with inters in IMS with the goal to 
draft, design and implement the IMS support in OpenSIPS.

More details on this may be found here, please read and act:

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


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/20231114/6ccb463d/attachment.html>

From bogdan at opensips.org  Wed Nov 15 07:15:14 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 15 Nov 2023 09:15:14 +0200
Subject: [WG-IMS] [OpenSIPS-Business] Introducing OpenSIPS 3.5
In-Reply-To: <CALXCt0rHoXNNQzhr8ffbY52mjBauD7zpP24o_FB0JagcokMXyg@mail.gmail.com>
References: <d74fa9df-689a-90a2-5e9b-ac653f31f00d@opensips.org>
 <CALXCt0rHoXNNQzhr8ffbY52mjBauD7zpP24o_FB0JagcokMXyg@mail.gmail.com>
Message-ID: <e9c591d8-a26e-91b0-c876-0c10320e708d@opensips.org>

Honored to have your support Giovanni :). We will allocate couple of 
days to (1) start a wiki page with the basic /starting set of 
requirements and (b) let people subscribe so we can a good pool of brains :)

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 11/14/23 4:44 PM, Giovanni Maruzzelli wrote:
> On Tue, Nov 14, 2023 at 3:34 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org <mailto:bogdan at opensips.org>> wrote:
>
>
>     This year we introduce a new concept of an *OpenSIPS Working
>     Group*. And the *IMS OpenSIPS Working Group*
>     <https://www.opensips.org/Development/Working-Groups#ims-owg> is
>     the first one, aiming to gather people with inters in IMS with the
>     goal to draft, design and implement the IMS support in OpenSIPS.
>
>     More details on this may be found here, please read and act:
>
>     https://www.opensips.org/Development/Opensips-3-5-Planning
>     <https://www.opensips.org/Development/Opensips-3-5-Planning>
>
>
>
>
> G R E A T !!
> (count me on)
>
>
>
>
>
>
> -- 
> 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/20231115/556abe0f/attachment.html>

From gmaruzz at gmail.com  Tue Nov 14 14:44:05 2023
From: gmaruzz at gmail.com (Giovanni Maruzzelli)
Date: Tue, 14 Nov 2023 15:44:05 +0100
Subject: [WG-IMS] [OpenSIPS-Business] Introducing OpenSIPS 3.5
In-Reply-To: <d74fa9df-689a-90a2-5e9b-ac653f31f00d@opensips.org>
References: <d74fa9df-689a-90a2-5e9b-ac653f31f00d@opensips.org>
Message-ID: <CALXCt0rHoXNNQzhr8ffbY52mjBauD7zpP24o_FB0JagcokMXyg@mail.gmail.com>

On Tue, Nov 14, 2023 at 3:34 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

>
> This year we introduce a new concept of an *OpenSIPS Working Group*. And
> the *IMS OpenSIPS Working Group*
> <https://www.opensips.org/Development/Working-Groups#ims-owg> is the
> first one, aiming to gather people with inters in IMS with the goal to
> draft, design and implement the IMS support in OpenSIPS.
>
> More details on this may be found here, please read and act:
>
>     https://www.opensips.org/Development/Opensips-3-5-Planning
>
>


G R E A T !!
(count me on)






-- 
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/20231114/164081af/attachment.html>

From bogdan at opensips.org  Tue Nov 28 12:32:54 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 28 Nov 2023 14:32:54 +0200
Subject: [WG-IMS] IMS OpenSIPS Working Group - Kickoff
Message-ID: <b4a81d6b-7321-4e26-90d0-7c6572962b60@opensips.org>

Hi all,

As mentioned in the 3.5 planning 
<https://www.opensips.org/Development/Opensips-3-5-Planning>, this 
release is IMS focused. And to deal with the complexity of this task, we 
have this new tool, the IMS OpenSIPS Working Group. 
<https://github.com/OpenSIPS/opensips/wiki/IMS-OpenSIPS-Working-Group>

And now it is the time to start its work 🙂. As starting point, we put 
together the Roadmap of the group and also some initial Technical 
Requirements (as guidance). All this info is available on the group WIKI 
page <https://github.com/OpenSIPS/opensips/wiki/IMS-OpenSIPS-Working-Group>.

The main discussion channel is the group's mailing list 
<http://lists.opensips.org/cgi-bin/mailman/listinfo/wg-ims>. So, as a 
fist step, if interested to contribute to the IMS work, please subscribe 
to the list.

An now we have the official kick-off of the group by starting there the 
discussion on the *IMS scope in OpenSIPS*, so we need all hands on deck. 
Again, please subscribe to the mailing list; also check the list's 
archive to catch up with ongoing threads.

See you on the WG-IMS list ;)

-- 
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/20231128/e376e0e1/attachment.html>

From bogdan at opensips.org  Tue Nov 28 13:02:18 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Tue, 28 Nov 2023 15:02:18 +0200
Subject: [WG-IMS] Scope of IMS in OpenSIPS - RFC
Message-ID: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>

Hi all,

(disclaimer : cross lists posting is not a good practice - we will do 
this only to catch the attention and get momentum with this initial topic)

As a first step here, is to work out the scope of the IMS implementation 
in OpenSIPS. IMS is a vast concept, with SIP and non-SIP components, and 
we want to understand and agree on which components of IMS may be 
subject of work from the OpenSIPS perspective. For example, we do 
consider the CSCF as a must here, but we may explore the HSS, AS, MGW or 
other components.

 From the OpenSIPS perspective, we look for IMS components which are SIP 
related. At least as a starting point. So, the first obvious candidate 
is the *Call Session Control Function (CSCF)*. And here we need to look 
into and address the specific functionalities of each sub-component:
     * P-CSCF
     * I-CSCF
     * S-CSCF

Again, these are the pretty obvious components, still may look into and 
evaluate (if of an interest of the OpenSIPS IMS implementation) areas as:
     * HSS (from interconnection perspective)
     * MGCF / MGW  (from interconnection perspective)
     * SIP AS
     * others ?

Any feedback (with explanations and arguments) about what we should 
consider for our IMS implementation is more the welcome. I set here just 
a simple starting point, with no limitations or so. Feel free to 
contribute to the topic


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/20231128/ca83e294/attachment.html>

From gmaruzz at gmail.com  Wed Nov 29 09:11:51 2023
From: gmaruzz at gmail.com (Giovanni Maruzzelli)
Date: Wed, 29 Nov 2023 10:11:51 +0100
Subject: [WG-IMS] Scope of IMS in OpenSIPS - RFC
In-Reply-To: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>
References: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>
Message-ID: <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>

First of all:
CONGRATULATIONS to the OpenSIPS community !!!
(I believe this is the first step of a long and satisfying journey)

On the topic:
in addition to the CSCF component, I would like to see efforts on the AS
(Application Server) component of the IMS infrastructure.

The AS is probably way the simplest of it all, it will probably require the
least modifications/additions to OpenSIPS.

But I would say AS will be crucial to a lot of people/use cases.

While for sure there will be a lot of cases for our community to build the
voice/video complete IMS infrastructure on top of private 5G networks in
enterprises and public administrations, I see as very much relevant also
the use case of building infrastructure to provide additional third party
services to big carriers, and to big carriers partners.

Also, AS is the correct and manageable way to provide additional services
even if you build the core IMS infrastructure.

About HSS: this is the sancta sanctorum of a carrier/provider
Apart from the venerable fraunhofer java implementation, now we can count
on the flexible java implementation in
https://github.com/nickvsnetworking/pyhss with a lot of features, good
performances, and actually built for production.

I would say better we concentrate on accessing the various different
protocols of HSS (diameter/http2) from the various components (each
component in IMS access HSS with a different interface with
different vocabularies and actions.

MGCF/MGW, if needed, will be a natural extension of our CSCF/AS
architecture.

Just my two cents, to keep the ball rolling,

Congratulation again,

-giovanni


On Tue, Nov 28, 2023 at 2:02 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi all,
>
> (disclaimer : cross lists posting is not a good practice - we will do this
> only to catch the attention and get momentum with this initial topic)
>
> As a first step here, is to work out the scope of the IMS implementation
> in OpenSIPS. IMS is a vast concept, with SIP and non-SIP components, and we
> want to understand and agree on which components of IMS may be subject of
> work from the OpenSIPS perspective. For example, we do consider the CSCF as
> a must here, but we may explore the HSS, AS, MGW or other components.
>
> From the OpenSIPS perspective, we look for IMS components which are SIP
> related. At least as a starting point. So, the first obvious candidate is
> the *Call Session Control Function (CSCF)*. And here we need to look into
> and address the specific functionalities of each sub-component:
>     * P-CSCF
>     * I-CSCF
>     * S-CSCF
>
> Again, these are the pretty obvious components, still may look into and
> evaluate (if of an interest of the OpenSIPS IMS implementation) areas as:
>     * HSS (from interconnection perspective)
>     * MGCF / MGW  (from interconnection perspective)
>     * SIP AS
>     * others ?
>
> Any feedback (with explanations and arguments) about what we should
> consider for our IMS implementation is more the welcome. I set here just a
> simple starting point, with no limitations or so. Feel free to contribute
> to the topic
>
>
> 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
>


-- 
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/20231129/ffc966b5/attachment.html>

From gmaruzz at gmail.com  Wed Nov 29 09:26:07 2023
From: gmaruzz at gmail.com (Giovanni Maruzzelli)
Date: Wed, 29 Nov 2023 10:26:07 +0100
Subject: [WG-IMS] Scope of IMS in OpenSIPS - RFC
In-Reply-To: <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>
References: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>
 <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>
Message-ID: <CALXCt0r-2SW02bjEKF4kA+WVJGWXC1QJ6OQ_ZriuG0Pt51xL6g@mail.gmail.com>

On Wed, Nov 29, 2023 at 10:11 AM Giovanni Maruzzelli <gmaruzz at gmail.com>
wrote:

> About HSS: this is the sancta sanctorum of a carrier/provider
> Apart from the venerable fraunhofer java implementation, now we can count
> on the flexible java implementation in
> https://github.com/nickvsnetworking/pyhss with a lot of features, good
> performances, and actually built for production.
>
>
Errata: PyHSS is obviously written in Python (not in Java at all), and very
much open to integrating features/etc on GitHub

-- 
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/20231129/4be96514/attachment-0001.html>

From bogdan at opensips.org  Wed Nov 29 15:38:13 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 29 Nov 2023 17:38:13 +0200
Subject: [WG-IMS] Scope of IMS in OpenSIPS - RFC
In-Reply-To: <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>
References: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>
 <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>
Message-ID: <0d7d8cd9-8070-43af-babf-d5a83dc002cb@opensips.org>

Hi Giovanni,

Thanks for the feedback here, a valuable one as usual :).

On the HSS, what you are saying aligns with the my own thoughts - that 
its functioning logic is somehow outside the our scope here, but we need 
to pay attention to the interfacing (DIAMETER or HTTP2.0).

Now, on the AS side - as I understand, it holds whatever custom logic 
the operator may have in routing and proving services (included VAS's). 
So to say, I see it as a highly programmable component. And if so, what 
we need to provide here is probably a very high level interface / API to 
allow call manipulation in a very abstract way... :-/ ??

Best Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 29.11.2023 11:11, Giovanni Maruzzelli wrote:
> First of all:
> CONGRATULATIONS to the OpenSIPS community !!!
> (I believe this is the first step of a long and satisfying journey)
>
> On the topic:
> in addition to the CSCF component, I would like to see efforts on the 
> AS (Application Server) component of the IMS infrastructure.
>
> The AS is probably way the simplest of it all, it will probably 
> require the least modifications/additions to OpenSIPS.
>
> But I would say AS will be crucial to a lot of people/use cases.
>
> While for sure there will be a lot of cases for our community to build 
> the voice/video complete IMS infrastructure on top of private 5G 
> networks in enterprises and public administrations, I see as very much 
> relevant also the use case of building infrastructure to provide 
> additional third party services to big carriers, and to big carriers 
> partners.
>
> Also, AS is the correct and manageable way to provide additional 
> services even if you build the core IMS infrastructure.
>
> About HSS: this is the sancta sanctorum of a carrier/provider
> Apart from the venerable fraunhofer java implementation, now we can 
> count on the flexible java implementation in 
> https://github.com/nickvsnetworking/pyhss with a lot of features, good 
> performances, and actually built for production.
>
> I would say better we concentrate on accessing the various different 
> protocols of HSS (diameter/http2) from the various components (each 
> component in IMS access HSS with a different interface with 
> different vocabularies and actions.
>
> MGCF/MGW, if needed, will be a natural extension of our CSCF/AS 
> architecture.
>
> Just my two cents, to keep the ball rolling,
>
> Congratulation again,
>
> -giovanni
>
>
> On Tue, Nov 28, 2023 at 2:02 PM Bogdan-Andrei Iancu 
> <bogdan at opensips.org> wrote:
>
>     Hi all,
>
>     (disclaimer : cross lists posting is not a good practice - we will
>     do this only to catch the attention and get momentum with this
>     initial topic)
>
>     As a first step here, is to work out the scope of the IMS
>     implementation in OpenSIPS. IMS is a vast concept, with SIP and
>     non-SIP components, and we want to understand and agree on which
>     components of IMS may be subject of work from the OpenSIPS
>     perspective. For example, we do consider the CSCF as a must here,
>     but we may explore the HSS, AS, MGW or other components.
>
>     From the OpenSIPS perspective, we look for IMS components which
>     are SIP related. At least as a starting point. So, the first
>     obvious candidate is the *Call Session Control Function (CSCF)*.
>     And here we need to look into and address the specific
>     functionalities of each sub-component:
>         * P-CSCF
>         * I-CSCF
>         * S-CSCF
>
>     Again, these are the pretty obvious components, still may look
>     into and evaluate (if of an interest of the OpenSIPS IMS
>     implementation) areas as:
>         * HSS (from interconnection perspective)
>         * MGCF / MGW  (from interconnection perspective)
>         * SIP AS
>         * others ?
>
>     Any feedback (with explanations and arguments) about what we
>     should consider for our IMS implementation is more the welcome. I
>     set here just a simple starting point, with no limitations or so.
>     Feel free to contribute to the topic
>
>
>     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
>
>
>
> -- 
> 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/20231129/49c23caa/attachment.html>

From Johan at democon.be  Wed Nov 29 16:07:36 2023
From: Johan at democon.be (Johan De Clercq)
Date: Wed, 29 Nov 2023 17:07:36 +0100
Subject: [WG-IMS] Scope of IMS in OpenSIPS - RFC
In-Reply-To: <0d7d8cd9-8070-43af-babf-d5a83dc002cb@opensips.org>
References: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>
 <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>
 <0d7d8cd9-8070-43af-babf-d5a83dc002cb@opensips.org>
Message-ID: <CAEVWGm_9rUssQam6yKqqdYx1YN8TftMHWQNCiK=VDswbnnXxRA@mail.gmail.com>

In addition, the IMS should be able to handle 4G and 5G calls.
In my opinion, we should no longer about 2 and 3 G as they are being phased
out everywhere.

wkr,

Op wo 29 nov 2023 om 16:39 schreef Bogdan-Andrei Iancu <bogdan at opensips.org
>:

> Hi Giovanni,
>
> Thanks for the feedback here, a valuable one as usual :).
>
> On the HSS, what you are saying aligns with the my own thoughts - that its
> functioning logic is somehow outside the our scope here, but we need to pay
> attention to the interfacing (DIAMETER or HTTP2.0).
>
> Now, on the AS side - as I understand, it holds whatever custom logic the
> operator may have in routing and proving services (included VAS's). So to
> say, I see it as a highly programmable component. And if so, what we need
> to provide here is probably a very high level interface / API to allow call
> manipulation in a very abstract way... :-/ ??
>
> Best Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 29.11.2023 11:11, Giovanni Maruzzelli wrote:
>
> First of all:
> CONGRATULATIONS to the OpenSIPS community !!!
> (I believe this is the first step of a long and satisfying journey)
>
> On the topic:
> in addition to the CSCF component, I would like to see efforts on the AS
> (Application Server) component of the IMS infrastructure.
>
> The AS is probably way the simplest of it all, it will probably require
> the least modifications/additions to OpenSIPS.
>
> But I would say AS will be crucial to a lot of people/use cases.
>
> While for sure there will be a lot of cases for our community to build the
> voice/video complete IMS infrastructure on top of private 5G networks in
> enterprises and public administrations, I see as very much relevant also
> the use case of building infrastructure to provide additional third party
> services to big carriers, and to big carriers partners.
>
> Also, AS is the correct and manageable way to provide additional services
> even if you build the core IMS infrastructure.
>
> About HSS: this is the sancta sanctorum of a carrier/provider
> Apart from the venerable fraunhofer java implementation, now we can count
> on the flexible java implementation in
> https://github.com/nickvsnetworking/pyhss with a lot of features, good
> performances, and actually built for production.
>
> I would say better we concentrate on accessing the various different
> protocols of HSS (diameter/http2) from the various components (each
> component in IMS access HSS with a different interface with
> different vocabularies and actions.
>
> MGCF/MGW, if needed, will be a natural extension of our CSCF/AS
> architecture.
>
> Just my two cents, to keep the ball rolling,
>
> Congratulation again,
>
> -giovanni
>
>
> On Tue, Nov 28, 2023 at 2:02 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi all,
>>
>> (disclaimer : cross lists posting is not a good practice - we will do
>> this only to catch the attention and get momentum with this initial topic)
>>
>> As a first step here, is to work out the scope of the IMS implementation
>> in OpenSIPS. IMS is a vast concept, with SIP and non-SIP components, and we
>> want to understand and agree on which components of IMS may be subject of
>> work from the OpenSIPS perspective. For example, we do consider the CSCF as
>> a must here, but we may explore the HSS, AS, MGW or other components.
>>
>> From the OpenSIPS perspective, we look for IMS components which are SIP
>> related. At least as a starting point. So, the first obvious candidate is
>> the *Call Session Control Function (CSCF)*. And here we need to look
>> into and address the specific functionalities of each sub-component:
>>     * P-CSCF
>>     * I-CSCF
>>     * S-CSCF
>>
>> Again, these are the pretty obvious components, still may look into and
>> evaluate (if of an interest of the OpenSIPS IMS implementation) areas as:
>>     * HSS (from interconnection perspective)
>>     * MGCF / MGW  (from interconnection perspective)
>>     * SIP AS
>>     * others ?
>>
>> Any feedback (with explanations and arguments) about what we should
>> consider for our IMS implementation is more the welcome. I set here just a
>> simple starting point, with no limitations or so. Feel free to contribute
>> to the topic
>>
>>
>> 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
>>
>
>
> --
> Sincerely,
>
> Giovanni Maruzzelli
> OpenTelecom.IT
> cell: +39 347 266 56 18
>
>
> _______________________________________________
> 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/20231129/c7ec3d0f/attachment-0001.html>

From bogdan at opensips.org  Wed Nov 29 17:25:25 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Wed, 29 Nov 2023 19:25:25 +0200
Subject: [WG-IMS] Scope of IMS in OpenSIPS - RFC
In-Reply-To: <CAEVWGm_9rUssQam6yKqqdYx1YN8TftMHWQNCiK=VDswbnnXxRA@mail.gmail.com>
References: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>
 <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>
 <0d7d8cd9-8070-43af-babf-d5a83dc002cb@opensips.org>
 <CAEVWGm_9rUssQam6yKqqdYx1YN8TftMHWQNCiK=VDswbnnXxRA@mail.gmail.com>
Message-ID: <fd0064f2-e498-4505-babc-64c20f3eca95@opensips.org>

Hi Johan,

The lowest point we should address in the whole IMS arch is the P-CSCF, 
so we are agnostic to the actual transport layer below us (like the xG 
stuff). Or am I saying here something wrong and there are some 
implications to the upper layers ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 29.11.2023 18:07, Johan De Clercq wrote:
> In addition, the IMS should be able to handle 4G and 5G calls.
> In my opinion, we should no longer about 2 and 3 G as they are being 
> phased out everywhere.
>
> wkr,
>
> Op wo 29 nov 2023 om 16:39 schreef Bogdan-Andrei Iancu 
> <bogdan at opensips.org>:
>
>     Hi Giovanni,
>
>     Thanks for the feedback here, a valuable one as usual :).
>
>     On the HSS, what you are saying aligns with the my own thoughts -
>     that its functioning logic is somehow outside the our scope here,
>     but we need to pay attention to the interfacing (DIAMETER or HTTP2.0).
>
>     Now, on the AS side - as I understand, it holds whatever custom
>     logic the operator may have in routing and proving services
>     (included VAS's). So to say, I see it as a highly programmable
>     component. And if so, what we need to provide here is probably a
>     very high level interface / API to allow call manipulation in a
>     very abstract way... :-/ ??
>
>     Best Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 29.11.2023 11:11, Giovanni Maruzzelli wrote:
>>     First of all:
>>     CONGRATULATIONS to the OpenSIPS community !!!
>>     (I believe this is the first step of a long and satisfying journey)
>>
>>     On the topic:
>>     in addition to the CSCF component, I would like to see efforts on
>>     the AS (Application Server) component of the IMS infrastructure.
>>
>>     The AS is probably way the simplest of it all, it will probably
>>     require the least modifications/additions to OpenSIPS.
>>
>>     But I would say AS will be crucial to a lot of people/use cases.
>>
>>     While for sure there will be a lot of cases for our community to
>>     build the voice/video complete IMS infrastructure on top of
>>     private 5G networks in enterprises and public administrations, I
>>     see as very much relevant also the use case of building
>>     infrastructure to provide additional third party services to big
>>     carriers, and to big carriers partners.
>>
>>     Also, AS is the correct and manageable way to provide additional
>>     services even if you build the core IMS infrastructure.
>>
>>     About HSS: this is the sancta sanctorum of a carrier/provider
>>     Apart from the venerable fraunhofer java implementation, now we
>>     can count on the flexible java implementation in
>>     https://github.com/nickvsnetworking/pyhss with a lot of features,
>>     good performances, and actually built for production.
>>
>>     I would say better we concentrate on accessing the various
>>     different protocols of HSS (diameter/http2) from the various
>>     components (each component in IMS access HSS with a different
>>     interface with different vocabularies and actions.
>>
>>     MGCF/MGW, if needed, will be a natural extension of our CSCF/AS
>>     architecture.
>>
>>     Just my two cents, to keep the ball rolling,
>>
>>     Congratulation again,
>>
>>     -giovanni
>>
>>
>>     On Tue, Nov 28, 2023 at 2:02 PM Bogdan-Andrei Iancu
>>     <bogdan at opensips.org> wrote:
>>
>>         Hi all,
>>
>>         (disclaimer : cross lists posting is not a good practice - we
>>         will do this only to catch the attention and get momentum
>>         with this initial topic)
>>
>>         As a first step here, is to work out the scope of the IMS
>>         implementation in OpenSIPS. IMS is a vast concept, with SIP
>>         and non-SIP components, and we want to understand and agree
>>         on which components of IMS may be subject of work from the
>>         OpenSIPS perspective. For example, we do consider the CSCF as
>>         a must here, but we may explore the HSS, AS, MGW or other
>>         components.
>>
>>         From the OpenSIPS perspective, we look for IMS components
>>         which are SIP related. At least as a starting point. So, the
>>         first obvious candidate is the *Call Session Control Function
>>         (CSCF)*. And here we need to look into and address the
>>         specific functionalities of each sub-component:
>>             * P-CSCF
>>             * I-CSCF
>>             * S-CSCF
>>
>>         Again, these are the pretty obvious components, still may
>>         look into and evaluate (if of an interest of the OpenSIPS IMS
>>         implementation) areas as:
>>             * HSS (from interconnection perspective)
>>             * MGCF / MGW (from interconnection perspective)
>>             * SIP AS
>>             * others ?
>>
>>         Any feedback (with explanations and arguments) about what we
>>         should consider for our IMS implementation is more the
>>         welcome. I set here just a simple starting point, with no
>>         limitations or so. Feel free to contribute to the topic
>>
>>
>>         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
>>
>>
>>
>>     -- 
>>     Sincerely,
>>
>>     Giovanni Maruzzelli
>>     OpenTelecom.IT
>>     cell: +39 347 266 56 18
>>
>
>     _______________________________________________
>     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/20231129/704b3980/attachment.html>

From gmaruzz at gmail.com  Wed Nov 29 17:45:58 2023
From: gmaruzz at gmail.com (Giovanni Maruzzelli)
Date: Wed, 29 Nov 2023 18:45:58 +0100
Subject: [WG-IMS] Scope of IMS in OpenSIPS - RFC
In-Reply-To: <fd0064f2-e498-4505-babc-64c20f3eca95@opensips.org>
References: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>
 <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>
 <0d7d8cd9-8070-43af-babf-d5a83dc002cb@opensips.org>
 <CAEVWGm_9rUssQam6yKqqdYx1YN8TftMHWQNCiK=VDswbnnXxRA@mail.gmail.com>
 <fd0064f2-e498-4505-babc-64c20f3eca95@opensips.org>
Message-ID: <CALXCt0qEs4Vumq69muKeukn9h1P1qy7h4HT7jSuhbTQ7BH+2Jg@mail.gmail.com>

Yes, actually there is a difference between 5g and 4g infrastructure, that
actually often involve different interfacing from IMS to it, particularly
pcscf and icscf, eg: the way they interact with hss and pcf/pcrf.
Problem is that 4g infrastructure is different from 5g. When they implement
4g+5g, they implement actually both (so, no problem)

4g+5g is called NSA (not stand alone)

A pure 5g is SA (stand alone) and offer different interfaces from the ones
provided by 4g.

In NSA you (IMS) can behave like it's pure 4g (you use 4g interfaces to do
all things, even for the 5g part)

In SA not at all, you must interface to 5g

The main difference for what ims is concerned is pcf vs pcrf

Let's note that most private networks (enterprise, etc) will be SA

Most carriers will obviously be NSA



answered from mobile, please pardon terseness and typos,
-giovanni

On Wed, Nov 29, 2023, 18:25 Bogdan-Andrei Iancu <bogdan at opensips.org> wrote:

> Hi Johan,
>
> The lowest point we should address in the whole IMS arch is the P-CSCF, so
> we are agnostic to the actual transport layer below us (like the xG stuff).
> Or am I saying here something wrong and there are some implications to the
> upper layers ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
>   https://www.siphub.com
>
> On 29.11.2023 18:07, Johan De Clercq wrote:
>
> In addition, the IMS should be able to handle 4G and 5G calls.
> In my opinion, we should no longer about 2 and 3 G as they are being
> phased out everywhere.
>
> wkr,
>
> Op wo 29 nov 2023 om 16:39 schreef Bogdan-Andrei Iancu <
> bogdan at opensips.org>:
>
>> Hi Giovanni,
>>
>> Thanks for the feedback here, a valuable one as usual :).
>>
>> On the HSS, what you are saying aligns with the my own thoughts - that
>> its functioning logic is somehow outside the our scope here, but we need to
>> pay attention to the interfacing (DIAMETER or HTTP2.0).
>>
>> Now, on the AS side - as I understand, it holds whatever custom logic the
>> operator may have in routing and proving services (included VAS's). So to
>> say, I see it as a highly programmable component. And if so, what we need
>> to provide here is probably a very high level interface / API to allow call
>> manipulation in a very abstract way... :-/ ??
>>
>> Best Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>>   https://www.siphub.com
>>
>> On 29.11.2023 11:11, Giovanni Maruzzelli wrote:
>>
>> First of all:
>> CONGRATULATIONS to the OpenSIPS community !!!
>> (I believe this is the first step of a long and satisfying journey)
>>
>> On the topic:
>> in addition to the CSCF component, I would like to see efforts on the AS
>> (Application Server) component of the IMS infrastructure.
>>
>> The AS is probably way the simplest of it all, it will probably require
>> the least modifications/additions to OpenSIPS.
>>
>> But I would say AS will be crucial to a lot of people/use cases.
>>
>> While for sure there will be a lot of cases for our community to build
>> the voice/video complete IMS infrastructure on top of private 5G networks
>> in enterprises and public administrations, I see as very much relevant also
>> the use case of building infrastructure to provide additional third party
>> services to big carriers, and to big carriers partners.
>>
>> Also, AS is the correct and manageable way to provide additional services
>> even if you build the core IMS infrastructure.
>>
>> About HSS: this is the sancta sanctorum of a carrier/provider
>> Apart from the venerable fraunhofer java implementation, now we can count
>> on the flexible java implementation in
>> https://github.com/nickvsnetworking/pyhss with a lot of features, good
>> performances, and actually built for production.
>>
>> I would say better we concentrate on accessing the various different
>> protocols of HSS (diameter/http2) from the various components (each
>> component in IMS access HSS with a different interface with
>> different vocabularies and actions.
>>
>> MGCF/MGW, if needed, will be a natural extension of our CSCF/AS
>> architecture.
>>
>> Just my two cents, to keep the ball rolling,
>>
>> Congratulation again,
>>
>> -giovanni
>>
>>
>> On Tue, Nov 28, 2023 at 2:02 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
>> wrote:
>>
>>> Hi all,
>>>
>>> (disclaimer : cross lists posting is not a good practice - we will do
>>> this only to catch the attention and get momentum with this initial topic)
>>>
>>> As a first step here, is to work out the scope of the IMS implementation
>>> in OpenSIPS. IMS is a vast concept, with SIP and non-SIP components, and we
>>> want to understand and agree on which components of IMS may be subject of
>>> work from the OpenSIPS perspective. For example, we do consider the CSCF as
>>> a must here, but we may explore the HSS, AS, MGW or other components.
>>>
>>> From the OpenSIPS perspective, we look for IMS components which are SIP
>>> related. At least as a starting point. So, the first obvious candidate is
>>> the *Call Session Control Function (CSCF)*. And here we need to look
>>> into and address the specific functionalities of each sub-component:
>>>     * P-CSCF
>>>     * I-CSCF
>>>     * S-CSCF
>>>
>>> Again, these are the pretty obvious components, still may look into and
>>> evaluate (if of an interest of the OpenSIPS IMS implementation) areas as:
>>>     * HSS (from interconnection perspective)
>>>     * MGCF / MGW  (from interconnection perspective)
>>>     * SIP AS
>>>     * others ?
>>>
>>> Any feedback (with explanations and arguments) about what we should
>>> consider for our IMS implementation is more the welcome. I set here just a
>>> simple starting point, with no limitations or so. Feel free to contribute
>>> to the topic
>>>
>>>
>>> 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
>>>
>>
>>
>> --
>> Sincerely,
>>
>> Giovanni Maruzzelli
>> OpenTelecom.IT
>> cell: +39 347 266 56 18
>>
>>
>> _______________________________________________
>> 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/20231129/9b1c7a32/attachment-0001.html>

From johan at democon.be  Wed Nov 29 17:52:48 2023
From: johan at democon.be (Johan De Clercq)
Date: Wed, 29 Nov 2023 17:52:48 +0000
Subject: [WG-IMS] Scope of IMS in OpenSIPS - RFC
In-Reply-To: <CALXCt0qEs4Vumq69muKeukn9h1P1qy7h4HT7jSuhbTQ7BH+2Jg@mail.gmail.com>
References: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>
 <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>
 <0d7d8cd9-8070-43af-babf-d5a83dc002cb@opensips.org>
 <CAEVWGm_9rUssQam6yKqqdYx1YN8TftMHWQNCiK=VDswbnnXxRA@mail.gmail.com>
 <fd0064f2-e498-4505-babc-64c20f3eca95@opensips.org>
 <CALXCt0qEs4Vumq69muKeukn9h1P1qy7h4HT7jSuhbTQ7BH+2Jg@mail.gmail.com>
Message-ID: <AS4P194MB17661ED944C57A4D14033163A783A@AS4P194MB1766.EURP194.PROD.OUTLOOK.COM>

I agree Giovanni. If the decision is made to go nsa (even not in first release), that should be taken into account. That’s why we need to scope.

Verzonden vanuit Outlook voor iOS<https://aka.ms/o0ukef>
________________________________
Van: Giovanni Maruzzelli <gmaruzz at gmail.com>
Verzonden: Wednesday, November 29, 2023 6:45:58 PM
Aan: Bogdan-Andrei Iancu <bogdan at opensips.org>
CC: Johan De Clercq <Johan at democon.be>; Giovanni Maruzzelli <gmaruzz at opentelecom.it>; wg-ims at lists.opensips.org <wg-ims at lists.opensips.org>; OpenSIPS users mailling list <users at lists.opensips.org>
Onderwerp: Re: [WG-IMS] Scope of IMS in OpenSIPS - RFC

Yes, actually there is a difference between 5g and 4g infrastructure, that actually often involve different interfacing from IMS to it, particularly pcscf and icscf, eg: the way they interact with hss and pcf/pcrf.
Problem is that 4g infrastructure is different from 5g. When they implement 4g+5g, they implement actually both (so, no problem)

4g+5g is called NSA (not stand alone)

A pure 5g is SA (stand alone) and offer different interfaces from the ones provided by 4g.

In NSA you (IMS) can behave like it's pure 4g (you use 4g interfaces to do all things, even for the 5g part)

In SA not at all, you must interface to 5g

The main difference for what ims is concerned is pcf vs pcrf

Let's note that most private networks (enterprise, etc) will be SA

Most carriers will obviously be NSA



answered from mobile, please pardon terseness and typos,
-giovanni

On Wed, Nov 29, 2023, 18:25 Bogdan-Andrei Iancu <bogdan at opensips.org<mailto:bogdan at opensips.org>> wrote:
Hi Johan,

The lowest point we should address in the whole IMS arch is the P-CSCF, so we are agnostic to the actual transport layer below us (like the xG stuff). Or am I saying here something wrong and there are some implications to the upper layers ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
  https://www.siphub.com

On 29.11.2023 18:07, Johan De Clercq wrote:
In addition, the IMS should be able to handle 4G and 5G calls.
In my opinion, we should no longer about 2 and 3 G as they are being phased out everywhere.

wkr,

Op wo 29 nov 2023 om 16:39 schreef Bogdan-Andrei Iancu <bogdan at opensips.org<mailto:bogdan at opensips.org>>:
Hi Giovanni,

Thanks for the feedback here, a valuable one as usual :).

On the HSS, what you are saying aligns with the my own thoughts - that its functioning logic is somehow outside the our scope here, but we need to pay attention to the interfacing (DIAMETER or HTTP2.0).

Now, on the AS side - as I understand, it holds whatever custom logic the operator may have in routing and proving services (included VAS's). So to say, I see it as a highly programmable component. And if so, what we need to provide here is probably a very high level interface / API to allow call manipulation in a very abstract way... :-/ ??

Best Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
  https://www.siphub.com

On 29.11.2023 11:11, Giovanni Maruzzelli wrote:
First of all:
CONGRATULATIONS to the OpenSIPS community !!!
(I believe this is the first step of a long and satisfying journey)

On the topic:
in addition to the CSCF component, I would like to see efforts on the AS (Application Server) component of the IMS infrastructure.

The AS is probably way the simplest of it all, it will probably require the least modifications/additions to OpenSIPS.

But I would say AS will be crucial to a lot of people/use cases.

While for sure there will be a lot of cases for our community to build the voice/video complete IMS infrastructure on top of private 5G networks in enterprises and public administrations, I see as very much relevant also the use case of building infrastructure to provide additional third party services to big carriers, and to big carriers partners.

Also, AS is the correct and manageable way to provide additional services even if you build the core IMS infrastructure.

About HSS: this is the sancta sanctorum of a carrier/provider
Apart from the venerable fraunhofer java implementation, now we can count on the flexible java implementation in https://github.com/nickvsnetworking/pyhss with a lot of features, good performances, and actually built for production.

I would say better we concentrate on accessing the various different protocols of HSS (diameter/http2) from the various components (each component in IMS access HSS with a different interface with different vocabularies and actions.

MGCF/MGW, if needed, will be a natural extension of our CSCF/AS architecture.

Just my two cents, to keep the ball rolling,

Congratulation again,

-giovanni


On Tue, Nov 28, 2023 at 2:02 PM Bogdan-Andrei Iancu <bogdan at opensips.org<mailto:bogdan at opensips.org>> wrote:
Hi all,

(disclaimer : cross lists posting is not a good practice - we will do this only to catch the attention and get momentum with this initial topic)

As a first step here, is to work out the scope of the IMS implementation in OpenSIPS. IMS is a vast concept, with SIP and non-SIP components, and we want to understand and agree on which components of IMS may be subject of work from the OpenSIPS perspective. For example, we do consider the CSCF as a must here, but we may explore the HSS, AS, MGW or other components.

From the OpenSIPS perspective, we look for IMS components which are SIP related. At least as a starting point. So, the first obvious candidate is the Call Session Control Function (CSCF). And here we need to look into and address the specific functionalities of each sub-component:
    * P-CSCF
    * I-CSCF
    * S-CSCF

Again, these are the pretty obvious components, still may look into and evaluate (if of an interest of the OpenSIPS IMS implementation) areas as:
    * HSS (from interconnection perspective)
    * MGCF / MGW  (from interconnection perspective)
    * SIP AS
    * others ?

Any feedback (with explanations and arguments) about what we should consider for our IMS implementation is more the welcome. I set here just a simple starting point, with no limitations or so. Feel free to contribute to the topic


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<mailto: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


_______________________________________________
Wg-ims mailing list
Wg-ims at lists.opensips.org<mailto: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/20231129/ee1705ba/attachment-0001.html>

From bogdan at opensips.org  Thu Nov 30 09:01:25 2023
From: bogdan at opensips.org (Bogdan-Andrei Iancu)
Date: Thu, 30 Nov 2023 11:01:25 +0200
Subject: [WG-IMS] Scope of IMS in OpenSIPS - RFC
In-Reply-To: <CALXCt0qEs4Vumq69muKeukn9h1P1qy7h4HT7jSuhbTQ7BH+2Jg@mail.gmail.com>
References: <e97a984f-1b9b-4c46-b4a0-94ff1a7a71bc@opensips.org>
 <CALXCt0pfHiKhAHnP7a9XewpzTpfb9PjnD8O0T3_TA7rfCJyLBA@mail.gmail.com>
 <0d7d8cd9-8070-43af-babf-d5a83dc002cb@opensips.org>
 <CAEVWGm_9rUssQam6yKqqdYx1YN8TftMHWQNCiK=VDswbnnXxRA@mail.gmail.com>
 <fd0064f2-e498-4505-babc-64c20f3eca95@opensips.org>
 <CALXCt0qEs4Vumq69muKeukn9h1P1qy7h4HT7jSuhbTQ7BH+2Jg@mail.gmail.com>
Message-ID: <ef9f9a66-0dbc-4b13-adb3-85ad481a7dab@opensips.org>

It looks I have to do more reading in this direction...some homework :). 
But yes, it seems a good point to be taken into consideration.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 29.11.2023 19:45, Giovanni Maruzzelli wrote:
> Yes, actually there is a difference between 5g and 4g infrastructure, 
> that actually often involve different interfacing from IMS to it, 
> particularly pcscf and icscf, eg: the way they interact with hss and 
> pcf/pcrf.
> Problem is that 4g infrastructure is different from 5g. When they 
> implement 4g+5g, they implement actually both (so, no problem)
>
> 4g+5g is called NSA (not stand alone)
>
> A pure 5g is SA (stand alone) and offer different interfaces from the 
> ones provided by 4g.
>
> In NSA you (IMS) can behave like it's pure 4g (you use 4g interfaces 
> to do all things, even for the 5g part)
>
> In SA not at all, you must interface to 5g
>
> The main difference for what ims is concerned is pcf vs pcrf
>
> Let's note that most private networks (enterprise, etc) will be SA
>
> Most carriers will obviously be NSA
>
>
>
> answered from mobile, please pardon terseness and typos,
> -giovanni
>
> On Wed, Nov 29, 2023, 18:25 Bogdan-Andrei Iancu <bogdan at opensips.org> 
> wrote:
>
>     Hi Johan,
>
>     The lowest point we should address in the whole IMS arch is the
>     P-CSCF, so we are agnostic to the actual transport layer below us
>     (like the xG stuff). Or am I saying here something wrong and there
>     are some implications to the upper layers ?
>
>     Regards,
>
>     Bogdan-Andrei Iancu
>
>     OpenSIPS Founder and Developer
>        https://www.opensips-solutions.com
>        https://www.siphub.com
>
>     On 29.11.2023 18:07, Johan De Clercq wrote:
>>     In addition, the IMS should be able to handle 4G and 5G calls.
>>     In my opinion, we should no longer about 2 and 3 G as they are
>>     being phased out everywhere.
>>
>>     wkr,
>>
>>     Op wo 29 nov 2023 om 16:39 schreef Bogdan-Andrei Iancu
>>     <bogdan at opensips.org>:
>>
>>         Hi Giovanni,
>>
>>         Thanks for the feedback here, a valuable one as usual :).
>>
>>         On the HSS, what you are saying aligns with the my own
>>         thoughts - that its functioning logic is somehow outside the
>>         our scope here, but we need to pay attention to the
>>         interfacing (DIAMETER or HTTP2.0).
>>
>>         Now, on the AS side - as I understand, it holds whatever
>>         custom logic the operator may have in routing and proving
>>         services (included VAS's). So to say, I see it as a highly
>>         programmable component. And if so, what we need to provide
>>         here is probably a very high level interface / API to allow
>>         call manipulation in a very abstract way... :-/ ??
>>
>>         Best Regards,
>>
>>         Bogdan-Andrei Iancu
>>
>>         OpenSIPS Founder and Developer
>>            https://www.opensips-solutions.com
>>            https://www.siphub.com
>>
>>         On 29.11.2023 11:11, Giovanni Maruzzelli wrote:
>>>         First of all:
>>>         CONGRATULATIONS to the OpenSIPS community !!!
>>>         (I believe this is the first step of a long and
>>>         satisfying journey)
>>>
>>>         On the topic:
>>>         in addition to the CSCF component, I would like to see
>>>         efforts on the AS (Application Server) component of the IMS
>>>         infrastructure.
>>>
>>>         The AS is probably way the simplest of it all, it will
>>>         probably require the least modifications/additions to OpenSIPS.
>>>
>>>         But I would say AS will be crucial to a lot of people/use cases.
>>>
>>>         While for sure there will be a lot of cases for our
>>>         community to build the voice/video complete IMS
>>>         infrastructure on top of private 5G networks in enterprises
>>>         and public administrations, I see as very much relevant also
>>>         the use case of building infrastructure to provide
>>>         additional third party services to big carriers, and to big
>>>         carriers partners.
>>>
>>>         Also, AS is the correct and manageable way to provide
>>>         additional services even if you build the core IMS
>>>         infrastructure.
>>>
>>>         About HSS: this is the sancta sanctorum of a carrier/provider
>>>         Apart from the venerable fraunhofer java implementation, now
>>>         we can count on the flexible java implementation in
>>>         https://github.com/nickvsnetworking/pyhss with a lot of
>>>         features, good performances, and actually built for production.
>>>
>>>         I would say better we concentrate on accessing the various
>>>         different protocols of HSS (diameter/http2) from the various
>>>         components (each component in IMS access HSS with a
>>>         different interface with different vocabularies and actions.
>>>
>>>         MGCF/MGW, if needed, will be a natural extension of our
>>>         CSCF/AS architecture.
>>>
>>>         Just my two cents, to keep the ball rolling,
>>>
>>>         Congratulation again,
>>>
>>>         -giovanni
>>>
>>>
>>>         On Tue, Nov 28, 2023 at 2:02 PM Bogdan-Andrei Iancu
>>>         <bogdan at opensips.org> wrote:
>>>
>>>             Hi all,
>>>
>>>             (disclaimer : cross lists posting is not a good practice
>>>             - we will do this only to catch the attention and get
>>>             momentum with this initial topic)
>>>
>>>             As a first step here, is to work out the scope of the
>>>             IMS implementation in OpenSIPS. IMS is a vast concept,
>>>             with SIP and non-SIP components, and we want to
>>>             understand and agree on which components of IMS may be
>>>             subject of work from the OpenSIPS perspective. For
>>>             example, we do consider the CSCF as a must here, but we
>>>             may explore the HSS, AS, MGW or other components.
>>>
>>>             From the OpenSIPS perspective, we look for IMS
>>>             components which are SIP related. At least as a starting
>>>             point. So, the first obvious candidate is the *Call
>>>             Session Control Function (CSCF)*. And here we need to
>>>             look into and address the specific functionalities of
>>>             each sub-component:
>>>                 * P-CSCF
>>>                 * I-CSCF
>>>                 * S-CSCF
>>>
>>>             Again, these are the pretty obvious components, still
>>>             may look into and evaluate (if of an interest of the
>>>             OpenSIPS IMS implementation) areas as:
>>>                 * HSS (from interconnection perspective)
>>>                 * MGCF / MGW  (from interconnection perspective)
>>>                 * SIP AS
>>>                 * others ?
>>>
>>>             Any feedback (with explanations and arguments) about
>>>             what we should consider for our IMS implementation is
>>>             more the welcome. I set here just a simple starting
>>>             point, with no limitations or so. Feel free to
>>>             contribute to the topic
>>>
>>>
>>>             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
>>>
>>>
>>>
>>>         -- 
>>>         Sincerely,
>>>
>>>         Giovanni Maruzzelli
>>>         OpenTelecom.IT
>>>         cell: +39 347 266 56 18
>>>
>>
>>         _______________________________________________
>>         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/20231130/0069b7fe/attachment.html>