Debugging “stuck” Inbound Call

Home » Asterisk Users » Debugging “stuck” Inbound Call
Asterisk Users 1 Comment

Asterisk 11.1.0 running on Ubuntu 12.04 64 bit Dahdi Digium T1 card

Occasionally, I will find an inbound call that just seems to be stuck, usually in our after-hours menu portion of the dial plan.

This morning I had this one

core show channels concise DAHDI/i1/5184097869-1baf2!MainMenu!s!20!Up!BackGround!custom/aa-night-hello&custom/hours_8:0-17:0_0:0-0:0_0:0-0:0&custom/aa-night-instructions!5184097869!!!3!9393!(None)!sip1-1396004671.285644

which had been there for about 2.5 hours (time from core show channels verbose).

The inbound channel here is to our toll free number on the T1.

When we’ve researched these in the past, we’ve not found a correspondingly long call on the phone bill, leading me to wonder if the call is actually being disconnected, but Asterisk just doesn’t find out.

How can I go about debugging this? Are the dahdi commands that can show me the connection status from the hardware perspective?

One thought on - Debugging “stuck” Inbound Call

  • 1) put a maximum number of loops in your IVR to terminate calls which are dead or gone.
    2) put maximum message length in voicemail.conf (ever tried to delete a 4 day long voicemail?)
    3) Call sometimes get stuck. This is life.

    —–Original Message—