In SIPp 3.2 (and all earlier versions as far as I can tell), the XML
parser moves forward one character too far after parsing a comment,
DOCTYPE or CDATA, which can cause it not to recognise an XML element
which follows it immediately (i.e. without an intervening space or
newline). This is because the string pointer is moved forwards to just
after the '>' character, but the end of the xp_open_element function
also increments the pointer, and so skips a character.
In addition, the DOCTYPE parser moves forward one additional character
too far, which caused the bug originally reported. The attached patch
fixes both problems.
I also attach 1205629_repro_1.xml, which has a <scenario> tag
immediately following a comment, and 1205629_repro_2.xml, which has a
<scenario> tag separated from the <DOCTYPE> declaration by a single
newline. SIPp 3.2 will give the error "No 'scenario' section in xml
scenario file." for both files.
I'll check the patch in shortly if there are no objections, and try to
use the attached XML files as the basis of a regression test for this