And also as per RFC 2327, only v, o, s fields are mandatory in SDP
Somesh
friend friend wrote:
> Hi,
> Thanks for your response.
>
> but RFC 2327 Grammar says like
>
>media-field ="m=" media space port ["/" integer]
> space proto 1*(space fmt) CRLF
>
>
>
These are interesting cases. I think they go beyond what is specified,
and hence are subject to creative implementation, which in this case is
probably a bad thing.
I agree with the opinion that this should be treated much like an
INVITE. In particular,
- the request should be routed to a desti
Thanks Paul. This is really good explanation.
On Tue, Apr 21, 2009 at 5:19 PM, Paul Kyzivat wrote:
> I disagree with the notion that you should include C-T:application/sdp and
> C-L:0 to indicate no offer. In fact, I think it is probably invalid to do
> so.
>
> There are at least a couple of issu
I disagree with the notion that you should include C-T:application/sdp
and C-L:0 to indicate no offer. In fact, I think it is probably invalid
to do so.
There are at least a couple of issues with that:
- If you specify a C-T, then the body needs to conform to the
specification for that type. I
Hi,
According RFC 4566.
media-descriptions = *( media-field information-field *connection-field
bandwidth-fields key-field attribute-fields )
And if remember right in RFC text too: There may be zero media lines.
With 0 lines just session created and new offer can add stream to it.
friend fri
Hi,
Thanks for your response.
but RFC 2327 Grammar says like
media-field ="m=" media space port ["/" integer]
space proto 1*(space fmt) CRLF
media = 1*(alpha-numeric)
;typically "audio", "video", "application"
Hi,
Hope this thread has more info about this topic
https://lists.cs.columbia.edu/pipermail/sip-implementors/2008-October/020798.html
Karthik
On Tue, Apr 21, 2009 at 7:31 PM, Frank Shearar wrote:
> friend friend wrote:
> > Dear Friends,
> > In SDP, media (m line) is mandatory? if so, if
Hi Praveen,
As per RFC 3261 section 8.1.1.7 Via and 9.1 its understood that the
matching happens if branch parameter in the request is equal to
the one in the top Via header field of the request that created the
transaction, hence branch parameter in the INVITE and CANCEL should be same.
> > Is it must to send 'timer' tag extension in Supported: header
> > if Session-Expire: 60;refresher=uac/uas header is present in
> > a request?
>
> Adding supported timer is required if including refresher=uac.
>
> Adding supported timer is not required if included no refresher or
> included re
friend friend wrote:
> Dear Friends,
> In SDP, media (m line) is mandatory? if so, if the UAC doesnt support
> video, audio, can the UAC send SDP like m: 0(zero)?
>
> Please clarify.
>
The m header is not mandatory. RFC 4566 section 5 says
An SDP session description consists of a
Dear Friends,
In SDP, media (m line) is mandatory? if so, if the UAC doesnt support
video, audio, can the UAC send SDP like m: 0(zero)?
Please clarify.
Thanks & Regards,
Vijay
Now surf faster and smarter ! Check out the new Firefox 3 - Yahoo!
Edition http://downloads.yahoo.com
> Is it must to send 'timer' tag extension in Supported: header
> if Session-Expire: 60;refresher=uac/uas header is present in
> a request?
Adding supported timer is required if including refresher=uac.
Adding supported timer is not required if included no refresher or included
refresher=uas.
Dear,
I have a question regarding how to deliver ringback rtp to a SIP station if it
is located under a broadband router, assuming the broadband router acts as a
dummy line sharer. As you may know, rtp port number recorded in the dummy
router can be different the rtp port number stated in SDP b
Hi Praveen, As per RFC 3261 section 8.1.1.7 Via and 9.1 its understood that
the matching happens if branch parameter in the request is equal to the one in
the top Via header field of the request that created the transaction, hence
branch parameter in the INVITE and CANCEL should be same. The
2009/4/21 Krishna Rao Gurram :
> Hi All,
Hi Krishna. When sending a mail to a maillist, please use a
descriptive subject. "Urgent!!" is not a valid one.
Regards.
--
Iñaki Baz Castillo
___
Sip-implementors mailing list
Sip-implementors@list
>>Is it must to send 'timer' tag extension in
>>Supported: header if Session-Expire:
>>60;refresher=uac/uas header is present in a request?
it is a must to send 'timer' tag in a request if you want it to work
>>What should be the behaviour if UAS receives a message
>>including the header "Sess
Yes, if UAC supports session timers, it must set Supported header as
"timer", else, the UAS may not perform session-timer related
processing even though Session-Expired header is present.
On Tue, Apr 21, 2009 at 12:57 AM, Krishna Rao Gurram
wrote:
> Hi All,
> I have a query about Su
Krishna Rao Gurram wrote:
> Hi All,
>I have a query about Supported header. Is it must to send
> 'timer' tag extension in Supported: header if Session-Expire:
> 60;refresher=uac/uas header is present in a request?
>
> What should be the behaviour if UAS receives a message includi
Hi All,
I have a query about Supported header. Is it must to send
'timer' tag extension in Supported: header if Session-Expire:
60;refresher=uac/uas header is present in a request?
What should be the behaviour if UAS receives a message including the
header "Session-Expire: 600;ref
19 matches
Mail list logo
