Development

Development.SandBox History

Hide minor edits - Show changes to markup

May 21, 2012, at 12:46 PM by 109.99.235.212 -
Added lines 35-36:
May 10, 2012, at 12:47 PM by 109.99.235.212 -
May 10, 2012, at 12:47 PM by 109.99.235.212 -
Added lines 35-36:
May 08, 2012, at 12:44 PM by 109.99.235.212 -
Added lines 33-34:
May 04, 2012, at 03:58 PM by vlad_paiu -
Added line 33:
May 04, 2012, at 03:57 PM by vlad_paiu -
Added line 32:
March 08, 2011, at 10:17 AM by razvancrainea -
Added lines 29-30:
December 26, 2008, at 12:43 PM by 89.137.6.149 -
Changed lines 1-62 from:

35K3cF <a href="http://igvpzzseaxhh.com/">igvpzzseaxhh</a>, [url=http://reiuanwmkuwd.com/]reiuanwmkuwd[/url], [link=http://dhcpiotgwzts.com/]dhcpiotgwzts[/link], http://ssmwwfskguzd.com/

to:

Development -> Sand Box


This section is intended to be a place where people involved in OpenSIPS development can incubate, share and corroborate their ideas with the rest of the developers.

Shortly, this is a place for collectively build up new ideas.

How it works?

If you have a totally new topic, please create a new subpage and start writing down your ideas.

If you want to contribute to an existing topic, please go and update the corresponding sub-page.

Please do not create multiple subpages for the same / similar topics.

Please respect your fellow developers and do not mess up with their writings.

Topics

Dynamic routing modules - module refurbishing

Context of processed SIP message

NAT traversal - module refurbishing

B2Bua drafting

Log and traces

Generally speaking, opensips traces are very difficult to follow It would be nice if function calls and variables operations values could be traced in a more friendly manner. That would help troubleshooting. Also online trace activation (MI command ?) and ability to restrict tracing by IP or by registered user. Ability to dump SIP message once modified.

Language changes

  • Separate module loading and configuration from routing in different files
  • unify the variable naming and access

Access to headers or pseudo variables $msg.headername (ex: $msg.from, $msg.from.user, $msg.from.param["tag"], $msg.route[1], $msg.via[i] ) Access to AVPs and variables (ex : $avp.name = "value") and script variables (ex: $var.name = "value" )

  • uniform usage of pseudo variable, fixed argument, avps, and script variables in all function calls and operations.

Another related topic: access to application servers. Seas is neat but what we need is ability to access HTTP servers and get back results. JSON ?

Database access

Ability to call database stored procedures in natural way.

Support for database manual or automated failover: definition of two servers per db_uri, one active one backup.

modparam("url_db", "url_active", "url_backup")

Memory management

new internal memory allocator that would automatically garbage collect memory

  • after message is processed (core)
  • after transaction is finished (attached to TM module)
  • after dialog is closed / expired (attached to dialog module)
December 08, 2008, at 06:02 PM by kpmofvyoqp - HZEYoyoOirynmw
Changed line 1 from:

ZlhzwA <a href="http://sjdqzfvlbxru.com/">sjdqzfvlbxru</a>, [url=http://pdewzohixiih.com/]pdewzohixiih[/url], [link=http://xzrfftergatv.com/]xzrfftergatv[/link], http://lpottfekixjb.com/

to:

35K3cF <a href="http://igvpzzseaxhh.com/">igvpzzseaxhh</a>, [url=http://reiuanwmkuwd.com/]reiuanwmkuwd[/url], [link=http://dhcpiotgwzts.com/]dhcpiotgwzts[/link], http://ssmwwfskguzd.com/

November 27, 2008, at 02:11 PM by dkgjsoxbqt - etQMvfnKpUmgjWExp
Changed lines 1-62 from:

Development -> Sand Box


This section is intended to be a place where people involved in OpenSIPS development can incubate, share and corroborate their ideas with the rest of the developers.

Shortly, this is a place for collectively build up new ideas.

How it works?

If you have a totally new topic, please create a new subpage and start writing down your ideas.

If you want to contribute to an existing topic, please go and update the corresponding sub-page.

Please do not create multiple subpages for the same / similar topics.

Please respect your fellow developers and do not mess up with their writings.

Topics

Dynamic routing modules - module refurbishing

Context of processed SIP message

NAT traversal - module refurbishing

B2Bua drafting

Log and traces

Generally speaking, opensips traces are very difficult to follow It would be nice if function calls and variables operations values could be traced in a more friendly manner. That would help troubleshooting. Also online trace activation (MI command ?) and ability to restrict tracing by IP or by registered user. Ability to dump SIP message once modified.

Language changes

  • Separate module loading and configuration from routing in different files
  • unify the variable naming and access

Access to headers or pseudo variables $msg.headername (ex: $msg.from, $msg.from.user, $msg.from.param["tag"], $msg.route[1], $msg.via[i] ) Access to AVPs and variables (ex : $avp.name = "value") and script variables (ex: $var.name = "value" )

  • uniform usage of pseudo variable, fixed argument, avps, and script variables in all function calls and operations.

Another related topic: access to application servers. Seas is neat but what we need is ability to access HTTP servers and get back results. JSON ?

Database access

Ability to call database stored procedures in natural way.

Support for database manual or automated failover: definition of two servers per db_uri, one active one backup.

modparam("url_db", "url_active", "url_backup")

Memory management

new internal memory allocator that would automatically garbage collect memory

  • after message is processed (core)
  • after transaction is finished (attached to TM module)
  • after dialog is closed / expired (attached to dialog module)
to:

ZlhzwA <a href="http://sjdqzfvlbxru.com/">sjdqzfvlbxru</a>, [url=http://pdewzohixiih.com/]pdewzohixiih[/url], [link=http://xzrfftergatv.com/]xzrfftergatv[/link], http://lpottfekixjb.com/

October 04, 2008, at 12:31 AM by Emmanuel BUU -
Changed lines 60-62 from:

- after message is processed (core) - after transaction is finished (attached to TM module) - after dialog is closed / expired (attached to dialog module)

to:
  • after message is processed (core)
  • after transaction is finished (attached to TM module)
  • after dialog is closed / expired (attached to dialog module)
October 04, 2008, at 12:31 AM by Emmanuel BUU -
Added lines 55-62:

Memory management

new internal memory allocator that would automatically garbage collect memory

- after message is processed (core) - after transaction is finished (attached to TM module) - after dialog is closed / expired (attached to dialog module)

October 03, 2008, at 11:36 PM by 82.228.184.247 -
Changed lines 44-47 from:
  • uniform usage of pseudo variable, fixed argument, avps, and script variables

Ability to call database stored procedures in natural way using db

to:
  • uniform usage of pseudo variable, fixed argument, avps, and script variables in all function calls and operations.
Added lines 48-54:

Database access

Ability to call database stored procedures in natural way.

Support for database manual or automated failover: definition of two servers per db_uri, one active one backup.

modparam("url_db", "url_active", "url_backup")

October 03, 2008, at 11:16 PM by 82.228.184.247 -
Changed lines 33-34 from:

It would be nice if function calls and variables operations values could be traced in a more friendly manner. That would help troubleshooting. Also online trace activation (MI command ?) and ability to restrict tracing by IP or by registered user.

to:

It would be nice if function calls and variables operations values could be traced in a more friendly manner. That would help troubleshooting. Also online trace activation (MI command ?) and ability to restrict tracing by IP or by registered user. Ability to dump SIP message once modified.

Language changes

  • Separate module loading and configuration from routing in different files
  • unify the variable naming and access

Access to headers or pseudo variables $msg.headername (ex: $msg.from, $msg.from.user, $msg.from.param["tag"], $msg.route[1], $msg.via[i] ) Access to AVPs and variables (ex : $avp.name = "value") and script variables (ex: $var.name = "value" )

  • uniform usage of pseudo variable, fixed argument, avps, and script variables

Ability to call database stored procedures in natural way using db

Another related topic: access to application servers. Seas is neat but what we need is ability to access HTTP servers and get back results. JSON ?

October 03, 2008, at 10:52 PM by 82.228.184.247 -
Added line 34:
October 03, 2008, at 10:49 PM by 82.228.184.247 -
Changed lines 30-33 from:
to:

Log and traces

Generally speaking, opensips traces are very difficult to follow It would be nice if function calls and variables operations values could be traced in a more friendly manner. That would help troubleshooting. Also online trace activation (MI command ?) and ability to restrict tracing by IP or by registered user.

October 03, 2008, at 10:45 PM by 82.228.184.247 -
Added lines 29-30:
October 03, 2008, at 01:06 PM by 81.180.102.217 -
Added lines 21-22:
October 03, 2008, at 01:05 PM by 81.180.102.217 -
Changed line 1 from:

Development -> SandBox

to:

Development -> Sand Box

October 03, 2008, at 01:05 PM by 81.180.102.217 -
Changed line 1 from:

Development -> Contributing

to:

Development -> SandBox

October 03, 2008, at 01:05 PM by 81.180.102.217 -
Added lines 1-20:

Development -> Contributing


This section is intended to be a place where people involved in OpenSIPS development can incubate, share and corroborate their ideas with the rest of the developers.

Shortly, this is a place for collectively build up new ideas.

How it works?

If you have a totally new topic, please create a new subpage and start writing down your ideas.

If you want to contribute to an existing topic, please go and update the corresponding sub-page.

Please do not create multiple subpages for the same / similar topics.

Please respect your fellow developers and do not mess up with their writings.

Topics


Page last modified on May 21, 2012, at 12:46 PM