The values on the Gm/Gm Node Measurement tabs report SIP registration/subscriber related measurements for the MME/SGW Nodal and IMS Node test cases.
In the default view, the Reports tab displays the Summary view, which summarizes the measurements for the test session. If your test includes multiple test cases, you can view the report for a single test case by changing the report view...
Unless otherwise noted, cumulative values report the number of occurrences or rates calculated since the start of the test, and per-interval values report the number of occurrences or rates calculated during the interval. You can view either by changing the measurement values...
Elapsed Time is the first measurement on every tab. It reports the amount of time between the start of the test and the end of the report interval.
Test Iteration reports the current iteration in a repeating test session. It is only displayed when a Number of Iterations is defined for the test session.
The following measurements record the number and types of messages exchanged between the UE and IMS Node.
SCRIPT Successes — Total number of SCRIPT Successes.
SCRIPT Failures — Total number of SCRIPT Failures.
SCRIPT in Progress — Total number of SCRIPTS in Progress.
Total SIP Messages Sent — Total number of SIP Messages sent.
Total SIP Messages Received — Total number of SIP Messages received.
Total SIP Messages — Total number of SIP Messages sent and received.
SIP REFER Messages — Total number of SIP Refer - sent and received.
SIP Call Setup Count — The total number of SIP Call Setup messages received.
SIP Registration Setup Count — The total number of SIP Registration Setup messages received.
SIP Average Registration Setup — The average time, in microseconds, required to register a SIP Call.
SIP Minimum Registration Setup — The minimum time, in microseconds, required to register a SIP Call.
SIP Maximum Registration Setup — The maximum time, in microseconds, required to register a SIP Call.
SIP DE-Registration Setup Count — The total number of SIP De-Registration Setup messages received.
SIP Average De-Registration Setup — The average time, in microseconds, required to deregister a SIP Call.
SIP Minimum De-Registration Setup — The minimum time, in microseconds, required to deregister a SIP Call.
SIP Maximum De-Registration Setup — The maximum time, in microseconds, required to deregister a SIP Call.
SIP Call Setup Count — The total number of SIP Call Setup messages received.
SIP Average Call Setup — The average time, in microseconds, required to setup a SIP Call.
SIP Minimum Call Setup — The minimum time, in microseconds, required to setup a SIP Call.
SIP Maximum Call Setup — The maximum time, in microseconds, required to setup a SIP Call.
SIP Call Teardown Count — Number of SIP Teardown commands received/processed.
SIP Average Teardown Time — The average time, in microseconds, required to teardown a SIP Call.
SIP Minimum Teardown Time — The minimum time, in microseconds, required to teardown a SIP Call.
SIP Maximum Teardown Time — The maximum time, in microseconds, required to teardown a SIP Call.
SIP MT Call Attempts — The total number of SIP MT Call Attempts. It has the same meaning as the existing "SIP Call Attempts", which includes the case where MO/MT tries to send SIP INVITE but failed.
SIP MT Call Rejects — Call Rejection is defined as the Originator or Terminator rejected call. This measurement does not include SIP INVITE send failures. This is different from the existing measurement "Call Failures", which includes the case. This includes these two scenarios as well as other failures : 1. A 607 SIP response code indicates specifically that the MT rejected the call. 2. A 608 SIP response code indicated that an intermediary (machine or process) rejected that call.
SIP MT Call Reject Rate — MT Call Reject Rate = Ratio of VoNR/VoLTE calls rejected to call attempts from terminating side.
SIP MT Call Setup Count — The total number of SIP MT Call Setup messages received.
SIP MT Call Retain Successes — "retain" means actual call duration >= expected call duration. Note: If Supplementary Services is enabled, call duration is uncertain, so Call Retain Successes cannot be measured and will always be zero. Otherwise, MO side always know the expected call duration from configured Call Hold Time on GUI. However, if one test case is configured with All Terminate roles, then currently there will not be any way to get the expected call duration, so MT Call Retain Successes will be zero. If a test case emulate both MO and MT sides, then LS will use the Call Hold Time as the expected call duration for both MO and MT. Also, 500 milliseconds tolerance time will be added in the implementation to cover any transmission latency. For example, if Call Hold Time is configured to 20 seconds, but actually call duration from a test is 199500 ms, then this call will be included in the Call Retain Successes.
SIP MT Call Retain Success Rate — MT Call Retain Success Rate = Ratio of VoNR/VoLTE call retain success to call setup success from terminating side.
SIP MT Call Setup Success Time — Total time for successful VoNR/VoLTE call setup from terminating side.
SIP MT Call Abnormal Terminations — An Abnormal Termination as the SIP BYE message did not happen according to the protocol. In other words, instead of receiving a normal release with a BYE message, a SIP code was inserted in its place (487, etc). Abnormal Termination include:
SIP BYE is never sent out either by SIP subscriber or IMS proxy or SBC for an established call - this may be caused by test session abort, test server recycle, etc.
SIP BYE is sent out by SIP subscriber with a Reason Header that specifies a cause, which is >=400 (See https://www.rfc-editor.org/rfc/rfc3326 for optional Reason Header)
SIP BYE is sent out with no Reason Header but receives a response with error code >=400
SIP BYE is sent out with a Reason Header that specifies a cause, which is <400, but receives a response with error code >=400
NOTE : Landslide is not currently including optional Reason Header when it's sending SIP BYE request, but the customer is able to add a Reason Header with any cause with supplementary services/SIP message editor. If the Reason Header in BYE or response code in ACK is added/modified using Landslide SIP message editor, then Landslide will not be able to report Call Abnormal Termination measurement from the SIP message sending side. Only receiving side will be able to report such measurement. Abnormal Terminations do NOT include the cases that actual call duration is shorter than expected, since it is already reflected with the Call Retain Failure measurement.
SIP MT Call Abnormal Termination Rate — MT Call Abnormal Term Rate = Ratio of VoNR/VoLTE call abnormally terminated to call setup success from terminating side.
SIP MO Call Attempts — The total number of SIP MO Call Attempts. It has the same meaning as the existing "SIP Call Attempts", which includes the case where MO/MT tries to send SIP INVITE but failed.
SIP MO Call Rejects — Call Rejection is defined as the Originator or Terminator rejected call. This measurement does not include SIP INVITE send failures. This is different from the existing measurement "Call Failures", which includes the case. This includes these two scenarios as well as other failures : 1. A 607 SIP response code indicates specifically that the MT rejected the call. 2. A 608 SIP response code indicated that an intermediary (machine or process) rejected that call.
SIP MO Call Reject Rate — MO Call Reject Rate = Ratio of VoNR/VoLTE calls rejected to call attempts from originating side.
SIP MO Call Setup Count — The total number of SIP MO Call Setup messages received.
SIP MO Call Retain Successes — "retain" means actual call duration >= expected call duration.
SIP MO Call Retain Success Rate — MO Call Retain Success Rate = Ratio of VoNR/VoLTE call retain success to call setup success from originating side.
SIP MO Call Setup Success Time — Total time for successful VoNR/VoLTE call setup from originating side.
SIP MO Call Abnormal Terminations — An Abnormal Termination as the SIP BYE message did not happen according to the protocol. In other words, instead of receiving a normal release with a BYE message, a SIP code was inserted in its place (487, etc). Abnormal Termination include:
SIP BYE is never sent out either by SIP subscriber or IMS proxy or SBC for an established call - this may be caused by test session abort, test server recycle, etc.
SIP BYE is sent out by SIP subscriber with a Reason Header that specifies a cause, which is >=400 (See https://www.rfc-editor.org/rfc/rfc3326 for optional Reason Header)
SIP BYE is sent out with no Reason Header but receives a response with error code >=400
SIP BYE is sent out with a Reason Header that specifies a cause, which is <400, but receives a response with error code >=400
NOTE 1. Landslide is not currently including optional Reason Header when it's sending SIP BYE request, but the customer is able to add a Reason Header with any cause with supplementary services/SIP message editor. If the Reason Header in BYE or response code in ACK is added/modified using Landslide SIP message editor, then Landslide will not be able to report Call Abnormal Termination measurement from the SIP message sending side. Only receiving side will be able to report such measurement. Abnormal Terminations do NOT include the cases that actual call duration is shorter than expected, since it is already reflected with the Call Retain Failure measurement.
SIP MO Call Abnormal Termination Rate —MO Call Abnormal Term Rate = Ratio of VoNR/VoLTE call abnormally terminated to call setup success from originating side.
Dedicated Bearer Reservation Count — The number of dedicated bearer reservation requests received.
| NOTE: The Dedicated Bearer Reservation Time (average/minimum/maximum) is called as follows. For a calling party it is the time between sending INVITE and sending UPDATE; for a called party this is the time between sending 183 and sending 180 (ringing). |
Dedicated Bearer Average Reservation Time — The average time required for dedicated bearer reservation.
Dedicated Bearer Minimum Reservation Time — The minimum time required for dedicated bearer reservation.
Dedicated Bearer Maximum Reservation Time — The maximum time required for dedicated bearer reservation.
SIP Call Successes — The number of SIP call that were successfully established.
SIP Call Failures — The number of SIP call that failed due to one of the errors
SIP Call Attempts — The number of initial SIP Call Setup attempted. Although this value is the sum of Successes and Failures, the equation may not hold true at any given time during session processing since some sessions may be in a transient state when the measurements are collected.
SIP Registration Failures — The number of unsuccessful SIP registration attempts.
SIP Registration Retries — The number SIP Calls that were sent again for registration.
SIP REGISTER Messages — Total number of SIP Register messages- sent and received (for registration).
SIP REGISTER Messages Received— The number of SIP Register messages received (for registration).
SIP REGISTER Messages Retransmissions — Total number of SIP Register message retransmitted. (for registration).
SIP REGISTER Messages Sent — The number of SIP Register messages sent (for registration).
SIP INVITE Messages — Total number of SIP Invite messages sent and received.
SIP INVITE Messages Received — Number of SIP Invite messages received.
SIP MCPTT INVITE Messages Received — Number of SIP MCPTT Invite messages received.
SIP INVITE Messages Retransmissions— Total number of SIP Invite messages retransmitted.
SIP INVITE Messages Sent — Number of SIP Invite messages sent .
SIP ACK Messages — Total number of acknowledgements - Sent and received .
SIP ACK Messages Received — Number of acknowledgements received.
SIP ACK Messages Sent — Number of acknowledgements Sent.
SIP BYE Messages — Total number of SIP Bye messages - sent and received.
SIP BYE Messages Received — Number of SIP Bye messages received.
SIP BYE Messages Retransmissions— Total number of SIP Bye messages retransmitted.
SIP BYE Messages Sent — Number of SIP Bye messages sent.
SIP OPTION Messages — Total number of messages sent and received with option-tag, for example, pre-condition option-tag, outbound option-tag for multiple registrations (RFC 5626 [92])
SIP OPTION Messages Received — Number of messages received with option-tag, for example, pre-condition option-tag, outbound option-tag for multiple registrations (RFC 5626 [92])
SIP OPTION Messages Retransmissions— Total number of SIP Option messages retransmitted.
SIP OPTION Messages Sent — Number of messages sent with option-tag, for example, pre-condition option-tag, outbound option-tag for multiple registrations (RFC 5626 [92])
SIP CANCEL Messages — Total number of SIP CANCEL - sent and received.
SIP CANCEL Messages Received — Number of SIP CANCEL registration requests received.
SIP CANCEL Messages Retransmissions— Total number of SIP Cancel messages retransmitted.
SIP CANCEL Messages Sent — Number of SIP CANCEL registration requests sent.
SIP PRACK Messages — Total number of acknowledgements sent and received using the precondition mechanism. (RFC 3312 [30] as updated by RFC 4032 [64])
SIP PRACK Messages Received — Number of acknowledgements received using the precondition mechanism. (RFC 3312 [30] as updated by RFC 4032 [64])
SIP PRACK Messages Retransmissions— Total number of SIP Prack messages retransmitted.
SIP PRACK Messages Sent — Number of acknowledgements sent using the precondition mechanism. (RFC 3312 [30] as updated by RFC 4032 [64])
SIP UPDATE Messages — Total number of update messages sent and received
SIP UPDATE Messages Received — Number of update messages received.
SIP UPDATE Messages Retransmissions— Total number of SIP Update messages retransmitted.
SIP UPDATE Messages Sent — Number of update messages sent.
SIP SUBSCRIBE Messages — Total number of SIP Subscribe messages sent and received.
SIP SUBSCRIBE Messages Received — Number of SIP Subscribe messages received.
SIP SUBSCRIBE Messages Retransmissions— Total number of SIP Subscribe messages retransmitted.
SIP SUBSCRIBE Messages Sent — Number of SIP Subscribe messages sent.
SIP NOTIFY Messages — Total number of NOTIFY messages sent and received (with the Subscription-State header field set with relevant notifications, for example, terminate, register multiple Public User Ids, etc)
SIP NOTIFY Messages Received — Number of NOTIFY messages received (with the Subscription-State header field set with relevant notifications, for example, terminate, register multiple Public User Ids, etc)
SIP NOTIFY Messages Retransmissions— Total number of SIP Notify messages retransmitted.
SIP NOTIFY Messages Sent — Number of NOTIFY messages sent (with the Subscription-State header field set with relevant notifications, for example, terminate, register multiple Public User Ids, etc)
SIP PUBLISH Messages — Total number of PUBLISH messages sent and received (with the Subscription-State header field set with relevant notifications, for example, terminate, register multiple Public User Ids, etc)
SIP PUBLISH Messages Received — Number of PUBLISH messages received (with the Subscription-State header field set with relevant notifications, for example, terminate, register multiple Public User Ids, etc)
SIP PUBLISH Messages Retransmissions— Total number of SIP PUBLISH messages retransmitted.
SIP PUBLISH Messages Sent — Number of SIP PUBLISH messages sent (with the Subscription-State header field set with relevant notifications, for example, terminate, register multiple Public User Ids, etc)
SIP REFER Messages Received — Number of SIP Refer requests received.
SIP REFER Messages Retransmissions— Total number of SIP Refer messages retransmitted.
SIP REFER Messages Sent — Number of SIP Refer requests sent.
SIP 100 Trying Messages — Total number of 100 Trying messages sent and received.
SIP 100 Trying Messages Received — Number of 100 Trying messages received.
SIP 100 Trying Messages Sent — Number of 100 Trying messages sent.
SIP 180 Ringing Messages — Total number of 180 Ringing response sent and received. (Typically, this first response is a 180 (Ringing) or 200 (OK) response if the remote UA supports the "integration of resource management in SIP" extension, or a re-INVITE request if the remote UA does not support the "integration of resource management in SIP" extension.)
SIP 180 Ringing Messages Received — Number of 180 Ringing response received.
SIP 180 Ringing Messages Sent — Number of 180 Ringing response sent.
SIP 1xx Other Messages — Total number of 1xx Other messages sent and received. (See RFC 3261).
SIP 1xx Other Messages Received — Number of 1xx Other messages received. (See RFC 3261).
SIP 1xx Other Messages Sent — Number of 1xx Other messages sent. (See RFC 3261).
SIP 200 OK Messages — Total number of 200 OK messages- sent and received (See RFC 3261).
SIP 200 OK Messages Received — Number of 200 OK messages received . (See RFC 3261).
SIP 200 OK Messages Sent — Number of 200 OK messages sent.. (See RFC 3261).
SIP 3xx Messages — Total Number of 3xx messages- sent and received. (See RFC 3261).
SIP 3xx Messages Received — Number of 3xx messages received. (See RFC 3261).
SIP 3xx Messages Sent — Number of 3xx messages Sent. (See RFC 3261).
SIP 4xx Messages — Total Number of 4xx Messages - sent and Received. (See RFC 3261).
SIP 4xx Messages Received — Total Number of 4xx Messages received. (See RFC 3261).
SIP 4xx Messages Sent — Total Number of 4xx Messages sent. (See RFC 3261).
SIP 5xx Messages — Total number of SIP 5xx messages - sent and received (See RFC 3261).
SIP 5xx Messages Received — Number of SIP 5xx messages received (See RFC 3261).
SIP 5xx Messages Sent — Number of SIP 5xx messages sent (See RFC 3261).
SIP 6xx Messages — Total number of SIP 6xxx messages - sent and received (See RFC 3261).
SIP 6xx Messages Received — Number of SIP 6xxx messages received (See RFC 3261).
SIP 6xx Messages Sent — Number of SIP 6xxx messages sent (See RFC 3261).
MSRP MO Messages — Number of Mobile Originated messages sent.
MSRP MT Messages — Number of Mobile Terminate messages sent.
MSRP SEND Messages — Number of MSRP SEND messages sent.
MSRP 200 OK Messages — Total Number of MSRP 200 OK messages.
MSRP 4xx Messages — Total Number of MSRP 4xx messages.
MSRP 5xx Messages — Total Number of MSRP 5xx messages.
MSRP Direct File Transfer Sent Messages — Total Number of Direct File Transfer messages sent.
MSRP Direct File Transfer Received Messages — Total Number of Direct File Transfer messages Received.
MSRP Direct File Transfer Error Messages — Total Number of Direct File Transfer Error messages.
MPS Request Received — Total Number of MPS Request received messages.
MPS Request Ignored Unknown Resource — Total Number of MPS Request Ignored Unknown Resource messages.
MPS Request Forbidden Unknown Resource — Total Number of MPS Request Forbidden Unknown Resource messages.
MPS Request Forbidden Not Subscribed — Total Number of MPS Request Forbidden Not Subscribed messages.
MPS Request Forbidden Too High — Total Number of MPS Request Forbidden Too High messages.
MPS Request Permitted — Total Number of MPS Request Permitted messages.
Call Transfer Requests Received — Total Number of Call Transfer Requests messages (available when IMS Node Mode = B2BUA) .
Call Transfer Successes — Total Number of Call Transfer Success messages (available when IMS Node Mode = B2BUA) .
Call Transfer Failures — Total Number of Call Transfer Failure messages (available when IMS Node Mode = B2BUA) .
Number of Active Conferences — Total Number of Active Conferences (available when IMS Node Mode = B2BUA).
Number of Inactive Conferences — Total Number of Inactive Conferences (available when IMS Node Mode = B2BUA).
Number of Participants — Total Number of Participants (available when IMS Node Mode = B2BUA).
RTCP Floor Request Sent — Total Number of RTCP Floor Request messages sent.
RTCP Floor Granted Received — Total Number of RTCP Floor Granted messages received.
RTCP Floor Takens Received — Total Number of RTCP Floor Taken messages received.
RTCP Floor Idles Received — Total Number of RTCP Floor Idle messages received.
RTCP Floor Releases Sent — Total Number of RTCP Floor Release messages sent.