Search results

Page title matches

• How To For External Modules In Telnet
  73 B (11 words) - 10:03, 12 April 2013

Page text matches

• Rmanager
  This module allows controlling Yate using a simple telnet client. # telnet 0 5038
  7 KB (1,041 words) - 13:24, 4 June 2014
• Debug Output
  * from telnet client ([[Rmanager]] module is required). If you telnet into the rmanager interface you can enable debugging and increase the level
  6 KB (819 words) - 14:08, 16 August 2023
• How To's
  Debug an external module in Telnet
  9 KB (1,376 words) - 10:01, 27 October 2017
• Modules
  Remote manager accessible from telnet
  12 KB (1,662 words) - 13:25, 1 October 2019
• Building Jabber server using Yate
  * Connect to yate using telnet. Issue the following commands: telnet 0 5038
  21 KB (3,052 words) - 09:24, 4 November 2013
• PostgreSQL
  Another way to check if module is loaded is from telnet, use command '''status''' check if pgsqldb is in the list:
  5 KB (763 words) - 07:19, 10 June 2014
• Users
  From telnet the command can be used to add/delete/update a user: telnet 0 5038
  3 KB (394 words) - 12:51, 5 June 2013
• MySQL
  Another way to check if module is loaded is from telnet, use command '''status''' check if mysqldb is in the list:
  5 KB (810 words) - 11:18, 4 November 2013
• CDR Build Module
  ...l records) and creates a list for the calls that can be interrogated using telnet command [[CDR_Build_Module#Rmanager_command|status]].<br/> From telnet you can see details from live CDRs by using 'status' command:
  10 KB (1,558 words) - 13:22, 13 January 2014
• How to find which external modules are loaded from rmanager
  ...g at any moment you can run in Telnet the command '''external'''. <br>From telnet you can start/stop/restart an external module without stopping Yate (operat Follow the next steps to know how to see from Telnet the running global external modules.
  2 KB (255 words) - 15:59, 31 October 2013
• External Module
  *[[How To For External Modules In Telnet]]
  3 KB (459 words) - 11:15, 4 November 2013
• Debugging and, or Investigation of messages
  === Enable / Disable sniffer in telnet === The module must be loaded so that you can use this commands from telnet:
  17 KB (1,082 words) - 13:07, 18 August 2022
• Beginners in Yate
  Also to see the flow of the messages, use a telnet client. Connect like this: telnet localhost 5038
  5 KB (888 words) - 13:05, 10 March 2015
• Using Yate's PHP library on windows
  * connect to yate in telnet and type "external". Output should be:
  2 KB (241 words) - 11:52, 4 November 2013
• Stopping and restarting Yate
  === Telnet commands === telnet 127.0.0.1 5038
  2 KB (234 words) - 09:39, 4 November 2013
• Programmer's guide
  * [[How To For External Modules In Telnet]]
  4 KB (524 words) - 09:01, 10 March 2016
• Bug reporting
  Do not use screen or telnet captures from rmanager. Some scripts and third party libraries write only t
  5 KB (943 words) - 09:36, 9 July 2013
• Debugging in Yate
  ...llows controlling Yate using a simple [http://en.wikipedia.org/wiki/Telnet telnet] client. telnet localhost 5038
  7 KB (905 words) - 15:03, 14 October 2016
• Monitoring Yate
  ...d to use [[Rmanager]], a module that makes possible the connection through Telnet to your Yate. The default configuration binds the localhost (127.0.0.1) and Type ''telnet 127.0.0.1 5038'' in a terminal and this should follow:
  9 KB (1,268 words) - 15:48, 31 October 2013
• Database Connection Problems
  Type in console: '''telnet localhost 5038''' and enter '''status'''. If
  4 KB (587 words) - 08:36, 4 November 2013