Presence_Profile Module

MihÃ¡ly MÃ©szÃ¡ros

   <misi@niif.hu>

Edited by

MÃ©szÃ¡ros MihÃ¡ly

   <misi@niif.hu>

Edited by

Alex Balashov

   <abalashov@evaristesys.com>

   Copyright © 2011 MÃ©szÃ¡ros MihÃ¡ly
     __________________________________________________________________

   Table of Contents

   1. Admin Guide

        1. Overview
        2. Dependencies

              2.1. Kamailio Modules
              2.2. External Libraries or Applications

        3. Exported Parameters
        4. Exported Functions

Chapter 1. Admin Guide

   Table of Contents

   1. Overview
   2. Dependencies

        2.1. Kamailio Modules
        2.2. External Libraries or Applications

   3. Exported Parameters
   4. Exported Functions

1. Overview

   The module extends the presence server implementation, providing the
   ability to handle the 'ua-profile' event. When a user agent subscribes
   to ua-profile event for its own AoR, it retrieves the profile data
   document from the body of a NOTIFY request.

   The profile data document format is usually specific to the user agent.
   Such documents have to be built and added to presentity table by either
   the admin or a third party application.

   Warning: When you add a profile data document (i.e. the user agent's
   provisioning config) to the presentity table, you must make sure that
   you set the presentity table expires field to a time value far in the
   future.

   Read more about SIP user agent configuration framework in RFC6080:
   http://tools.ietf.org/html/rfc6080.

2. Dependencies

   2.1. Kamailio Modules
   2.2. External Libraries or Applications

2.1. Kamailio Modules

   The following modules must be loaded before this module:
     * presence.

2.2. External Libraries or Applications

   None.

3. Exported Parameters

   None.

4. Exported Functions

   None to be used in configuration file.
