[asterisk-dev] [Code Review] 3182: testsuite: LinkedID Propagation test
Scott Griepentrog
reviewboard at asterisk.org
Mon Feb 17 15:01:52 CST 2014
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/3182/
-----------------------------------------------------------
(Updated Feb. 17, 2014, 3:01 p.m.)
Review request for Asterisk Developers.
Changes
-------
Removed extraneous debug message
Bugs: ASTERISK-23120
https://issues.asterisk.org/jira/browse/ASTERISK-23120
Repository: testsuite
Description
-------
This monitors bridge enter/exit and CEL events, and builds
a picture of which channels are bridged together, and when
their LinkedID changes, and then verifies that each change
is correct.
Note: The BridgeEnter and CEL 'BRIDGE_ENTER' events can be
in either order - so wait for both to arrive before making
a judgement on the LinkedID.
This test can be added to any other bridging test to add a
layer of LinkedId Propagation checking to it.
This test has now been added to the existing bridge_action
test rather than have a separate test for it.
The bridge_action test has been changed to use an event to
trigger channel creation sequence which resolves a problem
with creation order determination.
Diffs (updated)
-----
/asterisk/trunk/tests/bridge/bridge_action/test-config.yaml 4722
/asterisk/trunk/tests/bridge/bridge_action/bridge_action.py 4722
/asterisk/trunk/lib/python/asterisk/linkedid_check.py PRE-CREATION
Diff: https://reviewboard.asterisk.org/r/3182/diff/
Testing
-------
This test is now running consistently without errors. It sill contains a warning on incorrect linkedid on CEL events which would have to be resolved in Asterisk.
Thanks,
Scott Griepentrog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20140217/49e2ce51/attachment.html>
More information about the asterisk-dev
mailing list