theyre getting a custom firmware with a timing adjustment

On Tue, May 3, 2016 at 4:42 PM, Chuck McCown <ch...@wbmfg.com> wrote:

> http://www.epanorama.net/documents/telecom/cid_bellcore.html
>
> *From:* That One Guy /sarcasm <thatoneguyst...@gmail.com>
> *Sent:* Tuesday, May 03, 2016 3:41 PM
> *To:* af@afmug.com
> *Subject:* Re: [AFMUG] PBX not displaying POTs caller ID
>
> I only have a 4.95$ buttset with me, im glad it even shows cid
>
> On Tue, May 3, 2016 at 4:39 PM, Chuck McCown <ch...@wbmfg.com> wrote:
>
>> It is a bell 202 1200 baud burst of data.  If your buttset shows it, it
>> is there.
>>
>> *From:* That One Guy /sarcasm <thatoneguyst...@gmail.com>
>> *Sent:* Tuesday, May 03, 2016 3:38 PM
>> *To:* af@afmug.com
>> *Subject:* [AFMUG] PBX not displaying POTs caller ID
>>
>> we dropped a fortivoice last week, the office at the time didnt have
>> caller ID, it got turned up today
>> I can run the pots lines into an analog handset, it displays fine, so im
>> assuming it is getting there. This is a brand new telco drop outside with a
>> 25 foot interior demarc extension from the telco demarc.
>>
>> Is there any testing or troubleshooting of something like format of the
>> cid? its present on the buttset, so its there. Im incluned to think its the
>> fortivoice, just want to eliminate any variables
>>
>> the CDR shows blank so the system is blind to it for one reason or another
>>
>> --
>> If you only see yourself as part of the team but you don't see your team
>> as part of yourself you have already failed as part of the team.
>>
>
>
>
> --
> If you only see yourself as part of the team but you don't see your team
> as part of yourself you have already failed as part of the team.
>



-- 
If you only see yourself as part of the team but you don't see your team as
part of yourself you have already failed as part of the team.

Reply via email to