Open liviuchircu opened 3 years ago
As of today, the user
module is distinguishing whether the OpenSIPS version is "3.2
or newer" by looking at the subscriber
table version. With this information, it is able to insert the appropriate data in the table.
Opening up this issue just for accounting purposes, so we start monitoring the core problem. In short: the CLI was originally written for OpenSIPS 3.0, and already there seem to be a few MI incompatibilities between 3.0 and 3.1. Along with the B2B module changes in 3.2, the incompatibility list grows, so this seems like a good time to start documenting all problems, so we can solve them as part of one solution.
MI Incompatibilities
3.0
->3.1
: the "event_jsonrpc" module has been renamed to "event_stream". This affects thediagnose
command, which is currently detecting the version by itself, so it can recommend users to load the correct module for their OpenSIPS version3.1
->3.2
: theb2b_trigger_scenario
MI command of the "b2b_logic" module has been reworked, both with different parameters and extra flavors (combinations) of them TODO: other ones?Implementation Ideas
3.0
->3.1+
: this transition may be inferred by simply checking for the presence of theraise_event
command in the typicalmi which
command which is already internally performed byopensips-cli
on startup.raise_event
was added in OpenSIPS 3.1.