[Asterisk-Dev] How do I figure out instability?

[sales at minixel.com]

I figured out how to reproduce the problem. Please look
at the trace below. It dies with the word "killed"
after a call to the cdr_odbc function. However, is this
the offending program or the reason of the blowup is
that I don't have a "t" tule in my context? Thanks in
advance for your patience.

-- Executing Dial("H323/ip$192.168.85.100:35466/19625",
"H323/1954817812802 at 192.168.85.100/19544447408") in new
stack
    -- Called 1954817812802 at 192.168.85.100
    -- Executing
Dial("H323/ip$192.168.85.100:35467/19626",
"H323/19544447408 at 192.168.85.100/19544447408") in new
stack
    -- Called 19544447408 at 192.168.85.100
    -- Executing
Dial("H323/ip$192.168.85.100:35468/19627",
"Sip/19544447408") in new stack
    -- Called 19544447408
Apr 16 13:21:20 WARNING[98311]: chan_sip.c:503
retrans_pkt: Maximum retries exceeded on call
3e5bdddd574fab0d666a16487e2f638a at 192.168.85.100 for
seqno 102 (Critical Request)
  == No one is available to answer at this time
Apr 16 13:21:26 WARNING[98311]: chan_sip.c:503
retrans_pkt: Maximum retries exceeded on call
3e5bdddd574fab0d666a16487e2f638a at 192.168.85.100 for
seqno 102 (Non-critical Request)
Apr 16 13:21:30 WARNING[458781]: pbx.c:1858
ast_pbx_run: Timeout, but no rule 't' in context
'from-ip'
       > cdr_odbc: Query Successful!
  == Spawn extension (from-ip, 19548178128, 1) exited
non-zero on 'SIP/19544447408-85ad'
       > cdr_odbc: Using cached prepare
Killed