Re: [AFMUG] ATA CallerID question

[Chuck McCown]

Both actually.  Keeps the PBX from placing a call at the exact same time the 
central office is sending a call.  (glare).
PBX grounds the ring side of the line to indicate it wants dial tone.
The central office reciprocates by a ground on the tip side of the line.  The 
PBX then goes off hook and everybody lifts their grounds.

In reverse the C.O. grounds before ringing the line.   Just a layer of 
handshake protocol to prevent glare.  


From: Adam Moffett 
Sent: Monday, November 27, 2017 12:22 PM
To: af@afmug.com 
Subject: Re: [AFMUG] ATA CallerID question

I've probably got that wrong, I think the PBX was expecting a pin to get 
grounded and since that didn't happen it would never pick up.  In any case, I'm 
pretty sure it would ring but you couldn't answer it.


-- Original Message --
From: "Adam Moffett" <dmmoff...@gmail.com>
To: af@afmug.com
Sent: 11/27/2017 2:19:02 PM
Subject: Re: [AFMUG] ATA CallerID question

  When I plugged loop start lines into a ground start PBX they couldn't answer 
the phones.  I may not be remembering this right, but I think they did ring.  I 
think the PBX would try to ground the line when you picked up a handset, and 
that resulted in a hangup on the ATA.  

  That's also the incident which introduced me to the Adtran Total Access.  It 
was the first ATA I found which supported ground start, and I've been very 
happy with that product.

  -- Original Message --
  From: "Chuck McCown" <ch...@wbmfg.com>
  To: af@afmug.com
  Sent: 11/27/2017 11:47:26 AM
  Subject: Re: [AFMUG] ATA CallerID question

Any chance of a ground start vs loop start issue?  Some PBXs were ground 
start.  Not sure how that would affect caller ID.  
Is the PBX actually detecting the ringing?

From: Nate Burke 
Sent: Monday, November 27, 2017 9:34 AM
To: af@afmug.com 
Subject: Re: [AFMUG] ATA CallerID question

Just an Update, I put a splitter in the phone line, and caller ID works 
perfect on any 'modern' handset.  But still does not work on the Lucent PBX.  
The customer still swears it worked with his old AT lines, but seems resigned 
to the fact that he won't have caller ID Anymore.  I tried to sell him into a 
new PBX, but he "Has a truckload of spare parts for this PBX"  


On 11/9/2017 3:53 PM, Adam Moffett wrote:

  Oh rightI haven't picked up the phone yet so there's nothing to hear.
  Sorry.  I haven't actually used one of these telephone thingys in a long 
time.


  -- Original Message --
  From: "Lewis Bergman" <lewis.berg...@gmail.com>
  To: af@afmug.com
      Sent: 11/9/2017 4:52:46 PM
  Subject: Re: [AFMUG] ATA CallerID question

Remember, the signal comes between rings. Unless you are listening on a 
butt set in line or watching the info pass through a switch you wouldn't see or 
hear it. The only reason I remembered between first and second is sitting at a 
class 5 switch trying to figure out why caller ID was failing on a feature 
group D trunk group and seeing them come through after one ringy dingy.

On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:

  Is it at an inaudible frequency?  If so, then it wouldn't make it 
through 2600hz bandpass filters would it?  Or maybe it's audible, but so short 
you don't notice it? I'm fuzzy on this.

  I probably shouldn't ask.  I don't need to know that much about POTS 
anymore.


  -- Original Message --
  From: "Lewis Bergman" <lewis.berg...@gmail.com>
  To: af@afmug.com
  Sent: 11/9/2017 4:40:57 PM
  Subject: Re: [AFMUG] ATA CallerID question

More info than anyone probably wants to know. I found this about 
the original question: 
Caller-ID Signaling
According to Telcordia specifications, CND signaling starts as 
early as 300 mS after the first ring burst and ends at least 475 mS before the 
second ring burst

From here: http://www.tech-faq.com/caller-id.html



On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:

  I did not know that tone contained modulated data.  I just 
thought it
  was a noise you wouldn't ignore.

  That's a fun fact to have.


  -- Original Message --
  From: ch...@wbmfg.com
  To: af@afmug.com
      Sent: 11/7/2017 4:39:27 PM
  Subject: Re: [AFMUG] ATA CallerID question

  >Monitor the line for the data burst.  It is the exact same 
modulation
  >method as the emergency alert system you hear squawking on the TV
  >before the beep and thunderstorm warning.
  >
  >I think it comes before the first ring or right after the first 
ring.
  >Some of the original display units rectified 

Re: [AFMUG] ATA CallerID question

[Adam Moffett]

I've probably got that wrong, I think the PBX was expecting a pin to get 
grounded and since that didn't happen it would never pick up.  In any 
case, I'm pretty sure it would ring but you couldn't answer it.



-- Original Message --
From: "Adam Moffett" <dmmoff...@gmail.com>
To: af@afmug.com
Sent: 11/27/2017 2:19:02 PM
Subject: Re: [AFMUG] ATA CallerID question

When I plugged loop start lines into a ground start PBX they couldn't 
answer the phones.  I may not be remembering this right, but I think 
they did ring.  I think the PBX would try to ground the line when you 
picked up a handset, and that resulted in a hangup on the ATA.


That's also the incident which introduced me to the Adtran Total 
Access.  It was the first ATA I found which supported ground start, and 
I've been very happy with that product.


-- Original Message --
From: "Chuck McCown" <ch...@wbmfg.com>
To: af@afmug.com
Sent: 11/27/2017 11:47:26 AM
Subject: Re: [AFMUG] ATA CallerID question

Any chance of a ground start vs loop start issue?  Some PBXs were 
ground start.  Not sure how that would affect caller ID.

Is the PBX actually detecting the ringing?

From:Nate Burke
Sent: Monday, November 27, 2017 9:34 AM
To:af@afmug.com
Subject: Re: [AFMUG] ATA CallerID question

Just an Update, I put a splitter in the phone line, and caller ID 
works perfect on any 'modern' handset.  But still does not work on the 
Lucent PBX.  The customer still swears it worked with his old AT 
lines, but seems resigned to the fact that he won't have caller ID 
Anymore.  I tried to sell him into a new PBX, but he "Has a truckload 
of spare parts for this PBX"


On 11/9/2017 3:53 PM, Adam Moffett wrote:
Oh rightI haven't picked up the phone yet so there's nothing to 
hear.
Sorry.  I haven't actually used one of these telephone thingys in a 
long time.



-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
Sent: 11/9/2017 4:52:46 PM
Subject: Re: [AFMUG] ATA CallerID question

Remember, the signal comes between rings. Unless you are listening 
on a butt set in line or watching the info pass through a switch you 
wouldn't see or hear it. The only reason I remembered between first 
and second is sitting at a class 5 switch trying to figure out why 
caller ID was failing on a feature group D trunk group and seeing 
them come through after one ringy dingy.


On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:
Is it at an inaudible frequency?  If so, then it wouldn't make it 
through 2600hz bandpass filters would it?  Or maybe it's audible, 
but so short you don't notice it? I'm fuzzy on this.


I probably shouldn't ask.  I don't need to know that much about 
POTS anymore.



-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
Sent: 11/9/2017 4:40:57 PM
Subject: Re: [AFMUG] ATA CallerID question

More info than anyone probably wants to know. I found this about 
the original question:

Caller-ID Signaling
According to Telcordia specifications, CND signaling starts as 
early as 300 mS after the first ring burst and ends at least 475 
mS before the second ring burst


From here: http://www.tech-faq.com/caller-id.html


On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:
I did not know that tone contained modulated data.  I just 
thought it

was a noise you wouldn't ignore.

That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com
To: af@afmug.com
Sent: 11/7/2017 4:39:27 PM
Subject: Re: [AFMUG] ATA CallerID question

>Monitor the line for the data burst.  It is the exact same 
modulation
>method as the emergency alert system you hear squawking on the 
TV

>before the beep and thunderstorm warning.
>
>I think it comes before the first ring or right after the first 
ring.
>Some of the original display units rectified and stored ring 
voltage
>for power so it may need the ring first to power the display box 
then

>the data.
>
>In any event, you can hear it if you have a butt sett with line 
monitor

>mode.
>Bell 202 is correct.
>
>-Original Message- From: Nate Burke
>Sent: Tuesday, November 7, 2017 1:58 PM
>To: Animal Farm
>Subject: [AFMUG] ATA CallerID question
>
>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 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

Re: [AFMUG] ATA CallerID question

[Adam Moffett]

When I plugged loop start lines into a ground start PBX they couldn't 
answer the phones.  I may not be remembering this right, but I think 
they did ring.  I think the PBX would try to ground the line when you 
picked up a handset, and that resulted in a hangup on the ATA.


That's also the incident which introduced me to the Adtran Total Access. 
 It was the first ATA I found which supported ground start, and I've 
been very happy with that product.


-- Original Message --
From: "Chuck McCown" <ch...@wbmfg.com>
To: af@afmug.com
Sent: 11/27/2017 11:47:26 AM
Subject: Re: [AFMUG] ATA CallerID question

Any chance of a ground start vs loop start issue?  Some PBXs were 
ground start.  Not sure how that would affect caller ID.

Is the PBX actually detecting the ringing?

From:Nate Burke
Sent: Monday, November 27, 2017 9:34 AM
To:af@afmug.com
Subject: Re: [AFMUG] ATA CallerID question

Just an Update, I put a splitter in the phone line, and caller ID works 
perfect on any 'modern' handset.  But still does not work on the Lucent 
PBX.  The customer still swears it worked with his old AT lines, but 
seems resigned to the fact that he won't have caller ID Anymore.  I 
tried to sell him into a new PBX, but he "Has a truckload of spare 
parts for this PBX"


On 11/9/2017 3:53 PM, Adam Moffett wrote:
Oh rightI haven't picked up the phone yet so there's nothing to 
hear.
Sorry.  I haven't actually used one of these telephone thingys in a 
long time.



-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
Sent: 11/9/2017 4:52:46 PM
Subject: Re: [AFMUG] ATA CallerID question

Remember, the signal comes between rings. Unless you are listening on 
a butt set in line or watching the info pass through a switch you 
wouldn't see or hear it. The only reason I remembered between first 
and second is sitting at a class 5 switch trying to figure out why 
caller ID was failing on a feature group D trunk group and seeing 
them come through after one ringy dingy.


On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:
Is it at an inaudible frequency?  If so, then it wouldn't make it 
through 2600hz bandpass filters would it?  Or maybe it's audible, 
but so short you don't notice it? I'm fuzzy on this.


I probably shouldn't ask.  I don't need to know that much about POTS 
anymore.



-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
Sent: 11/9/2017 4:40:57 PM
Subject: Re: [AFMUG] ATA CallerID question

More info than anyone probably wants to know. I found this about 
the original question:

Caller-ID Signaling
According to Telcordia specifications, CND signaling starts as 
early as 300 mS after the first ring burst and ends at least 475 mS 
before the second ring burst


From here: http://www.tech-faq.com/caller-id.html


On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:
I did not know that tone contained modulated data.  I just thought 
it

was a noise you wouldn't ignore.

That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com
To: af@afmug.com
Sent: 11/7/2017 4:39:27 PM
Subject: Re: [AFMUG] ATA CallerID question

>Monitor the line for the data burst.  It is the exact same 
modulation

>method as the emergency alert system you hear squawking on the TV
>before the beep and thunderstorm warning.
>
>I think it comes before the first ring or right after the first 
ring.
>Some of the original display units rectified and stored ring 
voltage
>for power so it may need the ring first to power the display box 
then

>the data.
>
>In any event, you can hear it if you have a butt sett with line 
monitor

>mode.
>Bell 202 is correct.
>
>-Original Message- From: Nate Burke
>Sent: Tuesday, November 7, 2017 1:58 PM
>To: Animal Farm
>Subject: [AFMUG] ATA CallerID question
>
>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 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

Re: [AFMUG] ATA CallerID question

[Lewis Bergman]

This is probably way off but is there any chance he had more than one line
and the one you are now working with doesn't have callerID? When you say
"When he had AT" does that mean you ported the lines to some other
provider? If so, is callerID enabled on the new line(s)?

On Mon, Nov 27, 2017 at 11:04 AM Nate Burke <n...@blastcomm.com> wrote:

> The phones on the PBX ring/talk/terminate normally.  Just no Caller ID.
> There is no Voicemail on the PBX, he has a answering machine plugged into
> the phone splitter, it yells out the Caller ID number when a call comes in,
> so that's working.  This is a small engine repair shop, proprietor has to
> be in his 70's, goes through about 4 packs of smokes a day while hunched
> over a tank full of gas.  I think the PBX was probably installed when he
> first opened his shop, however many decades ago that was.
>
> On 11/27/2017 10:47 AM, Chuck McCown wrote:
>
> Any chance of a ground start vs loop start issue?  Some PBXs were ground
> start.  Not sure how that would affect caller ID.
> Is the PBX actually detecting the ringing?
>
> *From:* Nate Burke
> *Sent:* Monday, November 27, 2017 9:34 AM
> *To:* af@afmug.com
> *Subject:* Re: [AFMUG] ATA CallerID question
>
> Just an Update, I put a splitter in the phone line, and caller ID works
> perfect on any 'modern' handset.  But still does not work on the Lucent
> PBX.  The customer still swears it worked with his old AT lines, but
> seems resigned to the fact that he won't have caller ID Anymore.  I tried
> to sell him into a new PBX, but he "Has a truckload of spare parts for this
> PBX"
>
> On 11/9/2017 3:53 PM, Adam Moffett wrote:
>
> Oh rightI haven't picked up the phone yet so there's nothing to hear.
> Sorry.  I haven't actually used one of these telephone thingys in a long
> time.
>
>
> -- Original Message ------
> From: "Lewis Bergman" <lewis.berg...@gmail.com>
> To: af@afmug.com
> Sent: 11/9/2017 4:52:46 PM
> Subject: Re: [AFMUG] ATA CallerID question
>
>
> Remember, the signal comes between rings. Unless you are listening on a
> butt set in line or watching the info pass through a switch you wouldn't
> see or hear it. The only reason I remembered between first and second is
> sitting at a class 5 switch trying to figure out why caller ID was failing
> on a feature group D trunk group and seeing them come through after one
> ringy dingy.
>
>
> On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>
>> Is it at an inaudible frequency?  If so, then it wouldn't make it through
>> 2600hz bandpass filters would it?  Or maybe it's audible, but so short you
>> don't notice it? I'm fuzzy on this.
>>
>> I probably shouldn't ask.  I don't need to know that much about POTS
>> anymore.
>>
>>
>> -- Original Message --
>> From: "Lewis Bergman" <lewis.berg...@gmail.com>
>> To: af@afmug.com
>> Sent: 11/9/2017 4:40:57 PM
>> Subject: Re: [AFMUG] ATA CallerID question
>>
>>
>> More info than anyone probably wants to know. I found this about the
>> original question:
>> Caller-ID Signaling
>>
>> According to Telcordia specifications, CND signaling starts as early as
>> 300 mS after the first ring burst and ends at least 475 mS before the
>> second ring burst
>>
>> From here: http://www.tech-faq.com/caller-id.html
>>
>> On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>>
>> I did not know that tone contained modulated data.  I just thought it
>>> was a noise you wouldn't ignore.
>>>
>>> That's a fun fact to have.
>>>
>>>
>>> -- Original Message --
>>> From: ch...@wbmfg.com
>>> To: af@afmug.com
>>> Sent: 11/7/2017 4:39:27 PM
>>> Subject: Re: [AFMUG] ATA CallerID question
>>>
>>> >Monitor the line for the data burst.  It is the exact same modulation
>>> >method as the emergency alert system you hear squawking on the TV
>>> >before the beep and thunderstorm warning.
>>> >
>>> >I think it comes before the first ring or right after the first ring.
>>> >Some of the original display units rectified and stored ring voltage
>>> >for power so it may need the ring first to power the display box then
>>> >the data.
>>> >
>>> >In any event, you can hear it if you have a butt sett with line monitor
>>> >mode.
>>> >Bell 202 is correct.
>>> >
>>> >-Original Message- From: Nate Burke
>>> >Sent: Tuesday, November 7

Re: [AFMUG] ATA CallerID question

[Nate Burke]

The phones on the PBX ring/talk/terminate normally.  Just no Caller ID.  
There is no Voicemail on the PBX, he has a answering machine plugged 
into the phone splitter, it yells out the Caller ID number when a call 
comes in, so that's working.  This is a small engine repair shop, 
proprietor has to be in his 70's, goes through about 4 packs of smokes a 
day while hunched over a tank full of gas.  I think the PBX was probably 
installed when he first opened his shop, however many decades ago that was.


On 11/27/2017 10:47 AM, Chuck McCown wrote:
Any chance of a ground start vs loop start issue?  Some PBXs were 
ground start.  Not sure how that would affect caller ID.

Is the PBX actually detecting the ringing?
*From:* Nate Burke
*Sent:* Monday, November 27, 2017 9:34 AM
*To:* af@afmug.com
*Subject:* Re: [AFMUG] ATA CallerID question
Just an Update, I put a splitter in the phone line, and caller ID 
works perfect on any 'modern' handset.  But still does not work on the 
Lucent PBX.  The customer still swears it worked with his old AT 
lines, but seems resigned to the fact that he won't have caller ID 
Anymore.  I tried to sell him into a new PBX, but he "Has a truckload 
of spare parts for this PBX"


On 11/9/2017 3:53 PM, Adam Moffett wrote:

Oh rightI haven't picked up the phone yet so there's nothing to hear.
Sorry.  I haven't actually used one of these telephone thingys in a 
long time.

-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
Sent: 11/9/2017 4:52:46 PM
Subject: Re: [AFMUG] ATA CallerID question
Remember, the signal comes between rings. Unless you are listening 
on a butt set in line or watching the info pass through a switch you 
wouldn't see or hear it. The only reason I remembered between first 
and second is sitting at a class 5 switch trying to figure out why 
caller ID was failing on a feature group D trunk group and seeing 
them come through after one ringy dingy.

On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:

Is it at an inaudible frequency?  If so, then it wouldn't make
it through 2600hz bandpass filters would it?  Or maybe it's
audible, but so short you don't notice it? I'm fuzzy on this.
I probably shouldn't ask.  I don't need to know that much about
POTS anymore.
-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
    Sent: 11/9/2017 4:40:57 PM
Subject: Re: [AFMUG] ATA CallerID question

More info than anyone probably wants to know. I found this
about the original question:


Caller-ID Signaling

According to Telcordia specifications, CND signaling starts as
early as 300 mS after the first ring burst and ends at least
475 mS before the second ring burst

From here: http://www.tech-faq.com/caller-id.html


On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett
<dmmoff...@gmail.com> wrote:

I did not know that tone contained modulated data.  I just
thought it
was a noise you wouldn't ignore.

That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com
To: af@afmug.com
    Sent: 11/7/2017 4:39:27 PM
Subject: Re: [AFMUG] ATA CallerID question

>Monitor the line for the data burst.  It is the exact same
modulation
>method as the emergency alert system you hear squawking on
the TV
>before the beep and thunderstorm warning.
>
>I think it comes before the first ring or right after the
first ring.
>Some of the original display units rectified and stored
ring voltage
>for power so it may need the ring first to power the
display box then
>the data.
>
>In any event, you can hear it if you have a butt sett with
line monitor
>mode.
>Bell 202 is correct.
>
>-Original Message- From: Nate Burke
        >Sent: Tuesday, November 7, 2017 1:58 PM
>To: Animal Farm
>Subject: [AFMUG] ATA CallerID question
>
>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 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

Re: [AFMUG] ATA CallerID question

[Chuck McCown]

Any chance of a ground start vs loop start issue?  Some PBXs were ground start. 
 Not sure how that would affect caller ID.  
Is the PBX actually detecting the ringing?

From: Nate Burke 
Sent: Monday, November 27, 2017 9:34 AM
To: af@afmug.com 
Subject: Re: [AFMUG] ATA CallerID question

Just an Update, I put a splitter in the phone line, and caller ID works perfect 
on any 'modern' handset.  But still does not work on the Lucent PBX.  The 
customer still swears it worked with his old AT lines, but seems resigned to 
the fact that he won't have caller ID Anymore.  I tried to sell him into a new 
PBX, but he "Has a truckload of spare parts for this PBX"  


On 11/9/2017 3:53 PM, Adam Moffett wrote:

  Oh rightI haven't picked up the phone yet so there's nothing to hear.
  Sorry.  I haven't actually used one of these telephone thingys in a long time.


  -- Original Message --
  From: "Lewis Bergman" <lewis.berg...@gmail.com>
  To: af@afmug.com
  Sent: 11/9/2017 4:52:46 PM
  Subject: Re: [AFMUG] ATA CallerID question

Remember, the signal comes between rings. Unless you are listening on a 
butt set in line or watching the info pass through a switch you wouldn't see or 
hear it. The only reason I remembered between first and second is sitting at a 
class 5 switch trying to figure out why caller ID was failing on a feature 
group D trunk group and seeing them come through after one ringy dingy.

On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:

  Is it at an inaudible frequency?  If so, then it wouldn't make it through 
2600hz bandpass filters would it?  Or maybe it's audible, but so short you 
don't notice it? I'm fuzzy on this.

  I probably shouldn't ask.  I don't need to know that much about POTS 
anymore.


  -- Original Message --
  From: "Lewis Bergman" <lewis.berg...@gmail.com>
  To: af@afmug.com
  Sent: 11/9/2017 4:40:57 PM
  Subject: Re: [AFMUG] ATA CallerID question

More info than anyone probably wants to know. I found this about the 
original question: 
Caller-ID Signaling
According to Telcordia specifications, CND signaling starts as early as 
300 mS after the first ring burst and ends at least 475 mS before the second 
ring burst

From here: http://www.tech-faq.com/caller-id.html



On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> wrote:

  I did not know that tone contained modulated data.  I just thought it
  was a noise you wouldn't ignore.

  That's a fun fact to have.


  -- Original Message --
  From: ch...@wbmfg.com
  To: af@afmug.com
      Sent: 11/7/2017 4:39:27 PM
  Subject: Re: [AFMUG] ATA CallerID question

  >Monitor the line for the data burst.  It is the exact same modulation
  >method as the emergency alert system you hear squawking on the TV
  >before the beep and thunderstorm warning.
  >
  >I think it comes before the first ring or right after the first ring.
  >Some of the original display units rectified and stored ring voltage
  >for power so it may need the ring first to power the display box then
  >the data.
  >
  >In any event, you can hear it if you have a butt sett with line 
monitor
  >mode.
  >Bell 202 is correct.
  >
  >-Original Message- From: Nate Burke
      >Sent: Tuesday, November 7, 2017 1:58 PM
  >To: Animal Farm
  >Subject: [AFMUG] ATA CallerID question
  >
  >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 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

Re: [AFMUG] ATA CallerID question

[Nate Burke]

Just an Update, I put a splitter in the phone line, and caller ID works 
perfect on any 'modern' handset.  But still does not work on the Lucent 
PBX.  The customer still swears it worked with his old AT lines, but 
seems resigned to the fact that he won't have caller ID Anymore.  I 
tried to sell him into a new PBX, but he "Has a truckload of spare parts 
for this PBX"


On 11/9/2017 3:53 PM, Adam Moffett wrote:

Oh rightI haven't picked up the phone yet so there's nothing to hear.
Sorry.  I haven't actually used one of these telephone thingys in a 
long time.



-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com 
<mailto:lewis.berg...@gmail.com>>

To: af@afmug.com <mailto:af@afmug.com>
Sent: 11/9/2017 4:52:46 PM
Subject: Re: [AFMUG] ATA CallerID question

Remember, the signal comes between rings. Unless you are listening on 
a butt set in line or watching the info pass through a switch you 
wouldn't see or hear it. The only reason I remembered between first 
and second is sitting at a class 5 switch trying to figure out why 
caller ID was failing on a feature group D trunk group and seeing 
them come through after one ringy dingy.


On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com 
<mailto:dmmoff...@gmail.com>> wrote:


Is it at an inaudible frequency?  If so, then it wouldn't make it
through 2600hz bandpass filters would it?  Or maybe it's audible,
but so short you don't notice it? I'm fuzzy on this.

I probably shouldn't ask.  I don't need to know that much about
POTS anymore.


-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com
<mailto:lewis.berg...@gmail.com>>
To: af@afmug.com <mailto:af@afmug.com>
Sent: 11/9/2017 4:40:57 PM
Subject: Re: [AFMUG] ATA CallerID question


More info than anyone probably wants to know. I found this about
the original question:


Caller-ID Signaling

According to Telcordia specifications, CND signaling starts as
early as 300 mS after the first ring burst and ends at least 475
mS before the second ring burst

From here: http://www.tech-faq.com/caller-id.html


On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com
<mailto:dmmoff...@gmail.com>> wrote:

I did not know that tone contained modulated data.  I just
thought it
was a noise you wouldn't ignore.

That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com <mailto:ch...@wbmfg.com>
To: af@afmug.com <mailto:af@afmug.com>
Sent: 11/7/2017 4:39:27 PM
Subject: Re: [AFMUG] ATA CallerID question

>Monitor the line for the data burst.  It is the exact same
modulation
>method as the emergency alert system you hear squawking on
the TV
>before the beep and thunderstorm warning.
>
>I think it comes before the first ring or right after the
first ring.
>Some of the original display units rectified and stored
ring voltage
>for power so it may need the ring first to power the
display box then
>the data.
>
>In any event, you can hear it if you have a butt sett with
line monitor
>mode.
>Bell 202 is correct.
>
    >-----Original Message- From: Nate Burke
>Sent: Tuesday, November 7, 2017 1:58 PM
>To: Animal Farm
>Subject: [AFMUG] ATA CallerID question
>
>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 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

Re: [AFMUG] ATA CallerID question

[Chuck McCown]

OH, I still have the MOSFET book and all my tab books.  It is just the books 
full of transistor and chip data sheets that I tossed.  

From: Forrest Christian (List Account) 
Sent: Thursday, November 09, 2017 10:30 PM
To: af 
Subject: Re: [AFMUG] ATA CallerID question

There are a few that I have that I haven't been able to find electronically and 
still refer to.   For example, the MOSFET data book I could never find 
anywhere, and I still occasionally will refer back to the wonderful discussion 
of MOSFET operation when needed (although it's been a while since I've needed 
to).   The archive I pointed toward has that one and I think the majority of 
the books I have. 

I also have a few old tab electronics books with cool old projects.  Haven't 
found those anywhere either.   

On Thu, Nov 9, 2017 at 10:25 PM, Chuck McCown <ch...@wbmfg.com> wrote:

  I tossed mine years ago, once I was sure they were available on CD.  

  The law firm I use still has a large law library.  
  It is where people go for some quiet or to eat lunch.  

  From: Forrest Christian (List Account) 
  Sent: Thursday, November 09, 2017 10:20 PM
  To: af 
  Subject: Re: [AFMUG] ATA CallerID question

  I've got a good collection still here in boxes, haven't had a chance to go 
through them yet.

  I think the plan will be to verify I have a .pdf copy of the ones I care of 
and then sell/discard/donate to the cause as appropriate.   

  On Thu, Nov 9, 2017 at 10:17 PM, Chuck McCown <ch...@wbmfg.com> wrote:

Oh man!  I had forgotten how many different data manuals there were and I 
had most of them too.  
Wow

From: Forrest Christian (List Account) 
Sent: Thursday, November 09, 2017 10:12 PM
To: af 
Subject: Re: [AFMUG] ATA CallerID question

Chuck,

I'm sorry for the timesink I'm about to introduce you to:

http://www.bitsavers.org/components/motorola/_dataBooks/

http://www.bitsavers.org/components/ti/_dataBooks/

http://www.bitsavers.org/components/national/_dataBooks/


Or you can just go to www.bitsavers.org for even more time consumption.



On Thu, Nov 9, 2017 at 9:44 PM, Chuck McCown <ch...@wbmfg.com> wrote:

  Back in the day, I was a bona-fide SLIC expert.  Subscriber Line 
Interface Circuit.  I designed and built crap that interfaced with POTS lines.  
So I knew just about everything having to do with dial tone circuits.  Much of 
the stuff was learned by reading data manuals.  I had hundreds of them  Blue 
and brown from Motorola.  Yellow from Texas Instruments.  Gray from Maxim.  
Navy blue from National.  etc etc Good bed time readin’

  From: Steve Jones 
  Sent: Thursday, November 09, 2017 9:19 PM
  To: af@afmug.com 
  Subject: Re: [AFMUG] ATA CallerID question

  Out of curiousity, i learn this nonsense from folks in the know. Where do 
folks in the know learn this shit? Is it that they were involved in the day 
when people in the service industry knew what they were doing, or prior to 
mailing lists was there some analog solution center? Like did you old folks 
hang out near your telegraph listening to everybodies conversations? Does it 
boil down to some old chinese guy sending out coded messages or what? 
  Was at a customers joint the other day, an issue with ms rdp, end of the 
day, it boiled down to remote connectivity, had to disable a tertiary networks 
gpo printer and disable bitmap caching. I got this from google. Seperate 
threads and a brain connection that this was the second remote joint via vpn, 
and the two remote joints couldnt communicate.
  Customer noted the google use, i told him its cause we dont have manuals 
now.
  Is the truth that some chinese guy just answers all our google queries 
now and we are just corporate puppets?

  Is there only one really old rice eating fellow that actually knows the 
answers? What if he dies?
  Are we fucked if the chinaman dies?

  On Nov 9, 2017 4:46 PM, "Forrest Christian (List Account)" 
<li...@packetflux.com> wrote:

If you have call waiting, you'll often hear the caller id 'data burp' 
after the first 'call is waiting' beep...

On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com> 
wrote:

  Remember, the signal comes between rings. Unless you are listening on 
a butt set in line or watching the info pass through a switch you wouldn't see 
or hear it. The only reason I remembered between first and second is sitting at 
a class 5 switch trying to figure out why caller ID was failing on a feature 
group D trunk group and seeing them come through after one ringy dingy.

  On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:

Is it at an inaudible frequency?  If so, then it wouldn't make it 
through 2600hz bandpass filters would it?  Or maybe it's audible, but so short 
you don't notice it? I'm fuzzy on this.

I

Re: [AFMUG] ATA CallerID question

[Forrest Christian (List Account)]

There are a few that I have that I haven't been able to find electronically
and still refer to.   For example, the MOSFET data book I could never find
anywhere, and I still occasionally will refer back to the wonderful
discussion of MOSFET operation when needed (although it's been a while
since I've needed to).   The archive I pointed toward has that one and I
think the majority of the books I have.

I also have a few old tab electronics books with cool old projects.
Haven't found those anywhere either.

On Thu, Nov 9, 2017 at 10:25 PM, Chuck McCown <ch...@wbmfg.com> wrote:

> I tossed mine years ago, once I was sure they were available on CD.
>
> The law firm I use still has a large law library.
> It is where people go for some quiet or to eat lunch.
>
> *From:* Forrest Christian (List Account)
> *Sent:* Thursday, November 09, 2017 10:20 PM
> *To:* af
> *Subject:* Re: [AFMUG] ATA CallerID question
>
> I've got a good collection still here in boxes, haven't had a chance to go
> through them yet.
>
> I think the plan will be to verify I have a .pdf copy of the ones I care
> of and then sell/discard/donate to the cause as appropriate.
>
> On Thu, Nov 9, 2017 at 10:17 PM, Chuck McCown <ch...@wbmfg.com> wrote:
>
>> Oh man!  I had forgotten how many different data manuals there were and I
>> had most of them too.
>> Wow
>>
>> *From:* Forrest Christian (List Account)
>> *Sent:* Thursday, November 09, 2017 10:12 PM
>> *To:* af
>> *Subject:* Re: [AFMUG] ATA CallerID question
>>
>> Chuck,
>>
>> I'm sorry for the timesink I'm about to introduce you to:
>>
>> http://www.bitsavers.org/components/motorola/_dataBooks/
>> http://www.bitsavers.org/components/ti/_dataBooks/
>> http://www.bitsavers.org/components/national/_dataBooks/
>>
>> Or you can just go to www.bitsavers.org for even more time consumption.
>>
>>
>>
>> On Thu, Nov 9, 2017 at 9:44 PM, Chuck McCown <ch...@wbmfg.com> wrote:
>>
>>> Back in the day, I was a bona-fide SLIC expert.  Subscriber Line
>>> Interface Circuit.  I designed and built crap that interfaced with POTS
>>> lines.  So I knew just about everything having to do with dial tone
>>> circuits.  Much of the stuff was learned by reading data manuals.  I had
>>> hundreds of them  Blue and brown from Motorola.  Yellow from Texas
>>> Instruments.  Gray from Maxim.  Navy blue from National.  etc etc Good
>>> bed time readin’
>>>
>>> *From:* Steve Jones
>>> *Sent:* Thursday, November 09, 2017 9:19 PM
>>> *To:* af@afmug.com
>>> *Subject:* Re: [AFMUG] ATA CallerID question
>>>
>>> Out of curiousity, i learn this nonsense from folks in the know. Where
>>> do folks in the know learn this shit? Is it that they were involved in the
>>> day when people in the service industry knew what they were doing, or prior
>>> to mailing lists was there some analog solution center? Like did you old
>>> folks hang out near your telegraph listening to everybodies conversations?
>>> Does it boil down to some old chinese guy sending out coded messages or
>>> what?
>>> Was at a customers joint the other day, an issue with ms rdp, end of the
>>> day, it boiled down to remote connectivity, had to disable a tertiary
>>> networks gpo printer and disable bitmap caching. I got this from google.
>>> Seperate threads and a brain connection that this was the second remote
>>> joint via vpn, and the two remote joints couldnt communicate.
>>> Customer noted the google use, i told him its cause we dont have manuals
>>> now.
>>> Is the truth that some chinese guy just answers all our google queries
>>> now and we are just corporate puppets?
>>>
>>> Is there only one really old rice eating fellow that actually knows the
>>> answers? What if he dies?
>>> Are we fucked if the chinaman dies?
>>>
>>> On Nov 9, 2017 4:46 PM, "Forrest Christian (List Account)" <
>>> li...@packetflux.com> wrote:
>>>
>>> If you have call waiting, you'll often hear the caller id 'data burp'
>>> after the first 'call is waiting' beep...
>>>
>>> On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com>
>>> wrote:
>>>
>>>> Remember, the signal comes between rings. Unless you are listening on a
>>>> butt set in line or watching the info pass through a switch you wouldn't
>>>> see or hear it. The only reason I remembered between first and second is
>>>> sitting at a class 5 switch trying to figu

Re: [AFMUG] ATA CallerID question

[Chuck McCown]

I tossed mine years ago, once I was sure they were available on CD.  

The law firm I use still has a large law library.  
It is where people go for some quiet or to eat lunch.  

From: Forrest Christian (List Account) 
Sent: Thursday, November 09, 2017 10:20 PM
To: af 
Subject: Re: [AFMUG] ATA CallerID question

I've got a good collection still here in boxes, haven't had a chance to go 
through them yet.

I think the plan will be to verify I have a .pdf copy of the ones I care of and 
then sell/discard/donate to the cause as appropriate.   

On Thu, Nov 9, 2017 at 10:17 PM, Chuck McCown <ch...@wbmfg.com> wrote:

  Oh man!  I had forgotten how many different data manuals there were and I had 
most of them too.  
  Wow

  From: Forrest Christian (List Account) 
  Sent: Thursday, November 09, 2017 10:12 PM
  To: af 
  Subject: Re: [AFMUG] ATA CallerID question

  Chuck,

  I'm sorry for the timesink I'm about to introduce you to:

  http://www.bitsavers.org/components/motorola/_dataBooks/

  http://www.bitsavers.org/components/ti/_dataBooks/

  http://www.bitsavers.org/components/national/_dataBooks/


  Or you can just go to www.bitsavers.org for even more time consumption.



  On Thu, Nov 9, 2017 at 9:44 PM, Chuck McCown <ch...@wbmfg.com> wrote:

Back in the day, I was a bona-fide SLIC expert.  Subscriber Line Interface 
Circuit.  I designed and built crap that interfaced with POTS lines.  So I knew 
just about everything having to do with dial tone circuits.  Much of the stuff 
was learned by reading data manuals.  I had hundreds of them  Blue and brown 
from Motorola.  Yellow from Texas Instruments.  Gray from Maxim.  Navy blue 
from National.  etc etc Good bed time readin’

From: Steve Jones 
Sent: Thursday, November 09, 2017 9:19 PM
To: af@afmug.com 
Subject: Re: [AFMUG] ATA CallerID question

Out of curiousity, i learn this nonsense from folks in the know. Where do 
folks in the know learn this shit? Is it that they were involved in the day 
when people in the service industry knew what they were doing, or prior to 
mailing lists was there some analog solution center? Like did you old folks 
hang out near your telegraph listening to everybodies conversations? Does it 
boil down to some old chinese guy sending out coded messages or what? 
Was at a customers joint the other day, an issue with ms rdp, end of the 
day, it boiled down to remote connectivity, had to disable a tertiary networks 
gpo printer and disable bitmap caching. I got this from google. Seperate 
threads and a brain connection that this was the second remote joint via vpn, 
and the two remote joints couldnt communicate.
Customer noted the google use, i told him its cause we dont have manuals 
now.
Is the truth that some chinese guy just answers all our google queries now 
and we are just corporate puppets?

Is there only one really old rice eating fellow that actually knows the 
answers? What if he dies?
Are we fucked if the chinaman dies?

On Nov 9, 2017 4:46 PM, "Forrest Christian (List Account)" 
<li...@packetflux.com> wrote:

  If you have call waiting, you'll often hear the caller id 'data burp' 
after the first 'call is waiting' beep...

  On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com> 
wrote:

Remember, the signal comes between rings. Unless you are listening on a 
butt set in line or watching the info pass through a switch you wouldn't see or 
hear it. The only reason I remembered between first and second is sitting at a 
class 5 switch trying to figure out why caller ID was failing on a feature 
group D trunk group and seeing them come through after one ringy dingy.

On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:

  Is it at an inaudible frequency?  If so, then it wouldn't make it 
through 2600hz bandpass filters would it?  Or maybe it's audible, but so short 
you don't notice it? I'm fuzzy on this.

  I probably shouldn't ask.  I don't need to know that much about POTS 
anymore.


  -- Original Message --
  From: "Lewis Bergman" <lewis.berg...@gmail.com>
  To: af@afmug.com
  Sent: 11/9/2017 4:40:57 PM
  Subject: Re: [AFMUG] ATA CallerID question

More info than anyone probably wants to know. I found this about 
the original question: 
Caller-ID Signaling
According to Telcordia specifications, CND signaling starts as 
early as 300 mS after the first ring burst and ends at least 475 mS before the 
second ring burst

From here: http://www.tech-faq.com/caller-id.html



On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:

  I did not know that tone contained modulated data.  I just 
thought it
  was a noise you wouldn't ignore.

  That

Re: [AFMUG] ATA CallerID question

[Forrest Christian (List Account)]

I've got a good collection still here in boxes, haven't had a chance to go
through them yet.

I think the plan will be to verify I have a .pdf copy of the ones I care of
and then sell/discard/donate to the cause as appropriate.

On Thu, Nov 9, 2017 at 10:17 PM, Chuck McCown <ch...@wbmfg.com> wrote:

> Oh man!  I had forgotten how many different data manuals there were and I
> had most of them too.
> Wow
>
> *From:* Forrest Christian (List Account)
> *Sent:* Thursday, November 09, 2017 10:12 PM
> *To:* af
> *Subject:* Re: [AFMUG] ATA CallerID question
>
> Chuck,
>
> I'm sorry for the timesink I'm about to introduce you to:
>
> http://www.bitsavers.org/components/motorola/_dataBooks/
> http://www.bitsavers.org/components/ti/_dataBooks/
> http://www.bitsavers.org/components/national/_dataBooks/
>
> Or you can just go to www.bitsavers.org for even more time consumption.
>
>
>
> On Thu, Nov 9, 2017 at 9:44 PM, Chuck McCown <ch...@wbmfg.com> wrote:
>
>> Back in the day, I was a bona-fide SLIC expert.  Subscriber Line
>> Interface Circuit.  I designed and built crap that interfaced with POTS
>> lines.  So I knew just about everything having to do with dial tone
>> circuits.  Much of the stuff was learned by reading data manuals.  I had
>> hundreds of them  Blue and brown from Motorola.  Yellow from Texas
>> Instruments.  Gray from Maxim.  Navy blue from National.  etc etc Good
>> bed time readin’
>>
>> *From:* Steve Jones
>> *Sent:* Thursday, November 09, 2017 9:19 PM
>> *To:* af@afmug.com
>> *Subject:* Re: [AFMUG] ATA CallerID question
>>
>> Out of curiousity, i learn this nonsense from folks in the know. Where do
>> folks in the know learn this shit? Is it that they were involved in the day
>> when people in the service industry knew what they were doing, or prior to
>> mailing lists was there some analog solution center? Like did you old folks
>> hang out near your telegraph listening to everybodies conversations? Does
>> it boil down to some old chinese guy sending out coded messages or what?
>> Was at a customers joint the other day, an issue with ms rdp, end of the
>> day, it boiled down to remote connectivity, had to disable a tertiary
>> networks gpo printer and disable bitmap caching. I got this from google.
>> Seperate threads and a brain connection that this was the second remote
>> joint via vpn, and the two remote joints couldnt communicate.
>> Customer noted the google use, i told him its cause we dont have manuals
>> now.
>> Is the truth that some chinese guy just answers all our google queries
>> now and we are just corporate puppets?
>>
>> Is there only one really old rice eating fellow that actually knows the
>> answers? What if he dies?
>> Are we fucked if the chinaman dies?
>>
>> On Nov 9, 2017 4:46 PM, "Forrest Christian (List Account)" <
>> li...@packetflux.com> wrote:
>>
>> If you have call waiting, you'll often hear the caller id 'data burp'
>> after the first 'call is waiting' beep...
>>
>> On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com>
>> wrote:
>>
>>> Remember, the signal comes between rings. Unless you are listening on a
>>> butt set in line or watching the info pass through a switch you wouldn't
>>> see or hear it. The only reason I remembered between first and second is
>>> sitting at a class 5 switch trying to figure out why caller ID was failing
>>> on a feature group D trunk group and seeing them come through after one
>>> ringy dingy.
>>>
>>> On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>>>
>>>> Is it at an inaudible frequency?  If so, then it wouldn't make it
>>>> through 2600hz bandpass filters would it?  Or maybe it's audible, but so
>>>> short you don't notice it? I'm fuzzy on this.
>>>>
>>>> I probably shouldn't ask.  I don't need to know that much about POTS
>>>> anymore.
>>>>
>>>>
>>>> -- Original Message --
>>>> From: "Lewis Bergman" <lewis.berg...@gmail.com>
>>>> To: af@afmug.com
>>>> Sent: 11/9/2017 4:40:57 PM
>>>> Subject: Re: [AFMUG] ATA CallerID question
>>>>
>>>>
>>>> More info than anyone probably wants to know. I found this about the
>>>> original question:
>>>> Caller-ID Signaling
>>>>
>>>> According to Telcordia specifications, CND signaling starts as early as
>>>> 300 mS after the first rin

Re: [AFMUG] ATA CallerID question

[Chuck McCown]

Oh man!  I had forgotten how many different data manuals there were and I had 
most of them too.  
Wow

From: Forrest Christian (List Account) 
Sent: Thursday, November 09, 2017 10:12 PM
To: af 
Subject: Re: [AFMUG] ATA CallerID question

Chuck,

I'm sorry for the timesink I'm about to introduce you to:

http://www.bitsavers.org/components/motorola/_dataBooks/

http://www.bitsavers.org/components/ti/_dataBooks/

http://www.bitsavers.org/components/national/_dataBooks/


Or you can just go to www.bitsavers.org for even more time consumption.



On Thu, Nov 9, 2017 at 9:44 PM, Chuck McCown <ch...@wbmfg.com> wrote:

  Back in the day, I was a bona-fide SLIC expert.  Subscriber Line Interface 
Circuit.  I designed and built crap that interfaced with POTS lines.  So I knew 
just about everything having to do with dial tone circuits.  Much of the stuff 
was learned by reading data manuals.  I had hundreds of them  Blue and brown 
from Motorola.  Yellow from Texas Instruments.  Gray from Maxim.  Navy blue 
from National.  etc etc Good bed time readin’

  From: Steve Jones 
  Sent: Thursday, November 09, 2017 9:19 PM
  To: af@afmug.com 
  Subject: Re: [AFMUG] ATA CallerID question

  Out of curiousity, i learn this nonsense from folks in the know. Where do 
folks in the know learn this shit? Is it that they were involved in the day 
when people in the service industry knew what they were doing, or prior to 
mailing lists was there some analog solution center? Like did you old folks 
hang out near your telegraph listening to everybodies conversations? Does it 
boil down to some old chinese guy sending out coded messages or what? 
  Was at a customers joint the other day, an issue with ms rdp, end of the day, 
it boiled down to remote connectivity, had to disable a tertiary networks gpo 
printer and disable bitmap caching. I got this from google. Seperate threads 
and a brain connection that this was the second remote joint via vpn, and the 
two remote joints couldnt communicate.
  Customer noted the google use, i told him its cause we dont have manuals now.
  Is the truth that some chinese guy just answers all our google queries now 
and we are just corporate puppets?

  Is there only one really old rice eating fellow that actually knows the 
answers? What if he dies?
  Are we fucked if the chinaman dies?

  On Nov 9, 2017 4:46 PM, "Forrest Christian (List Account)" 
<li...@packetflux.com> wrote:

If you have call waiting, you'll often hear the caller id 'data burp' after 
the first 'call is waiting' beep...

On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com> 
wrote:

  Remember, the signal comes between rings. Unless you are listening on a 
butt set in line or watching the info pass through a switch you wouldn't see or 
hear it. The only reason I remembered between first and second is sitting at a 
class 5 switch trying to figure out why caller ID was failing on a feature 
group D trunk group and seeing them come through after one ringy dingy.

  On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:

Is it at an inaudible frequency?  If so, then it wouldn't make it 
through 2600hz bandpass filters would it?  Or maybe it's audible, but so short 
you don't notice it? I'm fuzzy on this.

I probably shouldn't ask.  I don't need to know that much about POTS 
anymore.


-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
    Sent: 11/9/2017 4:40:57 PM
Subject: Re: [AFMUG] ATA CallerID question

  More info than anyone probably wants to know. I found this about the 
original question: 
  Caller-ID Signaling
  According to Telcordia specifications, CND signaling starts as early 
as 300 mS after the first ring burst and ends at least 475 mS before the second 
ring burst

  From here: http://www.tech-faq.com/caller-id.html



  On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:

I did not know that tone contained modulated data.  I just thought 
it
was a noise you wouldn't ignore.

That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com
To: af@afmug.com
    Sent: 11/7/2017 4:39:27 PM
Subject: Re: [AFMUG] ATA CallerID question

>Monitor the line for the data burst.  It is the exact same 
modulation
>method as the emergency alert system you hear squawking on the TV
>before the beep and thunderstorm warning.
>
>I think it comes before the first ring or right after the first 
ring.
>Some of the original display units rectified and stored ring 
voltage
>for power so it may need the ring first to power the display box 
then
 

Re: [AFMUG] ATA CallerID question

[Chuck McCown]

Do they have the thomas register too?

From: Forrest Christian (List Account) 
Sent: Thursday, November 09, 2017 10:12 PM
To: af 
Subject: Re: [AFMUG] ATA CallerID question

Chuck,

I'm sorry for the timesink I'm about to introduce you to:

http://www.bitsavers.org/components/motorola/_dataBooks/

http://www.bitsavers.org/components/ti/_dataBooks/

http://www.bitsavers.org/components/national/_dataBooks/


Or you can just go to www.bitsavers.org for even more time consumption.



On Thu, Nov 9, 2017 at 9:44 PM, Chuck McCown <ch...@wbmfg.com> wrote:

  Back in the day, I was a bona-fide SLIC expert.  Subscriber Line Interface 
Circuit.  I designed and built crap that interfaced with POTS lines.  So I knew 
just about everything having to do with dial tone circuits.  Much of the stuff 
was learned by reading data manuals.  I had hundreds of them  Blue and brown 
from Motorola.  Yellow from Texas Instruments.  Gray from Maxim.  Navy blue 
from National.  etc etc Good bed time readin’

  From: Steve Jones 
  Sent: Thursday, November 09, 2017 9:19 PM
  To: af@afmug.com 
  Subject: Re: [AFMUG] ATA CallerID question

  Out of curiousity, i learn this nonsense from folks in the know. Where do 
folks in the know learn this shit? Is it that they were involved in the day 
when people in the service industry knew what they were doing, or prior to 
mailing lists was there some analog solution center? Like did you old folks 
hang out near your telegraph listening to everybodies conversations? Does it 
boil down to some old chinese guy sending out coded messages or what? 
  Was at a customers joint the other day, an issue with ms rdp, end of the day, 
it boiled down to remote connectivity, had to disable a tertiary networks gpo 
printer and disable bitmap caching. I got this from google. Seperate threads 
and a brain connection that this was the second remote joint via vpn, and the 
two remote joints couldnt communicate.
  Customer noted the google use, i told him its cause we dont have manuals now.
  Is the truth that some chinese guy just answers all our google queries now 
and we are just corporate puppets?

  Is there only one really old rice eating fellow that actually knows the 
answers? What if he dies?
  Are we fucked if the chinaman dies?

  On Nov 9, 2017 4:46 PM, "Forrest Christian (List Account)" 
<li...@packetflux.com> wrote:

If you have call waiting, you'll often hear the caller id 'data burp' after 
the first 'call is waiting' beep...

On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com> 
wrote:

  Remember, the signal comes between rings. Unless you are listening on a 
butt set in line or watching the info pass through a switch you wouldn't see or 
hear it. The only reason I remembered between first and second is sitting at a 
class 5 switch trying to figure out why caller ID was failing on a feature 
group D trunk group and seeing them come through after one ringy dingy.

  On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:

Is it at an inaudible frequency?  If so, then it wouldn't make it 
through 2600hz bandpass filters would it?  Or maybe it's audible, but so short 
you don't notice it? I'm fuzzy on this.

I probably shouldn't ask.  I don't need to know that much about POTS 
anymore.


-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
    Sent: 11/9/2017 4:40:57 PM
Subject: Re: [AFMUG] ATA CallerID question

  More info than anyone probably wants to know. I found this about the 
original question: 
  Caller-ID Signaling
  According to Telcordia specifications, CND signaling starts as early 
as 300 mS after the first ring burst and ends at least 475 mS before the second 
ring burst

  From here: http://www.tech-faq.com/caller-id.html



  On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:

I did not know that tone contained modulated data.  I just thought 
it
was a noise you wouldn't ignore.

That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com
To: af@afmug.com
    Sent: 11/7/2017 4:39:27 PM
Subject: Re: [AFMUG] ATA CallerID question

>Monitor the line for the data burst.  It is the exact same 
modulation
>method as the emergency alert system you hear squawking on the TV
>before the beep and thunderstorm warning.
>
>I think it comes before the first ring or right after the first 
ring.
>Some of the original display units rectified and stored ring 
voltage
>for power so it may need the ring first to power the display box 
then
>the data.
>
>In a

Re: [AFMUG] ATA CallerID question

[Forrest Christian (List Account)]

Chuck,

I'm sorry for the timesink I'm about to introduce you to:

http://www.bitsavers.org/components/motorola/_dataBooks/
http://www.bitsavers.org/components/ti/_dataBooks/
http://www.bitsavers.org/components/national/_dataBooks/

Or you can just go to www.bitsavers.org for even more time consumption.



On Thu, Nov 9, 2017 at 9:44 PM, Chuck McCown <ch...@wbmfg.com> wrote:

> Back in the day, I was a bona-fide SLIC expert.  Subscriber Line Interface
> Circuit.  I designed and built crap that interfaced with POTS lines.  So I
> knew just about everything having to do with dial tone circuits.  Much of
> the stuff was learned by reading data manuals.  I had hundreds of them
> Blue and brown from Motorola.  Yellow from Texas Instruments.  Gray from
> Maxim.  Navy blue from National.  etc etc Good bed time readin’
>
> *From:* Steve Jones
> *Sent:* Thursday, November 09, 2017 9:19 PM
> *To:* af@afmug.com
> *Subject:* Re: [AFMUG] ATA CallerID question
>
> Out of curiousity, i learn this nonsense from folks in the know. Where do
> folks in the know learn this shit? Is it that they were involved in the day
> when people in the service industry knew what they were doing, or prior to
> mailing lists was there some analog solution center? Like did you old folks
> hang out near your telegraph listening to everybodies conversations? Does
> it boil down to some old chinese guy sending out coded messages or what?
> Was at a customers joint the other day, an issue with ms rdp, end of the
> day, it boiled down to remote connectivity, had to disable a tertiary
> networks gpo printer and disable bitmap caching. I got this from google.
> Seperate threads and a brain connection that this was the second remote
> joint via vpn, and the two remote joints couldnt communicate.
> Customer noted the google use, i told him its cause we dont have manuals
> now.
> Is the truth that some chinese guy just answers all our google queries now
> and we are just corporate puppets?
>
> Is there only one really old rice eating fellow that actually knows the
> answers? What if he dies?
> Are we fucked if the chinaman dies?
>
> On Nov 9, 2017 4:46 PM, "Forrest Christian (List Account)" <
> li...@packetflux.com> wrote:
>
> If you have call waiting, you'll often hear the caller id 'data burp'
> after the first 'call is waiting' beep...
>
> On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com>
> wrote:
>
>> Remember, the signal comes between rings. Unless you are listening on a
>> butt set in line or watching the info pass through a switch you wouldn't
>> see or hear it. The only reason I remembered between first and second is
>> sitting at a class 5 switch trying to figure out why caller ID was failing
>> on a feature group D trunk group and seeing them come through after one
>> ringy dingy.
>>
>> On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>>
>>> Is it at an inaudible frequency?  If so, then it wouldn't make it
>>> through 2600hz bandpass filters would it?  Or maybe it's audible, but so
>>> short you don't notice it? I'm fuzzy on this.
>>>
>>> I probably shouldn't ask.  I don't need to know that much about POTS
>>> anymore.
>>>
>>>
>>> -- Original Message --
>>> From: "Lewis Bergman" <lewis.berg...@gmail.com>
>>> To: af@afmug.com
>>> Sent: 11/9/2017 4:40:57 PM
>>> Subject: Re: [AFMUG] ATA CallerID question
>>>
>>>
>>> More info than anyone probably wants to know. I found this about the
>>> original question:
>>> Caller-ID Signaling
>>>
>>> According to Telcordia specifications, CND signaling starts as early as
>>> 300 mS after the first ring burst and ends at least 475 mS before the
>>> second ring burst
>>>
>>> From here: http://www.tech-faq.com/caller-id.html
>>>
>>> On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>>>
>>> I did not know that tone contained modulated data.  I just thought it
>>>> was a noise you wouldn't ignore.
>>>>
>>>> That's a fun fact to have.
>>>>
>>>>
>>>> -- Original Message --
>>>> From: ch...@wbmfg.com
>>>> To: af@afmug.com
>>>> Sent: 11/7/2017 4:39:27 PM
>>>> Subject: Re: [AFMUG] ATA CallerID question
>>>>
>>>> >Monitor the line for the data burst.  It is the exact same modulation
>>>> >method as the emergency alert system you hear squawking on the TV
>>>> >before the beep 

Re: [AFMUG] ATA CallerID question

[Chuck McCown]

Back in the day, I was a bona-fide SLIC expert.  Subscriber Line Interface 
Circuit.  I designed and built crap that interfaced with POTS lines.  So I knew 
just about everything having to do with dial tone circuits.  Much of the stuff 
was learned by reading data manuals.  I had hundreds of them  Blue and brown 
from Motorola.  Yellow from Texas Instruments.  Gray from Maxim.  Navy blue 
from National.  etc etc Good bed time readin’

From: Steve Jones 
Sent: Thursday, November 09, 2017 9:19 PM
To: af@afmug.com 
Subject: Re: [AFMUG] ATA CallerID question

Out of curiousity, i learn this nonsense from folks in the know. Where do folks 
in the know learn this shit? Is it that they were involved in the day when 
people in the service industry knew what they were doing, or prior to mailing 
lists was there some analog solution center? Like did you old folks hang out 
near your telegraph listening to everybodies conversations? Does it boil down 
to some old chinese guy sending out coded messages or what? 
Was at a customers joint the other day, an issue with ms rdp, end of the day, 
it boiled down to remote connectivity, had to disable a tertiary networks gpo 
printer and disable bitmap caching. I got this from google. Seperate threads 
and a brain connection that this was the second remote joint via vpn, and the 
two remote joints couldnt communicate.
Customer noted the google use, i told him its cause we dont have manuals now.
Is the truth that some chinese guy just answers all our google queries now and 
we are just corporate puppets?

Is there only one really old rice eating fellow that actually knows the 
answers? What if he dies?
Are we fucked if the chinaman dies?

On Nov 9, 2017 4:46 PM, "Forrest Christian (List Account)" 
<li...@packetflux.com> wrote:

  If you have call waiting, you'll often hear the caller id 'data burp' after 
the first 'call is waiting' beep...

  On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com> wrote:

Remember, the signal comes between rings. Unless you are listening on a 
butt set in line or watching the info pass through a switch you wouldn't see or 
hear it. The only reason I remembered between first and second is sitting at a 
class 5 switch trying to figure out why caller ID was failing on a feature 
group D trunk group and seeing them come through after one ringy dingy.

On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:

  Is it at an inaudible frequency?  If so, then it wouldn't make it through 
2600hz bandpass filters would it?  Or maybe it's audible, but so short you 
don't notice it? I'm fuzzy on this.

  I probably shouldn't ask.  I don't need to know that much about POTS 
anymore.


  -- Original Message --
  From: "Lewis Bergman" <lewis.berg...@gmail.com>
  To: af@afmug.com
  Sent: 11/9/2017 4:40:57 PM
  Subject: Re: [AFMUG] ATA CallerID question

More info than anyone probably wants to know. I found this about the 
original question: 
Caller-ID Signaling
According to Telcordia specifications, CND signaling starts as early as 
300 mS after the first ring burst and ends at least 475 mS before the second 
ring burst

From here: http://www.tech-faq.com/caller-id.html



On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> wrote:

  I did not know that tone contained modulated data.  I just thought it
  was a noise you wouldn't ignore.

  That's a fun fact to have.


  -- Original Message --
  From: ch...@wbmfg.com
  To: af@afmug.com
  Sent: 11/7/2017 4:39:27 PM
  Subject: Re: [AFMUG] ATA CallerID question

  >Monitor the line for the data burst.  It is the exact same modulation
  >method as the emergency alert system you hear squawking on the TV
  >before the beep and thunderstorm warning.
  >
  >I think it comes before the first ring or right after the first ring.
  >Some of the original display units rectified and stored ring voltage
  >for power so it may need the ring first to power the display box then
  >the data.
  >
  >In any event, you can hear it if you have a butt sett with line 
monitor
  >mode.
  >Bell 202 is correct.
  >
  >-Original Message- From: Nate Burke
      >Sent: Tuesday, November 7, 2017 1:58 PM
  >To: Animal Farm
  >Subject: [AFMUG] ATA CallerID question
  >
  >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 Lines, and it appears to be hitting
  >the ATA Properly.   Is there a setting on the ATA

Re: [AFMUG] ATA CallerID question

[Steve Jones]

Out of curiousity, i learn this nonsense from folks in the know. Where do
folks in the know learn this shit? Is it that they were involved in the day
when people in the service industry knew what they were doing, or prior to
mailing lists was there some analog solution center? Like did you old folks
hang out near your telegraph listening to everybodies conversations? Does
it boil down to some old chinese guy sending out coded messages or what?
Was at a customers joint the other day, an issue with ms rdp, end of the
day, it boiled down to remote connectivity, had to disable a tertiary
networks gpo printer and disable bitmap caching. I got this from google.
Seperate threads and a brain connection that this was the second remote
joint via vpn, and the two remote joints couldnt communicate.
Customer noted the google use, i told him its cause we dont have manuals
now.
Is the truth that some chinese guy just answers all our google queries now
and we are just corporate puppets?

Is there only one really old rice eating fellow that actually knows the
answers? What if he dies?
Are we fucked if the chinaman dies?

On Nov 9, 2017 4:46 PM, "Forrest Christian (List Account)" <
li...@packetflux.com> wrote:

If you have call waiting, you'll often hear the caller id 'data burp' after
the first 'call is waiting' beep...

On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com>
wrote:

> Remember, the signal comes between rings. Unless you are listening on a
> butt set in line or watching the info pass through a switch you wouldn't
> see or hear it. The only reason I remembered between first and second is
> sitting at a class 5 switch trying to figure out why caller ID was failing
> on a feature group D trunk group and seeing them come through after one
> ringy dingy.
>
> On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>
>> Is it at an inaudible frequency?  If so, then it wouldn't make it through
>> 2600hz bandpass filters would it?  Or maybe it's audible, but so short you
>> don't notice it? I'm fuzzy on this.
>>
>> I probably shouldn't ask.  I don't need to know that much about POTS
>> anymore.
>>
>>
>> -- Original Message --
>> From: "Lewis Bergman" <lewis.berg...@gmail.com>
>> To: af@afmug.com
>> Sent: 11/9/2017 4:40:57 PM
>> Subject: Re: [AFMUG] ATA CallerID question
>>
>> More info than anyone probably wants to know. I found this about the
>> original question:
>> Caller-ID Signaling
>>
>> According to Telcordia specifications, CND signaling starts as early as
>> 300 mS after the first ring burst and ends at least 475 mS before the
>> second ring burst
>>
>> From here: http://www.tech-faq.com/caller-id.html
>>
>> On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>>
>> I did not know that tone contained modulated data.  I just thought it
>>> was a noise you wouldn't ignore.
>>>
>>> That's a fun fact to have.
>>>
>>>
>>> -- Original Message --
>>> From: ch...@wbmfg.com
>>> To: af@afmug.com
>>> Sent: 11/7/2017 4:39:27 PM
>>> Subject: Re: [AFMUG] ATA CallerID question
>>>
>>> >Monitor the line for the data burst.  It is the exact same modulation
>>> >method as the emergency alert system you hear squawking on the TV
>>> >before the beep and thunderstorm warning.
>>> >
>>> >I think it comes before the first ring or right after the first ring.
>>> >Some of the original display units rectified and stored ring voltage
>>> >for power so it may need the ring first to power the display box then
>>> >the data.
>>> >
>>> >In any event, you can hear it if you have a butt sett with line monitor
>>> >mode.
>>> >Bell 202 is correct.
>>> >
>>> >-Original Message- From: Nate Burke
>>> >Sent: Tuesday, November 7, 2017 1:58 PM
>>> >To: Animal Farm
>>> >Subject: [AFMUG] ATA CallerID question
>>> >
>>> >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 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
>>>
>>>


-- 
*Forrest Christian* *CEO**, PacketFlux Technologies, Inc.*
Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602
<https://maps.google.com/?q=3577+Countryside+Road,+Helena,+MT+59602=gmail=g>
forre...@imach.com | http://www.packetflux.com
<http://www.linkedin.com/in/fwchristian>  <http://facebook.com/packetflux>
<http://twitter.com/@packetflux>

Re: [AFMUG] ATA CallerID question

[Forrest Christian (List Account)]

If you have call waiting, you'll often hear the caller id 'data burp' after
the first 'call is waiting' beep...

On Thu, Nov 9, 2017 at 2:52 PM, Lewis Bergman <lewis.berg...@gmail.com>
wrote:

> Remember, the signal comes between rings. Unless you are listening on a
> butt set in line or watching the info pass through a switch you wouldn't
> see or hear it. The only reason I remembered between first and second is
> sitting at a class 5 switch trying to figure out why caller ID was failing
> on a feature group D trunk group and seeing them come through after one
> ringy dingy.
>
> On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>
>> Is it at an inaudible frequency?  If so, then it wouldn't make it through
>> 2600hz bandpass filters would it?  Or maybe it's audible, but so short you
>> don't notice it? I'm fuzzy on this.
>>
>> I probably shouldn't ask.  I don't need to know that much about POTS
>> anymore.
>>
>>
>> -- Original Message --
>> From: "Lewis Bergman" <lewis.berg...@gmail.com>
>> To: af@afmug.com
>> Sent: 11/9/2017 4:40:57 PM
>> Subject: Re: [AFMUG] ATA CallerID question
>>
>> More info than anyone probably wants to know. I found this about the
>> original question:
>> Caller-ID Signaling
>>
>> According to Telcordia specifications, CND signaling starts as early as
>> 300 mS after the first ring burst and ends at least 475 mS before the
>> second ring burst
>>
>> From here: http://www.tech-faq.com/caller-id.html
>>
>> On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>>
>> I did not know that tone contained modulated data.  I just thought it
>>> was a noise you wouldn't ignore.
>>>
>>> That's a fun fact to have.
>>>
>>>
>>> -- Original Message --
>>> From: ch...@wbmfg.com
>>> To: af@afmug.com
>>> Sent: 11/7/2017 4:39:27 PM
>>> Subject: Re: [AFMUG] ATA CallerID question
>>>
>>> >Monitor the line for the data burst.  It is the exact same modulation
>>> >method as the emergency alert system you hear squawking on the TV
>>> >before the beep and thunderstorm warning.
>>> >
>>> >I think it comes before the first ring or right after the first ring.
>>> >Some of the original display units rectified and stored ring voltage
>>> >for power so it may need the ring first to power the display box then
>>> >the data.
>>> >
>>> >In any event, you can hear it if you have a butt sett with line monitor
>>> >mode.
>>> >Bell 202 is correct.
>>> >
>>> >-Original Message- From: Nate Burke
>>> >Sent: Tuesday, November 7, 2017 1:58 PM
>>> >To: Animal Farm
>>> >Subject: [AFMUG] ATA CallerID question
>>> >
>>> >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 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
>>>
>>>


-- 
*Forrest Christian* *CEO**, PacketFlux Technologies, Inc.*
Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602
forre...@imach.com | http://www.packetflux.com
<http://www.linkedin.com/in/fwchristian>  <http://facebook.com/packetflux>
<http://twitter.com/@packetflux>

Re: [AFMUG] ATA CallerID question

[chuck]

1200 and 2200 hz I think (bell 202 FSK).  You can certainly hear it.  It is the 
same as the data burst during the emergency broadcast system.  EAS system.  
Very annoying.  

Ring frequency is normally 20 Hz 90 VAC.  You can hear it but it is more of 
sensation to your ear that you feel than hear.  
You can certainly feel it if you put your fingers across the line.  

From: Adam Moffett 
Sent: Thursday, November 9, 2017 2:46 PM
To: af@afmug.com 
Subject: Re: [AFMUG] ATA CallerID question

Is it at an inaudible frequency?  If so, then it wouldn't make it through 
2600hz bandpass filters would it?  Or maybe it's audible, but so short you 
don't notice it? I'm fuzzy on this.

I probably shouldn't ask.  I don't need to know that much about POTS anymore.


-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
Sent: 11/9/2017 4:40:57 PM
Subject: Re: [AFMUG] ATA CallerID question

  More info than anyone probably wants to know. I found this about the original 
question: 
  Caller-ID Signaling
  According to Telcordia specifications, CND signaling starts as early as 300 
mS after the first ring burst and ends at least 475 mS before the second ring 
burst

  From here: http://www.tech-faq.com/caller-id.html


  On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> wrote:

I did not know that tone contained modulated data.  I just thought it
was a noise you wouldn't ignore.

That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com
To: af@afmug.com
Sent: 11/7/2017 4:39:27 PM
    Subject: Re: [AFMUG] ATA CallerID question

>Monitor the line for the data burst.  It is the exact same modulation
>method as the emergency alert system you hear squawking on the TV
>before the beep and thunderstorm warning.
>
>I think it comes before the first ring or right after the first ring.
>Some of the original display units rectified and stored ring voltage
>for power so it may need the ring first to power the display box then
>the data.
>
>In any event, you can hear it if you have a butt sett with line monitor
>mode.
>Bell 202 is correct.
>
>-Original Message- From: Nate Burke
>Sent: Tuesday, November 7, 2017 1:58 PM
>To: Animal Farm
>Subject: [AFMUG] ATA CallerID question
>
>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 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

Re: [AFMUG] ATA CallerID question

[Adam Moffett]

Oh rightI haven't picked up the phone yet so there's nothing to 
hear.
Sorry.  I haven't actually used one of these telephone thingys in a long 
time.



-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
Sent: 11/9/2017 4:52:46 PM
Subject: Re: [AFMUG] ATA CallerID question

Remember, the signal comes between rings. Unless you are listening on a 
butt set in line or watching the info pass through a switch you 
wouldn't see or hear it. The only reason I remembered between first and 
second is sitting at a class 5 switch trying to figure out why caller 
ID was failing on a feature group D trunk group and seeing them come 
through after one ringy dingy.


On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:
Is it at an inaudible frequency?  If so, then it wouldn't make it 
through 2600hz bandpass filters would it?  Or maybe it's audible, but 
so short you don't notice it? I'm fuzzy on this.


I probably shouldn't ask.  I don't need to know that much about POTS 
anymore.



-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
Sent: 11/9/2017 4:40:57 PM
Subject: Re: [AFMUG] ATA CallerID question

More info than anyone probably wants to know. I found this about the 
original question:

Caller-ID Signaling
According to Telcordia specifications, CND signaling starts as early 
as 300 mS after the first ring burst and ends at least 475 mS before 
the second ring burst


From here: http://www.tech-faq.com/caller-id.html


On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:
I did not know that tone contained modulated data.  I just thought 
it

was a noise you wouldn't ignore.

That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com
To: af@afmug.com
Sent: 11/7/2017 4:39:27 PM
Subject: Re: [AFMUG] ATA CallerID question

>Monitor the line for the data burst.  It is the exact same 
modulation

>method as the emergency alert system you hear squawking on the TV
>before the beep and thunderstorm warning.
>
>I think it comes before the first ring or right after the first 
ring.
>Some of the original display units rectified and stored ring 
voltage
>for power so it may need the ring first to power the display box 
then

>the data.
>
>In any event, you can hear it if you have a butt sett with line 
monitor

>mode.
>Bell 202 is correct.
>
>-Original Message- From: Nate Burke
>Sent: Tuesday, November 7, 2017 1:58 PM
>To: Animal Farm
>Subject: [AFMUG] ATA CallerID question
>
>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 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

Re: [AFMUG] ATA CallerID question

[Lewis Bergman]

Remember, the signal comes between rings. Unless you are listening on a
butt set in line or watching the info pass through a switch you wouldn't
see or hear it. The only reason I remembered between first and second is
sitting at a class 5 switch trying to figure out why caller ID was failing
on a feature group D trunk group and seeing them come through after one
ringy dingy.

On Thu, Nov 9, 2017 at 3:46 PM Adam Moffett <dmmoff...@gmail.com> wrote:

> Is it at an inaudible frequency?  If so, then it wouldn't make it through
> 2600hz bandpass filters would it?  Or maybe it's audible, but so short you
> don't notice it? I'm fuzzy on this.
>
> I probably shouldn't ask.  I don't need to know that much about POTS
> anymore.
>
>
> -- Original Message --
> From: "Lewis Bergman" <lewis.berg...@gmail.com>
> To: af@afmug.com
> Sent: 11/9/2017 4:40:57 PM
> Subject: Re: [AFMUG] ATA CallerID question
>
> More info than anyone probably wants to know. I found this about the
> original question:
> Caller-ID Signaling
>
> According to Telcordia specifications, CND signaling starts as early as
> 300 mS after the first ring burst and ends at least 475 mS before the
> second ring burst
>
> From here: http://www.tech-faq.com/caller-id.html
>
> On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> wrote:
>
> I did not know that tone contained modulated data.  I just thought it
>> was a noise you wouldn't ignore.
>>
>> That's a fun fact to have.
>>
>>
>> -- Original Message --
>> From: ch...@wbmfg.com
>> To: af@afmug.com
>> Sent: 11/7/2017 4:39:27 PM
>> Subject: Re: [AFMUG] ATA CallerID question
>>
>> >Monitor the line for the data burst.  It is the exact same modulation
>> >method as the emergency alert system you hear squawking on the TV
>> >before the beep and thunderstorm warning.
>> >
>> >I think it comes before the first ring or right after the first ring.
>> >Some of the original display units rectified and stored ring voltage
>> >for power so it may need the ring first to power the display box then
>> >the data.
>> >
>> >In any event, you can hear it if you have a butt sett with line monitor
>> >mode.
>> >Bell 202 is correct.
>> >
>> >-Original Message- From: Nate Burke
>> >Sent: Tuesday, November 7, 2017 1:58 PM
>> >To: Animal Farm
>> >Subject: [AFMUG] ATA CallerID question
>> >
>> >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 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
>>
>>

Re: [AFMUG] ATA CallerID question

[Adam Moffett]

Is it at an inaudible frequency?  If so, then it wouldn't make it 
through 2600hz bandpass filters would it?  Or maybe it's audible, but so 
short you don't notice it? I'm fuzzy on this.


I probably shouldn't ask.  I don't need to know that much about POTS 
anymore.



-- Original Message --
From: "Lewis Bergman" <lewis.berg...@gmail.com>
To: af@afmug.com
Sent: 11/9/2017 4:40:57 PM
Subject: Re: [AFMUG] ATA CallerID question

More info than anyone probably wants to know. I found this about the 
original question:

Caller-ID Signaling
According to Telcordia specifications, CND signaling starts as early as 
300 mS after the first ring burst and ends at least 475 mS before the 
second ring burst


From here: http://www.tech-faq.com/caller-id.html


On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> 
wrote:

I did not know that tone contained modulated data.  I just thought it
was a noise you wouldn't ignore.

That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com
To: af@afmug.com
Sent: 11/7/2017 4:39:27 PM
Subject: Re: [AFMUG] ATA CallerID question

>Monitor the line for the data burst.  It is the exact same modulation
>method as the emergency alert system you hear squawking on the TV
>before the beep and thunderstorm warning.
>
>I think it comes before the first ring or right after the first ring.
>Some of the original display units rectified and stored ring voltage
>for power so it may need the ring first to power the display box then
>the data.
>
>In any event, you can hear it if you have a butt sett with line 
monitor

>mode.
>Bell 202 is correct.
>
>-Original Message- From: Nate Burke
>Sent: Tuesday, November 7, 2017 1:58 PM
>To: Animal Farm
>Subject: [AFMUG] ATA CallerID question
>
>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 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

Re: [AFMUG] ATA CallerID question

[Lewis Bergman]

More info than anyone probably wants to know. I found this about the
original question:
Caller-ID Signaling

According to Telcordia specifications, CND signaling starts as early as 300
mS after the first ring burst and ends at least 475 mS before the second
ring burst

>From here: http://www.tech-faq.com/caller-id.html

On Tue, Nov 7, 2017 at 9:29 PM Adam Moffett <dmmoff...@gmail.com> wrote:

> I did not know that tone contained modulated data.  I just thought it
> was a noise you wouldn't ignore.
>
> That's a fun fact to have.
>
>
> -- Original Message --
> From: ch...@wbmfg.com
> To: af@afmug.com
> Sent: 11/7/2017 4:39:27 PM
> Subject: Re: [AFMUG] ATA CallerID question
>
> >Monitor the line for the data burst.  It is the exact same modulation
> >method as the emergency alert system you hear squawking on the TV
> >before the beep and thunderstorm warning.
> >
> >I think it comes before the first ring or right after the first ring.
> >Some of the original display units rectified and stored ring voltage
> >for power so it may need the ring first to power the display box then
> >the data.
> >
> >In any event, you can hear it if you have a butt sett with line monitor
> >mode.
> >Bell 202 is correct.
> >
> >-Original Message- From: Nate Burke
> >Sent: Tuesday, November 7, 2017 1:58 PM
> >To: Animal Farm
> >Subject: [AFMUG] ATA CallerID question
> >
> >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 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
>
>

Re: [AFMUG] ATA CallerID question

[Adam Moffett]

I did not know that tone contained modulated data.  I just thought it 
was a noise you wouldn't ignore.


That's a fun fact to have.


-- Original Message --
From: ch...@wbmfg.com
To: af@afmug.com
Sent: 11/7/2017 4:39:27 PM
Subject: Re: [AFMUG] ATA CallerID question

Monitor the line for the data burst.  It is the exact same modulation 
method as the emergency alert system you hear squawking on the TV 
before the beep and thunderstorm warning.


I think it comes before the first ring or right after the first ring.  
Some of the original display units rectified and stored ring voltage 
for power so it may need the ring first to power the display box then 
the data.


In any event, you can hear it if you have a butt sett with line monitor 
mode.

Bell 202 is correct.

-Original Message- From: Nate Burke
Sent: Tuesday, November 7, 2017 1:58 PM
To: Animal Farm
Subject: [AFMUG] ATA CallerID question

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 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

Re: [AFMUG] ATA CallerID question

[chuck]

Some ATAs don’t put out 48 volts.  That could be a thing.  

From: Nate Burke 
Sent: Tuesday, November 7, 2017 3:13 PM
To: af@afmug.com 
Subject: Re: [AFMUG] ATA CallerID question

Is there any chance it could be a polarity problem?  If somewhere between the 
ATA and the PBX the 2 wires are reversed?


On 11/7/2017 3:42 PM, Lewis Bergman wrote:

  I seem to remember it comes in between the first and second ring.

  On Tue, Nov 7, 2017 at 3:39 PM <ch...@wbmfg.com> wrote:

Monitor the line for the data burst.  It is the exact same modulation method
as the emergency alert system you hear squawking on the TV before the beep
and thunderstorm warning.

I think it comes before the first ring or right after the first ring.  Some
of the original display units rectified and stored ring voltage for power so
it may need the ring first to power the display box then the data.

In any event, you can hear it if you have a butt sett with line monitor
mode.
Bell 202 is correct.

-Original Message-
From: Nate Burke
Sent: Tuesday, November 7, 2017 1:58 PM
To: Animal Farm
Subject: [AFMUG] ATA CallerID question

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 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

Re: [AFMUG] ATA CallerID question

[Nate Burke]

Is there any chance it could be a polarity problem?  If somewhere 
between the ATA and the PBX the 2 wires are reversed?


On 11/7/2017 3:42 PM, Lewis Bergman wrote:

I seem to remember it comes in between the first and second ring.

On Tue, Nov 7, 2017 at 3:39 PM <ch...@wbmfg.com 
<mailto:ch...@wbmfg.com>> wrote:


Monitor the line for the data burst.  It is the exact same
modulation method
as the emergency alert system you hear squawking on the TV before
the beep
and thunderstorm warning.

I think it comes before the first ring or right after the first
ring.  Some
of the original display units rectified and stored ring voltage
for power so
it may need the ring first to power the display box then the data.

In any event, you can hear it if you have a butt sett with line
monitor
mode.
Bell 202 is correct.

-Original Message-
From: Nate Burke
Sent: Tuesday, November 7, 2017 1:58 PM
To: Animal Farm
    Subject: [AFMUG] ATA CallerID question

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 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

Re: [AFMUG] ATA CallerID question

[Lewis Bergman]

I seem to remember it comes in between the first and second ring.

On Tue, Nov 7, 2017 at 3:39 PM <ch...@wbmfg.com> wrote:

> Monitor the line for the data burst.  It is the exact same modulation
> method
> as the emergency alert system you hear squawking on the TV before the beep
> and thunderstorm warning.
>
> I think it comes before the first ring or right after the first ring.  Some
> of the original display units rectified and stored ring voltage for power
> so
> it may need the ring first to power the display box then the data.
>
> In any event, you can hear it if you have a butt sett with line monitor
> mode.
> Bell 202 is correct.
>
> -Original Message-
> From: Nate Burke
> Sent: Tuesday, November 7, 2017 1:58 PM
> To: Animal Farm
> Subject: [AFMUG] ATA CallerID question
>
> 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 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
>
>

Re: [AFMUG] ATA CallerID question

[chuck]

Monitor the line for the data burst.  It is the exact same modulation method 
as the emergency alert system you hear squawking on the TV before the beep 
and thunderstorm warning.


I think it comes before the first ring or right after the first ring.  Some 
of the original display units rectified and stored ring voltage for power so 
it may need the ring first to power the display box then the data.


In any event, you can hear it if you have a butt sett with line monitor 
mode.

Bell 202 is correct.

-Original Message- 
From: Nate Burke

Sent: Tuesday, November 7, 2017 1:58 PM
To: Animal Farm
Subject: [AFMUG] ATA CallerID question

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 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 

Re: [AFMUG] ATA CallerID question

[Adam Moffett]

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 
listeningor 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 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

Re: [AFMUG] ATA CallerID question

[Adam Moffett]

I think he means incoming.  Maybe try a different ATA.  I'm positive I 
had one or two that failed in some way that they wouldn't the send the 
caller ID data anymore.  Those were Motorola.not sure it ever 
happened to us on a Cisco.



-- Original Message --
From: "can...@believewireless.net" <p...@believewireless.net>
To: "af@afmug.com" <af@afmug.com>
Sent: 11/7/2017 4:16:39 PM
Subject: Re: [AFMUG] ATA CallerID question


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 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

Re: [AFMUG] ATA CallerID question

[Steve Jones]

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  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 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
>>
>
>

Re: [AFMUG] ATA CallerID question

[Nate Burke]

It's the inbound caller ID (the customer is receiving a call), not the 
Outbound Caller ID.


On 11/7/2017 3:16 PM, can...@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 > 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 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

Re: [AFMUG] ATA CallerID question

[can...@believewireless.net]

The outbound CID should be set in the PBX, not the ATA.

On Tue, Nov 7, 2017 at 3:58 PM, Nate Burke  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 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
>

[AFMUG] ATA CallerID question

[Nate Burke]

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 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