Sip subscribe rls » History » Version 7
Adrian Georgescu, 10/26/2008 06:46 PM
1 | 1 | Adrian Georgescu | == sip_subscribe_rls == |
---|---|---|---|
2 | |||
3 | To use this script you must to have a valid [wiki:configuration_file configuration file]. |
||
4 | |||
5 | === Description === |
||
6 | |||
7 | 5 | Adrian Georgescu | [[Image(http://www.openxcap.org/chrome/site/SIMPLE-RLS-services.png, align=right, nolink)]] |
8 | 4 | Adrian Georgescu | |
9 | 7 | Adrian Georgescu | A Resource List Server (RLS) services application is a Session Initiation Protocol (SIP) application whereby a server receives SIP SUBSCRIBE requests for resource, and generates subscriptions towards a resource list. |
10 | |||
11 | This script implements sending SUBSCRIBE to a RLS server and receiving NOTIFY messages from it. |
||
12 | 6 | Adrian Georgescu | |
13 | 2 | Adrian Georgescu | Source code: [source:scripts/sip_subscribe_rls.py scripts/sip_subscribe_rls.py] |
14 | 1 | Adrian Georgescu | |
15 | {{{ |
||
16 | 3 | Adrian Georgescu | adigeo@ag-imac3:~$sip_subscribe_rls -h |
17 | Usage: sip_subscribe_rls [options] [target-user@target-domain.com] |
||
18 | 1 | Adrian Georgescu | |
19 | This script will SUBSCRIBE to the presence event published by the specified |
||
20 | 3 | Adrian Georgescu | SIP target assuming it is a resource list handled by a RLS server. The RLS |
21 | server will then SUBSCRIBE in behalf of the account, collect NOTIFYs with the |
||
22 | presence information of the recipients and provide periodically aggregated |
||
23 | NOTIFYs back to the subscriber. If a target address is not specified, it will |
||
24 | subscribe to the account's own address. It will then interprete PIDF bodies |
||
25 | 1 | Adrian Georgescu | contained in NOTIFYs and display their meaning. The program will un-SUBSCRIBE |
26 | and quit when CTRL+D is pressed. |
||
27 | |||
28 | Options: |
||
29 | -h, --help show this help message and exit |
||
30 | -a NAME, --account-name=NAME |
||
31 | The account name from which to read account settings. |
||
32 | Corresponds to section Account_NAME in the |
||
33 | configuration file. If not supplied, the section |
||
34 | Account will be read. |
||
35 | --sip-address=SIP_ADDRESS |
||
36 | SIP address of the user in the form user@domain |
||
37 | -p PASSWORD, --password=PASSWORD |
||
38 | Password to use to authenticate the local account. |
||
39 | This overrides the setting from the config file. |
||
40 | -n DISPLAY_NAME, --display-name=DISPLAY_NAME |
||
41 | Display name to use for the local account. This |
||
42 | overrides the setting from the config file. |
||
43 | -e EXPIRES, --expires=EXPIRES |
||
44 | "Expires" value to set in SUBSCRIBE. Default is 300 |
||
45 | seconds. |
||
46 | -o IP[:PORT], --outbound-proxy=IP[:PORT] |
||
47 | Outbound SIP proxy to use. By default a lookup of the |
||
48 | domain is performed based on SRV and A records. This |
||
49 | overrides the setting from the config file. |
||
50 | -c CONTENT_TYPE, --content-type=CONTENT_TYPE |
||
51 | "Content-Type" the UA expects to receving in a NOTIFY |
||
52 | for this subscription. For the known events this does |
||
53 | not need to be specified, but may be overridden". |
||
54 | -s, --trace-sip Dump the raw contents of incoming and outgoing SIP |
||
55 | messages (disabled by default). |
||
56 | -l, --log-pjsip Print PJSIP logging output (disabled by default). |
||
57 | }}} |