Summary: | ASTERISK-11848: pri loop TestClient/TestServer fails: server SEND DTMF 8 | ||
Reporter: | Tzafrir Cohen (tzafrir) | Labels: | |
Date Opened: | 2008-04-14 16:31:27 | Date Closed: | 2009-03-26 16:18:40 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Applications/app_test |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) testserver-debug-output.txt | |
Description: | I connect a loop between two PRI ports (one is net and one is CPE). The channels in the "net" part go into a context in which extension 224 runs TestServer() . Channel 35 is one of the channels of the CPE port. I run: originate Zap/35/224 application TestClient 35 Expected result: a successful test. Actual result: TestClint succeds. TestServer fails at 'SEND DTMF 8'. It seems that the channel is hung up before the DTMF is properly sent. Workaround: add a sleep of one second in testclient_exec right after identifying the DTMF 8 and efore hanging up. This seems to work, but I'm not sure why the whole thing suddenly broke. Hence I don't consider it a patch (yet?). | ||
Comments: | By: Leif Madsen (lmadsen) 2008-10-14 12:18:03 Could have sworn I commented on this issue previously, but I guess not. Can this only be reproduced with a PRI circuit looped, or can it be done with another technology? I don't have any PRI cards here in order to attempt to reproduce the issue with. By: Leif Madsen (lmadsen) 2009-01-05 09:48:56.000-0600 I don't even seem to get as far as you. I performed the following tests: 'originate Local/224@bug12442 application TestClient 35' and across to a separate virtual machine using SIP: 'originate SIP/cluster2/testserver application TestClient 0123456789' The output from the 2nd test is the following, although it is almost identical to the other test: /var/log/asterisk/testresults/0123456789-server.txt SERVERCHAN: SIP/cluster2-0b3bf860 SERVERTEST ID: 0123456789 ANSWER: PASS SEND DTMF 1: PASS WAIT DTMF 2: PASS MEASURENOISE: FAIL (-1) -- END TEST-- I did a test to make sure the DTMF was getting across fine, and it is. Just dialed with a softphone from one server to the other, and then used Read() to capture some digits and output the result. That seemed to work fine. I'm attaching a file with the output of the DTMF and debugging information that was output during the test as well. By: Digium Subversion (svnbot) 2009-03-26 16:07:33 Repository: asterisk Revision: 184388 U branches/1.4/apps/app_test.c ------------------------------------------------------------------------ r184388 | dvossel | 2009-03-26 16:07:33 -0500 (Thu, 26 Mar 2009) | 8 lines pri loop TestClient/TestServer fails: server SEND DTMF 8 app_test was failing when sending the last DTMF digit, 8, because of the 100ms pause issued after DTMF is sent. During this pause the other side would hang up causing the test to look like it failed. Now the other side waits a second before hanging up. (closes issue ASTERISK-11848) Reported by: tzafrir ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=184388 By: Digium Subversion (svnbot) 2009-03-26 16:09:38 Repository: asterisk Revision: 184389 _U trunk/ U trunk/apps/app_test.c ------------------------------------------------------------------------ r184389 | dvossel | 2009-03-26 16:09:37 -0500 (Thu, 26 Mar 2009) | 14 lines Merged revisions 184388 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r184388 | dvossel | 2009-03-26 16:07:32 -0500 (Thu, 26 Mar 2009) | 8 lines pri loop TestClient/TestServer fails: server SEND DTMF 8 app_test was failing when sending the last DTMF digit, 8, because of the 100ms pause issued after DTMF is sent. During this pause the other side would hang up causing the test to look like it failed. Now the other side waits a second before hanging up. (closes issue ASTERISK-11848) Reported by: tzafrir ........ ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=184389 By: Digium Subversion (svnbot) 2009-03-26 16:17:45 Repository: asterisk Revision: 184391 _U branches/1.6.0/ U branches/1.6.0/apps/app_test.c ------------------------------------------------------------------------ r184391 | dvossel | 2009-03-26 16:17:45 -0500 (Thu, 26 Mar 2009) | 21 lines Merged revisions 184389 via svnmerge from https://origsvn.digium.com/svn/asterisk/trunk ................ r184389 | dvossel | 2009-03-26 16:09:37 -0500 (Thu, 26 Mar 2009) | 14 lines Merged revisions 184388 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r184388 | dvossel | 2009-03-26 16:07:32 -0500 (Thu, 26 Mar 2009) | 8 lines pri loop TestClient/TestServer fails: server SEND DTMF 8 app_test was failing when sending the last DTMF digit, 8, because of the 100ms pause issued after DTMF is sent. During this pause the other side would hang up causing the test to look like it failed. Now the other side waits a second before hanging up. (closes issue ASTERISK-11848) Reported by: tzafrir ........ ................ ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=184391 By: Digium Subversion (svnbot) 2009-03-26 16:18:40 Repository: asterisk Revision: 184394 _U branches/1.6.1/ U branches/1.6.1/apps/app_test.c ------------------------------------------------------------------------ r184394 | dvossel | 2009-03-26 16:18:39 -0500 (Thu, 26 Mar 2009) | 21 lines Merged revisions 184389 via svnmerge from https://origsvn.digium.com/svn/asterisk/trunk ................ r184389 | dvossel | 2009-03-26 16:09:37 -0500 (Thu, 26 Mar 2009) | 14 lines Merged revisions 184388 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r184388 | dvossel | 2009-03-26 16:07:32 -0500 (Thu, 26 Mar 2009) | 8 lines pri loop TestClient/TestServer fails: server SEND DTMF 8 app_test was failing when sending the last DTMF digit, 8, because of the 100ms pause issued after DTMF is sent. During this pause the other side would hang up causing the test to look like it failed. Now the other side waits a second before hanging up. (closes issue ASTERISK-11848) Reported by: tzafrir ........ ................ ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=184394 |