2 Oct
2009
2 Oct
'09
6:31 a.m.
Henning Westerholt wrote:
Ah, you mean something like a "pv_printf()"
exported to the configuration
file? This would be indeed a nice workaround, but not sure if its possible
on a first glance. Perhaps Daniel can comment on this?
Yeah, exactly. :) A container that defers binding of the string or
numerical scalar value to runtime and whose return value would be
evaluated by the config lexer exactly the same as if it were a string
literal in the file, i.e.
rtpproxy_offer("", make_str_from_pv("$var(src_ip)"));
This would provide a bridge to solve a lot of compatibility problems
that presently exist between PV-enabled and legacy pre-PV core and
module functions.
Another thing, it
should be not that hard to update rtpproxy to be able to use PVs, the
fixup function and the evaluation functions are available in the core and
more or less just needs to be called.
Yeah, I think I don't have a choice and that is what I'm going to have
to try. But it's all for nothing if rtpproxy can't bridge traffic
from 5 network interfaces by binding to them all simultaneously. Do
you know if this is possible?
--
Alex Balashov - Principal
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671