|
|
|
|
Joined: Feb 2005
Posts: 30
Member
|
|
Member
Joined: Feb 2005
Posts: 30 |
We have one customer with the IWATSU ECS system and cannot get caller ID to work on a POTS line. We have an IX-408 combo card which is supposed to support CID. We have verified that CID is coming from the telephone company and can't figure out how to get it working. We are connected and programming with the software.
Last edited by KJPMaine; 04/07/15 03:42 PM.
|
|
|
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: Jun 2006
Posts: 1,624
Member
|
|
Member
Joined: Jun 2006
Posts: 1,624 |
In hardware, do you have the definition of the trunks set to "Enhanced CO"? Also, in Voice Mail Integration you may need to update your Trunk ID Packet.
"I'm the one that has to die when it's time for me to die, so let me live my life, the way I want to."
-- Jimi Hendrix
|
|
|
|
|
Joined: Mar 2006
Posts: 46
Member
|
|
Member
Joined: Mar 2006
Posts: 46 |
I bet Keighlar is correct regarding 'Enhanced CO', but you might also check the Display CID/ANI/Name/Number settings under 'System Features'. (Or for you old-school folks {like me} Class 04.71.45). Make sure you have the correct item(s) showing to display on incoming calls.
|
|
|
|
|
Joined: Feb 2005
Posts: 30
Member
|
|
Member
Joined: Feb 2005
Posts: 30 |
Thank you. As soon as the tech came back to the office I looked at the software and found the enhanced CO option you spoke of. It's working, thanks very much.
|
|
|
|
|
Joined: Jun 2006
Posts: 1,624
Member
|
|
Member
Joined: Jun 2006
Posts: 1,624 |
"I'm the one that has to die when it's time for me to die, so let me live my life, the way I want to."
-- Jimi Hendrix
|
|
|
|
Forums84
Topics94,492
Posts639,865
Members49,836
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
|
|
