<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/4444/">https://reviewboard.asterisk.org/r/4444/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On February 27th, 2015, 9:39 a.m. CST, <b>Scott Griepentrog</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I updated the chan_dahdi [channels] configuration with cadences matching the Bellcore spec and retested for both CID detection and DR pattern recognition. Results are certain patterns (especially DR2, DR4, and DR5) exhibit failure rate on CID detection approaching 50%. As the DR1 pattern has a 0% failure rate, I'm confident that it's still a remaining DR problem. Additionally, the DR pattern numbers (#,#,#) are inconsistent for certain cadences. DR2 for example may be 359,297,259, sometimes 359,0,0, sometimes 297,0,0. The inconsistent DR patterns may or may not be related to the CID failure, although there appears to be a correlation. There may be leftover artifacts on CID detection between calls, as repeating a failed call tends to correlate to another failure.</pre>
</blockquote>
<p>On February 27th, 2015, 9:40 a.m. CST, <b>Scott Griepentrog</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I forgot to paste in my cadences:
usedistinctiveringdetection=yes
;Bellcore-r1:
;60(2/4)
cadence=2000,-4000
;Bellcore-r2:
;60(.3/.2,1/.2,.3/4)
cadence=300,200,1000,200,300,-4000
;Bellcore-r3:
;60(.8/.4,.8/4)
cadence=800,400,800,-4000
;Bellcore-r4:
;60(.4/.2,.3/.2,.8/4)
cadence=400,200,300,200,800,-4000
;Bellcore-r5:
;60(.2/.2,.2/.2,.2/.2,1/4)
cadence=200,200,200,200,200,200,1000,-4000
;Bellcore-r6:
;60(.2/.4,.2/.4,.2/4)
cadence=200,400,200,400,200,-4000
;Bellcore-r7:
;60(.4/.2,.4/.2,.4/4)
cadence=400,200,400,200,400,-4000
;Bellcore-r8:
;60(0.25/9.75)
cadence=250,-9750
</pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I had an error in my cadence configuration. For the testing above I was actually running:
cadence=125,125,2000,-4000
cadence=250,250,500,1000,250,250,500,-4000
cadence=125,125,125,125,125,-4000
cadence=1000,500,2500,-5000
cadence=1000,1000,1000,1000,-4000
cadence=500,500,1000,2000,2000,-4000
Once corrected to proper bellcore set below, I still encountered ~50% CID failure and 75% dring detection failure (i.e. all 3 numbers 0 on patterns > dr1).
cadence 'r1' added: 2000,-4000
cadence 'r2' added: 300,200,1000,200,300,-4000
cadence 'r3' added: 800,400,800,-4000
cadence 'r4' added: 400,200,300,200,800,-4000
cadence 'r5' added: 200,200,200,200,200,200,1000,-4000
cadence 'r6' added: 200,400,200,400,200,-4000
cadence 'r7' added: 400,200,400,200,400,-4000
cadence 'r8' added: 250,-9750
</pre>
<br />
<p>- Scott</p>
<br />
<p>On February 23rd, 2015, 6:51 p.m. CST, rmudgett wrote:</p>
<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 rmudgett.</div>
<p style="color: grey;"><i>Updated Feb. 23, 2015, 6:51 p.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Bugs: </b>
<a href="https://issues.asterisk.org/jira/browse/ASTERISK-24825">ASTERISK-24825</a>
</div>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
Asterisk
</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;">The distinctive ring feature interferes with detecting Caller ID and
appears to have been broken for years. What happens is if you have a
ring-ring cadence as used in the UK you get too many DAHDI events for the
distinctive ring pattern array and Caller ID detection is aborted. I
think when Zapata/DAHDI added the ring begin event it broke distinctive
ring. More events happen than before and the code does no filtering of
which event times are recorded in the pattern array.
* Made distinctive ring only record the ringt count when the ring ends
instead of on just any DAHDI event. Distinctive ring can be ring,
ring-ring, ring-ring-ring, or different ring durations for the up to three
rings.
* Fixed the distinctive ring detection enable (chan_dahdi.conf option
usedistinctiveringdetection) to be per port instead of somewhat per port
and somewhat global. This has been broken since v1.8.
* Fixed using the default distinctive ring context when the detected
pattern does not match any configured dringX patterns. The default
context did not get set when the previous call was a matched distinctive
ring pattern and the current call is not matched. This has been broken
since v1.8.
* Made distinctive ring have no effect on Caller ID detection when it is
disabled. Caller ID detection just monitors for 10 seconds before giving
up.
* Fixed leak of struct callerid_state memory when a polarity reversal
during Caller ID detection causes the incoming call to be aborted.
</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;">Tested the following scenarios for US (ring) and UK (ring-ring) ring cadences:
1) usedistinctiveringdetection=no
2) usedistinctiveringdetection=yes with distinctiveringaftercid=no
3) usedistinctiveringdetection=yes with distinctiveringaftercid=yes
* Caller-ID was detected for each call
* The configured distinctive ring dringX pattern was detected and the specified context set.
</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>/branches/11/channels/sig_analog.c <span style="color: grey">(432173)</span></li>
<li>/branches/11/channels/sig_analog.h <span style="color: grey">(432173)</span></li>
<li>/branches/11/channels/chan_dahdi.c <span style="color: grey">(432173)</span></li>
<li>/branches/11/UPGRADE.txt <span style="color: grey">(432173)</span></li>
</ul>
<p><a href="https://reviewboard.asterisk.org/r/4444/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>