ACS R7 Caller ID Issue

[idoelectronics]

I have a strange one. We have 5 lines coming into a new building - about 100 ft of 25 pair cable to the telecom room and terminated on a 66 block.

New ACS R7 processor - one the main line - CID data is showing up on the phones about 10% of the time. All other lines display CID data accurately.

We setup a cheap CID reader on the main line for a few hours and EVERY call was picked up correctly so the CID data is coming in on the line properly.

We tried an ACS R6 processor as a test to see if the ACS R7 was defective and it happened on the R6 also???? Is there a possibility that this main line has a voltage or Ma problem that is not sending the data through in a format or manner that the ACS processors can't read it?

SBC tested the line all the way back to the CO and a pedistal and said the CID data is coming through ok?

I have never run into this before, but it is now a major problem.

Any ideas?

 

[FordMan77]

How quickly does someone answer the call when it rings in on this line?

Jay

 

[Telecomboy]

To expand on FordMan77: It takes 2-rings usually for caller ID info to be passed. Is the AA or a person answering before that?

 

[TouchToneTommy]

Swap Line 1 and Line 2 on the control unit, see if the problem is associated with the particular dial tone, or the particular line port.

 

[1043]

Is your dialtone being provided via channelbank or a 3rd party vendor? There are known problems with certain providers in our area where the caller ID isn't working like you discribe. It is usally an Adran channelbank. We have 2 3rd party providers using the ADTRAN equipment. Each using diferent models, one works one doesn't. I have another provider (Fibernet) who will not charge my customer for caller ID because they know it won't work with Avaya switches.

 

[idoelectronics]

Have done those basic checks before - always wait 2 rings for CID info to show up.

Have swapped line 1 & 2 and the CID issue follows the line.

Basically have checked everything that is obvious and then some but the problem still persists. Again - CID info is passing through about 10% of the time and some of those calls always show up from a few customers lines which is very odd - other CID info that makes it though on line one is just random.

That is why I think it might be a voltage issue on the line and the ACS can't read/strip it from the call consistently.

 

[aarenot]

A few tips.
Assuming all 5 lines are in the Telco hunt group, and line one is their published number? Set line one as the first to be accessed for outgoing calls via auto line selection. If there is one caller on an outgoing call, you wont have this issue at that time. Short term partial solution, which may win you some favor.
If it is not the published number, for intance, it is an 800 number which is published, remove line from the telco hunt group. You can always add a lime, change its order in the hunt group, and keep or remove this line from service.
I assume you have deleted and recreated ALL programming for the line, including CLID settings, defaulted the Partner programmimg and restored(both from back up first, and by hand), replaced the ground source( strange what issues this can fix). Other than that eliminate one component at a time to see if something is causing a system wide issue, I have seen this happen more than a few times.
It does not sound like a telco issue since the CLID works on a seperate CLID unit. Unless that seperate CLID unit has a wider range of capability than the standards for CLID. The CLID info. is not unproccessable, it is just not proccessable by the ACS.
You could try the R6 at he dmarc to see if it has issue there.
Sounds like an issue for Avaya support. If it works on a seperate CLID unit, it should work on the ACS.



You do not always get what you pay for, but you never get what you do not pay for.

 

[idoelectronics]

The LEC is SBC and the CID info is stripped accurately on the other 4 CO Lines so that isn't the problem.

I think we will try an ACS R6 at the DEMARC to see if we can repeat it there before our 25 pair 90' cable run to the telco room.

Thanks all.

 

[aarenot]

You could try swapping the lines at the dmarc, instead of at the system. That would swap the path on the 25 pair.
I might also check for an alarm, modem, etc., they may cause some issue.


You do not always get what you pay for, but you never get what you do not pay for.

 

[idoelectronics]

Found a fix DSL filter. Excelsus Technologies model Z-200SM worked Z330TJA didn’t work both from Excelsus Technologies. Excelsus Technologies

http://www.excelsus-tech.com

800-457-0967