Windows keeps a log of modem communications.  This can be helpful in determining why Ascendis Caller ID does not report caller information.

 

The easy way to view the modem log is in the Modem Log Window using the Modem Logs menu item on the Diagnostics menu on the Help menu.  This should be available in versions of Ascendis Caller ID greater than or equal to 1.6.2.0.  Otherwise you can view the modem log through the appropriate control panel.

 

The first part of the modem log contains modem driver information.  The modem driver files are listed as "File:" entries:

06-11-2003 22:18:19.797 - File: C:\WINDOWS\System32\tapisrv.dll, Version 5.1.2600  

06-11-2003 22:18:19.797 - File: C:\WINDOWS\System32\unimdm.tsp, Version 5.1.2600  

06-11-2003 22:18:19.797 - File: C:\WINDOWS\System32\unimdmat.dll, Version 5.1.2600  

06-11-2003 22:18:19.797 - File: C:\WINDOWS\System32\uniplat.dll, Version 5.1.2600  

06-11-2003 22:18:19.812 - File: C:\WINDOWS\System32\drivers\modem.sys, Version 5.1.2600  

06-11-2003 22:18:19.812 - File: C:\WINDOWS\System32\modemui.dll, Version 5.1.2600  

06-11-2003 22:18:19.828 - File: C:\WINDOWS\System32\mdminst.dll, Version 5.1.2600  

These can usually be ignored.

 

The second part contains modem type information:

06-11-2003 22:18:19.828 - Modem type: Conexant HSF V92 56K Data Fax PCI Modem

06-11-2003 22:18:19.828 - Modem inf path: oem22.inf

06-11-2003 22:18:19.828 - Modem inf section: ModemX

06-11-2003 22:18:19.828 - Matching hardware ID: pci\ven_14f1&dev_2013&subsys_021213e0

The "Modem inf path" line shows the name of the modem's INF file.  This file can be found in Windows' INF folder, which is usually C:\Windows\Inf.

The "Modem inf section" line shows the specific modem section in the inf file that Windows uses.  (INF files can define many models from the same manufacturer.)  This key and the INF file can be used to learn which features are enabled for the modem.  Unless you know how to read INF files, this can be tricky, but the information is there.

 

The next line shows the communication parameters:

06-11-2003 22:18:20.297 - 115200,8,N,1, ctsfl=1, rtsctl=2

 

The next section shows the modem initialization sequence:

06-11-2003 22:18:20.297 - Initializing modem.

06-11-2003 22:18:20.312 - Send: AT<cr>

06-11-2003 22:18:20.312 - Recv: <cr><lf>OK<cr><lf>

06-11-2003 22:18:20.312 - Interpreted response: OK

06-11-2003 22:18:20.328 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>

06-11-2003 22:18:20.547 - Recv: <cr><lf>OK<cr><lf>

06-11-2003 22:18:20.547 - Interpreted response: OK

06-11-2003 22:18:20.562 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>

06-11-2003 22:18:20.578 - Recv: <cr><lf>OK<cr><lf>

06-11-2003 22:18:20.578 - Interpreted response: OK

06-11-2003 22:18:20.578 - Waiting for a call.

06-11-2003 22:18:20.594 - Send: at+vcid=1<cr>

06-11-2003 22:18:20.609 - Recv: <cr><lf>OK<cr><lf>

06-11-2003 22:18:20.609 - Interpreted response: OK

06-11-2003 22:18:20.625 - Send: ATS0=0<cr>

06-11-2003 22:18:20.640 - Recv: <cr><lf>OK<cr><lf>

06-11-2003 22:18:20.640 - Interpreted response: OK

You can see the specific commands sent to the modem to initialize it.  You can see in this example that caller id is enabled by sending the "+vcid=1" command.  The modem responds "OK" after each command.  You should also note that Windows, after receiving "OK" embedded within some carriage-return + linefeed sequences, interprets this as "OK" ("Interpreted response: OK").

 

If you don't see a command to enable caller id on your modem, you can add it manually in the modem control panel.  Detailed instructions are available here.  Of course, if Windows isn't already enabling caller id on your modem, it could indicate a problem with the INF file which cannot be fixed so easily.  In that case, continue reading.

 

Finally, we have a call coming in:

06-12-2003 11:35:02.044 - Recv: <cr><lf>RING<cr><lf>

06-12-2003 11:35:02.044 - Interpreted response: Ring

06-12-2003 11:35:02.950 - Recv: <cr><lf>RING<cr><lf>

06-12-2003 11:35:02.950 - Interpreted response: Ring

06-12-2003 11:35:03.497 - Recv: <cr><lf>RING<cr><lf>

06-12-2003 11:35:03.497 - Interpreted response: Ring

06-12-2003 11:35:04.700 - Recv: <cr><lf>DATE =

06-12-2003 11:35:04.700 - Interpreted response: DATE

06-12-2003 11:35:04.700 - Recv: 0612<cr><lf>

06-12-2003 11:35:04.700 - Recv: TIME =

06-12-2003 11:35:04.700 - Interpreted response: TIME

06-12-2003 11:35:04.700 - Recv: 1134<cr><lf>

06-12-2003 11:35:04.700 - Recv: NAME =

06-12-2003 11:35:04.700 - Interpreted response: NAME

06-12-2003 11:35:04.700 - Recv: B G S U<cr><lf>

06-12-2003 11:35:04.700 - Recv: NMBR =

06-12-2003 11:35:04.700 - Interpreted response: NMBR

06-12-2003 11:35:04.700 - Recv: 5558327569<cr><lf>

06-12-2003 11:35:07.934 - Recv: <cr><lf>RING<cr><lf>

06-12-2003 11:35:07.934 - Interpreted response: Ring

06-12-2003 11:35:08.731 - Recv: <cr><lf>RING<cr><lf>

06-12-2003 11:35:08.731 - Interpreted response: Ring

The modem sends a "RING" message when the phone rings.  Caller id information is sent by the phone company between the first and second ring, but the modem used in this example is a little unusual, and reports three rings before the caller information.  At any rate, we can see that Windows interprets the caller information correctly.

 

Sometimes the modem reports the caller information, as it does above, but Windows doesn't interpret it correctly.  In such a case, you might see something like the following:

04-08-2003 13:29:44.182 - Recv: TIME=1

04-08-2003 13:29:44.182 - Interpreted response: DATE

04-08-2003 13:29:44.222 - Recv: 32

04-08-2003 13:29:44.222 - Unknown Response

04-08-2003 13:29:44.222 - Recv: 6<cr><lf>NMBR=560

04-08-2003 13:29:44.222 - Unknown Response

04-08-2003 13:29:44.262 - Recv: 3

04-08-2003 13:29:44.262 - Unknown Response

04-08-2003 13:29:44.262 - Recv: 62

04-08-2003 13:29:44.262 - Unknown Response

04-08-2003 13:29:44.302 - Recv: 5

04-08-2003 13:29:44.302 - Unknown Response

04-08-2003 13:29:44.302 - Recv: 468<cr><lf>NAME=

04-08-2003 13:29:44.302 - Unknown Response

04-08-2003 13:29:44.342 - Recv: S

04-08-2003 13:29:44.342 - Unknown Response

04-08-2003 13:29:44.342 - Recv: O D

04-08-2003 13:29:44.342 - Unknown Response

04-08-2003 13:29:44.462 - Recv: A

04-08-2003 13:29:44.462 - Unknown Response

04-08-2003 13:29:44.462 - Recv: KOTA ST OF<cr><lf>

04-08-2003 13:29:44.462 - Unknown Response

04-08-2003 13:29:48.658 - Recv: <cr><lf>RING<cr><lf>

04-08-2003 13:29:48.658 - Interpreted response: Ring

This indicates the modem's INF file is incorrect.  It is either missing the section of caller id responses, or they are incorrect.  This is actually fairly common.  In this case, you should first download the latest modem drivers from the manufacturers web site and follow their directions for re-installing the modem or updating the drivers.  If this does not solve the problem, you may be able to fix the INF file manually, or fix the corresponding entries in the registry.  The safest route is to get the current responses using the Modem Responses window, and follow the directions for fixing the responses.

 

In the unlikely event that your modem is reporting the caller information correctly and Windows is interpreting it correctly but Ascendis Caller ID still does not report the caller information, try enabling line monitoring within Caller ID.