- sg16-avd - lists.packetizer.com

From H.245 tunneling to separate connection?
by Paul Long 17 Aug '99

17 Aug '99

Why would an EP ever want to switch from H.245 tunneling to a separate H.245 connection? What possible use could there be in such a thing? Paul Long Smith Micro Software, Inc.

3 2

CallId/ConfId in LRQ
by Manoj Paul 16 Aug '99

16 Aug '99

Hi, Presently, when a GK needs to resolve some aliasaddress, it sends LRQ to another GK which has a co-located Border Element (BE). This BE may need to generate an Access Request (according to H.225 Annex G), to another BE. It might be mandatory for the requesting BE to include callInformation (callId/ConfId) in this Access Request (depending on the address template it holds). But LRQ message does not have a callId field in it. How can the requesting BE then derive … [View More]

2 1

CallId/ConfId in LRQ.
by Manoj Paul 16 Aug '99

16 Aug '99

Hi, Presently, when a GK needs to resolve some aliasaddress, it sends LRQ to another GK which has a co-located Border Element (BE). This BE may need to generate an Access Request (according to H.225 Annex G), to another BE. It might be mandatory for the requesting BE to include callInformation (callId/ConfId) in this Access Request (depending on the address template it holds). But LRQ message does not have a callId field in it. How can the requesting BE then derive … [View More]

1 0

Re: RTP question!!
by Aparna Saha 13 Aug '99

13 Aug '99

Hello Deepak, RTP states that in case a source changes its source transport address, it must also choose a new SSRC identifier . ( Refer to the last line of the description of SSRC as a field of the RTP Header. Section A.5.1, H.225 ). Hence, no SSRC collision will be registered. After changing the DSP (also resulting in change of IP address - assuming that it is associated with a different NIC), the source transport address as well as the SSRC changes as a result of which the receiver … [View More]

2 1

H.248 proposed changes being discussed
by Nancy-M Greene 12 Aug '99

12 Aug '99

Based on the msg I sent out after Berlin entitled "Results from the ITU SG16 Berlin mtg", I have just sent out a series of msgs to the megaco list proposing actual edits to Megaco/H.248 to incorporate the changes suggested in Berlin. If you would like to be a part of this discussion, it would be a good idea to join the megaco mailing list. If you would just like to see what is being discussed, you can go to the Megaco archive at http://standards.nortelnetworks.com. I don't think this should be … [View More]

1 0

Re: H.245v6 ASN.1 tree?
by Paul Long 12 Aug '99

12 Aug '99

Mike, Oh, yeah, you're right! I gotta get used to genericCapabilities. Without looking closely at the other TDs, I thought they introduced new syntax. Thanks. So even though H.323v3 is Decided, we may modify the syntax for H.245v6, based on SG8's response regarding T.38? Paul Long Smith Micro Software, inc. -----Original Message----- From: mike.nilsson(a)BT.COM To: ITU-SG16(a)MAILBAG.INTEL.COM Sent: 8/12/99 1:56 AM Subject: Re: H.245v6 ASN.1 tree? Paul, The only change to the syntax for … [View More]

1 0

Re: H.245v6 ASN.1 tree?
by mike.nilsson＠BT.COM 12 Aug '99

12 Aug '99

Paul, The only change to the syntax for V6 that I am aware of is the change given below (from TD69/PLEN of Santiago), where ** is used to label additions. MediaTransportType ::=CHOICE { ip-UDP NULL, ip-TCP NULL, atm-AAL5-UNIDIR NULL, -- virtual circuits used as unidirectional atm-AAL5-BIDIR NULL, -- virtual circuits used as bidirectional ..., ** atm-AAL5-compressed SEQUENCE ** { ** variable-delta … [View More]

1 0

Berlin meeting report APC-1644
by Sakae OKUBO 12 Aug '99

12 Aug '99

Dear Q12-14/16 experts, Draft meeting report of the Berlin meeting has been placed at the PictureTel ftp site as: ftp://standard.pictel.com/avc-site/Incoming/APC-1644.zip or http://standard.pictel.com/ftp/avc-site/Incoming/APC-1644.zip I have edited this document by integrating TD-20, 21, 22, 23 and other relevant materials. Though there are still some points needing confirmation of Q13 and Q14 Rapporteurs (as indicated with yellow marks), please review this draft, list of participants in … [View More]

1 0

Fwd: TD-27a
by Sakae OKUBO 12 Aug '99

12 Aug '99

Dear Q12-14/16 experts, In response to Mr. Coldren's request as attached, TD-27a.zip has been placed at the /9908_Ber directory. TD-27.zip there will be removed. The convention for the file name is as follows: TD-nn.zip - initial submission TD-nna.zip - first revision TD-nnb.zip - second revision etc. whatever name the file had when posted. Best regards, Sakae OKUBO (Mr.) *********************************************************** Waseda Research Center Telecommunications Advancement … [View More]

1 0

H.245v6 ASN.1 tree?
by Paul Long 12 Aug '99

12 Aug '99

Has a complete ASN.1 syntax been put together for H.245v6, the version used by H.323v3? If so, where I can find it online? I guess it would be H.245v5 with the Santiago TDs applied. I can combine them on my own, but I'd like something with which to corroborate my result. Paul Long Smith Micro Software, Inc.

1 0