Typically the SUBSCRIBE shall catch 404 when the resource uri for which the
SUBSCRIBE request is meant for is not available or server couldn't find it.
Somesh
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
Thanks for the reply..
*But i am able to subscribe the user when i am subscribing it locally
the same requested URI...
So please suggest some idea regarding that coz we are able to register
the USER with its register request.
And similarly when we are not able to entertain the SUBSCRIBE
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
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
