Skip to content

SIP User Documentation Chapter 7

Jump to bottom
Vincent Hérilier edited this page Nov 26, 2019 · 1 revision

Result structure produced by SIP specific samplers

PREVIOUS CHAPTER | TOC | NEXT CHAPTER

You can check the XML result structure of SIP specific samplers both in GUI and command line mode. You can change the format to CSV but note that the CSV output cannot be opened in GUI mode.

Related concepts

See Samplers, Listeners and Assertions page.
SIPCommandSampler is a sampler that can be added to Thread Groups. Sampler results can be displayed through JMeter native elements, for example, through Listener elements.

Checking sampler result structure in GUI mode

About this task

The results structure of a sampler depends on sampler configuration.

Procedure
  1. Start Apache JMeter in GUI mode.
  2. Add and configure a SIP node element and a corresponding Thread Group with a SIPCommandSampler in your Test Plan.
  3. Add a Listener element to your Test Plan.
  4. Start the scenario.
  5. Click on the Listener element and check the result.
    If you added the View Results Tree listener element to your Test Plan, you can display the following details for SIPCommandSampler elements: – Result tree structure: If the sampler is executed without an error, a green icon is shown in the result tree structure. The icon turns red if any of the following conditions apply: – The sampler itself fails. – A Response assertion that is added to the sampler returns an error. – In the Sampler result tab of the View Results Tree element, the Response message is listed with the result of the sampler. – If it is executed without an error, the complete text of the sent or received SIP message is included in the Response message field, as shown in the following example:
    It is the response message of a sampler that is configured to send a 200 OK message. For samplers that are configured to check the reception of a message, the Success string is added to indicate that the messages was received.
Response message: SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.228.130:6688;branch=z9hG4bK-393831-ef69cd6bd13ea89cc0c334f919f529aa
CSeq: 1 INVITE
Call-ID: mylovelycallidvalue5
From: "TheBguy" <sip:[email protected]>;tag=9876
To: "TheAguy" <sip:[email protected]>;tag=1234
Content-Type: application/sdp
Contact: "The A guy" <sip:[email protected]:6677>

– If the sampler fails, the Failure string appears in the Response message field followed by the reason for the error, as shown in the following example:

Response message: Failure. differences :
CSeq check failed: CSeq:3 BYE:CSeq: 2UPDATE.

It is the response message of a sampler that is configured to check the reception of a SIP message. The first value (3 BYE) is the expected value, the second value (2 UPDATE) is the received value.

NOTE: If the issue is caused by multiple headers, all the differences are listed.

Checking the result structure in command line mode

Procedure
  1. Start JMeter in command line mode with the following command -l option:
$ jmeter -l {jtl_file}

As <{jtl_file}>, for example, result.jtl.

The result of the scenario execution will be included in this file.

  1. Add and configure a SIP node element and a corresponding Thread Group with a SIPCommandSampler in your Test Plan and start the scenario.
  2. Open the output file GUI in mode.

Opening result XML files in GUI mode

Procedure
  1. Start Apache JMeter in GUI mode and open the Test Plan that the result XML file is associated to.

NOTE: Any Test Plan can be used for this purpose but it is recommended to open the associated Test Plan because it helps to interpret the results.

  1. Add the View Results Tree Listener to the Test Plan and click it.
  2. Click Browse and browse for the result file that was saved in XML output format.
  3. Select the result file.
Results

The result tree structure is displayed in the GUI.

PREVIOUS CHAPTER | TOC | NEXT CHAPTER

© Copyright 2019-2020 Hewlett Packard Enterprise Development LP

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.
You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.

User documentation:

Clone this wiki locally