[asterisk-dev] [Code Review] 4274: Testsuite: Ensure that outbound registrations with bad auth do not result in an infinite loop.

Mark Michelson reviewboard at asterisk.org
Wed Dec 17 13:13:48 CST 2014

This is an automatically generated e-mail. To reply, visit:

(Updated Dec. 17, 2014, 7:13 p.m.)

Review request for Asterisk Developers.


* Modified SIPp scenario to use a better scenario name and removed irrelevant comment about "rrs"
* Modified test-config.yaml to check for Registry event

Repository: testsuite


This is a test for the contents of review 4273.

This test sets up a SIPp scenario that expects two REGISTER requests to be sent from Asterisk. Each of these REGISTER requests is responded to with a 401. Asterisk should completely cease sending registrations after the second 401 is received. The SIPp scenario stays alive a little after the final 401 is sent to ensure that Asterisk does not send any further REGISTER requests.

Diffs (updated)

  /asterisk/trunk/tests/channels/pjsip/registration/outbound/tests.yaml 6075 
  /asterisk/trunk/tests/channels/pjsip/registration/outbound/auth_loop/test-config.yaml PRE-CREATION 
  /asterisk/trunk/tests/channels/pjsip/registration/outbound/auth_loop/sipp/uas-reg-401.xml PRE-CREATION 
  /asterisk/trunk/tests/channels/pjsip/registration/outbound/auth_loop/configs/ast1/pjsip.conf PRE-CREATION 

Diff: https://reviewboard.asterisk.org/r/4274/diff/


This test fails without the changes from /r/4273. The test succeeds with the changes applied.


Mark Michelson

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20141217/785c09ad/attachment.html>

More information about the asterisk-dev mailing list