rtpengine_faq.xml 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. <?xml version="1.0" encoding='ISO-8859-1'?>
  2. <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
  3. "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
  4. <!-- Include general documentation entities -->
  5. <!ENTITY % docentities SYSTEM "../../../docbook/entities.xml">
  6. %docentities;
  7. ]>
  8. <!-- Module FAQ -->
  9. <chapter>
  10. <title>&faqguide;</title>
  11. <qandaset defaultlabel="number">
  12. <qandaentry>
  13. <question>
  14. <para>How do I migrate from <quote>rtpproxy</quote> or <quote>rtpproxy-ng</quote> to
  15. <quote>rtpengine</quote>?</para>
  16. </question>
  17. <answer>
  18. <para>
  19. For the most part, only the names of the functions have changed, with
  20. <quote>rtpproxy</quote> in each name replaced with <quote>rtpengine</quote>.
  21. For example, <quote>rtpproxy_manage()</quote> has become
  22. <quote>rtpengine_manage()</quote>. A few name duplications have also been resolved,
  23. for example there is now a single <quote>rtpengine_delete()</quote> instead of
  24. <quote>unforce_rtp_proxy()</quote> and the identical <quote>rtpproxy_destroy()</quote>.
  25. </para>
  26. <para>
  27. The largest difference to the old module is how flags are passed to
  28. <quote>rtpengine_offer()</quote>, <quote>rtpengine_answer()</quote>,
  29. <quote>rtpengine_manage()</quote> and <quote>rtpengine_delete()</quote>. Instead of
  30. having a string of single-letter flags, they now take a string of space-separated
  31. items, with each item being either a single token (word) or a <quote>key=value</quote>
  32. pair.
  33. </para>
  34. <para>
  35. For example, if you had a call <quote>rtpproxy_offer("FRWOC+PS");</quote>, this would
  36. then become:
  37. </para>
  38. <programlisting>
  39. rtpengine_offer("force trust-address symmetric replace-origin replace-session-connection ICE=force RTP/SAVPF");
  40. </programlisting>
  41. <para>
  42. Finally, if you were using the second paramater (explicit media address) to any of
  43. these functions, this has been replaced by the <quote>media-address=...</quote>
  44. option within the first string of flags.
  45. </para>
  46. </answer>
  47. </qandaentry>
  48. <qandaentry>
  49. <question>
  50. <para>Where can I find more about &kamailio;?</para>
  51. </question>
  52. <answer>
  53. <para>
  54. Take a look at &kamailiohomelink;.
  55. </para>
  56. </answer>
  57. </qandaentry>
  58. <qandaentry>
  59. <question>
  60. <para>Where can I post a question about this module?</para>
  61. </question>
  62. <answer>
  63. <para>
  64. First at all check if your question was already answered on one of
  65. our mailing lists:
  66. </para>
  67. <itemizedlist>
  68. <listitem>
  69. <para>User Mailing List - &kamailiouserslink;</para>
  70. </listitem>
  71. <listitem>
  72. <para>Developer Mailing List - &kamailiodevlink;</para>
  73. </listitem>
  74. </itemizedlist>
  75. <para>
  76. E-mails regarding any stable &kamailio; release should be sent to
  77. &kamailiousersmail; and e-mails regarding development versions
  78. should be sent to &kamailiodevmail;.
  79. </para>
  80. <para>
  81. If you want to keep the mail private, send it to
  82. &kamailiohelpmail;.
  83. </para>
  84. </answer>
  85. </qandaentry>
  86. <qandaentry>
  87. <question>
  88. <para>How can I report a bug?</para>
  89. </question>
  90. <answer>
  91. <para>
  92. Please follow the guidelines provided at:
  93. &kamailiobugslink;.
  94. </para>
  95. </answer>
  96. </qandaentry>
  97. </qandaset>
  98. </chapter>