[asterisk-bugs] [JIRA] Issue Comment Edited: (DAHLIN-298) dahdi-linux 2.6.1 fails to detect ringing
Shaun Ruffell (JIRA)
noreply at issues.asterisk.org
Tue Aug 14 00:03:07 CDT 2012
[ https://issues.asterisk.org/jira/browse/DAHLIN-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195748#comment-195748 ]
Shaun Ruffell edited comment on DAHLIN-298 at 8/14/12 12:01 AM:
----------------------------------------------------------------
jkroon, Thanks for bisecting to find the offending commit. The attached patch (which is also on my dahlin-298-1 branch on git://github.com/sruffell/dahdi-linux ) will hopefully allow us to see the transitions the ring detector is going through.
I would load the driver, then enable debug "echo 1 > /sys/module/wctdm24xxp/parameters/debug" and you should see output like:
{code}
6121.922070] wctdm24xxp 0000:0a:07.0: Ring State: RINGOFF -> DEBOUNCING_RINGING_NEGATIVE (-65) (0x4c)
[ 6121.933044] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_NEGATIVE -> DEBOUNCING_RINGING_POSITIVE (-36) (0x2c)
[ 6121.956017] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_POSITIVE -> DEBOUNCING_RINGING_NEGATIVE (-6) (0x4c)
[ 6121.974023] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_NEGATIVE -> DEBOUNCING_RINGING_POSITIVE (-16) (0x2c)
[ 6121.995021] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_POSITIVE -> DEBOUNCING_RINGING_NEGATIVE (-3) (0x4c)
[ 6122.014023] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_NEGATIVE -> RINGING (-6) (0x2c)
[ 6122.014031] wctdm24xxp 0000:0a:07.0: RING on WCTDM/1/0!
[ 6122.032027] wctdm24xxp 0000:0a:07.0: Ring State: RINGING -> DEBOUNCING_RINGOFF (30) (0xc)
[ 6122.034013] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGOFF -> RINGING (4) (0x4c)
[ 6122.051030] wctdm24xxp 0000:0a:07.0: Ring State: RINGING -> DEBOUNCING_RINGOFF (-36) (0xc)
[ 6122.054013] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGOFF -> RINGING (1) (0x2c)
[ 6122.071027] wctdm24xxp 0000:0a:07.0: Ring State: RINGING -> DEBOUNCING_RINGOFF (36) (0xc)
[ 6122.073014] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGOFF -> RINGING (9) (0x4c)
[ 6122.090058] wctdm24xxp 0000:0a:07.0: Ring State: RINGING -> DEBOUNCING_RINGOFF (-42) (0xc)
{code}
was (Author: sruffell):
jkroon, The attached patch (which is also on my dahlin-298-1 branch on git://github.com/sruffell/dahdi-linux ) will hopefully allow us to see the transitions the ring detector is going through.
I would load the driver, then enable debug "echo 1 > /sys/module/wctdm24xxp/parameters/debug" and you should see output like:
{code}
6121.922070] wctdm24xxp 0000:0a:07.0: Ring State: RINGOFF -> DEBOUNCING_RINGING_NEGATIVE (-65) (0x4c)
[ 6121.933044] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_NEGATIVE -> DEBOUNCING_RINGING_POSITIVE (-36) (0x2c)
[ 6121.956017] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_POSITIVE -> DEBOUNCING_RINGING_NEGATIVE (-6) (0x4c)
[ 6121.974023] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_NEGATIVE -> DEBOUNCING_RINGING_POSITIVE (-16) (0x2c)
[ 6121.995021] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_POSITIVE -> DEBOUNCING_RINGING_NEGATIVE (-3) (0x4c)
[ 6122.014023] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGING_NEGATIVE -> RINGING (-6) (0x2c)
[ 6122.014031] wctdm24xxp 0000:0a:07.0: RING on WCTDM/1/0!
[ 6122.032027] wctdm24xxp 0000:0a:07.0: Ring State: RINGING -> DEBOUNCING_RINGOFF (30) (0xc)
[ 6122.034013] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGOFF -> RINGING (4) (0x4c)
[ 6122.051030] wctdm24xxp 0000:0a:07.0: Ring State: RINGING -> DEBOUNCING_RINGOFF (-36) (0xc)
[ 6122.054013] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGOFF -> RINGING (1) (0x2c)
[ 6122.071027] wctdm24xxp 0000:0a:07.0: Ring State: RINGING -> DEBOUNCING_RINGOFF (36) (0xc)
[ 6122.073014] wctdm24xxp 0000:0a:07.0: Ring State: DEBOUNCING_RINGOFF -> RINGING (9) (0x4c)
[ 6122.090058] wctdm24xxp 0000:0a:07.0: Ring State: RINGING -> DEBOUNCING_RINGOFF (-42) (0xc)
{code}
> 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
More information about the asterisk-bugs
mailing list