Hello,
with r1352 this is improved:
DTMF detection improved, the timestamp of the DTMF RTP packets is
considered
- if an RTP event with timestamps differing from the last one is
received, the
event is sent out immediately
- RTP DTMF packets with the same timestamp as an already detected
keypress are
ignored.
This allows to raise the value for timeout on sending out RTP DTMF
event, to 5 packets
(100 or 150ms with 20/30ms packet size)
Double detection should not occur with this any more. If you encounter
any issues, please post/pm a trace.
Stefan
o Stefan Sayer [03/26/09 18:39]:
Hello,
o Ovidiu Sas [03/25/09 23:42]:
Also it will have to handle multiple end events, as my source sends it
three times.
that is the reason it waits for some time before it passes the DTMF
as key
press to the session. It may indeed be not possible to tell with 100%
certainity whether the RTP events belong to the same key press; there
is no
ID or the like in the events.
The timestamp for two different events should be different and this
can act as an event ID. This should be an indication that a packet
belongs to a new event (even if the event is identical to the previous
one) and it should reliably detect a new event.
thats true. I have attached a patch that does use this. Its not yet
optimal though - in the case of RTP event detect timeout it can still
not distinguish the two keys.
Stefan
Regards,
Ovidiu Sas
------------------------------------------------------------------------
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
--
Stefan Sayer
VoIP Services
[email protected]
www.iptego.com
IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany
Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev
