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.
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.
Access to headers or pseudo variables $msg.headername (ex: $msg.from, $msg.from.user, $msg.from.param["tag"], $msg.route, $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 ?
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")
new internal memory allocator that would automatically garbage collect memory