Development |
Development.Opensips-3-1-Planning HistoryHide minor edits - Show changes to markup May 27, 2020, at 03:36 PM
by
- Changed line 115 from:
to:
Changed line 117 from:
to:
May 25, 2020, at 02:33 PM
by
- Changed line 120 from:
to:
Changed line 122 from:
to:
May 14, 2020, at 10:30 AM
by
- Changed lines 10-12 from:
Routing calls and handling large volume of traffic is not a challenge anymore for OpenSIPS. The upcoming 3.1 release will focus on complex call crafting, basically on increasing OpenSIPS's ability to create and handle complex calling scenarios where multiple SIP calls are mixed and able to interact. Or shortly said, the 3.1 release will address the Class 5 specific calling features and how to control such calling features via APIs. As usual, all the OpenSIPS major releases are in depth presented during the OpenSIPS Summit yearly events. So, the 3.1 release is the star of OpenSIPS Summit in Amsterdam, May 2020. to:
Routing calls and handling large volume of traffic is not a challenge anymore for OpenSIPS. The upcoming 3.1 release will focus on complex call crafting, basically on increasing OpenSIPS's ability to create and handle complex calling scenarios where multiple SIP calls are mixed and able to interact. Or shortly said, the 3.1 release will address the Class 5 specific calling features and how to control such calling features via APIs. May 14, 2020, at 10:30 AM
by
- Changed line 119 from:
to:
May 14, 2020, at 10:29 AM
by
- Changed line 119 from:
to:
Changed line 127 from:
to:
May 07, 2020, at 10:11 AM
by
- Changed line 121 from:
to:
May 05, 2020, at 01:15 PM
by
- Changed line 131 from:
to:
May 05, 2020, at 01:15 PM
by
- Changed lines 116-118 from:
to:
Changed lines 120-121 from:
to:
Changed line 123 from:
to:
Changed lines 125-130 from:
to:
Changed line 132 from:
to:
March 25, 2020, at 03:14 PM
by
- Changed line 121 from:
to:
March 25, 2020, at 03:14 PM
by
- Changed lines 120-121 from:
to:
Changed line 125 from:
to:
March 10, 2020, at 12:02 PM
by
- Changed line 120 from:
to:
March 10, 2020, at 11:42 AM
by
- Changed line 118 from:
to:
March 10, 2020, at 11:34 AM
by
- Changed line 125 from:
to:
March 10, 2020, at 11:33 AM
by
- Changed line 130 from:
to:
February 06, 2020, at 12:53 PM
by
- Changed lines 19-20 from:
Without actually using a Back2Back model, but simply operating with calls (dialogs, UACs or UASs), many complex class 5 calling (and call mixing) scenarios may be scripted. to:
Without actually using a Back2Back model, but simply operating with calls (dialogs, UACs or UASs), many complex class 5 calling (and media bridging) scenarios may be scripted. Changed lines 24-25 from:
Call mixingAnother new OpenSIPS module, that is able to manipulate calls/dialogs going through OpenSIPS, along with UAC/UAS dialogs (call originated or terminated into OpenSIPS), with the sole propose of mixing the RTP media between these multiple flows. The idea is to make possible the injection of streams of media from / to proxied calls, with the help of auxiliary calls initiated by OpenSIPS. Typical example is to play media within an existing call/dialog with nothing more than simple re-INVITEs - OpenSIPS will initial a new sip call to a media server, in order to get the RTP stream for the playback and it will push it into the proxied call by triggering in-dialog re-INVITEs. to:
Call media bridgingAnother new OpenSIPS module, that is able to manipulate calls/dialogs going through OpenSIPS, along with UAC/UAS dialogs (call originated or terminated into OpenSIPS), with the sole propose of mixing the RTP media between these multiple flows. The idea is to make possible the injection of streams of media from / to proxied calls, with the help of auxiliary calls initiated by OpenSIPS. Typical example is to play media within an existing call/dialog with nothing more than simple re-INVITEs - OpenSIPS will initial a new sip call to a media server, in order to get the RTP stream for the playback and it will push it into the proxied call by triggering in-dialog re-INVITEs. Details about implementation of this feature can be found in the Media Bridging page. February 06, 2020, at 12:51 PM
by
- Changed line 123 from:
to:
February 06, 2020, at 12:51 PM
by
- Changed line 125 from:
to:
January 14, 2020, at 06:33 PM
by
- Added lines 106-135:
Poll ResultsThank you to everyone who voted! Please find the poll results below -- regarding the additional feature suggestions we received, we will go through them and pick the most popular / interesting ones in a future announcement. We try to update the list with their development status, so you can have a clear view over the 3.0 progress. Nevertheless, we strongly recommend you to check the Feature list of 3.1.
December 19, 2019, at 07:50 PM
by
- Changed line 103 from:
We are undergoing an OpenSIPS 3.1 Feature Survey (due 13th January 2020), and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you! to:
We are undergoing an OpenSIPS 3.1 Feature Survey (due 13th January 2020), and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you! December 19, 2019, at 07:39 PM
by
- Changed lines 9-15 from:
https://blogopensips.files.wordpress.com/2018/12/opensips-3.0-icon.png For the upcoming OpenSIPS 3.0 release (and 3.x family) the main focus is on the devops concept. This translates into introducing and enhancing in OpenSIPS features / capabilities that (1) will increase the easiness when comes the writing / developing OpenSIPS scripts and (2) simplify the operational activities when comes to running and managing OpenSIPS. This OpenSIPS 3.0 release is the star of OpenSIPS Summit in Amsterdam, April-May 2019 - beside presentations and workshops around the new cool things in this version, OpenSIPS 3.0 will also be the subject of several interactive demos on its new capabilities. to:
https://blogopensips.files.wordpress.com/2019/12/opensips-3.1-crafting.jpg Routing calls and handling large volume of traffic is not a challenge anymore for OpenSIPS. The upcoming 3.1 release will focus on complex call crafting, basically on increasing OpenSIPS's ability to create and handle complex calling scenarios where multiple SIP calls are mixed and able to interact. Or shortly said, the 3.1 release will address the Class 5 specific calling features and how to control such calling features via APIs. As usual, all the OpenSIPS major releases are in depth presented during the OpenSIPS Summit yearly events. So, the 3.1 release is the star of OpenSIPS Summit in Amsterdam, May 2020. Changed lines 16-27 from:
Script Development aspectsGeneric Preprocessor SupportThis feature adds full built-in pre-processing support for the OpenSIPS script. OpenSIPS 3.0 integrates various existing pre-processors within OpenSIPS. This simplify the scripting itself, the script portability across multiple servers and not to mention the entire deployment process of more complex platforms (where OpenSIPS is just a part of it). Even more, you will be able to use your preferred pre-processor and align OpenSIPS with the rest of your system (M4, Jinja, Embedded Ruby or others). Module Functions Now Benefit From a New Parameter InterfaceAs a response to frequent mailing list complaints of wildly varying behaviors across different module functions (e.g. some accept integers/strings as inputs while others accept both integers/strings or variables holding such values), we've introduced an abstract layer which handles the parameter passing task for all module functions, effectively making all of them more powerful by globally allowing flexible input. An added benefit is that new OpenSIPS modules are now even faster to develop. See the new function calling conventions here. to:
Class 5 calling ingredientsWithout actually using a Back2Back model, but simply operating with calls (dialogs, UACs or UASs), many complex class 5 calling (and call mixing) scenarios may be scripted. Calling APIA new OpenSIPS module, placed on top of dialog module, will allow remote control over the calls going through OpenSIPS. The module will expose a simplified set of commands (API like) for setting up new calls, for answering and terminating calls, for transferring or putting on-hold calls - all these without interacting with the end-devices, but triggering and handling the action only from the OpenSIPS (as proxy) level. Call mixingAnother new OpenSIPS module, that is able to manipulate calls/dialogs going through OpenSIPS, along with UAC/UAS dialogs (call originated or terminated into OpenSIPS), with the sole propose of mixing the RTP media between these multiple flows. The idea is to make possible the injection of streams of media from / to proxied calls, with the help of auxiliary calls initiated by OpenSIPS. Typical example is to play media within an existing call/dialog with nothing more than simple re-INVITEs - OpenSIPS will initial a new sip call to a media server, in order to get the RTP stream for the playback and it will push it into the proxied call by triggering in-dialog re-INVITEs. Per-call hooksAs we already have for transactions, the dialog module will allow the script writer to set, in a per-dialog fashion, script routes to be triggered by various dialog events. Similar to t_on_failure(route), you can do dlg_on_timeout(route) to have a route called when the dialog lifetime is exceed. In the route, you may decide to extend the lifetime, to terminate the call or do any other logging. We can foresen dlg_on_answer(route), dlg_on_terminate(route)' (and more) triggers, which will give a better interaction and control over the ongoing calls. SDP topology hidingDue to the specificity of class 5 scenarios, there is a real need to completely decouple the SDP's (not only from IP/port perspective) from the caller and callee side, like hiding the originator or overwriting the session name and version. DTMF supportFor both RTProxy and RTPEngine, OpenSIPS will be able to report to the OpenSIPS script the DTMF events sampled from the passing RTP. This will make possible the implementation of simple IVRs and/or authentication via DTMF with nothing more than OpenSIPS and the media relay. Extended BLF supportIn Class 5 services, BLF is an important feature. Besides working out clustering support for BLF, an important task is reworking the BLF implementation to be call-branch aware, to be able to properly report the call events in parallel calling or call hunting scenarios. Dialog module enhancementsWe are looking at a good set of additions for the dialog module, like:
Changed lines 46-79 from:
Operational aspectsRouting Script Re-loadOpenSIPS 3.0 exposes the valuable ability of reloading the routes (not the module configuration) during runtime, with zero penalties and with zero loses as traffic. See the documentation of the MI "reload_routes" function. Processes Auto-Scaling SupportThis is the ability of OpenSIPS to scale up and down the number of processes at runtime. Basically OpenSIPS is able to automatically scale up (by forking new processes) according to the volume of traffic, or to scale down (terminating some worker processes) if the internal load is low. This means you do not have to worry if your estimation on the number for worker processes is correct or not (will my OpenSIPS hold to the traffic??) or to worry about planning restarts during the night (to manually resize the number of processes). New OpenSIPS CLI (Command Line Interface) toolStarting with OpenSIPS 3.0, the old opensipsctl tool becomes deprecated (as functionality and as software) and it is replaced by the new opensips-cli - a powerful Python3 application that allows you to interact in a smart way with OpenSIPS, to invoke advanced tools such as diagnose or tracer, as well as to perform DB provisioning. Read a full description of opensips-cli here. Selectable Memory Allocator SupportThis feature allows the internal memory manager to be selected at startup time. In OpenSIPS 3.0, the memory manager selection becomes a startup option, via command line arguments, allowing you to change it without any need to recompile or redeploy. Read a full description of this feature here. Internal Memory Persistence during RestartAs there are several modules caching (in OpenSIPS internal memory, not in external no-sql cachers) large chunks of data, like Dynamic Routing, Dialplan, Dispatcher or Permissions, OpenSIPS 3.0 is able to avoid the data loading and caching penalty during a restart - this segments of the internal memory do "survive" during the restart. This dramatically reduces the time to restart of the entire service. Unified Sharing Tags for ClusteringIn 2.4, each module (with clustering support) is managing its own sharing tags completely isolated from other modules - this make the operating OpenSIPS a bit difficult sometime, as for a single switch from active to backup, you need to individually inform and change the tags in several modules, via several MI commands. In OpenSIPS 3.0 we have now the sharing tags managed by clusterer module itself and shared between multiple modules. So with a single MI command, changing a single sharing tag, you can control all the cluster-aware modules (like dialog timeouts, nathelper pinging, dispatcher pinging, etc) Read a full description of this feature here. to:
Back-to-back supportThe existing B2B implementation in OpenSIPS has some limitations, so we are looking to overcome via some major rework here. Script driven B2BInstead of using the XML scenario to drive the B2B logic (mixing between the calls), we want to use the OpenSIPS scripting for this purpose. This will eliminate all the limitations of the XML language (logic and action) and it will tremendously increase the level of integration of the B2B engine with the rest of the OpenSIPS functionalities. Shortly, more complex B2B logic will be possible, and also better integrated with the rest of OpenSIPS. B2B clustering supportTo be 100% production ready, an High-Availability support maybe available for the B2B engine. This will be achieved by adding clustering and replication support for the B2B calling. B2B contextAn important improvement of the B2B engine will be the addition of the B2B context, to help in correlating all the entities (UAC, UAS) part of a B2B session, to attach custom data to the entities and to exchange such data between the entities. This will help with Accounting and media relaying support for B2B, but also with building custom data sharing inside a B2B session (or between the sessions). Changed lines 62-75 from:
Integration aspectsMI Interaction StandardizationAn extensive rework of the Management Interface in an attempt to standardize and speed up development of external applications which need to interact with OpenSIPS. The custom, JSON-based HTTP calls of OpenSIPS 2.X are now replaced with the JSON-RPC version 2 standard. The custom, line-oriented syntax was completely dropped. XMLRPC and mi_html (former mi_http) were kept backwards-compatible. Read a detailed description of the new interactions here SMPP supportOpenSIPS 3.0 provides a new SMPP module that allows you to do bidirectional gatewaying between SIP and SMPP traffic - this is a powerful but flexible way to integrate with most of the SMS providers / gateways. Read a full description of this feature here. RabbitMQ Consumer supportA new RabbitMQ consumer module which manages connections with one or more brokers, subscribes for events and propagates them at OpenSIPS script level via the event interface. to:
Call CenterFor 3.1, we are looking at:
Device Feature Key Synchronization (DFKS)DFKS support is planned for OpenSIPS 3.1. This will help to keep feature settings in sync between multiple device and application servers, an essential need in a class 5 / PBX environment. STIR/SHAKENDealing with Robocalling and CLI spoofing becomes a must when building advanced calling solutions. The support for STIR/SHAKEN will be part of OpenSIPS 3.1, providing multiple usage models, in terms of how the certificates are to be handled during the verification process. Also a flexible approach (to the standards) will be able to cope with all the potential changes derived from the adoption process (of the standard by the providers). Push Notification (RFC8599)The existing PN support will be improved and aligned to the requirements as per newly adopted RFC 8599. Besides the notification itself, we need to address some particularities in contact registration, derived from privacy concerns or device identification concerns. noSQL adds-onThe DB layer needs a constant attention, so here is the plan for 3.1:
December 19, 2019, at 07:37 PM
by
- Changed lines 9-13 from:
https://blogopensips.files.wordpress.com/2018/12/opensips-3.1-icon.png For the upcoming OpenSIPS 3.1 release (and 3.x family) the main focus is on the devops concept. This translates into introducing and enhancing in OpenSIPS features / capabilities that (1) will increase the easiness when comes the writing / developing OpenSIPS scripts and (2) simplify the operational activities when comes to running and managing OpenSIPS. For the OpenSIPS 3.1 release, the following areas of development are considered: to:
https://blogopensips.files.wordpress.com/2018/12/opensips-3.0-icon.png For the upcoming OpenSIPS 3.0 release (and 3.x family) the main focus is on the devops concept. This translates into introducing and enhancing in OpenSIPS features / capabilities that (1) will increase the easiness when comes the writing / developing OpenSIPS scripts and (2) simplify the operational activities when comes to running and managing OpenSIPS. This OpenSIPS 3.0 release is the star of OpenSIPS Summit in Amsterdam, April-May 2019 - beside presentations and workshops around the new cool things in this version, OpenSIPS 3.0 will also be the subject of several interactive demos on its new capabilities. Changed lines 21-36 from:
This is about improving the experience of the OpenSIPS script writer (developer), by enhancing and simplifying the OpenSIPS script:
Want to provide feedback? See below to:
Generic Preprocessor SupportThis feature adds full built-in pre-processing support for the OpenSIPS script. OpenSIPS 3.0 integrates various existing pre-processors within OpenSIPS. This simplify the scripting itself, the script portability across multiple servers and not to mention the entire deployment process of more complex platforms (where OpenSIPS is just a part of it). Even more, you will be able to use your preferred pre-processor and align OpenSIPS with the rest of your system (M4, Jinja, Embedded Ruby or others). Module Functions Now Benefit From a New Parameter InterfaceAs a response to frequent mailing list complaints of wildly varying behaviors across different module functions (e.g. some accept integers/strings as inputs while others accept both integers/strings or variables holding such values), we've introduced an abstract layer which handles the parameter passing task for all module functions, effectively making all of them more powerful by globally allowing flexible input. An added benefit is that new OpenSIPS modules are now even faster to develop. See the new function calling conventions here. Changed lines 34-57 from:
Several enhancements and new concepts are planned for OpenSIPS 3.1 in order to help with operating OpenSIPS - making it simpler to run, to monitor, to troubleshoot and diagnose:
Want to provide feedback? See below to:
Routing Script Re-loadOpenSIPS 3.0 exposes the valuable ability of reloading the routes (not the module configuration) during runtime, with zero penalties and with zero loses as traffic. See the documentation of the MI "reload_routes" function. Processes Auto-Scaling SupportThis is the ability of OpenSIPS to scale up and down the number of processes at runtime. Basically OpenSIPS is able to automatically scale up (by forking new processes) according to the volume of traffic, or to scale down (terminating some worker processes) if the internal load is low. This means you do not have to worry if your estimation on the number for worker processes is correct or not (will my OpenSIPS hold to the traffic??) or to worry about planning restarts during the night (to manually resize the number of processes). New OpenSIPS CLI (Command Line Interface) toolStarting with OpenSIPS 3.0, the old opensipsctl tool becomes deprecated (as functionality and as software) and it is replaced by the new opensips-cli - a powerful Python3 application that allows you to interact in a smart way with OpenSIPS, to invoke advanced tools such as diagnose or tracer, as well as to perform DB provisioning. Read a full description of opensips-cli here. Selectable Memory Allocator SupportThis feature allows the internal memory manager to be selected at startup time. In OpenSIPS 3.0, the memory manager selection becomes a startup option, via command line arguments, allowing you to change it without any need to recompile or redeploy. Read a full description of this feature here. Internal Memory Persistence during RestartAs there are several modules caching (in OpenSIPS internal memory, not in external no-sql cachers) large chunks of data, like Dynamic Routing, Dialplan, Dispatcher or Permissions, OpenSIPS 3.0 is able to avoid the data loading and caching penalty during a restart - this segments of the internal memory do "survive" during the restart. This dramatically reduces the time to restart of the entire service. Unified Sharing Tags for ClusteringIn 2.4, each module (with clustering support) is managing its own sharing tags completely isolated from other modules - this make the operating OpenSIPS a bit difficult sometime, as for a single switch from active to backup, you need to individually inform and change the tags in several modules, via several MI commands. In OpenSIPS 3.0 we have now the sharing tags managed by clusterer module itself and shared between multiple modules. So with a single MI command, changing a single sharing tag, you can control all the cluster-aware modules (like dialog timeouts, nathelper pinging, dispatcher pinging, etc) Read a full description of this feature here. Changed lines 70-77 from:
More integration capabilities are to be added to the 3.1 release :
to:
MI Interaction StandardizationAn extensive rework of the Management Interface in an attempt to standardize and speed up development of external applications which need to interact with OpenSIPS. The custom, JSON-based HTTP calls of OpenSIPS 2.X are now replaced with the JSON-RPC version 2 standard. The custom, line-oriented syntax was completely dropped. XMLRPC and mi_html (former mi_http) were kept backwards-compatible. Read a detailed description of the new interactions here SMPP supportOpenSIPS 3.0 provides a new SMPP module that allows you to do bidirectional gatewaying between SIP and SMPP traffic - this is a powerful but flexible way to integrate with most of the SMS providers / gateways. Read a full description of this feature here. RabbitMQ Consumer supportA new RabbitMQ consumer module which manages connections with one or more brokers, subscribes for events and propagates them at OpenSIPS script level via the event interface. Changed lines 88-121 from:
We are undergoing an OpenSIPS 3.1 Feature Survey (due 6th January 2019), and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you!
Poll ResultsThank you to everyone who voted! Please find the poll results below -- regarding the additional feature suggestions we received, we will go through them and pick the most popular / interesting ones in a future announcement. We try to update the list with their development status, so you can have a clear view over the 3.1 progress. Nevertheless, we strongly recommend you to check the Feature list of 3.1.
to:
We are undergoing an OpenSIPS 3.1 Feature Survey (due 13th January 2020), and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you! April 11, 2019, at 01:20 PM
by
- Changed line 100 from:
to:
April 05, 2019, at 03:26 PM
by
- Changed line 92 from:
to:
April 05, 2019, at 03:25 PM
by
- Changed line 98 from:
to:
March 18, 2019, at 06:57 PM
by
- Added lines 81-82:
We try to update the list with their development status, so you can have a clear view over the 3.1 progress. Nevertheless, we strongly recommend you to check the Feature list of 3.1. Changed lines 85-104 from:
to:
Changed line 106 from:
OpenSIPS 3.1 Feature Survey Results to:
January 09, 2019, at 12:20 PM
by
- Changed lines 74-105 from:
We are undergoing an OpenSIPS 3.1 Feature Survey (due 6th January 2019), and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you! to:
We are undergoing an OpenSIPS 3.1 Feature Survey (due 6th January 2019), and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you!
Poll ResultsThank you to everyone who voted! Please find the poll results below -- regarding the additional feature suggestions we received, we will go through them and pick the most popular / interesting ones in a future announcement.
OpenSIPS 3.1 Feature Survey Results
December 13, 2018, at 05:08 PM
by
- Changed line 1 from:
to:
December 13, 2018, at 02:16 PM
by
- Changed lines 16-17 from:
Want to provide feedback? See below to:
Added lines 31-32:
Want to provide feedback? See below Changed lines 35-36 from:
Want to provide feedback? See below to:
Added lines 58-59:
Want to provide feedback? See below Deleted line 61:
Want to provide feedback? See below December 13, 2018, at 02:15 PM
by
- Deleted line 15:
Deleted line 33:
Deleted line 59:
December 13, 2018, at 02:15 PM
by
- Added lines 17-18:
Want to provide feedback? See below Added lines 36-37:
Want to provide feedback? See below Added lines 63-64:
Want to provide feedback? See below Added line 73:
December 13, 2018, at 02:12 PM
by
- Changed line 69 from:
We are undergoing an OpenSIPS 3.1 Feature Survey, and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you! to:
We are undergoing an OpenSIPS 3.1 Feature Survey (due 6th January 2019), and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you! December 13, 2018, at 02:09 PM
by
- Changed line 69 from:
We are undergoing an OpenSIPS 3.1 Feature Survey, and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you! to:
We are undergoing an OpenSIPS 3.1 Feature Survey, and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you! December 13, 2018, at 02:06 PM
by
- Changed line 69 from:
We are undergoing an OpenSIPS 3.1 Feature Survey, and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming release. Thank you! to:
We are undergoing an OpenSIPS 3.1 Feature Survey, and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming 3.1 release. Thank you! December 13, 2018, at 02:05 PM
by
- Added line 6:
Added lines 66-69:
Vote your Favorite Features!We are undergoing an OpenSIPS 3.1 Feature Survey, and we would like to gather opinions on the currently chosen feature set, as well as any additional ideas you may have. Your feedback will help us prioritize the work that will go into the upcoming release. Thank you! December 13, 2018, at 12:57 PM
by
- Changed line 64 from:
to:
December 13, 2018, at 12:56 PM
by
- Changed line 24 from:
to:
December 13, 2018, at 11:50 AM
by
- Added line 13:
Changed line 30 from:
to:
Added line 55:
December 12, 2018, at 07:35 PM
by
- Changed lines 13-14 from:
"Dev" areato:
Script Development aspectsChanged lines 30-31 from:
"Ops" areato:
Operational aspectsChanged line 54 from:
Integration areato:
Integration aspectsDecember 12, 2018, at 07:34 PM
by
- Changed line 58 from:
to:
December 12, 2018, at 07:21 PM
by
- Changed line 54 from:
Integrationto:
Integration areaDecember 12, 2018, at 07:07 PM
by
- Changed line 58 from:
to:
December 12, 2018, at 07:04 PM
by
- Changed line 8 from:
https://blogopensips.files.wordpress.com/2017/11/google-idi_018-1.jpg to:
https://blogopensips.files.wordpress.com/2018/12/opensips-3.1-icon.png December 12, 2018, at 06:58 PM
by
- Added lines 19-20:
Deleted lines 36-37:
December 12, 2018, at 06:28 PM
by
- Deleted line 3:
(:toc-float Table of Content:) December 12, 2018, at 06:27 PM
by
- Changed line 37 from:
to:
December 12, 2018, at 06:15 PM
by
- Added line 64:
December 12, 2018, at 06:14 PM
by
- Added lines 39-40:
Added lines 59-60:
Added line 64:
December 12, 2018, at 06:01 PM
by
- Changed lines 18-21 from:
to:
Added lines 22-23:
Changed lines 26-28 from:
to:
Changed lines 35-38 from:
to:
Added lines 43-52:
Changed lines 57-60 from:
to:
December 12, 2018, at 04:44 PM
by
- Added line 17:
Added lines 20-21:
Changed line 45 from:
to:
December 12, 2018, at 01:56 PM
by
- Changed lines 28-30 from:
This feature will also impact the resource consumption (as power or cloud resources) thanks to the automatic down-scaling under low traffic. to:
Changed line 42 from:
to:
December 12, 2018, at 01:56 PM
by
- Added lines 1-43:
Development -> Topics? -> OpenSIPS 3.1 Planning(:title OpenSIPS 3.1 Planning:) (:toc-float Table of Content:) OpenSIPS 3.1 philosophyhttps://blogopensips.files.wordpress.com/2017/11/google-idi_018-1.jpg For the upcoming OpenSIPS 3.1 release (and 3.x family) the main focus is on the devops concept. This translates into introducing and enhancing in OpenSIPS features / capabilities that (1) will increase the easiness when comes the writing / developing OpenSIPS scripts and (2) simplify the operational activities when comes to running and managing OpenSIPS. For the OpenSIPS 3.1 release, the following areas of development are considered: "Dev" areaThis is about improving the experience of the OpenSIPS script writer (developer), by enhancing and simplifying the OpenSIPS script:
"Ops" areaSeveral enhancements and new concepts are planned for OpenSIPS 3.1 in order to help with operating OpenSIPS - making it simpler to run, to monitor, to troubleshoot and diagnose:
This feature will also impact the resource consumption (as power or cloud resources) thanks to the automatic down-scaling under low traffic.
IntegrationMore integration capabilities are to be added to the 3.1 release : |