If the far-end UA has set its Contact URI to have "+sip.rendering=no", I
think that can be safely taken as "the far-end has put us on hold".
Other than that, if all the media streams are on "sendonly" or
"inactive", you could consider the call to be on hold.
Dale
rayana Jayaprakash; Paul Kyzivat;
Rajani
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] SIP video Hold
Hi Satyanarayana,
Thanks.
Any thought on the first question?
>From the receiving end, should the UAS assume that the call is on hold
when it receives
, 2009 11:40:49 AM
Subject: Re: [Sip-implementors] SIP video Hold
Hi Satyanarayana,
Thanks.
Any thought on the first question?
>From the receiving end, should the UAS assume that the call is on hold
when it receives only one of the media streams on hold?
Regards,
ana Jayaprakash ;
Paul Kyzivat ; Rajani
Cc: sip-implementors@lists.cs.columbia.edu
Sent: Tuesday, July 21, 2009 10:55:46 AM
Subject: Re: [Sip-implementors] SIP video Hold
No, each stream is to be treated independently. i.e. the other streams
continue to have sendrecv in answer.
-Original Mess
: Tuesday, July 21, 2009 5:52 PM
To: Paul Kyzivat; Rajani
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] SIP video Hold
Hi Paul,
Thanks for the response. My question is understood right.
>From the receiving end, should the UAS assume that the call is on hold
when it recei
7 PM
To: Rajani
Cc: Lakshminarayana Jayaprakash; sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] SIP video Hold
Rajani wrote:
> In SDP body for each media line we have its media attribute values set
below
> the media line. Each of them have default values if its not mentioned
, should call be considered as
hold?
Regards,
J.P.
-Original Message-
From: Rajani [mailto:choudhury.raj...@gmail.com]
Sent: Monday, July 20, 2009 2:13 PM
To: Lakshminarayana Jayaprakash; sip-implementors@lists.cs.columbia.edu
Subject: RE: [Sip-implementors] SIP video Hold
In SDP body for
edu] On Behalf Of
> Lakshminarayana Jayaprakash
> Sent: Friday, July 17, 2009 3:23 AM
> To: sip-implementors@lists.cs.columbia.edu
> Subject: [Sip-implementors] SIP video Hold
>
> Hi,
>
> Is there a convention how SIP video terminal should do call hold?
> Case-1: [Hol
Rajani
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
[mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of
Lakshminarayana Jayaprakash
Sent: Friday, July 17, 2009 3:23 AM
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] SIP video Ho
Hi,
Is there a convention how SIP video terminal should do call hold?
Case-1: [Hold for both audio and video
streams]
c=IN IP4 a.b.c.d
a=sendonly
m=audio
...
m=video
c=IN IP4 p.q.r.t
a=sen
On Thu, 2009-07-16 at 17:53 -0400, Lakshminarayana Jayaprakash wrote:
> Is there a convention how SIP video terminal should do call hold?
Remember that there is no specified concept of "hold".
Presumably, you put a multi-media call on hold by setting all the
streams to "sendonly".
Dale
Hi,
Is there a convention how SIP video terminal should do call hold?
Case-1: [Hold for both audio and video streams]
c=IN IP4 a.b.c.d
a=sendonly
m=audio
...
m=video
c=IN IP4 p.q.r.t
a=sendonly
Case-2: [Hold for audio stream only]
c=IN IP4 a.b.c.d
a=sendonly
m=audio
...
m=video
c=IN IP4 p.q.r
12 matches
Mail list logo
