Caller Id Doesn't Show In Log

[Guest Glenn Stehr]

I recently lost my hard drive and had to download and install your Interactive Voice Guide software again. Using the same modem and computer, I now do not have caller ID showing in my call log. I used hyperterminal as suggested in your FAQ section and the called ID shows in there, under the most common modem string. Is it because the IVG was updated since I bought it last year or can you suggest what may be different and causing this. I have the same Win98 operating system and am running the same scripts.

[bobjdixon]

I have the same problem. Using hyperterminal I get the following caller id strings:

 

with AT#CID=1

===========

OK

RING

 

DATE = 0307

TIME = 1137

NMBR = 07971123123

 

with AT#CID=2

===========

 

OK

RING

 

MESG = 801A11010101083033303732313326020B313739373135373339363260

 

 

NMBR value changed to protect the innocent

 

In the log:

 

 

55765 0 tapie callstate OFFERING 65536 0 4

55775 0 tapie ring 1

58770 0 tapie ring 2

61764 0 tapie ring 3

64768 0 tapie ring 4

64768 0 Answer the call

64768 0 lineAnswer(65536) => 66509

64768 0 tapie callstate ACCEPTED 65536 0 0

65159 0 tapi Reply 66509 0

65169 0 tapie callstate CONNECTED 65536,0,0

65169 0 WorkingModeTAPI=

65169 0 WorkingModeScript=

65169 0 CID at StartLoadedVgs []

65169 0 CID at RunModule% []

65169 0 [Play 1] Playing

 

VoiceGuide 4.8.51 Registered

 

I though this might be a modem intialisation problem but I've run a serial port monitor alongside VoiceGuide and although the modem is definately sending the caller ID string, the VoiceGuide debug window does not show it.

[SupportTeam]

VoiceGuide uses the modem's TAPI drivers to control the modem and receive information from it, VoiceGuide does not issue the AT#CID=1 command directly and then read the responses directly.

 

The reason why VoiceGuide is not seeing the CallerID information is because the modems TAPI driver is not providing it to VoiceGuide.

 

Sometimes the modems TAPI configuration file supplied does not turn the CallerID on at all - as it needs to be ..

 

To see if AT#CID=1 is issued to your modem you can enable the commands tracing option.

See the modem's "Properties" window -> "Diagnostics" tab -> "Record to a Log" option.

 

When VoiceGuide is started and the modem is initialized the log of initialization commands can be seen. (example below):

 

03-09-2003 14:12:54.906 - File: C:\WINNT\System32\unimdm.tsp, Version 5.0.2175 - Retail

03-09-2003 14:12:54.921 - File: C:\WINNT\System32\unimdmat.dll, Version 5.0.2134 - Retail

03-09-2003 14:12:54.937 - File: C:\WINNT\System32\uniplat.dll, Version 5.0.2151 - Retail

03-09-2003 14:12:54.968 - File: C:\WINNT\System32\drivers\modem.sys, Version 5.0.2134 - Retail

03-09-2003 14:12:54.968 - File: C:\WINNT\System32\modemui.dll, Version 5.0.2146 - Retail

03-09-2003 14:12:54.968 - Modem type: Rockwell V.34 Voice, Speakerphone PnP

03-09-2003 14:12:54.968 - Modem inf path: mdmrock4.inf

03-09-2003 14:12:54.968 - Modem inf section: ROCK_08

03-09-2003 14:12:54.984 - Opening Modem

03-09-2003 14:12:54.984 - 115200,8,N,1, ctsfl=1, rtsctl=2

03-09-2003 14:12:54.984 - Initializing modem.

03-09-2003 14:12:55.000 - Send: AT

03-09-2003 14:12:55.000 - Recv: OK

03-09-2003 14:12:55.000 - Interpreted response: OK

03-09-2003 14:12:55.031 - Send: AT &F E0 V1 &C1 &D2 S95=47 S0=0

03-09-2003 14:12:55.031 - Recv: OK

03-09-2003 14:12:55.031 - Interpreted response: OK

03-09-2003 14:12:55.046 - Send: ATS7=60S30=0L1M1\N3%C3&K3B0 N1X4

03-09-2003 14:12:55.046 - Recv: OK

03-09-2003 14:12:55.046 - Interpreted response: OK

03-09-2003 14:12:55.046 - Waiting for a call.

03-09-2003 14:12:55.062 - Send: at#cid=1

03-09-2003 14:12:55.062 - Recv: OK

03-09-2003 14:12:55.062 - Interpreted response: OK

03-09-2003 14:12:55.078 - Send: ATS0=0

03-09-2003 14:12:55.078 - Recv: OK

03-09-2003 14:12:55.078 - Interpreted response: OK

 

In the above trace we can see that at#cid=1 is issued, and we can expect that this means the modems TAPI configuration file is designed to retrieve CallerID data.

 

The above test is a good start but in any further questions about configuring individual modems to return the Caller ID data via their TAPI driver should be directed to the modem manufacturer's support.

 

In many cases installing the modem using another driver which does enable Caller ID fixes things. Chances are when installing the modem you have a choice of various drivers you can use for it - or you can possibly use one of the drivers which come with Windows. For example the modem used to generate the trace above is a Dynalink modem, but the following driver was selected to use with it:

 

Rockwell V.34 Voice Speakerphone PnP

 

The Rockwell driver comes standard with Windows and it works well for most generic Rockwell based voice modems...

 

For more technical users:

 

You can modify the commands sent by the TAPI driver to the modem by modifying the modem's .INF files (in Windows INF directory). The log file above indicates which inf file/section is used by the driver:

 

03-09-2003 14:12:54.968 - Modem inf path: mdmrock4.inf

03-09-2003 14:12:54.968 - Modem inf section: ROCK_08

[bobjdixon]

I understand what you're saying here but as you can see from the attached log, the modem is being issued with the #CID command.

 

I've also linked a screendump showing the concurrent input/output from the modem and the VoiceGuide log.

 

Are you saying that this is still related to the tapi modem driver because it's quite clear that the modem is presenting the CLI information but VoiceGuide is not getting it.

 

Does the tapi driver filter the info from the modem and represent it to the VoiceGuide application, in this case not properly?

 

Sorry about the image size, 116K - compression looses resolution.

 

 

03-08-2003 15:10:12.607 - File: C:\WINDOWS\System32\tapisrv.dll, Version 5.1.2600

03-08-2003 15:10:12.607 - File: C:\WINDOWS\System32\unimdm.tsp, Version 5.1.2600

03-08-2003 15:10:12.607 - File: C:\WINDOWS\System32\unimdmat.dll, Version 5.1.2600

03-08-2003 15:10:12.607 - File: C:\WINDOWS\System32\uniplat.dll, Version 5.1.2600

03-08-2003 15:10:12.627 - File: C:\WINDOWS\System32\drivers\modem.sys, Version 5.1.2600

03-08-2003 15:10:12.627 - File: C:\WINDOWS\System32\modemui.dll, Version 5.1.2600

03-08-2003 15:10:12.657 - File: C:\WINDOWS\System32\mdminst.dll, Version 5.1.2600

03-08-2003 15:10:12.657 - Modem type: U.S. Robotics 56K Message EXT PnP

03-08-2003 15:10:12.657 - Modem inf path: oem14.inf

03-08-2003 15:10:12.657 - Modem inf section: Modem_DFVExtNH

03-08-2003 15:10:12.657 - Matching hardware ID: serenum\usr0083

03-08-2003 15:10:12.657 - 115200,8,N,1, ctsfl=1, rtsctl=2

03-08-2003 15:10:12.657 - Initializing modem.

03-08-2003 15:10:12.667 - Send: AT

03-08-2003 15:10:12.797 - Recv: OK

03-08-2003 15:10:12.797 - Interpreted response: OK

03-08-2003 15:10:12.807 - Send: AT&F1E0Q0V1&C1&D2S0=0

03-08-2003 15:10:12.937 - Recv: OK

03-08-2003 15:10:12.937 - Interpreted response: OK

03-08-2003 15:10:12.947 - Send: ATS7=60S19=0M1&M4&K1&H1&R2&I0B0X4

03-08-2003 15:10:13.077 - Recv: OK

03-08-2003 15:10:13.087 - Interpreted response: OK

03-08-2003 15:10:13.087 - Sending user initialization commands.

03-08-2003 15:10:13.097 - Send: at#cid=1+mca=1+mcr=6+mcv=0+mcf=0

03-08-2003 15:10:13.228 - Recv: OK

03-08-2003 15:10:13.228 - Interpreted response: OK

03-08-2003 15:10:13.238 - Waiting for a call.

03-08-2003 15:10:13.248 - Send: AT#CID=1

03-08-2003 15:10:13.378 - Recv: OK

03-08-2003 15:10:13.378 - Interpreted response: OK

03-08-2003 15:10:13.388 - Send: ATS0=0

03-08-2003 15:10:13.508 - Recv: OK

03-08-2003 15:10:13.508 - Interpreted response: OK

03-09-2003 10:41:29.460 - Session Statistics:

03-09-2003 10:41:29.460 - Reads : 36 bytes

03-09-2003 10:41:29.460 - Writes: 108 bytes

 

[SupportTeam]

I would say the problem is still because the TAPI layer does not issue the TAPI event informing VoiceGuide that CallerID information has arrived.

 

Its TAPI layer that filters the info from the modem and presents it to VoiceGuide. It does look like the driver is configuring the modem to report the CallerID, so it is a bit surprising that it then does not report it.

 

The following message would be visible in VoiceGuide trace when CallerID event is reported:

 

TimeStamp LineID Lev_CallerID [CallerNumber,CallerName]

 

I would try deleting the current modem and reloading it again using a different driver. Not too sure if you would be able to use the Rockwell V.34 Voice, Speakerphone PnP driver with this modem, but I suppose there's no harm trying.

 

Otherwise try getting the latest USR drivers (the .inf files) from http://www.usr.com/support/s-main-menu.asp

If the latest drivers for your modem still do not work it would be good to also ask USR why their .inf files do not configure the TAPI layer to report the CallerID.

 

BTW: Can you tell us what is that serial monitor program that you are using?

[Guest Guest]

Thanks for the response. I'm beginning to understand the problem now.

 

Heres the link to SerialMonitor - a good piece of kit.

 

http://www.hhdsoftware.com/sermon.html