[asterisk-bugs] [Asterisk 0018005]: chan_dahdi does not detect polarity change when using AEX800P/wctdm24xxp

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Sep 21 12:27:09 CDT 2010


The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18005 
====================================================================== 
Reported By:                pruiz
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18005
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.11 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 suspended
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-09-16 19:54 CDT
Last Modified:              2010-09-21 12:27 CDT
====================================================================== 
Summary:                    chan_dahdi does not detect polarity change when
using AEX800P/wctdm24xxp
Description: 
My POTS telco (Telefonica/Spain) uses polarity switch for answer and hangup
signalling, and as such I've been using TDM4XXP cards with
hanguponpolarityswitch/answeronpolarityswitch=yes for years without problem
on asterisk 1.4.x..

However, a couple of weeka ago we bougth a new AEX800P with 6 FXO ports,
and I've been unable to make it work as it seem to completely ignore
polarity changes.

I've tried with different combinations of options at chan_dahdi, and with
different wctdm24xxp module options w/o any success..

Also, setting debug and verbose to 99, and loading wctdm24xxp with
debug=1, the only log relating to polarity which I from dmesg or asterisk
full logs,  get during a call are:

chan_dahdi.c: Ignore possible polarity reversal on line seizure
chan_dahdi.c: Setting IDLE polarity due to ring. Old polarity was 0


Here is chan_dadi.conf:

[channels]
context=from-pstn
signalling=fxs_ks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=no
canpark=no
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=256
rxgain=5.0
txgain=5.0
relaxdtmf=yes
callgroup=1
pickupgroup=1
hardwaredtmf=yes
;mwimonitor=fsk
;waitfordialtone=15000
adsi=yes
sendcalleridafter=2
cidsignalling=bell
cidstart=ring
language=es
polarityevents=yes
answeronpolarityswitch=yes
hanguponpolarityswitch=yes
polarityswitchondelay=1
faxdetect=both
;faxdetect=no
;callprogress=no
;usedistinctiveringdetection=yes
tonezone=6      ; 6 == Spain

group=0
channel => 1-6
====================================================================== 

---------------------------------------------------------------------- 
 (0127202) lmadsen (administrator) - 2010-09-21 12:27
 https://issues.asterisk.org/view.php?id=18005#c127202 
---------------------------------------------------------------------- 
I'm going to suspend and close this issue as this appears to be a hardware
related issue. I'd suggest you contact Digium support where an issue will
be opened in a fashion that will help resolve the issue quicker. If Digium
supports redirects you back here, then please reopen this issue. Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-21 12:27 lmadsen        Note Added: 0127202                          
2010-09-21 12:27 lmadsen        Status                   new => closed       
2010-09-21 12:27 lmadsen        Resolution               open => suspended   
======================================================================




More information about the asterisk-bugs mailing list