Transforming call flow diagrams into SIPp files

You can transform call flow diagrams to SIPp files.

About this task

The SIPp is an open source Session Initiation Protocol (SIP) service traffic generator that is used for unit and performance testing of SIP applications. The SIPp reads the XML file and generates the appropriate traffic. The transformation accepts a UML package or model as source, and a folder as target.

Latest modeling with Next Generation Networks tools articles from developerWorks

Session Initiation Protocol (SIP) technical support

The To, From, Via, and CSeq headers are required by the SIP specification and Rational® Performance Tester on each message. For the Via header, use the performance tester defined keyword <<local-host>> to insert the IP address of the local host. For the call flow diagrams that describe a scenario between multiple participants, apply the <<Tester>> stereotype to all the lifelines that must have a test case.

Note:

For the call flow diagrams that describe a scenario between multiple participants, the stereotype of all the lifelines must have a test case with the <<Tester>> stereotype.

Procedure

Click File > New > Other > Transformations > Transformation Configuration, and click Next.
In the New Transformation Configuration window, type a name for the new transformation.
In the Forward Transformation field, select NGN Modeling Toolkit > Call Flow to SIPp Transformation.
Select the UML model and a folder as target, and click Finish.

Results

The transformation iterates over all UML packages of the source model. If the transformation configuration option, Generate Folders for Packages is checked, an output folder for each package is created in the target folder. The name of the folder is the same as the name of the package. If unchecked, the SIPp files will be created in the target folder itself. For each package, the transformation iterates over all call flows, UML collaborations with a <<Call Flow>> stereotype value. For each call flow, the transformation iterates over the lifelines with a <<Tester>> stereotype value. For each lifeline, a SIPp file is created in the output folder corresponding to the UML package containing it. The name of the SIPp file will be <Call Flow Name>_<Lifeline Name>.xml.

The UML documentation for the <<Call Flow>> will be at the top of the SIPp file as XML comments. The SIPp file is populated according to the messages originating or terminating the lifeline.

Note:

A UML collaboration can contain multiple interactions or sequence diagrams. The generation of SIPp files is supported for an interaction in the collaboration. The transform validation will report an error if there are more than one interaction within a call flow.

The following SIPp elements do not have a modeling representation and will not be supported:

<nop>
<sendCmd>
<recvCmd>
<label>
<ResponseTimeRapertition>
<CallLengthRepartition>
<Globals>
<User>
<Reference>

Feedback