summaryrefslogtreecommitdiff
path: root/include/asterisk
diff options
context:
space:
mode:
authorAutomerge script <automerge@asterisk.org>2013-01-13 22:20:48 +0000
committerAutomerge script <automerge@asterisk.org>2013-01-13 22:20:48 +0000
commit9e3bf9ba54bcd6edec584ea4eb3ae3fefeb370c5 (patch)
tree594dade3195aed5c3231f20da7996e2a6318e62e /include/asterisk
parentf7f7850f7a3a85df4174b5b736eea2235fc4e6eb (diff)
Merged revisions 378985 via svnmerge from
file:///srv/subversion/repos/asterisk/trunk ................ r378985 | mjordan | 2013-01-13 16:07:00 -0600 (Sun, 13 Jan 2013) | 20 lines Reset RTP timestamp; sequence number on SSRC change In r370252 for ASTERISK-18404, Asterisk's handling of RTP was modified to better account for out of order RTP packets. This was accomplished by using the RTP timestamp and sequence number to check for out of order packets. However, when a SSRC change occurs, the timestamp and sequence number will no longer have any relation to the previously received packets. The variables tracking the timestamp and sequence number therefore have to be reset. (closes issue ASTERISK-20906) Reported by: Eelco Brolman patches: dtmf_on_hold.patch uploaded by Eelco Brolman (license #6442) ........ Merged revisions 378967 from http://svn.asterisk.org/svn/asterisk/branches/1.8 ........ Merged revisions 378984 from http://svn.asterisk.org/svn/asterisk/branches/11 ................ git-svn-id: https://origsvn.digium.com/svn/asterisk/team/mmichelson/threadpool@378993 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'include/asterisk')
0 files changed, 0 insertions, 0 deletions