[EMAIL PROTECTED] wrote:

> In addition, the I-D could describe why 181 is not sufficient solution.
> 
> [DA] What use case do you have in mind that can be solved by using 181?
> 
> [Jari] The CW use case: how to indicate to the caller that the callee is
> alerting but busy with another call. I think this was the original
> problem to be solved? 

181 means "Call is being forwarded". What does that have to do with call 
waiting?

IMO the entire CW user experience carries much legacy baggage.

Its not at all clear to me that the caller needs to know anything about 
it, or that the callee necessarily wants the caller to know he is on 
another call. If so, there are many potential ways to make that known to 
the caller. The legacy way is with a special tone. More modern devices 
could find other ways to do it - perhaps graphical. But obviously when 
interoperating with a PSTN caller one needs to do something consistent 
with what the caller expects and can handle.

Sending *some* signal that indicates the call state seems desirable 
because it allows the calling end to render that as it wishes. 
Alert-Info with URNs is one way of encoding the semantic intent to 
inform the caller of the state without tying down how it is rendered. 
Then a GW can render it in the legacy way, and a more modern sip UAC can 
render it as it wishes.

Certainly there are other possible ways to signal this information. But 
I don't think 181 is one of those ways.

        Thanks,
        Paul
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss

Reply via email to