db_url
(str)xcap_table
(str)force_active
(int)pidf_manipulation
(int)integrated_xcap_server
(int)server_address
(str)db_url
parameterxcap_table
parameterforce_active
parameterpidf_manipulation
parameterintegrated_xcap_server
parameterxcap_server
parameterThe module does specific handling for notify-subscribe events using xml bodies. It is used with the general event handling module, presence. It constructs and adds 3 events to it: presence, presence.winfo, dialog;sla.
This module uses xcap_table with permission rules to deal with authorization rules for presence.
The following modules must be loaded before this module:
a database module.
presence.
sl.
xcap_client.
Only compulsory if not using an integrated xcap server (if 'integrated_xcap_server' parameter is not set).
The following libraries or applications must be installed before running OpenSER with this module loaded:
libxml.
xcap_table
(str)The name of the database table where XCAP documents are stored.
Default value is "xcap".
force_active
(int)This parameter is used for permissions when handling Subscribe messages. If set to 1, subscription state is considered active and the presentity is not queried for permissions (should be set to 1 if not using an XCAP server). Otherwise, the XCAP server is queried and the subscription states is according to user defined permission rules. If no rules are defined for a certain watcher, the subscriptions remains in pending state and the Notify sent will have no body.
Note: When switching from one value to another, the watchers table must be emptied.
Default value is "0".
pidf_manipulation
(int)Setting this parameter to 1 enables the features described in RFC 4827. It gives the possibility to have a permanent state notified to the users even in the case in which the phone is not online. The presence document is taken from the XCAP server and aggregated together with the other presence information, if any exist, for each Notify that is sent to the watchers. It is also possible to have information notified even if not issuing any Publish (useful for services such as email, SMS, MMS).
Default value is "0".
integrated_xcap_server
(int)This parameter is a flag for the type of XCAP server or servers used. If the XCAP server is integrated with OpenSER presence_XML module and access the same database tables directly, like the XCAP-lite server from AG Projects, the parameter should be set to a positive value. Apart from updating in xcap table, the integrated server must send an MI command refershWatchers [pres_uri] [event] when a user modifies a rules document, to instruct the presence_xml module to update states from the database and, if needed, send NOTIFY updates.
Otherwise, it uses xcap_client module to fetch documents from the XCAP servers with HTTP requests.
Default value is "0".
server_address
(str)This parameter is compulsory if the integrated_xcap_server parameter is not set. It can be set more that once, to construct an address list of trusted XCAP servers.
The module requires one table in OpenSER database: "xcap". The SQL syntax to create it can be found in presence-create.sql script in the database directories in the openser/scripts folder. You can also find the complete database documentation on the project webpage, http://www.openser-project.org/docs/db-tables/openser-db-devel.html.
Take a look at http://www.openser-project.org/.
First at all check if your question was already answered on one of our mailing lists:
User Mailing List - http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Developer Mailing List - http://lists.openser-project.org/cgi-bin/mailman/listinfo/devel
E-mails regarding any stable OpenSER release should be sent to
<users@lists.openser-project.org>
and e-mails regarding development versions
should be sent to <devel@lists.openser-project.org>
.
If you want to keep the mail private, send it to
<team@lists.openser-project.org>
.
Please follow the guidelines provided at: http://sourceforge.net/tracker/?group_id=139143.