Hopefully such behavior, if present at all, will be configurable. I feel
perfectly capable of hanging up the phone when I become tired of waiting
for the call to be answered, and in fact I will generally have to take
much the same action even if my phone terminates the call on its own, so
there is really no benefit to it doing so. So, *I* would prefer not to
have my phones unilaterally terminate a call attempt. YMMV.
Paul
Brett Tate wrote:
>> From: "Brett Tate" <[EMAIL PROTECTED]>
>>
>> Be aware that some customer service and reservation
>> systems send 18x
>> responses while queued waiting to be answered by person.
>> It might take
>> longer than 180 seconds for the call to be answered by
>> person. Thus
>> your users might complain about poor interoperability
>> (dropped calls)
>> concerning calls to such numbers.
>>
>> Or we might interpret it this way: I don't want to do
>> business with companies that take over 180 seconds (three
>> minutes!) to answer their phones, and provisioning my SIP
>> phone this way enforces that rule.
>
> Sounds good to me; however the extra minute is sometimes worth reaching
> the called party. :)
>
>>From a caller perspective (on some phones), it might not always be clear
> that the call has not yet been answered. If the timer expires while
> caller is hearing recordings indicating that their call will be answered
> in approximately 5 minutes, the user might not immediately recognize
> that they potentially should locally adjust such a timeout value prior
> to calling the same number again.
>
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
