Actually the bis draft (-9, dated feb 27) mentions in line 504 that the UA
sends a response such as 406 when a re-invite happens.
And in line 2245: it says an initial INVITE should be rejected with a 488.
Here is my take: It should send a 488 when it wants to specifically tell
the caller that only *it* cannot accept this call.
In the case of an initial invite, it may have been forked to many UAs some
of which may accept it. So 488 is more applicable here.
In the case of a re-INVITE or UPDATE to an existing session, it may choose
to send 406 since it knows that it is the called party and no one
else can accept it. However, I dont see a harm in sending 488 in both
cases though.
Above is my assumption of course judging by the scope of 'Not Accepted
here' vs 'Not Accepted'
Although I doubt if any existing clients really act differently on getting
a 406 vs. 488. In reality I strongly suspect both have the same
end result.
regds
Arjun
--
Arjun Roychowdhury @ Hughes Software Systems
11717 Exploration Lane, Germantown MD 20876
(O): 301-212-7860 (M): 240-475-2139
"Feldman, Michael" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
05/21/02 11:45 AM
To: [EMAIL PROTECTED]
cc:
Subject: [Sip-implementors] 406 vs 488 responses
When should a 406 (Not Acceptable) be sent verse a 488 (Not Acceptable
Here)?
the UPDATE draft mentions
an update could be reject a codec change with a 488,
the bis9 draft mentions
a Re-INVITE codec change is rejected with a 406 or a 488?
thanks,
mike feldman
[EMAIL PROTECTED]
bis9 page 18, section 4:
This is accomplished by sending a re-INVITE containing a new media
description. This
re-INVITE references the existing dialog so that the other party knows
that
it is to
modify an existing session instead of establishing a new session. The
other
party
sends a 200 (OK) to accept the change. The requestor responds to the 200
(OK) with an
ACK. If the other party does not accept the change, he sends an error
response such as
406 (Not Acceptable), which also receives an ACK.
but bis 9 in section 14.2 page 90:
If the new session description is not acceptable, the UAS can reject it by
returning a 488 (Not Acceptable Here) response to the re-invite.
draft-ietf-sip-update-02, section 5.2:
If the new session description is not acceptable, the UAS can reject it by
returning a
488 (Not Acceptable Here) response for the UPDATE.
_______________________________________________
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
