Hello Wilmar,SIPp is a testing tool so it is quite flexible in terms of headers' and methods' names - you can make intentional typos in them to check how the DUT deals with such errors. So if you want to use SIPp to generate requests with non-standard methods and headers, there is no limitation on that (except maybe some string lengths but I doubt such limitation is relevant for your purpose).
Similarly, if you want to use SIPp to receive such messages, you can make the scenario expect any method name using |<recv request="WHATEVER_STRING_YOU_LIKE">|, and you can use at least |<ereg search_in="msg" ...>| to handle the contents of non-standard headers, but I am almost sure you can also use |<ereg search_in="hdr" ... header="whatever_header_name">| , and I believe you can even use |[last_whatever_header_name]| to copy non-standard headers from received messages to ones you send.
The best way to make sure what you can do is to create one UAC scenario and one UAS scenario and run the two against each other. I would start with standard methods and headers first, and then change them to your desired ones one by one.
Pavel
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
