Re: Paper on multimedia contexts in H.gcp/megacoP (pdf format)
John, I would like to clarify the distributed multi media functionality. If you take an H.323 MCU instead of implementing T.120 in the same physical equipment you can use an external T.120 MP and using the option of opening a logical channel to it using a different IP/Port address. The MGC still has to know that it is one call, if the end points does a disconnect, the MGC should also disconnect the T.120 part. Another point about H.323/H.320 gateway is that in H.320 you open an mlp/hmlp channel that can be used for T.120 but may also serve for H.281 FECC, if an H.281 FECC data comes the MG should tell the MGC to start an H.282/283 FECC termination on the H.323 side. Regards Roni ********************************************** Roni Even VP Product Marketing Accord Video Telecommunication Email: roni_e@accord.co.il Tel: +972-3-9251412 Fax: +972-3-9211571 ***************************************************
-----Original Message----- From: John Segers [SMTP:jsegers@LUCENT.COM] Sent: Monday, May 03, 1999 6:19 PM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Paper on multimedia contexts in H.gcp/megacoP (pdf format)
Attached you'll find a document explaining how multimedia contexts could work. The document is still evolving (see notes on the last page), but I thought I'd better get it out in time for people to be able to look at it before tomorrow's conference call.
Regards,
John Segers -- John Segers email: jsegers@lucent.com Lucent Technologies Room HE 344 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954 << File: mm-hgcp.pdf >>
Roni, I agree with your point that in case there are multiple MGs that handle multiple media in a call, the MGC is the entity that should tie it all together. It can certainly do so if no lip sync is necessary between the involved MGs. The MGs don't even have to know that there's another MG involved in the call. On the other subject, far end camera control, I'm not familiar with H.282/H.283. If the protocols are there for both H.320 and H.323 side and the MG only has to translate/transport the information, the model is flexible enough to fit it in. Regards, John Roni Even wrote:
John, I would like to clarify the distributed multi media functionality. If you take an H.323 MCU instead of implementing T.120 in the same physical equipment you can use an external T.120 MP and using the option of opening a logical channel to it using a different IP/Port address. The MGC still has to know that it is one call, if the end points does a disconnect, the MGC should also disconnect the T.120 part. Another point about H.323/H.320 gateway is that in H.320 you open an mlp/hmlp channel that can be used for T.120 but may also serve for H.281 FECC, if an H.281 FECC data comes the MG should tell the MGC to start an H.282/283 FECC termination on the H.323 side. Regards Roni
********************************************** Roni Even VP Product Marketing Accord Video Telecommunication Email: roni_e@accord.co.il Tel: +972-3-9251412 Fax: +972-3-9211571 ***************************************************
-----Original Message----- From: John Segers [SMTP:jsegers@LUCENT.COM] Sent: Monday, May 03, 1999 6:19 PM To: ITU-SG16@MAILBAG.INTEL.COM Subject: Paper on multimedia contexts in H.gcp/megacoP (pdf format)
Attached you'll find a document explaining how multimedia contexts could work. The document is still evolving (see notes on the last page), but I thought I'd better get it out in time for people to be able to look at it before tomorrow's conference call.
Regards,
John Segers -- John Segers email: jsegers@lucent.com Lucent Technologies Room HE 344 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954 << File: mm-hgcp.pdf >>
-- John Segers email: jsegers@lucent.com Lucent Technologies Room HE 306 Dept. Forward Looking Work phone: +31 35 687 4724 P.O. Box 18, 1270 AA Huizen fax: +31 35 687 5954
participants (2)
-
John Segers -
Roni Even