-
Notifications
You must be signed in to change notification settings - Fork 583
IMS Working Group Roadmap
The current roadmap is available below. This is a starting point, milestones may be added or removes, also the timing may change with the progress of the discussions within the group. We will try to updates as realtime as possible here.
-
Kickoff - the OpenSIPS core team is to provide a starting point (seed) for the discussions, in terms of roadmap, areas to cover (as IMS solution) and technical requirements.
-
Define the scope - the first goal of the IMS OWG is to define the scope of the IMS support 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.
-
Technical Requirements - once the scope is in place, the next task of the IMS OWG is to explore the technical details and implications of each IMS component to be addressed. Here we are heavily relying on the input (as expertise) from people already involved in the IMS world.
-
Planning the development - with the Technical Requirements in place, the development work is to be planned, in terms of available man power (people/entities/companies looking to be involved in the actual devel) and in terms of software solution design.
-
Development work - this is probably the simplest to define step, still the most time and resources intensive. Following the agreed Planning, the implementation work is to be done.
-
Packing and Documenting - the code is not everything, so the IMS OWG had to wrap up the developed code into an usable IMS support. This means producing documentation on the IMS approach and support in IMS, together with packing ready to be used IMS components with OpenSIPS.