Re: [Sip-implementors] SIP Reject codes: Why draft-worley-6xx-considered-harmful (441 Decline) is still a draft?

2008-03-05 Thread Iñaki Baz Castillo
El Wednesday 05 March 2008 05:29:25 [EMAIL PROTECTED] escribió: Personally I don't understant why 486 User Busy is used for rejecting a call. One reason is to reject the call without returning to the caller an explicit indication that the call has been rejected by the callee. Before

Re: [Sip-implementors] SIP Reject codes: Why draft-worley-6xx-considered-harmful (441 Decline) is still a draft?

2008-03-04 Thread Paul Kyzivat
The choice of which response to generate to reject a call is a conscious decision on the part of the implementer depending on how he wants the rejection to be perceived by the caller. A 486 is used when the *goal* is for the caller to be informed that the callee is busy. A 480 can be used so

Re: [Sip-implementors] SIP Reject codes: Why draft-worley-6xx-considered-harmful (441 Decline) is still a draft?

2008-03-04 Thread Dale . Worley
From: =?utf-8?q?I=C3=B1aki_Baz_Castillo?= [EMAIL PROTECTED] Hi, SIP response codes for rejecting a call is a pain, each implementator does a different thing. RFC 3261 doesn't help a lot with the ambiguity of 480/486/603 codes. It is true that the various error codes are not clearly