search for: rtmap

...for wide band operation. If for some reason the offerer has bandwith limitations, he may use the "b=" header, as explained in SDP [4]. The following example illustrates the case where the offerer cannot receive more than 10 kbit/s. m=audio 8088 RTP/AVP 97 b=AS:10 a=rtmap:97 speex/8000 In this case, if the remote part agrees, it should configure its speex encoder so that it does not use modes that produce more than 10 kbit/s. Note that the "b=" constraint also applies on all payload types that may be proposed in the media line ("m=")...

...for wide band operation. If for some reason the offerer has bandwith limitations, he may use the "b=" header, as explained in SDP [5]. The following example illustrates the case where the offerer cannot receive more than 10 kbit/s. m=audio 8088 RTP/AVP 97 b=AS:10 a=rtmap:97 speex/8000 In this case, if the remote part agrees, it should configure its speex encoder so that it does not use modes that produce more than 10 kbit/s. Note that the "b=" constraint also applies on all payload types that may be proposed in the media line ("m=")...

...ltra-wide band operation. If for some reason the offerer has bandwith limitations, he may use the "b=" header, as explained in SDP [4]. The following example illustrates the case where the offerer cannot receive more than 10 kbit/s. m=audio 8088 RTP/AVP 97 b=AS:10 a=rtmap:97 speex/8000 In this case, if the remote part agrees, it should configure its speex encoder so that it does not use modes that produce more than 10 kbit/s. Note that the "b=" constraint also applies on all payload types that may be proposed in the media line ("m=")...

...If for some reason the offerer has bandwidth limitations, the client may use the "b=" header, as explained in SDP [4]. The following example illustrates the case where the offerer cannot receive more than 10 kbit/s. m=audio 8088 RTP/AVP 97 b=AS:10 a=rtmap:97 speex/8000 <p><p><p>Herlein, Valin, et. al. Expires January 30, 2004 [Page 5] ^L Internet-Draft draft-herlein-speex-rtp-profile-01 July 2003 <p> In this case, if the remote part agrees, it should configure its Speex encoder so that it do...

...ltra-wide band operation. If for some reason the offerer has bandwith limitations, he may use the "b=" header, as explained in SDP [4]. The following example illustrates the case where the offerer cannot receive more than 10 kbit/s. m=audio 8088 RTP/AVP 97 b=AS:10 a=rtmap:97 speex/8000 In this case, if the remote part agrees, it should configure its speex encoder so that it does not use modes that produce more than 10 kbit/s. Note that the "b=" constraint also applies on all payload types that may be proposed in the media line ("m=")...

...ted modes (all speex mode). > > > > > > > Herlein, et al. Expires December 7, 2007 [Page 13] > > Internet-Draft Speex June 2007 > > > m=audio 8088 RTP/AVP 97 > a=rtmap:97 speex/8000 > a=fmtp:97 mode=6;mode=any > > The offerer indicates the mode he wishes to receive (speex 'mode 3'). > This offer indicates mode 3 and mode 5 are supported and that no > other modes are supported. The remote party MUST not configure its...

...ration. If for some reason the offerer has bandwith limitations, he may use the "b=" header, as explained in SDP [5]. The following example illustrates the case where the offerer cannot receive more than 10 kbit/s. m=audio 8088 RTP/AVP 97 b=AS:10 a=rtmap:97 SPX/8000 In this case, if the remote part agrees, it should configure its speex encoder so that it does not use modes that produce more than 10 kbit/s. Note that the "b=" constraint also applies on all payload types that may be proposed in the media line ("m=")....

...hes to receive (speex 'mode 6') followed by all supported modes (all speex mode). Herlein, et al. Expires November 30, 2007 [Page 13] Internet-Draft Speex May 2007 m=audio 8088 RTP/AVP 97 a=rtmap:97 speex/8000 a=fmtp:97 mode=6;mode=any The offerer indicates the mode he wishes to receive (speex 'mode 3'). This offer indicates mode 3 and mode 5 are supported and that no other modes are supported. The remote party MUST not configure its encoder using another...

Do not forget to add the "Copying conditions" to the RFC. Check http://wiki.debian.org/NonFreeIETFDocuments That page contains a section titled "Template for RFC authors to release additional rights". To follow that guideline a section like the following should be added: x. Copying conditions The author(s) agree to grant third parties the irrevocable right to

...If for some reason the offerer has bandwidth limitations, the client may use the "b=" header, as explained in SDP [4]. The following example illustrates the case where the offerer cannot receive more than 10 kbit/s. m=audio 8088 RTP/AVP 97 b=AS:10 a=rtmap:97 speex/8000 In this case, if the remote part agrees, it should configure its Speex encoder so that it does not use modes that produce more than 10 kbit/s. Note that the "b=" constraint also applies on all payload types that may be proposed in the media line ("m=")...

...reason the offerer has bandwidth limitations, the client > may use the "b=" header, as explained in SDP [4]. The following example > illustrates the case where the offerer cannot receive more than > 10 kbit/s. > > m=audio 8088 RTP/AVP 97 > b=AS:10 > a=rtmap:97 speex/8000 > > > > > Herlein, Valin, et. al. Expires January 30, 2004 [Page 5] > ^L > Internet-Draft draft-herlein-speex-rtp-profile-01 July 2003 > > > In this case, if the remote part agrees, it should configure its > Spee...

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

...hes to receive (speex 'mode 6') followed by all supported modes (all speex mode). Herlein, et al. Expires December 7, 2007 [Page 13] Internet-Draft Speex June 2007 m=audio 8088 RTP/AVP 97 a=rtmap:97 speex/8000 a=fmtp:97 mode=6;mode=any The offerer indicates the mode he wishes to receive (speex 'mode 3'). This offer indicates mode 3 and mode 5 are supported and that no other modes are supported. The remote party MUST not configure its encoder using another...

...on the offerer has bandwidth limitations, the client may use the "b=" header, as explained in SDP [RFC4566]. The following example illustrates the case where the offerer cannot receive more than 10 kbit/s. m=audio 8088 RTP/AVP 97 b=AS:10 a=rtmap:97 speex/8000 In this case, if the remote part agrees, it should configure its Speex encoder so that it does not use modes that produce more than 10 kbit/s. Note that the "b=" constraint also applies on all payload types that may be proposed in the media line ("m="...