123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103 |
- <?xml version="1.0" encoding='ISO-8859-1'?>
- <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
- "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
- <!-- Include general documentation entities -->
- <!ENTITY % docentities SYSTEM "../../../docbook/entities.xml">
- %docentities;
- ]>
- <!-- Module FAQ -->
- <chapter>
- <title>&faqguide;</title>
- <qandaset defaultlabel="number">
- <qandaentry>
- <question>
- <para>How do I migrate from <quote>rtpproxy</quote> or <quote>rtpproxy-ng</quote> to
- <quote>rtpengine</quote>?</para>
- </question>
- <answer>
- <para>
- For the most part, only the names of the functions have changed, with
- <quote>rtpproxy</quote> in each name replaced with <quote>rtpengine</quote>.
- For example, <quote>rtpproxy_manage()</quote> has become
- <quote>rtpengine_manage()</quote>. A few name duplications have also been resolved,
- for example there is now a single <quote>rtpengine_delete()</quote> instead of
- <quote>unforce_rtp_proxy()</quote> and the identical <quote>rtpproxy_destroy()</quote>.
- </para>
- <para>
- The largest difference to the old module is how flags are passed to
- <quote>rtpengine_offer()</quote>, <quote>rtpengine_answer()</quote>,
- <quote>rtpengine_manage()</quote> and <quote>rtpengine_delete()</quote>. Instead of
- having a string of single-letter flags, they now take a string of space-separated
- items, with each item being either a single token (word) or a <quote>key=value</quote>
- pair.
- </para>
- <para>
- For example, if you had a call <quote>rtpproxy_offer("FRWOC+PS");</quote>, this would
- then become:
- </para>
- <programlisting>
- rtpengine_offer("force trust-address symmetric replace-origin replace-session-connection ICE=force RTP/SAVPF");
- </programlisting>
- <para>
- Finally, if you were using the second paramater (explicit media address) to any of
- these functions, this has been replaced by the <quote>media-address=...</quote>
- option within the first string of flags.
- </para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>Where can I find more about &kamailio;?</para>
- </question>
- <answer>
- <para>
- Take a look at &kamailiohomelink;.
- </para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>Where can I post a question about this module?</para>
- </question>
- <answer>
- <para>
- First at all check if your question was already answered on one of
- our mailing lists:
- </para>
- <itemizedlist>
- <listitem>
- <para>User Mailing List - &kamailiouserslink;</para>
- </listitem>
- <listitem>
- <para>Developer Mailing List - &kamailiodevlink;</para>
- </listitem>
- </itemizedlist>
- <para>
- E-mails regarding any stable &kamailio; release should be sent to
- &kamailiousersmail; and e-mails regarding development versions
- should be sent to &kamailiodevmail;.
- </para>
- <para>
- If you want to keep the mail private, send it to
- &kamailiohelpmail;.
- </para>
- </answer>
- </qandaentry>
- <qandaentry>
- <question>
- <para>How can I report a bug?</para>
- </question>
- <answer>
- <para>
- Please follow the guidelines provided at:
- &kamailiobugslink;.
- </para>
- </answer>
- </qandaentry>
- </qandaset>
- </chapter>
|