trouble.xml 7.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE section PUBLIC '-//OASIS//DTD DocBook XML V4.2//EN'
  3. 'http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd'>
  4. <section><title>Tracing of trouble</title>
  5. <para>Sometimes it is needed to solve problems with presence related stuff...
  6. ;-)</para>
  7. <section id="pres.known_problems"><title>Known problems</title>
  8. <para>
  9. <itemizedlist>
  10. <listitem><para>AVPs might not work properly with presence. If you create
  11. AVPs they can disappear after call to handle_subscription or similar
  12. function. The reason is that from such functions is created new transaction
  13. (sent a NOTIFY request) and AVPs are not returned correctly to previous
  14. one.</para></listitem>
  15. <listitem><para>There are some standard incompliances in presence modules,
  16. often caused by standard ambiguity or contradiction or by partial
  17. implementation only. Please refer to specific
  18. module documentation in such situations.</para></listitem>
  19. <listitem><para>SIP clients often use broken data, not corresponding with
  20. the data format specification. Look into the specification in such cases (for
  21. example <xref linkend="pres_rfc_pidf"/>).</para></listitem>
  22. <listitem><para>The XCAP module is incompatible with TLS module due to Openssl
  23. initialization!</para>
  24. <para>XCAP module uses libcurl for HTTP communication and libcurl is using
  25. libopenssl internaly. But the TLS module needs some extra openssl initialization which
  26. is not working when libcurl initializes Openssl by itself.</para>
  27. <para>Thanks Samuel ([email protected]) for pointing this out.</para></listitem>
  28. </itemizedlist>
  29. </para>
  30. </section>
  31. <section><title>Reporting problems</title>
  32. <para>If you can not find the source of your problem or if you are not sure how
  33. to do this or that, you can:
  34. <itemizedlist>
  35. <listitem><para>Try to search for similar problem in mailing lists on
  36. <ulink url="http://www.sip-router.org/">SIP-router's main page</ulink> or in
  37. <ulink url="http://lists.sip-router.org/cgi-bin/mailman/listinfo/">list archives</ulink>.
  38. </para></listitem>
  39. <listitem><para>Send an email to <ulink
  40. url="mailto:[email protected]">[email protected]</ulink> for
  41. user related problem or
  42. <ulink url="mailto:[email protected]">[email protected]</ulink>
  43. for development related things. There are lots of interesting people on
  44. these lists with lots of experiences with SIP related stuff ;-).
  45. </para></listitem>
  46. <listitem><para>For presence-only related things you can send me an email
  47. directly to [email protected], but I highly prefer to use one of
  48. mailing lists above because many people may be interested in the same
  49. problem as you have.</para></listitem>
  50. </itemizedlist>
  51. </para>
  52. <para>If you find a bug, please report it to our <ulink
  53. url="http://sip-router.org/tracker/">bug tracker</ulink>
  54. or send an email to lists mentioned above or directly to me (email above).</para>
  55. </section>
  56. <section><title>New features</title>
  57. <para>There is a list of features to be implemented in my TODO list. I will put them
  58. into our bug tracker as soon as I will have more time for it. ;-)
  59. </para>
  60. <para>If you are interested in a feature you can search or ask in mailing lists
  61. or you can add your feature into bug tracker and might be that it will be
  62. implemented or at least discussed.
  63. </para>
  64. </section> <!-- new features -->
  65. <section><title>Searching a problem</title>
  66. <para>Most of presence modules have <quote>trace</quote> method which can be
  67. invoked through SIP-router's management interface. Such methods often dumps current status,
  68. existing subscriptions etc.
  69. </para>
  70. <para>For calling management methods you can simply use set of
  71. <application>sercmd</application> utilities (don't mess with deprecated serctl
  72. utility which is from unknown reason still installed with SIP-router) or
  73. <application>binrpc</application> which uses more effective binary
  74. protocol.</para>
  75. <example id="searching_problem_trace">
  76. <title>Using ser_ctl for debugging problems</title>
  77. <para>
  78. <programlisting>
  79. <userinput>kubartv@~/src/serctl$ ./ser_rpc -t pa.trace 2</userinput>
  80. <![CDATA[+------------------------------------------------------------------------------------------------------------------------+
  81. | value |
  82. +------------------------------------------------------------------------------------------------------------------------+
  83. | registrar |
  84. | * sip:[email protected] (uid=parf) |
  85. | - tuples: |
  86. | 6574y1y45d334fay6e9d7c60 contact='sip:[email protected]:6198;transport=udp' exp=976014034 status=0 published=0 (id=) |
  87. | notes: |
  88. | extension elements: |
  89. | status extension elements: |
  90. | |
  91. | - watchers: |
  92. | - winfo watchers: |
  93. | sip:[email protected] status=1 exp=3545 |
  94. | - internal watchers: |
  95. | - notes: |
  96. | - extension elements: |
  97. | * sip:[email protected] (uid=gozner) |
  98. | - tuples: |
  99. | - watchers: |
  100. | sip:[email protected] status=1 exp=3562 |
  101. | - winfo watchers: |
  102. | - internal watchers: |
  103. | - notes: |
  104. | - extension elements: |
  105. | presentity count: 2 |
  106. +------------------------------------------------------------------------------------------------------------------------+
  107. ]]></programlisting>
  108. </para>
  109. </example>
  110. </section>
  111. </section>