[Home]

Summary:DAHLIN-00186: FXO Outgoing dial not passing audio until channel answer
Reporter:Sebastian Gutierrez (sum)Labels:
Date Opened:2010-04-21 14:53:57Date Closed:2016-06-07 12:15:28
Priority:MinorRegression?No
Status:Closed/CompleteComponents:dahdi (the module)
Versions:2.3.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have a FXO conected to the PSTN, previously I just Dial a number and I have the feedback of the telco (ringback), with the las version of dahdi (not sure if dahdy or chan_dahdi issue), I have to do an answer befor dial to let the ringback pass to the calling party.
Comments:By: David Woolley (davidw) 2010-04-23 05:43:19

I believe this is a duplicate.
By: David Woolley (davidw) 2010-04-23 05:58:20

ASTERISK-1639604 looks related, and maybe duplicate.
By: Michael Spiceland (mspiceland) 2010-04-23 08:21:59

sum, is this new behavior with an upgrade of DAHDI?  If so, you have noted that you experienced this with DAHDI 2.3.0.  What version were you using previously that didn't have this behavior.

Also, could you review 0016604 as davidw suggested to see if it is the same issue?
By: Sebastian Gutierrez (sum) 2010-04-23 09:54:39

yes this is new behavior of an upgrade

used to work:
Asterisk: 1.6.2.1
DAHDI Version: 2.2.1
and has 1.6.2.6 chan_dahdi with the modifications of dtmf callerid.


the new behavior:
Asterisk: 1.6.2.6
DAHDI: 2.3.0
chan_dahdi with the modification of dtmf callerid.


For example if I put before dial PlayTones(ring) it fails and never get to the dial section, if I do the same on the previous version it works ok, so it seems an issue of dahdi 2.3.0

It doesn't look the same as the issue mentioned, if I use the r option on the dial I can't hear the ring either.
I don't think is an asterisk issue, I think is dahdi, the other bug has no mention of dahdi version.
It also mention session progress, but i think has nothing to do with the behavior of the analog lines, here the problem is: on the previous version the audio from the telco was passing when I dial, now it doesn't until answer is detected.

The exact config of the lines is kewel start, with polarity reversal for answer and hangup but the beginin of the dtmf callerid comes before the polarity reversal (DTMF callerid without polarity reversal) with dtmf tones.


By: David Woolley (davidw) 2010-04-23 10:05:56

Call progress is exactly about passing audio before answer!  Although ASTERISK-1639604 is written (wrongly I think) from a SIP perspective, SIP 183 Progress corresponds to an internal Asterisk control frame AST_CONTROL_PROGRESS, which signals that the audio (ring back tones, and other call progress tones) should passed through, even though the call hasn't been answered.

The reason that issue doesn't mention dahdi driver versions is that they are thinking in terms of the SIP symptoms, when, in my view, chan_sip is simply reacting to the lack of an AST_CONTROL_PROGRESS from chan_dahdi.
By: Michael Spiceland (mspiceland) 2010-04-23 10:13:35

To verify, could you downgrade to DAHDI 2.2.1 again but this time only changing the DAHDI veersion and retest?
By: Sebastian Gutierrez (sum) 2010-04-23 10:19:50

I have 2 production sites with the data mention above, I just confirmed that the 1.6.2.1 with 2.2.1 works ok and hears the ring, the other site doesn't hear the ring if I don't put the Answer before the dial, remember both instalations has the same chan_dahdi (is the 1.6.2.6 with the modifications of dtmf callerid)
By: Sebastian Gutierrez (sum) 2010-05-06 21:34:09

any update on this issue?
By: Sebastian Gutierrez (sum) 2010-06-07 11:49:25

any update on this? this problem has several impact on cdr answertime and any action on the dialplan that has to check dialstatus.
By: Sebastian Gutierrez (sum) 2010-06-14 16:11:03

please update the status of this issue, is a regretion and a real important one, the status is on feedback for a month and a half! anyone looking at this? I will help as much as I can.
By: Sebastian Gutierrez (sum) 2010-06-28 12:05:18

anyone? this is still on feedback status and I don't know how more can I help to move this issue forward, I had to downgrade all my systems to 2.2.1
By: Shaun Ruffell (sruffell) 2010-06-28 13:11:22

Sum:  What actual hardware do you have?   Also, do you have a problem in trunk?
By: Sebastian Gutierrez (sum) 2010-06-28 13:37:58

tdm400 is on analog cards,
I haven't test trunk of dahdi, but 2.2.1 works ok, 2.3.0 not, I'll download dahdi trunk and test it.
By: Michael Spiceland (mspiceland) 2010-07-06 10:35:20

Any new results with trunk?
By: Sebastian Gutierrez (sum) 2010-07-12 08:48:02

seems ok in trunk lets close this issue for now, I will test when the new release comes out. thanks
By: Sebastian Gutierrez (sum) 2010-07-16 10:21:54

I found the problem again and now I know the exact config of the problem, if answerpolarityswitch is on the reported beheavior appears if no polarityswitch then it works ok.
I have the test enviroment ready for any test now.
By: Sebastian Gutierrez (sum) 2010-12-01 13:46:57.000-0600

any update??
By: Michael Spiceland (mspiceland) 2010-12-01 13:52:32.000-0600

To be clear, is this still resolved with trunk?  On 2010.07.12 you said that it is ok in trunk, but on 2010.07.16 you said that you isolated it to the answerpolarityswitch option.  Does this mean that you are able to reproduce it with trunk based on this option?
By: Sebastian Gutierrez (sum) 2010-12-01 13:58:30.000-0600

yes, is easy to reproduce, if answerpolarityswitch is on I cant hear anything (ring) until the channel is answered, when I said trunk was ok I couldn't test it on a line with polarity reversal, some days later I did and reported back that the problem is reproducible.

example: 1.6.2.14 and 2.4.0 has this issue.
By: Sebastian Gutierrez (sum) 2016-06-07 12:15:28.711-0500

no relevant anymore