Seagull

Seagull is a multi-protocol traffic generator. Especially targeted towards IMS, Seagull supports Diameter (RFC3588 and all applications) over TCP/SCTP and IPv4/IPv6 , TCAP (over SS7 or Sigtran), XCAP over HTTP and Radius. Seagull-1.5.0 has been ... [More] released. Here are the changes since 1.4.1: NEW: Support of authentication (MD5/Digest and AKA) for text protocols like http, xcap and SIP NEW: Reconnection in case a LAN failure (option of transport channel) NEW: configuration parameters for text protocols (see http://gull.sourceforge.net/doc/core.html#config_param\) NEW: Add two features for Traffic control : pause and resume (http://gull.sourceforge.net/doc/core.html#control_remote) NEW: Added stop, pause and resume to remote control Perl example TLV: New protocol family: TLV (Type, Length, Value) - no public execution environment available for this family OCTCAP: Fix error-tag functions OCTCAP: Fix u-abort-cause to be set in octcap lib DIAMETER: Fix for start-length that was not working properly under certain circumstances FIX: TLS open could fail under certain circumstances FIX: Log a message if the message is not fully sent in case of TCP segmentation FIX: Seagull could core dump on check-value action FIX: Removed ntl library during compilation See: https://sourceforge.net/projects/gull [Less]

Seagull is a multi-protocol traffic generator. Especially targeted towards IMS, Seagull supports Diameter (RFC3588 and all applications) over TCP/SCTP and IPv4/IPv6 , TCAP (over SS7 or Sigtran), XCAP over HTTP and Radius. (1 comments)

I thought I would let you know of what is coming in Seagull before the end of October '06. * TLS transport: this has been added end of September in the source repository and will be officially released * SIP support: As a complement to SIPp, Seagull ... [More] will support also SIP to allow mixed SIP/DIAMETER/XCAP scenarios * Uniform distribution: some users have noticed that new scenario attempts are not placed evenly within the second (10 scenario per seconds is not one scenario every 10th of the second). The new version provides a uniform distribution of the calls * Poisson distribution: a contribution from Vincent Planat provides a Poisson distribution for the scenarios. It is aimed at emulating real networks by adding "randomness". * Evolution on distributions: because of the 2 changes mentioned, distributions are now more opened and more scenario distributions can be easily added * Actions: As a performance improvement, actions are now derived from a base action object. This allows to create new action very easily - with a limited understanding of Seagull's code * Programmatic control: Seagull can be remote controlled using a very simple http interface. With a single http request, you can change the scenario rate (immediately or following a ramp), dump Seagull's counters or quit. This allows to create GUIs, Eclipse plugins or Seagull clusters very easily. * Programmatic scripting: Using the new programmatic control interface, a simple Perl script is provided (as an example) to sequence a series of actions. A script, as parsed by this Perl program (launched with "./ctrl.pl http://192.168.0.2:10055/ scenario.txt") looks like: WAIT 5S SET RATE 20 WAIT 1M SET RATE 40 DUMP RAMP 100 IN 10S If useful, the scripting language could be extended I'm quite excited about all those features, and I am sure we will have the occasion to discuss all that on the mailing list when it comes out! [Less]

I thought I would let you know of what is coming in Seagull before the end of October '06. * TLS transport: this has been added end of September in the source repository and will be officially released * SIP support: As a complement to SIPp, Seagull ... [More] will support also SIP to allow mixed SIP/DIAMETER/XCAP scenarios * Uniform distribution: some users have noticed that new scenario attempts are not placed evenly within the second (10 scenario per seconds is not one scenario every 10th of the second). The new version provides a uniform distribution of the calls * Poisson distribution: a contribution from Vincent Planat provides a Poisson distribution for the scenarios. It is aimed at emulating real networks by adding "randomness". * Evolution on distributions: because of the 2 changes mentioned, distributions are now more opened and more scenario distributions can be easily added * Actions: As a performance improvement, actions are now derived from a base action object. This allows to create new action very easily - with a limited understanding of Seagull's code * Programmatic control: Seagull can be remote controlled using a very simple http interface. With a single http request, you can change the scenario rate (immediately or following a ramp), dump Seagull's counters or quit. This allows to create GUIs, Eclipse plugins or Seagull clusters very easily. * Programmatic scripting: Using the new programmatic control interface, a simple Perl script is provided (as an example) to sequence a series of actions. A script, as parsed by this Perl program (launched with "./ctrl.pl http://192.168.0.2:10055/ scenario.txt") looks like: WAIT 5S SET RATE 20 WAIT 1M SET RATE 40 DUMP RAMP 100 IN 10S If useful, the scripting language could be extended I'm quite excited about all those features, and I am sure we will have the occasion to discuss all that on the mailing list when it comes out! [Less]

I thought I would let you know of what is coming in Seagull before the end of October '06. * TLS transport: this has been added end of September in the source repository and will be officially released (0 comments)

I thought I would let you know of what is coming in Seagull before the end of October '06. * TLS transport: this has been added end of September in the source repository and will be officially released (0 comments)

New H248 and XCAP protocols were added, support of GT_SSN routing type for TCAP was added, check-value for strings was fixed, error messages were clarified, several other fixes. (0 comments)

New H248 and XCAP protocols were added, support of GT_SSN routing type for TCAP was added, check-value for strings was fixed, error messages were clarified, several other fixes. (0 comments)

New H248 and XCAP protocols were added, support of GT_SSN routing type for TCAP was added, check-value for strings was fixed, error messages were clarified, several other fixes. The next release will add support for SIP (this will consist in an XML dictionary only-no code), TLS transport and traffic pattern control (ramp, sin, burst).

New H248 and XCAP protocols were added, support of GT_SSN routing type for TCAP was added, check-value for strings was fixed, error messages were clarified, several other fixes. The next release will add support for SIP (this will consist in an XML dictionary only-no code), TLS transport and traffic pattern control (ramp, sin, burst).