Subject: Re: [Megaco] cause/generic

From: Christian Groves <[email-masked]>
Date: Thu, 12 May 2005 13:34:39 +1000

Hello Moshe,

Cause codes are usually associated with a release of a bearer. Bearer control 
protocols eg. Q.AAL2 will carry a 'cause' code on why the bearer was released. 
You can also look at Q.931 for a listing of cause codes.
In H.248 there are 2 types of cause. Failure cause is the specific cause 
associated with the Bearer Control Protocol. GeneralCause it the mapping a MG 
provides from one of the FailureCauses. This is so that multiple bearer controls 
can be used in a MG without the MGC having to know bearer specific causes.

ITU-T Q.1950 may also be of some help.

Regards, Christian

Moshe Levy wrote:

> Hi all,
>  
> The "cause" event of the generic package has 2 parameters: generalcause
> and failurecause. The generalcause includes 6 groups of failures (NR,
> UR, FT, FP, etc.). 
> Can someone explain the usage of these causes (i.e. in what scenarios
> they are used)? Also in a normal call (i.e. without any failure), if
> this event is requested by the MGC should the MG notify with the NR
> cause, right? Is the request of this event is a common behavior of MGCs
> (didn't find any call flow which use it)? What is the meaning of the
> failurecause (can I get an example)?
>  
> Regards,
> Moshe
>  
> Moshe Levy 
> Telrad Networks Ltd. 
> www.telrad.co.il 
> Tel +972-3-9157441   
>  <Mailto:[email-masked]> Mailto:[email-masked] 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Megaco mailing list
> [email-masked]
> https://www1.ietf.org/mailman/listinfo/megaco

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco