[Speex-dev] Speex RTP profile

[Juan Zapatero]

If I use SDP, or SIP, or H.32x, I would have my total headers length
increased, making it harder to fit payload and headers all together in
the GPRS bandwidth (9.6Kbps). So I would like, if possible, to avoid
using nothing but RTP/UDP/IP.

Juan.

El vie, 20-01-2006 a las 08:03 -0800, Duane Storey escribió:
> You generally negotiate the RTP stream via a protocol like SIP or H.323.
> For SIP, you specify SPEEX in the SDP (session description protocol) and
> assign it an arbitrary payload type within the dynamic range (I think it's
> 96 and above).  Lower numbers are predefined (or reserved), so you can't use
> them. Read RFC 2327 about SDP. 
> 
> Duane
> 
> -----Original Message-----
> From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On
> Behalf Of Juan Zapatero
> Sent: Friday, January 20, 2006 3:26 AM
> To: Speex-dev at xiph.org
> Subject: [Speex-dev] Speex RTP profile
> 
> Hello,
> I am trying to write a simple application to test VoIP capabilities over
> a GPRS link. To do such a thing I've used Speex 1.1.11 to capture voice
> and compress it as much as posible. And now, I am taking care about the
> communication process. Because it is supposed to be a voice application,
> I need at least the use of RTP to ensure proper handling of packets over
> the GPRS network.
> So far, I've been working on RTP client examples, and I've read the
> Speex draft too. But still, I don't know how Payload Type must be
> specified. In the Speex draft it says 'dynamically allocated payload
> type SHOULD be chosen', but I don't understand what this means.
> 
> Thanks a lot for any tip.
> 
> 
> ______________________
> Este mensaje, y en su caso, cualquier fichero anexo al mismo,
>  puede contener informacion clasificada por su emisor como confidencial
>  en el marco de su Sistema de Gestion de Seguridad de la 
> Informacion siendo para uso exclusivo del destinatario, quedando 
> prohibida su divulgacion copia o distribucion a terceros sin la 
> autorizacion expresa del remitente. Si Vd. ha recibido este mensaje 
>  erroneamente, se ruega lo notifique al remitente y proceda a su borrado. 
> Gracias por su colaboracion.
> ______________________
> This message including any attachments may contain confidential 
> information, according to our Information Security Management System,
>  and intended solely for a specific individual to whom they are addressed.
>  Any unauthorised copy, disclosure or distribution of this message
>  is strictly forbidden. If you have received this transmission in error,
>  please notify the sender immediately and delete it.
> ______________________
> 
> 
> 


______________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
 puede contener informacion clasificada por su emisor como confidencial
 en el marco de su Sistema de Gestion de Seguridad de la 
Informacion siendo para uso exclusivo del destinatario, quedando 
prohibida su divulgacion copia o distribucion a terceros sin la 
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje 
 erroneamente, se ruega lo notifique al remitente y proceda a su borrado. 
Gracias por su colaboracion.
______________________
This message including any attachments may contain confidential 
information, according to our Information Security Management System,
 and intended solely for a specific individual to whom they are addressed.
 Any unauthorised copy, disclosure or distribution of this message
 is strictly forbidden. If you have received this transmission in error,
 please notify the sender immediately and delete it.
______________________