]> git.ipfire.org Git - thirdparty/asterisk.git/commit
Merged revisions 289798 via svnmerge from
authorJeff Peeler <jpeeler@digium.com>
Sat, 2 Oct 2010 02:43:45 +0000 (02:43 +0000)
committerJeff Peeler <jpeeler@digium.com>
Sat, 2 Oct 2010 02:43:45 +0000 (02:43 +0000)
commitddebf12b88fd79704d51ae7b411178e5e7d04738
treed11e0d1f7cdeb2456a50e9f47d0b592d113ccbd4
parent1d766ede6313f95dedb3dc881fa1c9ab9d5dd0c2
Merged revisions 289798 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.6.2

................
  r289798 | jpeeler | 2010-10-01 18:01:31 -0500 (Fri, 01 Oct 2010) | 22 lines

  Merged revisions 289797 via svnmerge from
  https://origsvn.digium.com/svn/asterisk/branches/1.4

  ........
    r289797 | jpeeler | 2010-10-01 17:58:38 -0500 (Fri, 01 Oct 2010) | 15 lines

    Change RFC2833 DTMF event duration on end to report actual elapsed time.

    The scenario here is with a non P2P early media session. The reported time
    length of DTMF presses are coming up short when sending to the remote side.
    Currently the event duration is a running total that is incremented when sending
    continuation packets. These continuation packets are only triggered upon
    incoming media from the remote side, which means that the running total probably
    is not going to end up matching the actual length of time Asterisk received
    DTMF. This patch changes the end event duration to be lengthened if it is
    detected that the end event is going to come up short.

    Review: https://reviewboard.asterisk.org/r/957/

    ABE-2476
  ........
................

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.8@289840 65c4cc65-6c06-0410-ace0-fbb531ad65f3
channels/chan_sip.c
include/asterisk/rtp_engine.h
main/rtp_engine.c
res/res_rtp_asterisk.c