From d6cd5655df83d233562ab557a0e73cb5e65f0b1c Mon Sep 17 00:00:00 2001 From: Daniel-Constantin Mierla Date: Thu, 5 Apr 2018 20:03:23 +0200 Subject: [PATCH] textops: documentation for append_body_part_hex() --- src/modules/textops/doc/textops_admin.xml | 57 +++++++++++++++++++++++ 1 file changed, 57 insertions(+) diff --git a/src/modules/textops/doc/textops_admin.xml b/src/modules/textops/doc/textops_admin.xml index 3ff09fb8121..966169d2dd4 100644 --- a/src/modules/textops/doc/textops_admin.xml +++ b/src/modules/textops/doc/textops_admin.xml @@ -1561,6 +1561,63 @@ Content-Disposition: signal;handling=required 7e Od 04 55 75 69 20 4d 61 6b 65 43 61 6c 6c +--unique-boundary-1 +... + + + + +
+ + <function moreinfo="none">append_body_part_hex(txt,content_type[, content_disposition])</function> + + + Append a part on multipart body SIP message, with the content provided + in hexa format. Will use "unique-boundary-1" as boundary. + + Meaning of the parameters is as follows: + + + txt - content for the multipart body in + hexa format. Spaces can be used between the pairs of hexa digits + to make it easier to read in the config, they are ignored and + not added in the body part. The parameter can include + pseudo-variables. + + + + content_type - value of Content-Type header, + can include pseudo-variables. + + + + content_disposition - value of Content-Disposition header, + can include pseudo-variables. + + + + + This function can be used from REQUEST_ROUTE, FAILURE_ROUTE, BRANCH_ROUTE. + + + The core will take care of the last boundary ending "--". Detecting wich one is + the last and fixing the others if needed. + + + <function>append_body_part_hex</function> usage + +... +$var(b) = "6b 61 6d 61 69 6c 69 6f"; +append_body_part_hex("$var(b)", "application/my-custom-ext"); +... + +# Will append this to the body: + +... +Content-Type: application/my-custom-ext + +kamailio + --unique-boundary-1 ...