#96 application-level configuration of mediaproxy domain

[Kobi Eshun]

Hi,

Attached is a patch that facilitates explicit, per-call specification of the mediaproxy domain name.

Currently, the mediaproxy dispatcher automatically computes the "best" mediaproxy to use based on the domains extracted from the message headers. This patch provides a mechanism to directly specify which mediaproxy to use, based on the results of some arbitrary logic performed by the script (a stored-procedure call, for example).

There is a new module parameter, "mediaproxy_domain_avp," which defaults to "s:mediaproxy_domain". If that AVP is populated when use_media_proxy() is invoked, then the "info" portion of the dispatcher request will include a "mpxdomain:<blah-blah-blah>" attribute/value pair.

For example, the following script code:

modparam ("mediaproxy", "mediaproxy_domain_avp","i:140")

...

$avp(i:140)="domain://sip.sightspeed.org";
use_media_proxy();

results in a request to the dispatcher with "info" like this:

info=from:kobi.at.work@sip.sightspeed.org,to:kobi.at.work@sip.sightspeed.org,fromtag:0eb5e253,totag:,mproxydomain:domain://sip.sightspeed.org

There is a corresponding patch to the media proxy itself that I'll push out as soon as I've figured out where to send patches to. Cheers,
--
kobi

[Kobi Eshun]

[Dan Pascu]

Logged In: YES
user_id=1296758
Originator: NO

It was added with some slight modifications to trunk. Also present in the mediaproxy server since version 1.9.0.

[Kobi Eshun]

Logged In: YES
user_id=1039134
Originator: YES

Cool -- thanks, Dan.
--
kobi