> -----Original Message-----
> From: Barry Desborough [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 20, 2001 7:13 AM
> To: '[EMAIL PROTECTED]'
> Cc: [EMAIL PROTECTED] (E-mail)
> Subject: RE: [Sip-implementors] Encoding names in SDP rtpmap
> attributes
>
>
> Thanks, but this does not cover some examples I've seen recently, viz.
>
> a=rtpmap:96 G.729a/8000/1
> a=rtpmap:97 G.726-16/8000/1
> a=rtpmap:98 G.726-24/8000/1
>
> (from a Cisco IAD I believe)
>
> Is there no choice but to trawl through all the drafts in
> case they mention
> a new encoding name?
Ultimately, all of these will be registered under IANA, and can be found
under the IANA media types registration page.
However, the AVT group has not completed this work yet. As such, the IANA
registrations are in an internet-draft:
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-mime-04.txt
I will note that the update of rfc1890 specifies that G.729 and G.729a do
not need to be distinguished from a signaling perspective, which would
explain why there is no name for g.729a. As such, it would appear that this
Cisco IAD is non-compliant. Furthermore, the media type for G.729 is "G729",
without the period, so this is an error on the part of this device.
Similarly, the names for G.726 codecs above are incorrect in the above
device output. For the 24 bit one, its "G726-24" as specified in the update
to rfc1890. I'm not sure why "G726-24" doesn't appear in the MIME type
registration draft, though. Perhaps some of the avt folks, cc'd, can
comment.
Thanks,
Jonathan R.
---
Jonathan D. Rosenberg 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.cs.columbia.edu/~jdrosen PHONE: (973) 952-5000
http://www.dynamicsoft.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
