o Juha Heinanen on 02/03/2012 09:01 PM:
[email protected] writes:
This call control module asks HTTP server for replacements of call
profile data and uses them when processing incoming invite ("start" DI
function).
how about also allowing the profile data in the incoming sip request
itself in a header? for example:
here is an example, how imaginary sdp_filter and header_filter module
behavior could be specified by incoming message:
P-SDP-Filter: whitelist;list="g729,ilbc,speex,amr"
P-SDP-Filter: sanity,anonymize
P-Header-Filter: replace;from=sip:anonymous at anonymous.invalid
P-Header-Filter: blacklist;list="P-Asserted-Identity,Remote-Party-Identity"
P-Header-Filter: add;P-Source-IP=$si,add;P-Source-Port=$sp
those shouldn't be hard to implement. if you look at the call control
template module, you'll find the start(...) function, which gets the
variables, and can access the sbc profile directly.
using http server would be a much heavier solution, since my sip proxy
would first need to create the file for http server when it processes
incoming message for sems.
the idea of this is to have it interface to some web applications,
dynamically generating the call profile from there.
stefan
-- juha
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
--
tel:+491621366449
sip:[email protected]
mailto/xmpp:[email protected]
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
