<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=content-type></HEAD>
<BODY dir=ltr bgColor=#ffffff text=#000000>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>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”,””) .
</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=liviu@opensips.org
href="mailto:liviu@opensips.org">Liviu Chircu</A> </DIV>
<DIV><B>Sent:</B> Thursday, January 28, 2016 1:09 PM</DIV>
<DIV><B>To:</B> <A title=devel@lists.opensips.org
href="mailto:devel@lists.opensips.org">OpenSIPS devel mailling list</A> ; <A
title=users@lists.opensips.org href="mailto:users@lists.opensips.org">OpenSIPS
users mailling list</A> </DIV>
<DIV><B>Subject:</B> [OpenSIPS-Users] [OpenSIPS Public Meeting] Follow-up:
Scripting variables in OpenSIPS 3.x</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'><TT>Hello!</TT><TT><BR></TT>
<DIV class=moz-forward-container><TT></TT><TT><BR></TT><TT>The conclusions of
yesterday's Public Meeting can be found here
[1]</TT><TT><BR></TT><TT></TT><TT><BR></TT><TT>Here is a quick summary of the
decided upon changes for variable restructuring in OpenSIPS
3.x:</TT><TT><BR></TT><TT></TT><TT><BR></TT><TT>* variable referencing will now
mandate an </TT><TT><B>explicit scope</B></TT><TT> (local, msg (read/write into
the SIP msg), tm, dlg, global)</TT><TT><BR></TT><TT>* variables will still be
</TT><TT><B>dynamically typed</B></TT><TT><BR></TT><TT>* improvements to
</TT><TT><B>explicit casting</B></TT><TT> (from a couple of transformations to
int(), str(), list() and json())</TT><TT><BR></TT><TT>* </TT><TT><B>new data
types</B></TT><TT>: list and json, along with contructors and specific operators
("+" for concat, [] for indexing)</TT><TT><BR></TT><TT>* </TT><TT><B>AVPs
dropped</B></TT><TT><BR></TT><TT>* </TT><TT><B>NULL </B></TT><TT>special value
to be kept</TT><TT><BR></TT><TT>* find the best way of adapting the multi-index
pseudo-vars, e.g.
$(hdr(Contact)[1])</TT><TT><BR></TT><TT></TT><TT><BR></TT><TT>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!</TT><TT><BR></TT><TT></TT><TT><BR></TT><TT>[1]:
</TT><TT><A class=moz-txt-link-freetext
href="http://www.opensips.org/Community/IRCmeeting20160127"
moz-do-not-send="true">http://www.opensips.org/Community/IRCmeeting20160127</A></TT><TT><BR></TT><TT></TT><TT><BR></TT><TT>Best
regards,</TT><TT><BR></TT><TT></TT><TT></TT><PRE class=moz-signature cols="72">--
Liviu Chircu
OpenSIPS Developer
<A class=moz-txt-link-freetext href="http://www.opensips-solutions.com" moz-do-not-send="true">http://www.opensips-solutions.com</A></PRE></DIV>
<P>
<HR>
_______________________________________________<BR>Users mailing
list<BR>Users@lists.opensips.org<BR>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<BR></DIV></DIV></DIV></BODY></HTML>