[asterisk-bugs] [JIRA] (ASTERISK-22019) overlap=no in chan_dahdi.conf does not work

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan closed ASTERISK-22019.
----------------------------------

    Resolution: Not A Bug
    
> overlap=no in chan_dahdi.conf does not work
> -------------------------------------------
>
>                 Key: ASTERISK-22019
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22019
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: 1.8.22.0
>         Environment: Linux 2.6.34, libpri 1.4.12, dahdi-linux-complete-2.6.1+2.6.1, asterisk-1.8.22.0. Three euroisdn Point-to-point BRI spans on a Digium B410p.
>            Reporter: Lelio della Pietra
>         Attachments: config and output.tgz
>
>
> After upgrading to asterisk 1.8 from an old 1.6 a customer of mine reported that dialing became slow (I don't have old config files, so I can't say if it is a regression, sorry).
> I discovered that the call is being placed in overlap mode (remote sends a SETUP ACKNOWLEDGE (13) message and call enters state 2 (Overlap Sending)). I run an euroisdn switch.
> So I modified the default chan_dahdi.conf file setting overlap=no, but nothing changes. To force en-bloc dial, I have to postpone a hash (#) to the dialed number, but this will not work for me because my calls are placed they are placed through AMI directly to the channel, bypassing the extensions.conf file.
> A pri show span 1 command shows that on the span overlap dial is correctly set to no.
> Enclosed:
> a) chan_dahdi.conf
> b) users.conf - only the span definition
> c) dahdi system.conf
> d) a CLI capture showing a "simple" call (it takes 5 seconds to dial), a call with the hash postponed to the number (it takes less than a second to dial) and the pri show span 1 output.
> Thank you in advance!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira