moduleSER CVS as off January 18, 2007 Generic LDAPi module that handles connection to the ldap server and exports a simple API to interact with the server. Also, a LDAP authentication module that uses the API exported from the generic LDAP module. Save the patchfile to the directory with the file to patch, then (having that directory as current) use the command 'patch -p0 < patchfile.txt' LDAPi module configuration: modparam("ldap", "ldap_version", 3) <= optional, possible values are 1, 2 or 3 modparam("ldap", "ldap_url", "ldap://localhost:389") <== optional, defaults to "ldap://localhost", ldaps connections require ldap_version >= 2
Many modules have new selects. These are documented in the regular module documentation. Here are only major changes documented.
This is the page where YOU add your most wanted SERi features or modules! Please feel free to edit this page. See a more detailed list of wishlist items on the tracker (items on this wishlist will end up in the tracker when they are detailed enough to do actual coding). New groups can also be added. This wishlist is used for evaluating what to focus on for future releases. In order to know the general interest of a feature, you can also vote for features. Just add an * in parenthesis behind the feature, and please only add one... The acc_db module can be used to implement database based accounting of SIP transactionsi. The module uses the internal SERi database API and thus it can be used with any database supported by SER, such as mysql, postgres, dbtext, or flatstore. The accounting module works with SIP transactions. For every transactioni that is marked with a special flag the accounting module will extract some information from SIP request and associated responses and write it in the database. The accounted data contains all information that is necessary to calculate biling information, such as the URIi of the callee and caller, date and time of the SIP request arrival and so on. Because the module needs information from both the SIP request and final response, the module does not write anything in the database when an INVITE comes, for example, but all information accumulated from the INVITE and 200 OK to the INVITE will be written at once when 200 OK comes. The data from the INVITE and 200 OK is written in the database as single row and the row contains all information extracted from the SIP transaction.  |
Navigation |