That sounds like the right track. The data is sent via some simple
modulation coding either before the first ring or during the first ring.
I could imagine some scenario where the ATA sends it before the PBX is
listening....or some crap like that.
------ Original Message ------
From: "Steve Jones" <thatoneguyst...@gmail.com>
To: "af@afmug.com" <af@afmug.com>
Sent: 11/7/2017 4:20:13 PM
Subject: Re: [AFMUG] ATA CallerID question
we had to adjust a wait time or something like that in the fortivoice
systems when this happens
On Tue, Nov 7, 2017 at 3:16 PM,
can...@believewireless.net<p...@believewireless.net> wrote:
The outbound CID should be set in the PBX, not the ATA.
On Tue, Nov 7, 2017 at 3:58 PM, Nate Burke <n...@blastcomm.com> wrote:
At a customer, I just hooked up a Cisco SPA122 into an Ancient Lucent
PBX system. The customer says that caller ID is not coming through,
but it used to work with his old AT&T Lines, and it appears to be
hitting the ATA Properly. Is there a setting on the ATA that needs
to be set that older systems may be looking for?
The only settings I see for Caller ID in the ATA are Caller ID
Method, currently set to 'Bellcore(N.Amer,China)' and Caller ID FSK
Standard, set to 'Bell 202' I've never had to mess with those
settings before.
Nate
