| Author |
|
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: July 30 2010 at 8:51am | IP Logged
|
|
|
LS Support Note:
We received this email from a new customer. We wanted to post this information here so that others can benefit from the information.
------------------------------------------------------------ ------
From the customer:
We are trying to develop an IVR/dialer system using SIP through C# (VS 2008) and it appears that your API will help us accomplish this but I want to make sure you API can provide the following functionality.
1. Handle high volume dialing (400+ lines)
2. Play audio files
3. Play audio streams
4. Capture and send DTMF tones
5. Call recording
6. Conferencing with coaching and monitoring support
7. CPA (Call progress analysis, detect live body, answering machine, busy, no answers etc. for outbound dialing).
This IVR/dialer system would be hosted at a single location to provide our clients with a messaging service so we can broadcast messages and interact with the user over the phone like taking payments. So it appears that the licensing would be per installation or would there be a per line charge.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: July 30 2010 at 10:03am | IP Logged
|
|
|
Hello Eric,
Thanks for your email.
Yes the VOIP media Engine (LME) is a good fit for VOIP IVR development using VS2008/VS2010 and C#.
All the functionality of the LME is available to both native code (C/C++) and .NET language developed applications.
I will take your points one at a time…
Handle high volume dialing (400+ lines):
512 lines is the highest line density we currently offer. All lines can be used concurrently. We can theoretically increase this number to whatever we want however there are host operating system, memory and hardware limitations that make increasing this number meaningless.
The actual number of concurrent line you will be able to use depends on how you code your C# VOIP application and the speed and throughput of your host hardware. Mileage varies but we can assist you to ensure that you get the most out of the LME and your application code.
Play audio files:
Not a problem. You can use built in support for reading audio files and then send the sample block data from the files directly to the phone line via each phone line’s transmit IVR output interface. It is very easy.
Play audio streams:
Yes you can do this if you can obtain audio sample block data from the stream source. In this case, your C# code will take sample blocks received from the stream source and write them out to the phone lines transmit IVT outputs – just like for audio files above.
Capture and send DTMF tones:
Full in-band and RFC2833 DTMF generation and detection are supported by the LME.
Call recording:
Yes. Complete call recording on a per phone line basis is supported. You can record the received call audio by itself, the transmitted call audio by itself or digitally mixed Tx+Rx call audio.
Conferencing with coaching and monitoring support:
The LME supports all of these conferencing models. The LME’s conferencing model is generic, powerful and quite amazing.
How your C# VOIP application determines the signaling between conference clients to control how each client is treated in the conference session is also entirely up to you (use SIP signaling or DTMF control tones for example).
Please allow me to give you an example:
Let’s assume there is a customer, an operator and a manager/coach. All three can be connected to the LME based server app. Here are the three conference scenarios we can handle and see the most:
1)
Customer and operator can speak and hear each other. Manager silently listens.
2)
Customer and operator can speak and hear each other. Manager can hear and speak to the operator while the customer does not hear the “coaching”.
3)
Customer, operator and Manager are in a full conference session. All can talk and hear each other.
These conference scenarios are all handled by the LME. The C# application only needs to tell the LME how to manage the conference sessions.
CPA (Call progress analysis):
CPA = Call progress analysis, detect live body, answering machine, busy, no answers etc. for outbound dialing.
This is where we lack a bit. :( At this point our customers have implemented their own CPA to fit their specific deployment scenarios.
They accomplish this by accessing the received audio sample blocks from LME phone line received audio and processing the sample blocks as their application requires.
I understand the need for LS to add robust generic CPA capability to the VOIP Media Engine. We would certainty like to work with your group to make this happen.
You >>>
This IVR/dialer system would be hosted at a single location to provide our clients with a messaging service so we can broadcast messages and interact with the user over the phone like taking payments. So it appears that the licensing would be per installation or would there be a per line charge.
<<< Randal
You are correct – the licensing of the LME (your VOIP server) is a function of deployment and not per line licensing. This web page (see the Licensing Requirements section) talks about LME licensing:
http://www.lanscapecorp.com/ProductPages/LanScapeVoipMediaEn gine.asp
To summarize the licensing:
Infinite deployment (any number of your apps per year) requires that the license fee be paid each year you deploy your VOIP apps using the LME. Good for soft phone or other high volume deployments.
“Block deployment” allows you to deploy up to 10 of your LME based products (your servers) for each LME license purchased. You purchase new licenses as needed to deploy addition blocks of 10 of your servers. This incremental approach is for lower volume deployments.
Thanks Eric,
Randal
|
| Back to Top |
|
| |
|
|
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Pre-Sales Technical Support
Topic: Developing an IVR/dialer using SIP and C# (VS 2008)
