call waiting response

[Rich Greenberg]

Suppose I (with call waiting) am on the phone speaking to person A.

Person B calls me. Person B gets ringback and I get CW beeps.

If I ignore the CW beeps, person B gets RNA (Ring No Answer) until they
give up.

Is this the proper result or should Person B's ringback change to busy
after some interval? Or does this depend on the switch type?

Telcodata shows the switch as CLLI: NFMYFLXBRS0 but does not show the
type of switch. The LEC is Embarq.

[danny burstein]

Post by Rich Greenberg
Suppose I (with call waiting) am on the phone speaking to person A.
Person B calls me. Person B gets ringback and I get CW beeps.
If I ignore the CW beeps, person B gets RNA (Ring No Answer) until they
give up.
Is this the proper result or should Person B's ringback change to busy
after some interval? Or does this depend on the switch type?

Everytime I've made such a call I get RNA. In the old days
that went on just this side of forever; nowadays I bump into
a general timeout after a couple of minutes.

Post by Rich Greenberg
Telcodata shows the switch as CLLI: NFMYFLXBRS0 but does not show the
type of switch. The LEC is Embarq.

[Robert Bonomi]

Post by Rich Greenberg
Suppose I (with call waiting) am on the phone speaking to person A.
Person B calls me. Person B gets ringback and I get CW beeps.
If I ignore the CW beeps, person B gets RNA (Ring No Answer) until they
give up.
Is this the proper result or should Person B's ringback change to busy
after some interval? Or does this depend on the switch type?

If person B calls you, and you are _not_ on the phone, Person B gets
ringback, and your phone rings.

If you ignore the ringing, person B continues to get ring until they give
up.

Is _this_ the proper result,or should Person B's ringback change to busy
after some interval? Or does this depend on the switch type?


Answer my questions, and you'll have the answers to yours. <grin>


Note: AFAIK, the -called- switch never 'arbitrarily' changes the call status.
The *originating* switch _may_ decide an unanswered all is 'unproductive'
and 'forcibly terminate' the call. I suspect it's a simple matter of
feature programming.

[John L]

Post by Robert Bonomi
Note: AFAIK, the -called- switch never 'arbitrarily' changes the call status.

The switch that handles my AT&T mobile phone does. I don't have voice mail
so it rings for a while and eventually goes to an AT&T recording saying
that the customer isn't there.

[Robert Bonomi]

Post by John L

Post by Robert Bonomi
Note: AFAIK, the -called- switch never 'arbitrarily' changes the call status.

The switch that handles my AT&T mobile phone does. I don't have voice mail
so it rings for a while and eventually goes to an AT&T recording saying
that the customer isn't there.

Which is not changing the call status, but just re-directing the call -- to
wit, "Call Forward No Answer" -- to a generic intercept (without SIT tones).
so that the caller doesn't get billed.