Anca-Maria Vamanu
- Copyright © 2007 Voice Sistem SRL
+ Copyright © 2007 Voice Sistem SRL
__________________________________________________________________
Table of Contents
The database url.
- Default value is “mysql://openser:openserrw@localhost/openser”.
+ Default value is "mysql://kamailio:kamailiorw@localhost/kamailio".
Example 1.1. Set db_url parameter
...
same time. This parameter enables each server to have its own (possibly
local) rls_presentity table.
- Default value is a mirror of the “db_url” setting.
+ Default value is a mirror of the "db_url" setting.
Example 1.2. Set rlpres_db_url parameter
...
The xcap database url. This parameter only needs to be specified if the
rls db and integerated xcap server db have different urls.
- Default value is a mirror of the “db_url” setting.
+ Default value is a mirror of the "db_url" setting.
Example 1.3. Set xcap_db_url parameter
...
in a database, allowing scalability at the expense of speed. Mode 1 is
reserved.
- Default value is “0”
+ Default value is "0"
Example 1.4. Set db_mode parameter
...
the name of the table must be the same as the one set for the
xcap_client module.
- Default value is “xcap”.
+ Default value is "xcap".
Example 1.5. Set xcap_table parameter
...
The name of the db table where resource lists subscription information
is stored.
- Default value is “rls_watchers”.
+ Default value is "rls_watchers".
Example 1.6. Set rlsubs_table parameter
...
The name of the db table where notified event specific information is
stored.
- Default value is “rls_presentity”.
+ Default value is "rls_presentity".
Example 1.7. Set rlpres_table parameter
...
The period at which to check for expired information. 0 means do not
check.
- Default value is “100”.
+ Default value is "100".
Example 1.8. Set clean_period parameter
...
rls_watchers on different timeouts. This is useful when they are in
different databases.
- Default value is “-1”.
+ Default value is "-1".
Example 1.9. Set rlpres_clean_period parameter
...
presence state of the subscribed list or watcher information within
this many seconds of a change occurring.
- Default value is “5”.
+ Default value is "5".
Example 1.10. Set waitn_time parameter
...
Separate notifier processes are only run when db_mode is 2 (DB only
mode).
- Default value is “10”.
+ Default value is "10".
Example 1.11. Set notifier_poll_rate parameter
...
Separate notifier processes are only run when db_mode is 2 (DB only
mode).
- Default value is “1”.
+ Default value is "1".
Example 1.12. Set notifier_processes parameter
...
The maximum accepted expires for a subscription to a list.
- Default value is “7200”.
+ Default value is "7200".
Example 1.13. Set max_expires parameter
...
seconds ago are deleted from the database. Negative offsets are treated
as though an offset of zero was specifed.
- Default value is “0”.
+ Default value is "0".
Example 1.14. Set expires_offset parameter
...
This parameter will be used as the power of 2 when computing table
size.
- Default value is “9 (512)”.
+ Default value is "9 (512)".
Example 1.15. Set hash_size parameter
...
The address of the xcap server.
- Default value is “NULL”.
+ Default value is "NULL".
Example 1.16. Set hash_size parameter
...
This parameter should be set if only integrated xcap servers are used
to store resource lists.
- Default value is “0”.
+ Default value is "0".
Example 1.17. Set integrated_xcap_server parameter
...
same machine, to call handle_subscribe on the message causing this
code.
- Default value is “0”.
+ Default value is "0".
Example 1.18. Set to_presence_code parameter
...
should also be handled by RLS they should be added using this
parameter. It can be set more than once.
- Default value is “"presence"”.
+ Default value is ""presence"".
Example 1.19. Set rls_event parameter
...
The SIP address where to send RLS subscriptions (outbound proxy address
as SIP URI).
- Default value is “NULL”.
+ Default value is "NULL".
Example 1.20. Set outbound_proxy parameter
...
4.2. rls_handle_notify()
4.3. rls_update_subs(uri, event)
-4.1. rls_handle_subscribe([watcher_uri])
+4.1. rls_handle_subscribe([watcher_uri])
This function detects if a Subscribe message should be handled by RLS.
If not it replies with the configured to_presence_code. If it is, it
...
-4.2. rls_handle_notify()
+4.2. rls_handle_notify()
This function can be used from REQUEST_ROUTE.
rls_handle_notify();
...
-4.3. rls_update_subs(uri, event)
+4.3. rls_update_subs(uri, event)
This function can be used in configuration to trigger updates to
resource list subscriptions (for example, after the contents of a
5.1. rls_cleanup
-5.1. rls_cleanup
+5.1. rls_cleanup
Manually triggers the cleanup functions forthe rls_watchers and
rls_presentity tables. Useful if you have set clean_period to zero or
projects / sip-router / commitdiff