Actually 487 does not seem to be a correct response to INFO ...
When the originator of the INFO wishes to cancel the INFO sent, it sends a
CANCEL, and 487 can only be sent in response to this CANCEL request.
Per RFC 2976, sec. 2.2:
A 200 OK response MUST be sent by a UAS for an INFO request with
no message body if the INFO request was successfully received for
an existing call. Beyond that, no additional operations are
required.
and
If a server receives an INFO request with a body it understands,
but it has no knowledge of INFO associated processing rules for
the body, the body MAY be rendered and displayed to the user. The
INFO is responded to with a 200 OK.
If the INFO request contains a body that the server does not
understand then, in the absence of INFO associated processing
rules for the body, the server MUST respond with a 415 Unsupported
Media Type message.
>From the above, it seems to mean that:
1. If the (SIP) request is syntactically incorrect,
it sends a 400
2. If it is syntactically correct, but doesn't understand the (SDP) body,
it sends 415
3. If it is syntactically correct, and it also understands the body,
but does not implement the processing rules for the request,
it sends a 200
Apart from the above, I guess only 481 and 501 are other possible responses.
Hence, if the sender of INFO receives a 200, it has no way of knowing
whether the other end has actually processed the request or has ignored the
same.
Sharad
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 2:34 PM
To: Prasanna; Himanshoo Ks; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
it is neither a clinet nor server error, but UAS sends 487 indicating to UAC
that it is not interested in accepting the request.
Ranjit :-)
-----Original Message-----
From: Prasanna [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 1:57 PM
To: [EMAIL PROTECTED]; Himanshoo Ks; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
As such 487 is sent when a cancellation of a request is triggered by the UAC
itself (conditions like CANCEL, expiration of the request), but I do not
believe that this is a UAC triggered cancellation. I withdraw my suggestion
for a 400, for I am also not convinced if UAC behaves erroneously sending
this request or the server behaves erroneously by not able to understand
this.
Do we have a clarity if this is a client error or a server error?
-Prasanna
-----Original Message-----
From: Ranjit Avasarala [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 4:14 PM
To: Prasanna; Himanshoo Ks; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
487 is ok be'se if UAS does not want to accept the INFO request, it will
cancel it. U cannot send 400 Bad Request be'se its not a bad request.
Ranjit :-)
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Prasanna
Sent: Monday, September 23, 2002 11:28 AM
To: [EMAIL PROTECTED]; Himanshoo Ks; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: [Sip-implementors] RE: [Sip] SIP INFO
HI Ranjit,
I do not believe 487 is a suitable response for such a condition. As such
there is no response that is suitable that is usable in this case, but we
can respond with a 400 response. But do we even have an agreement that this
is a client error!
Rgds,
Prasanna
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 1:41 PM
To: Himanshoo Ks; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [Sip-implementors] RE: [Sip] SIP INFO
Hi Himanshoo
if there is any extra info to be conveyed to UAS, then UAC generates INFO
request and sends it to UAS. but if UAS is not interested in the info, then
UAS can respond with "487 Request Cancelled" response.
HTH
Ranjit :-)
-----Original Message-----
From: Himanshoo Ks [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 23, 2002 10:25 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: [Sip] SIP INFO
Your mail says that:
"while INFO method is used to convey mid session information. The INFO
method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not."
If UAS can't tell what information it is interested in, then what is the use
of INFO method...
Also, then how does UAC decide which information to send.
regards
Himanshoo
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ranjit
Avasarala
Sent: Wednesday, September 18, 2002 10:10 AM
To: Himanshoo Ks; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: [Sip] SIP INFO
Hi Himanshoo
SUBSCRIBE / NOTIFY methods are used to register for specific events like
call fowrward, automatic call back , etc.
while INFO method is used to convey mid session information. The INFO method
only provides optioanl extra information. So UAC may not know whether UAS is
interested in the information or not.
Ranjit :-)
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
Himanshoo Ks
Sent: Monday, September 23, 2002 8:56 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [Sip] SIP INFO
Hi,
This is with reference to the SIP INFO Method defined in RFC2976.
SIP INFO method is used for sending mid call signaling information. The way
information is sent by a UAC to UAS is clear. But I have one basic question:
1. How does the UAC generating this INFO message know that the UAS is
ineterested in knowing that event.
2. Also we have SUBSCRIBE/NOTIFY messages in SIP which can be used to
subscribe for soem information and then report the same. So in what way is
INFO different than these ..
Could somebody please answer these questions ?
regards
Himanshoo
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
