<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="monospace">Hi Julien,<br>
<br>
The term of AS is super abused when comes to what it should
deliver. First of all you clearly need to define what should be
the services/functionalities you need from an "AS" and to see what
solutions are available to implement them. <br>
<br>
In most of the cases, OpenSIPS as proxy (dialog stateful) is able
to provide most of them, without the need so any fancy external
servlet or app - just using the OpenSIPS script.<br>
<br>
If there are good reasons to externalize the routing logic, you
should consider more simple and flexible approach, take a look at
this:<br>
<a class="moz-txt-link-freetext" href="https://blog.opensips.org/2023/03/22/api-driven-sip-user-agent-end-point-with-opensips-3-4/">https://blog.opensips.org/2023/03/22/api-driven-sip-user-agent-end-point-with-opensips-3-4/</a><br>
<br>
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>
<div class="moz-cite-prefix">On 20.04.2024 11:50,
<a class="moz-txt-link-abbreviated" href="mailto:julien.royannais@orange.com">julien.royannais@orange.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:DU5PR02MB107089FB368BBCD127F467D6DE40C2@DU5PR02MB10708.eurprd02.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator"
content="Microsoft Word 15 (filtered medium)">
<style>@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:"Helvetica 75 Bold";
panose-1:2 11 8 4 2 2 2 2 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ligatures:standardcontextual;
mso-fareast-language:EN-US;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0cm;}ul
{margin-bottom:0cm;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hello everyone,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I'm reaching out to get
your opinion on using openSIPS with a business Application
Server (AS) that would handle the routing logic.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">At first glance, the
SEAS module seems designed for this purpose, but it doesn't
appear to be a good fit as it seems highly coupled with a
Sip Servlet implementation using a specific protocol only
supported for WeSIP.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">It might be better to
use REST interfaces, a 302 redirect-based mechanism, or
possibly another module.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Thank you for your
insights & advice!<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">JR</span><o:p></o:p></p>
<div
style="margin-left:5.0pt;margin-top:5.0pt;margin-right:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="text-align:center" align="center"><span
style="font-size:8.0pt;font-family:"Helvetica 75 Bold",sans-serif;color:#ED7D31">Orange
Restricted<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<p
style="font-family:Helvetica 75 Bold;font-size:8pt;color:#ED7D31;margin:5pt;font-style:normal;font-weight:normal;text-decoration:none;"
align="Center">
Orange Restricted<br>
</p>
<pre>_________________<wbr>______________________________<wbr>______________________________<wbr>______________________________<wbr>_
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.</pre>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>