Hi all, I am currently developing another SIPp-XML-scenario and I have one *wish* for future functionalities:
Today, if I want to analyse the response codes of e.g. a failed call, it looks this way: -------------------------------------------------------- <recv response="400" optional="true" next="2"> </recv> <recv response="401" optional="true" next="2"> </recv> <recv response="403" optional="true" next="2"> </recv> <recv response="404" optional="true" next="2"> </recv> <recv response="407" optional="true" next="2"> </recv> -------------------------------------------------------- It is clear, that the XML is quite unreadable and the responsecodes are still incomplete - if a "402" is returned, this responsecode is not catched. Now my proposal: it would be great if we can aggregate multiple respnses into one recv-statement: -------------------------------------------------------- <recv response="4??" optional="true" next="2"> </recv> -------------------------------------------------------- or -------------------------------------------------------- <recv response="40?" optional="true" next="2"> </recv> <recv response="41?" optional="true" next="3"> </recv> -------------------------------------------------------- or even -------------------------------------------------------- <recv response="(400|401|402)" optional="true" next="2"> </recv> -------------------------------------------------------- This would be a massive impromevent for creating generic and readable XML-files BR Michael ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
