This special treatment for "call waiting" has always baffled me.
It seems to be rooted in the telco partitioning of services rather than
on any fundamental difference.
Specifically, from a caller perspective, how is a call handled via "call
waiting" at the callee any different from the call ringing on a phone
with two lines where the other line is in use? Why should the caller get
a special signal in one case and not in the other case?
AFAICT, from the caller perspective this is just a "this callee may take
an unusually long time to answer the call" indicator, and callees ought
to be able to make their own decision about when to specify it.
Thanks,
Paul
Attila Sipos wrote:
>>> 182 doesn't mean "call-waiting", it can mean "call-waiting", "queued"...
>
> It's the same thing isn't it?
>
> If you've got a "call-waiting", then your call is queued to be answered.
> And you're queuing, you're a call that is waiting to be answered.
>
> For me, call-waiting is a type of queue (a queue of one).
>
>
>
>
>
>
> -----Original Message-----
> From: sip-implementors-boun...@lists.cs.columbia.edu
> [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Iñaki
> Baz Castillo
> Sent: 10 June 2009 21:30
> To: sip-implementors@lists.cs.columbia.edu
> Subject: Re: [Sip-implementors] Indicating "Call Waiting" in a 1XX response
>
> El Miércoles, 10 de Junio de 2009, Dale Worley escribió:
>
>>> Do you mean that the UAC could display the reason phrase in *English*?
>>> IMHO a standarized code or "string" should be needed for this
>>> instead of a custom string in English.
>> Strictly speaking, the UAC would display the reason phrase in whatever
>> language the reason phrase is written in. And since SIP uses Unicode
>> consistently... Try
>> http://www.evertype.com/standards/csur/tengwar.html
>> or http://en.wikipedia.org/wiki/List_of_Unicode_characters#Dingbats
>
> So, if something is written with Unicode encoding... it becomes automatically
> readable by anyone in the world? Great, I'll talk my grandmother about it. XD
>
> Ok, imagine that 180 and 183 don't exist. Instead an unique 101 code exists
> and the description is the reason phrase. But any device could write that
> description in whatever language (as you suggested above for 182 code) so:
>
> SIP/101 Ringing <-- English
> SIP/101 Sonando <-- Spanish
> SIP/101 Session Progress <-- English
> SIP/101 Early Session <-- English too
> SIP/101 En progreso <-- Spanish
>
> I'm sure that you don't agree with this "feature", so why do you suggest
> exactly the same for 182? Note that 182 doesn't mean "call-waiting", it can
> mean "call-waiting", "queued"...
>
> Another possibility would take place if we all agree on the real meaning of
> 182: could it mean that the called has received the call but he is already on
> other call? In that case 182 would just mean "call-waiting in remote side",
> so our intelligent UAC doesn't require to "translate" the reason phrase and
> display it to the user.
>
>
> Thanks.
>
>
> --
> Iñaki Baz Castillo <i...@aliax.net>
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
