[Asterisk-video] continue dialplan execution after h324m_call

[Klaus Darilion]

Hi Sergio!

Attached is a patch which fixed the problem for me. By setting the 
hangupcause I can use ${HANGUPCAUSE} after h324m_call priority to get 
indication. Nevertheless it is very limited as the cause is derived from 
the control frame subtype, thus either BUSY or CONGESTION. It would be 
better if the original zap hangupcause would be available, but this is 
somehow lost over the local channel. Thus, the patch is not applied to 
SVN as I hope there will be a better solution.

regards
klaus

Sergio Garcia Murillo schrieb:
>> Klaus Darilion schrieb:
>>> Johansson Olle E schrieb:
>>>> 22 jan 2008 kl. 10.26 skrev Klaus Darilion:
> [..]
>>>> If an application returns -1, Asterisk will stop execution.
>>> ...without looking into this particular app...
>> This is the reason.
>> Nevertheless I do not get the ->hangupcause from the local channel - it 
>> is always 0. Any hints?
> 
> Yes, as Olle says the application hangup by returning -1. Do you think it could
> be interesting to return to different extensions to handle the different exit causes??
> I.E. as I've seen in some other apps:
> 0 if normal realease (or hangup??)
> ext+100 if not answered
> ext+101 if .. 
> 
> Apart of that the hangupcause is a still pending bug, I'll try to solve it as soon as I can.
> 
> BR
> Sergio
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> 
> asterisk-video mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-video
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: h324m_call_hangup_patch.txt
Url: http://lists.digium.com/pipermail/asterisk-video/attachments/20080123/b68a57fa/attachment.txt