|
Development |
Development.SandBox HistoryShow minor edits - Show changes to markup May 10, 2012, at 01:47 PM
by - May 04, 2012, at 04:58 PM
by -
Added line 33:
December 26, 2008, at 01:43 PM
by -
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 BoxThis 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. TopicsDynamic routing modules - module refurbishing Context of processed SIP message NAT traversal - module refurbishing 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
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" )
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
December 08, 2008, at 07:02 PM
by - 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 03:11 PM
by - etQMvfnKpUmgjWExp
Changed lines 1-62 from:
Development -> Sand BoxThis 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. TopicsDynamic routing modules - module refurbishing Context of processed SIP message NAT traversal - module refurbishing 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
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" )
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
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 01:31 AM
by -
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:
October 04, 2008, at 01:31 AM
by -
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 04, 2008, at 12:36 AM
by -
Changed lines 44-47 from:
Ability to call database stored procedures in natural way using db to:
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 04, 2008, at 12:16 AM
by -
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
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" )
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 11:52 PM
by -
Added line 34:
October 03, 2008, at 11:49 PM
by -
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 02:08 PM
by -
Changed lines 22-28 from:
to:
October 03, 2008, at 02:05 PM
by -
Changed line 1 from:
Development -> SandBoxto:
Development -> Sand BoxOctober 03, 2008, at 02:05 PM
by -
Changed line 1 from:
Development -> Contributingto:
Development -> SandBoxOctober 03, 2008, at 02:05 PM
by -
Added lines 1-20:
Development -> ContributingThis 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 |