# &faqguide;

How do I migrate from rtpproxy or rtpproxy-ng to rtpengine?

For the most part, only the names of the functions have changed, with rtpproxy in each name replaced with rtpengine. For example, rtpproxy_manage() has become rtpengine_manage(). A few name duplications have also been resolved, for example there is now a single rtpengine_delete() instead of unforce_rtp_proxy() and the identical rtpproxy_destroy().

The largest difference to the old module is how flags are passed to rtpengine_offer(), rtpengine_answer(), rtpengine_manage() and rtpengine_delete(). 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 key=value pair.

For example, if you had a call rtpproxy_offer("FRWOC+PS");, this would then become:

    rtpengine_offer("force trust-address symmetric replace-origin replace-session-connection ICE=force RTP/SAVPF");

Finally, if you were using the second paramater (explicit media address) to any of these functions, this has been replaced by the media-address=... option within the first string of flags.

Where can I find more about OpenSIPS?

Take a look at &osipshomelink;.

Where can I post a question about this module?

First at all check if your question was already answered on one of our mailing lists:

- User Mailing List - &osipsuserslink;

- Developer Mailing List - &osipsdevlink;

E-mails regarding any stable &osips; release should be sent to &osipsusersmail; and e-mails regarding development versions should be sent to &osipsdevmail;.

If you want to keep the mail private, send it to &osipshelpmail;.

How can I report a bug?

Please follow the guidelines provided at: &osipsbugslink;.