Summary: | ASTERISK-20339: chan_mgcp, resp_pktccops ast_debug support | ||
Reporter: | Tomas Maldonado (tmaldonado) | Labels: | |
Date Opened: | 2012-08-29 12:18:16 | Date Closed: | 2021-08-10 12:33:28 |
Priority: | Minor | Regression? | |
Status: | Closed/Complete | Components: | Channels/chan_mgcp |
Versions: | 1.8.16.0 13.18.4 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Red Hat 5 | Attachments: | |
Description: | "mgcp set debug on" and "pktccops set debug on" show no extra log messages. In asterisk 1.6 and previous typing this commands used to show a lot of extra log messages. I see that in version 1.8 there is a new core function "core set debug channel ..." but neider one of this modules is recognised by this command. | ||
Comments: | By: Matt Jordan (mjordan) 2012-09-06 10:15:31.821-0500 I've moved this bug from Triage to Open. However, chan_mgcp and res_pktccops are extended support, and are supported primarily by the Asterisk developer community. Response times may reflect that. More information on module support levels can be found here: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States By: Tomas Maldonado (tmaldonado) 2012-09-06 10:29:57.120-0500 I understand. If you or someone else could point me out on how the ast_debug logging macro works, I could look into having this modules support it correctly. I belief it is necessary for the modules to register themselfs somewhere so the "core set debug channel" recognice them, but I have not found the way to do this. By: Matt Jordan (mjordan) 2013-01-15 09:06:05.437-0600 Tomas: The best way to look at how 'sip set debug' or one of the other variants work is probably to look at one of the implementations already in Asterisk. {{res_xmpp}} in Asterisk 11 might be a good one to start with, as it doesn't require opening {{chan_sip}}. In particular look at the implementation of the CLI command in {{xmpp_do_set_debug}}. In general, these commands toggle some global setting in the module. When enabled, additional {{ast_debug}} commands are called. Usage of the {{ast_debug}} macro is allowed through the inclusion of the {{logger.h}} header file. By: Sean Bright (seanbright) 2021-08-10 12:33:28.784-0500 In the latest Asterisk 16, you can turn on debugging of these modules: {noformat} *CLI> core set debug 10 chan_mgcp.so Core debug was 0 and has been set to 10 for 'chan_mgcp'. *CLI> core set debug 100 res_pktccops.so Core debug was 0 and has been set to 100 for 'res_pktccops'. {noformat} By: Friendly Automation (friendly-automation) 2021-08-16 12:16:32.990-0500 Change 16274 merged by Friendly Automation: mgcp: Remove dead debug code [https://gerrit.asterisk.org/c/asterisk/+/16274|https://gerrit.asterisk.org/c/asterisk/+/16274] By: Friendly Automation (friendly-automation) 2021-08-16 12:33:02.318-0500 Change 16273 merged by Joshua Colp: mgcp: Remove dead debug code [https://gerrit.asterisk.org/c/asterisk/+/16273|https://gerrit.asterisk.org/c/asterisk/+/16273] By: Friendly Automation (friendly-automation) 2021-08-16 12:33:11.736-0500 Change 16275 merged by Joshua Colp: mgcp: Remove dead debug code [https://gerrit.asterisk.org/c/asterisk/+/16275|https://gerrit.asterisk.org/c/asterisk/+/16275] By: Friendly Automation (friendly-automation) 2021-08-16 12:33:21.155-0500 Change 16235 merged by Joshua Colp: mgcp: Remove dead debug code [https://gerrit.asterisk.org/c/asterisk/+/16235|https://gerrit.asterisk.org/c/asterisk/+/16235] |