What is the difference between G.723.1 and G.723? And I don't mean the
numerical difference, as in 0.1 :-) Are they the same thing, and people are
just being imprecise when they refer to G.723.1 as "G.723?" For SuperOp!
scheduling, they were both listed as two of the possible audio codecs, as if
they were different. Does anyone truly support G.723 but not G.723.1? If so,
I've never come across such an implementation. Also, what is the history of
G.723.1? I believe the current version is …
[View More]something called 5.1. Is this
correct? Were there some intermediate versions?
Paul Long
Smith Micro Software, Inc.
[View Less]
Paul,
G.723 was an old ITU-T Recommendation that has been withdrawn
and has nothing to do with G.723.1. So, when people today use
G.723 they usually mean G.723.1.
For the software version this is a bit confusing:
For the most current version it is best to look up the ITU-T Database:
http//www.itu.int.
Unfortunately, in the text of the Recommendation no reference is made to the
actual C-Code version (we have requested to have a better version control
for the future Recommendations). On the top …
[View More]of it since C-Code
is also a program (contains as many bugs as any other program...:-( ), in
some of the
past SG meeting bugs were corrected (so you have to go through the SG16
reports). I am not sure whether eventually the bug corrections have been
also
incorported into the C-Code that the ITU is currently selling as the latest
version. So, my message is that extrem care is needed not to miss
something.
Regards,
Istvan
--------------------------------------------------------------------------
Dr. Istvan Sebestyen
Siemens AG, ICN WN ES SP 4,
Hofmannstr. 51 D-81359 Munich
Tel:+49-89-722-47230
Fax:+49-89-722-47713
E-Mail: istvan.sebestyen(a)icn.siemens.de
Intranet:http://netinfo.icn.siemens.de/es/team/essp/team/essp4
----------------------------------------------------------------------------
----------------
> ----------
> From: Paul Long[SMTP:plong@SMITHMICRO.COM]
> Reply To: Mailing list for parties associated with ITU-T Study Group
> 16
> Sent: Wednesday, October 06, 1999 5:29 PM
> To: ITU-SG16(a)mailbag.cps.intel.com
> Subject: G.723.1 vs. G.723
>
> What is the difference between G.723.1 and G.723? And I don't mean the
> numerical difference, as in 0.1 :-) Are they the same thing, and people
> are
> just being imprecise when they refer to G.723.1 as "G.723?" For SuperOp!
> scheduling, they were both listed as two of the possible audio codecs, as
> if
> they were different. Does anyone truly support G.723 but not G.723.1? If
> so,
> I've never come across such an implementation. Also, what is the history
> of
> G.723.1? I believe the current version is something called 5.1. Is this
> correct? Were there some intermediate versions?
>
> Paul Long
> Smith Micro Software, Inc.
>
[View Less]
Dear Mr. Potter,
> Title: Object Profile for ISUP Transport in H.225 using Generic Extensible
> Framework.
>
> Source: Tony Stephens, BT.
APC-1694 has been allocated to your contribution.
Best regards,
Sakae OKUBO (Mr.)
***********************************************************
Waseda Research Center
Telecommunications Advancement Organization of Japan (TAO)
5th Floor, Nishi-Waseda Bldg.
1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 Japan
Tel: +81 3 5286 3830
Fax:…
[View More] +81 3 5287 7287
e-mail: okubo(a)giti.or.jp
***********************************************************
[View Less]
Dear contributors,
The following APC numbers have been allocated to your contributions:
Mr. Potter,
APC-1683
>Title: ISUP Transport in H.225 using a Generic, Extensible Framework.
>
>Source: Morgan Potter, BT.
Mr. Anderson,
APC-1684
>Title: Multiple UsageIndications in Annex G
>Source: Terry Anderson, Lucent Technologies and Lior Moscovici,
>VocalTec
>
>Abstract: Specifying the meaning and use of multiple usageIndication
>messages for a single call.
&…
[View More]gt;Purpose: for discussion
APC-1685
>Title: Using CPL with H.323
>Source: Terry Anderson, Lucent Technologies
>Abstract: The use of Call Processing Language (CPL) with H.323 will
>require changes to both H.323 and the current CPL draft. This
>document descibes some of the issues and the work that must be done.
Mr. Bowen,
APC-1686
>Source: Editor (R Bowen)
>Title: Draft H.225.0 v4"
Mr. Coldren,
APC-1687
>SOURCE* : Lucent Technologies
>TITLE : H.323 Annex F Hookflash Signaling Enhancements
>PURPOSE : Proposal
Mr. Hellstrom,
APC-1688
>Source: Gunnar Hellstr $BSN (B, LM Ericsson
>Title: H.323 Annex G Text Conversation, draft
>Purpose: Discussion
>Abstract: Some small changes are made after Berlin to the text
>conversation annex G to H.323.
APC-1689
>Source: Gunnar Hellstr $BSN (B, Ericsson
>Title: RTP-Text for H.323 Annex G Text Conversation
>Purpose: Information
>Abstract: An RTP embedding of T.140 is specified in the IETF avt.
APC-1690
>Source: Gunnar Hellstr $BSN (B, Ericsson
>Title: F.MCVS conversation service description with Total
>Conversation and Text telephony.
>Purpose: Information and discussion
>Abstract: Draft service description, with Total Convaersation and
>Text Telephony included
APC-1691
>Source: Gunnar Hellstr $BSN (B, LM Ericsson
>Title: H.248 packages and additions for text telephony and total
>conversation.
>Purpose: Discussion and proposal
>Abstract: A collection of proposed additions to H.248 and its annexes
>for gateways supporting Total Conversation including text telephony .
Mr. Qiaobing Xie,
APC-1692
>Source: Motorola
>Title: Using SCTP as an Alternate H.248 Transport
Mr. Jones,
APC-1693
>Source: Editor (P Jones)
>Title: H.323 Implementers Guide
Best regards,
Sakae OKUBO (Mr.)
***********************************************************
Waseda Research Center
Telecommunications Advancement Organization of Japan (TAO)
5th Floor, Nishi-Waseda Bldg.
1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 Japan
Tel: +81 3 5286 3830
Fax: +81 3 5287 7287
e-mail: okubo(a)giti.or.jp
***********************************************************
[View Less]
Michaela,
This is what I have. Not sure that is the latest. I think (but again not sure)
that these annexes will only
be part of REV4, not REV3
(See attached file: H323_AnnexF-05-ncm.doc)(See attached file:
H323_AnnexF_comments.doc)
Michaela Goffri <Michaela_Goffri(a)3COM.COM> on 10/05/99 11:23:44 AM
Please respond to Mailing list for parties associated with ITU-T Study Group 16
<ITU-SG16(a)mailbag.cps.intel.com>
Sent by: Michaela Goffri <Michaela_Goffri(a)3COM.…
[View More]COM>
To: ITU-SG16(a)mailbag.cps.intel.com
cc: (Offer Pazy/IL/3Com)
Subject: Looking for H.323 Annex docs
Hi,
Does anyone know where I can get the H.323: Annex F and Annex J documents?
Thanks,
Michaela
[View Less]
Draft H.323 Annex J as APC-1674 will be shorty finalized and presented at the next Rapp. meeting.
Approved recommendation H.323 Annex F is available from the ITU.
Martin
-----------------------------------------------------------------------
| Dipl.-Inf. Phone: +49 89 636-46201
| Martin Euchner Fax : +49 89 636-48000
| Siemens AG
| ZT IK 3 mailto:Martin.Euchner@mchp.siemens.de
| Intranet: http://zt-…
[View More]security.mchp.siemens.de/Standardization/ITU-T_SG16/index.html
| Otto-Hahn-Ring 6 Internet: http://www.siemens.de
| D-81730 Muenchen
| __________________
| Germany
-----------------------------------------------------------------------
> -----Original Message-----
> From: Michaela Goffri [SMTP:Michaela_Goffri@3COM.COM]
> Sent: Tuesday, October 05, 1999 11:24 AM
> To: ITU-SG16(a)mailbag.cps.intel.com
> Subject: Looking for H.323 Annex docs
>
> Hi,
>
> Does anyone know where I can get the H.323: Annex F and Annex J documents?
>
> Thanks,
> Michaela
[View Less]
Dear Skip Cave,
In response to your request, APC-1682 has been allocated to your contribution.
SC> DOCUMENT TITLE: Media Redirection and Replication
SC>
SC> PURPOSE: The contribution proposes that the functional
SC> entities described in this
SC> contribution be included in the H.323 V4 document.
SC>
SC> ABSTRACT: This contribution identifies and describes
SC> the requirements for a
SC> distributed switching/conferencing …
[View More]functionality in H.323 networks.
Best regards,
Sakae OKUBO (Mr.)
***********************************************************
Waseda Research Center
Telecommunications Advancement Organization of Japan (TAO)
5th Floor, Nishi-Waseda Bldg.
1-21-1 Nishi-Waseda, Shinjuku-ku, Tokyo
169-0051 Japan
Tel: +81 3 5286 3830
Fax: +81 3 5287 7287
e-mail: okubo(a)giti.or.jp
***********************************************************
[View Less]
Hi All,
I have a few concerns about H.323 Annex E proposed document.
My reference is the "Proposed changes to H.323 Annex E"
document which was presented at Santiago meeting of SG13/16.
Section E.1.3.2 states Serial Model. It says that Annex E
stack will wait until a positive reply is returned * for the
same Session-Identifier *. This means that an outgoing Annex
E PDU can only contain multiple payloads of the same session
only. Second, it implies that the sequence number (which is
…
[View More]present in Annex E PDU header) must be
unique now across < sender host+port, rcv host+port, session-id>.
We can not make sequence number unique across <sender host+port,
rcv host+port> only, because the message sequences should be blocking
only for same session-identifier, as stated by the NOTE appended
below section E.1.3.2.
The Annex E Ack message, however, only contains the sequence
number of Annex E PDU. How can the sender of an Annex E PDU
will distinguish for what session's PDU this ack has come for?
Because sender might have sent Annex E PDUs with the same
sequence number for different sessions over a given < sender host+port,
rcv host+port>.
Am I missing something here. I will appreciate any clarifications
on the above.
regards,
Manoj Paul.
[View Less]
Dear Mr. OKUBO:
I am sending this mail again. Please issue the APC numbers for three
contributions as indicated earlier.
Best regards,
Radhika R. Roy, AT&T
> -----Original Message-----
> From: Roy, Radhika R, ALARC
> Sent: Thursday, September 30, 1999 1:57 PM
> To: 'okubo(a)giti.or.jp'
> Subject: APC Numbers
>
> Dear Mr. OKUBO:
>
> Please provide APC numbers for the following contributions (expected to be
> joint contributions along with other …
[View More]companies, but the names of other
> companies will be provided at the time of actual distribution):
>
> 1. Call Flows Supporting H.323 QOS
> 2. Extensions of H.225.0 and H.225.0 Annex G Signaling Messages and their
> ASN.1 Syntax to Support H.323 QOS
> 3. Framework for Mapping of H.323 QOS over Packet-based Networks
>
> Best regards,
>
> Radhika R. Roy
> AT&T
> + 1 732 420 1580
[View Less]
