About: Potential problems with codecs negotiation using SDP protocol     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : http://linked.opendata.cz/ontology/domain/vavai/Vysledek, within Data Space : linked.opendata.cz associated with source document(s)

AttributesValues
rdf:type
rdfs:seeAlso
Description
  • Modern voice communication networks are usually built as converged networks enabling voice and data transfer upon using an Internet Protocol (IP). Voice services further require a signalling protocol for their work. Nowadays, the Session Initiation Protocol (SIP) is the most popular signalling protocol used in these types of networks. Compared to traditional telephone networks, voice communication over the IP protocol enables a choice of a codec. The codec that will be used to communicate is negotiated by terminals or gateways using the Session Description Protocol (SDP). It is transmitted in the body of the SIP protocol. If respected the rule that each communicating device must support the G.711 codec, it should not lead to a situation where the communicating parties cannot agree on the codec. In practice, the situation is quite different. In many cases, it is not possible to establish voice communications because of unsuccessful negotiation of the codec. The following article briefly presents basic features of the G.729 codec, the SDP according to RFC 4566 and presents one example of unsuccessful codec negotiation obtained in experiments with VoIP equipment, especially equipment used in the ACR.
  • Modern voice communication networks are usually built as converged networks enabling voice and data transfer upon using an Internet Protocol (IP). Voice services further require a signalling protocol for their work. Nowadays, the Session Initiation Protocol (SIP) is the most popular signalling protocol used in these types of networks. Compared to traditional telephone networks, voice communication over the IP protocol enables a choice of a codec. The codec that will be used to communicate is negotiated by terminals or gateways using the Session Description Protocol (SDP). It is transmitted in the body of the SIP protocol. If respected the rule that each communicating device must support the G.711 codec, it should not lead to a situation where the communicating parties cannot agree on the codec. In practice, the situation is quite different. In many cases, it is not possible to establish voice communications because of unsuccessful negotiation of the codec. The following article briefly presents basic features of the G.729 codec, the SDP according to RFC 4566 and presents one example of unsuccessful codec negotiation obtained in experiments with VoIP equipment, especially equipment used in the ACR. (en)
Title
  • Potential problems with codecs negotiation using SDP protocol
  • Potential problems with codecs negotiation using SDP protocol (en)
skos:prefLabel
  • Potential problems with codecs negotiation using SDP protocol
  • Potential problems with codecs negotiation using SDP protocol (en)
skos:notation
  • RIV/60162694:G43__/13:00492667!RIV14-MO0-G43_____
http://linked.open...avai/riv/aktivita
http://linked.open...avai/riv/aktivity
  • I
http://linked.open...vai/riv/dodaniDat
http://linked.open...aciTvurceVysledku
http://linked.open.../riv/druhVysledku
http://linked.open...iv/duvernostUdaju
http://linked.open...titaPredkladatele
http://linked.open...dnocenehoVysledku
  • 97842
http://linked.open...ai/riv/idVysledku
  • RIV/60162694:G43__/13:00492667
http://linked.open...riv/jazykVysledku
http://linked.open.../riv/klicovaSlova
  • Codec negotiation; RFC 3555; SDP; G.729 (en)
http://linked.open.../riv/klicoveSlovo
http://linked.open...ontrolniKodProRIV
  • [8C1FE765BAB5]
http://linked.open...v/mistoKonaniAkce
  • Brno
http://linked.open...i/riv/mistoVydani
  • Brno
http://linked.open...i/riv/nazevZdroje
  • International Conference on Military Technologies 2013, ICMT'13
http://linked.open...in/vavai/riv/obor
http://linked.open...ichTvurcuVysledku
http://linked.open...cetTvurcuVysledku
http://linked.open...UplatneniVysledku
http://linked.open...iv/tvurceVysledku
  • Mazálek, Antonín
  • Vránová, Zuzana
http://linked.open...vavai/riv/typAkce
http://linked.open.../riv/zahajeniAkce
number of pages
http://purl.org/ne...btex#hasPublisher
  • University of Defence, Brno, 2013
https://schema.org/isbn
  • 978-80-7231-917-6
http://localhost/t...ganizacniJednotka
  • G43
Faceted Search & Find service v1.16.118 as of Jun 21 2024


Alternative Linked Data Documents: ODE     Content Formats:   [cxml] [csv]     RDF   [text] [turtle] [ld+json] [rdf+json] [rdf+xml]     ODATA   [atom+xml] [odata+json]     Microdata   [microdata+json] [html]    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3240 as of Jun 21 2024, on Linux (x86_64-pc-linux-gnu), Single-Server Edition (126 GB total memory, 58 GB memory in use)
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2024 OpenLink Software