Author |
|
bsummers Intermediate
Joined: October 29 2005 Posts: 5
|
Posted: October 29 2005 at 8:31am | IP Logged
|
|
|
Good Morning,
I am interested in the OEM product. Can you tell me the licensing terms or point me to a site with more details on the terms of the license?
Can the license be used by multiple developers in my organization? What is license for the end clients?
A technical question: Is there a COM interface for your VoIP SDK?
Regards,
Bob
|
Back to Top |
|
|
lsadmin Administrator
Joined: October 01 2003 Location: United States Posts: 19
|
Posted: October 29 2005 at 8:42am | IP Logged
|
|
|
Bob,
Licensing Requirements are simple. Purchase a license to include the VOIP Media engine into a single end product.
We impose no limit on the number of developers that can install and use the product. Distribute as many copies of your end application as you see fit. No per copy royalties apply.
More info can be found here:
http://www.lanscapecorp.com/ProductPages/LanScapeVoipMediaEn gine.asp
Look for the section entitled "Licensing Requirements" 1/2 way down the page.
COM interface:
None available yet. The VOIP API in DLL form has worked for customers well so far. The few customers that wanted a COM interface due to them integrating the VOIP Media Engine into a scripting environment have rolled their own COM wrapper.
Best regards,
Sales
|
Back to Top |
|
|
bsummers Intermediate
Joined: October 29 2005 Posts: 5
|
Posted: October 29 2005 at 8:46am | IP Logged
|
|
|
Thank you for the information. The licensing is very simple, and that is good. We will evaluate the software in the next week. Can you give me some examples of commercial products that are using your product?
I have looked around your site and I do not see any clear statements about who is using your product.
Regards,
Bob
|
Back to Top |
|
|
lsadmin Administrator
Joined: October 01 2003 Location: United States Posts: 19
|
Posted: October 29 2005 at 8:48am | IP Logged
|
|
|
Unfortunately we do not release this kind of information. :(
Best Regards,
Sales
|
Back to Top |
|
|
bsummers Intermediate
Joined: October 29 2005 Posts: 5
|
Posted: October 29 2005 at 8:52am | IP Logged
|
|
|
I appreciate your response. I have been working with the toolkit and find it useful so far. When registered, does the developer have control over the SIP stack name that is transmitted in the header. Currently it reports "lanscape trial edition, etc..". Does the licensed version use our company name in the protocol?
Thank you and have a great weekend,
Bob
|
Back to Top |
|
|
bsummers Intermediate
Joined: October 29 2005 Posts: 5
|
Posted: October 29 2005 at 8:54am | IP Logged
|
|
|
Hi Bob,
The normal (non trial) version changes the "User-Agent:" header to something different. Here is an INVITE message from a non trial version:
INVITE sip:tolson@lanscapecorp.dnsalias.com:7000 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:7003
From: <sip:9438252@192.168.1.2:7003>;tag=56a172d
To: "Tom Olson" <sip:tolson@lanscapecorp.dnsalias.com:7000>;tag=569df5 7
Contact: <sip:StandAlone@192.168.1.2:7003>
Call-Id: 5563f964-e28e-4ee3-ac55-2f12cb2f058a-000005e4@192.168.1.2
CSeq: 90824649 INVITE
Max-Forwards: 70
Content-Length: 154
User-Agent: LanScape VOIP Media Engine/5.10.0102 (www.LanScapeCorp.com)
Content-Type: application/sdp
v=0
o=LanScape 3330270214 3330270214 IN IP4 192.168.1.2
s=LanScape
c=IN IP4 0.0.0.0
t=0 0
m=audio 16172 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
Regardless of the version, the "User-Agent:" header cannot be changed by the application via the API.
Repost as required,
Support
|
Back to Top |
|
|