On 2006-06-12 at 17:22, Donald Ritchie ([EMAIL PROTECTED]) wrote:
> >I'm not at all sure, but I don't think that equipment is that smart.
> >IF there is a call waiting, the CO should send the CID info,
>
> I wonder if anybody REALLY knows how this works ?
According to this document
(http://www.s
As you and I said
"the receive has no means of signaling or handshaking to the co line"
Don
.
Larry wrote:
Donald Ritchie wrote:
The thing I wonder about, that doc is like 15 years old, and while it
explains incoming CID
it said nothing about CID delivery on a "call waiting" call.
I wo
At 06:14 PM 6/12/2006, Larry wrote:
>Donald Ritchie wrote:
>
> > The thing I wonder about, that doc is like 15 years old, and while it
> > explains incoming CID
> > it said nothing about CID delivery on a "call waiting" call.
> > I wonder if anybody REALLY knows how this works ?
> >
>
>cwcid- the
Donald Ritchie wrote:
> The thing I wonder about, that doc is like 15 years old, and while it
> explains incoming CID
> it said nothing about CID delivery on a "call waiting" call.
> I wonder if anybody REALLY knows how this works ?
>
cwcid- the co outbound audio path is opened, cwtone is sent
The thing I wonder about, that doc is like 15 years old, and while it
explains incoming CID
it said nothing about CID delivery on a "call waiting" call.
I wonder if anybody REALLY knows how this works ?
Don
Larry wrote:
Donald Ritchie wrote:
I'm not at all sure, but I don't think that
Donald Ritchie wrote:
> I'm not at all sure, but I don't think that equipment is that smart.
> IF there is a call waiting, the CO should send the CID info, IF there
> IS CID info
> Asking the CO to wait for an Answer back or an "ack" would slow down
> the process to much
>
> Much like a udp pac
I'm not at all sure, but I don't think that equipment is that smart.
IF there is a call waiting, the CO should send the CID info, IF there IS
CID info
Asking the CO to wait for an Answer back or an "ack" would slow down
the process to much
Much like a udp packet in tcp-ip
That's my opinion,
On 2006-06-12 at 12:07, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> So they are getting the 300 baud, but the 824 isn't picking it up.
Actually, no, there's no data (I believe it's actually 1200 bps) being
sent, presumably because the 824 isn't sending the correct response to
the CID/CW alert
In a message dated 6/12/2006 10:28:50 A.M. Eastern Daylight Time,
[EMAIL PROTECTED] writes:
Steve,
read as CW-CID and it makes more sense.
OH, OKthat makes more sense definitely. Helps to be specific. So they
are getting the 300 baud, but the 824 isn't picking it up.
Steve L.
lp.com
Subject: Re: KX-T: KX-TA824 & Caller ID / Call Waiting
In a message dated 6/12/2006 3:40:12 A.M. Eastern Daylight Time,
[EMAIL PROTECTED] writes:
Your results are exactly what my customers are seeing - more likely to fail
on outgoing calls than incoming, etc.
How in the world do you get
In a message dated 6/12/2006 3:40:12 A.M. Eastern Daylight Time,
[EMAIL PROTECTED] writes:
Your results are exactly what my customers are seeing - more likely to fail
on outgoing calls than incoming, etc.
How in the world do you get Caller ID from an outgoing call? My TD1232 only
get
m: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Jim Gottlieb
Sent: Sunday, June 11, 2006 7:48 PM
To: kxt@kxthelp.com
Subject: KX-T: KX-TA824 & Caller ID / Call Waiting
After almost 20 years of using a KX-T61610 system at home, today I upgraded
to a KX-TA824, along with some new KX-T7731
After almost 20 years of using a KX-T61610 system at home, today I
upgraded to a KX-TA824, along with some new KX-T7731 sets.
My main motivation for upgrading was to be able to get Caller ID / Call
Waiting information at all sets. Yet this is the one feature that is
not working reliably.
On some
13 matches
Mail list logo
