This module offers the functionality of a presence user agent client, sending SUBSCRIBE and PUBLISH SIP messages. It's a core part of Kamailio's SIP presence package, implementing SIMPLE and various shared line appearance implementations. It can be used with the following modules: pua_rpc, pua_usrloc, pua_bla, pua_dialoginfo, pua_reginfo and pua_xmpp. The pua_rpc module offers the possibility to publish any kind of information via the RPC transport. The pua_usrloc module calls a function exported by pua modules to publish elementary presence information, such as basic status "open" or "closed", for clients that do not implement client-to-server presence. Through pua_bla , BRIDGED LINE APPEARANCE features are added to Kamailio The pua_xmpp module represents a gateway between SIP and XMPP, so that jabber and SIP clients can exchange presence information. The pua_reginfo modules presents registration information from the usrloc module using the reginfo event package. The module supports 2 modes of operation. In the first a cache is used to store the presentity list and writes to database on timer to be able to recover upon restart. The presence is kept in-memory during run-time. The second is a database only mode where the presentity list is stored purely in a database, allowing both scalability and resilience.
| Parámetro | Tipo | Descripción |
|---|---|---|
| hash_size | int | 3.2. db_url (str) 3.3. db_table (str) 3.4. min_expires (int) 3.5. default_expires (int) 3.6. update_period (int) 3.7. outbound_proxy (str) 3.8. dlginfo_increase_version (int) 3.9. reginfo_increase_ver |
| db_url | str | 3.3. db_table (str) 3.4. min_expires (int) 3.5. default_expires (int) 3.6. update_period (int) 3.7. outbound_proxy (str) 3.8. dlginfo_increase_version (int) 3.9. reginfo_increase_version (int) 3.10. d |
| db_table | str | 3.4. min_expires (int) 3.5. default_expires (int) 3.6. update_period (int) 3.7. outbound_proxy (str) 3.8. dlginfo_increase_version (int) 3.9. reginfo_increase_version (int) 3.10. db_mode (int) 3.11. d |
| min_expires | int | 3.5. default_expires (int) 3.6. update_period (int) 3.7. outbound_proxy (str) 3.8. dlginfo_increase_version (int) 3.9. reginfo_increase_version (int) 3.10. db_mode (int) 3.11. db_table_lock_write (int |
| default_expires | int | 3.6. update_period (int) 3.7. outbound_proxy (str) 3.8. dlginfo_increase_version (int) 3.9. reginfo_increase_version (int) 3.10. db_mode (int) 3.11. db_table_lock_write (integer) 3.12. check_remote_co |
| update_period | int | 3.7. outbound_proxy (str) 3.8. dlginfo_increase_version (int) 3.9. reginfo_increase_version (int) 3.10. db_mode (int) 3.11. db_table_lock_write (integer) 3.12. check_remote_contact (int) 3.13. fetch_r |
| outbound_proxy | str | 3.8. dlginfo_increase_version (int) 3.9. reginfo_increase_version (int) 3.10. db_mode (int) 3.11. db_table_lock_write (integer) 3.12. check_remote_contact (int) 3.13. fetch_rows (integer) |
| dlginfo_increase_version | int | 3.9. reginfo_increase_version (int) 3.10. db_mode (int) 3.11. db_table_lock_write (integer) 3.12. check_remote_contact (int) 3.13. fetch_rows (integer) |
| reginfo_increase_version | int | 3.10. db_mode (int) 3.11. db_table_lock_write (integer) 3.12. check_remote_contact (int) 3.13. fetch_rows (integer) |
| db_mode | int | 3.11. db_table_lock_write (integer) 3.12. check_remote_contact (int) 3.13. fetch_rows (integer) |
| db_table_lock_write | integer | 3.12. check_remote_contact (int) 3.13. fetch_rows (integer) |
| check_remote_contact | int | 3.13. fetch_rows (integer) |
| fetch_rows | integer | 3.1. hash_size (int) |
| hash_size | int | The size of the hash table used for storing SUBSCRIBE and PUBLISH information. This parameter will be used as the power of 2 when computing table size. |
| db_url | str | Database url. |
| db_table | str | The name of the database table. |
| min_expires | int | The inferior expires limit for both Publish and Subscribe. |
| default_expires | int | The default expires value used in case this information is not provisioned. |
| update_period | int | The interval at which the information in database and hash table should be updated. In the case of the hash table updating means deleting expired messages. Setting a value less than or equal to zero, |
| outbound_proxy | str | SIP URI of outbound proxy to be used when sending PUBLISH requests if no outbound proxy is given in outbound_proxy field of struct publ_info. |
| dlginfo_increase_version | int | When sending PUBLISH messages for Event: dialog, the body contains an XML document according to RFC 4235. This XML document contains a version attribute to easily detect changes in the dialog state. B |
| reginfo_increase_version | int | When sending PUBLISH messages for Event: reg, the body contains an XML document according to RFC 4235(?). This XML document contains a version attribute to easily detect changes in the registration st |
| db_mode | int | The module supports 2 modes of operation, high speed memory based storage (mode 0), and database only (mode 2) where all data is stored in a database, allowing scalability at the expense of speed. Mod |
| db_table_lock_write | integer | Enable (=1) or disable (=0) the Locks for table during a transaction. Locking only the "current" table causes problems with a MySQL-Databases in "DB-Only" mode. |
| check_remote_contact | int | When sending a SUBSCRIBE check that the remote contact matches the one in the stored dialog or not. If the remote contact is checked and does not match the one in the stored dialog then the dialog is |
| fetch_rows | integer | Number of rows to be loaded in one step from database. |
4.1. pua_update_contact()
The remote target can be updated by the Contact of a subsequent in dialog request. In the PUA watcher case (sending a SUBSCRIBE messages), this means that the remote target for the following Subscribe messages can be updated at any time by the contac
Copyright © 2006 Voice Sistem SRL
