Re: H.248 Syntax im H.323 Annex L

26 Feb 2001


      Hi John,
Is it not that we are just emulating MGCP model in the Stimuls COntrol
Protocol provided by H.323 Annex L? I mean, the way a MGC controls an MG
using H.248, an Annex L Feature Server controls an H.323 endpoint. According
to my understanding it is just that H.248 is used "as is" for the later.
   Why do we need to tunnel H.248 and between what entities
in the network?
I shall appreciate your comments in this.
thanks
Manoj.
-----Original Message-----
From: Li, John [mailto:John.Li@Dialogic.com]
Sent: Monday, February 26, 2001 12:15 PM
To: 'Paul, Manoj'
Subject: RE: H.248 Syntax im H.323 Annex L
I think, By doing that, H.248 information can be tunneled within h.245
messages, so the H.248 section can be processed by a MEGACO entity directly
for interoperability.
Although BER was not a optimal solution (nor was SDP) for encoding in
MEGACO, SIG 16 allows it to be used.
John
-----Original Message-----
From: Paul, Manoj [mailto:mpaul@TRILLIUM.COM]
Sent: Monday, February 26, 2001 2:13 PM
To: ITU-SG16@mailbag.cps.INTEL.COM
Subject: H.248 Syntax im H.323 Annex L
Hi All,
Could someone point out the reason for keeping h248Message codepoint
as
OCTET STRING in stimulusControl IE in H.323 Version 4 for Annex L support.
        H.323 Annex L specifies h248Message as OCTET STRING in
stimulusControl code
point. This surely saves importing H.248 ASN.1 syntax in H.323, but it does
require the user to encode/decode H.248 PDUs as text/BER. And then re-encode
the H248
message as an OCTET STRING using PER in H.323 UUPDU.
 Was there any reason why the specific H.248 codepoints were not imported in
H.323
so that the user may have to use only PER encode scheme to encode
simulusControl
IE. Does not the earlier approach necessiates the user to have H.248
implementation
with H.323 to support Annex L?
Thanks for your time,
Manoj Paul.
Trillium Digital Systems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv@mailbag.intel.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
For help on this mail list, send "HELP ITU-SG16" in a message to
listserv@mailbag.intel.com