I want to suggest allowing some key functions to also accept variables as
input. To name a few: save(), lookup(), remove(), force_send_socket(). For
example, when using mongo, multiple Opensips servers and multiple location
tables it’s inflexible in the script to use some of these functions when you
have to hardcode something like, lookup(“location”,””) .
From: Liviu Chircu
Sent: Thursday, January 28, 2016 1:09 PM
To: OpenSIPS devel mailling list ; OpenSIPS users mailling list
Subject: [OpenSIPS-Users] [OpenSIPS Public Meeting] Follow-up: Scripting
variables in OpenSIPS 3.x
Hello!
The conclusions of yesterday's Public Meeting can be found here [1]
Here is a quick summary of the decided upon changes for variable restructuring
in OpenSIPS 3.x:
* variable referencing will now mandate an explicit scope (local, msg
(read/write into the SIP msg), tm, dlg, global)
* variables will still be dynamically typed
* improvements to explicit casting (from a couple of transformations to int(),
str(), list() and json())
* new data types: list and json, along with contructors and specific operators
("+" for concat, [] for indexing)
* AVPs dropped
* NULL special value to be kept
* find the best way of adapting the multi-index pseudo-vars, e.g.
$(hdr(Contact)[1])
This is still an ongoing effort, any feature is subject to change as we go
along with the development of OpenSIPS 3.0, so this is the ideal time to reply
to this thread and suggest improvements!
[1]: http://www.opensips.org/Community/IRCmeeting20160127
Best regards,
--
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
--------------------------------------------------------------------------------
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
