<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>hi all, <br></span></div><div><br><span></span></div><div>i have configured the 2 asterisk servers between use IAX trunk,</div><div><br></div><div>server 1.</div><div>dahdi line connect to telecom company, <br></div><div><br></div><div>server 2.</div><div>dahdi lines connect to siemens hicom analogy PBX<br></div><div><br></div><div>hicom extention number is NXX,<br></div><div><br></div><div>in this time, we have one problem, clients dial to server 1 through dahdi, when operator transfer the call to NXX extension, than finish the call(NXX extension and clients) , in this time keep the dahdi line of server 1 and servers between iax trunk(not hangup).</div><div> how to fix it? what problem? <br></div><div><br></div><div><br></div><div style="font-family: times new roman, new york, times, serif;
font-size: 12pt;"><div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"><font face="Arial" size="2"><hr size="1"><b><span style="font-weight:bold;">From:</span></b> "asterisk-dev-request@lists.digium.com" <asterisk-dev-request@lists.digium.com><br><b><span style="font-weight: bold;">To:</span></b> asterisk-dev@lists.digium.com<br><b><span style="font-weight: bold;">Sent:</span></b> Tuesday, September 20, 2011 4:53 AM<br><b><span style="font-weight: bold;">Subject:</span></b> asterisk-dev Digest, Vol 86, Issue 111<br></font><br>Send asterisk-dev mailing list submissions to<br> <a ymailto="mailto:asterisk-dev@lists.digium.com" href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev"
target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>or, via email, send a message with subject or body 'help' to<br> <a ymailto="mailto:asterisk-dev-request@lists.digium.com" href="mailto:asterisk-dev-request@lists.digium.com">asterisk-dev-request@lists.digium.com</a><br><br>You can reach the person managing the list at<br> <a ymailto="mailto:asterisk-dev-owner@lists.digium.com" href="mailto:asterisk-dev-owner@lists.digium.com">asterisk-dev-owner@lists.digium.com</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of asterisk-dev digest..."<br><br><br>Today's Topics:<br><br> 1. [Code Review] Add test execution modes to the Asterisk<br> Testsuite (mjordan)<br> 2. Re: [Code Review] Add test execution modes to the Asterisk<br> Testsuite (mjordan)<br> 3.
Re: [Code Review] Tests for SIP handling of 484 Address<br> Incomplete; Incomplete application (opticron)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 19 Sep 2011 19:11:04 -0000<br>From: "mjordan" <<a ymailto="mailto:reviewboard@asterisk.org" href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>><br>Subject: [asterisk-dev] [Code Review] Add test execution modes to the<br> Asterisk Testsuite<br>To: "Paul Belanger" <<a ymailto="mailto:pabelanger@digium.com" href="mailto:pabelanger@digium.com">pabelanger@digium.com</a>><br>Cc: , mjordan <<a ymailto="mailto:reviewboard@asterisk.org" href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>>, Asterisk Developers<br> <<a ymailto="mailto:asterisk-dev@lists.digium.com"
href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a>><br>Message-ID: <<a ymailto="mailto:20110919191104.9181.4649@hotblack.digium.com" href="mailto:20110919191104.9181.4649@hotblack.digium.com">20110919191104.9181.4649@hotblack.digium.com</a>><br>Content-Type: text/plain; charset="utf-8"<br><br><br>-----------------------------------------------------------<br>This is an automatically generated e-mail. To reply, visit:<br><a href="https://reviewboard.asterisk.org/r/1447/" target="_blank">https://reviewboard.asterisk.org/r/1447/</a><br>-----------------------------------------------------------<br><br>Review request for Asterisk Developers and Paul Belanger.<br><br><br>Summary<br>-------<br><br>This patch adds the ability for global 'modes' to be defined for the Asterisk test-suite. Those settings in a mode can then be applied either at the base level in the runtests.py script, or by any test that inherits from
TestClass.py. As the global settings file makes use of the TestConfig class, all settings in the TestConfig class theoretically be applied on a global scale - although since each test checks its dependencies independently, only the Test Conditions are currently useful.<br><br>One additional settings was added - exclude-tests. This lets the global settings file explicitly call out tests (or subsets of tests) to not run without having to modify the tests.yaml file, and acts as a counterpart to the --test command line flag.<br><br>The only assumption made by this patch is that the global settings file is named 'test-config.yaml' and is located at the current run directory (the location of the runtests.py script).<br><br><br>Diffs<br>-----<br><br> /asterisk/trunk/README.txt 2346 <br> /asterisk/trunk/lib/python/asterisk/TestCase.py 2346 <br> /asterisk/trunk/lib/python/asterisk/TestConfig.py 2346 <br>
/asterisk/trunk/runtests.py 2346 <br> /asterisk/trunk/test-config.yaml PRE-CREATION <br> /asterisk/trunk/tests/apps/voicemail/authenticate_extensions/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/authenticate_invalid_mailbox/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/authenticate_invalid_password/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/authenticate_nominal/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_callback/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_delete/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_dialout/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_envelope/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_new_user/test-config.yaml 2346 <br>
/asterisk/trunk/tests/apps/voicemail/check_voicemail_nominal/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_reply/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/func_vmcount/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_external_notification/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_forwarding/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_forwarding_auto_urgent/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_nominal/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_priority/test-config.yaml 2346 <br><br>Diff: <a href="https://reviewboard.asterisk.org/r/1447/diff" target="_blank">https://reviewboard.asterisk.org/r/1447/diff</a><br><br><br>Testing<br>-------<br><br>Tested fast config mode, standard
config mode, and pessimistic config mode. Each worked as intended:<br>* Fast config mode successfully excluded those tests with a reactor_timeout greater than one minute<br>* Standard config mode applied no global settings<br>* Pessimistic config mode applied the Test Conditions to all tests inheriting from TestCase. Those tests that further defined test specific overrides applied those settings over the global conditions.<br><br><br>Thanks,<br><br>mjordan<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.digium.com/pipermail/asterisk-dev/attachments/20110919/1cfa2ea3/attachment-0001.htm" target="_blank">http://lists.digium.com/pipermail/asterisk-dev/attachments/20110919/1cfa2ea3/attachment-0001.htm</a>><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 19 Sep 2011 19:22:04 -0000<br>From: "mjordan" <<a ymailto="mailto:reviewboard@asterisk.org"
href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>><br>Subject: Re: [asterisk-dev] [Code Review] Add test execution modes to<br> the Asterisk Testsuite<br>To: "Paul Belanger" <<a ymailto="mailto:pabelanger@digium.com" href="mailto:pabelanger@digium.com">pabelanger@digium.com</a>><br>Cc: , mjordan <<a ymailto="mailto:reviewboard@asterisk.org" href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>>, Asterisk Developers<br> <<a ymailto="mailto:asterisk-dev@lists.digium.com" href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a>><br>Message-ID: <<a ymailto="mailto:20110919192204.10973.19418@hotblack.digium.com" href="mailto:20110919192204.10973.19418@hotblack.digium.com">20110919192204.10973.19418@hotblack.digium.com</a>><br>Content-Type: text/plain;
charset="utf-8"<br><br><br>-----------------------------------------------------------<br>This is an automatically generated e-mail. To reply, visit:<br><a href="https://reviewboard.asterisk.org/r/1447/" target="_blank">https://reviewboard.asterisk.org/r/1447/</a><br>-----------------------------------------------------------<br><br>(Updated Sept. 19, 2011, 2:22 p.m.)<br><br><br>Review request for Asterisk Developers and Paul Belanger.<br><br><br>Summary (updated)<br>-------<br><br>This patch adds the ability for global 'modes' to be defined for the Asterisk test-suite. Those settings in a mode can then be applied either at the base level in the runtests.py script, or by any test that inherits from TestClass.py. As the global settings file makes use of the TestConfig class, all settings in the TestConfig class can theoretically be applied on a global scale - although since each test checks its dependencies independently, only the Test
Conditions are currently useful.<br><br>One additional settings was added - exclude-tests. This lets the global settings file explicitly call out tests (or subsets of tests) to not run without having to modify the tests.yaml file, and acts as a counterpart to the --test command line flag.<br><br>The only assumption made by this patch is that the global settings file is named 'test-config.yaml' and is located at the current run directory (the location of the runtests.py script).<br><br><br>Diffs<br>-----<br><br> /asterisk/trunk/README.txt 2346 <br> /asterisk/trunk/lib/python/asterisk/TestCase.py 2346 <br> /asterisk/trunk/lib/python/asterisk/TestConfig.py 2346 <br> /asterisk/trunk/runtests.py 2346 <br> /asterisk/trunk/test-config.yaml PRE-CREATION <br> /asterisk/trunk/tests/apps/voicemail/authenticate_extensions/test-config.yaml 2346 <br>
/asterisk/trunk/tests/apps/voicemail/authenticate_invalid_mailbox/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/authenticate_invalid_password/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/authenticate_nominal/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_callback/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_delete/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_dialout/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_envelope/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_new_user/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_nominal/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/check_voicemail_reply/test-config.yaml 2346 <br>
/asterisk/trunk/tests/apps/voicemail/func_vmcount/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_external_notification/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_forwarding/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_forwarding_auto_urgent/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_nominal/test-config.yaml 2346 <br> /asterisk/trunk/tests/apps/voicemail/leave_voicemail_priority/test-config.yaml 2346 <br><br>Diff: <a href="https://reviewboard.asterisk.org/r/1447/diff" target="_blank">https://reviewboard.asterisk.org/r/1447/diff</a><br><br><br>Testing<br>-------<br><br>Tested fast config mode, standard config mode, and pessimistic config mode. Each worked as intended:<br>* Fast config mode successfully excluded those tests with a reactor_timeout greater than one minute<br>*
Standard config mode applied no global settings<br>* Pessimistic config mode applied the Test Conditions to all tests inheriting from TestCase. Those tests that further defined test specific overrides applied those settings over the global conditions.<br><br><br>Thanks,<br><br>mjordan<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.digium.com/pipermail/asterisk-dev/attachments/20110919/1f32e8b7/attachment-0001.htm" target="_blank">http://lists.digium.com/pipermail/asterisk-dev/attachments/20110919/1f32e8b7/attachment-0001.htm</a>><br><br>------------------------------<br><br>Message: 3<br>Date: Mon, 19 Sep 2011 20:52:20 -0000<br>From: "opticron" <<a ymailto="mailto:reviewboard@asterisk.org" href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>><br>Subject: Re: [asterisk-dev] [Code Review] Tests for SIP handling of<br> 484 Address
Incomplete; Incomplete application<br>To: "Paul Belanger" <<a ymailto="mailto:pabelanger@digium.com" href="mailto:pabelanger@digium.com">pabelanger@digium.com</a>>, <a ymailto="mailto:rmudgett@digium.com" href="mailto:rmudgett@digium.com">rmudgett@digium.com</a><br>Cc: , opticron <<a ymailto="mailto:reviewboard@asterisk.org" href="mailto:reviewboard@asterisk.org">reviewboard@asterisk.org</a>>, Asterisk Developers<br> <<a ymailto="mailto:asterisk-dev@lists.digium.com" href="mailto:asterisk-dev@lists.digium.com">asterisk-dev@lists.digium.com</a>><br>Message-ID: <<a ymailto="mailto:20110919205220.21476.57145@hotblack.digium.com" href="mailto:20110919205220.21476.57145@hotblack.digium.com">20110919205220.21476.57145@hotblack.digium.com</a>><br>Content-Type: text/plain; charset="utf-8"<br><br><br>-----------------------------------------------------------<br>This is an automatically generated
e-mail. To reply, visit:<br><a href="https://reviewboard.asterisk.org/r/1417/#review4381" target="_blank">https://reviewboard.asterisk.org/r/1417/#review4381</a><br>-----------------------------------------------------------<br><br>Ship it!<br><br><br>Both of the run-tests files need to be marked as executable, but other than that it looks like it's good to go.<br><br>- opticron<br><br><br>On Sept. 6, 2011, 12:45 p.m., mjordan wrote:<br>> <br>> -----------------------------------------------------------<br>> This is an automatically generated e-mail. To reply, visit:<br>> <a href="https://reviewboard.asterisk.org/r/1417/" target="_blank">https://reviewboard.asterisk.org/r/1417/</a><br>> -----------------------------------------------------------<br>> <br>> (Updated Sept. 6, 2011, 12:45 p.m.)<br>> <br>> <br>> Review request for Asterisk Developers, Paul Belanger and rmudgett.<br>> <br>> <br>> Summary<br>>
-------<br>> <br>> These tests are for the change under review for ASTERISK-17288 (<a href="https://reviewboard.asterisk.org/r/1416/" target="_blank">https://reviewboard.asterisk.org/r/1416/</a> ). They test SIP handling of 484 Address Incomplete and the Incomplete application's effect on chan_sip.<br>> <br>> <br>> This addresses bug ASTERISK-17288.<br>> <a href="https://issues.asterisk.org/jira/browse/ASTERISK-17288" target="_blank">https://issues.asterisk.org/jira/browse/ASTERISK-17288</a><br>> <br>> <br>> Diffs<br>> -----<br>> <br>> /asterisk/trunk/lib/python/asterisk/sipp.py 2057 <br>> /asterisk/trunk/tests/apps/incomplete/sip_incomplete/configs/ast1/extensions.conf PRE-CREATION <br>> /asterisk/trunk/tests/apps/incomplete/sip_incomplete/configs/ast1/manager.general.conf.inc PRE-CREATION <br>>
/asterisk/trunk/tests/apps/incomplete/sip_incomplete/configs/ast1/sip.conf PRE-CREATION <br>> /asterisk/trunk/tests/apps/incomplete/sip_incomplete/run-test PRE-CREATION <br>> /asterisk/trunk/tests/apps/incomplete/sip_incomplete/sipp/receiver1.xml PRE-CREATION <br>> /asterisk/trunk/tests/apps/incomplete/sip_incomplete/sipp/sender1.xml PRE-CREATION <br>> /asterisk/trunk/tests/apps/incomplete/sip_incomplete/test-config.yaml PRE-CREATION <br>> /asterisk/trunk/tests/apps/incomplete/tests.yaml PRE-CREATION <br>> /asterisk/trunk/tests/apps/tests.yaml 2057 <br>> /asterisk/trunk/tests/channels/SIP/handle_response_address_incomplete/configs/ast1/extensions.conf PRE-CREATION <br>> /asterisk/trunk/tests/channels/SIP/handle_response_address_incomplete/configs/ast1/manager.general.conf.inc PRE-CREATION <br>>
/asterisk/trunk/tests/channels/SIP/handle_response_address_incomplete/configs/ast1/sip.conf PRE-CREATION <br>> /asterisk/trunk/tests/channels/SIP/handle_response_address_incomplete/run-test PRE-CREATION <br>> /asterisk/trunk/tests/channels/SIP/handle_response_address_incomplete/sipp/uas1.xml PRE-CREATION <br>> /asterisk/trunk/tests/channels/SIP/handle_response_address_incomplete/test-config.yaml PRE-CREATION <br>> /asterisk/trunk/tests/channels/SIP/tests.yaml 2057 <br>> <br>> Diff: <a href="https://reviewboard.asterisk.org/r/1417/diff" target="_blank">https://reviewboard.asterisk.org/r/1417/diff</a><br>> <br>> <br>> Testing<br>> -------<br>> <br>> Without the patch for ASTERISK-17288, both tests will fail. The application Incomplete test will fail with a timeout to the t extension, as it received no additional information to dial (and the SIP test will fail as the 484 response will
never be forwarded to the dialing party). The SIP handle response test will fail with a hangup cause of 111.<br>> <br>> <br>> Thanks,<br>> <br>> mjordan<br>> <br>><br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.digium.com/pipermail/asterisk-dev/attachments/20110919/e2f4058d/attachment.htm" target="_blank">http://lists.digium.com/pipermail/asterisk-dev/attachments/20110919/e2f4058d/attachment.htm</a>><br><br>------------------------------<br><br>_______________________________________________<br>--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br><br>AstriCon 2010 - October 26-28 Washington, DC<br>Put in your talk proposal: <a href="http://www.bit.ly/speak-astricon2010" target="_blank">http://www.bit.ly/speak-astricon2010</a><br><br>asterisk-dev mailing list<br>To UNSUBSCRIBE
or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br><br>End of asterisk-dev Digest, Vol 86, Issue 111<br>*********************************************<br><br><br></div></div></div></body></html>