Skip to content
Snippets Groups Projects
Select Git revision
  • dev_fxs_no_wb
  • lk_channel_joined_bridge_indication
  • 14600-wenpeng
  • asterisk_rdkb
  • fix_transport_fallback_at_dns_failure
  • fix_fallback
  • 14666_fxs_no_wideband_codec
  • fix_srv_records
  • wenpeng-test-250121
  • wenpeng-registration-test
  • fix_deadlock_in_bridge_peer_functions
  • devel default protected
  • securesip_pjproject_part1
  • PJ_Example_Review
  • fix_re_register_authorization_header
  • fix_internal_calls_auth
  • fix_internal_calls
  • Secure_SIPtelephony_part1
  • SIPtelephony_DECT_syslog
  • syslog_develop_phase1
  • 22.0.0-pre1
  • 21.4.2
  • 20.9.2
  • 18.24.2
  • certified-20.7-cert2
  • certified-18.9-cert11
  • 21.4.1
  • 20.9.1
  • 18.24.1
  • 21.4.0
  • 20.9.0
  • 18.24.0
  • certified-20.7-cert1
  • certified-18.9-cert10
  • 21.4.0-rc1
  • 20.9.0-rc1
  • 18.24.0-rc1
  • 21.3.1
  • 20.8.1
  • 18.23.1
40 results
Compare
user avatar
rtp: Add support for RTP extension negotiation and abs-send-time.
Joshua Colp authored 
When RTP was originally created it had the ability to place a single
extension in an RTP packet. In practice people wanted to potentially
put multiple extensions in one and so RFC 5285 (obsoleted by RFC
8285) came into existence. This allows RTP extensions to be negotiated
with a unique identifier to be used in the RTP packet, allowing
multiple extensions to be present in the packet.

This change extends the RTP engine API to add support for this. A
user of it can enable extensions and the API provides the ability to
retrieve the information (to construct SDP for example) and to provide
negotiated information (from SDP). The end result is that the RTP
engine can then query to see if the extension has been negotiated and
what unique identifier is to be used. It is then up to the RTP engine
implementation to construct the packet appropriately.

The first extension to use this support is abs-send-time which is
defined in the REMB draft[1] and is a second timestamp placed in an
RTP packet which is for when the packet has left the sending system.
It is used to more accurately determine the available bandwidth.

ASTERISK-27831

[1] https://tools.ietf.org/html/draft-alvestrand-rmcat-remb-03

Change-Id: I508deac557867b1e27fc7339be890c8018171588
a507c73a
History
user avatar a507c73a
History
Name Last commit Last update
..
stdtime
.gitignore
Makefile
abstract_jb.c
acl.c
adsi.c
alaw.c
alertpipe.c
aoc.c
app.c
ast_expr2.c
ast_expr2.fl
ast_expr2.h
ast_expr2.y
ast_expr2f.c
asterisk.c
asterisk.dynamics
asterisk.exports.in
astfd.c
astmm.c
astobj2.c
astobj2_container.c
astobj2_container_private.h
astobj2_hash.c
astobj2_private.h
astobj2_rbtree.c
audiohook.c
autochan.c
autoservice.c
backtrace.c
bridge.c
bridge_after.c
bridge_basic.c
bridge_channel.c
bridge_roles.c
bucket.c
buildinfo.c
callerid.c
ccss.c
cdr.c
cel.c
channel.c
channel_internal_api.c
chanvars.c
cli.c
codec.c
codec_builtin.c
config.c
config_options.c
conversions.c
core_local.c
core_unreal.c
crypt.c
cygload.c
data_buffer.c
datastore.c
db.c
devicestate.c
dial.c
dns.c
dns_core.c
dns_naptr.c
dns_query_set.c
dns_recurring.c
dns_srv.c
dns_system_resolver.c
dns_test.c
dns_tlsa.c
dnsmgr.c
dsp.c
ecdisa.h
endpoints.c
enum.c
event.c
features.c
features_config.c
features_config.h
file.c
fixedjitterbuf.c
fixedjitterbuf.h
format.c
format_cache.c
format_cap.c
format_compatibility.c
frame.c
framehook.c
fskmodem.c
fskmodem_float.c
fskmodem_int.c
global_datastores.c
hashtab.c
heap.c
http.c
image.c
indications.c
io.c
iostream.c
jitterbuf.c
json.c
libasteriskpj.c