| Summary: | DAHLIN-00332: TDM410 fails to detect ring on FXO in port 3 with empty port 0. | ||
| Reporter: | Shaun Ruffell (sruffell) | Labels: | |
| Date Opened: | 2013-12-20 12:45:24.000-0600 | Date Closed: | 2014-04-09 09:43:52 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | wctdm24xxp |
| Versions: | 2.8.0.1 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) b31cd5a2e4a41e.patch | |
| Description: | As reported in http://forums.asterisk.org/viewtopic.php?f=1&t=88767&start=0, the wctdm24xxp fails to properly detect ringing when opermode is set to SAUDIARABIA. | ||
| Comments: | By: Shaun Ruffell (sruffell) 2013-12-20 12:49:20.507-0600 The following patch on top of 2.8.0.1 will resolve the issue. {noformat} wget "https://issues.asterisk.org/jira/secure/attachment/48968/b31cd5a2e4a41e.patch" -O - | patch -p1 {noformat} By: Shaun Ruffell (sruffell) 2013-12-20 14:20:30.120-0600 Committed [(3933ffd350 "wctdm24xxp: Reset module specific type information on probe")|http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commit;h=3933ffd3505374ce8850fee067ad3949dc552d49] to the master DAHDI branch. The bug exposed had less to do with the opermode, and more to do with the specific layout of modules on a TDM410 card. Specifically nothing installed in port 1, and an FXO module installed in port 3. By: Shaun Ruffell (sruffell) 2014-04-09 09:43:52.640-0500 Fix in 2.9.0. | ||