[asterisk-bugs] [JIRA] (ASTERISK-29993) chan_dahdi: Operator control option borks both lines involved on callee disconnect

[Friendly Automation (JIRA)]

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

Friendly Automation closed ASTERISK-29993.
------------------------------------------

    Resolution: Fixed

> chan_dahdi: Operator control option borks both lines involved on callee disconnect
> ----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29993
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29993
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_dahdi
>    Affects Versions: 18.6.0
>            Reporter: N A
>
> The "O" Dial option which only works on DAHDI to DAHDI calls is buggy in a major way.
> The actual "operator ringback" functionality itself works properly and as described, in both modes.
> However, as soon as the operator side (the called party) of a call hangs up, both lines are completely out of commission until you run "dahdi restart" in the CLI. Essentially, this makes the feature completely unusable. As soon as you dial something with the "O" option, you've just taken 2 lines out of service.
> Nothing comes up with "core show channels". In fact, even with core debug 10, there is no discernible activity on these channels.
> This is possibly/additionally a bug with DAHDI Linux as well, given that there is no indication that Asterisk is updated about hook states of affected lines.
> e.g. if you do "channel request hangup all" while one of these operator calls is in session, the caller will get silence and the operator will hear congestion.
> This persists on both sides after they go on hook and off hook again. The operator side simply hears reorder tone whenever going off hook again, for perpetuity.
> However, "dahdi show channel <chan-no>" (which makes an ioctl call to DAHDI) does show the correct hook state in the "borked" mode.
> Dialing either of the lines involved from a working line results in them being "BUSY". This is because in both cases, p->subs[SUB_REAL].allocd is true.



--
This message was sent by Atlassian JIRA
(v6.2#6252)