-
Yate provides Debugging info on console.
The modalities to enable debug in Yate are:
6 KB (819 words) - 14:08, 16 August 2023
-
796 B (132 words) - 14:02, 7 June 2016
-
;for debugging yate
debug on
17 KB (1,082 words) - 13:07, 18 August 2022
-
In Yate there are several ways to debug issues that permits you to monitorize the state of the system and of the mo
The debugging can be done in two ways:
7 KB (905 words) - 15:03, 14 October 2016
-
... located and various command line options to start yate that will help you debug issues.
==Enhanced debug==
3 KB (583 words) - 08:05, 19 August 2013
-
When using Linux you can make use of tcpdump program to help you debug issues.
...n see a diagram of the messages sent and so on! It really helps a lot with debugging, and is IMHO easier than messing around with yate -vvvvv
797 B (134 words) - 08:36, 4 November 2013
-
== Testing and debug routing ==
An easy way to debug routing is to use the function echo:
20 KB (3,110 words) - 10:27, 4 November 2013
-
: - enable debugging
debug [module] [level|on|off]
7 KB (1,041 words) - 13:24, 4 June 2014
-
* '''debug''' [module] [level|on|off]
Show or change [[Debug_Output|debugging level]] globally or per module
2 KB (335 words) - 13:12, 13 May 2013
-
Yate provides Debugging info on console.
The modalities to enable debug in Yate are:
6 KB (819 words) - 14:08, 16 August 2023
-
==Monitoring and debugging Yate==
Some examples on how to monitor and enable debugging in Yate and the modules involved in this actions.
9 KB (1,376 words) - 10:01, 27 October 2017
-
; debug: int: OpenH323 debug level
;debug=0
13 KB (1,916 words) - 09:08, 4 November 2013
-
"line"="debug sip level 8"
"Module sip debug on level 8^M^J"
1 KB (183 words) - 15:56, 18 January 2013
-
; debuglevel: integer: The debug level of this group
; Defaults to the current debug level if missing or invalid
17 KB (2,660 words) - 08:04, 21 June 2018
-
-v Verbose debugging (you can use more than once)
-q Quieter debugging (you can use more than once)
4 KB (588 words) - 09:43, 8 December 2021
-
-v Verbose debugging (you can use more than once)
-q Quieter debugging (you can use more than once)
5 KB (770 words) - 08:44, 7 August 2013
-
There are three different projects that can be built as Debug or Release versions, for both MSVC 6 and VS.Net:
: Debug: ptlibsd.lib Release: ptlibs.lib
10 KB (1,772 words) - 15:03, 21 January 2013
-
; printmsg: boolean: Print sent/received frames to output if the module's debug
16 KB (2,483 words) - 09:12, 4 November 2013
-
Logging of spandsp messages at DEBUG and FLOW levels is disabled by default. It can be controlled at runtime fro
* ''debug spandsp'' - to show the current detailed logging status
6 KB (1,040 words) - 10:09, 4 November 2013
-
; printxml: boolean/string: Print sent/received XML data to output if debug
7 KB (984 words) - 09:21, 4 November 2013
-
* parameters for debugging
; printxml: boolean/string: Print sent/received XML data to output if debug
3 KB (443 words) - 09:20, 4 November 2013
-
; print_attributes: bool: Print returned attributes on debug level ALL
7 KB (947 words) - 10:30, 4 November 2013
-
* [[Debug Output]]
[[Category:Debug]] [[Category:Telnet]] [[Category:Rmanager]] [[Category:External]] [[Categor
2 KB (255 words) - 15:59, 31 October 2013
-
;for debugging yate
debug on
17 KB (1,082 words) - 13:07, 18 August 2022
-
* [[Debug_Output#Debugging_levels|Debug levels]]
3 KB (388 words) - 11:12, 4 November 2013
-
...o change all the other modules that are dependent, and also because we can debug what's happening much easier since we know which module passes which data t
Debug(DebugInfo,"Route for driver %s",driver);
8 KB (1,217 words) - 20:38, 10 March 2014