support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: February 28 2005 at 10:33am | IP Logged
|
|
|
Dear LanScape Customers,
We have been getting many questions regarding the types of example software applications that are shipped with the LanScape VOIP Media Engine. Attached to this post is the ReadMe.txt file that is part of the VOIP Media engine - Version 5.10 installation image.
This ReadMe file should be able to give you additional information regarding what the example VOIP applications will do.
If you have any other questions, please do not hesitate to post your questions to this forum.
Best regards,
LanScape Support
---------------------------------------------------------
ReadMe file for LanScape VOIP Media Engine Software examples.
Building the Examples:
Before building any of the example applications, you must first update the
Microcode\LanScapeVME.C file image with the "LanScapeVME.C" file you received with your license
information.
The current LanScapeVME.C file image in the Microcode directory is a dummy file. You must
take your licensed copy of the LanScapeVME.C file you received in your distribution and replace
the dummy copy. If you do not do this, the software example applications will build correctly
but will not function properly.
After replacing the dummy copy of the LanScapeVME.C file image with your valid image, start Visual Studio
and open any of the workspace files (*.dsw) for any of the software examples. Perform a "build all"
operation to build the image.
Each example software project has its own workspace and project file. You can build all examples
separately. If you want to build all of the examples at one time, open the BuildAll.dsw workspace.
LanScape VOIP Media Engines are purchased with specific capabilities built in or removed. If your
purchased version of the media engine supports all functions used by the example software, those functions
will be used. If your copy of the telephony engine does not support a particular feature, those
features will not be available.
MultiLine Phone:
This example demonstrates the basics of using the LanScape VOIP Media Engine in the context
of a multi line soft phone. All current telephony features are supported such as:
Make outgoing calls
Answer incoming calls
Call hold
Call transfer
Busy out line
Call conferencing
The example uses as many default features of the telephony engine as possible in an effort
to keep the example as simple as possible. For many instances, this example project can be used
as the basis for your own multi lined soft phone.
The example supports a maximum of 2 lines. If you have purchased a telephony engine that supports
more than 2 phone lines, only 2 lines will be created and used.
If you purchased a telephony engine that only supports a single phone line, the second phone line
of the example application will be disabled. Conferencing functions will also be disabled.
Conferencing capabilities are supported by telephony engines that support 2 or more phone lines.
Telephony Echo Server:
This example is based on the 2 line soft phone in the preceeding example. It however automatially
answers incoming phone calls. When an incoming call is answered, all voice media data that is
sent to the application is looped back to the originating end of the call.
The software also displays all received data from each supported phone line using a visual
format similar to a spectrum analyzer. This example application is a good example of how IVR
and/or gateway applications can access received streaming audio from each phone line.
It is a good idea to build this example application because it can be used as a simple echo server
that can be used to test your specific application.
Conference Server:
Note:
To successfully build and use this software example, you must purchase a multi
line version of the LanScape VOIP Media Engine that includes conferencing capabilities.
To experience the full capabilities of the example application, your telephony engine
should support three or more phone lines.
This example application supports multiple phone lines (up to six lines). It accepts and automatically
answers incoming phone calls on any of its phone lines. When 2 or more phone calls are active, the
application switches all active calls into a conference session.
When the calls are placed into a conference session, all phone lines will share audio data
regardless of the originating sample rates or data formats.
Signle Line Soft Phone:
This example application is supplied so you can interact with the Dual Line IVR Server example
application. This single line soft phone will allow you to initiate or receive phone calls. Call
hold and call transfer are also supported.
The single line phone supports a DTMF keypad on its user interface. If you call another SIP
enabled device, you can send DTMF tones down the phone line to the far end of the call. You
must use this single line phone when calling the Dual Line IVR Server example application if
you want to transact with the IVR server.
Dual Line IVR Server:
This application supports multiple phone calls at any one time. The application will answer
an incoming phone call automatically. When the phone call is answered, the user will hear
a prerecorded message. The prerecorded message is streamed to the phone line using the
telephony engine's IVR phone line API interface.
In order to interact with this IVR server example, you should use the single line phone
software example application. The single line phone supports dynamic generation of DTMF
digits to the phone line.
The Dual Line IVR Server will stream prerecorded voice prompts to the persom who made the
phone call. The IVR server will give the user menu options that can be selected using
a DTMF touch Tone(tm) keypad. The IVR server continuously monitors the received voice path
and will detect all supplied DTMF tomes and alter its menu propmts accordingly. If you
do not supply menu selection via DTMF within a time out period, the IVR server will inform
you that you are not responding. When it does that, it terminates the phone call.
This application can act as a base for automated attendant, voice mail, and answering
machine applications.
Simple Console App:
The sole purpose of this example application is to show that it does not take much
software programming to initialize the LanScape VOIP Media Engine(tm). This application
also has no knowledge of network programming or other such details.
This Win32 console example initializes the telephony engine and polls for incoming phone
calls. Its so sinple it doesn't even use the media engine's telephony event mechanism.
When the console application detects an incoming phone call, it will generate an incoming
ring. Incoming ring continues until the caller terminates the call.
Example library support:
There are two binary libraries distributed with the examples. One library supports the
spectrum analyzer display/rendering and the other supports required DTMF tone generation
and detection. These libraries are distributed in binary form only and no source code is
made available.
These libraries are designed to operate with the supplied example telephony applications.
The libraries are not designed to function with other applications.
End ReadMe.txt
LanScape Corporation
|
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Pre-Sales Technical Support
Topic: Example VOIP Software Applications
