1 / 5

Third Party Call Control with SDP Preconditions

This draft discusses third party call control protocols without Quality of Service (QoS), with emphasis on SDP preconditions. It also raises the open issue of "confirm" from the server.

Download Presentation

Third Party Call Control with SDP Preconditions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 3rd party call control with SDP preconditions draft-camarillo-3pcc-qos-00.txt Gonzalo Camarillo Gonzalo.Camarillo@ericsson.com

  2. Outline Third party call control without QoS Third party call control with SDP preconditions Open issue: “confirm” from the server

  3. Third party call control without QoS draft-rosenberg-sip-3pcc-00.txt INVITE (no SDP) 200 OK (SDP A) INVITE (SDP A) 200 OK (SDP B) ACK (SDP B) ACK B Controller A

  4. Third party call control with SDP preconditions (1): INVITE with preconditions but no media info. Format: c=IN IP4 0.0.0.0 m=audio 0 RTP/AVP a=qos:mandatory sendrecv confirm (5): PRACK used to send SDP (9) and (11): COMETs from the server (13): COMET to the server A. How can the client influence the confirm in the 183 from the server? (16): COMET to B after A has answered Controller A B

  5. How can a client influence the “confirm” from the server? INVITE (sendrecv confirm) 183 (sendrecv confirm) COMET COMET The server might choose to rely on ResvConf, for instance, instead of including “confirm” in the response.

More Related