Another attribute line for payload type 100 is needed, such as:
a=rtpmap:100 telephone-event
RFC 2833 defines two encoding schemes for tones. One based on naming events
and the other based on describing waveform characteristics. What you have
below in your a= line indicates event names. But you haven't specified the
corresponding encoding scheme.
Regards,
Bert
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Mohsen
> Soroush-nejad
> Sent: Tuesday, May 15, 2001 9:44 PM
> To: [EMAIL PROTECTED]
> Subject: [Sip-implementors] RFC 2833 in SDP?
>
>
> Hi All -
>
> Do you know how to describe RFC 2833 capability in SDP?
> For example, if I'm able to receive voice as G723 (PT=4) and
> can handle RFC 2833 DTMF (events 0-15),
> my SDP have the following:
>
> m=audio 20000 RTP/AVP 4 100
> a=rtpmap:4 G723
> a=fmtp:100 0-15
>
> something's missing?? another "a" line to define RFC 2833?
>
>
> p.s. I confess, this question is more on SDP and RFC 2833
> usage than SIP....
>
>
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
