If you can recompile, you can certainly enable building and loading of app_verbose, and debugging.
For the record, verbose is in version 1.0, which is the earliest version available on github, and is 19 years old.
I have app_verbose built, it is just not loaded as I have autoload disabled, so I specified a list of the modules needed.
The issue with debugging is that I can’t use gdb as libthread_db.so is missing. So I would have to attempt to figure out what’s going on by modifying the source code.
I did look into this a little more, and the string that is attempted to parse is Xm. That is weird, as I am passing bm to the Monitor-Application. Adding an additional F at the end of my monitor command in the dialplan and the string changes to XmF. Interestingly enough the message about the unrecognized F appears 2 times: First when the call is ringing and the executed monitor command is executed (there the string is bmF, as it should be), and then later on again when the call is answered and the string is XmF, causing the log entry with the unrecognized X. Any clue where that X might be coming from?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.