name mode size
..
doc 040000
ChangeLog 100644 8.06kB
Makefile 100644 699B
README 100644 5.01kB
async_auth.c 100644 3.28kB
async_auth.h 100644 246B
auth.c 100644 2.49kB
auth.h 100644 571B
dlist.c 100644 5.18kB
dlist.h 100644 1.89kB
extension_elements.c 100644 6.81kB
extension_elements.h 100644 741B
hslot.c 100644 2.42kB
hslot.h 100644 1.89kB
message.c 100644 2.27kB
message.h 100644 142B
mimetypes.c 100644 3.27kB
mimetypes.h 100644 353B
notify.c 100644 15.03kB
notify.h 100644 1.44kB
offline_winfo.c 100644 12.17kB
offline_winfo.h 100644 1.63kB
pa_mod.c 100644 20.04kB
pa_mod.h 100644 3.57kB
paerrno.c 100644 1.11kB
paerrno.h 100644 2.42kB
pdomain.c 100644 6.76kB
pdomain.h 100644 3.04kB
pres_notes.c 100644 6.63kB
pres_notes.h 100644 605B
pres_timer.c 100644 7.37kB
presentity.c 100644 14.08kB
presentity.h 100644 7.1kB
ptime.c 100644 1.16kB
ptime.h 100644 1.22kB
publish.c 100644 12.72kB
publish.h 100644 1.59kB
qsa_interface.c 100644 7.94kB
qsa_interface.h 100644 468B
reply.c 100644 6.46kB
reply.h 100644 1.22kB
rpc.c 100644 8.83kB
rpc.h 100644 1.15kB
status_query.c 100644 1.76kB
status_query.h 100644 181B
subscribe.c 100644 14.56kB
subscribe.h 100644 1.68kB
trace.h 100644 304B
tuple.c 100644 12.46kB
tuple.h 100644 1.68kB
tuple_extensions.c 100644 4.76kB
tuple_extensions.h 100644 740B
tuple_notes.c 100644 3.8kB
tuple_notes.h 100644 660B
watcher.c 100644 18.15kB
watcher.h 100644 4.96kB
winfo_doc.c 100644 5.35kB
winfo_doc.h 100644 363B
README
pa Module Jan Janak FhG FOKUS Edited by Jan Janak Jamey Hicks Copyright � 2003 FhG FOKUS _________________________________________________________ Table of Contents 1. User's Guide 1.1. Overview 1.2. Dependencies 1.2.1. SER Modules 1.2.2. External Libraries or Applications 1.3. Exported Parameters 1.3.1. default_expires (integer) 1.3.2. default_priority_percentage (integer) 1.3.3. db_url (string) 1.3.4. pa_domain (string) 1.4. Exported Functions 1.4.1. handle_subscription(domain) 1.4.2. handle_publish(domain) 1.4.3. pa_handle_registration(domain) 2. Developer's Guide 3. Frequently Asked Questions List of Examples 1-1. Set default_expires parameter 1-2. handle_subscription usage _________________________________________________________ Chapter 1. User's Guide 1.1. Overview This module implements a presence server, i.e. entity that receives SUBSCRIBE messages and sends NOTIFY when presence status of a user changes. Currently the presence server can be connected to registrar and jabber module so SIP users can see presence of jabber users. This module also acts as a presence aggregator, receiving PUBLISH messages to update extended status and generating NOTIFY messages. This module currently cannot work as a B2BUA, i.e. it cannot subscribe to presence of users using SIP. We are currently working on that feature. _________________________________________________________ 1.2. Dependencies 1.2.1. SER Modules The following modules must be loaded before this module: * No dependencies on other SER modules. _________________________________________________________ 1.2.2. External Libraries or Applications The following libraries or applications must be installed before running SER with this module loaded: * None. _________________________________________________________ 1.3. Exported Parameters 1.3.1. default_expires (integer) Default expires value to be used when the client doesn't supply one (in seconds). Default value is "3600". Example 1-1. Set default_expires parameter ... modparam("pa", "default_expires", 3600) ... 1.3.2. default_priority_percentage (integer) Default priority value to be used when not included in a PUBLISH message, expressed as a percentage. Default value is "50". Example 1-2. Set default_expires parameter ... modparam("pa", "default_expires", 50) ... 1.3.3. db_url (string) URL of the database containing presence-agent data. Example 1-3. Set db_url parameter ... modparam("pa", "db_url", "mysql:ser:heslo@localhost/ser") ... 1.3.4. pa_domain (string) Hostname of xcap server associated with presence agent. Example 1-4. Set default_expires parameter ... modparam("pa", "pa_domain", "ser.example.com") ... _________________________________________________________ 1.4. Exported Functions 1.4.1. handle_subscription(domain) This function processes SUBSCRIBE and generates NOTIFY. Meaning of the parameters is as follows: * domain - This can be either "registrar" or "jabber". Example 1-5. handle_subscription usage ... if (method=="SUBSCRIBE") { if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); }; handle_subscription("registrar"); break; }; ... 1.4.2. handle_publish(domain) This function processes PUBLISH and generates NOTIFY. Meaning of the parameters is as follows: * domain - This can be either "registrar" or "jabber". Example 1-6. handle_publish usage ... if (method=="PUBLISH") { if (!t_newtran()) { log(1, "newtran error\n"); sl_reply_error(); }; handle_publish("registrar"); break; }; ... 1.4.3. pa_handle_registration(domain) This function is no longer used. _________________________________________________________ Chapter 2. Developer's Guide The module does not provide any sort of API to use in other SER modules. _________________________________________________________ Chapter 3. Frequently Asked Questions 3.1. Where can I find more about SER? 3.2. Where can I post a question about this module? 3.3. How can I report a bug? 3.1. Where can I find more about SER? Take a look at http://iptel.org/ser. 3.2. Where can I post a question about this module? First at all check if your question was already answered on one of our mailing lists: * http://mail.iptel.org/mailman/listinfo/serusers * http://mail.iptel.org/mailman/listinfo/serdev E-mails regarding any stable version should be sent to <serusers@iptel.org> and e-mail regarding development versions or CVS snapshots should be send to <serdev@iptel.org>. 3.3. How can I report a bug? Please follow the guidelines provided at: http://iptel.org/ser/bugs