Hi,
You are right. The attribute line in the answer which in the service example is the 200 OK for mid call INVITE should be marked recvonly. I guess this must be a typo in the service example.
Padma
>From: Pranab Mehta <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: [Sip-implementors] Questions on Call Hold with a=sendonly/recvonly
>Date: Tue, 5 Nov 2002 11:13:47 -0500 (EST)
>
>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
Get faster connections�-- switch to�MSN Internet Access!
Click Here
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
