[asterisk-users] hangup not detected?

Thu May 24 17:07:18 CDT 2012

Here is the output from the cli:

dozer*CLI> core show channels
Channel              Location             State   Application(Data)
DAHDI/5-1            s at DB_LOOKUP:24       Up      Swift(""Schedule for employee
1 active channel
1 active call
1528 calls processed
dozer*CLI> core show channel dahdi/5-1
 -- General --
           Name: DAHDI/5-1
           Type: DAHDI
       UniqueID: 1337821128.1363
       LinkedID: 1337821128.1363
      Caller ID: (N/A)
 Caller ID Name: (N/A)
Connected Line ID: (N/A)
Connected Line ID Name: (N/A)
    DNID Digits: (N/A)
       Language: en
          State: Up (6)
          Rings: 1
  NativeFormats: 0x4 (ulaw)
    WriteFormat: 0x4 (ulaw)
     ReadFormat: 0x4 (ulaw)
 WriteTranscode: No
  ReadTranscode: No
1st File Descriptor: 15
      Frames in: 3967
     Frames out: 15882
 Time to Hangup: 0
   Elapsed Time: 20h56m23s
  Direct Bridge: <none>
Indirect Bridge: <none>
 --   PBX   --
        Context: DB_LOOKUP
      Extension: s
       Priority: 24
     Call Group: 0
   Pickup Group: 0
    Application: Swift
           Data: ""Schedule for employee number 9999:  "Thursday, May 24th, 2012, you are scheduled at XXXXXXXXXXXXXX"
    Blocking in: (Not Blocking)
      Variables:
READSTATUS=TIMEOUT
return_id=
MAX_REPEAT=4
ODBCSTATUS=SUCCESS
ODBCROWS=1
COUNTER=2
AAA_OUTPUT="Schedule for employee number 9999:  "Thursday, May 24th, 2012, you are scheduled at XXXXXX..
data=Thursday, May 24th, 2012, you are scheduled at XXXXXXXXXX
id=9999
ODBC_FETCH_STATUS=SUCCESS
~ODBCFIELDS~=id,data
ODBC_ID=903
ID_VALIDATED=AAA_VALIDATE_EMP_NUM(27,9999)
account_id=9999
read_length=7
get_param2=E
get_param1=27
validate_func=AAA_VALIDATE_EMP_NUM
truck_text=employee number
readprompt=AAA/enter_employee_number
comp_num=27
BACKGROUNDSTATUS=SUCCESS

  CDR Variables:
level 1: dnid=
level 1: dst=4
level 1: dcontext=default
level 1: channel=DAHDI/5-1
level 1: lastapp=Swift
level 1: lastdata=""Schedule for employee number 9999:  "Thursday, May 24th, 2012, you are schedu
level 1: start=2012-05-23 17:58:48
level 1: answer=2012-05-23 17:58:54
level 1: duration=75383
level 1: billsec=75377
level 1: disposition=ANSWERED
level 1: amaflags=DOCUMENTATION
level 1: accountcode=27_EMP
level 1: uniqueid=1337821128.1363
level 1: linkedid=1337821128.1363
level 1: userfield=2885
level 1: sequence=1363

Since the 'lastapp' variable is 'Swift', this would indicate that the cepstral wrapper is having a problem, correct?

Justin Killen
________________________________
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Justin Killen
Sent: Tuesday, May 22, 2012 8:53 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] hangup not detected?

Okay, the next time it gets in this state I'll gather that information.

Justin Killen
________________________________
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Warren Selby
Sent: Monday, May 21, 2012 1:22 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] hangup not detected?

On Fri, May 18, 2012 at 12:00 PM, Justin Killen <jkillen at allamericanasphalt.com<mailto:jkillen at allamericanasphalt.com>> wrote:
I have and automated call-in dispatch system where hundreds of people call in daily for 2-3 minutes each.  The extension is set up to get their information, then text-to-speech the dispatch information (via odbc).  It then loops 5 times then ends the call.  These calls are being handled by an 8 port analog digium card.

Sometimes though, I see calls via 'core show channel dahdi/1-1' that have a time of > 16 hours.  I'm not sure if this is a result of dahdi missing the hangup, ODBC timing out, or TTS failing for some reason.  When a channel gets in this state, the call doesn't seem to progress through the dialplan, they always display the TTS line.  Doing a 'dahdi destroy channel 1-1' doesn't seem to be effective - the only way I've been able to clear the calls is to do a 'dahdi restart' and/or restart the asterisk service.

For TTS I'm using cepstral with the Swift wrapper.

Here is a snippet of my dialplan:

Can you post the CLI output of a call that gets "hung"?  I'd like to see where it's hanging on.

Also, as a work-around to attempt to solve the symptom and not the underlying issue, you could maybe setup a cron job that runs once every ten minutes that checks for stale calls using AMI, and then hangs up any calls up that are over 10 minutes long?  Using the AMI Hangup command?

--
Thanks,
--Warren Selby, dCAP
http://www.SelbyTech.com<http://www.selbytech.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20120524/5e8e76ca/attachment.htm>