[trimming sip list] The answer to your question is below. However, the mechanism described in the I-D in the subject line is *not* being pursued within the IETF. Again, there is current work being done to define a general and widely applicable framework and mechanisms for the problem domain.
Himanshoo wrote: > Thanks for your clarification. But let me clarify one last thing : > > >>>1. It says that MGCP subtype can be used to indicate the protocol >>> > between > >>>MGC and MG and then some MGCP message can be encapsulated to request and >>>report the events as per MGCP packages. Does this mean that I can send >>> > the > >>>complete command line ( I mean whole of RQNT) as message body for the >>> > INFO > >>>request. It is needed since I also need to identify the end point where >>> > I > >>>want event to be detected. >>> >> >>The idea was that the the call identifying info in the SIP request would >>be used by the MGC to identify MGCP/Megaco connection. Just as it would >>for any other interworking function. The only proposed INFO message >>content was the actual event request/notification. >> > > As per your mail , it says : > "The only proposed INFO message content was the actual event > request/notification." > Does this mean (a part of or full ) event request / notification message , > as per MGCP ? > As per section 5 in the I-D, only the RequestedEvents, DigitMap and ObservedEvents parameters defined for the specific MGCP package would be present in the body of an INFO request. Just as they would appear in a MGCP message. No other MGCP protocol elements would be present as they are not needed for the limited function of requesting and reporting MGCP package events. Best regards, Bert > Best Regards > Himanshoo > > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
