To use the Caller ID Integration feature in Camelot 3.0, you need a modem in your computer, a phone line connected directly to the line port on that modem, and then your phone handset gets connected to the phone port on that modem.
- OR -
Camelot3 software can now intergrate with the Whozz Calling POS Etherlink caller id hardware devices available from http://www.callerid.com. Their Etherlink POS device takes your incoming phone lines which you can then route on to whatever phone system you are using, and then the device plugs into your Ethernet switch, hub, or router. All incoming caller id messages are then broadcast to all the computers on your local network. This is a great solution if you have more than 1 phone line and more than 1 computer and you have a phone system that currently handles your calls that may or may not have its own Microsoft TAPI interface. This hardware eliminates that need.
If you have a modem that is Microsoft TAPI compliant and only need to implement the Caller ID interface for 1 incoming line on 1 computer, then you should be able to implement the caller id popup feature without the aforementioned hardware, BUT WE CANNOT GUARANTEE THIS. Unfortunately not all modems have a valid Microsoft TAPI Caller ID interface, and even some that claim that they do don't actually work. So if you follow the steps here for trying to get your particular modem to work with caller id and Camelot3, and you do not have success, your ONLY solution is to purchase a device from http://www.callerid.com.
So, if you would like to try to use the modem you have already in your computer, then on the Misc/Setup > Company/Misc Info screen, go to the CallerID Integration tab, and choose your modem device in the Device Number drop-down box there, and the other settings (which wouldn't normally need to be changed) by default should be set to Media Mode=mmData and Line Privilege=lpOwner. Also, be sure that the Whozz Calling Port is set to "none" for this implementation with your modem device.
Then you can click Init Modem to see that the software does successfully connect to your modem device, and then do a test call by making sure you have a contact entry with a certain phone number (including area code), and then call your number from that phone (usually a cell phone would be used for this test).
You may end up needing to try different settings here to get it to work with your particular modem/computer/phone system setup. This means that there could be either a different Device you must choose other than the first one in the list, or you may need to try mmVoice as the Media Mode or lpMonitor as the Line Privelege mode. If you are having problems getting the caller id to be recognized by the software, you should try each combination of these options (e.g. mmData and lpOwner, mmData and lpMonitor, mmVoice and lpOwner, and mmVoice and lpMonitor).
There are some other options there on the left of that screen that are pretty self-explanatory on what you want it to do when the Caller ID message comes in.
IMPORTANT: If you are utilizing a phone system (e.g. Nortel) where the phone line going to your actual handset at the computer isn't coming directly from the phone company's trunk line, but is instead first routed through your phone system, then you may need to contact your phone system provider and ask them to provide you with a CTI (Computer Telephony Integration) device that will make that phone line going to the handset be Microsoft TAPI compliant so it can communicate through your computer. Or, as previously mentioned, use a device from http://www.callerid.com instead.
Using TAPI and CallerID on your PC requires at least four things.
* TAPI compliant hardware that is Caller ID capable (virtually all modems support TAPI)
* TAPI compliant Windows application (ours is, using KDTele components)
* Microsoft TAPI software components (automatically included with Win98/ME/2000/XP)
* TSPI component for your TAPI hardware with Caller ID enabled (automatically included with Win98/ME/2000/XP for modems)
The first is a piece of telephony hardware that supports TAPI. This could include MODEMs, serial devices, actual telephones, complex telephone switches, or any other component that supports the TAPI interface.
The second is a Windows application designed to take advantage of TAPI. Our software does this part.
The third are the Microsoft software components (TAPI.DLL and a few others) needed to support TAPI. A key component in this list for MODEM users is Microsoft UniModemV. These components are automatically installed for Windows 98/ME/2000/XP.
The fourth is a software component called the Telephony Service Provider Interface (TSPI). These components, for modem hardware, are automatically installed for Windows 98/ME/2000/XP.
If any of these pieces are missing, TAPI cannot be used. Each of these components may in fact include multiple software modules.
If you cannot get your modem to interface correctly with your phone system or computer modem after following the steps above for any reason, then you should instead look into getting the Whozz Calling POS Etherlink device from http://www.callerid.com as it will work regardless of your phone system, and gives the added bonus of a single incoming call causing the caller id information to popup on all the computers running Camelot3 on your network at once, and can work with multiple incoming phone lines.
callerid caller id modem