|
|
@@ -16,19 +16,19 @@
|
|
|
(sent a NOTIFY request) and AVPs are not returned correctly to previous
|
|
|
one.</para></listitem>
|
|
|
|
|
|
- <listitem><para>There are some standard
|
|
|
- incompliances in presence modules, often caused by standard ambiguity
|
|
|
- or contradiction or by partial implementation only. Please refer to specific
|
|
|
+ <listitem><para>There are some standard incompliances in presence modules,
|
|
|
+ often caused by standard ambiguity or contradiction or by partial
|
|
|
+ implementation only. Please refer to specific
|
|
|
module documentation in such situations.</para></listitem>
|
|
|
<listitem><para>SIP clients often use broken data, not corresponding with
|
|
|
- data format specification. Look into specification in such cases (for
|
|
|
+ the data format specification. Look into the specification in such cases (for
|
|
|
example <xref linkend="pres_rfc_pidf"/>).</para></listitem>
|
|
|
|
|
|
- <listitem><para>XCAP module is incompatible with TLS module due to openssl
|
|
|
+ <listitem><para>The XCAP module is incompatible with TLS module due to Openssl
|
|
|
initialization!</para>
|
|
|
- <para>XCAP module uses libcurl for HTTP comunication and libcurl is using
|
|
|
- libopenssl internaly. But TLS module needs some extra openssl initialization which
|
|
|
- is not working when libcurl initializes openssl by itself.</para>
|
|
|
+ <para>XCAP module uses libcurl for HTTP communication and libcurl is using
|
|
|
+ libopenssl internaly. But the TLS module needs some extra openssl initialization which
|
|
|
+ is not working when libcurl initializes Openssl by itself.</para>
|
|
|
<para>Thanks Samuel ([email protected]) for pointing this out.</para></listitem>
|
|
|
|
|
|
</itemizedlist>
|
|
|
@@ -40,28 +40,27 @@
|
|
|
to do this or that, you can:
|
|
|
<itemizedlist>
|
|
|
<listitem><para>Try to search for similar problem in mailing lists on
|
|
|
- <ulink url="http://www.iptel.org/listsearch">iptel's page</ulink> or in
|
|
|
- <ulink url="http://lists.iptel.org/">list archives</ulink>.
|
|
|
+ <ulink url="http://www.sip-router.org/">SIP-router's main page</ulink> or in
|
|
|
+ <ulink url="http://lists.sip-router.org/cgi-bin/mailman/listinfo/">list archives</ulink>.
|
|
|
</para></listitem>
|
|
|
|
|
|
- <listitem><para>Send and email to <ulink
|
|
|
- url="mailto:s[email protected]">[email protected].org</ulink> for
|
|
|
+ <listitem><para>Send an email to <ulink
|
|
|
+ url="mailto:s[email protected]">[email protected].org</ulink> for
|
|
|
user related problem or
|
|
|
- <ulink url="mailto:s[email protected]">[email protected].org</ulink>
|
|
|
+ <ulink url="mailto:s[email protected]">[email protected].org</ulink>
|
|
|
for development related things. There are lots of interesting people on
|
|
|
- these lists with
|
|
|
- lots of experiences with SIP related stuff ;-).
|
|
|
+ these lists with lots of experiences with SIP related stuff ;-).
|
|
|
</para></listitem>
|
|
|
|
|
|
<listitem><para>For presence-only related things you can send me an email
|
|
|
directly to [email protected], but I highly prefer to use one of
|
|
|
mailing lists above because many people may be interested in the same
|
|
|
- problem you have.</para></listitem>
|
|
|
+ problem as you have.</para></listitem>
|
|
|
</itemizedlist>
|
|
|
</para>
|
|
|
|
|
|
<para>If you find a bug, please report it to our <ulink
|
|
|
-url="http://tracker.iptel.org/browse/SER">bug tracker</ulink>
|
|
|
+url="http://sip-router.org/tracker/">bug tracker</ulink>
|
|
|
or send an email to lists mentioned above or directly to me (email above).</para>
|
|
|
|
|
|
</section>
|
|
|
@@ -79,13 +78,13 @@ implemented or at least discussed.
|
|
|
|
|
|
<section><title>Searching a problem</title>
|
|
|
<para>Most of presence modules have <quote>trace</quote> method which can be
|
|
|
-invoked through SER's XML-RPC interface. Such method often dumps current status,
|
|
|
+invoked through SIP-router's management interface. Such methods often dumps current status,
|
|
|
existing subscriptions etc.
|
|
|
</para>
|
|
|
|
|
|
-<para>For calling XML-RPC methods you can simply use set of
|
|
|
-<application>ser_ctl</application> utilities (don't mess with deprecated serctl
|
|
|
-utility which is from unknown reason still installed with SER) or
|
|
|
+<para>For calling management methods you can simply use set of
|
|
|
+<application>sercmd</application> utilities (don't mess with deprecated serctl
|
|
|
+utility which is from unknown reason still installed with SIP-router) or
|
|
|
<application>binrpc</application> which uses more effective binary
|
|
|
protocol.</para>
|
|
|
|
|
|
@@ -98,7 +97,7 @@ protocol.</para>
|
|
|
| value |
|
|
|
+------------------------------------------------------------------------------------------------------------------------+
|
|
|
| registrar |
|
|
|
-| * sip:parf@test-domain.com (uid=parf) |
|
|
|
+| * sip:parf@example.com (uid=parf) |
|
|
|
| - tuples: |
|
|
|
| 6574y1y45d334fay6e9d7c60 contact='sip:[email protected]:6198;transport=udp' exp=976014034 status=0 published=0 (id=) |
|
|
|
| notes: |
|
|
|
@@ -107,14 +106,14 @@ protocol.</para>
|
|
|
| |
|
|
|
| - watchers: |
|
|
|
| - winfo watchers: |
|
|
|
-| sip:parf@test-domain.com status=1 exp=3545 |
|
|
|
+| sip:parf@example.com status=1 exp=3545 |
|
|
|
| - internal watchers: |
|
|
|
| - notes: |
|
|
|
| - extension elements: |
|
|
|
-| * sip:gozner@test-domain.com (uid=gozner) |
|
|
|
+| * sip:gozner@example.com (uid=gozner) |
|
|
|
| - tuples: |
|
|
|
| - watchers: |
|
|
|
-| sip:parf@test-domain.com status=1 exp=3562 |
|
|
|
+| sip:parf@example.com status=1 exp=3562 |
|
|
|
| - winfo watchers: |
|
|
|
| - internal watchers: |
|
|
|
| - notes: |
|
oej