[asterisk-bugs] [JIRA] Feedback Entered: (DAHLIN-298) dahdi-linux 2.6.1 fails to detect ringing

Tue Aug 14 13:28:07 CDT 2012

     [ https://issues.asterisk.org/jira/browse/DAHLIN-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jaco Kroon updated DAHLIN-298:
------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

Thanks for the assistance Shaun.  Much appreciated.

Your commit:

commit 11f8933f0794f4fde7e80778de7bc357d632bb0c
Author: Shaun Ruffell <sruffell at digium.com>
Date:   Tue Aug 14 13:08:51 2012 -0500

    wip: decrease polarity changes to 3

To your dahlin-298-1 branch did the trick.  From looking at the diff this used to be four.  This is good enough for me.

As an asside, this is the quickest I've ever seen asterisk enter into the dialplan from an analog since forever.  Usually gave about two to three rings before asterisk even picked up on it - it's instantaneous now, much, much better.

Thanks for all your hard work.

> dahdi-linux 2.6.1 fails to detect ringing
> -----------------------------------------
>
>                 Key: DAHLIN-298
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-298
>             Project: DAHDI-Linux
>          Issue Type: Bug
>      Security Level: None
>          Components: wctdm24xxp
>    Affects Versions: 2.6.1
>         Environment: Linux, kernel 2.6.37
> Asterisk 1.8.13.1 and 1.8.15.0
> dahdi-tools 2.6.1
> libpri 1.4.12
>            Reporter: Jaco Kroon
>            Assignee: Jaco Kroon
>            Severity: Critical
>         Attachments: 0001-wctdm24xxp-wip-Add-ring-state-debug-flags.patch
>
>
> wctdm24xxp module won't pick up incoming ringing since upgrading to dahdi-linux 2.6.1.
> After discussion with sruffel on #asterisk and a bit of git bisecting the quilty commit is this one:
> df509300791f1bb5b4b652c2adcfbcc016f789e7 is the first bad commit
> commit df509300791f1bb5b4b652c2adcfbcc016f789e7
> Author: Shaun Ruffell <sruffell at digium.com>
> Date:   Tue Aug 30 16:38:32 2011 +0000
>     wctdm24xxp: Use time interval for debouncing FXO ring detect.
>     
>     Do not assume the ring detection function is called for every frame.
>     Also change the debounce logic to a state machine to clarify what state
>     a port is in and unify the technique for debouncing the various signals.
>     
>     Signed-off-by: Shaun Ruffell <sruffell at digium.com>
>     Acked-by: Russ Meyerriecks <rmeyerriecks at digium.com>
>     
>     git-svn-id: http://svn.asterisk.org/svn/dahdi/linux/trunk@10168 a0bf4364-ded3-4de4-8d8a-66a801d63aff
> :040000 040000 b5f6e1244fae106d3d5537258c532fa1ce1e302e 759c00e4d73a9417e9afa0266b038e3fc01d8a27 Mdrivers
> Module parameters:
> opermode=SOUTHAFRICA boostringer=1 fastringer=1 latency=7

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira