[asterisk-dev] PRI HANGUPCAUSE

[Vlasis Hatzistavrou]

I second that. A LOCALHANGUPCAUSE would be extremely helpful, even in the cases when there are VoIP call legs. 

For example, if there is no network connectivity an H323 call would probably return a Q931=3, which is different than when the remote side is reachable and returning an actual Q931=3 release cause.


Best regards,
Vlasis.

> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-
> bounces at lists.digium.com] On Behalf Of Anton
> Sent: Tuesday, October 31, 2006 11:53 AM
> To: Asterisk Developers Mailing List
> Subject: [asterisk-dev] PRI HANGUPCAUSE
> 
> 
> Hi,
> 
> Just was trying to distinguish between local disconnect Q931
> code 34 when no more PRI ZAP channels available and when
> remote switch returns 34 - when there is congestion
> somewhere. Seems now there is no way to do so. May I
> propose making an extra varialble like MVTS has -
> LOCALHANGUPCAUSE which will be setup accordingly local
> conditions, so it will be some normal return code if ZAP
> channel were allocated successfully but remote switch for
> instance returned 34.
> This should be usefull not only for me while working with
> dialplan, for example I would like to dial extra ZAP group
> if local HANGUPCAUSE is 34 (no more ZAP channels in the
> group) but do not want to dial another group if remote
> switch returned 34.
> 
> Regards
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev