[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 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. -- juha _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
