Paul Witty wrote: > When negotiating DTMF using RFC 4733, there are some parameters to > specify, for which there is currently no support in XEP-0181. As with > other RTP formats, a dynamic payload type and clock rate must be > specified. A list of supported events can also be supplied, but this > seems unnecessary, and assuming the default (0-9, #, *, A, B, C and D) > should be fine. > > I propose that the negotiation of the DTMF method should be either, for > XMPP-style: > <iq from='[EMAIL PROTECTED]/balcony' > id='dtmf2' > to='ivr.shakespeare.lit' > type='set'> > <jingle xmlns='urn:xmpp:tmp:jingle' > action='session-info' > initiator='[EMAIL PROTECTED]/balcony' > sid='a73sjjvkla37jfea'> > <dtmf-method xmlns='urn:xmpp:tmp:jingle:dtmf' method='xmpp'/> > </jingle> > </iq> > > or, for RTP: > <iq from='[EMAIL PROTECTED]/balcony' > id='dtmf2' > to='ivr.shakespeare.lit' > type='set'> > <jingle xmlns='urn:xmpp:tmp:jingle' > action='session-info' > initiator='[EMAIL PROTECTED]/balcony' > sid='a73sjjvkla37jfea'> > <dtmf-method xmlns='urn:xmpp:tmp:jingle:dtmf' method='rtp'> > <payload-type id='100' name='telephone-event' clockrate='8000'/> > </dtmf> > </jingle> > </iq> >
or:
<dtmf-method xmlns='urn:xmpp:tmp:jingle:dtmf' method='rtp'>
<payload-type id='101' name='audio-tone' clockrate='8000'/>
</dtmf>
The negotiation mechanism is not fully described right now so I will
clean that up (e.g., what if you want to switch from RFC 4733 to native
XMPP DTMF?).
Peter
--
Peter Saint-Andre
https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
