[Asterisk-Users] 'set debug' problems

[Christopher L. Wade]

Has anyone else noticed this?  I use 'set verbose 25' (insane, but I 
want to see *everything* right now) and would like to do the same for 
'set debug', but as you see, set debug has a bad impact on my CLI output.

asterisk*CLI>
     -- Executing Answer("SIP/824-b4ff", "") in new stack
     -- Executing Wait("SIP/824-b4ff", "0.5") in new stack
     -- Executing VoiceMailMain("SIP/824-b4ff", "824") in new stack
     -- Playing 'vm-password' (language 'en')
   == Spawn extension (internal, vm824, 3) exited non-zero on 'SIP/824-b4ff'
asterisk*CLI> set debug 25
Core debug was 0 and is now 25
     -- Playing 'vm-password' (language 'en')
asterisk*CLI> set debug 0
Core debug is now OFF
     -- Executing Answer("SIP/824-d2f2", "") in new stack
     -- Executing Wait("SIP/824-d2f2", "0.5") in new stack
     -- Executing VoiceMailMain("SIP/824-d2f2", "824") in new stack
     -- Playing 'vm-password' (language 'en')
   == Spawn extension (internal, vm824, 3) exited non-zero on 'SIP/824-d2f2'

I have logger.conf setup to dump absolutely everything to one file, this 
also affects the verbose output to that file as well.

Any help would be appreciated.

Thanks,
Chris

-- 
Christopher L. Wade                     Unistar-Sparco Computers, Inc.
Senior Systems Administrator                            dba Sparco.com
Email: clwade at sparco.com                             7089 Ryburn Drive
Phone: (901) 872 2272 / (800) 840 8400            Millington, TN 38053
Fax:   (901) 872 8482                                              USA