Hi: comment in line On 11/23/06, Tang Xi <[EMAIL PROTECTED]> wrote: > > Hi sip group: > > I have the following question: > > as RFC 3312 13.1 describing: > 1) UAC send: > m=audio 20000 RTP/AVP 0 > c=IN IP4 192.0.2.1 > a=curr:qos e2e none > a=des:qos mandatory e2e sendrecv > 2)UAS send: > m=audio 30000 RTP/AVP 0 > c=IN IP4 192.0.2.4 > a=curr:qos e2e none > a=des:qos mandatory e2e sendrecv > a=conf:qos e2e recv > 3)UAC send back: > m=audio 20000 RTP/AVP 0 > c=IN IP4 192.0.2.1 > a=curr:qos e2e send > a=des:qos mandatory e2e sendrecv > 4)UAS send back: > m=audio 30000 RTP/AVP 0 > c=IN IP4 192.0.2.4 > a=curr:qos e2e sendrecv > a=des:qos mandatory e2e sendrecv > > what is the meaning of UAS's "a=conf:qos e2e recv"? > Does it mean UAS wants the UAC to send a updated SDP once the UAC's "send > direction" is ready?
yes. and why UAC don't send "a=curr:qos e2e recv"? Confirmation attributes are not negotiated, it may be needed by both sides or not, deside by you. _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
