Closed GoogleCodeExporter closed 9 years ago
Original comment by pmerl...@googlemail.com
on 18 Sep 2009 at 7:25
Issue 160 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 16 Oct 2009 at 7:23
Looks like sipdroid is doin SIP INFO to implement DTMF. This method is not
supported by
majority of the VoIP service providers. Need to implement inband DTMF or
RFC2833. Are
there any plans to do down that path.
Original comment by gowth...@gmail.com
on 12 Nov 2009 at 4:04
Issue 261 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 31 Dec 2009 at 9:55
I have created another patch to support outband DTMF (RFC2833).
This also include small bug fix to codec selection mechanism (issue 232).
Pmerle, could I check-in this patch?
Original comment by tm.in...@gmail.com
on 21 Jan 2010 at 6:52
Attachments:
The code needs a few changes before checking in. It should test if rfc2833 is
supported
(as it already does) and when true, don't send SIP INFO packets for DTMF any
more.
The RFC2833 packets itself look differently than those sent by asterisk. Are
you sure
it is correct to send out 9 packets, not a total of 6? Also stop/start
recording and
sleeping should not be necessary for sending these packets.
Original comment by pmerl...@googlemail.com
on 25 Jan 2010 at 1:48
[deleted comment]
version 1.3.6
HTC G1 syanogenmod 4.2.13
my sip provider use RFC2833 only, and when i try to route in IVR, it just ignore
the dialing...
Original comment by Spon4ik
on 27 Jan 2010 at 12:19
(Reply to comment 6)
I have committed to r436 and r437.
With r437, SIP INFO will not be sent when rfc2833 can be used.
The packets are very similar to packets that X-Lite sends.
Number of packets to be sent depends on a duration of a DTMF event.
The duration is now 120ms (6 packets and 3 end packets), but can be changed to a
shorter period.
Stop/start recording may be unnecessary if record.read() ignores mic input
during
DTMF packets being sent.
Original comment by tm.in...@gmail.com
on 31 Jan 2010 at 10:00
Original comment by pmerl...@googlemail.com
on 3 Feb 2010 at 5:53
Original issue reported on code.google.com by
trushs...@gmail.com
on 18 Sep 2009 at 2:00