pua_publishpua_subscribepua_publish FIFO exampleThe pua_mi offers the possibility to publish presence information and subscribe to presence information via MI transports.
Using this module you can create independent applications/scripts to publish not sip-related information (e.g., system resources like CPU-usage, memory, number of active subscribers ...). Also, this module allows non-SIP speaking applications to subscribe presence information kept in a SIP presence server.
The following libraries or applications must be installed before running OpenSER with this module loaded:
none
pua_publishCommand parameters:
presentity_uri - e.g. sip:system@openser.org
expires - Relative expires time in seconds (e.g. 3600).
event package - Event package that is target of published information (e.g. presence).
content type - Content type of published information (e.g. application/pidf+xml) or . if no information is enclosed.
ETag - ETag that publish should match or . if no ETag is given.
body - The body of the publish request containing published information or missing if no published information. It has to be a single line for FIFO transport.
Example 1-1. pua_publish FIFO example
... :pua_publish:fifo_test_reply sip:system@openser.org 3600 presence application/pidf+xml . <?xml version='1.0'?><presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' entity='system@openser.org'><tuple id='0x81475a0'><status><basic>open</basic></status></tuple><dm:person id='pdd748945'><rpid:activities><rpid:away/>away</rpid:activities><dm:note>CPU:16 MEM:476</dm:note></dm:person></presence>
pua_subscribeCommand parameters:
presentity_uri - e.g. sip:presentity@openser.org
watcher_uri - e.g. sip:watcher@openser.org
event package
expires - Relative time in seconds for the desired validity of the subscription.
Take a look at http://www.openser-project.org/.
First at all check if your question was already answered on one of our mailing lists:
User Mailing List - http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
Developer Mailing List - http://lists.openser-project.org/cgi-bin/mailman/listinfo/devel
E-mails regarding any stable OpenSER release should be sent to
<users@lists.openser-project.org> and e-mails regarding development versions
should be sent to <devel@lists.openser-project.org>.
If you want to keep the mail private, send it to
<team@lists.openser-project.org>.
Please follow the guidelines provided at: http://sourceforge.net/tracker/?group_id=139143.