50 likes | 62 Views
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.
E N D
3rd party call control with SDP preconditions draft-camarillo-3pcc-qos-00.txt Gonzalo Camarillo Gonzalo.Camarillo@ericsson.com
Outline Third party call control without QoS Third party call control with SDP preconditions Open issue: “confirm” from the server
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
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
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.