2011/8/11 Kevin P. Fleming <[email protected]>: > You are talking about two different things; it's completely possible for > a callee's end system to be registered, but for that person to be 'not > logged in' (and thus unavailable to receive calls). Having a contact URI > registered at the callee's AoR does not mean they are 'logged in', it > just means we know how to contact the callee's system to *find out* if > they are logged in or not.
Hi, from the RFC 3261 perspective and SIP protocol in general, I don't know what "being logged in" means. SIP just talks about devices being registered (so can receive calls) or not (just talking about common scenarios with dynamic phones). I don't think that 21.4.18 talks about "a PBX with a queue in which an agent is, or is not, logged in". Neither I think it means that the human user enables/dissables "something" in the phone device to be reachable or not (as that concept is DND and is already present in same RFC section). Anyhow, I agree that the section 21.4.18 is unclear. When it says "The callee's end system was contacted successfully but the callee is currently unavailable" I expect that "callee's end system" could mean its inbound proxy, and not just the callee's own device (the phone). Indeed RFC 3261 should clarify MUCH MORE the correct response for the case in which an AoR is not registered is its proxy/server/registrar. But anyhow I really expect that 480 is the appropriate response. Regards. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
