El Lunes, 11 de Mayo de 2009, Dale Worley escribió: > Since the intention is to free the phone's user from dealing with the > call, any "lines" that show on the phone's user interface can be > released immediately. Of course, the phone software will still have to > handle the signaling of these calls, but since SIP is an Internet > protocol, there is no intrinsic limitation on the number of calls that a > phone can handle at any one time. And in this case, there is no > requirement that the phone handle media for *either* of the call legs > (even if it is implementing music-on-hold), the phone only handles > signaling, which is not computationally demanding. > > > How to explain the human user that a phone line is still busy even if he > > has already free-up himself? > > Since the user-interface representation of the "lines" can be freed > immediately, this does not have to be explained, as the user-interface > appearance matches the user's mental model (even if it doesn't match > reality). > > > This is a really bad design IMHO, and it's obvious why so many vendors > > have decided not to implement it. > > I invite you to design a mechanism that works better (but it needs to > work correctly in the face of forking).
Not neccesary, I prefer your explanation :) -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
