Hi Folks,

In section 6.1 of rfc3264 it states (for unicast streams):
"If a stream is offered as sendonly, the corresponding stream MUST be marked
as recvonly or inactive in the answer.  If a media stream is listed as
recvonly in the offer, the answer MUST be marked as sendonly or inactive in
the answer."

Does this imply that if a UA receives a mid-call INIVITE to put the call on
hold with a=sendonly as one of the attribute lines, it should reply with
a=recvonly in the 200ok to that mid-call INVITE ?

The reason I ask is because in the call hold example in
draft-ietf-sipping-service-examples-02.txt, the 200ok to the call hold
INVITE does not have a a=recvonly attribute. Isn't this against what is
stated in RFC3264 or am I missing something ?

TIA,
Pranab

_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to