readme.txt

AVAYA IPO 430 devlink demo代码

DevSpice Sample

Copyright 2002 Avaya


Introduction

DevSpice is an application that uses TAPI3 and the IP Office device specific interfaces. It requires the IP Office TAPI 3 compliant Telephony Service Provider (TSP), tspi3w.tsp, to be installed and the IP Office MSP (officemsp.dll) to be registered before it can be run. These can both be installed using the TAPI3Install.exe on this CD.  If you have the IP Office TAPI 2 TSP installed, this should be removed from the list of providers before installing the TAPI 3 TSP. As this sample uses TAPI 3 it can only be run on Windows 2000 or Windows XP. The media streaming capabilities of the MSP depend on the IP Office wave driver which must be installed and licenced.

The Code

DevSpice is written in a simple, procedural fashion. The project contains a single source file, devspice.cpp which contains all the code. A message loop responds to events generated by the dialog box which calls functions to demonstrate the features. CPoint.h contains code to handle events generated by the IPOfficePrivateEvent connection point. Interfaces.h contains definitions of the interfaces exposed by the MSP. officemsp_i.c contains GUIDs for all the interfaces.

The purpose of DevSpice is to demonstrate the use of TAPI3 and the IP Office device specific interfaces. It is not an example of how a TAPI3 application should be implemented. As a result some aspects of DevSpice are not robust. However this should not distract you from using DevSpice as a starting point in using the TAPI3 driver as long as the usual COM programming Paradigm is followed.

Building the Sample

The sample should be built on a Windows XP machine with the Microsoft Platform SDK, or on a Windows 2000 machine with a Platform SDK that contains TAPI3 definitions. A project file for Microsoft Visual C++ 6.0 is included with the sample code.

TAPI setup

DevSpice starts by opening a single IPOffice TAPI line. You should configure your IP Office TSP to first party. If you wish to use the sample to demonstrate the media streaming abilities of the MSP, make sure that the line you choose is a WAV user (with a name that begins with "TAPI:").  See the CTI Link Installation Manual and TAPI Link Developers Manual for details of WAV Users.

Usage:

Number to call:
Enter the number that you wish to call here and click the Make Call button to call. Click the Disconnect button to drop the call.

VoiceMail Messages:
This shows the number of voicemail messages on the controlled DN. The content is updated when the number of voicemail message changes. 

Account Code:
This allows an account code, that has been configured in Manager, to be set for a call.  There must be a call in progress for this to work.  Therefore this capability cannot be used for users that have "Forced Account Code" set.

Call Data:
This sets the Call Data for a call.  There must be a call in progress for this to work.
Using the sample to set call data will fail on Windows 2000. Please refer to the IP Office TAPI manual.

Agent:
Login/Logout:
The "Logged In" radio button indicates whether the user is currently logged in or out.
The Login button will log a user in that is currently logged out.
The Logout button will log out a user that is currently logged in.

Monitor:
This allows the controlled DN to monitor the call on the specified extension in a specified group. The controlled DN must have the 'Intrude On' property set and the monitored DN must have the 'Can not be intruded' property unset. The controlled DN and the monitored DN must belong to the same group and the controlled DN must be monitoring the group that the monitored DN belongs to (in Manager, set User\Telephony\Monitor Group). Also when the monitor command is issued the controlled DN must be offhook or the function will not work!

Intrude:
Requires similar conditions as Monitor but the controlled DN not need to be offhook. The controlled DN is effectively placed into conference with the other call parties.

Group:
Pickup Extn:
This picks up a call that is ringing at another extension.  The number of the ringing extension must be entered into the edit box.

Pickup Members:
This will pick up a call to a member of a group, whether the call is directed at the group or an extension within the group.  The number of the group must be entered in the edit box.

Enable/Disable:
The "In Group" radio button indicates whether a user is currently in a group.  Enable will enable a user in a group.  Disable will disable a user from a group.

Pickup Group:
This will pick up any call ringing a group that you are a member of. the number of the group need NOT be entered in the edit box.

Pickup Any:
This will pick up any call ringing an extension.  The number of the ringing extension need NOT be entered in the checkbox.

Diverts:
The "Divert Settings?" button will retrieve the divert settings for your extension and display the settings using the check boxes and divert destination edit box.  Using the same checkboxes and exit box, you can change the settings and press Apply to apply them.


Wave File:
Record:
This command records the current call to the specified wav file. A beep is played to signify recording has started.The resultant wav file can be played using the Windows media player or using DevSpice.exe. Note that you can not playback the recording in the same call as you recorded it. You must disconnect the call first, make a new call and playback the recording.

Stop: 
This command stops the recording. A beep is played to signify recording has stopped. Note that pressing stop when the call is not being recorded will cause the error measage 'StopRecord failed'.

Play:
This command stops the current audio stream,  starts playing the specified wav file and attaches the output to the audio stream. When the wav file finishes the audio stream is automatically reattached.

Stop:
This command stops the wav file from playing and will reconnect the audio stream. Note that pressing stop when no wav file is playing will cause an error message 'StopPlay failed'.