Capturing Callerid And User Entered Data

[SupportTeam]

Nicholas wrote:

 

I've spent a few days reviewing web information about ActiveX TAPI components, and various TAPI compliant boards, etc However, I think your product looks just about the easiest to use, but I am concerned it may not suit my needs.

 

What I want to build is a fairly standard IVR system to handle incoming calls only (will never need to phone out)

 

A crucial issue for me is that I must be able to get the Callers phone number and detect which keys they press on their phone and transfer that as data to a VFP (Microsoft Visual Foxpro .... version 8) application I will have running on the same network/LAN

 

Is this possible with VoiceGuide and if so how ?

[SupportTeam]

CallerID is captured by the system automatically.

 

To let users enter data you can just use a "Get Numbers" module. See: http://www.voiceguide.com/vghelp/html/modGetNumber.htm

 

Information captured by system or entered by the caller can be saved in databases using a "Database Query" module. See: http://www.voiceguide.com/vghelp/html/modDbQuery.htm

 

If the database is on the network then you probably need to setup an ODBC driver to it and then have VoiceGuide use the database via the ODBC driver. See: http://www.voiceguide.com/vghelp/html/conf...cDataSource.htm

 

All data is also saved in VoiceGuide's own log file. Just press the "Show Log" button on VoiceGuide's main screen to see the call log.

 

Please also see the Recommended Hardware section: http://www.voiceguide.com/suppRecomHardware.htm

[Guest TheyCalled Paul]

Using VG for updating a database is very easy - just be careful. We have been pushing voiceguide data into our MS SQL Server for 16 months now and are now on the verge of launching another site with V7 as our platform. Each call for us starts with VG getting the DNIS and Callers phone number which we push into sql upon answering the call. We have it return back information which enables us to place a 2nd call and then we bond them. We are updating our data along with way with duration and information about the call. We use stored proc's to push data in but you could create sql statements and use them as well. If you are pulling back data just make sure you check for null and eof. Foxpro should be perfect for this. You might want to make little vbs programs at first and practice pushing data this way. When writing new scripts I use the line monitor to watch what its doing and the logs are very helpful as well. Yes, I use MSGBOX alot if its not acting as planned - but I assure you it works.

 

Paul