search for: ebw

Hi, I have a few questions/remarks about the draft, in particular about the SDP usage of Speex (section 5): - Which samplerate should be used if you receive something like m=3Daudio 8008 RTP/AVP 97 a=3Drtpmap:97 speex/8000 a=3Dfmtp:97 sr=3D16000;ebw=3Dultra - There is an inconsistency in the description of the 'penh'parameter. According to the description, only the values '0' or '1' are valid. In section 6.1 however, the default values are defined as: ebw=3Dnarrow;mode=3;vbr=off;cng=off;ptime=20;sr=800...

All: Attached please find yet another RTP profile revision (v5). You can also find the document at: http://www.herlein.com/downloads/speex/docs/ Changes: - added vbr, cng, ebw, sr optional parameters to MIME - added vbr, cng, ebw a=fmtp options for SDP use - added required document attributes for submission to IETF and IANA (format and author contact information). Note that we also clearly state that the default mode is narrowband mode 3 (8kbps) with constant bit rat...

...be greater than zero." It might also be a good idea to say that even if an offerer would like to receive 20ms, the sender MAY use a different packetization interval... This is the origin of numerous interop issue with speex in SIP applications. sr: actual sample rate in Hz. ebw: encoding bandwidth - either 'narrow' or 'wide' or 'ultra' (corresponds to nominal 8000, 16000, and 32000 Hz sampling rates). Both the "sr" and "ebw" conflicts with speex/XXXX rtpmap. I really recommend to remote both those definition so that app...

...0, 0, 0, 0, 0, 0), correlation = corSymm()) > levels(kew$Season)==levels(x.for.lw.pred$Season) [1] TRUE TRUE TRUE TRUE > kew[1:10,] Grouped Data: lw ~ ageyr2 | farm X sheep doe ageyr2 MBreEco Season ecoreg farm village Breed MBreed date doy lw ebw 1 1 1 1 2.500000 Meatsemidesert 1. Fall-Winter semidesert AksToKa Aksenger KZP Meat 11/23/02 327 63.8 55.63211 2 2 1 139 2.883333 Meatsemidesert 2. Spring semidesert AksToKa Aksenger KZP Meat 4/10/03 100 51.7 44.53119 3 3 1 250 3.191667 Meatsemidesert 3. S...

...would like > to receive 20ms, the sender MAY use a different packetization interval... > This is the origin of numerous interop issue with speex in SIP > applications. Sounds fair. Just curious, what's the exact interop issue? > sr: actual sample rate in Hz. > > ebw: encoding bandwidth - either 'narrow' or 'wide' or 'ultra' > (corresponds to nominal 8000, 16000, and 32000 Hz sampling rates). > > Both the "sr" and "ebw" conflicts with speex/XXXX rtpmap. I really > recommend to remote both those defi...

...ER); return 0; } The above means: If you negotiate a different packetisation interval: just recompile ;( Weird... Old speex implementation in asterisk was doing the same, it seems it's now fixed in latest version. >> sr: actual sample rate in Hz. >> >> ebw: encoding bandwidth - either 'narrow' or 'wide' or 'ultra' >> (corresponds to nominal 8000, 16000, and 32000 Hz sampling rates). >> >> Both the "sr" and "ebw" conflicts with speex/XXXX rtpmap. I really >> recommend to remote...

...pe: speex Required parameters: Herlein, Valin, etc [Page 3] ^L Internet-Draft RTP Payload Format for the Speex Codec Nov 2002 Optional parameters: ptime: duration of each packet in milliseconds. sr: actual sample rate in Hz. ebw: encoding bandwidth - either 'narrow' or 'wide' or 'ultra' (corresponds to nominal 8000, 16000, and 32000 Hz sampling rates). vbr: variable bit rate - either 'on' 'off' or 'vad'. cng: comfort noise generation - either &...

qemu-stubdom was stripping the prefix from the "params" xenstore key in xenstore_parse_domain_config, which was then saved stripped in a variable. In xenstore_process_event we compare the "param" from xenstore (not stripped) with the stripped "param" saved in the variable, which leads to a medium change (even if there isn't any), since we are comparing something

On Tue, Dec 17, 2002 at 11:55:21PM -0800, Greg Herlein wrote: > If such a thing happens, discussion of the RTP profile draft > would be most welcome - please get responses back to the > list! Now, if this were finalised before the conference then we could do a demo and use it for broadcasting the lectures streams around the world... What is currently the best way of doing this? I'm

...quot;). An other way to make recommendations to the remote speex encoder is to use its specific parameters via the a=fmtp: directive. The following parameters are defined for use in this way: ptime: duration of each packet in milliseconds. sr: actual sample rate in Hz. ebw: encoding bandwidth - either 'narrow' or 'wide' or 'ultra' (corresponds to nominal 8000, 16000, and 32000 Hz sampling rates). vbr: variable bit rate - either 'on' 'off' or 'vad' (defaults to off). If on, variable bit rate...

...;). An other way to make recommendations to the remote Speex encoder is to use its specific parameters via the a=fmtp: directive. The following parameters are defined for use in this way: ptime: duration of each packet in milliseconds. sr: actual sample rate in Hz. ebw: encoding bandwidth - either 'narrow' or 'wide' or 'ultra' (corresponds to nominal 8000, 16000, and 32000 Hz sampling rates). Herlein, et al. Expires October 24, 2007 [Page 11] Internet-Draft Speex A...

...other way to make recommendations to the remote Speex encoder is to use its specific parameters via the a=fmtp: directive. The following parameters are defined for use in this way: ptime: duration of each packet in milliseconds. sr: actual sample rate in Hz. ebw: encoding bandwidth - either 'narrow' or 'wide' or 'ultra' (corresponds to nominal 8000, 16000, and 32000 Hz sampling rates). vbr: variable bit rate - either 'on' 'off' or 'vad' (defaults...

...other way to make recommendations to the remote Speex encoder is to use its specific parameters via the a=fmtp: directive. The following parameters are defined for use in this way: ptime: duration of each packet in milliseconds. sr: actual sample rate in Hz. ebw: encoding bandwidth - either 'narrow' or 'wide' or 'ultra' (corresponds to nominal 8000, 16000, and 32000 Hz sampling rates). vbr: variable bit rate - either 'on' 'off' or 'vad' (defaults...

...ndations to the remote Speex encoder > is to use its specific parameters via the a=fmtp: directive. The > following parameters are defined for use in this way: > > ptime: duration of each packet in milliseconds. > > sr: actual sample rate in Hz. > > ebw: encoding bandwidth - either 'narrow' or 'wide' or > 'ultra' (corresponds to nominal 8000, 16000, and > 32000 Hz sampling rates). > > vbr: variable bit rate - either 'on' 'off' or 'vad' > (defaults to off)....

The latest revision of the draft RTP Profile is attached for review. This will be submitted to the IETF Audio-Video Transport Working Group for consideration immediately, so if you have any more comments, let us know. In addition, we will be applying for an official MIME type. Note that the AVP code and the MIME type in this latest revision have been changed from "SPX" to

Hi. I''m a happy shorewall user. I found something that looks like a possible bug. I''m using shorewall on a single computer at home. I''m using the privoxy proxy server and dansguardian content filter. I configured shorewall based on the "one interface" example from the shorewall.net website. I set the firewall up so that users cannot directly connect to