Hello SIPp team,
I'm coming back to this old thread with an extended need, which is a
possibility to inject the binary bodies from file, to support dynamic
test scenarios where the contents of the binary body needs to be chosen
from a set of predefined values.
When the \xdd syntax is used in the injection file and then the
reference to the field is used in the scenario file, the body contains
literally "\","x","d","d".
When the \xdd syntax is used in the scenario file to fill an in-memory
injection file with the required values, like
<insert file="binbody.table"
value="[$binbody_id];\x03\x02\x03\x00\x05\xc3"/>
the body contains the binary characters as needed but only up to the
first null one.
The tested equipment doesn't understand other than binary-encoded body
so use of Content-Transfer-Encoding is not an option.
Lacking knowledge about the internal interpretation of the string
variables, I don't know what requires less effort to implement, whether
interpretation of the \xdd syntax as late as when expanding [field1
file="binbody.table" line="[$binbody_id]"] or changing the string
handling to allow the in-memory files (and string variables in general)
to contain binary zero octets mid-string. In my current case, the number
of body variants is up to ten so filling the in-memory injection file
from inside the scenario is OK, but maybe someone else would need
hundreds of different bodies, or would even like to compose the binary
body dynamically from parts?
Thank you for ideas or even solutions
Pavel
------------------------------------------------------------------------------
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
