Search results

...the calls that can be interrogated using telnet command [[CDR_Build_Module#Rmanager_command|status]].<br/> ===Rmanager command===

* [[Rmanager]] [[Category:Debug]] [[Category:Telnet]] [[Category:Rmanager]] [[Category:External]] [[Category:External module]]

...an external module fails to start the exact reason why is not displayed in rmanager.<br>

rmanager.yate=yes thread=0x9f9cc4c 'RManager Connection'

The call generator can be controlled from the rmanager as it processes "engine.command" messages or from Yate's command line. * [[Rmanager]]

For a call made from [[rmanager]]: * [[Rmanager]]

...''NOTE!''' : Parameters can be appended with chan.control message and with rmanager command ; '''Example''': [[rmanager]]

*This message can be generated by the [[rmanager]] [[Rmanager Commands|command control]], in that case '''targetid''' and '''component''' *If the message is generated from rmanager, chan.control will succeed if the requested component is found, even if the

...e events in the running instance can be seen through a [[Rmanager Commands|rmanager command]].

All the messages are binary inside of Yate. However you can use [[Rmanager]] to get them out in a human readable form. * [[Rmanager]]

* Restart your script from [[rmanager]] by issuing the following command: * [[Rmanager]]

The engine.help message is generated by the [[Rmanager|Remote Manager]] to ask a module for specific help.

...ser.account''' message is emitted by an interactive control module (like [[rmanager]]) when in need to act as a client for another server. The message is targe

If you have [[rmanager]] module enabled, you can also connect to port 5038 and use command "stop" ... in supervised mode (command line option -s) it can also be restarted from rmanager using "stop 128" - in fact any code between 128 and 255. The program will b

* [[Javascript Rmanager commands]] Commands and ways to interact with Javascript scripts or interpretor from rmanager.

Do not use screen or telnet captures from rmanager. Some scripts and third party libraries write only to the log file and you

The easiest way to check this, is from [[rmanager]] to write command '''status''' and to see if module name is listed there. Then start Yate and send status command from [[rmanager]].

#REDIRECT [[How to find which external modules are loaded from rmanager]]

* at runtime - use [[rmanager]] module that allows you to see logs in real time and control the logging l When starting Yate with logging, [[rmanager]] module can be used to change the levels for debugging. By doing this the

* [[Eventlogs]] accessed from [[rmanager]] ===Eventslog accessed from Rmanager===