![]() |
Home |
![]() |
| About TAPI |
![]() |
| Exclusive Articles |
![]() |
| TAPI-Applications |
![]() |
| TAPI Service Providers |
![]() |
| TAPI-Hardware |
![]() |
| Application Development |
![]() |
| TSP Development |
![]() |
| Resources |
Search
![]() |
Show Changes |
![]() |
Edit |
![]() |
|
![]() |
Recent Changes |
![]() |
Subscriptions |
![]() |
Lost and Found |
![]() |
Find References |
![]() |
Rename |
History
| 09.08.2007 20:40:39 |
| 213.239.248.120 |
| 31.07.2007 16:13:57 |
| -80.152.131.144 |
| 31.07.2007 16:12:52 |
| -80.152.131.144 |
| 31.07.2007 16:09:29 |
| -80.152.131.144 |
| 31.07.2007 16:04:14 |
| -80.152.131.144 |
![]() |
List all versions |
Atsp.c is a sample TAPI application that shows how to write a telephony service provider (TSP) for a modem. TSP's are used by the TAPI applications to interface with telephony devices. Call control is established in the tapi application through the TSP interface (TSPI). This sample will not run by itself, but can be used with a full TAPI application. The functionality can be tested in the TAPI TB20 or TB3X browser. For information on the TAPI browser, see the tools section of the Platform SDK (PSDK). This sample illustrates the basic TSPI required to initiate outgoing modem and interactive voice calls.
http://www.tapi.info/downloads/samples/psdk/tapi2/Atsp32.zip
Dialer.c is a sample TAPI 2 application that illustrates some of the basic TAPI dialing features. The aplication will: (1) initiates/drop calls, (2) handles simple TAPI request for other applications initiating/dropping calls on their behalf, (3) monitor incoming/outgoing calls and keep a call log based on the user's request. The application will read the speed dial button settings from the Dialer.ini file under the Speed Dial Settings section. The settings for the last dialed numbers and window position are also stored in the ini file under the Last dialed numbers and the Preference sections.
http://www.tapi.info/downloads/samples/psdk/tapi2/dialer.zip
The TapiComm sample uses both the Telephony API and the Win32 Communications API to demonstrate one way to implement a very simple TTY application. While the user interface and TTY emulation are very rudimentary, the TAPI and comm modules are fairly complete. For more information, see the tapicomm.doc or tapicomm.rtf file included in the TapiComm sample directory.
http://www.tapi.info/downloads/samples/psdk/tapi2/tapicomm.zip
Ansmach is a sample TAPI 3.0 application that waits for and answers incoming phone calls. It uses the Media Streaming Terminal (MST) to play out a recorded message and then records the caller's message to a file. In order to receive incoming call notifications, as well as any call state event notifications, the outgoing ITCallNotification interface
must be implemented by the TAPI 3.0 application, and registered with TAPI 3.0 through the IConnectionPoint mechanism. For more information on IConnectionPoint, and IConnectiontPointContainer, please refer to the COM documentation.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/ansmach.zip
FileTerm is a sample TAPI 3.1 application that waits for and answers incoming calls. It uses the File Terminals to play out a recorded message and then records the caller's message to a file. In order to receive incoming call notifications, as well as any call state event notifications, the outgoing ITCallNotification interface must be implemented by the TAPI 3.x application, and registered with TAPI 3.1 through the IConnectionPoint mechanism. For more information on IConnectionPoint, and IConnectiontPointContainer, please refer to the COM documentation.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/fileterm.zip
T3IN is a sample TAPI 3.0 application that waits for and answers incoming phone calls. In order to receive incoming call notifications, as well as any call state event notifications, the outgoing ITCallNotification interface must be implemented by the TAPI 3.0 application, and registered with TAPI 3.0 through the IConnectionPoint mechanism. For more information on IConnectionPoint, and IConnectiontPointContainer, please refer to the COM documentation.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/incoming.zip
T3OUT is a sample TAPI 3.0 application that makes outgoing phone calls. This sample shows the most basic TAPI 3.0 functionality - finding an appropriate address object and creating a call on it.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/outgoing.zip
PlgTerm is a sample TAPI 3.1 application that shows how to create a pluggable terminal. It uses MSPBase classes and DirectShow\BaseClasses.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/pluggable.zip
RendSam is a simple program demonstrates how to use TAPI 3.0 Rendezvous Controls COM interfaces to open an ILS directory, configure a conference, add a conference, enumerate conferences, delete a conference, configure a user, add a user, enumerate users, and delete a user. A few methods in TAPI 3.0 SDPBLB COM interfaces are also used in configuring a conference.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/rend.zip
The purpose of TAPIRecv sample is to illustrate the use of Media Streaming Terminal (MST) for retrieving audio data from a TAPI media stream. TAPIRecv is the receiving side of the call. It accepts a call and uses the MST to get incoming audio data, which it saves to a local audio file, recording.wav. When the remote side disconnects the call, the application exits.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/tapirecv.zip
The purpose of TAPISend sample is to illustrate the use of Media Streaming Terminal for injecting live audio data into a TAPI media stream. TAPISend initiates a TAPI call, opens a wave file and uses Media Streaming Terminal (MST) to send audio data from the file to the remote machine. When the file is processed, TAPISend disconnects the call and exits.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/tapisend.zip
This application allows users to create agents and agent sessions, monitors the corresponding address for incoming calls, allows the user to answer/disconnect the incoming calls and sets the agent and session states to reflect these changes. In order to receive incoming call notifications, as well as any call state event notifications, the outgoing ITCallNotification interface must be implemented by the TAPI 3.0 application, and registered with TAPI 3.0 through the IConnectionPoint mechanism. For more information on IConnectionPoint, and IConnectiontPointContainer, please refer
to the COM documentation.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/acdclient.zip
This application demonstrates the working of an ACD proxy application. This application allows creation of ACD groups and software call queues, handles proxy request messages from clients and sends status messages back to TAPI to reflect any changes in status. You can set the users who will be allowed to create agents on this proxy. All the above details should be specified in a file proxy.ini.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/acdproxy.zip
These are the sources for Media Streaming Provider Base Classes. See Platform SDK and SampleMSP sample for more information on using MSP Base Classes for writing Media Streaming Providers.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/mspbase.zip
SampMSP is a sample TAPI 3.1 MSP (media service provider) that shows how to use the MSP base classes. It is set up to work with audio using DirectShow, but it does not implement creation or connection of any specific transport filters. It is meant as a starting point which can be expanded to suit a particular type of transport. The sample is of interest to devlopers of TSPs (telephony service providers) who want to enable TAPI 3.1 applications to stream media with their TSPs. A TSP that does not have an acoompanying MSP will be fully functional for call control but will not support the media streaming features of TAPI 3.1. ATSP32.TSP in the Tapi2 sample directory tree is a Sample TSP that implements the necessary TSPI_ functions that link to this Sample MSP. Please see the Windows SDK documentation for more information.
http://www.tapi.info/downloads/samples/psdk/tapi3/cpp/samplemsp.zip
CALLHUB is a sample TAPI 3.0 application that monitors call and callhub events on all tapi addresses present on the machine, for all media modes.
http://www.tapi.info/downloads/samples/psdk/tapi3/vb/callhub.zip
DTMF is a sample TAPI 3.0 application that is able to generate and detect DTMF tones over an outgoing call made on an address that supports DTMF (e.g. a voice modem address).
http://www.tapi.info/downloads/samples/psdk/tapi3/vb/dtmf.zip
This file contains TAPI constants which are not part of the TAPI3.x Type library. It can be added to a VB project as module (.bas).
http://www.tapi.info/downloads/samples/psdk/tapi3/vb/include.zip
INCOMING is a Visual Basic sample TAPI 3.0 application that waits for and answers incoming calls: phone calls or H323 audio calls. In order to receive incoming call notifications, as well as the related call state event notifications, the application must call RegisterCallNotifications specifying the media types for which it wants to be notified (therefore
not all incoming calls will be offered to the app, but only those that have the desired media types). This sample registers for receiving audio calls (it registers for the "audio" media type).
http://www.tapi.info/downloads/samples/psdk/tapi3/vb/incoming.zip
OUTGOING is a sample TAPI 3.0 application that makes outgoing asynchronous audio (and eventually video) calls. This sample shows the most basic TAPI 3.0 functionality - finding an appropriate address object and creating a call on it.
It also shows some more advanced TAPI 3.0 functionality - how to use the stream interfaces to make video calls.
http://www.tapi.info/downloads/samples/psdk/tapi3/vb/outgoing.zip
USBPhone Sample is a Visual Basic sample TAPI 3.1 application that makes and receives audio calls on a USB phone using H323 Line. This sample shows the use of USB phone in two states, when phone handling is enabled and when it is disabled. In both states outgoing and incoming audio calls can be handled.
http://www.tapi.info/downloads/samples/psdk/tapi3/vb/usbphone.zip
You could originate your call from any of the TAPI3 addresses available on your computer: modem, H323 Line, etc. Different addresses support different types of "target party" addresses: modems support only Phone Number, H323 Lines support Phone Number and IP Address and Machine Name etc. Fill in the target address and select its type (phone number, ip address, etc). Choose the originating address and call properties: you can setup the call to be audio only or with outgoing video. Press Connect to call your party. You can hang-up your call at any time by pressing Disconnect. This sample registers itself on all available tapi3 addresses in order to receive incoming calls. You have the possibility to answer/reject the incoming calls.
http://www.tapi.info/downloads/samples/psdk/tapi3/vbscript/calldemo.zip
What functionality this sample does show: Rend.dll usage (connecting to ILS server, conference info extraction), Call management, Media and terminal management (including preview window), Video substreams management
http://www.tapi.info/downloads/samples/psdk/tapi3/vbscript/conferencejoin.zip
This sample allows you to: Obtain a list of IP Multicast conferences published on a given ILS server, Create new IP Multicast conferences, Delete IP Multicast conferences, Directly edit properties of existing conferences using SDPblob editor
http://www.tapi.info/downloads/samples/psdk/tapi3/vbscript/confmgr.zip
The JT3Call sample application/applet demonstrates the use of the Telephony API 3.0 to make outgoing calls. Depending on installed hardware, the applet will allow you to communicate with others over an IP network connection using streaming audio and video. One-to-one connections are supported, but you may also connect to network conferences in which you can communicate with multiple parties simultaneously.
http://www.tapi.info/downloads/samples/psdk/tapi3/java/jt3call.zip
The JT3Conf sample application/applet demonstrates the use of the Telephony API 3.0 and Rendevous Controls to create, delete, and join conferences. Depending on installed hardware, the applet will allow you to communicate with
others over a network connection using streaming audio and video.
http://www.tapi.info/downloads/samples/psdk/tapi3/java/jt3conf.zip
The JT3Rec sample application/applet demonstrates the use of the Telephony API 3.0 to receive incoming calls. Depending on installed hardware, the applet will allow you to communicate with others over a network connection using streaming audio and video.
http://www.tapi.info/downloads/samples/psdk/tapi3/java/jt3rec.zip
Recent Topics