<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="monospace">Hi all,<br>
<br>
(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)<br>
<br>
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.<br>
<br>
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 <b>Call Session Control Function (CSCF)</b>.
And here we need to look into and address the specific
functionalities of each sub-component: <br>
* P-CSCF<br>
* I-CSCF<br>
* S-CSCF<br>
<br>
Again, these are the pretty obvious components, still may look
into and evaluate (if of an interest of the OpenSIPS IMS
implementation) areas as:<br>
* HSS </font><font face="monospace"> (from interconnection
perspective)<br>
</font><font face="monospace"> * MGCF / MGW (from
interconnection perspective)<br>
* SIP AS<br>
* others ?<br>
<br>
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<br>
<br>
<br>
Best regards,<br>
</font>
<pre class="moz-signature" cols="72">--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
<a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a></pre>
</body>
</html>