Subject: RE: [Megaco] Stopping events.

From: "Kamitses, Jerry" <[email-masked]>
Date: Fri, 28 Jul 2006 10:50:46 -0400

So, per the ABNF, an empty events descriptor must be simply 
        events 
and not 
        events = 3333 { }
since the RequestID is not optional in the LBRKT - RBRKT pair 
 
This is distinct from the signalsDescriptor, which, per the ABNF, requires 
    signals { }
for an empty signalsDescriptor
 
signalsDescriptor    = SignalsToken LBRKT [ signalParm  *(COMMA signalParm)] RBRKT

-----Original Message-----
From: B Venkat S.R Swamy [mailto:[email-masked]]
Sent: Friday, July 28, 2006 10:41 AM
To: Nicolas Emiliani
Cc: [email-masked]
Subject: Re: [Megaco] Stopping events.

Hi Nicolas

H.248.1 V3(Sep 2005) , section 7.1.9, last paragraph clearly mentions how to disable event recognition and reportiing:

"An empty Events Descriptor disables all event recognition and reporting"

similarly ABNF grammar supports sending empty event descriptor
eventsDescriptor = EventsToken [EQUAL RequestID LBRKT requestedEvent
*(COMMA requestedEvent) RBRKT]

regards
B Venkat S.R Swamy 
Senior Technical Leader
Flextronics Software Systems
Phone: +91-124- 4176213
Fax: +91-124-4300247
web: www.flextronicssoftware.com
Inactive hide details for "Nicolas Emiliani" ' src="cid:023184714@28072006-204f" width=16>"Nicolas Emiliani" <[email-masked]>

	"Nicolas Emiliani" <[email-masked]> 

	07/27/2006 05:30 PM

To

[email-masked]	

cc

Subject

[Megaco] Stopping events.	

Hi List!
This is my first e-mail. I'm new to this protocol. I have been reading the rfc and I dont't seem to find the way to stop the detection of a given event. I understad that to stop any signal yo either replace them with another signal int the signal descriptor or u just send de signal descriptor empty. But what should I do to stop an event? 
for example if I asked for notification with this :
Events 3333 = {al/off}
would it be ok to do this to stop it?
Events 3333 = {}

I know it is a pretty stupid example since the off hook is going to come just one time. but it's just an example :P 
well if anybody can pinpoint me it would be great.
Thanks.

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

*********************** FSS-Restricted ***********************
"DISCLAIMER: This message is proprietary to Flextronics Software 
Systems Limited (FSS) and is intended solely for the use of the 
individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for 
any purpose other than for what it is intended. If you have received 
this message in error, please notify the originator immediately. 
If you are not the intended recipient, you are notified that you are
strictly prohibited from using, copying, altering, or disclosing
the contents of this message. FSS accepts no responsibility for
loss or damage arising from the use of the information transmitted
by this email including damage from virus."

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