DIALOG module
Admin Guide
Section titled “Admin Guide”Overview
Section titled “Overview”The dialog module provides dialog awareness to the OpenSIPS proxy. Its functionality is to keep trace of the current dialogs, to offer information about them (like how many dialogs are active).
Aside tracking, the dialog module offers functionalities like flags and attributes per dialog (persistent data across dialog), dialog profiling and dialog termination (on timeout base or external triggered).
The module, via an internal API, also provide the foundation to build on top of it more complex dialog-based functionalities via other OpenSIPS modules.
How it works
Section titled “How it works”To create the dialog associated to an initial request, the flag “dlg_flag” (dlg flag id) must be set before creating the corresponding transaction.
The dialog is automatically destroyed when a “BYE” is received. In case of no “BYE”, the dialog lifetime is controlled via the default timeout (see “default_timeout” - default timeout id) and custom timeout (see “timeout_avp” - timeout avp id). The dialog timeout is reset each time a sequential (except ACKs) request passes.
The module is able to cut/terminate the call from the middle (proxy side) when the dialog gives timeout. By setting the “bye_on_timeout_flag” - bye on timeout flag id on dialog creation, BYEs will be automatically sent (in both directions) when the timeout event occurs.
Dialog profiling
Section titled “Dialog profiling”Dialog profiling is a mechanism that helps in classifying, sorting and keeping trace of certain types of dialogs, using whatever properties of the dialog (like caller, destination, type of calls, etc). Dialogs can be dynamically added in different (and several) profile tables - logically, each profile table can have a special meaning (like dialogs outside the doamin, dialogs terminated to PSTN, etc).
There are two types of profiles:
- with no value - a dialog simply belongs to a profile. (like outbound calls profile). There is no other additional information to describe the dialog’s belonging to the profile;
- with value - a dialog belongs to a profile having a certain value (like in caller profile, where the value is the caller ID). The belonging of the dialog to the profile is strictly related to the value.
A dialog can be added to multiple profiles in the same time.
Profiles are visible (at the moment) in the request route (for initial and sequential requests) and in the branch, failure and reply routes of the original request.
Dependencies
Section titled “Dependencies”OpenSIPS Modules
Section titled “OpenSIPS Modules”The following modules must be loaded before this module:
- TM - Transaction module
- RR - Record-Route module
External Libraries or Applications
Section titled “External Libraries or Applications”The following libraries or applications must be installed before running OpenSIPS with this module loaded:
- None.
Exported Parameters
Section titled “Exported Parameters”enable_stats (integer)
Section titled “enable_stats (integer)”If the statistics support should be enabled or not. Via statistic variables, the module provide information about the dialog processing. Set it to zero to disable or to non-zero to enable it.
Default value is “1 (enabled)“.
...modparam("dialog", "enable_stats", 0)...hash_size (integer)
Section titled “hash_size (integer)”The size of the hash table internally used to keep the dialogs. A larger table is much faster but consumes more memory. The hash size must be a power of 2 number.
Default value is “4096”.
...modparam("dialog", "hash_size", 1024)...rr_param (string)
Section titled “rr_param (string)”Name of the Record-Route parameter to be added with the dialog cookie. It is used for fast dialog matching of the sequential requests.
Default value is “did”.
...modparam("dialog", "rr_param", "xyz")...dlg_flag (integer)
Section titled “dlg_flag (integer)”Flag to be used for marking if a dialog should be constructed for the current request (make sense only for initial requests).
Default value is “none”.
...modparam("dialog", "dlg_flag", 4)...bye_on_timeout_flag (integer)
Section titled “bye_on_timeout_flag (integer)”Message falg to be set if you want the dialog module to automatically send BYE requests (in both directions) when the dialog give timeout.
The flag must be set for the initial INVITE and before creating the dialog (before doing t_relay() or t_newtran()). You cannot change this option (of sending the BYEs at timeout event) during the dialog.
Default value is “none”.
...modparam("dialog", "bye_on_timeout_flag", 6)...timeout_avp (string)
Section titled “timeout_avp (string)”The specification of an AVP to contain a custom timeout (in seconds) for the dialog. It may be used only in a request (initial or sequential) context
Default value is “none”.
...modparam("dialog", "timeout_avp", "$avp(i:10)")...default_timeout (integer)
Section titled “default_timeout (integer)”The default dialog timeout (in seconds) if no custom one is set.
Default value is “43200 (12 hours)“.
...modparam("dialog", "default_timeout", 21600)...dlg_extra_hdrs (string)
Section titled “dlg_extra_hdrs (string)”A string containing the extra headers (full format, with EOH) to be added in the requests generated by the module (like BYEs).
Default value is “NULL”.
...modparam("dialog", "dlg_extra_hdrs", "Hint: credit expired\r\n")...dlg_match_mode (integer)
Section titled “dlg_match_mode (integer)”How the seqential requests should be matched against the known dialogs. The modes are a combination between matching based on a cookie (DID) stored as cookie in Record-Route header and the matching based on SIP elements (as in RFC3261).
The supported modes are:
- 0 - DID_ONLY - the match is done exclusively based on DID;
- 1 - DID_FALLBACK - the match is first tried based on DID and if not present, it will fallback to SIP matching;
- 2 - DID_NONE - the match is done exclusively based on SIP elements; no DID information is added in RR.
Default value is “0 (DID_ONLY)“.
...modparam("dialog", "dlg_match_mode", 1)...db_url (string)
Section titled “db_url (string)”If you want to store the information about the dialogs in a database a database url must be specified.
Default value is “mysql://opensips:opensipsrw@localhost/opensips”.
...modparam("dialog", "db_url", "dbdriver://username:password@dbhost/dbname")...db_mode (integer)
Section titled “db_mode (integer)”Describe how to push into the DB the dialogs’ information from memory.
The supported modes are:
- 0 - NO_DB - the memory content is not flushed into DB;
- 1 - REALTIME - any dialog information changes will be reflected into the database immediatly.
- 2 - DELAYED - the dialog information changes will be flushed into DB periodically, based on a timre routine.
- 3 - SHUTDOWN - the dialog information will be flushed into DB only at shutdown - no runtime updates.
Default value is “0”.
...modparam("dialog", "db_mode", 1)...db_update_period (integer)
Section titled “db_update_period (integer)”The interval (seconds) at which to update dialogs’ information if you chose to store the dialogs’ info at a given interval. A too short interval will generate intensiv database operations, a too large one will not notice short dialogs.
Default value is “60”.
...modparam("dialog", "db_update_period", 120)...table_name (string)
Section titled “table_name (string)”If you want to store the information about the dialogs in a database a table name must be specified.
Default value is “dialog”.
...modparam("dialog", "table_name", "my_dialog")...callid_column (string)
Section titled “callid_column (string)”The column’s name in the database to store the dialogs’ callid.
Default value is “callid”.
...modparam("dialog", "callid_column", "callid_c_name")...from_uri_column (string)
Section titled “from_uri_column (string)”The column’s name in the database to store the caller’s sip address.
Default value is “from_uri”.
...modparam("dialog", "from_uri_column", "from_uri_c_name")...from_tag_column (string)
Section titled “from_tag_column (string)”The column’s name in the database to store the From tag from the Invite request.
Default value is “from_tag”.
...modparam("dialog", "from_tag_column", "from_tag_c_name")...to_uri_column (string)
Section titled “to_uri_column (string)”The column’s name in the database to store the calee’s sip address.
Default value is “to_uri”.
...modparam("dialog", "to_uri_column", "to_uri_c_name")...to_tag_column (string)
Section titled “to_tag_column (string)”The column’s name in the database to store the To tag from the 200 OK response to the Invite request, if present.
Default value is “to_tag”.
...modparam("dialog", "to_tag_column", "to_tag_c_name")...caller_cseq_column (string)
Section titled “caller_cseq_column (string)”The column’s name in the database to store the cseq from caller side.
Default value is “caller_cseq”.
...modparam("dialog", "caller_cseq_column", "column_name")...callee_cseq_column (string)
Section titled “callee_cseq_column (string)”The column’s name in the database to store the cseq from callee side.
Default value is “callee_cseq”.
...modparam("dialog", "callee_cseq_column", "column_name")...caller_route_column (string)
Section titled “caller_route_column (string)”The column’s name in the database to store the route records from caller side (proxy to caller).
Default value is “caller_route_set”.
...modparam("dialog", "caller_route_column", "column_name")...callee_route_column (string)
Section titled “callee_route_column (string)”The column’s name in the database to store the route records from callee side (proxy to callee).
Default value is “callee_route_set”.
...modparam("dialog", "to_route_column", "column_name")...caller_contact_column (string)
Section titled “caller_contact_column (string)”The column’s name in the database to store the caller’s contact uri.
Default value is “from_contact”.
...modparam("dialog", "caller_contact_column", "column_name")...callee_contact_column (string)
Section titled “callee_contact_column (string)”The column’s name in the database to store the callee’s contact uri.
Default value is “callee_contact”.
...modparam("dialog", "callee_contact_column", "column_name")...caller_sock_column (string)
Section titled “caller_sock_column (string)”The column’s name in the database to store the information about the local interface receiving the traffic from caller.
Default value is “caller_sock”.
...modparam("dialog", "caller_sock_column", "column_name")...callee_sock_column (string)
Section titled “callee_sock_column (string)”The column’s name in the database to store information about the local interface receiving the traffic from callee.
Default value is “callee_contact”.
...modparam("dialog", "callee_sock_column", "column_name")...h_id_column (string)
Section titled “h_id_column (string)”The column’s name in the database to store the dialogs’ hash id information.
Default value is “hash_id”.
...modparam("dialog", "h_id_column", "hash_id_c_name")...h_entry_column (string)
Section titled “h_entry_column (string)”The column’s name in the database to store the dialogs’ hash entry information.
Default value is “hash_entry”.
...modparam("dialog", "h_entry_column", "h_entry_c_name")...state_column (string)
Section titled “state_column (string)”The column’s name in the database to store the dialogs’ state information.
Default value is “state”.
...modparam("dialog", "state_column", "state_c_name")...start_time_column (string)
Section titled “start_time_column (string)”The column’s name in the database to store the dialogs’ start time information.
Default value is “start_time”.
...modparam("dialog", "start_time_column", "start_time_c_name")...timeout_column (string)
Section titled “timeout_column (string)”The column’s name in the database to store the dialogs’ timeout.
Default value is “timeout”.
...modparam("dialog", "timeout_column", "timeout_c_name")...profiles_with_value (string)
Section titled “profiles_with_value (string)”List of names for profiles with values.
Default value is “empty”.
...modparam("dialog", "profiles_with_value", "caller ; my_profile")...profiles_no_value (string)
Section titled “profiles_no_value (string)”List of names for profiles without values.
Default value is “empty”.
...modparam("dialog", "profiles_no_value", "inbound ; outbound")...Exported Functions
Section titled “Exported Functions”create_dialog()
Section titled “create_dialog()”The function creats the dialog for the currently processed request. The request must be an initial request.
The function returns true if the dialog was successfully created or if the dialog was previously created.
This function can be used from REQUEST_ROUTE.
...create_dialog();...set_dlg_profile(profile,[value])
Section titled “set_dlg_profile(profile,[value])”Inserts the current dialog into a profile. Note that the profile does not supports values, this will be silently discarded. Also, there is no check for inserting the same dialog in the same profile for multiple times.
Meaning of the parameters is as follows:
- profile - name of the profile to be added to;
- value (optional) - string value to define the belonging of the dialog to the profile - note that the profile must support values. Pseudo-variables are supported.
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE, REPLY_ROUTE and FAILURE_ROUTE.
...set_dlg_profile("inbound_call");set_dlg_profile("caller","$fu");...unset_dlg_profile(profile,[value])
Section titled “unset_dlg_profile(profile,[value])”Removes the current dialog from a profile.
Meaning of the parameters is as follows:
- profile - name of the profile to be removed from;
- value (optional) - string value to define the belonging of the dialog to the profile - note that the profile must support values. Pseudo-variables are supported.
This function can be used from BRANCH_ROUTE, REPLY_ROUTE and FAILURE_ROUTE.
...unset_dlg_profile("inbound_call");unset_dlg_profile("caller","$fu");...is_in_profile(profile,[value])
Section titled “is_in_profile(profile,[value])”Checks if the current dialog belongs to a profile. If the profile supports values, the check can be reinforced to take into account a specific value - if the dialog was inserted into the profile for a specific value. If no value is passed, only simply belonging of the dialog to the profile is checked. Note that if the profile does not support values, this will be silently discarded.
Meaning of the parameters is as follows:
- profile - name of the profile to be checked against;
- value (optional) - string value to toughen the check. Pseudo-variables are supported.
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE, REPLY_ROUTE and FAILURE_ROUTE.
...if (is_in_profile("inbound_call")) { log("this request belongs to a inbound call\n");}...if (is_in_profile("caller","XX")) { log("this request belongs to a call of user XX\n");}...get_profile_size(profile,[value],size)
Section titled “get_profile_size(profile,[value],size)”Returns the number of dialogs belonging to a profile. If the profile supports values, the check can be reinforced to take into account a specific value - how many dialogs were inserted into the profile with a specific value. If not value is passed, only simply belonging of the dialog to the profile is checked. Note that the profile does not supports values, this will be silently discarded.
Meaning of the parameters is as follows:
- profile - name of the profile to get the size for;
- value (optional) - string value to toughen the check. Pseudo-variables are supported;
- size - an AVP or script variable to return the profile size in.
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE, REPLY_ROUTE and FAILURE_ROUTE.
...get_profile_size("inbound_call","$avp(size)");xlog("currently there are $avp(size) inbound calls\n");...get_profile_size("caller","$fu");xlog("currently, the user %fu has $avp(size) active outgoing calls\n");...set_dlg_flag(idx)
Section titled “set_dlg_flag(idx)”Sets the dialog flag index idx to true. The dialog flags are dialog persistent and they can be accessed (set and test) for all requests belonging to the dialog.
The flag index can be between 0 and 31.
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE, REPLY_ROUTE and FAILURE_ROUTE.
...set_dlg_flag("3");...reset_dlg_flag(idx)
Section titled “reset_dlg_flag(idx)”Resets the dialog flag index idx to false. The dialog flags are dialog persistent and they can be accessed (set and test) for all requests belonging to the dialog.
The flag index can be between 0 and 31.
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE, REPLY_ROUTE and FAILURE_ROUTE.
...reset_dlg_flag("16");...is_dlg_flag_set(idx)
Section titled “is_dlg_flag_set(idx)”Returns true if the dialog flag index idx is set. The dialog flags are dialog persistent and they can be accessed (set and test) for all requests belonging to the dialog.
The flag index can be between 0 and 31.
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE, REPLY_ROUTE and FAILURE_ROUTE.
...if (is_dlg_flag_set("16")) { xlog("dialog flag 16 is set\n");}...store_dlg_value(name,val)
Section titled “store_dlg_value(name,val)”Attaches to the dialog the value val under the name name. The values attached to dialogs are dialog persistent and they can be accessed (read and write) for all requests belonging to the dialog.
Parameter val may contain pseudo-variables.
Same functionality may be obtain by assigning a value to pseudo variable $dlg_val(name).
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE, REPLY_ROUTE and FAILURE_ROUTE.
...store_dlg_value("inv_src_ip","$si");store_dlg_value("account type","prepaid");# or$dlg_val("account_type") = "prepaid";...fetch_dlg_value(name,pvar)
Section titled “fetch_dlg_value(name,pvar)”Fetches from the dialog the value of attribute named name. The values attached to dialogs are dialog persistent and they can be accessed (read and write) for all requests belonging to the dialog.
Parameter pvar may be a script var ($var) or and avp ($avp).
Same functionality may be obtain by reading the pseudo variable $dlg_val(name).
This function can be used from REQUEST_ROUTE, BRANCH_ROUTE, REPLY_ROUTE and FAILURE_ROUTE.
...fetch_dlg_value("inv_src_ip","$avp(i:2)");fetch_dlg_value("account type","$var(account)");# or$var(account) = $dlg_val("account_type");...Exported Statistics
Section titled “Exported Statistics”active_dialogs
Section titled “active_dialogs”Returns the number of current active dialogs (may be confirmed or not).
early_dialogs
Section titled “early_dialogs”Returns the number of early dialogs.
processed_dialogs
Section titled “processed_dialogs”Returns the total number of processed dialogs (terminated, expired or active) from the startup.
expired_dialogs
Section titled “expired_dialogs”Returns the total number of expired dialogs from the startup.
failed_dialogs
Section titled “failed_dialogs”Returns the number of failed dialogs.
Exported MI Functions
Section titled “Exported MI Functions”dlg_list
Section titled “dlg_list”Lists the description of a dialog or of all dialogs (calls). If only one dialogs is to be listed, the dialog identifiers are to be passed as paramter (callid and fromtag).
Name: dlg_list
Parameters:
- callid (optional) - callid if a single dialog to be listed.
- from_tag (optional, but cannot be present without the callid paramter) - fromtag (as per initial request) of the dialog to be listed. entry
MI FIFO Command Format:
:dlg_list:_reply_fifo_file__empty_line_:dlg_list:_reply_fifo_file_abcdrssfrs122444@192.168.1.1AAdfeEFF33dlg_list_ctx
Section titled “dlg_list_ctx”The same as the “dlg_list” but including in the dialog description the associated context from modules sitting on top of the dialog module.
Name: dlg_list_ctx
Parameters: see “dlg_list”
MI FIFO Command Format:
:dlg_list_ctx:_reply_fifo_file__empty_line_dlg_end_dlg
Section titled “dlg_end_dlg”Terminates an ongoing dialog by sending BYE in both directions.
Name: dlg_end_dlg
Parameters:
- h_entry - hash entry of the dialog in the internal dialog table
- h_id - hash id of the dialog on the hash entry
- extra_hdrs - (optional) string containg extra headers (full format) to be added to the BYE requests.
The values for the h_entry and h_id can be get via the dlg_list MI command.
MI FIFO Command Format:
:dlg_end_dlg:_reply_fifo_file_34256_empty_line_profile_get_size
Section titled “profile_get_size”Returns the number of dialogs belonging to a profile. If the profile supports values, the check can be reinforced to take into account a specific value - how many dialogs were inserted into the profile with a specific value. If not value is passed, only simply belonging of the dialog to the profile is checked. Note that the profile does not supports values, this will be silently discarded.
Name: profile_get_size
Parameters:
- profile - name of the profile to get the value for.
- value (optional)- string value to toughen the check;
MI FIFO Command Format:
:profile_get_size:_reply_fifo_file_inbound_calls_empty_line_profile_list_dlgs
Section titled “profile_list_dlgs”Lists all the dialogs belonging to a profile. If the profile supports values, the check can be reinforced to take into account a specific value - list only the dialogs that were inserted into the profile with that specific value. If not value is passed, all dialogs belonging to the profile will be listed. Note that the profile does not supports values, this will be silently discarded.
Name: profile_list_dlgs
Parameters:
- profile - name of the profile to list the dialog for.
- value (optional)- string value to toughen the check;
MI FIFO Command Format:
:profile_list_dlgs:_reply_fifo_file_inbound_calls_empty_line_Exported Pseudo-Variables
Section titled “Exported Pseudo-Variables”$DLG_count
Section titled “$DLG_count”Returns the number of current active dialogs (may be confirmed or not).
$DLG_status
Section titled “$DLG_status”Returns the status of the dialog corresponding to the processed sequential request. This PV will be available only for sequential requests, after doing loose_route().
Value may be:
- NULL - Dialog not found.
- 3 - Confirmed by a final reply but no ACK received yet.
- 4 - Confirmed by a final reply and ACK received.
- 5 - Dialog ended.
$DLG_lifetime
Section titled “$DLG_lifetime”Returns the duration (in seconds) of the dialog corresponding to the processed sequential request. The duration is calculated from the dialog confirmation and the current moment. This PV will be available only for sequential requests, after doing loose_route().
NULL will be returned if there is no dialog for the request.
$DLG_flags
Section titled “$DLG_flags”Returns the the dialog flags array (as a single interger value) of the dialog corresponding to the processed sequential request. This PV will be available only for sequential requests, after doing loose_route().
NULL will be returned if there is no dialog for the request.
$dlg_val(name)
Section titled “$dlg_val(name)”This is a read/write variable that allows access to the dialog attribute named name. This PV will be available only for sequential requests, after doing loose_route().
NULL will be returned if there is no dialog for the request.
Developer Guide
Section titled “Developer Guide”Available Functions
Section titled “Available Functions”register_dlgcb (dialog, type, cb, param, free_param_cb)
Section titled “register_dlgcb (dialog, type, cb, param, free_param_cb)”Register a new callback to the dialog.
Meaning of the parameters is as follows:
- struct dlg_cell dlg* - dialog to register callback to. If maybe NULL only for DLG_CREATED callback type, which is not a per dialog type.
- int type - types of callbacks; more
types may be register for the same callback function; only
DLG_CREATED must be register alone. Possible types:
- DLGCB_LOADED
- DLGCB_SAVED
- DLG_CREATED - called when a new dialog is created - it’s a global type (not associated to any dialog)
- DLG_FAILED - called when the dialog was negatively replied (non-2xx) - it’s a per dialog type.
- DLG_CONFIRMED - called when the dialog is confirmed (2xx replied) - it’s a per dialog type.
- DLG_REQ_WITHIN - called when the dialog matches a sequential request - it’s a per dialog type.
- DLG_TERMINATED - called when the dialog is terminated via BYE - it’s a per dialog type.
- DLG_EXPIRED - called when the dialog expires without receiving a BYE - it’s a per dialog type.
- DLGCB_EARLY - called when the dialog is created in an early state (18x replied) - it’s a per dialog type.
- DLGCB_RESPONSE_FWDED - called when the dialog matches a reply to the initial INVITE request - it’s a per dialog type.
- DLGCB_RESPONSE_WITHIN - called when the dialog matches a reply to a subsequent in dialog request - it’s a per dialog type.
- DLGCB_MI_CONTEXT - called when the mi dlg_list_ctx command is invoked - it’s a per dialog type.
- DLGCB_DESTROY
- dialog_cb cb - callback function to be called. Prototype is: “void (dialog_cb) (struct dlg_cell* dlg, int type, struct dlg_cb_params * params); ”
- *void param - parameter to be passed to the callback function.
- param_free callback_param_free - callback function to be called to free the param. Prototype is: “void (param_free_cb) (void *param);“
Frequently Asked Questions
Section titled “Frequently Asked Questions”Q: What happend with “use_tight_match” parameter?
The parameter was removed with version 1.3 as the option of tight matching became mandatory and not configurable. Now, the tight matching is done all the time (when using DID matching).
Q: Where can I find more about OpenSIPS?
Take a look at http://www.opensips.org/.
Q: Where can I post a question about this module?
First at all check if your question was already answered on one of our mailing lists:
E-mails regarding any stable OpenSIPS release should be sent to users@lists.opensips.org and e-mails regarding development versions should be sent to devel@lists.opensips.org.
If you want to keep the mail private, send it to users@lists.opensips.org.
Q: How can I report a bug?
Please follow the guidelines provided at: https://github.com/OpenSIPS/opensips/issues.
Contributors
Section titled “Contributors”By Commit Statistics
Section titled “By Commit Statistics”Top contributors by DevScore(1), authored commits(2) and lines added/removed(3)
| # | Name | DevScore | Commits | Lines++ | Lines— |
|---|---|---|---|---|---|
| 1. | Bogdan-Andrei Iancu (@bogdan-iancu) | 256 | 147 | 9191 | 1864 |
| 2. | Dan Pascu (@danpascu) | 27 | 22 | 210 | 156 |
| 3. | Stefan Darius (@dariusstefan) | 27 | 5 | 1775 | 374 |
| 4. | Ovidiu Sas (@ovidiusas) | 25 | 16 | 530 | 186 |
| 5. | Daniel-Constantin Mierla (@miconda) | 16 | 13 | 76 | 66 |
| 6. | Henning Westerholt (@henningw) | 16 | 10 | 172 | 187 |
| 7. | Carsten Bock | 6 | 3 | 116 | 87 |
| 8. | Hugues Mitonneau | 5 | 3 | 44 | 2 |
| 9. | Tavis Paquette | 5 | 1 | 146 | 69 |
| 10. | Jerome Martin | 4 | 2 | 11 | 6 |
All remaining contributors: Klaus Darilion, Michel Bensoussan, Richard Revels, Elena-Ramona Modroiu, Jeffrey Magder, Andrei Dragus, Ron Winacott, Andy Pyles, Konstantin Bokarius, Razvan Crainea (@razvancrainea), UnixDev, Alex Hermann, Eliot Gable, Edson Gellert Schubert.
(1) DevScore = author_commits + author_lines_added / (project_lines_added / project_commits) + author_lines_deleted / (project_lines_deleted / project_commits)
(2) including any documentation-related commits, excluding merge commits
(3) ignoring whitespace edits, renamed files and auto-generated files
By Commit Activity
Section titled “By Commit Activity”| # | Name | Commit Activity |
|---|---|---|
| 1. | Stefan Darius (@dariusstefan) | Jun 2026 - Jul 2026 |
| 2. | Razvan Crainea (@razvancrainea) | Jun 2026 - Jun 2026 |
| 3. | Bogdan-Andrei Iancu (@bogdan-iancu) | Apr 2006 - Apr 2010 |
| 4. | Andrei Dragus | Sep 2009 - Sep 2009 |
| 5. | Hugues Mitonneau | Feb 2009 - Mar 2009 |
| 6. | Richard Revels | Feb 2009 - Feb 2009 |
| 7. | UnixDev | Feb 2009 - Feb 2009 |
| 8. | Dan Pascu (@danpascu) | Dec 2007 - Dec 2008 |
| 9. | Ovidiu Sas (@ovidiusas) | Feb 2008 - Nov 2008 |
| 10. | Alex Hermann | Nov 2008 - Nov 2008 |
All remaining contributors: Henning Westerholt (@henningw), Carsten Bock, Klaus Darilion, Daniel-Constantin Mierla (@miconda), Konstantin Bokarius, Edson Gellert Schubert, Jerome Martin, Tavis Paquette, Michel Bensoussan, Eliot Gable, Andy Pyles, Elena-Ramona Modroiu, Jeffrey Magder, Ron Winacott.
(1) including any documentation-related commits, excluding merge commits
Documentation
Section titled “Documentation”Contributors
Section titled “Contributors”Last edited by: Razvan Crainea (@razvancrainea), Bogdan-Andrei Iancu (@bogdan-iancu), Hugues Mitonneau, Klaus Darilion, Henning Westerholt (@henningw), Ovidiu Sas (@ovidiusas), Daniel-Constantin Mierla (@miconda), Konstantin Bokarius, Edson Gellert Schubert, Dan Pascu (@danpascu), Michel Bensoussan, Andy Pyles, Elena-Ramona Modroiu.
License
Section titled “License”All documentation files (i.e. .md extension) are licensed under the Creative Common License 4.0