[asterisk-bugs] [JIRA] (ASTERISK-24249) SIP debugs do not stop

[Walter Doekes (JIRA)]

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

Walter Doekes commented on ASTERISK-24249:
------------------------------------------

Interesting.

Looks like the {{sipdebug}} value is a bitmask of {{sip_debug_config | sip_debug_console}}.

By setting {{sipdebug=yes}} in your sip.conf, you've set {{sipdebug=sip_debug_config}}.

Now doing {{sip set debug on/off}} will only toggle the {{sip_debug_console}} bit.

However: I don't see any output separation between {{sip_debug_console}} vs. {{sip_debug_config}}, i.e. *if either is on, it is on*.

Turns out it is "expected" behaviour, although possibly not documented clearly enough. Patch to clarify is attached.

{noformat}
/*! \brief debugging state
 * We store separately the debugging requests from the config file
 * and requests from the CLI. Debugging is enabled if either is set
 * (which means that if sipdebug is set in the config file, we can
 * only turn it off by reloading the config).
 */
{noformat}

Workaround: edit sip.conf and {{set sipdebug=no}} and do {{sip reload}}.

(Code checked was 1.8-head.)

> SIP debugs do not stop
> ----------------------
>
>                 Key: ASTERISK-24249
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24249
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/PBX
>    Affects Versions: 11.10.2
>         Environment: Asterisk Console
>            Reporter: Avinash Mohod
>            Severity: Minor
>              Labels: Debugs, SIP
>         Attachments: issueA24249_clarify_sipdebug_conf_limitation.patch, logger.conf, sip.conf
>
>
> For troubleshooting purpose I have started sip debugs from asterisk console. But after turning the debug off, still show sip debugs in console. I also restarted the asterisk service multiple times but no effect. 
> i think i am facing same issue reported below.
> ASTERISK-11598
> Please advice possible solution or workaround for this problem.
> Regards
> Avinash



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