[OpenSIPS-Users] Calling engage_media_proxy per branch

Richard Revels rrevels at bandwidth.com
Thu May 28 18:05:19 CEST 2009

For scenario b I suspect you could just call a route from within the  
failure route and engage the media proxy there.  I know you will be  
able to make the function call without error, just never tested it to  
see if it has any undesired side effects.  Like not actually working.

Richard Revels

On May 28, 2009, at 11:27 AM, Thomas Gelf wrote:

> Hi list,
> I really like engage_media_proxy() as it really makes life easier.
> However, currently it is dialog-based and cannot be called in a
> branch_route. This has some side-effect:
> a) if a call is forked to two users, one behind NAT and one with
>   non-symmetric router and STUN or on public IP, mediaproxy is
>   always used, even if the client without NAT picks up the call.
> While I could live with this, a second scenario is really ugly:
> b) A is calling B, both with public IP. B issues a conditional
>   call forward (30x) to C, with C being behind NAT. As far as
>   I understood the module there is no way to "engage" Mediaproxy
>   in this scenario.
> What I would like to know is:
> - is there a known workaround for this issue, that I can apply
>  to my config script?
> - is it planned to change engage_media_proxy to make it "branch-
>  aware"?
> - if you can acknowledge neither of the above: do I really need
>  to tear down/re-use Mediaproxy session on each ReINVITE? What
>  is the current best practice in this case?
> Many thanks for your answers!
> Best regards,
> Thomas Gelf
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

More information about the Users mailing list