diff options
| author | Shaun Ruffell <sruffell@digium.com> | 2012-03-13 22:12:37 +0000 |
|---|---|---|
| committer | Shaun Ruffell <sruffell@digium.com> | 2012-03-13 22:12:37 +0000 |
| commit | 4c8604274794ec9cb5fee22d98aa70c1ab822f29 (patch) | |
| tree | c0750b14e5e1cc01feb32e2fb18e3d51d9ced52d | |
| parent | 00a4ff1bd81d8f3774792539cb50712231d72bfe (diff) | |
wctdm24xxp: Shorten RINGOFF debounce interval from 512ms to 128ms.
In commit r10168 "wctdm24xxp: Use time interval for debouncing FXO ring
detect" [1], I inadvertently changed the debounce interval of the RINGOFF
event from 128ms to 512ms. The result was a potential failure to detect CID,
depending on line conditions, since Asterisk would bump the rx gains on the
channel in the middle of the CID spill as opposed to before the CID spill.
This fixes a regression first introduced in DAHDI-Linux 2.6.0.
[1] http://svnview.digium.com/svn/dahdi?view=revision&revision=10168
Internal-Issue-ID: DAHDI-951
Reported-and-Tested-by: Jack Wilson <ljwilson@digitalav.com>
Signed-off-by: Shaun Ruffell <sruffell@digium.com>
git-svn-id: http://svn.asterisk.org/svn/dahdi/linux/trunk@10473 a0bf4364-ded3-4de4-8d8a-66a801d63aff
| -rw-r--r-- | drivers/dahdi/wctdm24xxp/base.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/dahdi/wctdm24xxp/base.c b/drivers/dahdi/wctdm24xxp/base.c index 10bf9fb..d324a2a 100644 --- a/drivers/dahdi/wctdm24xxp/base.c +++ b/drivers/dahdi/wctdm24xxp/base.c @@ -1904,7 +1904,7 @@ static void wctdm_fxo_ring_detect(struct wctdm *wc, struct wctdm_module *mod) if (!is_fxo_ringing(fxo)) { set_ring(fxo, DEBOUNCING_RINGOFF); fxo->ringdebounce_timer = - wc->framecount + ringdebounce / 2; + wc->framecount + ringdebounce / 8; } break; case DEBOUNCING_RINGOFF: |