[asterisk-bugs] [JIRA] (ASTERISK-26893) No "alert" or "progress" in chan_ooh323 if debug is enabled only on the module

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243170#comment-243170 ] 

Friendly Automation commented on ASTERISK-26893:
------------------------------------------------

Change 8848 merged by Richard Mudgett:
chan_ooh323: fix ooManualProgress/ooManualRingback on ooh323 debuggin on

[https://gerrit.asterisk.org/8848|https://gerrit.asterisk.org/8848]

> No "alert" or "progress" in chan_ooh323 if debug is enabled only on the module
> ------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26893
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26893
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/chan_ooh323
>    Affects Versions: 13.14.0
>         Environment: Debian 8 amd64
>            Reporter: Marco Giordani
>            Assignee: Alexander Anikin
>
> During my debug of an h323 call from another vendor device I noticed that asterisk doesn’t send back “alerting” to the caller party and the call never starts “ringing” for the caller. This happens only if debug is enabled from the cli with “ooh323 set debug” and core debug is off.
> When both ooh323 debug and core debug are consistent (enabled or disabled) the call behavior is normal and asterisk sends back the alerting message.
> Even if I should not make assumption, I’ve noticed that if h323 debug is enabled, ooManualRingback is invoked by ast_debug that executes only if core debug is enabled.
> The same problem is present for ooManualProgress.
> I have made a very  simple patch that solves the problem invoking ooManualRingback and ooManualProgress before ast_debug. 



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