<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://reviewboard.asterisk.org/r/4077/">https://reviewboard.asterisk.org/r/4077/</a>
</td>
</tr>
</table>
<br />
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('https://reviewboard.asterisk.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for Asterisk Developers.</div>
<div>By jbigelow.</div>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
testsuite
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">This tests unregistering outbound registrations that are registered using the PJSIPUnregister AMI action. It ensures that Asterisk sends a REGISTER message with an Expires header of '0' upon executing the PJSIPUnregister AMI action and that AMI Registry events are present with a status of "Unregistered". The test uses all combinations of IPv4/IPv6 and UDP/TCP.
Upon an outbound registration registering, the PJSIPUnregister action is executed to unregister it. SIPp is used as the registrar to respond when Asterisk registers and unregisters where the Expires header is checked.
Note: This test currently fails due to the following Asterisk bugs:
* https://issues.asterisk.org/jira/browse/ASTERISK-24411
* https://issues.asterisk.org/jira/browse/ASTERISK-24414
The SIPp scenario contains a pause at the end to work around ASTERISK-24414 for the time being. The 'expectedResult' property is set within the YAML file to expect the test to fail (and thus pass) while ASTERISK-24411 is unresolved however there appears to be a bug in testsuite as it's still marked as failed.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">* Ran test in a shell loop 300 times without failure (with patch for Asterisk applied from ASTERISK-24411 and work around for ASTERISK-24414)
* Ran test several times without patch applied from ASTERISK-24411 which constantly failed as expected.
* Ran test several times without work around for ASTERISK-24414 which frequently failed as expected.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>/asterisk/trunk/tests/channels/pjsip/registration/outbound/unregister/unauthed/test-config.yaml <span style="color: grey">(PRE-CREATION)</span></li>
<li>/asterisk/trunk/tests/channels/pjsip/registration/outbound/unregister/unauthed/sipp/unregister.xml <span style="color: grey">(PRE-CREATION)</span></li>
<li>/asterisk/trunk/tests/channels/pjsip/registration/outbound/unregister/unauthed/configs/ast1/pjsip.conf <span style="color: grey">(PRE-CREATION)</span></li>
<li>/asterisk/trunk/tests/channels/pjsip/registration/outbound/unregister/tests.yaml <span style="color: grey">(PRE-CREATION)</span></li>
<li>/asterisk/trunk/tests/channels/pjsip/registration/outbound/tests.yaml <span style="color: grey">(5726)</span></li>
</ul>
<p><a href="https://reviewboard.asterisk.org/r/4077/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>