RE: Megaco Event Descriptor question

Raphael,
 
RFC 3525 says that tonedet package is a extend only package and it defines "*" as the only possible tone id:
 
E.4 Tone Detection Package (of 3225)
Possible values: "wildcard" as defined above is the only value defined in this package. Extensions to this package would add additional possible values for tone id.

Given that, what should the MG send to MGC on detecting a tone.
 
- ramesh


 _____ 
From: Raphael Tryster [mailto:[email protected]] Sent: Thursday, December 27, 2007 2:55 PMTo: Ramesh Babu Kuppili; [email protected]: RE: [Megaco] Megaco Event Descriptor question
After the second Modify, the GW would only report tones detected according to the new Events descriptor in that command, and would no longer process the digit map.  The quote at the end of your message is applicable, exept that it is from H.248.1, not RFC 3435 which describes MGCP.
 
Raphael Tryster (not a guru but standing in for vacationing gurus)

 _____ 
From: Ramesh Babu Kuppili [mailto:[email protected]] Sent: Thursday, December 27, 2007 11:14 AMTo: [email protected]: [Megaco] Megaco Event Descriptor question
Hello Gurus,
 
I have a question about Megaco Event Descriptor.  I am receiving the following message from the MGC.
 
!/1 [xx.xx.xx.xx]:2944 T=372855742{C=-{MF=A1{E=369098767{dd/ce{DM=dmap1},al/*},SG{cg/dt},DM=dmap1{(1xx|9xx|0[2-9]xxx|00[1-9]xxxx|[2-8]xxxxxx|0[2-9]xxxxxxx|05xxxxxxxx|E|F|x.F|[0-9].L)}}}
 
The event descriptor in the above message is asking the GW to use ditigmap "dmap1".  After sometime we are receiving the following message from MGC:
 
!/1 [xx.xx.xx.xx]:2944 T=372855743{C=-{MF=A1{E=369098752{tonedet/std{tl=*},al/*},SG{}}}
 
Please note that the event descriptor in the above message does not have any digitmap event.  The quesion is, "on receiving the seocond modify from MGC, should GW still be detecting DTMF to be reported immediately to the switch based on the dtmp package received in the first modify message.  
 
Or should it overwrite its event decriptor with the one from second Modify (RFC 3435 seems to propose this).  Thereby not detecting any DTMF after the second modify is received.
 
text from RFC 3435
"An EventsDescriptor received by a media gateway replaces any previous Events descriptor. Event notification in process shall complete, and events detected after the command containing the new EventsDescriptor executes, shall be processed according to the new EventsDescriptor." (section 7.1.9).
 
Thanks for your time.
 
- ramesh
 _____ 
IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only.If you have received this email in error, please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies thereof.*** eSafe scanned this email for viruses, vandals, and malicious content. *** 
 _____

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