Summary:ASTERISK-16492: Incorrect hangupcause (says 34)
Reporter:Giovanni Proscia (djprojay)Labels:
Date Opened:2010-08-03 04:50:46Date Closed:2010-09-14 14:40:08
Versions:Frequency of
Environment:Attachments:( 0) myDebugLog
Description:My script works in this way.

i get the providers list that can handle my extension.
i try the first provider, but for same problems it says that it is unable to process the call.
The script takes the variables dialstatus: CONGESTION, and hangupcause: 34.

Then the script tryes to start the call trough the second provider. The calls starts, the called answers, and the call closes correctly.

But when i take hangupcause it says yet 34, i think it is incorrect.

Is this an issue resolved in 1.6.2.x?
Comments:By: Giovanni Proscia (djprojay) 2010-08-03 07:44:00

Tested over, same problem
Dialstatus field updated (correct), hangupcause remains the first taken from the first call; asterisk does not say the latest info via agi command GET VARIABLE HANGUPCAUSE.

By: Paul Belanger (pabelanger) 2010-08-03 08:32:48

We require a complete debug log to help triage the issue.

This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue:


By: Giovanni Proscia (djprojay) 2010-08-03 09:27:26

the request file is online, please if it is possible HIDE it from public view

By: Leif Madsen (lmadsen) 2010-08-05 15:30:29

* What do you think the hangupcause should be other than 34? Why is it wrong?
* I've marked this as private -- this means community developers will not be able to help with this issue
* Re: "Is this issue resolved in 1.6.2.x?" -- I don't know; have you tried it?

By: Giovanni Proscia (djprojay) 2010-08-06 08:31:21

Hangupcause at the second try should be for example, 16 (normal_call_clearing) if the called answers, or 17 (user_busy), if the called is busy.

But not 34 (no_circuit_available) beacause the first try was unsuccessfull.

I tested also with but same problem

By: Richard Mudgett (rmudgett) 2010-08-20 17:58:43

I am unable to reproduce your problem.  My testing on trunk and the 1.6.2 branch is showing the hangup cause being updated for the second call.  Is your script re-reading the HANGUPCAUSE?

Please redo your trace with "agi set debug on" so we can see what is sent between your AGI script and Asterisk.

By: Richard Mudgett (rmudgett) 2010-09-09 19:06:47

Any status update?

By: Richard Mudgett (rmudgett) 2010-09-14 14:40:07

Reporter has disappeared and I could not reproduce.