From e9bc9ae06c74ef833af635ad7f8f3063c07c518c Mon Sep 17 00:00:00 2001 From: Shaun Ruffell Date: Thu, 15 Mar 2012 15:03:27 +0000 Subject: 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 Signed-off-by: Shaun Ruffell Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=10473 git-svn-id: http://svn.asterisk.org/svn/dahdi/linux/branches/2.6@10481 a0bf4364-ded3-4de4-8d8a-66a801d63aff --- drivers/dahdi/wctdm24xxp/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/dahdi/wctdm24xxp/base.c b/drivers/dahdi/wctdm24xxp/base.c index 07813da..039c379 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: -- cgit v1.2.3