Changes between and

  • Fix bug which prevented binary fields from matching data defined in tables. (SCEN-433)

  • Fix an invalid validation failure in which valid dialogs were being misreported as ambiguous dialogs. (SCEN-1257)

  • Fix bug where a SELECT field matched when it should not match, when the value matched some rows which didn’t overlap with the previous selection. (SCEN-1256)

Changes between and

  • Fix false positives in validation rules related to field generators, for roles in which generator inputs are defined in incoming messages. (SCEN-1247)

  • Auto populate any missing generator inputs during scenario validation, for schema fields which support auto population. (SCEN-1248)

  • Added 'reset-stats' command to reset simulator statistics. (SCEN-74)

  • Support setting the same ALIAS between both an integer field and a character string field. (SCEN-1253)

  • Support fields with integer values larger than 2^63-1. Schemas can make use of this support on a field by field basis. (SCEN-1255)

Changes between and

  • The Scenario Simulator package now includes HTTP scenario pack 1.0.1, which includes support for HTTP digest authentication. (SCEN-1230) Note: existing HTTP scenarios must be updated using the scenario migration tool:

    $ ./ -migrate /path/to/your/http-scenario.scen
  • When matching incoming dialogs by the remote address: exclude local endpoints, and require exactly one matching remote endpoint. This makes incoming HTTP dialog matching reliable for configurations in which the simulator runs on the same host as the remote endpoint. Caveat: incoming HTTP dialogs from hosts on which there are multiple remote endpoints are now rejected, as remote HTTP endpoints can only be distinguished by the host address. (SCEN-1241)

  • Added support for case-insensitive character string types. (SCEN-277)

Scenario Simulator/Editor

  • Added HTTP support via the HTTP scenario pack

  • Updated SIP scenario pack from 1.0.2 to 1.0.3, and the Diameter scenario pack from 2.5.0 to 2.6.0, including various big fixes and performance improvements.

  • Updated the CGIN scenario pack from 1.5.1 to 1.5.2. Note: scenarios written with the previous version will need to be updated using the scenario editor or the scenario migration tool.

  • Various bug fixes and improvements related to the scenario simulator and the scenario editor.

  • Each scenario pack now has its own changelog in the CHANGELOGS directory.

    Note: The Scenario Simulator and Scenario Editor now require JDK 7.

Scenario Simulator

Scenario Simulator improvements and bug fixes

  • Scenario Simulator 2.2.0 has support for flexible message ordering (SCEN-423, SCEN-716) The scenario simulator is now more flexible about message ordering for incoming messages across multiple dialogs. refer to the Opencloud Developer Protal for details.
  • Fixed misleading output "Non-match for preferred scenario", when the scenario definition matches and only one scenario is loaded. (SCEN-835)

  • Added a validation rule to detect the use of differing hard-coded values on fields which share the same ALIAS. (SCEN-877)

  • Fixed a number of issues related to replacing a scenario definition encountered when loading a scenario definition with the same name as an existing scenario. Prior to this change, some configuration related to the previous scenario was not cleared, leading to confusing output from the 'print-config' command. (SCEN-888)

Scenario Editor improvements and bug fixes

(Note that the Scenario Editor's seperate changelog has now been removed;
 changes to the editor are now included in this document.)
  • Added support for drag & drop loading of scenario files. Scenario files can now be dragged into the main editor interface (from a filesystem browser or similar) to load them. (SCEN-20)

  • Renaming a role will also rename any dialogs which use that role if they are using the default naming convention of 'RoleA-RoleB'. (SCEN-50)

  • When creating a new scenario the scenario rename dialog will now be displayed. (SCEN-67)

  • Scenario editor now saves configuration settings to it’s temporary directory, so settings will persist over separate sessions. (SCEN-144)

  • Elements which have children with warnings will now show up in a different color to elements which have children with errors. (SCEN-573)

  • Added support to the scenario editor for opening scenarios in an existing scenario editor instance. The flags -x and -n can be used to disable this new behaviour. See the usage message for further documentation. (SCEN-850)

  • Increased the amount of RAM available to the scenario editor when launched using the script. (SCEN-862)

Included Scenario Pack improvements and bug fixes

SIP Scenario Pack

  • The new SIP Scenario pack changes the way that dialogs are differentiated in SIP scenarios, to align scenario dialogs more closely with SIP dialogs as defined in RFC 3261. The local and remote tags (From and To tags) are now included in the identity of a SIP dialog, along with the Call-ID.

    NB: This requires changes to only a very specific type of scenario, in which
    multiple SIP dialogs were being specified in the same scenario dialog, with
    the same Call-ID, between the same pair of roles. Scenarios matching this
    pattern should now model the two SIP dialogs as separate dialogs in the scenario.
    Other scenarios will not be affected by this change. (SCEN-652)
  • Fixed an error which occurred when using a media line inside an SDP media description in a scenario. (SCEN-826)

  • Added a SIP validation rule: the first request in a scenario cannot have a To tag. (SCEN-827)

  • Added a SIP validation rule: In a forked dialog with a response as the first message, the first message must have a To tag. (SCEN-828)

  • Added a SIP validation rule: a response cannot be the first message between the two roles in a scenario. (SCEN-829)

  • Added a SIP validation rule: The Call-ID, From tag and To tag must be the same for all messages in a dialog, and must be unique between dialogs. (SCEN-830)

  • Improved auto-generation of From and To tags when using AUTO. (SCEN-833)

  • Added support for AUTO generation of seq-id values in the CSeq header for outgoing SIP requests. (SCEN-834)

  • SIP examples now uses the new IGNORED_ORDER_GROUP attribute for messages that could be received in different orders. (SCEN-841)

  • SIP scenario validation now detects the case where multiple SIP dialogs are included in a single dialog in the scenario. (SCEN-851)

  • Improved user feedback related to the use of the Via field in scenarios. (SCEN-855)

  • The Simulator now provides more information when an incoming dialog matches no scenario, or when a message times out. (SCEN-860)

  • Improved the error handling related to processing of stray SIP responses. (SCEN-874)

  • Improved the auto-generation of Via values when the ViaSentByAddress is not configured. (SCEN-875)

  • Improved the auto-generation of Via fields in SIP responses when using AUTO. (SCEN-876)

  • The "tag" field in the From header is now mandatory. (SCEN-810)

  • Fixed an unnecessary warning in SIP scenario validation about missing lr URI parameters. (SCEN-893)

  • Support for the Target-Dialog header has been added. (SCEN-896)

Scenario Simulator

New Features and improvements

  • Added the Diameter Scenario Pack to the Scenario Simulator, supporting Diameter base accounting, CCA, Ro/Gy, Sh, Gx and Rf (SCEN-241)

  • Added support for recursive data types in the scenario editor and simulator. In SIP, the Via, Route and Record-Route fields are now infinitely recursive, rather than just recursing to a limited depth. Existing scenarios are not affected. (SCEN-82)

  • SIP validation: ensure that the Call-ID is defined in a message, so that it’s value is unique among all other dialogs in the same pair of roles. (SCEN-740)

  • The ALIAS drop-down in the scenario editor is now sorted alphabetically (SCEN-187)

  • When printing enumeration values, the ordinal value is now included along with the name (for example, "NATIONAL (1)"). The reverse is true when printing integer values which also have a name (for example, "1 (NATIONAL)"). (SCEN-733)


  • SIP: Fixed a bug where the simulator was generating and inserting a tag into the To header, when the tag was not present, in situations when it shouldn’t. (SCEN-504)

  • The Simulator now provides more detail in descibing non-matching array values. (SCEN-112)

  • When starting the Scenario Simulator, the 'log file' option (-l) now handles absolute paths. (SCEN-467)

  • Fixed a possible NullPointerException that occurred when sending an Invite from a SIP endpoint (SCEN-602)

  • Fixed potential classpath issues on Windows, which could cause runtime failures. (SCEN-608)

  • Changed line endings in some .bat files, to make them easier to open on Windows. (SCEN-609)

  • Fixed a bug which caused scenario failures when binding a negative value to an ALIAS. (SCEN-648)

  • The performance of the first session of a scenario has been improved to avoid retransmits when using SIP over UDP (SCEN-665)

  • The Scenario Editor now handles changing protocols with a scenario file open more gracefully (SCEN-671)

  • The Scenario Editor now performs validation to ensure an answer is provided in the correct direction (SCEN-672)

  • Fixed a bug which prevented loading of scenarios which contained absent fields (with COUNT 0), where the type of that field was a record type which included mandatory fields. (SCEN-705)

  • Fixed an issue that could cause the Scenario Editor to freeze when expanding two attributes (SCEN-711)

  • SIP validation: Improved warning message when the Request URI transport and Via transport differ. (SCEN-743)

Scenario Simulator

Scenario Simulator 2.0 is the first stand-alone version of the simulator.
Prior to 2.0, the application was bundled with the CGIN Connectivity
The Scenario Simulator package includes:
  • The Scenario Simulator itself.

  • The Scenario Editor.

  • SIP support, via the SIP Scenario Pack.

  • IN support, via the IN Scenario Pack.

    Note that the IN Scenario Pack contains all IN protocols supported by the
    CGIN Connectivity Pack. See the Scenario Simulator DevPortal space for
    more details:
    Other new features in Scenario Simulator 2.0 include:
  • Much improved simulator performance, particularly in scenarios that use dialog correlation.

  • Support for Scenario Packs. New protocols will now be delivered independently from the Scenario Simulator via downloads from the DevPortal.

  • Many other bugfixes and improvements.

    Users of the Scenario Simulator bundled with CGIN should refer to the
    Scenario Simulator DevPortal space for information on upgrading and new