Summary: | ASTERISK-24249: SIP debugs do not stop | ||
Reporter: | Avinash Mohod (amohod) | Labels: | Debugs SIP |
Date Opened: | 2014-08-20 07:18:22 | Date Closed: | 2014-08-21 17:38:08 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/PBX |
Versions: | 11.10.2 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Asterisk Console | Attachments: | ( 0) issueA24249_clarify_sipdebug_conf_limitation.patch ( 1) logger.conf ( 2) sip.conf |
Description: | 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 | ||
Comments: | By: Walter Doekes (wdoekes) 2014-08-21 04:56:31.690-0500 What does your logger.conf and sip.conf look like? (Please remove any sensitive information from either file.) By: Walter Doekes (wdoekes) 2014-08-21 17:08:43.073-0500 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.) By: Avinash Mohod (amohod) 2014-08-21 17:34:13.117-0500 After applying workaround the issue is resolved. Thank Walter for your inputs. |