Welcome to the Telephony Web Service SDK! The Telephony Web Service is a high level web service that allows your application to perform the following requests with simple, string based parameters: - makeCall: Creates a 2 party call from the originating party to the destination party. - singleStepConferenceCall: Adds the specified destination party to the active call on the originating party's terminal. - singleStepTransferCall: Transfers the active call on the originating party's terminal to the destination party. - answerAlertingCall: Answers an alerting call on the specified party's terminal. - disconnectActiveCall: Disconnects the specified party from the active call on their terminal. Any other parties on that call remain connected. In addition, the following methods are provided for session management: - attach: Allows the application to start a session. This is an optional step. It allows the app to authenticate the user and absorb the time required to initiate a session in a separate step from a telephony request. If these are not concerns, the app can simply set authentication credentials in the first service request sent. - release: When the app is done using the Telephony Web Service, it should send a release request to allow the server to end the session and free up resources. ----------------------- DIRECTORY STRUCTURE ----------------------------------- - telsvcsdk/wsdl: Contains the single most important item: the WSDL file. Using the web service tools of your choice, you can input the WSDL file and generate client side stubs for your application. The name of the WSDL file is TelephonyService.xml. - telsvcsdk/example/src: Contains the source code for the example application described below. - telsvcsdk/example/lib: Contains the Axis jar files and the generated client side Axis stubs for the example application described below. - telsvcsdk/example/ant: Contains the Ant tool, which is used to run the example application. - telsvcsdk/example/bin: Contains the shell script / batch file used to run the example appliation described below. ----------------------- EXAMPLE APPLICATION ----------------------------------- The example application is a simple Java GUI based client for the telephony service. It allows the user to log in, then perform the basic telephony operations listed above. This application uses Jakarta Axis as it's client side SOAP handling infrastructure. telsvcsdk/example/lib contains all of the Axis client side jars, as well as the generated TelephonyService stubs. If you would like to use Axis as your client side SOAP infrastructure, you can feel free to use these jar files for your application. Alternatively, you can use the WSDL file and the platform of your choice. In order to run the application, simply type "ant.sh runTelSvcClient" (Linux) or "ant.bat runTelSvcClient" (Windows). The user is first presented with a login screen. This screen has text boxes that allow the user to specify the following parameters: - Service IP: This is the IP address of the server that is hosting the telephony web service. - Username: The user's username. The user should have been administered either through the User Web Service or through the AE Services OAM web pages. They must have been provisioned in the AE Services OAM Web pages to have permission to control the originating extension entered on the next screen. - Password: The user's password. - Switch Name: This is the name of the Communication Manager as administered in the AE Services OAM web pages. There is also a checkbox that allows the user to specify whether they would like to use SSL to connect securely, or use the unsecure port. After the user enters this information, they will be authenticated with the Telephony Web Service, and a session will be created. At this point, the user can enter an originating extension and (in most cases) a destination extension, then click one of the buttons to initiate a request. makeCall, singleStepConferenceCall and singleStepTransferCall all require both an originating and a destination extension number. answerAlertingCall and disconnectActiveCall only use the originating extension number: the destination extension number is ignored. All operations require that the user has permissions to control the originating extension number. These permissions are administered through the AE Services OAM web pages. The AE Server comes preconfigured with with a certificate that has been signed by a sample certificate authority. This certificate is by default the same on all servers. Needless to say, this is not an extremely secure configuration! This is intended to allow SSL to be working by default "out of the box", and is not intended to be a long term secure configuration. Much better is to use the /usr/share/tomcat4/bin/makecert.sh script to generate a new script that is signed by the sample CA. This will use unique keys for the SSL handshake, so the data will be secure, and it will work with the default keystore that is distributed with the SDK. It still doesn't provide a great solution for server authentication, however, as anbody that has an AE Server can generate a certificate signed by the sample CA. 2 alternatives exist to get to a truly secure solution: 1) Use the makecert.sh script to generate a new private key / certificate. Then use the java keytool command to export a certificate for the avayakey alias. Transfer this certificate file to your client machine, and use the replaceKeystore.sh or replaceKeystore.bat script to import this certificate into the client keystore as a trusted certificate. Performing these steps will ensure that the client will trust only that specific AE Server. 2) Use an alternative PKI (Public Key Infrastructure) to sign the certificate for your AE Server, and use the replaceKeystore.sh or replaceKeystore.bat scripts to import a certificate into your client keystores. -------------------- EXAMPLE CLIENT STUB GENERATION --------------------------- This section will demonstrate how you can generate client stubs from the WSDL file. It shows how to use the Axis toolset to do so. You'll need to have the following jars in your classpath: axis.jar commons-discovery.jar commons-logging.jar jaxrpc.jar saaj.jar wsdl4j.jar Then simply execute the following command: java org.apache.axis.wsdl.WSDL2Java TelephonyService.xml There are many options on this command, to see them all execute this command: java org.apache.axis.wsdl.WSDL2Java /?Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.