SIPp's XML parser is unfortunately not an XML parser, so errors are not caught very well at all.
The timeout value should be fine. What is the precise error message you see (please copy and paste). Any extra spaces or things would mess up this value. If you want help getting the scenario loaded you should post it if at all possible. Charles "Michael Lynch" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 05/21/2008 03:09 PM To "Srivastava, Anuj Kumar" <[EMAIL PROTECTED]>, <[email protected]> cc Subject Re: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly Hi, Ok, done a bit more investigation and I?d like to share our progress with you and how we went about it ? because it was a bit arduous and hopefully someone will get some benefit from our experience even though we still can?t get it working with version 3.1. When we loaded the scenario into a different XML editor we found a missing tag. However ? we also found a problem in the DTD which might explain why our original XML editor didn?t pick up our missing tag. The error in the DTD we get is at line 21: <!ATTLIST exec command CDATA > - we don?t know what this is about or whether it is serious or not, anyway we fixed the missing tag in our XML, but we were then back to where we were before (almost), with the scenario working in 3.0 but not in 3.1. When we ran it in 3.0 it created calls and it worked. In 3.1 we got an error, it complained about the label ?m? which we used to denote the master. The way we successfully debugged was to remove the block with ?m? in it. SIPP then complained about something in the block above it, we deleted this block and guess what ? it complained about the block above that. We did this iteratively until SIPP started successfully and then we examined the block we had just removed. We found a couple of extraneous bits in there, an assignment which was never used and a tretrans on a receive command which obviously wasn?t necessary. During the debug process we found out that it didn?t like a timeout value of 1800000, having removed that it now works on v3.0 and performs very well ? still no joy with 3.1 though. Question ? is there a limit on values for timeouts? We need a long timeout because we have queuing on our sip server. Thanks, Michael From: Srivastava, Anuj Kumar [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 21, 2008 2:45 AM To: Michael Lynch; [email protected] Subject: RE: 3.1 - scenarios don't work, no documentation, not packaged properly Hello Michael, Due to the fact that many new features have been added in this release, and usage of few have changed from before, it would be useful if you can mention what exactly is the problem faced by your team regarding 3pcc and other issues. That would help to fix whatever issues are there. Documentation is very much available under "current documentation", which you can refer. http://sipp.sourceforge.net/doc/reference.html Thanks Anuj From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Lynch Sent: Tuesday, May 20, 2008 8:40 PM To: [email protected] Subject: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly My team and I have found the following problems with v3.1 1) Our scenarios do not work properly (they worked fine in 3.0) ? (features we use are regexp, 3PCC) 2) There is no documentation specific to this version - despite the long list of functionality additions on sourceforge, I can?t find the documentation for it 3) The PCAP support is not packaged hence we have to compile it I am very disappointed by this release, it seems to have bypassed quality control. Michael Lynch CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities. CONFIDENTIALITY NOTICE: This e-mail and any files attached may contain confidential and proprietary information of Alcatel-Lucent and/or its affiliated entities. Access by the intended recipient only is authorized. Any liability arising from any party acting, or refraining from acting, on any information contained in this e-mail is hereby excluded. If you are not the intended recipient, please notify the sender immediately, destroy the original transmission and its attachments and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Copyright in this e-mail and any attachments belongs to Alcatel-Lucent and/or its affiliated entities. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
