Re: [Sip] Question on RFC3840/3841

Thanks Paul.
So would it be right if i have a Contact Headers describing Duplex Audio & 
one-way Video Capabilities as follows?

    Contact:sip:alice@atlanta.com;
    Contact:sip:audio;duplex=full;
    Contact:sip:video;duplex=recieve-only;

NOTE: The Predicate(for above) for which i'm attempting is
& ( & (sip.audio) (sip.duplex=full) )
    (  & (sip.video) (sip.duplex=receive-only) )

regards
Mahesh

----- Original Message ----- 
From: "Paul Kyzivat" <pkyzivat@cisco.com>
To: "Mahesh Anjanappa" <mahesha@samsung.com>
Cc: "Christer Holmberg" <christer.holmberg@ericsson.com>; <sip@ietf.org>
Sent: Wednesday, January 09, 2008 7:55 PM
Subject: Re: [Sip] Question on RFC3840/3841

>
>
> Mahesh Anjanappa wrote:
>> hi
>> That is my understanding as well. But if that is the case then it should 
>> apply to Contact header as well
>> when describing Capabilities using Feature parameters in Contact Header.
>> But i'm not sure if it applies the same way. I had posted this question 
>> long ago but didnt get any comments on it.
>
> The rule forbidding multiple instances of a parameter applies to all 
> headers, so it applies to Contact.  E.g. the following is illegal:
>
> Contact:sip:alice@atlanta.com;methods="INVITE";methods="CANCEL"
>
> Paul 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip