Re: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly
Thanks Charles, Forgive my ignorance - what is SVN? And where can I get hold of the package containing it? Thanks, Michael -Original Message- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 3:39 PM To: Michael Lynch Cc: Srivastava, Anuj Kumar; sipp-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: RE: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly This is a bug that has been fixed in SVN. Charles Michael Lynch [EMAIL PROTECTED] 05/22/2008 12:58 PM To Charles P Wright/Watson/[EMAIL PROTECTED] cc Srivastava, Anuj Kumar [EMAIL PROTECTED], sipp-users@lists.sourceforge.net, [EMAIL PROTECTED] Subject RE: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly Thanks Charles, We've got rid of some of the errors now. These are the latest versions of the scenario files and config files. They work in 3.0 and not in 3.1. The error we get from transfer-to-ss is:- In pcap pcap/dtmf_2833_1.pcap, npkts 10 max pkt length 24 base port 1 In pcap pcap/t30sec.pcap, npkts 1094 max pkt length 180 base port 49172 2008-05-21 10:13:10:0761211375590.076638: The label 'master' was not defined (index 9, ontimeout attribute) . (Also - XMLPad still picks up an error in the DTD shipped with both versions, so you might want to see if you can fix that one too.) Thanks, Michael -Original Message- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 7:58 AM To: Michael Lynch Cc: Srivastava, Anuj Kumar; sipp-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly 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], sipp-users@lists.sourceforge.net 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 180, 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; sipp-users@lists.sourceforge.net 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: sipp-users@lists.sourceforge.net Subject: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly My
Re: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly
SVN is subversion (like CVS), which is the source code control that we use for SIPp development. With a new Fedora or RedHat you can probably type svn to see if you have it. If not you can use yum to install subversion. This page has the URL to the SIPp repository http://sipp.sourceforge.net/wiki/index.php/Dev, which is: https://sipp.svn.sourceforge.net/svnroot/sipp/sipp/trunk And this is a basic tutorial if you are familiar with CVS: http://svn.collab.net/repos/svn/trunk/doc/user/cvs-crossover-guide.html Charles Michael Lynch [EMAIL PROTECTED] 05/23/2008 10:23 AM To Charles P Wright/Watson/[EMAIL PROTECTED] cc Srivastava, Anuj Kumar [EMAIL PROTECTED], sipp-users@lists.sourceforge.net, [EMAIL PROTECTED] Subject RE: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly Thanks Charles, Forgive my ignorance - what is SVN? And where can I get hold of the package containing it? Thanks, Michael -Original Message- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 3:39 PM To: Michael Lynch Cc: Srivastava, Anuj Kumar; sipp-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: RE: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly This is a bug that has been fixed in SVN. Charles Michael Lynch [EMAIL PROTECTED] 05/22/2008 12:58 PM To Charles P Wright/Watson/[EMAIL PROTECTED] cc Srivastava, Anuj Kumar [EMAIL PROTECTED], sipp-users@lists.sourceforge.net, [EMAIL PROTECTED] Subject RE: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly Thanks Charles, We've got rid of some of the errors now. These are the latest versions of the scenario files and config files. They work in 3.0 and not in 3.1. The error we get from transfer-to-ss is:- In pcap pcap/dtmf_2833_1.pcap, npkts 10 max pkt length 24 base port 1 In pcap pcap/t30sec.pcap, npkts 1094 max pkt length 180 base port 49172 2008-05-21 10:13:10:0761211375590.076638: The label 'master' was not defined (index 9, ontimeout attribute) . (Also - XMLPad still picks up an error in the DTD shipped with both versions, so you might want to see if you can fix that one too.) Thanks, Michael -Original Message- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 7:58 AM To: Michael Lynch Cc: Srivastava, Anuj Kumar; sipp-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly 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], sipp-users@lists.sourceforge.net 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 180, 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
Re: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly
Thanks Charles, I'm not sure what you're saying though. What I meant to ask was how do I get the fix for our issue? i.e. a SIPP release package containing the fix? Will there be a release soon? Or are you saying that the only way I can get the fix is by checking the latest code out of SVN? Thanks again, Michael -Original Message- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Friday, May 23, 2008 11:41 AM To: Michael Lynch Cc: Srivastava, Anuj Kumar; sipp-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: RE: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly SVN is subversion (like CVS), which is the source code control that we use for SIPp development. With a new Fedora or RedHat you can probably type svn to see if you have it. If not you can use yum to install subversion. This page has the URL to the SIPp repository http://sipp.sourceforge.net/wiki/index.php/Dev, which is: https://sipp.svn.sourceforge.net/svnroot/sipp/sipp/trunk And this is a basic tutorial if you are familiar with CVS: http://svn.collab.net/repos/svn/trunk/doc/user/cvs-crossover-guide.html Charles Michael Lynch [EMAIL PROTECTED] 05/23/2008 10:23 AM To Charles P Wright/Watson/[EMAIL PROTECTED] cc Srivastava, Anuj Kumar [EMAIL PROTECTED], sipp-users@lists.sourceforge.net, [EMAIL PROTECTED] Subject RE: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly Thanks Charles, Forgive my ignorance - what is SVN? And where can I get hold of the package containing it? Thanks, Michael -Original Message- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 3:39 PM To: Michael Lynch Cc: Srivastava, Anuj Kumar; sipp-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: RE: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly This is a bug that has been fixed in SVN. Charles Michael Lynch [EMAIL PROTECTED] 05/22/2008 12:58 PM To Charles P Wright/Watson/[EMAIL PROTECTED] cc Srivastava, Anuj Kumar [EMAIL PROTECTED], sipp-users@lists.sourceforge.net, [EMAIL PROTECTED] Subject RE: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly Thanks Charles, We've got rid of some of the errors now. These are the latest versions of the scenario files and config files. They work in 3.0 and not in 3.1. The error we get from transfer-to-ss is:- In pcap pcap/dtmf_2833_1.pcap, npkts 10 max pkt length 24 base port 1 In pcap pcap/t30sec.pcap, npkts 1094 max pkt length 180 base port 49172 2008-05-21 10:13:10:0761211375590.076638: The label 'master' was not defined (index 9, ontimeout attribute) . (Also - XMLPad still picks up an error in the DTD shipped with both versions, so you might want to see if you can fix that one too.) Thanks, Michael -Original Message- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 7:58 AM To: Michael Lynch Cc: Srivastava, Anuj Kumar; sipp-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly 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], sipp-users@lists.sourceforge.net 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
Re: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly
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], sipp-users@lists.sourceforge.net 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 180, 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; sipp-users@lists.sourceforge.net 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: sipp-users@lists.sourceforge.net 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
[Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly
Hello, I just had a look at your scenorio files, and the obvious errors which I could see are the normal syntax errors which sipp 3.1 doesen't allow. Sipp now throws understandable errors -: The label %s was not defined ; Variable %s is referenced 1 times! ; assign_to value is missing etc.. Which you would have noticed in your xml. I see label 5 used but not defined, variables (3) referenced but never used, and probably in few places regexp is used, But the value obtained is not assigned anywhere. These are the normal syntax checks which sipp 3.1 has introduced. I could not find any such error for label 'm' or timeout though. As Charles said, you must copy paste your specific errors and other scenarios you use. Regarding pcap packaging, sipp needs to be compiled with pcap option as before. Regards Anuj -Original Message- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Thursday, May 22, 2008 4:28 PM To: Michael Lynch Cc: Srivastava, Anuj Kumar; sipp-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [Sipp-users] 3.1 - scenarios don't work, no documentation, not packaged properly 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], sipp-users@lists.sourceforge.net 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 180, 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; sipp-users@lists.sourceforge.net 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: sipp-users@lists.sourceforge.net 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
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 180, 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; sipp-users@lists.sourceforge.net 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: sipp-users@lists.sourceforge.net 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
Re: [Sipp-users] 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: sipp-users@lists.sourceforge.net 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. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
