[sr-dev] rtpproxy (k): removal of force_rtpproxy

[Ovidiu Sas]

Without using the dialog module, it will be difficult to keep track of
the rtpproxy session for the duration of the call.
It can be tracked for the duration of the transaction and in this case
we could have:
 - use_rtp_proxy: for the creation of the rtpproxy session;
 - update_rtp_proxy: for updating an rtpproxy session for an in-dialog request;
 - end_rtp_session is just like unforce_rtp_proxy.

Regards,
Ovidiu Sas

On Thu, Sep 23, 2010 at 11:50 AM, Juha Heinanen <jh at tutpro.com> wrote:
>  What you propose is a new functionality.  I would prefer a new name
>  (engage_rtp_proxy) for this function and still drop the old
>  force_rtp_proxy.
>
> ovidiu,
>
> it may be confusing to call the new function engage_rtp_proxy, because
> similar name is used in mediaproxy module for a dialog based function
> that tries to handle the whole dialog, but fails to address important
> issues, such as forking.
>
> if the idea is not to have a dialog based thing, then function names
> like use_rtp_proxy/end_rtp_session would be better.
>
> -- juha
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>