| Summary: | ASTERISK-02543: TRON TROFF in extensions.conf | ||
| Reporter: | randulo (randulo) | Labels: | |
| Date Opened: | 2004-10-06 01:22:59 | Date Closed: | 2011-06-07 14:05:25 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | How about a pseudo-app or meta that allows us to specify whether to show specific priorities on the console? The idea is to be able to trace new test extensions and macros but not to see every single line of other stuff. If this isn't practical, I'd really like to see finer control over what's sent to the console. ****** ADDITIONAL INFORMATION ****** ; example ; like Noop() Tron could send output as well exten => 2040,1,Dial(SIP/2040,etc) exten => 2040,2,Troff() ;(other stuff) exten => 2040,102,Tron(${something}) Maybe add a global at the beginning like TRON=off|on to select an initial state? | ||
| Comments: | By: Brian West (bkw918) 2004-10-06 09:45:02 You could use Verbose bkw By: randulo (randulo) 2004-10-06 10:46:51 Suppose you have a production server. It runs all day with no programmer sitting there watching it. A new extension is added and we want to debug it. Turning output on and off in a script is a good way to do this. Ok, it's no priority but the idea has little to do with verbose. By: Brian West (bkw918) 2004-10-11 08:08:36 thats what verbose is for and app_verbose. I do this all the time.... its very practical and easy to work within the current code to accomplish this. By: Brian West (bkw918) 2004-10-11 08:34:12 Learned of app_Verbose... problem solved :) Its monday... we are all a bit slow today! :) | ||