You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(35) |
Jul
(20) |
Aug
(30) |
Sep
(88) |
Oct
(44) |
Nov
(42) |
Dec
(21) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(53) |
Feb
(40) |
Mar
(71) |
Apr
(52) |
May
(33) |
Jun
(33) |
Jul
(31) |
Aug
(38) |
Sep
(31) |
Oct
(31) |
Nov
(14) |
Dec
(1) |
2008 |
Jan
(7) |
Feb
(11) |
Mar
(13) |
Apr
(19) |
May
(15) |
Jun
(17) |
Jul
(18) |
Aug
(6) |
Sep
(4) |
Oct
(13) |
Nov
(6) |
Dec
(5) |
2009 |
Jan
(7) |
Feb
(23) |
Mar
(1) |
Apr
(20) |
May
(26) |
Jun
(28) |
Jul
(6) |
Aug
(25) |
Sep
(40) |
Oct
(42) |
Nov
(7) |
Dec
(11) |
2010 |
Jan
(12) |
Feb
(11) |
Mar
(34) |
Apr
(14) |
May
(20) |
Jun
(22) |
Jul
(21) |
Aug
(17) |
Sep
(9) |
Oct
(17) |
Nov
(12) |
Dec
(16) |
2011 |
Jan
(14) |
Feb
(6) |
Mar
(4) |
Apr
(8) |
May
(1) |
Jun
(9) |
Jul
(1) |
Aug
(12) |
Sep
(7) |
Oct
(9) |
Nov
(48) |
Dec
(7) |
2012 |
Jan
(10) |
Feb
(18) |
Mar
(26) |
Apr
(15) |
May
(9) |
Jun
(4) |
Jul
(4) |
Aug
(15) |
Sep
(24) |
Oct
(8) |
Nov
(16) |
Dec
(7) |
2013 |
Jan
(7) |
Feb
(8) |
Mar
(16) |
Apr
(8) |
May
(9) |
Jun
(8) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
(4) |
Nov
(7) |
Dec
(3) |
2014 |
Jan
(12) |
Feb
(16) |
Mar
(5) |
Apr
(2) |
May
(12) |
Jun
(16) |
Jul
(1) |
Aug
(1) |
Sep
(9) |
Oct
(10) |
Nov
(5) |
Dec
(4) |
2015 |
Jan
(8) |
Feb
(1) |
Mar
(4) |
Apr
(12) |
May
(1) |
Jun
(4) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(6) |
Dec
|
2016 |
Jan
(6) |
Feb
(3) |
Mar
(2) |
Apr
(11) |
May
(1) |
Jun
|
Jul
(4) |
Aug
|
Sep
(3) |
Oct
(2) |
Nov
|
Dec
(12) |
2017 |
Jan
(13) |
Feb
|
Mar
(4) |
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
(7) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2019 |
Jan
(1) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: Jacques, O. \(O. T. Infra\) <oli...@hp...> - 2006-06-19 21:47:05
|
Hello Anjlica, Can you send on the list: - The command line you are using to start Seagull - The XML scenario and config file that are listed in the command line Thanks, Olivier. > -----Original Message----- > From: gul...@li...=20 > [mailto:gul...@li...] On Behalf=20 > Of Anjlica Malla XX (TX/EUS) > Sent: lundi 19 juin 2006 22:58 > To: gul...@li... > Subject: Re: [Seagull-users] Diameter protocol support (and thanks) >=20 > Hi, > Is there a URL to check if there is existing FAQ for trouble=20 > getting the Diameter protocol started? >=20 > My issue: > I am testing a Diameter server. So I am using Seagull to=20 > simulate the Diameter client. > I edited the scenario .xml and config.xml to specify my host=20 > IP and Diameter Realm. When I start the client, I get an error: > 2006-06-16.16:48:19.778|T|Error while sending [[CER >=20 > I see that its still sending the AVP values that were in the=20 > file by default. Its not taking the values that I entered in=20 > the .xml file. >=20 > Thanks in advance. > Anjlica=20 > =20 >=20 >=20 > _______________________________________________ > Gull-users mailing list > Gul...@li... > https://lists.sourceforge.net/lists/listinfo/gull-users >=20 |
From: Jacques, O. \(O. T. Infra\) <oli...@hp...> - 2006-06-19 21:42:41
|
Hi, =20 You are right, sctp support is not included in Seagull yet.=20 SCTP support in Seagull relies on sctplib (http://www.sctp.de/sctp-download.html).=20 But we didn't checked some files in SVN and this prevents Seagull to use SCTP right now. It is just a matter of days so please be patient. =20 Olivier. =20 ________________________________ From: gul...@li... [mailto:gul...@li...] On Behalf Of Jun Yin Sent: lundi 19 juin 2006 22:25 To: gul...@li... Subject: [Seagull-users] How to enable SCTP support =09 =09 Hi,=20 I hope to use seagull to do SCTP test. the document said I have to use the file:libtrans_extsctp.so" , but I cannot find it in any place. I tried to change the file name to "libtrans_extsctp.so" , when running, it said "cannot find file: libtrans_extsctp.so". =09 How can I solve the problem? Thanks a lot. =09 --=20 Rgds,=20 =09 Hans Yin Web: homeofhans.homeip.net Email: ha...@gm...=20 MSN: ha...@ho... Skype: hans_yin_vancouver=20 |
From: Anjlica M. XX (TX/EUS) <anj...@er...> - 2006-06-19 21:32:22
|
Have u done a search for this file on your machine? I had to specify the whole path to in the config file: /home/userid/seagull.1.3.0/build-1.3.0/libtrans_ip.so In fact I had to specify full paths for seagull as well. good luck. _____ From: gul...@li... [mailto:gul...@li...] On Behalf Of Jun Yin Sent: Monday, June 19, 2006 3:25 PM To: gul...@li... Subject: [Seagull-users] How to enable SCTP support Hi, I hope to use seagull to do SCTP test. the document said I have to use the file:libtrans_extsctp.so" , but I cannot find it in any place. I tried to change the file name to "libtrans_extsctp.so" , when running, it said "cannot find file: libtrans_extsctp.so". How can I solve the problem? Thanks a lot. -- Rgds, Hans Yin Web: homeofhans.homeip.net <http://homeofhans.homeip.net> Email: ha...@gm... <mailto:ha...@gm...> MSN: ha...@ho... <mailto:ha...@ho...> Skype: hans_yin_vancouver |
From: Anjlica M. XX (TX/EUS) <anj...@er...> - 2006-06-19 20:58:30
|
Hi, Is there a URL to check if there is existing FAQ for trouble getting the Diameter protocol started? My issue: I am testing a Diameter server. So I am using Seagull to simulate the Diameter client. I edited the scenario .xml and config.xml to specify my host IP and Diameter Realm. When I start the client, I get an error: 2006-06-16.16:48:19.778|T|Error while sending [[CER I see that its still sending the AVP values that were in the file by default. Its not taking the values that I entered in the .xml file. Thanks in advance. Anjlica |
From: Jun Y. <ha...@gm...> - 2006-06-19 20:24:56
|
Hi, I hope to use seagull to do SCTP test. the document said I have to use the file:libtrans_extsctp.so" , but I cannot find it in any place. I tried to change the file name to "libtrans_extsctp.so" , when running, it said "cannot find file: libtrans_extsctp.so". How can I solve the problem? Thanks a lot. -- Rgds, Hans Yin Web: homeofhans.homeip.net Email: ha...@gm... MSN: ha...@ho... Skype: hans_yin_vancouver |
From: Jacques, O. \(O. T. Infra\) <oli...@hp...> - 2006-06-19 06:00:59
|
> Hi, >=20 > First off I'd like to say thanks to those involved in making=20 > this software available to the community. Thanks Perrin. =20 > I have spent a bit of time experimenting with the Diameter=20 > protocol generator, and started doing some testing against=20 > our Diameter stack and simulators. (There have been no=20 > interoperability issues so far.) Good to have this first "external" report. > During my testing, I found a few problems with the=20 > configuration files for the Diameter applications. So I=20 > adapted one of our tools to generate the dictionary files for=20 > the applications we support (using the same data we use for=20 > our code generation). I've also been extending some of the=20 > scenarios to be a bit more representative. Yes, example scenarios are kind of simplistic. We are also aware that Diameter base and Cx dictionaries are missing commands and AVPs (and some might just need a bit of refresh). > If it would be useful, I can share these changes -- what's=20 > the best way to do so? It would be great! There are two cases: If this is a new file, just send it to the Seagull-users mailing list. If this is a set of corrections to existing files (or if you have several files to provide), do: diff -bruN seagull.orig seagull.new > mycontrib.diff And send the resulting mycontrib.diff Thanks Perrin, Olivier. |
From: Perrin M. <pe...@op...> - 2006-06-18 22:34:40
|
Hi, First off I'd like to say thanks to those involved in making this software available to the community. I have spent a bit of time experimenting with the Diameter protocol generator, and started doing some testing against our Diameter stack and simulators. (There have been no interoperability issues so far.) During my testing, I found a few problems with the configuration files for the Diameter applications. So I adapted one of our tools to generate the dictionary files for the applications we support (using the same data we use for our code generation). I've also been extending some of the scenarios to be a bit more representative. If it would be useful, I can share these changes -- what's the best way to do so? Regards Perrin |
From: Olivier J. <oja...@gm...> - 2006-06-17 16:03:44
|
Hi, I just commited a Diameter-Draft-08 dictionary [Revision 24]. You can get a fresh copy of Seagull's source code by running: svn co https://svn.sourceforge.net/svnroot/gull/seagull/trunk/src seagull.src.svn Note that I didn't tested it. Olivier. On 6/16/06, Olivier Jacques <oja...@gm...> wrote: > On 6/16/06, Anjlica Malla XX (TX/EUS) <anj...@er...> wrote: > > Hi, > > Thanks for your response. I was evaluating a commercial tool. They are currently compliant with RFC 3588. I have the sample mesasges that are complaint with draft 8. I can send Ethereal traces to you if you want. I can also test the tool for you. > > That will be best as I won't have time to run tests. > > > Is the tool completely free? > > Yes. It is under GPL license and free. There is no feature nor usage > limitation. > > > Our call model: > > We are looking at generating a traffic of 44 sessions/second. > > Of the 44 sessions, 70% are events. 30% are GPRS and IM sesisosn that last for 10 minutes. > > Mixing a traffic (several call scenarios) will require to start > several Seagulls in parallel. Which is not really an issue. > > > So once the traffic ramps up, the number of active sessions at any given time will be roughly 8000. > > Can the Diameter tool support that? Are there any memory leaks or any performance issues that you have seen? > > Judge by yourself. Here is a screenshot with 21000 calls opened > simultaneously, Seagull having placed more than a million call at 450 > call/s (not Diameter protocol - but the core is the same): > http://gull.sourceforge.net/doc/faq.html#faq005 > > I would recommend that you try Seagull and judge by yourself. > Olivier. > > > > > Regards > > > > Anjlica > > > > -----Original Message----- > > From: Olivier Jacques [mailto:oja...@gm...] > > Sent: Thursday, June 15, 2006 5:27 PM > > To: Anjlica Malla XX (TX/EUS) > > Cc: gul...@li... > > Subject: Re: [Seagull-users] Diameter compliance to IETF diameter draft 8 > > > > On 6/16/06, Anjlica Malla XX (TX/EUS) <anj...@er...> wrote: > > > Hi, > > > Is the Diameter simulator compliant with IETF diameter draft 8 or does > > > it support only RFC 3588? > > > Thanks. > > > Anjlica > > > > Hi, > > > > Seagull describes Diameter commands and AVPs using an XML file. Here is the XML file for RFC 3588 and Cx application: > > http://svn.sourceforge.net/viewcvs.cgi/*checkout*/gull/seagull/trunk/src/exe-env/diameter-env/config/base_cx.xml?content-type=text%2Fplain > > > > Although I didn't looked at it in details, supporting draft-08 > > (http://tools.ietf.org/html/draft-ietf-aaa-diameter-08.txt) is most likely a matter of minutes, by changing XML dictionary. Unless there are important protocol format changes (in Seagull, even headers can change without impacting anything but the dictionary). > > > > We'll try to make this draft-08 dictionary as an example (without having a mean to test). > > > > Olivier. > > -- > > HP OpenCall Software > > http://www.hp.com/go/opencall/ > > > > > -- > HP OpenCall Software > http://www.hp.com/go/opencall/ > -- HP OpenCall Software http://www.hp.com/go/opencall/ |
From: Olivier J. <oja...@gm...> - 2006-06-16 14:52:34
|
On 6/16/06, Anjlica Malla XX (TX/EUS) <anj...@er...> wrote: > Hi, > Thanks for your response. I was evaluating a commercial tool. They are currently compliant with RFC 3588. I have the sample mesasges that are complaint with draft 8. I can send Ethereal traces to you if you want. I can also test the tool for you. That will be best as I won't have time to run tests. > Is the tool completely free? Yes. It is under GPL license and free. There is no feature nor usage limitation. > Our call model: > We are looking at generating a traffic of 44 sessions/second. > Of the 44 sessions, 70% are events. 30% are GPRS and IM sesisosn that last for 10 minutes. Mixing a traffic (several call scenarios) will require to start several Seagulls in parallel. Which is not really an issue. > So once the traffic ramps up, the number of active sessions at any given time will be roughly 8000. > Can the Diameter tool support that? Are there any memory leaks or any performance issues that you have seen? Judge by yourself. Here is a screenshot with 21000 calls opened simultaneously, Seagull having placed more than a million call at 450 call/s (not Diameter protocol - but the core is the same): http://gull.sourceforge.net/doc/faq.html#faq005 I would recommend that you try Seagull and judge by yourself. Olivier. > > Regards > > Anjlica > > -----Original Message----- > From: Olivier Jacques [mailto:oja...@gm...] > Sent: Thursday, June 15, 2006 5:27 PM > To: Anjlica Malla XX (TX/EUS) > Cc: gul...@li... > Subject: Re: [Seagull-users] Diameter compliance to IETF diameter draft 8 > > On 6/16/06, Anjlica Malla XX (TX/EUS) <anj...@er...> wrote: > > Hi, > > Is the Diameter simulator compliant with IETF diameter draft 8 or does > > it support only RFC 3588? > > Thanks. > > Anjlica > > Hi, > > Seagull describes Diameter commands and AVPs using an XML file. Here is the XML file for RFC 3588 and Cx application: > http://svn.sourceforge.net/viewcvs.cgi/*checkout*/gull/seagull/trunk/src/exe-env/diameter-env/config/base_cx.xml?content-type=text%2Fplain > > Although I didn't looked at it in details, supporting draft-08 > (http://tools.ietf.org/html/draft-ietf-aaa-diameter-08.txt) is most likely a matter of minutes, by changing XML dictionary. Unless there are important protocol format changes (in Seagull, even headers can change without impacting anything but the dictionary). > > We'll try to make this draft-08 dictionary as an example (without having a mean to test). > > Olivier. > -- > HP OpenCall Software > http://www.hp.com/go/opencall/ > -- HP OpenCall Software http://www.hp.com/go/opencall/ |
From: Olivier J. <oja...@gm...> - 2006-06-15 22:26:45
|
On 6/16/06, Anjlica Malla XX (TX/EUS) <anj...@er...> wrote: > Hi, > Is the Diameter simulator compliant with IETF diameter draft 8 or does it > support only RFC 3588? > Thanks. > Anjlica Hi, Seagull describes Diameter commands and AVPs using an XML file. Here is the XML file for RFC 3588 and Cx application: http://svn.sourceforge.net/viewcvs.cgi/*checkout*/gull/seagull/trunk/src/exe-env/diameter-env/config/base_cx.xml?content-type=text%2Fplain Although I didn't looked at it in details, supporting draft-08 (http://tools.ietf.org/html/draft-ietf-aaa-diameter-08.txt) is most likely a matter of minutes, by changing XML dictionary. Unless there are important protocol format changes (in Seagull, even headers can change without impacting anything but the dictionary). We'll try to make this draft-08 dictionary as an example (without having a mean to test). Olivier. -- HP OpenCall Software http://www.hp.com/go/opencall/ |
From: Anjlica M. XX (TX/EUS) <anj...@er...> - 2006-06-15 22:06:37
|
Hi, Is the Diameter simulator compliant with IETF diameter draft 8 or does it support only RFC 3588? Thanks. Anjlica |
From: Laurent S. <lau...@at...> - 2006-06-12 09:54:49
|
Hello Louis in fact you need to install the package pdksh (Public Domain KSH) located in category shell of the cygwin installer. Bye Laurent Jacques, Olivier (OpenCall Test Infra) wrote: > Hello Louis, > > can you try installing "ksh" shell for Cygwin? (type "type ksh" and > check if you can find it). > > Thanks, > Olivier. > HP OpenCall Software > > ________________________________ > > From: gul...@li... > [mailto:gul...@li...] On Behalf Of lijinxi > Sent: lundi 12 juin 2006 11:06 > To: gul...@li... > Subject: [Seagull-users] How to generate execution files in > cygwin > > > hi, > > It is first time to use seagull. When i built build.ksh in > cygwin environment. The belowing error info is come: > > "Bad interpreter" > > Any body can give me some info for cygwin? > > Regards > Louis > > > > _______________________________________________ > Gull-users mailing list > Gul...@li... > https://lists.sourceforge.net/lists/listinfo/gull-users > > > -- A+ Laurent ====================================================================== This electronic transmission and any files attached to it are strictly confidential and intended solely for the addressee. If you are not the intended addressee, you must not disclose, copy or take any action in reliance of this transmission. If you have received this transmission in error, please notify us by return and delete the same. The views expressed in this electronic transmission do not necessarily reflect those of Atos Origin or any of its subsidiary companies. Although the sender endeavours to maintain a computer virus free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Thank You. ====================================================================== |
From: Jacques, O. \(O. T. Infra\) <oli...@hp...> - 2006-06-12 09:20:11
|
Hello Louis, =20 can you try installing "ksh" shell for Cygwin? (type "type ksh" and check if you can find it). Thanks, Olivier. HP OpenCall Software ________________________________ From: gul...@li... [mailto:gul...@li...] On Behalf Of lijinxi Sent: lundi 12 juin 2006 11:06 To: gul...@li... Subject: [Seagull-users] How to generate execution files in cygwin =09 =09 hi, =20 It is first time to use seagull. When i built build.ksh in cygwin environment. The belowing error info is come: =20 "Bad interpreter" =20 Any body can give me some info for cygwin? =20 Regards Louis=20 |
From: lijinxi <li...@hu...> - 2006-06-12 09:10:54
|
hi, It is first time to use seagull. When i built build.ksh in cygwin environment. The belowing error info is come: "Bad interpreter" Any body can give me some info for cygwin? Regards Louis |
From: Jacques, O. \(O. T. Infra\) <oli...@hp...> - 2006-06-07 12:27:25
|
Hi, =20 This is a test message - please ignore. =20 Olivier. |
From: Olivier J. <oja...@gm...> - 2006-05-16 21:16:36
|
This is a test... --=20 HP OpenCall Software http://www.hp.com/go/opencall/ |