Presence_XML Module

Anca-Maria Vamanu

   voice-system.ro

Edited by

Anca-Maria Vamanu

   Copyright © 2007 voice-system.ro
   Revision History
   Revision $Revision: 8160 $ $Date: 2009-07-21 10:45:05 +0300
                              (Tue, 21 Jul 2009) $
     __________________________________________________________

   Table of Contents

   1. Admin Guide

        1.1. Overview
        1.2. Dependencies

              1.2.1. OpenSIPS Modules
              1.2.2. External Libraries or Applications

        1.3. Exported Parameters

              1.3.1. db_url(str)
              1.3.2. xcap_table(str)
              1.3.3. force_active (int)
              1.3.4. pidf_manipulation (int)
              1.3.5. integrated_xcap_server (int)
              1.3.6. xcap_server (str)
              1.3.7. pres_rules_auid (str)
              1.3.8. pres_rules_filename (str)

        1.4. Exported Functions
        1.5. Installation

   2. Developer Guide

   List of Examples

   1.1. Set db_url parameter
   1.2. Set xcap_table parameter
   1.3. Set force_active parameter
   1.4. Set pidf_manipulation parameter
   1.5. Set integrated_xcap_server parameter
   1.6. Set xcap_server parameter
   1.7. Set pres_rules_auid parameter
   1.8. Set pres_rules_filename parameter

Chapter 1. Admin Guide

1.1. Overview

   The 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 takes the xcap permission rule documents from
   xcap_table. The presence permission rules are interpreted
   according to the specifications in RFC 4745 and RFC 5025.

1.2. Dependencies

1.2.1. OpenSIPS Modules

   The following modules must be loaded before this module:
     * a database module.
     * presence.
     * signaling.
     * xcap_client.
       Only compulsory if not using an integrated xcap server (if
       'integrated_xcap_server' parameter is not set).

1.2.2. External Libraries or Applications

   The following libraries or applications must be installed
   before running OpenSIPS with this module loaded:
     * libxml-dev.

1.3. Exported Parameters

1.3.1. db_url(str)

   The database url.

   Default value is
   “mysql://opensips:opensipsrw@localhost/opensips”.

   Example 1.1. Set db_url parameter
...
modparam("presence_xml", "db_url", "dbdriver://username:password@dbhost/
dbname")
...

1.3.2. xcap_table(str)

   The name of the db table where XCAP documents are stored.

   Default value is “xcap”.

   Example 1.2. Set xcap_table parameter
...
modparam("presence_xml", "xcap_table", "xcaps")
...

1.3.3. 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”.

   Example 1.3. Set force_active parameter
...
modparam("presence_xml", "force_active", 1)
...

1.3.4. 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”.

   Example 1.4. Set pidf_manipulation parameter
...
modparam("presence_xml", "pidf_manipulation", 1)
...

1.3.5. integrated_xcap_server (int)

   This parameter is a flag for the type of XCAP server or servers
   used. If integrated ones, like XCAP-lite from AG Projects, with
   direct access to database table, 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.

   Otherwise, it uses xcap_client module to fetch documents from
   the XCAP servers with HTTP requests.

   Default value is “0”.

   Example 1.5. Set integrated_xcap_server parameter
...
modparam("presence_xml", "integrated_xcap_server", 1)
...

1.3.6. xcap_server (str)

   The address of the xcap servers used for storage. 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.

   Example 1.6. Set xcap_server parameter
...
modparam("presence_xml", "xcap_server", "xcap_server.example.org")
modparam("presence_xml", "xcap_server", "xcap_server.ag.org")
...

1.3.7. pres_rules_auid (str)

   This parameter should be configured if you are using the non
   integrated xcap mode and you need to use another pres-rules
   auid than the default 'pres-rules'.

   Example 1.7. Set pres_rules_auid parameter
...
modparam("presence_xml", "pres_rules_auid", "org.openmobilealliance.pres
-rules")
...

1.3.8. pres_rules_filename (str)

   This parameter should be configured if you are using the non
   integrated xcap mode and you need to configure another filename
   than the default 'index'.

   Example 1.8. Set pres_rules_filename parameter
...
modparam("presence_xml", "pres_rules_filename", "pres-rules")
...

1.4. Exported Functions

   None to be used in configuration file.

1.5. Installation

   The module requires 1 table in OpenSIPS database: xcap. The SQL
   syntax to create it can be found in presence-create.sql script
   in the database directories in the opensips/scripts folder. You
   can also find the complete database documentation on the
   project webpage,
   http://www.opensips.org/html/docs/db/db-schema-devel.html.

Chapter 2. Developer Guide

   The module exports no function to be used in other OpenSIPS
   modules.