[Bug 24902] interface for precomposed dial-strings

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=24902





--- Comment #8 from Andres Salomon <dilinger at collabora.co.uk>  2010-02-09 13:24:37 PST ---
(In reply to comment #7)
> (In reply to comment #6)
> > * How do you send tones "live" via a dial-pad, e.g. for "for sales and support,
> > press 3"? I infer that the answer is SendTones("3", x, x) for suitable x, or
> > possibly SendTones("3", x, x) for very large x on press and CancelTones() on
> > release; this should be documented explicitly.
> 
> Maybe I can propose duration=0 means "automatic" and duration="very long" (or
> -1) means "needs to be manually stopped or will last a very long time". 
> 

I like this.  I would even go so far as to say that, if duration=0 means
"automatic", CMs should actually honor non-automatic values.  That is, if the
client specifies duration=50 and the CM cannot play the tone for 50ms (due to
hardware/network requirements), SendTones should return an error.

Given that, CMs should also be required to specify a default duration/pause.

(Note that another option is to have another argument which takes an enum {
DURATION_AUTOMATIC, DURATION_SPECIFIED, DURATION_FOREVER }.)


> > * If you send "overlapping" tones (call SendTones a second time while tones are
> > still playing), what happens? I suspect the only sensible answer is to say
> > they're queued up, but this should be documented explicitly.
> 
> The DTMF GStreamer elements will queue them up and enforce a minimum duration
> and pause that we've found to make most IVRs happy. The spec should probably
> say something similar

Not Error.NotAvailable or Error.ServiceBusy?


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.