Re: Does an event generated by strict=state stop signals?

I go for interpretation 2.

Raphael Tryster wrote:
> Megaco stipulates that detection of an event should stop any signal that
> is playing.  Does an existing hook state, reported immediately with
> init=true because the MGC requested strict=state, count as an event for
> the purpose of stopping signals?
> 
>  
> 
> If the answer is yes, then we could have the following scenario:
> 
>  
> 
> 1.       MG sends Notify al/of.
> 
> 2.       MGC sends Modify, requesting signal cg/dt, and events
> al/of{strict=state},al/on(strict=state}.
> 
> 3.       MG immediately sends Notify al/of{init=true}, and stops the
> dial tone!
> 
>  
> 
> A variation of the above is when the strict parameter is omitted, but
> the MG decides to assume strict=state because it is working with Megaco
> version 1 or 2, where no default is specified.
> 
>  
> 
> Possible conclusions:
> 
>  
> 
> 1.       This is not a real event and the signal should not be stopped.
> 
> 2.       This is a real event and the MGC is stupid to send such a
> command.
> 
> 3.       This is a real event, and if strict is not specified, the MG
> must assume strict=exact.
> 
>  
> 
> I await the experts' opinion.
> 
>  
> 
> Raphael Tryster
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Megaco mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/megaco