Hi Juha, Most probably this functionality will become obsolete in a matter of days :(.... right now I'm working (and I hope I will finish it by the release) to a new type of route that will be triggered when a new request is internally generated. And there you can do changes on the request (like adding hdr) or trigger accounting....
Regards, Bogdan Juha Heinanen wrote: > i would have liked to add an extra header to publish request sent using > pua_publish of pua_mi module, but noticed that the interface doesn't > support it: > > 1.5.1. pua_publish > > Command parameters: > > * presentity_uri - e.g. sip:[EMAIL PROTECTED] > * expires - Relative expires time in seconds (e.g. 3600). > * event package - Event package that is target of published > information (e.g. presence). > * content type - Content type of published information > (e.g. application/pidf+xml) or . if no information is enclosed. > * ETag - ETag that publish should match or . if no ETag is given. > * body - The body of the publish request containing published > information or missing if no published information. It has to be a > single line for FIFO transport. > > although extra_headers is included in publ_info struct. is i ok if i > add extra_headers parameter to pua_mi pua_publish? > > looks like we have made the old mistake and not include parameter names > to the list. instead each parameter has a fixed position. this means > that adding extra_headers will break existing applications that use > pua_mi publish. > > -- juha > > _______________________________________________ > Devel mailing list > Devel@lists.openser.org > http://lists.openser.org/cgi-bin/mailman/listinfo/devel > > _______________________________________________ Devel mailing list Devel@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/devel
