[OpenSIPS-Users] choice of AS architecture

[Oleg Podguyko]

We looked at the seas for a reason. It seemed to us that was a good idea is when the SIP protocol is decoded only once and further work is already underway with this data. This approach, it seems to us, allows us to significantly increase the processing speed and avoid unnecessary encoding of such a message back to SIP for transmission to AS.
 
In our current scheme, part of the logic runs on the http server. Which we work with via http_rest_client.
We send part of the SIP headers to the http server, and to do this, we encode it all in json, then decode the response from the http server, and encode it in SIP. the HTTP server essentially performs the role of AS.
Everything works, but the load will grow. And we would like to have a light tool for working with SIP messages, without overhead such as SIP to JSON, JSON to SIP and so on.
Our opensips are already processing 400-500 CAPS. We periodically have problems (segfault). We even opened a ticket about this.
 
We are currently searching on the cscf + AS architecture. And we are trying to use the experience we have already gained
We think that there should be an idea of seas or maybe the possibility of using any other programming languages for some logic except lUA, for example python or something else to build AS next to opensips. 
It would be great also to have a mechanism where you can make changes to configs without restarting all opensips.
>Четверг, 16 апреля 2020, 14:00 +03:00 от Bogdan-Andrei Iancu <bogdan at opensips.org>:
> 
>Hey Oleg,
>
>What SIP features/capabilities do you want to have on the AS component? IMHO this is the point to start - based on your own requirements on what the AS must do, you can do a proper selection.
>
>And yes, as Tito said, seas is dead fish in the water for a long time.
>
>Regards,
>Bogdan-Andrei Iancu
>
>OpenSIPS Founder and Developer
>  https://www.opensips-solutions.com
>
>
>On 4/14/20 4:29 PM, Oleg Podguyko via Users wrote:
>>Hi Bogdan and all your team!
>> 
>>We have been working with opensips for quite some time and we like it. We keep the load on the order of 300-400 CAPS, and for example, the SIP-I module is perhaps the only solution that allows you to fully work with ISUP. Our programmers prepared several PRs based on the results of work with SIP-I and SCTP modules.
>>We are faced with the task of creating a classic bundle of cscf + AS server, in the future architecture opensips will play the role of cscf, and as AS we look at the module SEAS + external server.
>>
>>We are all moving towards IMS.
>> 
>>What do you think, how justified can such a choice be? Perhaps the opensips team already has its own new vision for this?
>>What would you choose as AS?
>> 
>> 
>>--
>>Oleg Podguyko  
>> 
>>_______________________________________________
>>Users mailing list
>>Users at lists.opensips.org
>>http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>> 
 
 
--
Олег Подгуйко
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200417/8cd5c1a0/attachment.html>