[prev in list] [next in list] [prev in thread] [next in thread]
List: sip-implementors
Subject: RE: [Sip-implementors] FW: SDP confusion
From: Attila Sipos <AttilaS () vegastream ! com>
Date: 2003-02-19 7:25:30
Message-ID: CFAC7B538F46D41185C000508BD9312B017792B1 () brack-exch ! bracknell ! pace ! co ! uk
[Download RAW message or body]
Hi Jade,
You need to say what profile "101" is.
So, you need to include a line like this:
a=rtpmap:101 telephone-event/8000
"telephone-event" tells the remote side
that you can receive RFC2833.
So, your SDP will look like this:
v=0
o=jade 2890844526 2890842807 IN IP4 11.11.2.2
s=POI Seminar
i=A Seminar on how to make Presentations on the Internet
u=http://www.ee.org
c=IN IP4 11.11.2.2/127
m=audio 49170 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
Regards,
Attila
Attila Sipos
Software Engineer
<http://www.vegastream.com>
VegaStream : A World of difference for your Integrated Communications
> -----Original Message-----
> From: Jade Chen Yan [mailto:jade@tencent.com]
> Sent: 19 February 2003 04:21
> To: Sip-Implementors (E-mail)
> Subject: [Sip-implementors] FW: SDP confusion
>
>
> Hi, List,
>
> In rfc 2833 ,DTMF event use the same port as audio.
> the SDP will like this:
>
> v=0
> o=jade 2890844526 2890842807 IN IP4 11.11.2.2
> s=POI Seminar
> i=A Seminar on how to make Presentations on the Internet
> u=http://www.ee.org
> c=IN IP4 11.11.2.2/127
> m=audio 49170 RTP/AVP 0 101 //101 is the payload
> type for DTMF
> enent.
> a=rtpmap:0 PCMU/8000
> a=fmtp:101 0-15 // we only support 0-15 event.
>
> Can the remote side read that the other side supports RFC 2833?
>
> Best Regards,
> Jade
>
>
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@cs.columbia.edu
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic