|
|
|
|
Joined: Apr 2007
Posts: 21
Member
|
|
Member
Joined: Apr 2007
Posts: 21 |
We have a 9.5" UX5000 Installed with an Intramail, 4 COI, 4 COI DB & a 16 Port Station Card. It is having issues receiving CID. Cell phones always come thru, other calls are sporadic. We can hook up a cheap little CID box and it picks up all the calls. Verizon is the provider so its not some off the wall CLEC. They are also just POTS lines. We have been dealing with NEC and finally they said thats all they can do. The Customer is getting a bit irate and I can't blame them. Any suggestions????? :shrug:
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Nov 2007
Posts: 369
Member
|
|
Member
Joined: Nov 2007
Posts: 369 |
Are the pots lines copper loops or off of a channel bank or multi-line modem?
I had similar issue with NEC DSX.... exactly as you describe above, except the service provider was the cable company using a multi-line modem. After several weeks of back-and-forth, finger pointing, and "it's not my problem", they finally discovered an error in their CID settings.
"I didn't do it, and I won't do it again"
|
|
|
|
|
Joined: Apr 2007
Posts: 21
Member
|
|
Member
Joined: Apr 2007
Posts: 21 |
No the lines are regular old POTS coming in on copper
|
|
|
|
|
Joined: Feb 2008
Posts: 683
Member
|
|
Member
Joined: Feb 2008
Posts: 683 |
I had a similar issue on the Aspire a few years ago that drove me nuts. Caller ID was random. Calls were even being dropped randomly. Like you, I hooked up a caller ID box and that passed all the ID's perfectly. Line voltage was at approx 50v. Check the loop current on the lines. It should be between 25 and 32 ma. per NEC field engineering. My lines were about 50 ma. I ended up padding the lines with 200 ohm resistors and the problem went away.
St Petersburg
|
|
|
|
|
Joined: Nov 2007
Posts: 369
Member
|
|
Member
Joined: Nov 2007
Posts: 369 |
Have you tried adjusting the Caller ID Wait Timer in 20-19-02? By default this value is set for 5 seconds. Try moving it out to about 8 seconds and see if there is a difference.
"I didn't do it, and I won't do it again"
|
|
|
|
|
Joined: Apr 2007
Posts: 21
Member
|
|
Member
Joined: Apr 2007
Posts: 21 |
We did change and play with the setting for the caller id wait time. I will try to get a measurement on the lines.
|
|
|
|
|
Joined: Nov 2006
Posts: 70
Member
|
|
Member
Joined: Nov 2006
Posts: 70 |
I had problems like this also with an Aspire, no caller ID or garbled CID characters. If I remember correctly after logging into WebPro on the Aspire with the manufacturer password we changed 81-01-02 to 46 and it fixed our problem. I can only assume the same fix would work for a UX5000.
"If at first you don't succeed, keep on sucking till you do succeed." - Curly Howard
|
|
|
|
|
Joined: Sep 2004
Posts: 4,220 Likes: 2
Member
|
|
Member
Joined: Sep 2004
Posts: 4,220 Likes: 2 |
|
|
|
|
|
Joined: Apr 2007
Posts: 21
Member
|
|
Member
Joined: Apr 2007
Posts: 21 |
Are you sure its 81-01-02 Loop current detection or 81-01-12 caller id detection???
|
|
|
|
|
Joined: Nov 2006
Posts: 70
Member
|
|
Member
Joined: Nov 2006
Posts: 70 |
It's definitely 81-01-02.
"If at first you don't succeed, keep on sucking till you do succeed." - Curly Howard
|
|
|
|
Forums84
Topics94,514
Posts639,941
Members49,845
| |
Most Online5,661
May 23rd, 2018
|
|
|
1 members (justbill),
131
guests, and
39
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
