[jitsi-dev] DTMF configuration


#1

Hi devs,

Jitsi is able to deal with 3 kinds of DTMF method: RTP (RFC4733), SIP-INFO and INBAND.

I am currently updating the configuration form to choose the DTMF method used for each SIP account (cf. screenshot joined). As you can see, you can choose between the 3 DTMF methods and an "auto" mode.

For the moment, the "auto" mode only deals with the RTP and SIP-INFO methods (cf. algorithm 1 below). I am wondering if it will be interesting (as it is quite a lot of work) to add the INBAND method as a last resort of the "auto" mode (cf. algorithm 2 below).

Auto mode algorithm 1)

···

----------------------
- If account supports RTP telephone-event:
----> use RTP DTMF.
- Else:
----> use SIP-INFO.

Auto mode algorithm 2)
----------------------
- If account supports RTP telephone-event:
----> use RTP DTMF.
- Else:
----> Try SIP-INFO. If [response == 200] stops, else use INBAND DTMF.

Regards,
Chenzo

--
Vincent Lucas, Ph.D. Jitsi developer
chenzo@jitsi.org http://jitsi.org


#2

Hey Chenzo,

I was thinking we should have the option of explicitly choosing either
of them. The Auto mode should only select between RTP and inband dtmf
based on the presence of the telephon-event format in the SDP (or lack
thereof).

Comments anyone?

Emil

···

On 09.02.12 12:01, Vincent Lucas wrote:

Hi devs,

Jitsi is able to deal with 3 kinds of DTMF method: RTP (RFC4733),
SIP-INFO and INBAND.

I am currently updating the configuration form to choose the DTMF method
used for each SIP account (cf. screenshot joined). As you can see, you
can choose between the 3 DTMF methods and an "auto" mode.

For the moment, the "auto" mode only deals with the RTP and SIP-INFO
methods (cf. algorithm 1 below). I am wondering if it will be
interesting (as it is quite a lot of work) to add the INBAND method as a
last resort of the "auto" mode (cf. algorithm 2 below).

Auto mode algorithm 1)
----------------------
- If account supports RTP telephone-event:
----> use RTP DTMF.
- Else:
----> use SIP-INFO.

Auto mode algorithm 2)
----------------------
- If account supports RTP telephone-event:
----> use RTP DTMF.
- Else:
----> Try SIP-INFO. If [response == 200] stops, else use INBAND DTMF.

Regards,
Chenzo

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#3

Hi Emil, devs,

The patch concerning DTMF configuration is ready (cf. joined file).

This patch includes as well:

- A commun interface for sending and stopping the RTP and INBAND DTMFs in AudioMediaStream and AudioMediaStreamImpl.

- The DtmfTransformEngine code reverted to the previous DTMFDispatcher as explained by Lyubomir.

Cheers,
Chenzo

patch_DTMF_configuration.patch (39.5 KB)

···

On 02/09/2012 12:37 PM, Emil Ivov wrote:

Hey Chenzo,

I was thinking we should have the option of explicitly choosing either
of them. The Auto mode should only select between RTP and inband dtmf
based on the presence of the telephon-event format in the SDP (or lack
thereof).

Comments anyone?

Emil

On 09.02.12 12:01, Vincent Lucas wrote:

Hi devs,

Jitsi is able to deal with 3 kinds of DTMF method: RTP (RFC4733),
SIP-INFO and INBAND.

I am currently updating the configuration form to choose the DTMF method
used for each SIP account (cf. screenshot joined). As you can see, you
can choose between the 3 DTMF methods and an "auto" mode.

For the moment, the "auto" mode only deals with the RTP and SIP-INFO
methods (cf. algorithm 1 below). I am wondering if it will be
interesting (as it is quite a lot of work) to add the INBAND method as a
last resort of the "auto" mode (cf. algorithm 2 below).

Auto mode algorithm 1)
----------------------
- If account supports RTP telephone-event:
----> use RTP DTMF.
- Else:
----> use SIP-INFO.

Auto mode algorithm 2)
----------------------
- If account supports RTP telephone-event:
----> use RTP DTMF.
- Else:
----> Try SIP-INFO. If [response == 200] stops, else use INBAND DTMF.

Regards,
Chenzo

--
Vincent Lucas, Ph.D. Jitsi developer
chenzo@jitsi.org http://jitsi.org