Subject: [Megaco] Default Event Detection

From: "Eric Cooper" <[email-masked]>
Date: Tue, 16 Apr 2002 15:08:12 -0400

The last statement of the call flow example in the spec states:

23.  The MGC now sets up both MG1 and MG2 to be ready to detect the next off-hook event. See step 1. Note that this could be the default state of a termination in the null context, and if this were the case, no message need be sent from the MGC to the MG. Once a termination returns to the null context, it goes back to the default termination values for that termination. 

My question is:  Does the protocol allow me to set the default state of a termination in the null context to include detection of off-hook events, or is that done through non-Megaco provisioning?  

Other statements in the text lead me to believe that a termination's Event descriptor returns to empty/"no value" when it enters the null context, so I guess this would be a non-Megaco provisioning activity, but I wanted to check.

Thanks,

Eric.

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