[Asterisk-Dev] Extracting specific call from 'iax debug' on a busy server?

[steve at daviesfam.org]

On Fri, 10 Sep 2004, Kris Boutilier wrote:

> I've got full debug including a suspect IAX call - I am running with
> 'notrunking=yes'. I was expecting each IAX call to have a seperate pid in
> the logs but apparently not. Given the start data:
> 
> Sep 10 11:11:06 VERBOSE[131081]: Rx-Frame Retry[No] -- OSeqno: 000 ISeqno:
> 000 Type: IAX     Subclass: NEW
> Sep 10 11:11:06 VERBOSE[131081]:    Timestamp: 00003ms  SCall: 00002  DCall:
> 00000 [10.0.40.140:4569]
> Sep 10 11:11:06 VERBOSE[131081]:    VERSION         : 2
> Sep 10 11:11:06 VERBOSE[131081]:    CALLED NUMBER   : 6405
> Sep 10 11:11:06 VERBOSE[131081]:    LANGUAGE        : en
> Sep 10 11:11:06 VERBOSE[131081]:    CALLED CONTEXT  : macro-out-t1nstar
> Sep 10 11:11:06 VERBOSE[131081]:    FORMAT          : 2
> Sep 10 11:11:06 VERBOSE[131081]:    CAPABILITY      : 258
> Sep 10 11:11:06 VERBOSE[131081]:    ADSICPE         : 2
> Sep 10 11:11:06 VERBOSE[131081]:    DATE TIME       : 153770362
> 
> How the heck can I extract the debug information for just that particular
> call? I was anticipating just grepping out the relevant lines using some
> sort of key. The data I'm getting is along the lines of:

Yeah - its a bit of a mess.  Jitter related stuff can be found with 
grep 'Jitter: call=2'

For other stuff you do get a feel for the messages and how to keep it all 
straight after a while ;-)

Steve