[OpenSIPS-Devel] SF.net SVN: opensips:[9602] trunk

2013-01-21 Thread Razvan Crainea
Revision: 9602
  http://opensips.svn.sourceforge.net/opensips/?rev=9602view=rev
Author:   razvancrainea
Date: 2013-01-21 10:50:34 + (Mon, 21 Jan 2013)
Log Message:
---
Create new message each time an event_route is run and backup the avp lists
Properly set the integer parameters type for the event_route

Modified Paths:
--
trunk/evi/event_interface.c
trunk/modules/event_route/event_route.c

This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.


___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel


[OpenSIPS-Devel] SF.net SVN: opensips:[9603] trunk

2013-01-21 Thread Liviu Chircu
Revision: 9603
  http://opensips.svn.sourceforge.net/opensips/?rev=9603view=rev
Author:   liviuchircu
Date: 2013-01-21 12:42:36 + (Mon, 21 Jan 2013)
Log Message:
---
New functionality: Script tracing!
With script tracing, you can better understand the flow of execution in the 
OpenSIPS script.
Moreover, you can also trace the values of pseudo-variables, as script 
execution progresses.

The blocks of the script where script tracing is enabled will print a line for 
each individual
action that is done (e.g. assignments, conditional tests, module functions, 
core functions, etc.).
Multiple pseudo-variables can be monitored by specifying a pv_format string
(e.g. $ru---$avp(var1)). The current value of the format will be printed 
along with each line.

The logs of multiple traced regions of your script can be differentiated by 
specifying an
additional plain string as the 3rd parameter.

Script tracing can be enabled with: script_trace(log_level, pv_format_string[, 
info_string])
To disable script tracing, just: script_trace()

Modified Paths:
--
trunk/action.c
trunk/cfg.lex
trunk/cfg.y
trunk/route_struct.h

This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.


___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel


[OpenSIPS-Devel] [EVENT] OpenSIPS at FOSDEM 2013

2013-01-21 Thread Răzvan Crainea

Hi all!

We would like to announce you that the *OpenSIPS* project will attend 
the 13th FOSDEM[1] conference on 2  3 February 2013, in Brussels, 
Belgium[2], where I(Răzvan Crainea), Vlad Paiu and Saúl Ibarra Corretgé 
will talk in the telephony devroom[3] about some of the most exciting 
topics of VoIP nowadays: clusters, monitoring and integration. You can 
find more information about the event here[4].The presentations will be 
the following:


 * SIP is hard, let's go shopping! by Saúl Ibarra Corretgé, onSunday, 
startingfrom09:35, in Room H.1309
 * OpenSIPS at the core of a distributed and maintainable VoIP 
platform, by Răzvan Crainea and Vlad Paiu, onSunday, starting from 
10:45, in Room H.1309
 * From SIP to XMPP and vice versa, by Saúl Ibarra Corretgé, onSunday, 
starting from 14:15, in Room H.1309


Besides that, we believe this is a good opportunity to consolidate our 
open-source community, and we would like to take advantage of it. 
Therefore we scheduled  an OpenSIPS beer session for Saturday, 2nd of 
February 2013, at 20:00 - meeting point is in front of the FOSDEM main 
entrance, each pays for his drinks. Having a beer and fun is a must, no 
technical skills required ;).


[1] https://fosdem.org/2013/
[2] https://fosdem.org/2013/practical/transportation/
[3] https://fosdem.org/2013/schedule/track/telephony/
[4] http://www.opensips.org/Events/Fosdem2013

Looking forward to meet you in Brussels!

--
Razvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel


[OpenSIPS-Devel] SF.net SVN: opensips:[9604] trunk

2013-01-21 Thread Liviu Chircu
Revision: 9604
  http://opensips.svn.sourceforge.net/opensips/?rev=9604view=rev
Author:   liviuchircu
Date: 2013-01-21 18:59:28 + (Mon, 21 Jan 2013)
Log Message:
---
Added named flags!
From now on, the proper way of setting a msg / script / branch flag is by 
supplying
an unquoted string: setflag(NEW_FLAG). Same for setsflag/setbflag and
their isflagset/resetflag/issflagset/resetsflag/isbflagset/resetbflag 
counterparts.

Regarding the module parameters which are affected, for now both INT/STRING 
versions are
supported, but setting INT flags the classic way is now deprecated, and will 
throw a
minor warning at module load.

The maximum individual flags of a flag type remains 32.

Modified Paths:
--
trunk/cfg.y
trunk/flags.c
trunk/flags.h
trunk/modules/acc/README
trunk/modules/acc/acc_mod.c
trunk/modules/acc/doc/acc_admin.xml
trunk/modules/auth_aaa/README
trunk/modules/auth_aaa/authaaa_mod.c
trunk/modules/auth_aaa/doc/auth_aaa_admin.xml
trunk/modules/call_control/README
trunk/modules/call_control/call_control.c
trunk/modules/call_control/doc/call_control_admin.xml
trunk/modules/nathelper/README
trunk/modules/nathelper/doc/nathelper_admin.xml
trunk/modules/nathelper/nathelper.c
trunk/modules/qos/README
trunk/modules/qos/doc/qos_admin.xml
trunk/modules/qos/qos.c
trunk/modules/siptrace/README
trunk/modules/siptrace/doc/siptrace_admin.xml
trunk/modules/siptrace/siptrace.c
trunk/modules/sst/README
trunk/modules/sst/doc/sst_admin.xml
trunk/modules/sst/sst.c
trunk/modules/tm/README
trunk/modules/tm/doc/tm_admin.xml
trunk/modules/tm/t_reply.c
trunk/modules/tm/t_reply.h
trunk/modules/tm/tm.c
trunk/modules/usrloc/README
trunk/modules/usrloc/doc/usrloc_admin.xml
trunk/modules/usrloc/ul_mod.c
trunk/route.c

This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.


___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel


[OpenSIPS-Devel] SF.net SVN: opensips:[9605] trunk/modules/nathelper/nathelper.c

2013-01-21 Thread Ovidiu Sas
Revision: 9605
  http://opensips.svn.sourceforge.net/opensips/?rev=9605view=rev
Author:   osas
Date: 2013-01-21 19:43:33 + (Mon, 21 Jan 2013)
Log Message:
---
nathelper: fix sipping_bflag to accept string as a value

Modified Paths:
--
trunk/modules/nathelper/nathelper.c

This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.


___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel


[OpenSIPS-Devel] SF.net SVN: opensips:[9606] trunk/scripts/opensipsdbctl

2013-01-21 Thread Ovidiu Sas
Revision: 9606
  http://opensips.svn.sourceforge.net/opensips/?rev=9606view=rev
Author:   osas
Date: 2013-01-21 20:21:08 + (Mon, 21 Jan 2013)
Log Message:
---
opensipsdbctl: fix presence tables provisioning

Modified Paths:
--
trunk/scripts/opensipsdbctl

This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.


___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel


[OpenSIPS-Devel] SF.net SVN: opensips:[9607] trunk/modules/pi_http

2013-01-21 Thread Ovidiu Sas
Revision: 9607
  http://opensips.svn.sourceforge.net/opensips/?rev=9607view=rev
Author:   osas
Date: 2013-01-21 20:41:54 + (Mon, 21 Jan 2013)
Log Message:
---
pi_http: renaming pi_root parameter to pi_http_root

Modified Paths:
--
trunk/modules/pi_http/README
trunk/modules/pi_http/doc/pi_http_admin.xml
trunk/modules/pi_http/pi_http.c

This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.


___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel


[OpenSIPS-Devel] [NEW] scripting enhancements

2013-01-21 Thread Bogdan-Andrei Iancu

Hi all,

OpenSIPS trunk (future 1.9) just got better with some awesome script 
enhancements:


1) *Flags with name*, thanks to Liviu  Chircu
Message, script and branch flags have now alphanumerical names, instead 
of numerical ID (as so far). Now you can simply do:

setflag(DO_SIPTRACE);
or
issflagset(SRC_IS_GW);
The migration to named flags affects all flag related functions and the 
module parameters used for defining flags (like flag to enable sip 
tracing, etc).
This change is 100% backward compatible, but you will get some warning 
about deprecation of the ID based flags.



2) *Script tracing*, also thanks to Liviu Chircu
With script tracing, you can better understand the flow of execution in 
the OpenSIPS script. Moreover, you can also trace the values of 
pseudo-variables, as script execution progresses.
The blocks of the script where script tracing is enabled will print a 
line for each individual action that is done (e.g. assignments, 
conditional tests, module functions, core functions, etc.). Multiple 
pseudo-variables can be monitored by specifying a pv_format string (e.g. 
$ru---$avp(var1)). The current value of the format will be printed 
along with each line.
Script tracing can be enabled with: script_trace(log_level, 
pv_format_string[, info_string])

Ex:
[line 578][me][module consume_credentials] - (INVITE from 
127.0.0.1 , ruri=sip:111...@opensips.org)
[line 581][me][core setsflag] - (INVITE from 127.0.0.1, 
ruri=sip:111...@opensips.org)
[line 583][me][assign equal] - (INVITE from 127.0.0.1, 
ruri=sip:111...@opensips.org)
[line 592][me][core if] - (INVITE from 127.0.0.1 , 
ruri=sip:tes...@opensips.org)
[line 585][me][module is_avp_set] - (INVITE from 127.0.0.1, 
ruri=sip:tes...@opensips.org)
[line 589][me][core if] - (INVITE from 127.0.0.1, 
ruri=sip:tes...@opensips.org)
[line 586][me][module is_method] - (INVITE from 127.0.0.1, 
ruri=sip:tes...@opensips.org)
[line 587][me][module trace_dialog] - (INVITE 127.0.0.1, 
ruri=sip:tes...@opensips.org)
[line 590][me][core setflag] - (INVITE from 127.0.0.1, 
ruri=sip:tes...@opensips.org)


See: http://www.opensips.org/Resources/DocsCoreFcn#toc146


3) *Routes with parameters*, thanks to Razvan Crainea
When calling a script route, some extra parameters can be attached 
(example: route(ROUTE_NAME, 1);), that can be later retrieved from 
within the route using the a type of '$param' pseudo variable.

You can push up to 7 parameters which can be strings, numbers or variables.
Ex:

  route[tester] {
  if ($param(1)  $param(2) )
xlog(test $param(3) failed \n);
send_reply(403,Forbidden);
exit;
  }
  }

  
  route(tester, $avp(calls), 10, max call limit);
  

See: http://www.opensips.org/Resources/DocsCoreFcn#toc145
 http://www.opensips.org/Resources/DocsCoreVar#toc56



I hope you will enjoy these new goodies, feedback is appreciated.


Best regards,

--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel