[Home]

Summary:DAHLIN-00163: DAHDI/TDM410P does not detect ANSWER
Reporter:Jonathan M Bradshaw (jonathanmbradshaw)Labels:
Date Opened:2009-12-08 06:51:03.000-0600Date Closed:2019-05-31 09:38:39
Priority:MinorRegression?No
Status:Closed/CompleteComponents:wctdm24xxp
Versions:2.2.0.2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) DIALSTATUSisANSWER.txt
( 1) DIALSTATUSisCANCEL.txt
( 2) full.17
( 3) no-answer-audio.raw
( 4) no-answer-audio.wav
Description:Outgoing calls to the POT's via DAHDI and a TDM410P do not detect the remote party ANSWER.  The call is generated using a .cal file (attached) and the call is never dispatched to the internal extension as expected.

A review of the RAW audio file (dahdi_monitor) shows that the call was connected.

****** ADDITIONAL INFORMATION ******

Asterisk Version : Asterisk 1.4.26.2
Linux Version : 2.6.27.24-78.2.53.fc9.x86_64 (FEDORA)

.cal File
Channel: DAHDI/4/0800*******
CallerID: "********** **********" <49080*********>
MaxRetries: 0
RetryTime: 300
WaitTime: 45

Context: inHouseNMBRs
Extension: ****
Priority: 1
AlwaysDelete: Yes
Archive: No

/etc/dahdi/system.conf
echocanceller=mg2,      1-4

# Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1" (MASTER)
fxoks=1
fxoks=2
fxsks=3
fxsks=4

# Global data
loadzone        = us
defaultzone     = us

/etc/asterisk/chan_dahdi.conf
answeronpolarityswitch=yes
hanguponpolarityswitch=yes
callprogress=yes
context=outsideLines
signalling=fxs_ks
callerid=asreceived
mailbox=1234
group=0

callerid="POT's" <6003>
channel => 3

callerid="POT's" <6004>
channel => 4
Comments:By: Alec Davis (alecdavis) 2009-12-09 12:58:22.000-0600

which DAHDI version? DAHDI does the polarity reversal detection.

Using a phone connected to your FXS ports do normal outgoing calls get answered?

I see your config has 'answeronpolarityswitch=yes' and 'hanguponpolarityswitch=yes', which requires the telco to switch polarity on each of these events, you didn't mention that you have confirmed this, whether you subscribe to them, and that indeed that they do reverse.
By: Jonathan M Bradshaw (jonathanmbradshaw) 2009-12-09 13:22:44.000-0600

dahdi version is 2.2.0.2

polarity reversal detection was switched on when I observed "polarity reversal ignored" messages in the log.  FYI : The device connected to the TDM410P port is a SBV5121 VoIP Cable model from Motorola.

The Motorola device is working and calls are being connected, I say this because I have used dahdi_monitor to catch and review sound traffic on the line.

A call on the port using a standard phone works as expected


By: dpage (dpage) 2010-01-05 10:48:38.000-0600

I seem to be getting the same issue using DAHDI 2.2.1-rc2.
By: Jared Smith (jsmith) 2010-01-05 12:02:33.000-0600

Just to clarify... in many countries (the United States being the most obvious one), the telco doesn't do *anything* to signal when the far-end answers a call.  Zip.  Zero.  Nada.  Nothing.  

If you're lucky enough to be in a country where the telco reverses polarity to signal that the far end has answered the call, then this is most likely a bug.  I just don't want people's expectations to be set inappropriately because of a misunderstanding.

Does that help clarify things?
By: Jonathan M Bradshaw (jonathanmbradshaw) 2010-01-06 02:18:13.000-0600

Just to restate, in this case the TELCO in not involved in polarity switching, the ASTERISK port is connected to a Motorla VoIP Cable modem (SBV5121) and I am reasonably confident that the Cable Modem is switching polarity; I say this because I noted polarity switch messages in one of the log files.

Perhaps we can clear this up, can you suggest what logging I can use and where I should look so that we can refine the problem statement?

An extract from the kernel ring buffer (dmesg) created by an incomming call on the WCTDM port.

       :
   4458886506 Polarity reversed (1 -> -1)
       :
       :
   4458887366 Polarity reversed (-1 -> 1)
       :

Regards Jonathan


By: Tzafrir Cohen (tzafrir) 2010-01-07 07:17:00.000-0600

Please enable debug logging in asterisk (e.g. the 'full' log from the sample logger.conf) and debug level that is high enough (5 should certainly do). You should then see all the events DAHDI sends up to Asterisk. This includes both "onhook" / "offhook" and polarity reversal.
By: Jonathan M Bradshaw (jonathanmbradshaw) 2010-01-07 10:33:29.000-0600

ASTERISK debug level 7, full log has been attached
- jmb
By: Jonathan M Bradshaw (jonathanmbradshaw) 2010-01-19 03:57:00.000-0600

I have attached two log files which may provide addition info..

   1. DIALSTATUSisCANCEL.txt
   2. DIALSTATUSisANSWER.txt

In the first log file ASTERISK behaves as described in the bug report.  In the second log file the call is shown as ANSWERED in the PBX, the only difference between the two calls is the number dialled.  It seems that ASTERISK is reacting differently to the two calls, is this perhaps a timing issue?
By: Jonathan M Bradshaw (jonathanmbradshaw) 2010-01-25 02:44:50.000-0600

Tested and fault found on dahdi-linux-complete-2.2.1+2.2.1
By: Luganet Sa (luganet) 2010-03-29 06:45:17

Same problem, when calling via DAHDI and a TDM410P, sometimes astersisk do not detect the remote party ANSWER, and I see ringing (DAHDI/10-1 is ringing) also when answered so the voice is unidirectional. I use Dahdi 2.2.1.1 and Asterisk 1.6.0.22-samy-r60
By: Jonathan M Bradshaw (jonathanmbradshaw) 2011-01-18 12:20:42.000-0600

Tested and the fault remains on;

   DAHDI 2.4.0
   ASTERISK 1.6.2.12-rc1

asterisk-dahdi.i686                               1.6.2.12-0.1.rc1.fc13
dahdi-linux.i686                                  2.4.0-69.fc13
dahdi-linux-kmdl-2.6.34.7-66.fc13.PAE.i686        2.4.0-69.fc13