Unexpected </action> (expected </assignstr>)
2023-11-26 15:09:54.629523 1700986194.629523: Invalid XML in scenario
2023-11-26 15:09:54.629523 1700986194.629523: Invalid XML in scenario
Via debugging, I saw that the <sip:alice@sipp.com> is parsed as an element, then the "/>" is used for closing this element instead of the assignstr.
With xml scenario contains an assignstr element like that:
The SIPp shows error:
Via debugging, I saw that the
<sip:alice@sipp.com>
is parsed as an element, then the "/>" is used for closing this element instead of the assignstr.