If I would ought to build the UAS, I would make it respond with 606 (Not
Acceptable), and include Warning header with text description which
parameter is missing. I would include the first missing parameter in the
warning text. Further, when the UAC sends the request with some another
parameter missing, that one would be returned in the warning with the
response. And repeat, repeat.. until UAC gets all the parameters right.

Warning header is described in rfc3261 Section 20.43.

Regards

On Wed, Apr 20, 2011 at 11:01 AM, Ravi Inder Singh <[email protected]>wrote:

> Hi
>    Parameters such as :-  'v', 's','o', 't' & 'm' are mandatory parameters
> in SDP RFC 4566 section 5.
>
> So it respond with 400 BAD request.
> Please correct me if i am wrong.
>
> Thanks
> Ravi Inder Singh
>
> On Wed, Apr 20, 2011 at 3:02 PM, <[email protected]> wrote:
>
> > Hi all
> > I’m working on technical SIP requirements for end-points devices and I
> > can’t find an answer for one question.
> > How UAS should behave receiving INVITE that contains SDP without one of
> > following items: v, o, s ,t.
> > For example having received IVITE without origin:
> > v=0
> > s=TT
> > c=IN IP4 10.15.21.1
> > t=0 0
> >
> > Should it respond with 200OK with origin?
> > v=0
> > o=CiscoSystemsCCM-SIP 2000 1 IN IP4 10.15.21.1
> > s=SIP Call
> > c=IN IP4 10.15.21.1
> > t=0 0
> >
> > or should it respond with 488Not acceptable Here? Are there any
> > requirements for that?
> >
> > Thanks in advance,
> > Bartek
> >
> >
> >
> > _______________________________________________
> > Sip-implementors mailing list
> > [email protected]
> > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
>
>
>
> --
> Thanks & Regards,
> Ravi Inder Singh
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to