IETF Logo Mail Archive

Re: [MMUSIC] RFC 7261 [codec G729AB]

Jan Bollen <jan.bollen@scarlet.be> Thu, 23 January 2020 11:06 UTC

Return-Path: <jan.bollen@scarlet.be>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7883512001E for <mmusic@ietfa.amsl.com>; Thu, 23 Jan 2020 03:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level:
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=scarlet.be
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UT3RMs0O9kWz for <mmusic@ietfa.amsl.com>; Thu, 23 Jan 2020 03:06:45 -0800 (PST)
Received: from eir.is.scarlet.be (eir.is.scarlet.be [193.74.71.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AD72120024 for <mmusic@ietf.org>; Thu, 23 Jan 2020 03:06:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scarlet.be; s=scarlet; t=1579777602; bh=bMcKPWYRv0BeEHO5rzNOG1QKOJoa3IBLbtjB0+zNhtM=; h=MIME-Version:Content-Type:Date:From:To:Cc:Subject:Reply-To: In-Reply-To:References:Message-ID; b=fbRsKjqGywb371LmNMEFHhN4Zcze5wJ3529DVtRrPjX4nBHYLwG2loe2kPhLg77ut ichijWP+EqpT9sjfZVoJYce965ZoFuf3LCZaQ5jwPmw51wbFQIr/6p9m0f+GLhbs+P vSrEXRzgm3JFYgFg0KJhci/Ah5Sn7MQY5sYC/DaQ=
Received: from webmail.scarlet.be (gresham.is.scarlet.be [193.74.71.215]) by eir.is.scarlet.be (8.15.2/8.14.9) with ESMTP id 00NB6fqj026599; Thu, 23 Jan 2020 12:06:42 +0100
X-Scarlet: d=1579777602 c=193.74.71.215
Received: from mail2.demensen.be ([194.78.77.186]) via mail2.demensen.be ([194.78.77.186]) by webmail.scarlet.be with HTTP (HTTP/1.1 POST); Thu, 23 Jan 2020 12:06:41 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_5a5ca1156f6b13ddb54e85468ca59d33"
Date: Thu, 23 Jan 2020 12:06:41 +0100
From: Jan Bollen <jan.bollen@scarlet.be>
To: mmusic@ietf.org
Reply-To: jan.bollen@scarlet.be
Mail-Reply-To: <jan.bollen@scarlet.be>
In-Reply-To: <AM5PR0402MB280329F383E5BE82C7C8AC5EF30D0@AM5PR0402MB2803.eurprd04.prod.outlook.com>
References: <AM5PR0402MB280329F383E5BE82C7C8AC5EF30D0@AM5PR0402MB2803.eurprd04.prod.outlook.com>
Message-ID: <3ddbe74cd11b0346d4823ea42775517c@scarlet.be>
X-Sender: jan.bollen@scarlet.be
User-Agent: Scarlet Webmail
X-DCC-scarlet.be-Metrics: eir; whitelist
X-Virus-Scanned: clamav-milter 0.98.1-exp at eir
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/sC6CyvKk68m3a6yhemzlfdtCfog>
Subject: Re: [MMUSIC] RFC 7261 [codec G729AB]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2020 11:06:48 -0000

  

Bonjour, 

 RFC3551 states: 

_A reduced-complexity version of the
G.729 algorithm is specified in Annex A to Rec. G.729. The speech coding
algorithms in the main body of G.729 and in G.729 Annex A are fully
interoperable with each other, so there is no need to further
distinguish between them. _ 

Hence I would think that Annex B (VAD &
CNG) indication in the SDP attribute rtpmap/fmtp should work for G729
and G729A:

a = rtpmap:18 G729/8000
a = fmtp:18 annexb=yes

The
publication of G729 Annex B can be found on the ITU specs pages. E.g. :
https://www.itu.int/rec/T-REC-G.729/fr

cheers,
jan

On Tue, 21 Jan 2020
10:48:14 +0000, Hicham EL ALAOUI wrote: 

> Bonjour, 
> 
> J'ai une
question à vous poser si vous pouvez m'aider : 
> 
> Le RFC 7261, publié
par l'IETF en mai 2014, ne prévoyait pas le CODEC G729AB, actuellement
je cherche sa date et sa publication par l'IETF. 
> 
> Merci d'avance
pour votre aide. 
> 
> Hicham EL ALAOUI​
> 
> Customer Support
Engineer
> 
> Mobile : 
> 002126 68 40 21 23
> 
> Phone : 
> +212 5 22
58 16 00
> 
> Siham 20, n°9 La colline
> Sidi Maarouf, 20190
>
Casablanca, Maroc 
> 
> WWW. [1]VOCALCOM [2].COM [3]
> 
> [4]
> 
> [5]
>

> [6]
> 
> [7]
> 
> [8]
> 
> [9]
> 
> [10]
> 
> Please consider the
environment before printing this email. If you are not the intended
recipient of this message, then please delete it and notify the
sender.

  

Links:
------
[1] https://www.vocalcom.com/
[2]
https://www.vocalcom.com/
[3] https://www.vocalcom.com/
[4]
https://www.vocalcom.com/en/latest-blog/?no-cache
[5]
https://www.linkedin.com/company/vocalcom
[6]
https://www.facebook.com/Vocalcom/
[7]
https://www.instagram.com/vocalcom/
[8] https://twitter.com/vocalcom
[9]
https://www.youtube.com/user/vocalcom
[10]
https://www.vocalcom.com/en/next-event/?no-cache

v2.23.0 | Report a Bug | By Email