Feldman, Michael wrote:
when user B changes the session to a=sendonly
1) user B could stop sending RTP traffic per
draft-ietf-sipping-service-examples-02
The top of page 9:
User A calls User B, User B places call on hold. User B then takes call off hold. User A hangs up call. Hold is unidirectional in nature. However, a UA that places the other party on hold will generally also stop sending media, resulting in no media exchange between the UAs.
Just to be clear, UserA should indicate its intentions to send/recv/send-recv/stop sending media in its SDP. UserA never changes its SDP in this example. I agree that from a practical perspective that "call hold" usually results in no audio from either participant. What's shown in 2.1 is more of a "mute the other end" rather than a "call hold" feature as many folks know it.
2) RTCP information is still sent regardless of whether the call is
sendonly or inactive...
per RFC 3264 top of page 6:
Note that in the case of the Real Time Transport Protocol (RTP) [4],
RTCP
is still sent and received for sendonly, recvonly, and inactive
streams.
Right, but RTP packets should only be transmitted in directions as specified in the SDP.
Regards,
Bert
thanks, mikeWhen after UserB send F10 message. UserB will not receive media packet from RTP, and send RTP packet continuous, is it right? User A should receive RTP packet continuous and stop sending RTP packet, is it correctly?Yes, to both questions. Regards, Bert_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
