Module: sip-router Branch: master Commit: 37397c5ee04b91bf75cb92857d5bb47ce8f95a75 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=37397c5… Author: Daniel-Constantin Mierla &lt;miconda(a)gmail.com&gt; Committer: Daniel-Constantin Mierla &lt;miconda(a)gmail.com&gt; Date: Thu Nov 17 15:22:33 2011 +0100 presence_profile: use ulink tag for http url to get it as link in html format - added few more details about the functionality provided by the module, based on summary of rfc6080 --- modules_k/presence_profile/README | 30 +++++++++++-------- .../doc/presence_profile_admin.xml | 20 +++++++++---- 2 files changed, 31 insertions(+), 19 deletions(-) diff --git a/modules_k/presence_profile/README b/modules_k/presence_profile/README index 1d59539..ddf8e7a 100644 --- a/modules_k/presence_profile/README +++ b/modules_k/presence_profile/README @@ -1,16 +1,16 @@ Presence_Profile Module -Mihály Mészáros +Mihály Mészáros &lt;misi(a)niif.hu&gt; Edited by -Mészáros Mihály +Mészáros Mihály &lt;misi(a)niif.hu&gt; - Copyright © 2011 Mészáros Mihály + Copyright � 2011 Mészáros Mihály __________________________________________________________________ Table of Contents @@ -41,18 +41,22 @@ Chapter 1. Admin Guide 1. Overview - The module does a very basic handling for ua-profile. You can subscribe - to ua-profile provisioning information if you add a provisioning - document to presentity table. + The module extends presence server implementation with ability of + handling ua-profile event. When an user agent subscribes to ua-profile + event for its own AoR, it will retrieve profile data document via body + of NOTIFY request. - Warning: When you add provisioning config to presentity table, then you - must make sure that you set the presentity table expires field to a - time value in long future + The profile data document format is usually specific per user agent, + such documents have to be built and added to presentity table by the + admin or a third party application. - If your user agent is subscribing to AoR and if the subscription event - is ua-profile, then it will receive provisioning data in the - notification body. Read more about sip user agent configuration - framework in RFC6080. http://tools.ietf.org/html/rfc6080 + Warning: When you add profile data document (i.e., user agent's + provisioning config) to presentity table, then you must make sure that + you set the presentity table expires field to a time value in long + future. + + Read more about SIP user agent configuration framework in RFC6080: + http://tools.ietf.org/html/rfc6080. 2. Dependencies diff --git a/modules_k/presence_profile/doc/presence_profile_admin.xml b/modules_k/presence_profile/doc/presence_profile_admin.xml index e1c026f..355159f 100644 --- a/modules_k/presence_profile/doc/presence_profile_admin.xml +++ b/modules_k/presence_profile/doc/presence_profile_admin.xml @@ -17,16 +17,24 @@ <section> <title>Overview</title> <para> - The module does a very basic handling for ua-profile. - You can subscribe to ua-profile provisioning information if you add a provisioning document to presentity table. + The module extends presence server implementation with ability of + handling ua-profile event. When an user agent subscribes to ua-profile + event for its own AoR, it will retrieve profile data document + via body of NOTIFY request. </para> <para> - Warning: When you add provisioning config to presentity table, then you must make sure - that you set the presentity table expires field to a time value in long future + The profile data document format is usually specific per user agent, such + documents have to be built and added to presentity table by the admin + or a third party application. </para> <para> - If your user agent is subscribing to AoR and if the subscription event is ua-profile, then it will receive provisioning data in the notification body. - Read more about sip user agent configuration framework in RFC6080. http://tools.ietf.org/html/rfc6080 + Warning: When you add profile data document (i.e., user agent's + provisioning config) to presentity table, then you must make sure that you + set the presentity table expires field to a time value in long future. + </para> + <para> + Read more about SIP user agent configuration framework in RFC6080: + <ulink url="http://tools.ietf.org/html/rfc6080">http://tools.ietf.org…c6080</ulink>. </para> </section>